From 9c82505cc29f06f059a5b620eecf087a6ce6411e Mon Sep 17 00:00:00 2001 From: Jaganathan Palanisamy Date: Thu, 28 Jun 2018 08:02:24 -0400 Subject: [PATCH] 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 --- plan-samples/plan-environment-derived-params.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/plan-samples/plan-environment-derived-params.yaml b/plan-samples/plan-environment-derived-params.yaml index 1923debfc9..d3497ea61b 100644 --- a/plan-samples/plan-environment-derived-params.yaml +++ b/plan-samples/plan-environment-derived-params.yaml @@ -8,6 +8,12 @@ environments: - path: overcloud-resource-registry-puppet.yaml workflow_parameters: tripleo.derive_params.v1.derive_parameters: + ########### Role-Specific derive parameters ############## + # Introspection hardware data is mandatory for role-specific + # derive parameters. Role specific derive parameters workflows + # will be invoked if this parameter is true, otherwise only + # derive parameters common workflows will be invoked. + hw_data_required: true ######### DPDK Parameters ######### # Specifices the minimum number of CPU physical cores to be allocated for DPDK # PMD threads. The actual allocation will be based on network config, if