In this document we describe how to enable ingress connectivity to the nested VMs running on top of VMware ESXi™/ vCenter in Ravello, also referred to as 2nd level VMs. Since Ravelo DHCP does not support nested virtual machines we will use static IP configuration.. For more information on using DHCP, and the additional configuration needed, see this post from Ohad, detailing the steps.
The Ravello DHCP servers do not give out IPs to the nested virtual machines, so we need to configure them with static IPs and create a virtual IP so they can be accessed from the Internet or remotely from outside of the Ravello Application Environment.
The steps included here:
Add an additional NIC to an ESXi node
The IP address 10.20.30.3 can be used for the first nested guest VM or it can remain a placeholder.
The optional DNS Server can be any IP. Ravello will create the DNS server as defined. You may also substitute your own DNS server running within the same Application Environment. his DNS server can then be assigned statically in your nested ESXi VMs.
Common ports to enable are:
22 for SSH
3389 for RDP
443 for HTTPS
80 for HTTP
To configure 1:1 network address translation, select “IP” as the protocol in the services. This forwards all traffic from the public IP to the private IP and can be useful when running a nested virtual router or networking virtualization software such as VMware NSX.
To use port forwarding without consuming a public IP for a service, configure “Port forwarding” on the virtual interface:
When the virtual machine has been started, the port mapping shows in the summary of the virtual machine. In my case, port 22 on the virtual machine is reachable through 18.104.22.168:10001.
It is also possible to provision more than one routed subnet on the same physical ESXi interface. This prevents you from having to create a new vSwitch and interface when you wish to configure virtual machines to use a separate subnet.
As shown below, I’ve created an additional virtual IP in a separate subnet with a separate router:
When we look at the network topology, a separate router is created and traffic can be routed between the virtual machines in different subnets.
Do not assign an IP address or VMkernel IP Stack to the new vSwitch.
You can find the external IP/hostname on the summary tab of the ESXi node. There is a drop down list for the available NICs with IP information for each additional IP you defined.