b3c670faeb
This change modifies the unbound playbook so that it follows a JIT pattern allowing the playbooks to install what they need when they need it. Prior to this change the unbound playbook would iterate through all target hosts, including containers, and attempt to install the client resource or simply execute the resolveconf role which would end in failure should the target resource not be available at the time of execution. Converting this to a JIT pattern should save general time when installing with and without unbound on initial deployments and will guarantee that the target hosts, including containers, have the most up-to-date client code unpo deployment, or upgrade, of a given service. Change-Id: I829747094cabc8027bad904cb822a6d265f48d73 Signed-off-by: Kevin Carter <kevin.carter@rackspace.com> |
||
|---|---|---|
| .. | ||
| cinder.yml | ||
| glance.yml | ||
| neutron.yml | ||
| nova.yml | ||
| unbound-clients.yml | ||