tripleo-heat-templates/docker/services
Juan Antonio Osorio Robles ffc14e3067 Refresh keystone after deployment
This is necessary for certain setups (such as enabling multiple LDAP
domains). So, instead of always adding checks every time to see if
we need to refresh or not, lets just do it always, thus simplifying
the already convoluted logic here.

Change-Id: Ie1a0b9740ed18663451a3907ec3e3575adb4e778
Closes-Bug: #1748219
Co-Authored-By: Raildo Mascena <rmascena@redhat.com>
2018-03-29 15:30:52 +00:00
..
ceph-ansible Remove hiera interpolation from ceph-ansible parameters 2018-03-16 15:41:21 +01:00
database Upgrade data on disk on mysql major upgrade - non HA 2018-03-22 21:38:44 +00:00
logging Fix docker neutron logging 2018-02-09 16:17:48 +00:00
octavia Run Octavia configuration on the overcloud 2018-01-16 13:19:09 +00:00
pacemaker HAProxy: expose stats socket in HA deployment after upgrade 2018-03-27 07:28:42 +00:00
skydive Remove hardcoded skydive container image 2017-11-27 10:21:17 +01:00
README.rst Merge "Update service readme files" 2018-03-21 19:34:01 +00:00
aodh-api.yaml FFU: Introduce Aodh fast-forward-upgrade tasks 2018-03-16 13:46:52 +01:00
aodh-evaluator.yaml FFU: Introduce Aodh fast-forward-upgrade tasks 2018-03-16 13:46:52 +01:00
aodh-listener.yaml FFU: Introduce Aodh fast-forward-upgrade tasks 2018-03-16 13:46:52 +01:00
aodh-notifier.yaml FFU: Introduce Aodh fast-forward-upgrade tasks 2018-03-16 13:46:52 +01:00
barbican-api.yaml Add step to run secret_store_sync before instance startup 2018-03-05 14:18:47 -05:00
ceilometer-agent-central.yaml Merge "Enable ceilometer-agent-central health check" 2018-03-14 03:39:10 +00:00
ceilometer-agent-compute.yaml Add fast_forward_upgrade_tasks for ceilometer services 2018-03-07 16:20:57 +01:00
ceilometer-agent-ipmi.yaml Add fast_forward_upgrade_tasks for ceilometer services 2018-03-07 16:20:57 +01:00
ceilometer-agent-notification.yaml Add fast_forward_upgrade_tasks for ceilometer services 2018-03-07 16:20:57 +01:00
cinder-api.yaml FFU: Fix Cinder services action order 2018-03-14 14:20:09 +01:00
cinder-backup.yaml Allows for configuration of the Ceph cluster name 2018-02-20 11:35:01 +01:00
cinder-common.yaml Unify the Cinder HA and non-HA docker configurations 2018-02-15 02:34:33 +00:00
cinder-scheduler.yaml FFU: Fix Cinder services action order 2018-03-14 14:20:09 +01:00
cinder-volume.yaml FFU: Fix Cinder services action order 2018-03-14 14:20:09 +01:00
collectd.yaml Add access to /var/run/openvswitch from collectd 2018-03-20 16:50:07 +01:00
congress.yaml Always evaluate step first in conditional 2018-02-09 17:12:29 +01:00
containers-common.yaml Fix a typo in docker_puppet_apply.sh 2018-02-16 18:31:31 +01:00
ec2-api.yaml Always evaluate step first in conditional 2018-02-09 17:12:29 +01:00
etcd.yaml Merge "Enable etcd health check" 2018-03-15 03:23:43 +00:00
fluentd.yaml Fix fluentd upgrade tasks during FFU. 2018-03-22 09:43:34 +01:00
glance-api.yaml FFU: Fix glance tasks 2018-03-14 17:54:35 +00:00
gnocchi-api.yaml Merge "FFU: Fix gnocchi FFU tasks" 2018-03-27 18:12:39 +00:00
gnocchi-metricd.yaml FFU: Fix gnocchi FFU tasks 2018-03-19 18:01:20 -04:00
gnocchi-statsd.yaml Merge "FFU: Fix gnocchi FFU tasks" 2018-03-27 18:12:39 +00:00
haproxy.yaml HAProxy: fix bind mount to expose stats socket 2018-03-23 20:13:27 +00:00
heat-api-cfn.yaml Adds fast_forward_upgrade_tasks for Heat services 2018-03-07 17:41:27 +01:00
heat-api.yaml Adds fast_forward_upgrade_tasks for Heat services 2018-03-07 17:41:27 +01:00
heat-engine.yaml Adds fast_forward_upgrade_tasks for Heat services 2018-03-07 17:41:27 +01:00
horizon.yaml Disable murano horizon plugin until dep is met 2018-02-27 18:10:29 +01:00
ironic-api.yaml Always evaluate step first in conditional 2018-02-09 17:12:29 +01:00
ironic-conductor.yaml Always evaluate step first in conditional 2018-02-09 17:12:29 +01:00
ironic-inspector.yaml inspector: fix perms on /var/lib/ironic 2018-01-31 12:02:40 -05:00
ironic-pxe.yaml Set tftp to only listen to the provisioning network 2018-01-03 15:50:25 +00:00
iscsid.yaml Merge "Enable iscsid health check" 2018-03-14 04:33:05 +00:00
keepalived.yaml Always evaluate step first in conditional 2018-02-09 17:12:29 +01:00
keystone.yaml Refresh keystone after deployment 2018-03-29 15:30:52 +00:00
logrotate-crond.yaml Change template names to queens 2017-11-23 10:15:32 +01:00
manila-api.yaml Always evaluate step first in conditional 2018-02-09 17:12:29 +01:00
manila-scheduler.yaml Always evaluate step first in conditional 2018-02-09 17:12:29 +01:00
manila-share.yaml Allows for configuration of the Ceph cluster name 2018-02-20 11:35:01 +01:00
memcached.yaml Merge "Enable memcached health check" 2018-03-14 04:33:03 +00:00
mistral-api.yaml Convert ServiceNetMap evals to hiera interpolation 2018-03-10 08:18:30 +00:00
mistral-engine.yaml Always evaluate step first in conditional 2018-02-09 17:12:29 +01:00
mistral-event-engine.yaml Enable mistral-event-engine health check 2018-02-26 12:24:52 +00:00
mistral-executor.yaml mistral-executor: mount /var/lib/mistral 2018-02-17 01:41:52 +00:00
multipathd.yaml Enable multipathd health check 2018-02-19 13:46:32 +00:00
neutron-api.yaml ffu: Introduce Neutron fast-forward upgrade tasks 2018-03-07 15:59:38 +01:00
neutron-bgpvpn-api.yaml Adding docker service for BGPVPN Service Plugin 2018-02-09 11:21:32 +01:00
neutron-dhcp.yaml ffu: Introduce Neutron fast-forward upgrade tasks 2018-03-07 15:59:38 +01:00
neutron-l2gw-api.yaml Adding docker service for the L2GW 2018-02-09 11:26:44 +01:00
neutron-l3.yaml Merge "Fixes certificate generation error for Neutron agents" 2018-03-10 02:06:55 +00:00
neutron-metadata.yaml Merge "Fixes certificate generation error for Neutron agents" 2018-03-10 02:06:55 +00:00
neutron-ovs-agent.yaml Mount openvswitch dir rather than socket 2018-03-21 16:04:58 -06:00
neutron-ovs-dpdk-agent.yaml Added the missing attributes for roles_data of ovs-dpdk-agent docker service 2018-03-22 11:46:40 +05:30
neutron-plugin-ml2-cisco-vts.yaml Fixes certificate generation error for Neutron agents 2018-03-08 11:05:33 -05:00
neutron-plugin-ml2.yaml Fixes certificate generation error for Neutron agents 2018-03-08 11:05:33 -05:00
neutron-sriov-agent.yaml Fixes certificate generation error for Neutron agents 2018-03-08 11:05:33 -05:00
nova-api.yaml FFU: Fix nova fast forward steps 2018-02-28 17:04:46 +01:00
nova-compute.yaml Add the service_config_settings from nova-compute base 2018-03-20 16:38:34 +01:00
nova-conductor.yaml FFU: Fix nova fast forward steps 2018-02-28 17:04:46 +01:00
nova-consoleauth.yaml FFU: Fix nova fast forward steps 2018-02-28 17:04:46 +01:00
nova-ironic.yaml FFU: Fix nova fast forward steps 2018-02-28 17:04:46 +01:00
nova-libvirt.yaml Add support for libvirt VNC TLS 2018-02-22 15:46:39 +00:00
nova-metadata.yaml Enable nova-metadata health check 2018-03-08 11:32:01 +05:30
nova-migration-target.yaml Enable nova-migration-target health check 2018-02-26 14:35:15 +00:00
nova-placement.yaml Enable nova placement health check 2018-02-26 16:26:12 +01:00
nova-scheduler.yaml FFU: Fix nova fast forward steps 2018-02-28 17:04:46 +01:00
nova-vnc-proxy.yaml Merge "FFU: Fix nova fast forward steps" 2018-03-06 13:38:25 +00:00
novajoin.yaml Add novajoin service 2018-03-14 13:55:16 +00:00
octavia-api.yaml Convert tags to when statements for Q major upgrade workflow 2018-01-08 13:57:47 +02:00
octavia-health-manager.yaml Always evaluate step first in conditional 2018-02-09 17:12:29 +01:00
octavia-housekeeping.yaml Convert tags to when statements for Q major upgrade workflow 2018-01-08 13:57:47 +02:00
octavia-worker.yaml Ensure packages for octavia only when EnablePackageInstall is True 2018-01-24 09:52:30 +00:00
opendaylight-api.yaml Fixes ODL container failing to start due to missing etc config 2018-03-16 10:15:23 -04:00
ovn-controller.yaml Always evaluate step first in conditional 2018-02-09 17:12:29 +01:00
ovn-dbs.yaml Always evaluate step first in conditional 2018-02-09 17:12:29 +01:00
ovn-metadata.yaml Fixes certificate generation error for Neutron agents 2018-03-08 11:05:33 -05:00
panko-api.yaml Enable panko API health check 2018-01-19 23:58:31 +01:00
qdrouterd.yaml Change template names to queens 2017-11-23 10:15:32 +01:00
rabbitmq.yaml Always evaluate step first in conditional 2018-02-09 17:12:29 +01:00
rsyslog-sidecar.yaml Change template names to queens 2017-11-23 10:15:32 +01:00
sahara-api.yaml Always evaluate step first in conditional 2018-02-09 17:12:29 +01:00
sahara-engine.yaml Always evaluate step first in conditional 2018-02-09 17:12:29 +01:00
sensu-client.yaml FFU: add fast forward upgrade support for sensu client 2018-03-07 15:58:59 +01:00
sshd.yaml Change template names to queens 2017-11-23 10:15:32 +01:00
swift-proxy.yaml FFU: Fix swift FFU tasks 2018-03-15 14:24:45 +00:00
swift-ringbuilder.yaml Change template names to queens 2017-11-23 10:15:32 +01:00
swift-storage.yaml FFU: Fix swift FFU tasks 2018-03-15 14:24:45 +00:00
tacker.yaml Merge "Enable Tacker health check" 2018-03-15 03:23:45 +00:00
tempest.yaml Added t-h-t for tempest container 2018-03-12 06:42:15 +00:00
tripleo-ui.yaml docker: add support for TripleO UI 2018-03-15 23:43:17 +01:00
zaqar.yaml Always evaluate step first in conditional 2018-02-09 17:12:29 +01:00

README.rst

Docker Services

TripleO docker services are currently built on top of the puppet services. To do this each of the docker services includes the output of the t-h-t puppet/service templates where appropriate.

In general global docker specific service settings should reside in these templates (templates in the docker/services directory.) The required and optional items are specified in the docker settings section below.

If you are adding a config setting that applies to both docker and baremetal that setting should (so long as we use puppet) go into the puppet/services templates themselves.

Also see the Puppet services README file for more information about how the service templates work in general.

Building Kolla Images

TripleO currently relies on Kolla docker containers. Kolla supports container customization and we are making use of this feature within TripleO to inject puppet (our configuration tool of choice) into the Kolla base images. The undercloud nova-scheduler also requires openstack-tripleo-common to provide custom filters.

To build Kolla images for TripleO adjust your kolla config1 to build your centos base image with puppet using the example below:

$ cat template-overrides.j2 {% extends parent_template %} {% set base_centos_binary_packages_append = ['puppet'] %} {% set nova_scheduler_packages_append = ['openstack-tripleo-common'] %}

kolla-build --base centos --template-override template-overrides.j2

Docker settings

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: This setting is generally inherited from the puppet/services templates and only need to be appended to on accasion if docker specific config settings are required.

  • kolla_config: Contains YAML that represents how to map config files into the kolla container. This config file is typically mapped into the container itself at the /var/lib/kolla/config_files/config.json location and drives how kolla's external config mechanisms work.

  • docker_config: Data that is passed to the docker-cmd hook to configure a container, or step of containers at each step. See the available steps below and the related docker-cmd hook documentation in the heat-agents project.

  • puppet_config: This section is a nested set of key value pairs that drive the creation of config files using puppet. Required parameters include:

    • puppet_tags: Puppet resource tag names that are used to generate config files with puppet. Only the named config resources are used to generate a config file. Any service that specifies tags will have the default tags of 'file,concat,file_line,augeas,cron' appended to the setting. Example: keystone_config
    • config_volume: The name of the volume (directory) where config files will be generated for this service. Use this as the location to bind mount into the running Kolla container for configuration.
    • config_image: The name of the docker image that will be used for generating configuration files. This is often the same container that the runtime service uses. Some services share a common set of config files which are generated in a common base container.
    • step_config: This setting controls the manifest that is used to create docker config files via puppet. The puppet tags below are used along with this manifest to generate a config directory for this container.
  • docker_puppet_tasks: This section provides data to drive the docker-puppet.py tool directly. The task is executed only once within the cluster (not on each node) and is useful for several puppet snippets we require for initialization of things like keystone endpoints, database users, etc. See docker-puppet.py for formatting.

Docker steps

Similar to baremetal docker containers are brought up in a stepwise manner. The current architecture supports bringing up baremetal services alongside of containers. For each step the baremetal puppet manifests are executed first and then any docker containers are brought up afterwards.

Steps correlate to the following:

Pre) Containers config files generated per hiera settings. 1) Load Balancer configuration baremetal a) step 1 baremetal b) step 1 containers 2) Core Services (Database/Rabbit/NTP/etc.) a) step 2 baremetal b) step 2 containers 3) Early Openstack Service setup (Ringbuilder, etc.) a) step 3 baremetal b) step 3 containers 4) General OpenStack Services a) step 4 baremetal b) step 4 containers c) Keystone containers post initialization (tenant,service,endpoint creation) 5) Service activation (Pacemaker) a) step 5 baremetal b) step 5 containers

Update steps:

All services have an associated update_tasks output that is an ansible snippet that will be run during update in an rolling update that is expected to run in a rolling update fashion (one node at a time)

For Controller (where pacemaker is running) we have the following states:
  1. Step=1: stop the cluster on the updated node;
  2. Step=2: Pull the latest image and retag the it pcmklatest
  3. Step=3: yum upgrade happens on the host.
  4. Step=4: Restart the cluster on the node
  5. Step=5: Verification: Currently we test that the pacemaker services are running.

Then the usual deploy steps are run which pull in the latest image for all containerized services and the updated configuration if any.

Note: as pacemaker is not containerized, the points 1 and 4 happen in puppet/services/pacemaker.yaml.

Fast-forward Upgrade Steps

Each service template may optionally define a fast_forward_upgrade_tasks key, which is a list of Ansible tasks to be performed during the fast-forward upgrade process. As with Upgrade steps each task is associated to a particular step provided as a variable and used along with a release variable by a basic conditional that determines when the task should run.

Steps are broken down into two categories, prep tasks executed across all hosts and bootstrap tasks executed on a single host for a given role.

The individual steps then correspond to the following tasks during the upgrade:

Prep steps:

  • Step=0: Check running services
  • Step=1: Stop the service
  • Step=2: Stop the cluster
  • Step=3: Update repos

Bootstrap steps:

  • Step=4: DB backups
  • Step=5: Pre package update commands
  • Step=6: Package updates
  • Step=7: Post package update commands
  • Step=8: DB syncs
  • Step=9: Verification

  1. See the override file which can be used to build Kolla packages that work with TripleO, and an `example build script <https://github.com/dprince/undercloud_containers/blob/master/build_kolla.sh>_.↩︎