Hello,

with yum info audit I can confirm that the package audit is installed.
with rpm -ql audit I can see a list of files, including /usr/share/doc/audit-2.3.7/*
But those files are missing
ls: cannot access /usr/share/doc/audit-2.3.7: No such file or directory

CentOS 6.7
Can you help with that?
Thanks.

Add documentation comments to all of the VmOrTemplate operations methods

When using the box built with osx-vm-templates, there is always some setting to tune in upper Vagrantfile.

Can we built those common settings into box with vagrantfile_template

There is a good [reference here](https://github.com/blueimp/boot2docker/blob/b33c71d07f2cfdc94e6f9150793bbb47a78f6b70/packer.jso

Story
As a VIC developer I want an easy way to determine how a package functions and how it should be used.
As a VIC developer I want to easily see the call logic of code that I'm changing or reviewing

Details
We currently have a significant lack of good package documentation, at least in part because review inline doc is hard without generated output available. This documentation is

Find a code coverage/review tool to run on every change and get it set up and running. Ideally, it would run all tests and report on the coverage as well as run RuboCop and potentially even more tools to ensure the code is only increasing in quality and never decreasing.

mech should report the winrm configuration

For instance:

$ vagrant winrm-config
Host default
  HostName 127.0.0.1
  User vagrant
  Password vagrant
  Port 2201
  RDPHostName 127.0.0.1
  RDPPort 2200
  RDPUser vagrant
  RDPPassword vagrant

These are the kernel options required that are missing from the latest vagrant box kernel:

• CONFIG_BRIDGE_NETFILTER
• CONFIG_NETFILTER_XT_MATCH_IPVS
• CONFIG_IP_NF_TARGET_REDIRECT
• CONFIG_EXT3_FS_XATTR
• CONFIG_VXLAN
• CONFIG_NF_NAT_TFTP
• CONFIG_NF_CONNTRACK_TFTP
• CONFIG_AUFS_FS
• `

Our wp-cli container's home page says 1.2.1 is the latest yet the tags show 1.5.1. This is not good for us if someone only looks at the main page and not the tags page.

Either we need to move to a fully-automated generation of these Docker main pages **or probably better since we can implement sooner we should remove the _"Supported tags and resp

It becomes very complicated start to use and contribute to this project, because it lacks documentation, apparently referring to unit testing, as if it were an appropriate way to start, but they are not.

Maybe for beginners like me it is complicated, but the idea is that everyone can contribute, or at least try.

Per Slack comment from @YanzhaoLi:

Could you help modify the vic doc: https://vmware.github.io/vic-product/assets/files/html/1.5/vic_vsphere_admin/vch_cert_options.html#auto-server ?
As customer says, we should point out that the server-crt.pem is self-signed, so that using the Server certificate for docker --tlscacert= which is the parameter referring to the CA certificate . I think we should

Error:
TASK [download : prep_kubeadm_images | Copy kubeadm binary from download dir to system path] ***
Thursday 02 January 2020 22:01:04 +0530 (0:00:00.778) 0:09:40.886 ******
fatal: [k8s-kubespray-master-0 -> 10.12.43.220]: FAILED! => {"changed": false, "cmd": "sshpass", "msg": "[Errno 2] No such file or directory: b'sshpass': b'sshpass'", "rc": 2}

Details:
Template Using : Ubuntu

Currently, only static IPs are possible, so definitely need to add in the dhcp option, which should probably be default.

/kind feature

Kubernetes has a providerless build tag which excludes all the in-tree cloud providers and their volume plugins. Even though the vSphere cloud provider works today with --cloud-provider=external set on all components, we should also validate that a pro