Placement API is not enabled on Ocata

[James Hebden]

Using 17.02 charms on a TLS-enabled nova-cloud-controller unit, the placement-api vhost was not enabled, so the API was not available to haproxy.

The result of this not being enabled is that attempts to launch and schedule instances returns an 'Unexpected EOF Error' when connecting to the API via HTTPS. The causes the cloud to not be able to launch new instances.

This appears to be addressed upstream -
https://review.openstack.org/#/c/431569
https://review.openstack.org/#/c/437685

One other observation, was that even when the vhost was manually enabled (a2ensite nova-placement-api) - the port in the vhost did not match what haproxy was trying to access. Haproxy attempts to contact the backend on 8768 (service port 8778 - 10) however the vhost template was rendered with the apache service listening on 8778. Manually correcting this allows for the placement of instances.