Open Stack

In doing a brief audit of the `tripleo-ansible` landscape it seems like we
have many repositories [0] with little to no activity (most being simple
role shells) [1].

While these repositories seem well intentioned, I'm not really sure we need
them. All of these roles fall under the `tripleo-ansible` acls and, in my
opinion, are at odds with the initial stated goal:

> ... co-locating all of the Ansible tasks/roles/libraries/plugins
throughout the code base into a single purpose-built repository ...

While I can see a place for some of these roles and could rationalize
building independent, reusable, repositories I don't think we're anywhere
near ready for that at this time. I also believe that when where we're
ready to begin building independent role repositories we should do so
collaboratively; working with the likes of Infra, OpenStack-Ansible, Kolla,
Airship, and anyone else who wants to contribute.

So the questions at hand are: what, if anything, should we do with these
repositories? Should we retire them or just ignore them? Is there anyone
using any of the roles?

[0] -
https://opendev.org/openstack/project-config/src/commit/a12c6b531f58aaf9c838299cc0f2abc8c9ee9f40/gerrit/projects.yaml#L891-L1060=
[1] -
https://review.opendev.org/#/q/project:%255Eopenstack/ansible-role-tripleo.*+status:open

Kevin Carter
IRC: cloudnull


On Mon, Jun 3, 2019 at 11:27 AM Kevin Carter <kecarter at redhat.com> wrote:

> Hello Stackers,
>
> I wanted to follow up on this post from last year, pick up from where it
> left off, and bring together a squad to get things moving.
>
> >
> http://lists.openstack.org/pipermail/openstack-dev/2018-August/133801.html
>
> The effort to convert tripleo Puppet and heat templates with embedded
> Ansible to a more consumable set of playbooks and roles is in full effect.
> As we're working through this effort we believe co-locating all of the
> Ansible tasks/roles/libraries/plugins throughout the code base into a
> single purpose-built repository will assist us in streamlining and
> simplifying. Structurally, at this time, most of tripleo will remain the
> same. However, the inclusion of tripleo-Ansible will allow us to create
> more focused solutions which are independently testable, much easier
> understand, and simple to include into the current heat template deployment
> methodologies. While a straight port of the existing Ansible tasks will not
> be entirely possible, the goal of this ongoing effort will be zero impact
> on our existing workflow and solutions.
>
> To reigniting this effort, I've put up a review to create a new
> "transformation" squad[0] geared toward building the structure around
> tripleo-ansible[1] and converting our current solutions into
> roles/playbooks/libraries/plugins. Initially, we'll be focused on our
> existing code base; however, long term, I believe it makes sense for this
> squad to work across projects to breakdown deployment barriers for folks
> using similar technologies.
>
> We're excited to get this effort rolling again and would love to work with
> anyone and everyone throughout the community. If folks are interested in
> this effort, please let us know.
>
> [0] - https://review.opendev.org/662763
> [1] - https://opendev.org/openstack/tripleo-ansible
> --
>
> Kevin Carter
> IRC: cloudnull
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190604/c500fe16/attachment.html>