On 3/13/15, 3:20 PM, "Jonathan Proulx" <[email protected]> wrote:
>On Fri, Mar 13, 2015 at 4:56 PM, Subbu Allamaraju <[email protected]> wrote: >> Regarding the discussion on tags, here is my take from the discussion on >> Monday. >> >> 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. >> >> 2. There is a general concern that dropping the integrated release >>process >> entirely creates more operability hurdles than that exist today. > >There was definite concern about co-gating, being sure there is a >defined set of core project releases that work together. I don't think >fixing these in an integrated release was seen as the only solution. > >For example if Neutron is releasing versions foo, bar and baz that all >gate with Nova foo there's no pressing reason that nova need to make >three releases just to keep naming in sync (or vice versa if Nova >moves at higher velocity the Neutron) > >The pressing need i s the ability to express that when the cogating >set changes so it is easily discoverable what set is tested togather. >Keeping the core integrated may be the simplest solution but I don't >think it was the only option in the room. Personally, I like the WordPress plugin model for discovering the compatibility between versions. See https://wordpress.org/plugins/akismet/ , right side near the bottom of the page. Allows you to figure out if service A version x works with service B version y. > >> 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. >> >> 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 > >> 5. Operators can certainly help shape an MVP feature set. > >there is a list of email volunteer on >https://etherpad.openstack.org/p/PHL-ops-tags to make up a ops-tags >working group to continue these discussions, so anyone who couldn't >make it to PHL and is interested in being part of that working group >should probably sign on on the etherpad. > >also those of us who have already signed on should probably figure out >what that means in terms of email discussion (should it be her or on >the user-comittee list or somewhere else) and possibly IRC meetings or >what have you... > >-Jon > >> Subbu >> >> >> On Mar 13, 2015, at 12:29 PM, Daniel Comnea <[email protected]> >>wrote: >> >> Tim, >> >> Are you aware of any other feedback etherpads for the other discussions? >> >> Cheers, >> Dani >> >> P.S for Nova Sean provided one of the best summaries. >> >> >> On Tue, Mar 10, 2015 at 10:04 AM, Tim Bell <[email protected]> wrote: >>> >>> I don't think there is any recording. The etherpads and summaries on >>> superuser.openstack.org give a feeling for the discussions though and >>>are an >>> interesting read. The tags one looked particularly lively. >>> >>> Tim >>> >>> > -----Original Message----- >>> > From: Adam Huffman [mailto:[email protected]] >>> > Sent: 10 March 2015 10:50 >>> > To: Daniel Comnea >>> > Cc: Tim Bell; [email protected] >>> > Subject: Re: [Openstack-operators] Ops meetup >>> > >>> > I was going to ask that too... >>> > >>> > Cheers, >>> > Adam >>> > >>> > On Tue, Mar 10, 2015 at 7:38 AM, Daniel Comnea >>><[email protected]> >>> > wrote: >>> > > Hi Tim, >>> > > >>> > > For those who can't be physically there, will be any sort of >>> > > recordings/ output coming out from this sessions? >>> > > >>> > > Thanks, >>> > > Dani >>> > > >>> > > On Sat, Mar 7, 2015 at 7:24 PM, Tim Bell <[email protected]> wrote: >>> > >> >>> > >> >>> > >> >>> > >> Great to see lots of input for the ops meetup nexts week. Feel >>>free >>> > >> to add your items to the agenda >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> Session Etherpads: >>> > >> >>> > >> Draft Agenda: >>> > >> >>>http://lists.openstack.org/pipermail/openstack-operators/2015-Februar >>> > >> y/006268.html >>> > >> >>> > >> >>> > >> >>> > >> Monday >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-OVS >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-security >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-app-eco-wg >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-tools-wg >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-large-deployments >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-tags >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-hardware >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-arch-show-tell >>> > >> >>> > >> >>> > >> >>> > >> Tuesday >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-rabbit-queue >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-nova-feedback >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-network-performance >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-capacity-mgmt >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-testing-interop >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-burning-issues >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-packaging >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-telco >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-arch-show-tell >>> > >> >>> > >> >>> > >> >>> > >> Feedback on the event & what you'd like to see in Vancouver: >>> > >> >>> > >> https://etherpad.openstack.org/p/PHL-ops-feedback >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> _______________________________________________ >>> > >> OpenStack-operators mailing list >>> > >> [email protected] >>> > >> >>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operato >>> > >> rs >>> > >> >>> > > >>> > > >>> > > _______________________________________________ >>> > > OpenStack-operators mailing list >>> > > [email protected] >>> > > >>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operator >>> > > s >>> > > >> >> >> _______________________________________________ >> OpenStack-operators mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >> >> _______________________________________________ >> OpenStack-operators mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> > >_______________________________________________ >OpenStack-operators mailing list >[email protected] >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
