search

vmware / vic

vSphere Integrated Containers Engine is a container runtime for vSphere.
http://vmware.github.io/vic
Other
640 stars 174 forks source link

Create VIC config validation container image #6704

Open corrieb opened 7 years ago

corrieb commented 7 years ago

Summary

There are only so many things that the vic-admin console can check for. Often times, once a customer has installed a VCH, if they suspect they're having issues or want to validate the installation, it would be extremely helpful if we provided them with a container image that makes that easier.

The concept is that the container image would contain a number of useful tools, possibly some automated scripts and would ship in vic-registry. If it's based on the same Photon image as DCH, it shouldn't add much to the download size.

The container image could be used alongside a series of steps in our documentation that should make it possible for customers to diagnose common misconfigurations or issues in their setup. For example, if the bridge port group doesn't have a vLAN id and the network hardware between ESXi hosts is configured to drop packets with no vLAN id, by running the validation image on multiple hosts, the customer can quickly and easily see that there's a connectivity issue and either debug further or get in touch with GSS.

One of the real benefits of this approach is that a canned image would eliminate any question of guest configuration from the issue reporting.

The addition of scripts that make the experience even friendlier - that can run through checks such as gateway connectivity, name server, connectivity to the endpoint VM, firewall and report back in a way that's simple to understand, would be awesome.

Let's use this Epic as a way of describing what it is we think it should do.

Things to check for:

Without NSX

With NSX

Suggested minimum set of tools:

dbarkelew commented 6 years ago

A json pretty print tool would be useful to add to the list of tools.