Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/virt-device-role-tagging.
This will provide a mechanism for the user to tag a device they have assigned to their guest with a specific role. The tag will be matched to the hardware address of the device and this mapping exposed to the guest OS via metadata service/cloud-init.
Specification URL (additional information):
Driving use case was addressed in Newton, cloned to address technical debt follow-ups in Ocata.
Dropping https://blueprints.launchpad.net/nova/+spec/virt-device-role-tagging from the URL for now as because we are re-using the same blueprint the bot is going to continue to get the status wrong.
Where can I find the Ocata era code reviews?
The gerrit topic is virt-device-tagged-attach-detach  (dunno why I put detach there, but what's done is done).
Quick status update: work is progressing upstream. Cautiously optimistic that we can merge this for Ocata, even though spec has been classified as 'slow progress/at risk'  by the PTL (Matt). It's not clear to me Matt is aware of the presence of a Tempest test , and there has been some reviewer attention o n the patches, including from Matt himself.
Moving to Queens as it seems likely at least some of these cleanup patches will still be outstanding.
Setting to POST as all patches are landed:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.