8febc6e6f4
This uses a puppet-tripleo profile to configure and start docker in step1 of the deployment, which is before we attempt to deploy any containers (see docker/services/README.rst#docker-steps) This enables existing environments on upgrade to configure things correctly, without using the docker/firstboot/setup_docker_host.sh - the firstboot approach may still be needed for atomic, but for environments where we can run puppet on the host this integrates more cleanly with our existing architecture I think. Depends-On: Id8add1e8a0ecaedb7d8a7dc9ba3747c1ac3b8eea Change-Id: If4ffe21579bcb2770f4e5a96be7960b52927a27b |
||
---|---|---|
.. | ||
extraconfig | ||
manifests | ||
services | ||
all-nodes-config.yaml | ||
blockstorage-role.yaml | ||
cephstorage-role.yaml | ||
compute-role.yaml | ||
config.role.j2.yaml | ||
controller-role.yaml | ||
deploy-artifacts.sh | ||
deploy-artifacts.yaml | ||
major_upgrade_steps.j2.yaml | ||
objectstorage-role.yaml | ||
post-upgrade.j2.yaml | ||
post.j2.yaml | ||
puppet-steps.j2 | ||
role.role.j2.yaml | ||
upgrade_config.yaml |