fc222b3963
There is some ongoing work to deploy the overcloud steps from Ansible. This patch aims to add the support for testing the feature. Parameters additions: - tripleo_config_download_log`: Sets the TripleO config-download log file path. - ansible_steps_log`: Sets the TripleO Ansible steps log file path. - config_download_args`: Sets the arguments to load config-download environment in THT. - step_tripleo_config_download`: false/true - whether to enable config-download. - deploy_steps_ansible`: false/true - whether to deploy the overcloud with config-download Ansible steps. Log collection (temporary, until we have a Mistral workflow): - /home/*/inventory - /home/*/tripleo-config-download/ Steps added to the overcloud-deploy: - Create config-downlad environment - Download TripleO configuration with tripleo-config-download - Add subnodes to known hosts - Deploy overcloud steps with Ansible Other: templates/config-download.yaml.j2 file is added to configure OS::TripleO::DeployedServer::ControlPlanePort resource_registry and also HostnameMap + DeployedServerPortMap. Some of the tasks implemented here are temporary and will be removed once we have a clean Mistral workflow. Co-Authored-By: James Slagle <jslagle@redhat.com> Co-Authored-By: Emilien Macchi <emilien@redhat.com> Implements: blueprint ansible-config-download Change-Id: I3a66e4a22d7bf15eddc5be1604af2b5737d49055 |
||
---|---|---|
.. | ||
cloud-names.yaml.j2 | ||
config-download.yaml.j2 | ||
deployed_server_prepare.sh.j2 | ||
neutronl3ha.yaml.j2 | ||
overcloud_roles.yaml.j2 | ||
overcloud_services.yaml.j2 | ||
overcloud-deploy-post.sh.j2 | ||
overcloud-deploy.sh.j2 | ||
overcloud-status.sh.j2 | ||
README.md | ||
resource-registry-nic-configs.yaml.j2 |
Overcloud ansible templates
overcloud_services jinja template
The overcloud_services jinja template is taking a dictionary from the default
variable overcloud_services
.
The dictionary is composed by: nodes and services.
Those value would build the heat environment file required for deploying
the overcloud with the specify services.
Example: if you want to deploy only keystone, just override the overcloud_services variable in a yaml file with:
overcloud_services:
- name: 'ControllerServices:'
services:
- OS::TripleO::Services::Kernel
- OS::TripleO::Services::Keystone
- OS::TripleO::Services::RabbitMQ
- OS::TripleO::Services::MySQL
- OS::TripleO::Services::HAproxy
- OS::TripleO::Services::Keepalived
- OS::TripleO::Services::Ntp
- OS::TripleO::Services::Timezone
- OS::TripleO::Services::TripleoPackages
Or with keystone and nova:
overcloud_services:
- name: 'ControllerServices:'
services:
- OS::TripleO::Services::Kernel
- OS::TripleO::Services::Keystone
- OS::TripleO::Services::RabbitMQ
- OS::TripleO::Services::MySQL
- OS::TripleO::Services::HAproxy
- OS::TripleO::Services::Keepalived
- OS::TripleO::Services::Ntp
- OS::TripleO::Services::Timezone
- OS::TripleO::Services::TripleoPackages
- name: 'ComputeServices:'
services:
- OS::TripleO::Services::NovaCompute