Designing Micro Templates
Micro templates are defined as a single template.yaml file, based on the Command Central DSL template definition. Each micro template is stored in a separate folder that contains a template definition file, named "template.yaml". You can store the user-defined micro templates in a version control system to be able to test and re-use the templates. To design a micro template, you first determine whether the template will be used to create an infrastructure layer or a run-time layer. Templates that you use to install and configure Platform Manager are infrastructure micro templates. Templates that you use to install and configure products (and their hosted run-time components) are run-time micro templates. Both types of micro templates include the following template definition sections:
environments
layers
templates
provision
In addition to the listed sections, the infrastructure micro templates include a nodes section. Run-time micro templates do not have a nodes section.
Each micro template (infrastructure or runtime) should include only one product inline template that has only one product instance.
In the environments section of the micro templates, you can define the following default parameters that are used for creating the layers:
environments:
default:
nodes: ${} # REQUIRED A comma-separated list of hostnames
# on which to provision the layer: host1,host2
release: # The release version of the stack as specified
# at the time of creating the stack.
repo.product: # The product repository to use for installing products.
repo.fix: # The fix repository to use for installing fixes.
repo.asset: # The asset repository to use for installing assets.
cc.installer: # The bootstrap installer to use when bootstrapping
# Platform Manager when creating an infrastructure layer.
runtimes.skip.start: <rcId1>,<rcId2> # A list of IDs of the run-time components, which
# Command Central will not start when applying the
# template. Use a comma (,) for list separator.