Browse Source

Providing parameters specific to a workflow via plan-environment

Parameters which are not part of the heat environment template
are required by the worflows like derive parameters. In order to
seprate from the heat environment parameters, the workflow only
parameters will be provided via plan-environement section,
workflow_parameters.
Implements: blueprint tripleo-derive-parameters

Change-Id: I36d295223c28afff1e0996b4885b8a81c00842f0
changes/74/457874/9
Saravanan KR 5 years ago
parent
commit
22a283aeeb
  1. 22
      plan-samples/README.rst
  2. 35
      plan-samples/plan-environment-derived-params.yaml
  3. 4
      releasenotes/notes/derive-params-custom-plan-env-3a810ff58a68e0ad.yaml

22
plan-samples/README.rst

@ -0,0 +1,22 @@
=================================
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
number_of_pmd_cpu_threads_per_numa_node: 2
All the parameters specified under the workflow name will be passed as
``user_input`` to the workflow, while invoking from the tripleoclient.

35
plan-samples/plan-environment-derived-params.yaml

@ -0,0 +1,35 @@
version: 1.0
name: overcloud
description: >
Default Deployment plan
template: overcloud.yaml
environments:
- path: overcloud-resource-registry-puppet.yaml
workflow_parameters:
tripleo.derive_params.v1.derive_parameters:
######### DPDK Parameters #########
# Specifices the minimum number of CPU threads to be allocated for DPDK
# PMD threads. The actual allocation will be based on network config, if
# the a DPDK port is associated with a numa node, then this configuration
# will be used, else 0.
number_of_pmd_cpu_threads_per_numa_node: 4
# Amount of memory to be configured as huge pages in percentage. Ouf the
# total available memory (excluding the NovaReservedHostMemory), the
# specified percentage of the remaining is configured as huge pages.
huge_page_allocation_percentage: 90
######### HCI Parameters #########
hci_profile: default
hci_profile_config:
default:
average_guest_memory_size_in_mb: 2048
average_guest_cpu_utilization_percentage: 50
many_small_vms:
average_guest_memory_size_in_mb: 1024
average_guest_cpu_utilization_percentage: 20
few_large_vms:
average_guest_memory_size_in_mb: 4096
average_guest_cpu_utilization_percentage: 80
nfv_default:
average_guest_memory_size_in_mb: 8192
average_guest_cpu_utilization_percentage: 90

4
releasenotes/notes/derive-params-custom-plan-env-3a810ff58a68e0ad.yaml

@ -0,0 +1,4 @@
---
features:
- Added a custom plan-environment file for providing workflow specific
inputs for the derived parameters workflow.
Loading…
Cancel
Save