9b3b1c6358
derive_parameters workflow input parameter needs to be changed as num_phy_cores_per_numa_node_for_pmd instead of number_of_pmd_cpu_threads_per_numa_node. The performance varies based on the physical core rather than the logical CPUs. Which means, user should be able to decide the number of physical cores, which is proportional to data rate. Implements: blueprint tripleo-derive-parameters Change-Id: I056fb330a17e647ab527e8bccd52bdf5e77067b6
23 lines
1.0 KiB
ReStructuredText
23 lines
1.0 KiB
ReStructuredText
=================================
|
|
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.
|