Deploy AHV based VMs via vRealize Automation

This is a follow up post to the Nutanix AHV, OpenStack & vRealize Automation released a few weeks ago. My colleague Gabe Contreras put this one together and it will show you how to configure a vRealize Automation (vRA) Openstack Endpoint, create a vRA reservation, and create a vRA blueprint for provisioning to AHV.

Screen Shot 2016-06-03 at 10.46.04

Follow the below steps to successfully deploy AHV based VMs on Nutanix via vRealize Automation.

  • Login to your vRA 7 Tenant with a user that has full Administrator and Architect permissions.  Then once logged in go to Infrastructure -> Credentials and add the Admin credentials for your Openstack Project that you created before.Screen Shot 2016-06-03 at 10.46.52
  • Create the EndPoint via clicking Infrastructure -> Endpoints -> New -> Cloud -> Openstack.  Fill out the following information:
    • Name
    • Description
    • Address using the following format, http://IP_or_FQDN:5000
    • Credentials
    • OpenStack project
      Screen Shot 2016-06-03 at 10.49.18
  • Verify the configuration works by mouse over the Endpoint and verify Data collection is successful.Screen Shot 2016-06-03 at 10.53.00
  • Enable the OpenStack Resource for your Fabric group via Infrastructure -> Fabric GroupsScreen Shot 2016-06-03 at 11.01.59
  • Create the vRA the Reservation via Infrastructure ->Reservations -> New ->Openstack.
    • On the General tab just fill out a name, I am not using any reservation Policy and putting priority of 1.
    • On the Resources tab in the drop down select the Openstack Resource you created, any machine quota if you want one, I choose for Key Pair on a per business group basis, and default Security group.
      Screen Shot 2016-06-03 at 12.22.23
    • On the Network tab we have two networks created for two separate VLAN’s. Select both and there will be no Network Profile created because AHV will be handling the IP assignments.
      Screen Shot 2016-06-03 at 12.23.41
    • We are not entering anything under Properties or Alerts for this use case. Click OK to create the Reservation.
  • Create a VirtualMachine.Network0.Name property definition for the two networks via Administration > Property Dictionary > Property definitions. Add the Network Property definition to a Property group which you will use later.
    Screen Shot 2016-06-03 at 12.28.19
  • Create the first template and in this case it will be based on CentOS Image already present in OpenStack. Go to Design > Blueprints and select New.
    • In the initial Windowjust name it CENTOS7 and an archive of 30 days, leave all other properties the defaults and select OK.
    • Via the Design Canvas, drag “OpenStack Machine” onto the canvas and input CENTOS7 as the ID. All other options on the tab can be at their default values(s)
    • Via the Build Information tab, add the following information:
      • Blueprint type
      • Provisioning workflow
      • OpenStack image
      • Key pair
      • Flavours
        Important: Select the flavours that respects the minimum requirements selected when you imported the image to OpenStack. If not, the provisioning will fail.
        Screen Shot 2016-06-03 at 12.28.46
    • Add the Property Group including the Network Property Definition created earlier. You can also use the Properties tab and add e.g. the machine state workflows so information can be sent to vRealize Orchestrator (vRO). To start post provisioning workflows you can to use Extensibility.Lifecycle.Properties.CloudProvisioning.Workflow.BuildComplete via the CloudProvisioningWorkflow.
  • Assign the newly created Blueprint to a vRA service, in this case OpenStack-Nutanix
    Screen Shot 2016-06-03 at 12.42.35
  • Request the CENTOS7 catalog item and select your options/fill out information for:
    • Instances
    • Flavour
    • Description
    • Network
    • Machine Name
      Screen Shot 2016-06-03 at 13.57.55

When provisioning is completed you’ll see the VM in the below two interfaces:

  • OpenStack
    Screen Shot 2016-06-03 at 14.56.17
  • Nutanix PRISM Element (PE)
    Screen Shot 2016-06-03 at 14.56.28

The newly created AHV based VM is now a managed object in vRA
Screen Shot 2016-06-03 at 14.56.37



6 pings

Comments have been disabled.