stable/train
stable/wallaby
master
stable/zed
6.0.0
wallaby-em
5.0.0
victoria-eol
victoria-em
2.6.0
ussuri-eol
4.2.0
ussuri-em
1.5.6
4.1.0
2.5.0
3.3.0
1.5.5
2.4.0
3.2.0
4.0.0
1.5.4
3.1.2
train-em
0.8.0
2.3.0
3.1.1
3.1.0
1.5.3
0.7.0
2.2.0
0.6.0
1.5.2
3.0.0
2.1.0
2.0.0
1.5.1
1.8.0
1.7.0
1.6.0
1.5.0
1.4.0
1.3.0
0.5.0
1.2.0
1.1.0
0.4.1
1.0.0
0.4.0
0.3.0
0.2.0
0.1.0
${ noResults }
1 Commits (71eb4ba2fa730166391c76321ee2b1aa8e73fa21)
| Author | SHA1 | Message | Date |
|---|---|---|---|
Emilien Macchi
|
24e9c33ad4 |
Add module "container_puppet_config"
This module will do two things:
Summary:
(1) Generate container configs for each container that has a puppet
deployment step; and but the files in
/var/lib/tripleo-config/container-puppet-config
(2) Update the container-startup-config of the containers which have a new
hash; so they get restarted later.
Details:
(1) Here are the steps that happen to generate the puppet container
configs:
- Create /var/lib/tripleo-config/container-puppet-config/step_X
- Generate a JSON file, that is the same format as the
well-known container-startup-configs (which are understood by
Paunch and tripleo-container-manage Ansible role). It mimics
the logic from THT/common/container-puppet.py to add the
required configuration so the container can run.
(2) If a container has a new configuration, the TRIPLEO_CONFIG_HASH
will be updated in the startup config of the container, so later
Paunch or tripleo-container-manage Ansible role can restart the
container so the config is applied.
Note: it processing a bunch of files and data, so it's better for it to
be a module and not an action plugin so the file generation can be
delegated on to the remote nodes instead of the undercloud.
In the future, we'll try to generate container configuration directly in
config-download so the data will be ready to be copied.
Change-Id: I6b656df725803db0c1cdaac6f534766398a15810
|
3 years ago |