[RFE] Change VIF list endpoint to output additional information
Bug #1657170 reported by
Vladyslav Drok
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ironic |
Confirmed
|
Wishlist
|
Vasyl Saienko | ||
Bug Description
Right now, vif_list only returns a list of ids, while it would be useful to also return object type (port or portgroup), uuid, mode and properties in case of portgroup, address etc. This could be used to fully abstract the attach/detach process, as one would be able to determine the object VIF is attached to without looping through all port-like objects and looking at extra/internal_
Also it would be good to have ability to specify interface_type when request vif_attach to allow user strictly define to what object port or portgroup attach vif to.
| tags: | added: rfe |
| description: | updated |
| Changed in ironic: | |
| assignee: | nobody → Vasyl Saienko (vsaienko) |
| Changed in ironic: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| Changed in ironic: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Sam Betts (sambetts) wrote | #1 |
Revision history for this message
| Vasyl Saienko (vsaienko) wrote | #3 |
| Changed in ironic: | |
| status: | In Progress → Confirmed |
To post a comment you must log in.
Vifs aren't attached to ports or portgroups they are attached to nodes, attaching them to ports/portgroups is a implementation detail of the neutron/flat network interfaces.
In some scenarios/on certain hardware a node doesn't have any ports/portgroups until the network interface attaches the networks as they are created on the BMC based on the VIFs attached, or in certain implementations a physical port in Ironic might have multiple vifs attached to it to represent a virtual interface card.
Both these situations break the assumption that one VIF attaches to one Port or Portgroup, so assuming this in the API will reduce the flexibility designed into the API to begin with.