Support non-unique network names in Servers IPs API response
Report correct server IP information when multiple networks with the same name
are used in VM. This spec proposes to group VM networks using their IDs rater
than names in Server IPs API resource.
Blueprint information
- Status:
- Not started
- Approver:
- Matt Riedemann
- Priority:
- Low
- Drafter:
- Maciej Kucia
- Direction:
- Needs approval
- Assignee:
- Maciej Kucia
- Definition:
- Pending Approval
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
| Bug #1708316: Nova send wrong information when there are several networks which have same name and VM uses more than one of them | In Progress |
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Non-unique network names in Servers IPs API response
Approved for Rocky but the spec needs to be updated to also mention fixing the 'addresses' field in the response for the GET /servers/detail and GET /servers/
Addressed by: https:/
Fix Non-unique network names in Servers IPs API response
We have about 6 weeks to feature freeze for Rocky and no code posted for this blueprint yet (that I'm aware of), so it would be in your best interest to start working on the code changes. -- mriedem 20180615
Addressed by: https:/
Update docs to reflect API changes for listing IPs
Gerrit topic: https:/
We're past feature freeze for Rocky, so this must be deferred. Please re-propose the spec for Stein if you'd like to work on it next cycle. -- melwitt 20180727
