Fix plan-samples README.rst
This is quite stale referencing mistral workflows. Change-Id: I3485543210aa04c89d9c0873a6d0e10c3d5758fc
This commit is contained in:
parent
147335f799
commit
e7d824688e
|
@ -2,21 +2,17 @@
|
||||||
Samples for plan-environment.yaml
|
Samples for plan-environment.yaml
|
||||||
=================================
|
=================================
|
||||||
|
|
||||||
The ``plan-environment.yaml`` file provides the details of the plan to be
|
The ``plan-environment.yaml`` file provides the details of playbooks
|
||||||
deployed by TripleO. Along with the details of the heat environments and
|
and their parameters required for use cases like derived parameter
|
||||||
parameters, it is also possible to provide workflow specific parameters to the
|
workflow. It has a section ``playbook_parameters`` that is used to
|
||||||
TripleO mistral workflows. A new section ``workflow_parameters`` has been
|
specify playbook name and playbooks parameters.
|
||||||
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:
|
These plan environment files can be provided as with ``-p`` option
|
||||||
tripleo.derive_params.v1.derive_parameters:
|
to the ``openstack overcloud deploy``.
|
||||||
|
|
||||||
|
The sample format to provide the playbook specific parameters::
|
||||||
|
|
||||||
|
playbook_parameters:
|
||||||
|
cli-derive-parameters.yaml:
|
||||||
# DPDK Parameters
|
# DPDK Parameters
|
||||||
num_phy_cores_per_numa_node_for_pmd: 2
|
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.
|
|
||||||
|
|
Loading…
Reference in New Issue