In this post, I intend to bring new folks into TripleO-Ansible by explaining how TripleO is evolving. We're building a modular set of Ansible roles, playbooks, plugins, and scripts, which are reforming the foundation of enterprise-ready OpenStack environments. While that's awesome in its own right, these tools are also built
TripleO-Ansible roles are built to be simple to understand, easily documented, and tested. In this post, I will go over the parts of a TripleO-Ansible role and why they're important. What is an Ansible Role Roles are simple and well documented by Ansible, > Roles are ways of automatically loading certain
The TripleO project team has been embarking on developing Ansible roles for deploying and operating OpenStack clouds. While this is not new, over the last couple of months, we've re-ignited our simplification efforts [http://lists.openstack.org/pipermail/openstack-discuss/2019-June/006836.html] and have focused on creating simple, well-tested tooling.