ComputeContainer addNetworkInterface request

Description

This API adds a virtual Network Interface Card (NIC) to a compute container. It supports the VMware hypervisor and Microsoft Windows and Red Hat Linux guest operating systems.

The following constraints apply to this API:

You can add NICs only to virtual machines (VMs). You cannot add NICs to physical servers.
You can add NICs only to VMs that have been commissioned via BMC Cloud Lifecycle Management.
The VM must be running. You cannot add a NIC to a VM that is stopped.
The API does not validate the input parameters that it receives. You must ensure that all input parameters are correct.
The networkLabel input parameter must match the label that was used to create the NIC in BMC Network Automation.

After the NIC is added to the VM, the NIC is configured. If the NIC properties cannot be configured, the request fails and you must remove the NIC that was added to the VM.

API stability classification

Unstable

Availability

Available in BMC Cloud Lifecycle Management version 2.1 SP2 and later

API overview

HTTP request message

Query string parameters

This API does not use query string parameters.

Request message headers

This API uses only common request headers listed in HTTP-request-and-response-headers.

Request message body

This API uses the following objects in the request message body JSON:
The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

The following table lists the input parameters to include in the operationParams object:
The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

HTTP response message

Response message headers

This API uses only common response headers listed in HTTP-request-and-response-headers.

Response message body

The response message body contains a Task object.
Unknown macro: confluence_report-block.