Expose virtual device tags in REST API
You can create a server with tagged block devices and virtual interfaces but there isn't a way to get the tags out of the REST API. This blueprint proposes that we add a microversion to expose the tags in the REST API when listing volume attachments and attached ports.
This was discussed at the Ocata summit:
https:/
It has come up a few times since, notably in removing the device_name parameter from the volume attach API:
https:/
And the detach/attach root volume spec: https:/
Blueprint information
- Status:
- Complete
- Approver:
- Sylvain Bauza
- Priority:
- Low
- Drafter:
- Matt Riedemann
- Direction:
- Approved
- Assignee:
- Matt Riedemann
- Definition:
- Approved
- Series goal:
- Accepted for stein
- Implementation:
-
Implemented
- Milestone target:
-
stein-3
- Started by
- Matt Riedemann
- Completed by
- Matt Riedemann
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Expose BDM tags in REST API < Spec
This is going to be deferred to queens. We'll work on https:/
Gerrit topic: https:/
Approved for Stein. -- mriedem 20181220
Addressed by: https:/
WIP: Add microversion to expose virtual device tags
Addressed by: https:/
Fix deps for api-samples tox env
Addressed by: https:/
Make VolumeAttachmen
Addressed by: https:/
Add unit tests for missing VirtualInterface in 2.70 os-interface
Work Items
Dependency tree
* Blueprints in grey have been implemented.
