Update to methods for deploying STF client-side components in Tripleo Modernisation of the deployment to remove the puppet configuration and using ansible for deploying components, this allows reusing of the deployment for these components outside of OSP. ~~~ ## Additional Testing Information (originally from STF-251) As soon as we have a viable downstream OSP17 puddle we should re-test the ansible work with special attention to: Collectd + QDR on CEPH nodes (correct interface utilization, certificate naming, etc) Collectd plugins covered by feature BZs QDR w/ TLS-everywhere QDR OSP -> OCP certificate issues I think we have semi-decent coverage on these already, but it's worth double checking the dark corners.
What's the current status here? Do we have a package to build? Is that missing?
Ansible is being replaced in tripleo by directord for OSP 18, so this work (which was originally scheduled as Tech Preview in 17) is being terminated.
This work has been revived. At least for OSP17 and 18, we believe that ansible will be supported.
This RFE was not marked MVP for OSP 17.0, it will be moved to 17.1. If Tech Preview is required for OSP 17.0 please clone issue and follow procedure, contact the TRAC team.
This RFE will be closed as this tech preview will not be utilized going forward. Please continue to leverage the existing automation components via puppet instead of using the Ansible version covered by this RFE. In future releases of RHOSP we may or may not make use of these components.
Closing this RFE which was slated to be tech preview for RHOSP 17.1. We do not intend to fully productize this solution, and thus the work here is now completed.