To deploy RabbitMQ, you configure a REST API request and provide the parameters for the RabbitMQ environment.
VMware Cloud Provider Lifecycle Manager 1.4 supports RabbitMQ 3.8.6 and 3.8.14.
During the deployment of RabbitMQ, you can specify additional properties.
Property | Value Type | Mandatory | Description |
---|---|---|---|
diskMode | VC disk mode | no | The vCenter disk mode for the created virtual disk. Values can be:
|
IbFqdn | FQDN | yes | The FQDN for the RabbitMQ load balancer. |
Iblp | IP address | yes | The IP address for the RabbitMQ load balancer. |
IbName | Hostname | no | The hostname for the RabbitMQ load balancer. |
portAmqpSsl | Port number | no | The AMQP SSL service port. The default port number is 5671. |
portRmqMgmt | Port number | no | The port for the RabbitMQ management service. The default port number is 15671. |
users | List with credentials | no | List with user accounts to be created in RabbitMQ. |
users[].username | String | yes | User names |
users[].password | Password string | yes | User passwords |
Prerequisites
- You must meet all requirements before deploying RabbitMQ. For information, see Before you deploy RabbitMQ.
- In the rmq/version-number/ova directory on the VMware Cloud Provider Lifecycle Manager host, save the RabbitMQ OVA file.
Procedure
- ♦ In your Web browser start Postman and configure the following HTTPS request.
- On the Headers tab, add the JSON session ID.
Setting Value JSESSIONID vcp_lcm_session_id - To deploy RabbitMQ, configure the following HTTPS request.
Setting Value HTTPS request method POST URL https://vcp_lcm_ip_address:port-number/api/api_versionlcm/environment?action=DEPLOY Body { "environmentName": "{{rmq_env_id}}", "products": [ { "productType": "RMQ", "productId": "{{rmq_product_id}}", "version": "{{version_number}}", "adminPassword": "{{password}}", "properties": { "lbName": "{{rmq_lb_name}}", "lbFqdn": "{{rmq_lb_name}}.{{domainName}}", "lbIp": "{{rmq_lb_ip}}", "portAmqpSsl": "{{rmq_port_amqp_ssl}}", "portRmqMgmt": "{{rmq_port_mgmt}}", "users": [ { "username": " user_name ", "password": "{{password}}" }, { "username": " user_name ", "password": "{{password}}" } ] }, "nodes": [ { "hostName": "{{rmq_01_name}}.{{domainName}}", "vmName": "{{rmq_01_name}}", "rootPassword": "{{password}}", "cpuNum": "cpu-number", "ramMemory": "ram-value", "nics": [ { "ipAddress": "{{rmq_01_ip}}", "networkName": "mgmt-nw-portgroup" } ] }, { "hostName": "{{rmq_02_name}}.{{domainName}}", "vmName": "{{rmq_02_name}}", "rootPassword": "{{password}}", "cpuNum": "cpu-number", "ramMemory": "ram-value", "nics": [ { "ipAddress": "{{rmq_02_ip}}", "networkName": "mgmt-nw-portgroup" } ] } ] } ] }
- On the Headers tab, add the JSON session ID.
Results
If the request is successful, you see an OK (200) status and "taskId":id-number. To check the status of the deployment, see Retrieve the status of a VMware Cloud Provider Lifecycle Manager task.