Name of function: Ansible integration with director User story: As an administrator/installer, I want to be able to use Ansible to make the use of director, as a tool both for deployment and managing my OpenStack, less complex and easier to learn, more reliable and able to debug installations for me. Purpose of function: Heat is still used in the typical fashion to create the stack and all of the descendant resources. Heat creates all the deployment data necessary to perform the Overcloud installation and configuration, but it does not apply any of the deployments. A config-download workflow is triggered after the Heat stack is completed that downloads all of the deployment data from Heat, which generates Ansible playbooks and tasks that are then used by the undercloud to complete the configuration of the Overcloud. Work required (from detail plan): Procedural ------ - dry run of Ansible before deployment? (OSP 13 TP) - How to enable ansible integration (OSP 14 FS) - default installation - remove enablement steps Test deployment: - Re-run and skip deployment steps? How to check for deployment failures - updating commands to allow the operator to get the status/ query logs ------ Conceptual ------ Install and enablement is by default in OSP 14 ------ Reference ------ N/A ------ Note: This functionality was enabled as a Technology Preview in RHOSP 13, and was documented as part of bug 1558145.
Accepting in RHOSP 14 program.
Assigning to Dan for review. Dan, I'm setting GA as the ultimate milestone for the EPIC, but your first drafts and set of BZs that track testing for QE should be aimed at Beta.
New upstream config-download docs patch: https://review.openstack.org/#/c/599053/
Peer review completed and guide republished.