openstack/tripleo-heat-templates
Code Issues Proposed changes

Fix plan-samples README.rst

Browse Source 
This is quite stale referencing mistral workflows.

Change-Id: I3485543210aa04c89d9c0873a6d0e10c3d5758fc
This commit is contained in:
ramishra 2021-03-04 13:42:01 +05:30
parent 147335f799
commit e7d824688e
1 changed files with 11 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
plan-samples/README.rst
View File

@ -2,21 +2,17 @@
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::
The ``plan-environment.yaml`` file provides the details of playbooks
and their parameters required for use cases like derived parameter
workflow. It has a section ``playbook_parameters`` that is used to
specify playbook name and playbooks parameters.
workflow_parameters:
tripleo.derive_params.v1.derive_parameters:
These plan environment files can be provided as with ``-p`` option
to the ``openstack overcloud deploy``.
The sample format to provide the playbook specific parameters::
playbook_parameters:
cli-derive-parameters.yaml:
# 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.