[tripleo][tripleo-ansible] Reigniting tripleo-ansible
I am really happy to hear about that as this could be much more effective than having an uncontrollable number of roles scattered across lots of repositories which usually do not play very nice with each other.
I hope that testing these roles using molecule (official ansible testing platform) is also part of this plan.
> On 3 Jun 2019, at 18:42, Kevin Carter <kecarter at redhat.com> wrote:
> On Mon, Jun 3, 2019 at 12:08 PM Mohammed Naser <mnaser at vexxhost.com <mailto:mnaser at vexxhost.com>> wrote:
> On Mon, Jun 3, 2019 at 12:55 PM Kevin Carter <kecarter at redhat.com <mailto: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 <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 geared toward building the structure around tripleo-ansible 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.
> Most definitely in. We've had great success working with the TripleO team on
> integrating the Tempest role and on the OSA side, we'd be more than happy
> to help try and converge our roles to maintain them together.
> If there's any meetings or anything that will be scheduled, I'd be
> happy to attend.
> its still very early but I expect to begin regular meetings (even if they're just impromptu IRC conversations to begin with) to work out what needs to be done and where we can begin collaborating with other folks. As soon as we have more I'll be sure to reach out here and on IRC.
> >  - https://review.opendev.org/662763 <https://review.opendev.org/662763>
> >  - https://opendev.org/openstack/tripleo-ansible <https://opendev.org/openstack/tripleo-ansible>
> > --
> > Kevin Carter
> > IRC: cloudnull
> Mohammed Naser â?? vexxhost
> D. 514-316-8872
> D. 800-910-1726 ext. 200
> E. mnaser at vexxhost.com <mailto:mnaser at vexxhost.com>
> W. http://vexxhost.com <http://vexxhost.com/>
-------------- next part --------------
An HTML attachment was scrubbed...