Comment 2 for bug 1691818
Revision history for this message
| James Hebden (ec0) wrote Re: ocata placement api not terminating an ssl endpoint | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
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.