aboutsummaryrefslogtreecommitdiffstats
path: root/docker/services/README.rst
diff options
context:
space:
mode:
authorJenkins <jenkins@review.openstack.org>2016-11-23 10:09:21 +0000
committerGerrit Code Review <review@openstack.org>2016-11-23 10:09:21 +0000
commit48c1daac3438fa12a3144b499bcc62f4a7cf87d0 (patch)
treee121e00f7276f4603d05daad88a38736d600660c /docker/services/README.rst
parent22b01f75dd32ea910abba93ea5f62c81ae096996 (diff)
parent6e866224fd2ca22933f5138e36e512f12074e46e (diff)
Merge "Containerized Services for Composable Roles"
Diffstat (limited to 'docker/services/README.rst')
-rw-r--r--docker/services/README.rst60
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 @@
+========
+services
+========
+
+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.
+
+Steps
+-----
+
+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)
+