Skip to content
This repository has been archived by the owner on Feb 29, 2024. It is now read-only.

Commit

Permalink
Role specific derive parameters workflow parameter
Browse files Browse the repository at this point in the history
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
  • Loading branch information
Jaganathancse committed Jun 28, 2018
1 parent c7b10fe commit 9c82505
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions plan-samples/plan-environment-derived-params.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 9c82505

Please sign in to comment.