InlineVifAttachmentContext1

JSON Example

{
    "app_id": "string",
    "bms_interface_config": {
        "app_intf_name": "string",
        "default_gateway": "string",
        "migrate_intf": "string",
        "routing_table": [
            "string"
        ]
    },
    "parent_vif_id": "string",
    "traffic_tag": 0,
    "transport_node_uuid": "string",
    "vif_type": "string"
}

string

app_id

Optional

An application ID used to identify / look up a child VIF behind a parent VIF. Only effective when vif_type is CHILD.

AttachedInterface

bms_interface_config

Optional

The Attached interface is only effective for the port on Bare metal server.

string

parent_vif_id

Optional

VIF ID of the parent VIF if vif_type is CHILD

integer As int32 As int32

traffic_tag

Optional

Current we use VLAN id as the traffic tag. Only effective when vif_type is CHILD. Each logical port inside a container must have a unique traffic tag. If the traffic_tag is not unique, no error is generated, but traffic will not be delivered to any port with a non-unique tag.

string

transport_node_uuid

Optional

Only effective when vif_type is INDEPENDENT. Each logical port inside a bare metal server or container must have a transport node UUID. We use transport node ID as transport node UUID.

string

vif_type

Required

Type of the VIF attached to logical port

Possible values are : PARENT, CHILD, INDEPENDENT,

Used By

VifAttachmentContext