Expose virtual device tags in REST API

Registered by Matt Riedemann on 2016-11-04

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://etherpad.openstack.org/p/ocata-nova-summit-api

It has come up a few times since, notably in removing the device_name parameter from the volume attach API:

https://review.openstack.org/#/c/452546/

And the detach/attach root volume spec: https://review.openstack.org/#/c/600628/

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:
milestone icon stein-3
Started by
Matt Riedemann on 2019-01-24
Completed by
Matt Riedemann on 2019-03-01

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#/q/bp/expose-virtual-device-tags-in-rest-api

Addressed by: https://review.openstack.org/393930
    Expose BDM tags in REST API < Spec

This is going to be deferred to queens. We'll work on https://blueprints.launchpad.net/nova/+spec/deprecate-os-virtual-interface in pike to set the stage. -- mriedem 20170406

Gerrit topic: https://review.openstack.org/#q,topic:bp/expose-virtual-device-tags-in-rest-api,n,z

Approved for Stein. -- mriedem 20181220

Addressed by: https://review.openstack.org/631948
    WIP: Add microversion to expose virtual device tags

Addressed by: https://review.openstack.org/633620
    Fix deps for api-samples tox env

Addressed by: https://review.openstack.org/633621
    Make VolumeAttachmentsSampleV249 test other methods

Addressed by: https://review.openstack.org/639141
    Add unit tests for missing VirtualInterface in 2.70 os-interface

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.