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

Building My First AI Chatbot with Azure OpenAI Services

In April 2024, I embarked on an exciting journey into the world of artificial intelligence (AI), starting with learning Python. Coming from an infrastructure-focused background, diving into AI development felt like a monumental shift. Without prior coding experience, I realized that building AI tools or training models from scratch would require a long-term commitment. However, I was determined to take small, practical steps toward understanding this fascinating field. Exploring cloud AI services from providers like AWS and Azure led me to Azure OpenAI services. This platform showed me how AI could be leveraged to create applications— like chatbots—without deep coding expertise. I was especially intrigued by concepts such as indexing, semantic search, and retrieval-augmented generation (RAG). These tools enabled me to build my first business use case: a Microsoft Teams chatbot designed to resolve internal queries and reduce dependency on subject matter experts (SMEs). This blog is a s...

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}