osc compute server interface create249
Creates a port interface and uses it to attach a port to a server.
Normal response codes: 200
Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), conflict(409), computeFault(500), NotImplemented(501)
Usage: osc compute server interface create249 [OPTIONS] <SERVER_ID>
Arguments:
<SERVER_ID>— server_id parameter for /v2.1/servers/{server_id}/os-interface/{id} API
Options:
- 
--fixed-ips <FIXED_IPS>— Fixed IP addresses. If you request a specific fixed IP address without anet_id, the request returns aBad Request (400)response code.Parameter is an array, may be provided multiple times.
 - 
--net-id <NET_ID>— The ID of the network for which you want to create a port interface. Thenet_idandport_idparameters are mutually exclusive. If you do not specify thenet_idparameter, the OpenStack Networking API v2.0 uses the network information cache that is associated with the instance - 
--port-id <PORT_ID>— The ID of the port for which you want to create an interface. Thenet_idandport_idparameters are mutually exclusive. If you do not specify theport_idparameter, the OpenStack Networking API v2.0 allocates a port and creates an interface for it on the network - 
--tag <TAG>— 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.New in version 2.49