Bug 1523328
Summary: | [RFE] Director Ansible integration - make config-download the default | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | James Slagle <jslagle> |
Component: | python-tripleoclient | Assignee: | James Slagle <jslagle> |
Status: | CLOSED ERRATA | QA Contact: | Gurenko Alex <agurenko> |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | 14.0 (Rocky) | CC: | asimonel, emacchi, hbrock, jcoufal, jliberma, jslagle, lmarsh, mburns, rhel-osp-director-maint |
Target Milestone: | Upstream M2 | Keywords: | FutureFeature, Triaged |
Target Release: | 14.0 (Rocky) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-tripleoclient-10.1.1-0.20180601020743.c54452b.el7ost | Doc Type: | Enhancement |
Doc Text: |
OpenStack director now uses Ansible for software configuration of the overcloud nodes. Ansible provides a more familiar and debuggable operator experience during overcloud deployment. Ansible is used to replace the communication and transport of the software configuration deployment data between heat and the heat agent (os-collect-config) on the overcloud nodes.
Instead of os-collect-config running on each overcloud node and polling for deployment data from heat, the Ansible control node applies the configuration by running an ansible-playbook with an Ansible inventory file and a set of playbooks and tasks. The Ansible control node (the node running ansible-playbook) is the undercloud by default.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-01-11 11:48:37 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1615694 |
Description
James Slagle
2017-12-07 18:02:09 UTC
Verified consistently since puddle 2018-08-21.2 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0045 |