posted

0 Comments

The following is article was written by Andrew Chin of the vSphere Integrated Containers engineering team at VMware

This post will discuss basic network configuration options when deploying a Virtual Container Host (VCH) to use vSphere Integrated Containers Engine (VICE).  For general information on vSphere Integrated Containers and Virtual Container Hosts, please see the vSphere Integrated Containers Engine documentation,

VCH Static IP Address

A common use case is to give the VCH a static IP address. There are several networks used by the VCH detailed in Networks Used by vSphere Integrated Containers Engine. For this we will use a basic configuration where all of the networks share the same port group.

The VCH is created with the following command to specify the static IP for the Public Network. Since the other VCH networks don’t have a port group specified, they default to the same value as the Public Network.

The end of the vic-machine create output shows that the static IP provided as the –public-network-ip was resolved to a hostname and tells us how to issue Docker commands to the VCH:

We can verify that Docker commands to the specified IP work as expected:

Setting DNS servers

By default when you set a static IP for the VCH, the VCH uses Google Public DNS servers 8.8.8.8 and 8.8.4.4. To specify your own DNS servers, use the –dns-server option when creating the VCH.

By using the VCH debugging mode we can see that the provided DNS servers are set:

Setting Routing Destinations

In VICE version 0.8, vic-machine required a gateway to be specified when a static IP is configured for client and management networks even though this option isn’t needed if the specified network is L2 adjacent.

A fix will be included in our next release, but until then users can apply the workaround shown below. The workaround is to enter a fake routing destination for the client/management network. Note that the fake destination must have a gateway on the same subnet as the client/management network static IP that is set.

Using the VCH debugging mode we can see the routing table:

 

For more information, see the official vSphere Integrated Containers product page. For more information on how VIC works, see the documentation.

Download vSphere Integrated Containers Today!

About the Author

Charu Chaubal

Charu Chaubal is the Director of Technical Marketing for the Cloud Platform Business Unit at VMware, and runs the team that works on the vSphere product line. He has been at the company since 2006, and has been responsible for customer education and sales enablement for a wide range of datacenter technologies, such as hypervisor security, virtual networking, hyperconverged storage, and Big Data. Previously, he worked at Sun Microsystems, where he had over 7 years experience with architecting distributed resource management and HPC infrastructure software solutions.