Difference between revisions of "Neutron/LBaaS/CommonAgentDriver"
(Created page with "== LBaaS Common Agent-based Driver == === Rationale === Haproxy-on-host reference implementation which is using agents is quite specific: * with haproxy it is easier to deploy...") |
|||
| Line 1: | Line 1: | ||
== LBaaS Common Agent-based Driver == | == LBaaS Common Agent-based Driver == | ||
| − | === Rationale === | + | ==== Rationale ==== |
Haproxy-on-host reference implementation which is using agents is quite specific: | Haproxy-on-host reference implementation which is using agents is quite specific: | ||
| − | * with haproxy it is easier to deploy the whole loadbalancer config from scratch every time | + | * with haproxy it is easier to deploy the whole loadbalancer config from scratch every time then to create/update/delete separate components |
| − | + | * namespace driver needs virtual interface driver on init, other drivers may have their own specific parameters | |
| − | * namespace driver needs virtual interface driver on init, | ||
| − | |||
So it is useful to unify reference agent implementation to: | So it is useful to unify reference agent implementation to: | ||
| − | + | * make it suite any driver which wants to use async mechanism | |
| − | + | * have single lbaas agent type and hense single agent scheduling mechanism | |
| − | + | ||
| − | + | What is required: | |
| − | + | # Revision of agent API | |
| + | # Revision of agent loading device driver(s) mechanism | ||
| + | |||
| + | ==== Agent API changes ==== | ||
| + | |||
| + | |||
| + | ==== Loading drivers in agent ==== | ||
Revision as of 07:45, 5 July 2013
Contents
LBaaS Common Agent-based Driver
Rationale
Haproxy-on-host reference implementation which is using agents is quite specific:
- with haproxy it is easier to deploy the whole loadbalancer config from scratch every time then to create/update/delete separate components
- namespace driver needs virtual interface driver on init, other drivers may have their own specific parameters
So it is useful to unify reference agent implementation to:
- make it suite any driver which wants to use async mechanism
- have single lbaas agent type and hense single agent scheduling mechanism
What is required:
- Revision of agent API
- Revision of agent loading device driver(s) mechanism
