API support for tagged device attachment
This patch adds microversion 2.49, which supports tagged attachment of network interfaces and block devices. Change-Id: I8d3bbe7e9a21d2694d10ee89628deb333e6b0487 Implements: blueprint virt-device-tagged-attach-detach
This commit is contained in:
@@ -71,6 +71,7 @@ Request
|
||||
- net_id: net_id
|
||||
- fixed_ips: fixed_ips
|
||||
- ip_address: ip_address_req
|
||||
- tag: device_tag_nic_attachment
|
||||
|
||||
**Example Create Interface: JSON request**
|
||||
|
||||
@@ -84,6 +85,11 @@ Create interface with ``port_id``.
|
||||
.. literalinclude:: ../../doc/api_samples/os-attach-interfaces/attach-interfaces-create-req.json
|
||||
:language: javascript
|
||||
|
||||
**Example Create Tagged Interface (v2.49): JSON request**
|
||||
|
||||
.. literalinclude:: ../../doc/api_samples/os-attach-interfaces/v2.49/attach-interfaces-create-req.json
|
||||
:language: javascript
|
||||
|
||||
Response
|
||||
--------
|
||||
|
||||
|
||||
@@ -67,12 +67,18 @@ Request
|
||||
- volumeAttachment: volumeAttachment_post
|
||||
- volumeId: volumeId
|
||||
- device: device
|
||||
- tag: device_tag_bdm_attachment
|
||||
|
||||
**Example Attach a volume to an instance: JSON request**
|
||||
|
||||
.. literalinclude:: ../../doc/api_samples/os-volumes/attach-volume-to-server-req.json
|
||||
:language: javascript
|
||||
|
||||
**Example Attach a volume to an instance and tag it (v2.49): JSON request**
|
||||
|
||||
.. literalinclude:: ../../doc/api_samples/os-volumes/v2.49/attach-volume-to-server-req.json
|
||||
:language: javascript
|
||||
|
||||
Response
|
||||
--------
|
||||
|
||||
|
||||
@@ -1794,6 +1794,19 @@ device_tag_bdm:
|
||||
required: false
|
||||
type: string
|
||||
min_version: 2.32
|
||||
device_tag_bdm_attachment:
|
||||
description: |
|
||||
A device role tag that can be applied to a volume when attaching it to the
|
||||
VM. The guest OS of a server that has devices tagged in this manner can
|
||||
access hardware metadata about the tagged devices from the metadata API and
|
||||
on the config drive, if enabled.
|
||||
|
||||
.. note:: Tagged volume attachment is not supported for shelved-offloaded
|
||||
instances.
|
||||
in: body
|
||||
required: false
|
||||
type: string
|
||||
min_version: 2.49
|
||||
device_tag_nic:
|
||||
description: |
|
||||
A device role tag that can be applied to a network interface. The guest OS
|
||||
@@ -1807,6 +1820,17 @@ device_tag_nic:
|
||||
required: false
|
||||
type: string
|
||||
min_version: 2.32
|
||||
device_tag_nic_attachment:
|
||||
description: |
|
||||
A device role tag that can be applied to a network interface when attaching
|
||||
it to the VM. The guest OS of a server that has devices tagged in this
|
||||
manner can access hardware metadata about the tagged devices from the
|
||||
metadata API and on the config
|
||||
drive, if enabled.
|
||||
in: body
|
||||
required: false
|
||||
type: string
|
||||
min_version: 2.49
|
||||
disabled_reason_body:
|
||||
description: |
|
||||
The reason for disabling a service.
|
||||
|
||||
Reference in New Issue
Block a user