Ocata - Placement API template does not support serving queries via HTTPS

[Ryan Beisner]

Ocata placement api is not terminating an ssl endpoint in the stable/17.02 charm. A fix already exists at master. Proposing a cherry pick stable update.

See related:
https://review.openstack.org/#/c/431569
https://review.openstack.org/#/c/437685

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/17.02
Review: https://review.openstack.org/466073

[James Hebden (ec0)]

Ideally we would like this to be sensitive to whether or not TLS is enabled and enable on the nova-placement-api vhost if enabled. Looking at the attached reviews, it seems that these changes move the placement-api vhost to being rendered via a context instead of a template, which will make it easier to do this, but I couldn't see specific code which enabled TLS on those vhost.

I have attached a quick and dirty modification that enables TLS, and I'd expect this to represent the end state of the nova placement API vhost config when the charm was configured with TLS enabled, but should not be configured this way if TLS certificates are not enabled.

[David Ames (thedac)]

Just to make this clear, the fix for this bug is in master and is in the process of being backported:

https://review.openstack.org/#/c/431569
https://review.openstack.org/#/c/437685