diff options
| author | Pavlo Shchelokovskyy <shchelokovskyy@gmail.com> | 2017-10-09 07:09:31 +0000 |
|---|---|---|
| committer | Pavlo Shchelokovskyy <shchelokovskyy@gmail.com> | 2017-11-09 10:30:56 +0000 |
| commit | 9b1a7ceb4b32089ccec2e9aca530699ae5e7cedb (patch) | |
| tree | 6efcc52bd0dc9d3583363d1a74ffafd885084366 /releasenotes/notes/ansible-deploy-15da234580ca0c30.yaml | |
| parent | 9175c2325e438a01cd9c8c9ee2d4f49f713127d1 (diff) | |
| download | ironic-9b1a7ceb4b32089ccec2e9aca530699ae5e7cedb.tar.gz | |
Add ansible deploy interface
this patch pulls the ansible deploy interface code
and related ansible playbooks and auxiliary files
from ironic-staging-drivers project into main ironic tree.
As discussed in the spec, the use of ramdisk callbacks
(lookup and hearbeats) is now mandatory with this deploy interface.
Playbooks and modules were updated to require Ansible>=2.4,
and custom Ansible module for executing 'parted' was replaced
with usage of built-in Ansible module.
The custom Ansible callback plugin now uses journald logger
by default to adapt to the default DevStack setup.
Documentation and devstack plugin changes enabling automated
testing of this interface will be proposed in followup patches.
Change-Id: I43f54688287953ccb1c2836437aea76236e6560b
Related-Bug: #1526308
Diffstat (limited to 'releasenotes/notes/ansible-deploy-15da234580ca0c30.yaml')
| -rw-r--r-- | releasenotes/notes/ansible-deploy-15da234580ca0c30.yaml | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/releasenotes/notes/ansible-deploy-15da234580ca0c30.yaml b/releasenotes/notes/ansible-deploy-15da234580ca0c30.yaml new file mode 100644 index 000000000..c49b3e700 --- /dev/null +++ b/releasenotes/notes/ansible-deploy-15da234580ca0c30.yaml @@ -0,0 +1,11 @@ +--- +features: + - | + Adds a new ``ansible`` deploy interface. It targets mostly undercloud + use-case by allowing greater customization of provisioning process. + + This new deploy interface is usable only with hardware types. + It is set as supported for a ``generic`` hardware type and all + its subclasses, but must be explicitly enabled in the + ``[DEFAULT]enabled_deploy_interfaces`` configuration file option + to actually allow setting nodes to use it. |