In case you missed the awesome news last Friday, George Kobar who works over in the vCloud Air team shared a really cool solution in which he demonstrates how to efficiently setup Nested ESXi running in vCloud Air which includes support for inner-vm guest communication without requiring Promiscuous Mode. Nested ESXi has been possible on vCloud Air for quite some time, in fact when I was first granted access I had to try it out myself and had written about it here. The great thing about vCloud Air is that it runs directly on vSphere which means you will get all the added benefits of the underlying vSphere platform including things like VHV (Virtual Hardware Assisted-Virtualization) to ensure that your Nested ESXi VM and its virutal workloads runs as efficiently and as performant as possible. If you are new to vCloud Air, I would recommend checking out this tutorial here which goes into some of the basic operations.

Given the updated news regarding Nested ESXi on vCloud Air, I am sure many of you are excited to try out this new trick for those requiring inner-vm guest communication. I figured most of you will be interested in trying out vSphere 6.0, especially with some of the new capabilities like SMP-FT and VSAN 6.0 which runs perfectly fine in a Nested ESXi environment for demo and learning purposes as shown here and here. I thought I would put together a quick guide on how to setup both Nested ESXi 6.0 as well as the new VCSA 6.0 (which does have a few minor caveats but can definitely run in vCloud Director and vCloud Air environment).





Disclaimer: The usual caveat ... Nested ESXi is not officially supported by VMware

ESXi 6.0

There is no version of vCloud Director for the Enterprise that supports vSphere 6.0 which means there is no direct support for the latest virtual hardware release which is 11 or support for ESXi 6.x guestOS type. This is also true for vCloud Air which is currently running on vSphere 5.5 and because of this reason, you will need to upload a VM that has been configured with ESXi 5.x as the guestOS type when looking to install ESXi 6.0. Once vCloud Air supports vSphere 6.0, then you can upload a VM that has been created with the ESXi 6.x guestOS type.

The easiest way to create Nested ESXi VM in a vCloud Director or vCloud Air environment is to simply import a VM that has already been configured with ESXi guestOS type (this does not need to be an already installed image). To help expedite the deployment of Nested ESXi in vCloud Air, I have built several Nested ESXi OVF Templates that that you can use. You will also need to upload an ESXi 6.0 ISO or whichever version of ESXi you plan on running since both ESX(i) 4.x and 5.x is possible.

VCSA 6.0

One of the challenges I came across when testing the new VCSA 6.0 in a vCloud Director based environment which also affect vCloud Air is that they do not support a few capabilities within the OVF specification, namely Deployment Options. Due to this limitation and few others, we can not directly import the VCSA 6.0 OVA into vCloud Director. Luckily, there is a workaround which I had looked into a few months before the GA of vSphere 6.0 and below are the steps to import a VCSA 6.0 OVA into a vCloud Director environment. If you are looking to run VCSA 5.5, then you can directly import the OVA without going through these steps.

Step 1 - Download and extract the contents of the VCSA 6.0 ISO (Build 2656757 was used)

Step 2 - Convert VCSA 6.0 OVA located in vcsa/vmware-vcsa into an OVF by either using ovftool, tar or a tool like 7zip.

ovftool --sourceType=OVA vmware-vcsa vmware-vcsa.ovf

Next, you will need to make several modifications to the OVF file. I do have to warn you, there are a few tweaks and I highly recommend that you use the OVF templates that I have already created for you. Make sure to also delete the .mf (manifest file) since you are making changes to the OVF else the OVF validation will throw an error because the files have been modified.

To save you some time, pain and troubles, I have pre-created the following 3 OVFs (based on vSphere 6.0 GA release of VCSA 6.0) which contains all the modifications mentioned in Step 3 which you can download and then jump to Step 4:

Step 3 - The first is to locate the "References" tag located at the top of the OVF file and remove the line containing the RPM reference. At the end it should look something like the following:

<References> <ovf:File ovf:href="VMware-vCenter-Server-Appliance-6.0.0.5100-2656759_OVF10-file1.json" ovf:id="layout.json_id" ovf:size="5756"/> <File ovf:href="VMware-vCenter-Server-Appliance-6.0.0.5100-2656759_OVF10-disk1.vmdk" ovf:id="VMware-vCenter-Server-Appliance-6.0.0.5100-2656759-system.vmdk_id" ovf:size="524469248"/> <File ovf:href="VMware-vCenter-Server-Appliance-6.0.0.5100-2656759_OVF10-disk2.vmdk" ovf:id="VMware-vCenter-Server-Appliance-6.0.0.5100-2656759-cloud-components.vmdk_id" ovf:size="1369250304"/> <File ovf:href="VMware-vCenter-Server-Appliance-6.0.0.5100-2656759_OVF10-disk3.vmdk" ovf:id="VMware-vCenter-Server-Appliance-6.0.0.5100-2656759-swap.vmdk_id" ovf:size="74240"/> </References> 1 2 3 4 5 6 < References > < ovf : File ovf : href = "VMware-vCenter-Server-Appliance-6.0.0.5100-2656759_OVF10-file1.json" ovf : id = "layout.json_id" ovf : size = "5756" / > < File ovf : href = "VMware-vCenter-Server-Appliance-6.0.0.5100-2656759_OVF10-disk1.vmdk" ovf : id = "VMware-vCenter-Server-Appliance-6.0.0.5100-2656759-system.vmdk_id" ovf : size = "524469248" / > < File ovf : href = "VMware-vCenter-Server-Appliance-6.0.0.5100-2656759_OVF10-disk2.vmdk" ovf : id = "VMware-vCenter-Server-Appliance-6.0.0.5100-2656759-cloud-components.vmdk_id" ovf : size = "1369250304" / > < File ovf : href = "VMware-vCenter-Server-Appliance-6.0.0.5100-2656759_OVF10-disk3.vmdk" ovf : id = "VMware-vCenter-Server-Appliance-6.0.0.5100-2656759-swap.vmdk_id" ovf : size = "74240" / > < / References >

In addition, depending on the method you took to convert the OVA to an OVF, you may also need to rename the json and disk file names located in this section to match the extracted contents.

The second is to delete the following section from the OVF that starts with MigrationUpgradeRequisitesSection:

<vmw:MigrationUpgradeRequisitesSection ovf:required="false"> <Info>Files necessary for migration-based upgrade.</Info> <vmw:Requisite ovf:fileRef="VMware-vCenter-Server-Appliance-6.0.0.5110-2656759-upgrade-requirements.rpm_id" vmw:purpose="requirements"/> </vmw:MigrationUpgradeRequisitesSection> 1 2 3 4 < vmw : MigrationUpgradeRequisitesSection ovf : required = "false" > < Info > Files necessary for migration - based upgrade . < / Info > < vmw : Requisite ovf : fileRef = "VMware-vCenter-Server-Appliance-6.0.0.5110-2656759-upgrade-requirements.rpm_id" vmw : purpose = "requirements" / > < / vmw : MigrationUpgradeRequisitesSection >

The fourth step is to specify the deployment option type that you wish to use. VCSA 6.0 supports the following: embedded, infrastructure (PSC) and management (VC). You will need to locate the following line containing guestinfo.cis.deployment.node.type and set the value property to one of the three options.

<Property ovf:key="guestinfo.cis.deployment.node.type" ovf:type="string" ovf:userConfigurable="false" ovf:value="infrastructure"> 1 < Property ovf : key = "guestinfo.cis.deployment.node.type" ovf : type = "string" ovf : userConfigurable = "false" ovf : value = "infrastructure" >

The fifth and final step is to specify the deployment size that you wish use for your VCSA, here are nine different supported options:

Embedded tiny small medium large

vCenter Server Management Node (only) management-tiny management-small management-medium management-large

(only) Platform Services Controller Node (only) infrastructure

(only)

Since both vCloud Director and vCloud Air does not support the Deployment Option OVF capability, you will need to specify the deployment you wish to use. Locate the DeploymentOptionSection and the first entry where it shows "default=true", you will need to change the id to match one of the entries show above. For example, if you wanted an Embedded VCSA deployment using the tiny size, you would specify "tiny" in the id field.

<DeploymentOptionSection> <Info>List of profiles</Info> <Configuration ovf:default="true" ovf:id="tiny"> 1 2 3 < DeploymentOptionSection > < Info > List of profiles < / Info > < Configuration ovf : default = "true" ovf : id = "tiny" >

Once you have selected the type of deployment, you will also need to remove ALL entries referencing the other deployment types else it will always deploy an Embedded deployment.

Note: I would like to give a big shout-out to Doug Baer who works over in the VMware HOL team, he actually discovered the initial issue with the Deployment Options and found the workaround by removing the other disk references. If not, you would end up needing ~2TB of storage as VCD tries to aggregate all nine deployments into one! When I had initially worked out the steps to deploy a VCSA 6.0, I had only used the Embedded deployment option.

Step 4 - Lastly, you will need to change the "capacity" property as seen below from 1303 to 1306 due to a known vCloud Air issue documented in KB2094271

<Disk ovf:capacity="1303" ovf:capacityAllocationUnits="byte * 2^20" ovf:diskId="cloudcomponents" ovf:fileRef="VMware-vCenter-Server-Appliance-6.0.0.5110-2656759-cloud-components.vmdk_id" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" ovf:populatedSize="1365573632"/> 1 < Disk ovf : capacity = "1303" ovf : capacityAllocationUnits = "byte * 2^20" ovf : diskId = "cloudcomponents" ovf : fileRef = "VMware-vCenter-Server-Appliance-6.0.0.5110-2656759-cloud-components.vmdk_id" ovf : format = "http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" ovf : populatedSize = "1365573632" / >

Step 5 - You are now ready to upload your VCSA 6.0 OVF to your vCloud Director or vCloud Air environment.

Note: For vCloud Air, you will need to use the "Manage in vCloud Director" link to upload the OVF as the vCloud Air interface does not support direct OVA/OVF uploads.

Step 6 - When you are are ready to deploy your VCSA, one very important step that you will need to do is to edit a few of the OVF properties in the VM before powering it on. If you power on the VCSA before performing this step, the system will need to be deleted and re-deployed as the OVF properties are only read in on the initial first boot which is required for proper configuration.

Make sure to disable guest customization, to do so right click on the VM and select Guest OS Customization and uncheck " Enable guest customization "

and uncheck " " To edit the OVF properties, right click on the VM and select Properties. Click on Guest Properties and you will ONLY be editing the following three sections

Networking Configuration



System Configuration



SSO Configuration



For an Embedded Configuration, you will need to edit the following (below is an example of the data input):

Host Network IP Address: 192.168.110.100

Host Network IP Address Family: ipv4

Host Network DNS Servers: 192.168.110.10

Host Network Default Gateway: 192.168.110.1

Host Network Mode: static

Host Network Identity: vc-01a.corp.local

Host Network Prefix: 24

Tools-based Time Synchronization Enable: check OR NTP Servers

Root Password: VMware1!

SSH Enabled: check/uncheck

Directory Domain Name: vghetto.local

New Identity Domain: check

Directory Password: VMware1!

Site Name: virtuallyGhetto



For a vCenter Server Management Node only , you will need to edit the following (below is an example of the data input):

Host Network IP Address: 192.168.110.100

Host Network IP Address Family: ipv4

Host Network DNS Servers: 192.168.110.10

Host Network Default Gateway: 192.168.110.1

Host Network Mode: static

Host Network Identity: vc-01a.corp.local

Host Network Prefix: 24

Tools-based Time Synchronization Enable: check OR NTP Servers

Platform Services Controller: psc-01a.corp.local

Root Password: VMware1!

SSH Enabled: check/uncheck

Directory Domain Name: vghetto.local

New Identity Domain: uncheck

Directory Password: VMware1!

Site Name: virtuallyGhetto



For a Platform Services Controller Node only, you will need to edit the following (below is an example of the data input):

Host Network IP Address: 192.168.110.110

Host Network IP Address Family: ipv4

Host Network DNS Servers: 192.168.110.10

Host Network Default Gateway: 192.168.110.1

Host Network Mode: static

Host Network Identity: psc-01a.corp.local

Host Network Prefix: 24

Tools-based Time Synchronization Enable: check OR NTP Servers

Root Password: VMware1!

SSH Enabled: check/uncheck

Directory Domain Name: vghetto.local

New Identity Domain: check

Directory Password: VMware1!

Site Name: virtuallyGhetto



If everything was deployed successfully, you should now have a VCSA 6.0 instance running in either your vCloud Director or vCloud Air environment.