Use TLS proxy for Glance API's internal TLS
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Thu, 8 Dec 2016 10:02:57 +0000 (12:02 +0200)
committerJuan Antonio Osorio Robles <jaosorior@redhat.com>
Mon, 23 Jan 2017 14:54:43 +0000 (14:54 +0000)
commit5318a833227ee09eccee520542f7235311675403
tree2f8a5ccacd5917b46bd3045dadb7897d68057033
parent499bb5911e0d0fb3c2c2d569ff05e018f1bbe173
Use TLS proxy for Glance API's internal TLS

This uses the tls_proxy resource added in the previous commit [1] in
front of the Glance API server when internal TLS is enabled. Right
now values are passed quite manually, but a subsequent commit will use
t-h-t to pass the appropriate hieradata, and then we'll be able to clean
it up from here.

Note that the proxy is only deployed when internal TLS is enabled.

[1] I82243fd3acfe4f23aab373116b78e1daf9d08467

bp tls-via-certmonger
Depends-On: Id5dfb38852cf2420f4195a3c1cb98d5c47bbd45e

Change-Id: Id35a846d43ecae8903a0d58306d9803d5ea00bee
manifests/haproxy.pp
manifests/profile/base/glance/api.pp