Use multiple Neutron L3 agent mode for HA-network solution.
In 5.1 release and before FUEL HA network solution based on one neutron-l3-agent, switchable between controllers.
This blueprint describes way for using multiple L3 agents instead single.
Blueprint information
- Status:
- Complete
- Approver:
- Vladimir Kuklin
- Priority:
- Essential
- Drafter:
- Sergey Vasilenko
- Direction:
- Approved
- Assignee:
- Sergey Vasilenko
- Definition:
- Approved
- Series goal:
- Accepted for 6.0.x
- Implementation:
-
Implemented
- Milestone target:
-
6.0
- Started by
- Sergey Vasilenko
- Completed by
- Vladimir Kuklin
Related branches
Related bugs
| Bug #1328970: [library] l3-agent active-passive failover takes 30+ seconds when a controller fails | Invalid |
| Bug #1359082: l3 and dhcp agents should be corosync clones | Fix Released |
Sprints
Whiteboard
<jpretorius 2014-05-23>
In another use-case, we'd like to see multiple L3 Agents for an entirely different reason - scaling. We'd like to dedicate L3 Agents to specific type of networks (eg: Provider Network VLANs) in order to carry traffic that's specific to that need. ie Internet-bound traffic would go through one L3 and all VLAN traffic would go through another. Each of those L3's would require HA, but HA is on the way: https:/
</jpretorius>
(aglarendil): Maybe, this blueprint is superseded by
https:/
Above 2 comments restored to keep the historic context
- angdraug 2014-08-21
Gerrit topic: https:/
Addressed by: https:/
Blueprint: fuel-multiple-
Gerrit topic: https:/
Addressed by: https:/
Multiple DHCP/L3 agents
Addressed by: https:/
Create file /etc/default/
Addressed by: https:/
make checking AMQP connection for OCF-script disableble.
Addressed by: https:/
Don't deploy nova-network on contoller.
Addressed by: https:/
Temporary revert "Rename parameter 'tag' to 'vlan_tag' in l23network module"
Addressed by: https:/
Multiple DHCP/L3 agents
Work Items
Dependency tree
* Blueprints in grey have been implemented.
