Provisioning to Azure from vRA -Part 2 of 2

vRA 7.2 Provisioning to Azure
vRA 7.2 Provisioning to Azure

Part 1 of this guide showed how to set up Azure, and configure an endpoint in vRA 7.2. This part will follow on from that and set up vRA Fabric Groups, Reservations, a Blueprint and finally provision to Azure.

Set up a Fabric Group

I already have a Fabric Group Configured but if you don’t have one create one ensuring your user is added as an admin then log off and back on to vRA.

Click Infastructure, then Fabric Groups, then New.

Create a Fabric Group

Create a Fabric Group

Set up Azure Resource Group & Storage Account

I have set up an Azure Resource Group, so that I can easily manage anything created from vRA, this is a simplified way of doing things in this lab environment but thought should be given to creating resource groups and storage accounts in a production environment.

Click Resource Groups, then Add, etner a name and set your location.

 

Then set up a storage account, Click Storage Accounts, Click Add, enter a name,  use your existing Resoure Group created in the previous step and se tthe locaiton. Click Create.

Note the name must be lower case only.

Now we need to create a vnet, click Networks, then Add, then enter a name, I changed the address space to a /16, then select the Resource Group and region.

 

Create a Reservation

Now to create a reservation in vRA that will use our newly created Azure constructs.

Click Infastructure, Reservations, New, and then Azure

Enter a Name, Business Group, and a Priority.

Click on the Resources Tab and enter your Subscription ID which we obtained in Part 1, Set your location and enter the Resource Group created earlier in this post.

I have not set up an LB or Security group for this post, but will look at these in futuree posts. Just use the vNet we created earlier in this post and enter its information here by clicking Network, New, and typing the Name.

 

Click OK. No need for alerts.

Creating an Azure Blueprint

Click on Design, Blueprints then Add

Enter a Name and the ID should auto-populate, you can ignore NSX and Properties settings.

Drag the Azure Machine on to the canvas

On the build information tab set your Location, and enter the image name. I used powerhsell to get the image name with the command “Get-AzureVMImage | Select * | Out-Gridview –Passthru” but if you want an example name you can use:

MicrosoftWindowsServer:WindowsServer:2016-Datacenter:2016.0.20170127

Note: I made a mistake below and was getting the error “The following component requests failed: Azure_Machine_1. VM image URN of type ‘Stock’ should comply to ‘publisher:offer:sku:version’ format.” but corrected it by using “MicrosoftWindowsServer:WindowsServer:2016-Datacenter:2016.0.20170127” which I got from following this.

 

Then enter a username and password, note the password must be 12 Characters long and the Instance type and size must be availiable in your chosen region.

On the Machine Resources Tab you can enter the resource group created previously.

On Storage Tab, enter the Storage Acount we created earlier (hoping for managed disk support in the future).

Enter the name of our vNet and the Subnet name will be default

Click the Blueprint and click Publish

Then head to Administration, Azure, click New

 

Create a new Service called Azure

Click on the new service and click Manage Catalog Items

 

Click Add then select the Blueprint

Check back to the catalog and you should be able to provision from vRA to Azure.

You can just click Create on this to request the VM in Azure.

Checking the Azure Portal you should see a VM being created.

 

If you missed Part 1 of this guide you can get it here: Part 1