Difference between revisions of "Neutron/LBaaS/RadwareAlteon"
| Line 32: | Line 32: | ||
== Config Life Cycle == | == Config Life Cycle == | ||
Create Actions: | Create Actions: | ||
| − | + | # Create actions (Pool, Member, Health Monitor) is disregarded until the Vip is created. | |
| − | + | # Upon Vip creation an ADC service is selected (based on the needed networks of the Pool and Vip). If ADC service does not exists, a new ADC service is created. | |
| − | + | # An ADC workflow identified by the Pool ID is created and the Vip including all the configuration (Pools, Members, Health Monitors) is being created on the selected ADC service. | |
| − | + | # Additional creation actions such as create Member, locate an existing workflow (based on the Pool ID), and invoke the appropriate action of the ADC workflow. | |
Update Actions: | Update Actions: | ||
| − | + | # Any update action locates an existing workflow (based on the Pool ID) and invokes the appropriate action of the ADC workflow. | |
| − | + | # Updating Pool and Vip (sub-nets and sequentially networks) {TBD} | |
| − | + | # Re-parenting (TBD} | |
| − | + | :# Member moves to another Pool which is provisioned on a different ADC Service | |
| − | + | :# Pool moves to another Vip which is provisioned on a different ADC Service. Vip is updated to point to another Pool which is provisioned on a different ADC Service. | |
Delete Actions: | Delete Actions: | ||
| − | + | # Member delete action locates an existing workflow (based on the Pool ID) and invokes the appropriate action of the ADC workflow. | |
| − | + | # Pool delete action {TBD} | |
| − | + | # Vip delete action {TBD} | |
Revision as of 11:48, 19 February 2013
/!\ Draft
Contents
Scope
This document describes Radware/Alteon driver for LBaaS. The feature scope is for the Open Stack Grizzly version.
Implementation Details
The driver is implemented according to Quantum/LBaaS/DriverAPI. The driver communicates with a management solution called Radware vDirect via a REST API.
Radware vDirect supports two elements of the LBaaS Driver implementation: 1. Managing the load balancer instances life-cycle (provisioning, reusing and decommissioning) via a mechanism called ADC service. 2. Managing the configuration life-cycle via a mechanism called ADC workflow.
Features
- Protocols: HTTPS, HTTP, TCP
- LB algorithms: ROUND_ROBIN, LEAST_CONNECTIONS, SOURCE_IP
- Session persistence: SOURCE_IP, HTTP_COOKIE, APP_COOKIE
- Health monitoring: TCP, HTTP, HTTPS
- Stats retrieval
Network Topology
- One arm - VIP and Members on the same network.
Load Balancer
- Configuration - SNAT.
- Form Factor - virtual appliance (Alteon VA).
Config Life Cycle
Create Actions:
- Create actions (Pool, Member, Health Monitor) is disregarded until the Vip is created.
- Upon Vip creation an ADC service is selected (based on the needed networks of the Pool and Vip). If ADC service does not exists, a new ADC service is created.
- An ADC workflow identified by the Pool ID is created and the Vip including all the configuration (Pools, Members, Health Monitors) is being created on the selected ADC service.
- Additional creation actions such as create Member, locate an existing workflow (based on the Pool ID), and invoke the appropriate action of the ADC workflow.
Update Actions:
- Any update action locates an existing workflow (based on the Pool ID) and invokes the appropriate action of the ADC workflow.
- Updating Pool and Vip (sub-nets and sequentially networks) {TBD}
- Re-parenting (TBD}
- Member moves to another Pool which is provisioned on a different ADC Service
- Pool moves to another Vip which is provisioned on a different ADC Service. Vip is updated to point to another Pool which is provisioned on a different ADC Service.
Delete Actions:
- Member delete action locates an existing workflow (based on the Pool ID) and invokes the appropriate action of the ADC workflow.
- Pool delete action {TBD}
- Vip delete action {TBD}
