Navigate to Design > Blueprints.
Give it a name. Here I am creating a Blueprint with a routed network. The same applies to non-routed deployments
Optional: IF you are using NSX and you deploy NSX Edges through the Blueprint (Routed / NAT / Load Balancer), configure the Edge Reservation. Typically you have a cluster dedicated for Edges, but in my case – well – I don’t 🙂
Select Transport Zone and Edge and routed gateway reservation policy
If you have properties applying to the whole Blueprint (remember, a Blueprint can have multiple VMs etc.) you can add them here. If there are properties specific to the individual machine inside of the Blueprint – add it to the machine instead (which is what I will be doing).
So here I keep it as is – empty.
Drag a vSphere Machine component onto the canvas. Enter a name for the VM component, select a Reservation Policy and Machine Prefix
Here I select Linked Clone, the Template, a Snapshot and a vCenter Customization Spec. Whilst the latter is not required, unless you have a customization spec, vRA – and subsequent vCenter – will not be able to customize the VM with a custom IP / Reset SID etc.
Select the minimum and maximum spec. Here I increased the maximum to double the resource (well, apart from storage – I am skint when it comes to storage).
Now drag a Network onto the canvas. If you use an Existing Network – select an External network, if you use Routed, select the Routed Network. You won’t be able to select the wrong one (External instead of Routed etc.)
Give it a name / id and select said network
Click your Virtual Machine again. Select the Network tab and select the newly created network
This should now link your network with the virtual machine.
Click Save / Finish
Now Publish the Blueprint
Navigate to Administration > Catalog Management > Services
Create a Service – essentially a ‘folder’ to collect specific Blueprints in
Example (Icons I found via google)
Next navigate to Catalog Items
Select your newly created Blueprint
Select an icon (if you got one) and the newly created service
Navigate to Entitlements
Give it a name, set the Status to Active and select the Users and Groups you want to allow to use the Blurprints, here I allow all users and groups.
Add the newly created Service. You don’t need to entitle individual items as they are inherited from the service (unless there is a need of course).
Also add the Actions such as power off, on, reboot and so on
You should now see the Service and Item in your Catalog
You can now request the Blueprint – hit Request
Increase the resources if needed
You can now follow the request from within vRA
But also vCenter
Again, this also only applies when using Routed Networks with NSX, but you can see that it has now added another Virtual Switch in NSX
And added it to my DLR
And the VM was cloned into the Resource Pool I have specified in the Reservation
Now wait until the deployment is finished.
That is it. One additional test here for this scenario (Routed) – making sure routing actually works
And the way my routing / firewalling is setup – the VM should be able to get out to the internet
One quick check at the routing table of my upstream router