Enable custom certificates for keystone communication
Nova creates a session back to keystone to verify project ids for
quota and flavor access APIs. The session that was being created was
not based on conf options, so it only worked in simple default
scenarios. This updates the session by using the newly added keystone
section to utilize keystoneauth1 to manage the session creation, which
allows for specifying custom site certificates to secure the link
between Nova and Keystone.
Change-Id: Ice4b226fdabdfb66e60b61de05ac8f3b37610661
Closes-Bug: 1704798
(cherry picked from commit 905d31dd9715505599b0a2ad123eebef37f606f5)
Reviewed: https:/ /review. openstack. org/505546 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=c0ff5b33ca4 2a417a5fa08e513 3a27397af08c3d
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit c0ff5b33ca42a41 7a5fa08e5133a27 397af08c3d
Author: jichenjc <email address hidden>
Date: Sun Jul 9 10:35:23 2017 +0800
Enable custom certificates for keystone communication
Nova creates a session back to keystone to verify project ids for
quota and flavor access APIs. The session that was being created was
not based on conf options, so it only worked in simple default
scenarios. This updates the session by using the newly added keystone
section to utilize keystoneauth1 to manage the session creation, which
allows for specifying custom site certificates to secure the link
between Nova and Keystone.
Change-Id: Ice4b226fdabdfb 66e60b61de05ac8 f3b37610661 599b0a2ad123eeb ef37f606f5)
Closes-Bug: 1704798
(cherry picked from commit 905d31dd9715505