VMware: enable VNC access without user having to enter password

When the vnc_password was not configured in the 'vmware' section
the user was unable to access the VNC console. The user would be
requested to enter a password but all attempts would fail.

The 'vnc_password' was added as a workaround to the problem above.

The fix ensures that the VMware driver behaves like all of the other
virt drivers when it comes to the VNC access, that is, the user will
not have to enter a password.

The password support will be deprecated and removed in the next
version.

Fixes bug: 1215352

Change-Id: I728861b8965ee3d3b8444a0440ddd0a8e5bb9021
Require oslo.config 1.2.0 final

Now that 1.2.0 has been released, require it rather than one of the beta
release tarballs.

Closes-Bug: #1182861
Change-Id: I75ffc4a572d14488d19491a38742d6920951c171
Add V3 API samples for security-groups

Partially implements blueprint v3-api-unittests

Change-Id: I6df70127a88881320052613f4c107e2287f375c1
Remove _get_compute_info from filter_scheduler.py

After patch I6de33ada6dc377e20f8df07da92244f2c150b9fe and
Ie6f104368140b69a60e124ea96ef6bf7715fe34e, in filter_scheduler.py,
_get_compute_info has no use and no one is calling it, so we
can remove it directly.

Fix bug 1228475

Change-Id: Ia85068e402b6f0b2a9ed2a809d1c1dc63e0f3041
Merge "VMware: enable VNC access without user having to enter password"
Merge "Remove _get_compute_info from filter_scheduler.py"
Merge "Add V3 API samples for security-groups"
Merge "Require oslo.config 1.2.0 final"