The binding Extended Attributes for Ports

Use the Networking API v2.0 with the binding extended attributes to get information about, create, and update port objects.

The binding-prefixed extended attributes for ports are:

Table 4.1. binding Extended Attributes for Ports
Attribute Type Required CRUD[a] Default Value Validation Constraints Notes

binding:vif_type

String

N/A

R

None

N/A

Read-only. The vif type for the specified port.

binding:host_id

uuid-str

N/A

CRU

None

N/A

The ID of the host where the port is allocated. In some cases different implementations can run on different hosts.

binding:profile

list(dict) N/A CRU None N/A

A dictionary that enables the application running on the specified host to pass and receive vif port-specific information to the plug-in.

binding:capabilities

list(dict) N/A R None N/A

Read-only. A dictionary that enables the application to pass information about functions that Networking API v2.0 provides. Specify the following value: port_filter : Boolean to define whether Networking API v2.0 provides port filtering features such as security group and anti-MAC/IP spoofing.

binding:vnic_type

String

N/A

CRU

normal

(normal, direct, macvtap)

The vnic type to be bound on the neutron port. To support SR-IOV PCI passthrough networking, you can request that the neutron port be realized as normal (virtual nic), direct (pci passthrough), or macvtap (virtual interface with a tap-like software interface). The ML2 plug-in supports the vnic_type.

[a]

  • C. Use the attribute in create operations.

  • R. This attribute is returned in response to show and list operations.

  • U. You can update the value of this attribute.

  • D. You can delete the value of this attribute.

Questions? Discuss on ask.openstack.org
Found an error? Report a bug against this page


loading table of contents...