New Era of Cloud Native Services Provisioning with VMware Aria Automation

In the ever-changing landscape of cloud computing, VMware Aria Automation continues to innovate and adapt to meet the evolving needs of customers. Recently, we unveiled an exciting new framework for provisioning Cloud Native Services, starting with AWS services. This innovative plugin-based framework empowers us to respond quickly to cloud provider evolution and enable more native services on the platform while extending the properties and characteristics of existing and future services.

In this blog post, we’ll delve into a basic example illustrating the minimum requirements for provisioning a simple Google Compute Engine instance using the new framework. We’ll explore how to define an instance and attach it to a subnet, as well as how to include essential requirements such as disk size and source image.

A Basic Example of Provisioning a Google Compute Engine Instance

Let’s start by defining our first building block – the compute disk. We’ll need to specify the source image and an optional disk size, as each image comes with specific size requirements. Here’s our definition for the compute disk:

Idem_GCP_COMPUTE_DISK_1:

type: Idem.GCP.COMPUTE.DISK

properties:

account: Google Service

zone: us-east1-b

name: my-disk-2

size_gb: 20

source_image: projects/centos-cloud/global/images/centos-stream-8-v20230615

Next, we’ll define our compute instance and associate it with the previously defined disk, marking it as the boot disk. Here’s our definition for the compute instance:

Idem_GCP_COMPUTE_INSTANCE_1:

type: Idem.GCP.COMPUTE.INSTANCE

properties:

name: myinstance

zone: us-east1-b

account: Google Service

machine_type: zones/us-east1-b/machineTypes/n1-standard-1

disks:

– boot: true

device_name: ${resource.Idem_GCP_COMPUTE_DISK_1.name}

source: ${resource.Idem_GCP_COMPUTE_DISK_1.resource_id}

Finally, we’ll attach our compute instance to a subnet. For simplicity, we’ll use the default subnet in this scenario:

network_interfaces:

– name: eth0

subnetwork: /regions/us-east1/subnetworks/default

plugin operates with full paths for resources such as source images, machine types, and subnets. While some resources are global, others are project-specific, so pay close attention to ensure smooth provisioning.

In this example, we’ve provisioned a simple Google Compute Engine instance using the new plugin-based framework. We’ve defined an instance and attached it to a subnet while including essential requirements such as disk size and source image. In our next post, we’ll delve into how to use inputs, constraints, and mappings in this new framework to further customize and automate your cloud native services provisioning.

Stay tuned for more exciting updates from VMware Aria Automation as we continue to evolve and innovate to meet the ever-changing needs of our customers. Happy automation!