path: root/docker/services/README.rst
diff options
authorIan Main <imain@redhat.com>2016-06-15 06:46:44 +0000
committerFlavio Percoco <flaper87@gmail.com>2016-11-22 11:42:49 +0100
commit6e866224fd2ca22933f5138e36e512f12074e46e (patch)
treef893847ee6ebb722dcad22efa97272ad761afc89 /docker/services/README.rst
parent2fc81bef2f696bd9d9486a2b35d52432d8486adc (diff)
Containerized Services for Composable Roles
This change modifies the template interface to support containers and converts the compute services to composable roles. Co-Authored-By: Dan Prince <dprince@redhat.com> Co-Authored-By: Flavio Percoco <flavio@redhat.com> Co-Authored-By: Martin André <m.andre@redhat.com> Co-Authored-By: Steve Baker <sbaker@redhat.com> Change-Id: I82fa58e19de94ec78ca242154bc6ecc592112d1b
Diffstat (limited to 'docker/services/README.rst')
1 files changed, 60 insertions, 0 deletions
diff --git a/docker/services/README.rst b/docker/services/README.rst
new file mode 100644
index 00000000..8d1f9e86
--- /dev/null
+++ b/docker/services/README.rst
@@ -0,0 +1,60 @@
+A TripleO nested stack Heat template that encapsulates generic configuration
+data to configure a specific service. This generally includes everything
+needed to configure the service excluding the local bind ports which
+are still managed in the per-node role templates directly (controller.yaml,
+compute.yaml, etc.). All other (global) service settings go into
+the puppet/service templates.
+Input Parameters
+Each service may define its own input parameters and defaults.
+Operators will use the parameter_defaults section of any Heat
+environment to set per service parameters.
+Config Settings
+Each service may define a config_settings output variable which returns
+Hiera settings to be configured.
+Each service may define an output variable which returns a puppet manifest
+snippet that will run at each of the following steps. Earlier manifests
+are re-asserted when applying latter ones.
+ * config_settings: Custom hiera settings for this service. These are
+ used to generate configs.
+ * step_config: A puppet manifest that is used to step through the deployment
+ sequence. Each sequence is given a "step" (via hiera('step') that provides
+ information for when puppet classes should activate themselves.
+ * docker_compose:
+ * container_name:
+ * volumes:
+Steps correlate to the following:
+ 1) Service configuration generation with puppet.
+ 2) Early Openstack Service setup (database init?)
+ 3) Early containerized networking services startup (OVS)
+ 4) Network configuration
+ 5) General OpenStack Services
+ 6) Service activation (Pacemaker)
+ 7) Fencing (Pacemaker)