109bb65c3a
The dib-utils repository was retired when TripleO was retired. We decided to vendor the dib-run-parts script in os-refresh-config so we no longer need the separate tiny package for the dib-run-parts script. Depends-on: https://review.opendev.org/c/openstack/os-refresh-config/+/910574 Change-Id: Id35efa4b387bd0fa21c1d73a4fe59f88c197f500
Boot config for installing software-config agent
This directory has environment files which each declare a resource type Heat::InstallConfigAgent.
This can be used by server user_data when booting a pristine image to install the agent required to use software deployment resources in templates. The templates assume that you have the heat-agents repository checked out alongside the heat-templates repository; if the agent code is in a different location you will need to adjust the paths in the templates.
The environments only install the heat-config-script hook. If other hooks are required then define your own environment file which defines a resource template based on one of the templates in template/
To install the agent during boot, include the following in the template:
- boot_config:
type: Heat::InstallConfigAgent
- server:
type: OS::Nova::Server properties: user_data_format: SOFTWARE_CONFIG user_data: {get_attr: [boot_config, config]} # ...
When creating the stack, reference the desired environment, eg:
openstack stack create -e fedora_yum_env.yaml -t ../example-templates/example-config-pristine-image.yaml deploy-to-pristine
Boot config with heat-container-agent
When creating the stack to deploy containers with docker-compose, include the following in the template:
- boot_config:
type: Heat::InstallConfigAgent
- server:
type: OS::Nova::Server properties: user_data_format: SOFTWARE_CONFIG user_data: {get_attr: [boot_config, config]} # ...
and reference the desired environment, eg:
openstack stack create -e container_agent_env.yaml -t ../example-templates/example-pristine-atomic-docker-compose.yaml deploy-to-pristine