Skip to main content

Creating a Mutlicloud Blueprint

As we all know cloud agnostic blueprints in vRA 8.x can be deployed in different cloud platforms. Today we will see how we can make use of it deploying in different vCenter instances.

Steps we are going to follow are
1. Create Two Cloud Zones
2. Create a Project
3. Create a Cloud-Agnostic Blueprint
  • Modify the YAML Code in Your Blueprint to Control the Cloud Machine
  • Configure the Customization Specification and Network Address
  • Modify the YAML Code in Your Blueprint to Select the Cloud Network
4. Deploy your Blueprints on your cloud

Step 1: Create two cloud zones in each vCenter server with capability tag Zone1 and Zone2


Step 2: Create a Project that has both newly created cloud zones added into it



Step 3: Create a Cloud-Agnostic Blueprint

Let's create a blueprint that will deploy a simple machine and network on either vCenter 1 or vCenter 2





Step 4: Deploy your Blueprints on your cloud

Based on user input selection machine and network will be deployed in respective vCenter instance.






Comments

Popular posts from this blog

Deleting stale kubernetes clusters in vCD

Unlike the previous version the CSE 4.x is a stateless appliance and its data is stored in VMware Cloud Director Database.  The cluster creation and deletion compared with CSE 3.x version has improved. Besides, there are some scenarios where the cluster deletion is failing even when the "Force Delete" option is chosen. We can use vCD API explorer to delete it, the following are the API queries you can execute  Under definedEntity POST /1.0.0/entities/{id}/resolve DELETE /1.0.0/entities/{id}

Manage RabbitMQ using VCP LCM

I have been working in vCD for quite some time, and most of the implementation engineers or consultants faced issues during the deployment or upgrade of RabbitMQ for the vCD message queuing service. From vCD 10.2.2, we can use the built-in MQTT client instead of RabbitMQ however, for VCD multisite configuration or some 3rd party applications need RabbitMQ, such as Veeam or VMware HCX. Using the VCP LCM, we can create a new RabbitMQ environment or manage an existing environment. The reason for this blog is that none of the VMware documentation has the information that registering an existing RMQ instance is only going to work if the RMQ instance was previously deployed by the VCP LCM (or at least, if it is a similar setup based on a Bitnami RMQ VM). Other RMQ instances (e.g., running in CentOS) are not supported and cannot be imported into the VCP LCM 1.5. I hope this information will be useful for someone who is performing green field deployment or upgrading an existing setup.