<div dir="ltr"><div dir="auto"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Hi !</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I thought my perspective might be valuable as the author of a project that would likely end up being slashed: ARA [1].</div></div><div dir="auto"><div dir="auto"><br></div><div dir="auto"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">In a nutshell, ARA provides easy and seamless Ansible reporting on playbook runs.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">It has nothing to do with OpenStack, to be honest: it doesn't require OpenStack to run, it doesn't run on OpenStack.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">We highlight that ARA is not an "official" OpenStack project in the contributors' documentation [2].</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">But, it was born out of necessity inside the RDO community (call that the extended OpenStack community, if you will) due to the vast amount of our workloads that are driven by Ansible.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I like to draw a parallel between ARA and JJB [3] (Jenkins Job Builder) as two tools that the OpenStack community develops and use without slapping the OpenStack brand on them.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">If we take a step back, would projects like Nodepool or Zuul also be affected by this kind of cut ? Where do we draw the line ? Are they OpenStack projects or not ?</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">For me, applying for ARA to be hosted as a "community" project [4], or what would've been a "Stackforge" project long ago, was a completely logical choice to me.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I could go and praise how the Gerrit workflow is vastly superior than GitHub pull requests or that the Zuul-driven CI is completely awesome.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">But... The truth is that I sincerely hoped it would help the project gain exposure and credibility in order to drive adoption *inside* the OpenStack community.<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">We say that hindsight is 20/20, but, in retrospect [5], I guess we could say it worked.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Maybe out of luck, maybe out of sheer dedication and long weekends spent working on the project.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">The reality is that today, ARA is used by many different projects inside the OpenStack ecosystem -- to name a few:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">- OpenStack-Ansible</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">- TripleO</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">- Browbeat</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">- Kolla/Kolla-Ansible</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">- Devstack-Gate</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">But also, like Jenkins Job Builder, it has gained adoption outside of the OpenStack community -- such as inside the OpenShift Ansible community or BonnyCI.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Being part of the OpenStack "ecosystem" allows ARA to do things like easily implement a gate job almost verbatim from OpenStack-Ansible [6] to make sure that each new commit doesn't break them.<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I feel that this is useful and powerful not just for ARA but for OpenStack-Ansible and the other projects that use it as well.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Ironically, some projects feel hindered by this ecosystem (see: Gnocchi) and have made an exit.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I do not share these feelings and I would in fact be very sad to be shown the door.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">My 0.02$CAD (not worth much right now)</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div></div><div dir="auto"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">[1]: <a href="https://github.com/openstack/ara">https://github.com/openstack/ara</a></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">[2]: <a href="http://ara.readthedocs.io/en/latest/contributing.html#contributing">http://ara.readthedocs.io/en/latest/contributing.html#contributing</a><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">[3]: <a href="https://github.com/openstack-infra/jenkins-job-builder">https://github.com/openstack-infra/jenkins-job-builder</a></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">[4]: <a href="https://review.openstack.org/#/c/321226/">https://review.openstack.org/#/c/321226/</a></div><div dir="auto"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">[5]: <a href="https://dmsimard.com/2017/05/08/ara-is-one-year-old-a-look-back-at-the-past-year/">https://dmsimard.com/2017/05/08/ara-is-one-year-old-a-look-back-at-the-past-year/</a></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">[6]: <a href="https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/ara.yaml#L21-L89">https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/ara.yaml#L21-L89</a></div></div><br><div dir="auto">David Moreau Simard<br>Senior Software Engineer | Openstack RDO<br><br>dmsimard = [irc, github, twitter]</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Jun 28, 2017 6:46 PM, "James E. Blair" <<a href="mailto:corvus@inaugust.com" target="_blank">corvus@inaugust.com</a>> wrote:<br type="attribution"><blockquote class="gmail-m_6139796064869656986quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-m_6139796064869656986quoted-text">Thierry Carrez <<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>> writes:<br>
<br>
> Removing the root cause would be a more radical move: stop offering<br>
> hosting to non-OpenStack projects on OpenStack infrastructure<br>
> altogether. We originally did that for a reason, though. The benefits of<br>
> offering that service are:<br>
><br>
> 1- it lets us set up code repositories and testing infrastructure before<br>
> a project applies to be an official OpenStack project.<br>
><br>
> 2- it lets us host things that are not openstack but which we work on<br>
> (like abandoned Python libraries or GPL-licensed things) in a familiar<br>
> environment<br>
><br>
> 3- it spreads "the openstack way" (Gerrit, Zuul) beyond openstack itself<br>
<br>
</div>I think this omits what I consider the underlying reason for why we did<br>
it:<br>
<br>
It helps us build a community around OpenStack.<br>
<br>
Early on we had so many people telling us that we needed to support<br>
"ecosystem" projects better. That was the word they used at the time.<br>
Many of us said "hey, you're free to use github" and they told us that<br>
wasn't enough.<br>
<br>
We eventually got the message and invited them in, and it surpassed our<br>
expectations and I think surprised even the most optimistic of us. We<br>
ended up in a place where anyone with an OpenStack related idea can try<br>
it out and collaborate frictionlessly with everyone else in the<br>
OpenStack community on it, and in doing so, become recognized in the<br>
community for that. The ability for someone to build something on top<br>
of OpenStack as part of the OpenStack community has been empowering.<br>
<br>
I confess to being a skeptic and a convert. I wasn't thrilled about the<br>
unbounded additional responsibility when we started this, but now that<br>
we're here, I think it's one of the best things about the project and I<br>
would hate to cleave our community by ending it.<br>
<br>
-Jim<br>
<div class="gmail-m_6139796064869656986elided-text"><br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></blockquote></div><br></div>
</div>