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 9e27288203
Merge "Add support for ceph-nfs manila backend"
5 years ago
..
ceph-ansible Merge "Add support for ceph-nfs manila backend" 5 years ago
database Merge "Remove unused env var during mysql bootstrap" 5 years ago
logging Remove httpd log dir for glance-api 5 years ago
octavia Run Octavia configuration on the overcloud 5 years ago
pacemaker Add support for ceph-nfs manila backend 5 years ago
skydive Remove hardcoded skydive container image 5 years ago
README.rst Drop step_config as top level docker requirement 5 years ago
aodh-api.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
aodh-evaluator.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
aodh-listener.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
aodh-notifier.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
barbican-api.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
ceilometer-agent-central.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
ceilometer-agent-compute.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
ceilometer-agent-ipmi.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
ceilometer-agent-notification.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
cinder-api.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
cinder-backup.yaml Run cinder-backup in a privileged container 5 years ago
cinder-scheduler.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
cinder-volume.yaml Merge "Cinder containers: volume and env customizations" 5 years ago
collectd.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
congress.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
containers-common.yaml Use docker_config_scripts for puppet apply 5 years ago
ec2-api.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
etcd.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
fluentd.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
glance-api.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
gnocchi-api.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
gnocchi-metricd.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
gnocchi-statsd.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
haproxy.yaml Containerize keepalived 5 years ago
heat-api-cfn.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
heat-api.yaml Merge "Convert tags to when statements for Q major upgrade workflow" 5 years ago
heat-engine.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
horizon.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
ironic-api.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
ironic-conductor.yaml Convert tags to when statements for Q major upgrade workflow 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 "Convert tags to when statements for Q major upgrade workflow" 5 years ago
keepalived.yaml Containerize keepalived 5 years ago
keystone.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
logrotate-crond.yaml Change template names to queens 5 years ago
manila-api.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
manila-scheduler.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
manila-share.yaml Align Manila Share docker templates 5 years ago
memcached.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
mistral-api.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
mistral-engine.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
mistral-event-engine.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
mistral-executor.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
multipathd.yaml Merge "Convert tags to when statements for Q major upgrade workflow" 5 years ago
neutron-api.yaml Merge "Convert tags to when statements for Q major upgrade workflow" 5 years ago
neutron-dhcp.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
neutron-l3.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
neutron-metadata.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
neutron-ovs-agent.yaml Adding support for ovs hw offloading in containers 5 years ago
neutron-plugin-ml2.yaml Change template names to queens 5 years ago
neutron-sriov-agent.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
nova-api.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
nova-compute.yaml Merge "Convert tags to when statements for Q major upgrade workflow" 5 years ago
nova-conductor.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
nova-consoleauth.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
nova-ironic.yaml Merge "Convert tags to when statements for Q major upgrade workflow" 5 years ago
nova-libvirt.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
nova-metadata.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
nova-migration-target.yaml Change template names to queens 5 years ago
nova-placement.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
nova-scheduler.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
nova-vnc-proxy.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
octavia-api.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
octavia-health-manager.yaml Convert tags to when statements for Q major upgrade workflow 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 Upgrade ODL 5 years ago
ovn-controller.yaml ovn: Provide the option to configure OVNCMSOptions ('ovn-cms-options') as a role parameter 5 years ago
ovn-dbs.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
ovn-metadata.yaml Correct erroneous upgrade tasks. 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 Convert tags to when statements for Q major upgrade workflow 5 years ago
rsyslog-sidecar.yaml Change template names to queens 5 years ago
sahara-api.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
sahara-engine.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
sensu-client.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
sshd.yaml Change template names to queens 5 years ago
swift-proxy.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
swift-ringbuilder.yaml Change template names to queens 5 years ago
swift-storage.yaml Merge "swift_rsync: don't bind mount /run" 5 years ago
tacker.yaml Convert tags to when statements for Q major upgrade workflow 5 years ago
zaqar.yaml Convert tags to when statements for Q major upgrade workflow 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.


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