<div dir="ltr"><div>Also packaging python is basically non-trivial to the point that most folks are talking about pushing python around as virtual machines, containers, or more likely virtualenvs ( packaged or otherwise ). pip is a PITA, we tend to do terrible things to pbr that we shouldn't because there is a lack of knowledge about how to work with it in a packaging scenario.<br><br></div>-Matt<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 13, 2015 at 4:56 PM, Subbu Allamaraju <span dir="ltr"><<a href="mailto:subbu@subbu.org" target="_blank">subbu@subbu.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>Regarding the discussion on tags, here<span style="background-color:rgba(255,255,255,0)"> is my take from the discussion on Monday.</span></div><div><br></div><div><div><span style="background-color:rgba(255,255,255,0)">1. There is vehement agreement that having an integrated release consisting of a small “inner ring” set of service is desirable. There are 6-7 projects that a majority of operators deploy. </span></div><div><span style="background-color:rgba(255,255,255,0)"><br></span></div><div><span style="background-color:rgba(255,255,255,0)">2. There is a general concern that dropping the integrated release process entirely creates more operability hurdles than that exist today.</span></div><div><span style="background-color:rgba(255,255,255,0)"><br></span></div><div><span style="background-color:rgba(255,255,255,0)">3. Many other projects are not seeing adoption for reasons such as lacking a minimum viable feature set, lack of operational feedback, concerns on scalability etc. Examples include designate, trove, zaqar, ceilometer etc. </span></div><div><span style="background-color:rgba(255,255,255,0)"><br></span></div><div><span style="background-color:rgba(255,255,255,0)">4. There is also a concern of whether tags make the tent too large and chaotic as any project can essentially claim to be an OpenStack project. This may leave it open for vendors and distro providers to define a product out of those OpenStack projects, eventually fragmenting the open source nature.</span></div><div><span style="background-color:rgba(255,255,255,0)"><br></span></div><div><span style="background-color:rgba(255,255,255,0)">5. Operators can certainly help shape an MVP feature set.</span></div></div><span class="HOEnZb"><font color="#888888"><div><br><div>Subbu</div><div><br></div></div></font></span><div><div class="h5"><div><br>On Mar 13, 2015, at 12:29 PM, Daniel Comnea <<a href="mailto:comnea.dani@gmail.com" target="_blank">comnea.dani@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div><div><div><div>Tim,<br><br></div>Are you aware of any other feedback etherpads for the other discussions? <br><br></div>Cheers,<br></div>Dani<br><br></div>P.S for Nova Sean provided one of the best summaries.<br> <br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 10, 2015 at 10:04 AM, Tim Bell <span dir="ltr"><<a href="mailto:Tim.Bell@cern.ch" target="_blank">Tim.Bell@cern.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I don't think there is any recording. The etherpads and summaries on <a href="http://superuser.openstack.org" target="_blank">superuser.openstack.org</a> give a feeling for the discussions though and are an interesting read. The tags one looked particularly lively.<br>
<span><font color="#888888"><br>
Tim<br>
</font></span><div><div><br>
> -----Original Message-----<br>
> From: Adam Huffman [mailto:<a href="mailto:adam.huffman@gmail.com" target="_blank">adam.huffman@gmail.com</a>]<br>
> Sent: 10 March 2015 10:50<br>
> To: Daniel Comnea<br>
> Cc: Tim Bell; <a href="mailto:openstack-operators@lists.openstack.org" target="_blank">openstack-operators@lists.openstack.org</a><br>
> Subject: Re: [Openstack-operators] Ops meetup<br>
><br>
> I was going to ask that too...<br>
><br>
> Cheers,<br>
> Adam<br>
><br>
> On Tue, Mar 10, 2015 at 7:38 AM, Daniel Comnea <<a href="mailto:comnea.dani@gmail.com" target="_blank">comnea.dani@gmail.com</a>><br>
> wrote:<br>
> > Hi Tim,<br>
> ><br>
> > For those who can't be physically there, will be any sort of<br>
> > recordings/ output coming out from this sessions?<br>
> ><br>
> > Thanks,<br>
> > Dani<br>
> ><br>
> > On Sat, Mar 7, 2015 at 7:24 PM, Tim Bell <<a href="mailto:Tim.Bell@cern.ch" target="_blank">Tim.Bell@cern.ch</a>> wrote:<br>
> >><br>
> >><br>
> >><br>
> >> Great to see lots of input for the ops meetup nexts week. Feel free<br>
> >> to add your items to the agenda<br>
> >><br>
> >><br>
> >><br>
> >><br>
> >> Session Etherpads:<br>
> >><br>
> >> Draft Agenda:<br>
> >> <a href="http://lists.openstack.org/pipermail/openstack-operators/2015-Februar" target="_blank">http://lists.openstack.org/pipermail/openstack-operators/2015-Februar</a><br>
> >> y/006268.html<br>
> >><br>
> >><br>
> >><br>
> >> Monday<br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-OVS" target="_blank">https://etherpad.openstack.org/p/PHL-ops-OVS</a><br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-security" target="_blank">https://etherpad.openstack.org/p/PHL-ops-security</a><br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-app-eco-wg" target="_blank">https://etherpad.openstack.org/p/PHL-ops-app-eco-wg</a><br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-tools-wg" target="_blank">https://etherpad.openstack.org/p/PHL-ops-tools-wg</a><br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-large-deployments" target="_blank">https://etherpad.openstack.org/p/PHL-ops-large-deployments</a><br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-tags" target="_blank">https://etherpad.openstack.org/p/PHL-ops-tags</a><br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-hardware" target="_blank">https://etherpad.openstack.org/p/PHL-ops-hardware</a><br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-arch-show-tell" target="_blank">https://etherpad.openstack.org/p/PHL-ops-arch-show-tell</a><br>
> >><br>
> >><br>
> >><br>
> >> Tuesday<br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-rabbit-queue" target="_blank">https://etherpad.openstack.org/p/PHL-ops-rabbit-queue</a><br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-nova-feedback" target="_blank">https://etherpad.openstack.org/p/PHL-ops-nova-feedback</a><br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-network-performance" target="_blank">https://etherpad.openstack.org/p/PHL-ops-network-performance</a><br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-capacity-mgmt" target="_blank">https://etherpad.openstack.org/p/PHL-ops-capacity-mgmt</a><br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-testing-interop" target="_blank">https://etherpad.openstack.org/p/PHL-ops-testing-interop</a><br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-burning-issues" target="_blank">https://etherpad.openstack.org/p/PHL-ops-burning-issues</a><br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-packaging" target="_blank">https://etherpad.openstack.org/p/PHL-ops-packaging</a><br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-telco" target="_blank">https://etherpad.openstack.org/p/PHL-ops-telco</a><br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-arch-show-tell" target="_blank">https://etherpad.openstack.org/p/PHL-ops-arch-show-tell</a><br>
> >><br>
> >><br>
> >><br>
> >> Feedback on the event & what you'd like to see in Vancouver:<br>
> >><br>
> >> <a href="https://etherpad.openstack.org/p/PHL-ops-feedback" target="_blank">https://etherpad.openstack.org/p/PHL-ops-feedback</a><br>
> >><br>
> >><br>
> >><br>
> >><br>
> >><br>
> >><br>
> >> _______________________________________________<br>
> >> OpenStack-operators mailing list<br>
> >> <a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operato" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operato</a><br>
> >> rs<br>
> >><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > OpenStack-operators mailing list<br>
> > <a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operator" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operator</a><br>
> > s<br>
> ><br>
</div></div></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>OpenStack-operators mailing list</span><br><span><a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a></span><br><span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a></span><br></div></blockquote></div></div></div><br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br></div>