To enable tasks for VMware Cloud Provider Program products, VMware Cloud Provider Lifecycle Manager provides REST APIs and a VMware Cloud Provider Program command-line interface (CLI) to communicate with the REST APIs.

To deploy and manage a VMware Cloud Provider Program product, VMware Cloud Provider Lifecycle Manager requires a definition of the REST API or CLI request and the product binaries.

VMware Cloud Provider Lifecycle Manager needs access to the repository containing the OVA files, upgrade packages, etc.

Workload Operation

Triggering a VMware Cloud Provider Lifecycle Manager request runs a predefined list with actions.

The VMware Cloud Provider Lifecycle Manager appliance processes asynchronous operations received through the request. The tasks associated with these operations are unique to the appliance and are identified by the task IDs.

Entity Structure

VMware Cloud Provider Lifecycle Manager deploys products as part of an environment. You must define the product and the deployment infrastructure for the product environment.

The definition of the deployment infrastructure includes information about vCenter Server and respective credentials, target cluster, datastores and networks, and other.

The products follow a generic definition pattern that defines basic common product fields and requires the definition of product-specific details as properties. The REST APIs and the CLI commands are generic and follow the same structure for each product. You can provide the product specific information in the request properties. This allows VMware Cloud Provider Lifecycle Manager to expose an API that is common for all supported products.

VMware Cloud Provider Lifecycle Manager manages the vCenter Server, NSX-T Manager, and vRealize Operations Manager infrastructure components as data center components. VMware Cloud Provider Lifecycle Manager cannot deploy and manage data center components. VMware Cloud Provider Lifecycle Manager stores the information about the data center components to deploy new products to previously registered vCenter Server.