Difference between revisions of "Neutron/LBaaS/SLB"
m (Liudong moved page Neutron/LBaaS/Huawei SLB to Neutron/LBaaS/SLB) |
|||
| Line 1: | Line 1: | ||
| − | + | == Description === | |
| − | + | Implementation of Plugin Driver and Device Driver to support SLB. SLB is a load balance software which provide L4/L7 rules provider released by Huawei.<br/> | |
| − | Implementation of Plugin Driver and Device Driver to support | ||
| − | |||
| − | |||
| − | |||
| + | == Use Cases === | ||
Cloud service providers who choose to adopt OpenStack and Neutron for their cloud orchestration, will also be able to provide load balancing through the Huawei SLB.<br/> | Cloud service providers who choose to adopt OpenStack and Neutron for their cloud orchestration, will also be able to provide load balancing through the Huawei SLB.<br/> | ||
| − | + | == Implementation === | |
| − | |||
==== The Provisioning ==== | ==== The Provisioning ==== | ||
| − | + | While using the SLB Neutron LBaaS driver, any operation which doesn't involve an active VIP model object will be simply managed and written in the DB, without changing the current network state.<br/> | |
| − | While using the SLB Neutron LBaaS driver, any operation which doesn't involve an active VIP model object will be simply managed and written in the DB, without changing the current network state. | ||
| − | |||
==== Asynchronous Calls==== | ==== Asynchronous Calls==== | ||
| − | |||
==== State Synchronization ==== | ==== State Synchronization ==== | ||
| − | + | == Configuration === | |
| − | |||
Revision as of 06:54, 17 December 2013
Contents
Description =
Implementation of Plugin Driver and Device Driver to support SLB. SLB is a load balance software which provide L4/L7 rules provider released by Huawei.
Use Cases =
Cloud service providers who choose to adopt OpenStack and Neutron for their cloud orchestration, will also be able to provide load balancing through the Huawei SLB.
Implementation =
The Provisioning
While using the SLB Neutron LBaaS driver, any operation which doesn't involve an active VIP model object will be simply managed and written in the DB, without changing the current network state.
