Re: [openstack-dev] [TripleO] Summit scheduling - using our time together wisely.
I'm anxious to get titles for the scheduled sessions so that people can start planning their daily schedules. I have heard some opinions about the Neutron/Nova/Ironic work that needs to happen to support L3 (I think we should still bring it up) and also a bit about Cinder HA. I think these are things that will benefit from a f2f conversation with the OpenStack community at large. I also think that the biggest theme I see beyond that is UI/onboarding. So I think we should split the 2 40 minute sessions into these two things: * L3 Networking + Cinder HA - Summary of changes needed in Cinder/Neutron/Nova/Ironic/etc. - Configuration changes needed - UI changes * TripleO's onramp - All things new contributor - QuintupleO progress report - Tuskar progress report - Alternative implementations roll call - Kolla - Puppet - Ansible The rest of the things in the etherpad will make for a good agenda for Friday. Does anyone have anything to add, or dissent to register? Excerpts from Clint Byrum's message of 2014-10-16 13:14:26 -0700: The format has changed slightly this summit, to help encourage a more collaborative design experience, rather than rapid fire mass-inclusion summit sessions. So we have two 40-minute long slots, and one whole day of contributor meetup.[1] Our etherpad topics page has received quite a few additions now [2], and so I'd like to hear thoughts on what things we want to talk about in the meetup versus the sessions. A few things I think we should stipulate: * The scheduled sessions will be heavily attended by the community at large. This often includes those who are just curious, or those who want to make sure that their voice is heard. These sessions should be reserved for those topics which have the most external influence or are the most dependent on other projects. * The meetup will be at the end of the week so at the end of it, we can't then go to any other meetups and ask for things / participate in those design activities. This reinforces that scheduled session time should be focused on things that are externally focused so that we can take the result of those discussions into any of the sessions that are after. * The Ops Summit is Wendesday/Thursday [3], which overlaps with these sessions. I am keenly interested in gathering more contribution from those already operating and deploying OpenStack. It can go both ways, but I think it might make sense to have more ops-centric topics discussed on Friday, when those participants might not be fully wrapped up in the ops sessions. If we can all agree on those points, given the current topics, I think our scheduled sessions should target at least (but not limited to): * Cinder + CEPH * Layer 3 segmentation I think those might fit into 40 minutes, as long as we hash some things out here on the mailing list first. Cinder + CEPH is really just a check-in to make sure we're on track to providing it. Layer 3, I've had discussions with Ironic and Neutron people and I think we have a plan, but I wanted to present it in the open and discuss the short term goals to see if it satisfies what users may want for the Kilo time frame. So, I would encourage you all to look at the etherpad, and expand on topics or add more, and then reply to this thread with ideas for how best to use our precious time together. [1] http://kilodesignsummit.sched.org/overview/type/tripleo [2] https://etherpad.openstack.org/p/kilo-tripleo-summit-topics [3] http://kilodesignsummit.sched.org/overview/type/ops+summit ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Summit scheduling - using our time together wisely.
On 10/27/2014 12:30 PM, Clint Byrum wrote: I'm anxious to get titles for the scheduled sessions so that people can start planning their daily schedules. I have heard some opinions about the Neutron/Nova/Ironic work that needs to happen to support L3 (I think we should still bring it up) and also a bit about Cinder HA. I think these are things that will benefit from a f2f conversation with the OpenStack community at large. I also think that the biggest theme I see beyond that is UI/onboarding. So I think we should split the 2 40 minute sessions into these two things: * L3 Networking + Cinder HA - Summary of changes needed in Cinder/Neutron/Nova/Ironic/etc. - Configuration changes needed - UI changes I still have some reservations about these, as I noted in my previous mail, but at this point I don't have an alternative suggestion so I guess +1 from me. * TripleO's onramp - All things new contributor - QuintupleO progress report This should be pretty brief, unless someone else has done a bunch of work on it that I'm not aware of. Nothing has really changed on my end since the blog post I made on this about a month ago. - Tuskar progress report - Alternative implementations roll call Any one of these seems like a potential rabbit hole that could end up taking the entire session. I definitely think these are important topics to discuss, but if we're going to try to fit them into one of the sessions I think we need to be very, very clear about the scope of the discussion. With basically five topics in this session, each one has less than 10 minutes available to it. We're talking very brief introduction and maybe a couple of questions here. - Kolla - Puppet - Ansible The rest of the things in the etherpad will make for a good agenda for Friday. Does anyone have anything to add, or dissent to register? Excerpts from Clint Byrum's message of 2014-10-16 13:14:26 -0700: The format has changed slightly this summit, to help encourage a more collaborative design experience, rather than rapid fire mass-inclusion summit sessions. So we have two 40-minute long slots, and one whole day of contributor meetup.[1] Our etherpad topics page has received quite a few additions now [2], and so I'd like to hear thoughts on what things we want to talk about in the meetup versus the sessions. A few things I think we should stipulate: * The scheduled sessions will be heavily attended by the community at large. This often includes those who are just curious, or those who want to make sure that their voice is heard. These sessions should be reserved for those topics which have the most external influence or are the most dependent on other projects. * The meetup will be at the end of the week so at the end of it, we can't then go to any other meetups and ask for things / participate in those design activities. This reinforces that scheduled session time should be focused on things that are externally focused so that we can take the result of those discussions into any of the sessions that are after. * The Ops Summit is Wendesday/Thursday [3], which overlaps with these sessions. I am keenly interested in gathering more contribution from those already operating and deploying OpenStack. It can go both ways, but I think it might make sense to have more ops-centric topics discussed on Friday, when those participants might not be fully wrapped up in the ops sessions. If we can all agree on those points, given the current topics, I think our scheduled sessions should target at least (but not limited to): * Cinder + CEPH * Layer 3 segmentation I think those might fit into 40 minutes, as long as we hash some things out here on the mailing list first. Cinder + CEPH is really just a check-in to make sure we're on track to providing it. Layer 3, I've had discussions with Ironic and Neutron people and I think we have a plan, but I wanted to present it in the open and discuss the short term goals to see if it satisfies what users may want for the Kilo time frame. So, I would encourage you all to look at the etherpad, and expand on topics or add more, and then reply to this thread with ideas for how best to use our precious time together. [1] http://kilodesignsummit.sched.org/overview/type/tripleo [2] https://etherpad.openstack.org/p/kilo-tripleo-summit-topics [3] http://kilodesignsummit.sched.org/overview/type/ops+summit ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Summit scheduling - using our time together wisely.
On 10/20/2014 04:34 PM, Ben Nemec wrote: I guess my only concern would be whether either of those things are contentious (both sound like must-do's at some point) and whether there is anything on either topic that requires f2f conversation to resolve. There's a spec out for Cinder HA already (https://review.openstack.org/#/c/101237/) that seems to have at least general support from everyone, and it's not clear to me that the L3 one can be resolved by us. It sounds like we need Nova and Neutron changes for that. Of course, if we can get some Nova and Neutron folks to commit to attending that session then I could see that being helpful. In general both of those topics on the etherpad are a little light on details, so I'd personally like to see some more specifics on what we'd be talking about. hi, agreed let me add some more comments here as a start. My plan for the Cinder HA session was to start with what we have today and compare it with what we propose in the spec. The spec indeed is currently 'on pause' because of issues affecting some backend drivers (Ceph included) when these are deployed in some active/active configuration. Cinder folks have/are working on it and will have a session about their new State Machine [1] which should help in this regard, if not fix it entirely. I'm planning to join their session before having ours, so we can sync up our planning with Cinder people and update the spec, hopefully for its final revision, jointly. 1. https://etherpad.openstack.org/p/kilo-cinder-summit-topics -- Giulio Fidente GPG KEY: 08D733BA | IRC: giulivo ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Summit scheduling - using our time together wisely.
I guess my only concern would be whether either of those things are contentious (both sound like must-do's at some point) and whether there is anything on either topic that requires f2f conversation to resolve. There's a spec out for Cinder HA already (https://review.openstack.org/#/c/101237/) that seems to have at least general support from everyone, and it's not clear to me that the L3 one can be resolved by us. It sounds like we need Nova and Neutron changes for that. Of course, if we can get some Nova and Neutron folks to commit to attending that session then I could see that being helpful. In general both of those topics on the etherpad are a little light on details, so I'd personally like to see some more specifics on what we'd be talking about. -Ben On 10/16/2014 03:14 PM, Clint Byrum wrote: The format has changed slightly this summit, to help encourage a more collaborative design experience, rather than rapid fire mass-inclusion summit sessions. So we have two 40-minute long slots, and one whole day of contributor meetup.[1] Our etherpad topics page has received quite a few additions now [2], and so I'd like to hear thoughts on what things we want to talk about in the meetup versus the sessions. A few things I think we should stipulate: * The scheduled sessions will be heavily attended by the community at large. This often includes those who are just curious, or those who want to make sure that their voice is heard. These sessions should be reserved for those topics which have the most external influence or are the most dependent on other projects. * The meetup will be at the end of the week so at the end of it, we can't then go to any other meetups and ask for things / participate in those design activities. This reinforces that scheduled session time should be focused on things that are externally focused so that we can take the result of those discussions into any of the sessions that are after. * The Ops Summit is Wendesday/Thursday [3], which overlaps with these sessions. I am keenly interested in gathering more contribution from those already operating and deploying OpenStack. It can go both ways, but I think it might make sense to have more ops-centric topics discussed on Friday, when those participants might not be fully wrapped up in the ops sessions. If we can all agree on those points, given the current topics, I think our scheduled sessions should target at least (but not limited to): * Cinder + CEPH * Layer 3 segmentation I think those might fit into 40 minutes, as long as we hash some things out here on the mailing list first. Cinder + CEPH is really just a check-in to make sure we're on track to providing it. Layer 3, I've had discussions with Ironic and Neutron people and I think we have a plan, but I wanted to present it in the open and discuss the short term goals to see if it satisfies what users may want for the Kilo time frame. So, I would encourage you all to look at the etherpad, and expand on topics or add more, and then reply to this thread with ideas for how best to use our precious time together. [1] http://kilodesignsummit.sched.org/overview/type/tripleo [2] https://etherpad.openstack.org/p/kilo-tripleo-summit-topics [3] http://kilodesignsummit.sched.org/overview/type/ops+summit ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] Summit scheduling - using our time together wisely.
Clint Byrum wrote: * The Ops Summit is Wendesday/Thursday [3], which overlaps with these sessions. I am keenly interested in gathering more contribution from those already operating and deploying OpenStack. It can go both ways, but I think it might make sense to have more ops-centric topics discussed on Friday, when those participants might not be fully wrapped up in the ops sessions. The Ops Summit is actually on Monday and Thursday. Not on Wednesday. You were wrong on the Internet. -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [TripleO] Summit scheduling - using our time together wisely.
The format has changed slightly this summit, to help encourage a more collaborative design experience, rather than rapid fire mass-inclusion summit sessions. So we have two 40-minute long slots, and one whole day of contributor meetup.[1] Our etherpad topics page has received quite a few additions now [2], and so I'd like to hear thoughts on what things we want to talk about in the meetup versus the sessions. A few things I think we should stipulate: * The scheduled sessions will be heavily attended by the community at large. This often includes those who are just curious, or those who want to make sure that their voice is heard. These sessions should be reserved for those topics which have the most external influence or are the most dependent on other projects. * The meetup will be at the end of the week so at the end of it, we can't then go to any other meetups and ask for things / participate in those design activities. This reinforces that scheduled session time should be focused on things that are externally focused so that we can take the result of those discussions into any of the sessions that are after. * The Ops Summit is Wendesday/Thursday [3], which overlaps with these sessions. I am keenly interested in gathering more contribution from those already operating and deploying OpenStack. It can go both ways, but I think it might make sense to have more ops-centric topics discussed on Friday, when those participants might not be fully wrapped up in the ops sessions. If we can all agree on those points, given the current topics, I think our scheduled sessions should target at least (but not limited to): * Cinder + CEPH * Layer 3 segmentation I think those might fit into 40 minutes, as long as we hash some things out here on the mailing list first. Cinder + CEPH is really just a check-in to make sure we're on track to providing it. Layer 3, I've had discussions with Ironic and Neutron people and I think we have a plan, but I wanted to present it in the open and discuss the short term goals to see if it satisfies what users may want for the Kilo time frame. So, I would encourage you all to look at the etherpad, and expand on topics or add more, and then reply to this thread with ideas for how best to use our precious time together. [1] http://kilodesignsummit.sched.org/overview/type/tripleo [2] https://etherpad.openstack.org/p/kilo-tripleo-summit-topics [3] http://kilodesignsummit.sched.org/overview/type/ops+summit ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
