Correlate address scope with network
Bug #1547380 reported by
Hong Hui Xiao
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
Wishlist
|
Hong Hui Xiao | ||
Bug Description
With address scope being enabled, networks now are in one ipv4 address scope and one ipv6 address scope. But now, it is difficult to find out the address scopes that the network is in. User have to check in this way: network-
This bug is to add a read-only, derived attribute to the network as part of the address scopes extension that will show related address scopes when viewing a network through the API.
| Changed in neutron: | |
| assignee: | nobody → Hong Hui Xiao (xiaohhui) |
| tags: | added: l3-ipam |
| tags: |
added: l3-ipam-dhcp removed: l3-ipam |
| tags: | added: address-scopes |
| Changed in neutron: | |
| milestone: | none → mitaka-3 |
| status: | New → Confirmed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to neutron (master) | #1 |
| Changed in neutron: | |
| status: | Confirmed → In Progress |
| Changed in neutron: | |
| importance: | Undecided → Wishlist |
| Changed in neutron: | |
| assignee: | Hong Hui Xiao (xiaohhui) → Carl Baldwin (carl-baldwin) |
| Changed in neutron: | |
| assignee: | Carl Baldwin (carl-baldwin) → Hong Hui Xiao (xiaohhui) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to neutron (master) | #2 |
| Changed in neutron: | |
| status: | In Progress → Fix Released |
Revision history for this message
| Thierry Carrez (ttx) wrote Fix included in openstack/neutron 8.0.0.0b3 | #3 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/