Deployment Template¶
Substitution Strings¶
You can use mustache format {{foo.bar}} in order to access various properties dynamically during the deployment. Currently the following properties can be used in the deployment template:
- tenant.displayname
- tenant.name
- collection.displayname
- collection.name
- deployment.displayname
- deployment.environment
- deployment.name
- deployment.shortid
- resourcegroup.rgname.computenodename
- resourcegroup.rgname.computenodename.hostname
- resourcegroup.rgname.computenodename.displayname
- resourcegroup.rgname.computenodename.dnsdomain
- resourcegroup.rgname.computenodename.fqdn
- resourcegroup.rgname.computenodename.logicalcpus
- resourcegroup.rgname.computenodename.memorymb
- resourcegroup.rgname.computenodename.name
- resourcegroup.rgname.computenodename.operatingsystem
Deployment Order¶
ResourceGroups Deployment are running in parallel.
After all ResourceGroups have been created, the PostConfig items will be executed. They are referencing to a list of AWX jobs.
Tags¶
Following tags are set by default: TODO
Specifications¶
To be created based on schema files.
Postconfig¶
In the "postconfig" key of the deployment template, additional config tasks can be described, which run after all resources / resourcegroups have been staged.
The same config tasks as for the computenode can be used. Please refer to Config Task section. Additionally limit key might need to be specified.