Cloud Administrator Guide claims that users should start multiple L3 agents to serve multiple external networks
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| openstack-manuals |
High
|
Darren Chan |
Bug Description
Quoting http://
"Because you can associate each L3 agent with, at most, one external network, you must invoke multiple L3 agents to define multiple floating IP pools."
This is wrong since https:/
Tom Fifield (fifieldt) wrote : | #1 |
Changed in openstack-manuals: | |
milestone: | none → juno |
status: | New → Confirmed |
importance: | Undecided → High |
tags: | added: neutron |
Changed in openstack-manuals: | |
assignee: | nobody → Darren Chan (dazzachan) |
Darren Chan (dazzachan) wrote : | #2 |
I'll look at this since I was trying to address this issue in https:/
Fix proposed to branch: master
Review: https:/
Changed in openstack-manuals: | |
status: | Confirmed → In Progress |
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 3488166f6308bc4
Author: darrenchan <email address hidden>
Date: Mon Oct 20 13:25:51 2014 +1100
Edited multiple floating IP pools in Cloud Administrator Guide
1. Removed steps to configure multiple L3 agents for multiple external networks
2. Added configuration of a L3 agent to handle multiple external networks.
Change-Id: I7ff2f01d40a84a
backport: icehouse
Closes-Bug: #1380585
Changed in openstack-manuals: | |
status: | In Progress → Fix Released |
This issue was fixed in the openstack/
Thanks Ihar!