tripleo-heat-templates/plan-samples
Jaganathan Palanisamy 913444d854 Update default value for derive params workflow inputs
This change is to update the default value for derive params
workflow inputs num_phy_cores_per_numa_node_for_pmd
and huge_page_allocation_percentage.
num_phy_cores_per_numa_node_for_pmd default value needs to be reduced
to 1 and cannot use more than 1 because of multi-queues.
huge_page_allocation_percentage default value needs to be reduced
from 90 because in some cases where we do not have enough memory
for some hosts

Change-Id: I8620f07f09337d0d63198c3168fec00f16262a63
Closes-Bug: #1736713
2018-01-15 05:50:47 -05:00
..
plan-environment-derived-params.yaml Update default value for derive params workflow inputs 2018-01-15 05:50:47 -05: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.