[openstack-dev] [TripleO] Summit scheduling - using our time together wisely.

Clint Byrum clint at fewbar.com
Mon Oct 27 19:59:40 UTC 2014


Excerpts from Ben Nemec's message of 2014-10-27 11:39:31 -0700:
> 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.
> 

Regardless of the changes that need to happen outside TripleO's
projects, we will have new things to configure, and new user interface
elements to discuss in Tuskar. I also want to check in on the status of
any changes we do need to drive. I want to use the scheduled sessions
for this so that anyone from those teams can come and comment, or
users/operators can come to understand how the change needs to percolate
through the rest of OpenStack.

> > 
> > * 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.
>

I think that's exactly what I'd like to see: the summary of what you
wrote about. This is for public dissemination and also for Q&A. We are
crowd-sourcing ideas in this context, not really putting together design
elements. I mostly want to make sure people who have tried it or are
interested in trying it can get connected with you and the rest of the
team in this context. "Embrace the beta testers" basically.

> >  - 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.
>

Yes, they all need to have deeper discussions on Friday. What I want to
do here is to have the people interested and responsible in these tool
sets stand up, introduce themselves, state clearly what their project
is trying to accomplish, and that is all. This way interested parties
can engage with these individuals and we can come to Friday ready to
work together on the topics that are most urgent and that have the
broadest appeal.



More information about the OpenStack-dev mailing list