add explicit check for 'external-network' in L3
Bug #1042030 reported by
dan wendlandt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Salvatore Orlando |
Bug Description
The existing L3 API has a notion of an 'external network', which is a network from which floating-ips can be allocated, as well as to which routers can be "uplinked' for access to the outside world.
However, we do not yet have a way to explicitly mark a network as external.
I have a branch that does this internally, but it will overlap/conflict with rkukura's provider networks branch, so I'm waiting until that branch is merged to complete this bug.
Changed in quantum: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → dan wendlandt (danwent) |
milestone: | none → folsom-rc1 |
summary: |
- add explicit notion of 'external-network' for L3 + add explicit check for 'external-network' in L3 |
Changed in quantum: | |
assignee: | Salvatore Orlando (salvatore-orlando) → dan wendlandt (danwent) |
Changed in quantum: | |
assignee: | dan wendlandt (danwent) → Salvatore Orlando (salvatore-orlando) |
Changed in quantum: | |
assignee: | Salvatore Orlando (salvatore-orlando) → dan wendlandt (danwent) |
Changed in quantum: | |
assignee: | dan wendlandt (danwent) → Salvatore Orlando (salvatore-orlando) |
status: | Fix Committed → In Progress |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
milestone: | folsom-rc1 → 2012.2 |
To post a comment you must log in.
Note: these external networks should also not allow DHCP to be enabled.