tripleo-heat-templates/deployment/glance
Alan Bishop 00c17b368f Add ability to deploy glance at DCN/Edge sites
This patch adds two new tripleo services that together support
deploying the glance-api service at edge sites. The service uses the
same glance database in the control plane, but allows other edge
services (e.g. cinder and nova) to access a glance endpoint that is
local to the edge site.

A new GlanceApiEdge service is a minor variant of the GlanceApi
service. The most significant change is it doesn't use the control
plane VIP, but instead configures cinder and nova services to access
the glance-api endpoint running on that edge node (not the VIP).

A companion HAproxyEdge service supports scaling out DCN sites with
larger (>3) number of nodes. Instead of deploying GlanceApiEdge on
every node, the HAproxyEdge service configures a local haproxy to
forward glance-api requests to the edge nodes running GlanceApiEdge.

The HAproxyEdge is extensible. While this patch is only concerned
with proxying glance-api, it can be extended to support additional
proxy requirements as needs arise.

blueprint: split-controlplane-glance-cache
Change-Id: Id6c416b8c7b3b6314d935e3eeb8a3f114492cecd
Depends-On: Ic8d652a5209219c96f795a8c18ceb457c6d9382a
(cherry picked from commit 30ca49bf61)
2020-01-05 19:13:14 -08:00
..
glance-api-container-puppet.yaml Make sure glance_api_tls_proxy logs are persisted on the host 2019-11-29 07:41:35 +01:00
glance-api-edge-container-puppet.yaml Add ability to deploy glance at DCN/Edge sites 2020-01-05 19:13:14 -08:00
glance-api-logging-file-container.yaml Make sure glance_api_tls_proxy logs are persisted on the host 2019-11-29 07:41:35 +01:00
glance-api-logging-stdout-puppet.yaml Flatten Glance service configuration 2018-12-14 08:23:32 +01:00