tripleo-heat-templates/plan-samples
Jaganathan Palanisamy 9c82505cc2 Role specific derive parameters workflow parameter
Added 'hw_data_required' parameter with default value 'true'.
This parameter is used to identify whether role specific
derive parameters workflows needs to be invoked or not.
invokes role specific derive parameters if hw_data_required is
true, otherwise only common derive parameters will be invoked.

Change-Id: I9807dbd1cb71deb6a483f24d36db344b8a09c63e
2018-06-28 08:10:27 -04:00
..
plan-environment-derived-params.yaml Role specific derive parameters workflow parameter 2018-06-28 08:10:27 -04:00
README.rst Workflow input parameter update in plan-environment 2017-07-05 07:57:43 -04:00

Samples for plan-environment.yaml

The plan-environment.yaml file provides the details of the plan to be deployed by TripleO. Along with the details of the heat environments and parameters, it is also possible to provide workflow specific parameters to the TripleO mistral workflows. A new section workflow_parameters has been added to provide workflow specific parameters. This provides a clear separation of heat environment parameters and the workflow only parameters. These customized plan environment files can be provided as with -p option to the openstack overcloud deploy and openstack overcloud plan create commands. The sample format to provide the workflow specific parameters:

workflow_parameters:
  tripleo.derive_params.v1.derive_parameters:
    # DPDK Parameters
    num_phy_cores_per_numa_node_for_pmd: 2

All the parameters specified under the workflow name will be passed as user_input to the workflow, while invoking from the tripleoclient.