To deploy a product, on the VMware Cloud Provider Lifecycle Manager host, first you must create the respective product environment.

Product Environments

VMware Cloud Provider Lifecycle Manager does not provide a database for storing of information about the deployed products and product environments. Whenever needed, you must provide the information about the product environment.

Important: You must create the product environment with a unique environment ID. If you configure a new product environment with the same environment ID as an already deployed product environment, the environment you deployed first is overwritten.

After a product deployment, VMware Cloud Provider Lifecycle Manager stores the product environment information in its memory. While the VMware Cloud Provider Lifecycle Manager docker service is running, the information about the product environment is available in the map and VMware Cloud Provider Lifecycle Manager can refer to it by using the product environment ID to access the specified values. You can trigger product API requests by referring to the available environments.

If VMware Cloud Provider Lifecycle Manager restarts, the information about the product environment is deleted from the map and you must import the product environments.

As a best practice, after deploying a product environment, keep the deployment payload saved somewhere.

Importing Product Environments

To re-populate the map with the existing environments, you trigger an import request that validates if the specified deployment is working, and imports the product environment information into the VMware Cloud Provider Lifecycle Manager map.

Supported Product Versions in VMware Cloud Provider Lifecycle Manager 1.1

VMware Cloud Provider Lifecycle Manager 1.1 supports RabbitMQ 3.8.14.

For information about the interoperability between VMware Cloud Provider Lifecycle Manager 1.1 and other VMware products, see the VMware Product Interoperability Matrix.