0464bdc17f
This change is the first step to providing a path to remove the mistral "derived_params" workflows. Deployers will now be able to execute playbooks from within a given plan by passing in the `playbook_parameters` key which contains a dictionary of playbook file paths, and all options applied to a given playbook. Story: 2007419 Task: 39118 Change-Id: I26ea1c01e17513d001e311d68fd239d3ba8c8a0d Signed-off-by: Kevin Carter <kecarter@redhat.com>
27 lines
957 B
YAML
27 lines
957 B
YAML
---
|
|
features:
|
|
- |
|
|
A new interface has been created allowing deployers to run arbitrary
|
|
playbooks which are defined within a deployment plan. This interface is
|
|
being created to replace the existing Mistral interface, which is largely
|
|
used for HCI and NFV use cases. The interface will now process playbooks
|
|
when they're defined within a plan under the `playbook_parameters` key.
|
|
|
|
Playbook entries can be defined with, and without the base path. If no base
|
|
path is defined within the entry, the interface will fall back to the
|
|
constant tripleo playbook path, `/usr/share/ansible/tripleo-playbooks`.
|
|
Options fined within a playbook entry will be passed into the playbook at
|
|
runtime using extra-vars.
|
|
|
|
* Interface usage example
|
|
|
|
.. code-block:: yaml
|
|
|
|
playbook_parameters:
|
|
sample-playbook-0.yaml:
|
|
x: 1
|
|
y: a
|
|
/path/to/sample-playbook-1.yaml:
|
|
x: a
|
|
y: 1
|