Heat templates for deploying OpenStack
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
tripleo-heat-templates/docker/services
Zuul 97664cb9fe Merge "FFU: Fix glance tasks" 5 years ago
..
ceph-ansible Remove hiera interpolation from ceph-ansible parameters 5 years ago
database FFU: Add mongodb fast forward upgrade tasks 5 years ago
logging Fix docker neutron logging 5 years ago
octavia Run Octavia configuration on the overcloud 5 years ago
pacemaker Merge "FFU: Upgrades: fix pacemaker checks" 5 years ago
skydive Remove hardcoded skydive container image 5 years ago
README.rst FFU: Upgrades: fix pacemaker checks 5 years ago
aodh-api.yaml Merge "Enable aodh-api health check" 5 years ago
aodh-evaluator.yaml Always evaluate step first in conditional 5 years ago
aodh-listener.yaml Always evaluate step first in conditional 5 years ago
aodh-notifier.yaml Always evaluate step first in conditional 5 years ago
barbican-api.yaml Add step to run secret_store_sync before instance startup 5 years ago
ceilometer-agent-central.yaml Merge "Enable ceilometer-agent-central health check" 5 years ago
ceilometer-agent-compute.yaml Add fast_forward_upgrade_tasks for ceilometer services 5 years ago
ceilometer-agent-ipmi.yaml Add fast_forward_upgrade_tasks for ceilometer services 5 years ago
ceilometer-agent-notification.yaml Add fast_forward_upgrade_tasks for ceilometer services 5 years ago
cinder-api.yaml FFU: Fix Cinder services action order 5 years ago
cinder-backup.yaml Allows for configuration of the Ceph cluster name 5 years ago
cinder-common.yaml Unify the Cinder HA and non-HA docker configurations 5 years ago
cinder-scheduler.yaml FFU: Fix Cinder services action order 5 years ago
cinder-volume.yaml FFU: Fix Cinder services action order 5 years ago
collectd.yaml FFU: Introduce collectd fast-forward-upgrade tasks 5 years ago
congress.yaml Always evaluate step first in conditional 5 years ago
containers-common.yaml Fix a typo in docker_puppet_apply.sh 5 years ago
ec2-api.yaml Always evaluate step first in conditional 5 years ago
etcd.yaml Merge "Enable etcd health check" 5 years ago
fluentd.yaml FFU: Introduce fluentd fast-forward-upgrade tasks 5 years ago
glance-api.yaml FFU: Fix glance tasks 5 years ago
gnocchi-api.yaml Merge "Fix gnocchi-upgrade Table <..> already exists errors" 5 years ago
gnocchi-metricd.yaml Merge "Enable gnocchi-metricd health check" 5 years ago
gnocchi-statsd.yaml Merge "Enable gnocchi-statsd health check" 5 years ago
haproxy.yaml Containerize keepalived 5 years ago
heat-api-cfn.yaml Adds fast_forward_upgrade_tasks for Heat services 5 years ago
heat-api.yaml Adds fast_forward_upgrade_tasks for Heat services 5 years ago
heat-engine.yaml Adds fast_forward_upgrade_tasks for Heat services 5 years ago
horizon.yaml Disable murano horizon plugin until dep is met 5 years ago
ironic-api.yaml Always evaluate step first in conditional 5 years ago
ironic-conductor.yaml Always evaluate step first in conditional 5 years ago
ironic-inspector.yaml inspector: fix perms on /var/lib/ironic 5 years ago
ironic-pxe.yaml Set tftp to only listen to the provisioning network 5 years ago
iscsid.yaml Merge "Enable iscsid health check" 5 years ago
keepalived.yaml Always evaluate step first in conditional 5 years ago
keystone.yaml FFU: Fix Keystone FFU tasks 5 years ago
logrotate-crond.yaml Change template names to queens 5 years ago
manila-api.yaml Always evaluate step first in conditional 5 years ago
manila-scheduler.yaml Always evaluate step first in conditional 5 years ago
manila-share.yaml Allows for configuration of the Ceph cluster name 5 years ago
memcached.yaml Merge "Enable memcached health check" 5 years ago
mistral-api.yaml Convert ServiceNetMap evals to hiera interpolation 5 years ago
mistral-engine.yaml Always evaluate step first in conditional 5 years ago
mistral-event-engine.yaml Enable mistral-event-engine health check 5 years ago
mistral-executor.yaml mistral-executor: mount /var/lib/mistral 5 years ago
multipathd.yaml Enable multipathd health check 5 years ago
neutron-api.yaml ffu: Introduce Neutron fast-forward upgrade tasks 5 years ago
neutron-bgpvpn-api.yaml Adding docker service for BGPVPN Service Plugin 5 years ago
neutron-dhcp.yaml ffu: Introduce Neutron fast-forward upgrade tasks 5 years ago
neutron-l2gw-api.yaml Adding docker service for the L2GW 5 years ago
neutron-l3.yaml Merge "Fixes certificate generation error for Neutron agents" 5 years ago
neutron-metadata.yaml Merge "Fixes certificate generation error for Neutron agents" 5 years ago
neutron-ovs-agent.yaml Merge "neutron: Call destroy-patch-ports before starting ovs-agent" 5 years ago
neutron-ovs-dpdk-agent.yaml Assignning a value to NeutronServiceName propertiy in neutron-ovs-dpdk-agent.yaml 5 years ago
neutron-plugin-ml2-cisco-vts.yaml Fixes certificate generation error for Neutron agents 5 years ago
neutron-plugin-ml2.yaml Fixes certificate generation error for Neutron agents 5 years ago
neutron-sriov-agent.yaml Fixes certificate generation error for Neutron agents 5 years ago
nova-api.yaml FFU: Fix nova fast forward steps 5 years ago
nova-compute.yaml FFU: Fix nova fast forward steps 5 years ago
nova-conductor.yaml FFU: Fix nova fast forward steps 5 years ago
nova-consoleauth.yaml FFU: Fix nova fast forward steps 5 years ago
nova-ironic.yaml FFU: Fix nova fast forward steps 5 years ago
nova-libvirt.yaml Add support for libvirt VNC TLS 5 years ago
nova-metadata.yaml FFU: Fix nova fast forward steps 5 years ago
nova-migration-target.yaml Enable nova-migration-target health check 5 years ago
nova-placement.yaml Enable nova placement health check 5 years ago
nova-scheduler.yaml FFU: Fix nova fast forward steps 5 years ago
nova-vnc-proxy.yaml Merge "FFU: Fix nova fast forward steps" 5 years ago
novajoin.yaml Add novajoin service 5 years ago
octavia-api.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
octavia-health-manager.yaml Always evaluate step first in conditional 5 years ago
octavia-housekeeping.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
octavia-worker.yaml Ensure packages for octavia only when EnablePackageInstall is True 5 years ago
opendaylight-api.yaml Minor update steps for ODL 5 years ago
ovn-controller.yaml Always evaluate step first in conditional 5 years ago
ovn-dbs.yaml Always evaluate step first in conditional 5 years ago
ovn-metadata.yaml Fixes certificate generation error for Neutron agents 5 years ago
panko-api.yaml Enable panko API health check 5 years ago
qdrouterd.yaml Change template names to queens 5 years ago
rabbitmq.yaml Always evaluate step first in conditional 5 years ago
rsyslog-sidecar.yaml Change template names to queens 5 years ago
sahara-api.yaml Always evaluate step first in conditional 5 years ago
sahara-engine.yaml Always evaluate step first in conditional 5 years ago
sensu-client.yaml Always evaluate step first in conditional 5 years ago
sshd.yaml Change template names to queens 5 years ago
swift-proxy.yaml FFU: Fix swift FFU tasks 5 years ago
swift-ringbuilder.yaml Change template names to queens 5 years ago
swift-storage.yaml FFU: Fix swift FFU tasks 5 years ago
tacker.yaml Merge "Enable Tacker health check" 5 years ago
tempest.yaml Added t-h-t for tempest container 5 years ago
tripleo-ui.yaml docker: add support for TripleO UI 5 years ago
zaqar.yaml Always evaluate step first in conditional 5 years ago

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.

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>_.