Bug 1272144

Description of problem:
In the basic deployment guide, we only give the most basic command-line parameters. However, most of the time you need to enter additional parameters to end up with a successful deployment. We cover a lot of CLI parameters in the Advanced Deployment section, but not in the Basic Deployment.

Steps to Reproduce:
1. Follow Basic Deployment guide
2. Deploy with "openstack overcloud deploy --templates"
3. (Probably fail to deploy)

Actual results:
In the majority of cases, additional parameters will be required, so the deployment will fail, or hang, or will complete but be non-functional.

Expected results:
The Basic Deployment guide should indicate which additional CLI parameters will be required under certain scenarios.

Additional info:
If the deployment is on virt, then the paramater '--libvirt-type qemu' is required.

If the deployment is on bare metal, then '--neutron-public-interface <NIC>' should be used to indicate which NIC will be used for the external bridge (br-ex).

The '--ntp-server <HOST>' should be used to make sure the computes and controllers don't skew too far apart (which can create token timeout errors), this is absolutely required for HA deployments

The '--neutron-network-type' and '--neutron-tunnel-types' parameters are valid for a Basic deployment, but we don't document them.

Examples should be given for different quantities of hosts:

1 controller + 1 compute: openstack deploy blahblahblah

HA: 3 controllers + 2 compute + 3 ceph: openstack deploy blahblahblah