Setup for VMware

This tutorial will walk you through steps to get your PMO cloud running on your existing or new VMware vSphere environment.

PMO connects with your VMware vSphere environment using a Virtual Gateway Appliance that acts as a gateway between the PMO management plane and your VMware vSphere environment. This appliance is designed to discover your existings vSphere clusters, VM workloads and VM templates from your vSphere environment and import metadata about them into PMO. Using this discovery mechanism, PMO can incorporate your clusters as hypervisors (or hosts), your current running virtual machines as VM instances, and your existing templates as images in PMO without you having to move / alter / modify your existing workloads. This capability makes it easy for you to integrate PMO seamlessly into your existing vSphere enviroment without having to create a new environment from scratch.

Layering PMO on top of vSphere this way allows you to leverage all of PMO capabilities such as multi-tenancy, leases and quotas, automated rule based workload placement, easy REST APIs and CLI based automation for your existing vSphere environment.

Step 1 - Prerequisites

Before you get started, you need to follow the prerequisites for connecting PMO with your VMware vSphere Environment first.

Step 2 - Download and Deploy PMO Virtual Gateway Appliance

The PMO virtual gateway appliance for connecting with VMware vSphere can be downloaded by clicking “Manage VMware Gateway” button on the “Hosts” tab as part of the “Infrastructure” menu. The appliance is packeged in OVH format.

Deploy with OVF Tool

Once downloaded, you can import the appliance into your target vCenter environment either through the vCenter UI, or via a command-line deployment solution—like ovftool. The appliance comes configured with OVF properties that must be set while deploying the appliance in order for it to report back to your PMO management plane for authorization. These properties include:

  1. host_ip - this is the hostname or IP of your vCenter
  2. host_username - the username to use to connect to your vCenter
  3. host_password - the user password to access vCenter

Optional parameters:

  1. proxy_ip - name or IP of the proxy host to use for outbound connections (if there is one)
  2. proxy_port - port to be used on the proxy host

If you are using ovftool for command-line deployments, this represents an example of the syntax you can use to import the appliance:

./ovftool --datastore= --network= --prop:host_ip= --prop:host_username= --prop:host_password= --powerOn "vi://:@//host/"

For more details on using ovftools please refer to the <a href=”https://www.vmware.com/support/developer/ovf/ovf410/ovftool-410_userguide.pdf” rel=”noopener” target=”_blank”>OVF Tool User Guide here</a>

Deploy with vCenter Client UI

If deploying through the vCenter client, you should be presented with this screen to allow you to set these properties, as appropriate:

vcenter_client_UI

Step 3 - Authorize Appliance

Once the appliance is deployed and powers on, it should show up in your PMO UI for authorization. vmware_setup_2 The appliance will connect to your vCenter and report back the clusters and datastores it finds so that you can choose the appropriate ones to be part of your PMO cloud during authorization.

vmware_setup_3
vmware_setup_3_1
vmware_setup_4 vmware_setup_5

After the clusters and datastores are selected and the appliance is authorized, it will take some time to discover all existing workloads, templates and utilization statistics. Once this is done, your PMO cloud on VMware vSphere is all set!

Step 4 - Populate Glance Image Catalog with VMware vSphere Images

Following support article describes easy way to Populate your Glance Image Catalog with VMware vSphere Images.