Open Stack

I've been told that the original subject of this broke some mail
clients. Hopefully this gets past their brokenness and you can all see
the content now. :)

Excerpts from Clint Byrum's message of 2017-02-17 10:16:05 -0800:
> Hello, I'm looking forward to seeing many of you next week in Atlanta.
> We're going to be working on Arch-WG topics all day Tuesday, and if
> you'd like to join us for that in general, please add your topic here:
> 
> https://etherpad.openstack.org/p/ptg-architecture-workgroup
> 
> I specifically want to call out an important discussion session for one
> of our active work streams, nova-compute-api:
> 
> https://review.openstack.org/411527
> https://review.openstack.org/435555
> 
> At this point, we've gotten a ton of information from various
> contributors, and I want to thank everyone who commented on 411527 with
> helpful data. I'll be compiling the data we have into some bullet points
> which I intend to share on the projector in an etherpad[1], and then invite
> the room to ensure the accuracy and completeness of what we have there.
> I grabbed two 30-minute slots in Macon for Tuesday to do this, and I'd
> like to invite anyone who has thoughts on how nova-compute interacts to
> join us and participate. If you will not be able to attend, please read
> the documents and comments in the reviews above and fill in any information
> you think is missing on the etherpad[1] so we can address it there.
> 
> [1] https://etherpad.openstack.org/p/arch-wg-nova-compute-api-ptg-pike
> 
> Once we have this data, I'll likely spend a small amount of time grabbing people from
> each relevant project team on Wednesday/Thursday to get a deeper understanding of some
> of the pieces that we talk about on Tuesday.
> 
> >From that, as a group we'll produce a detailed analysis of all the ways
> nova-compute is interacted with today, and ongoing efforts to change
> them. If you are interested in this please do raise your hand and come
> to our meetings[2] as my time to work on this is limited, and the idea
> for the Arch-WG isn't "Arch-WG solves OpenStack" but "Arch-WG provides
> a structure by which teams can raise understanding of architecture."
> 
> [2] https://wiki.openstack.org/wiki/Meetings/Arch-WG
> 
> Once we've produced that analysis, which we intend to land as a document
> in our arch-wg repository, we'll produce a set of specs in the appropriate
> places (likely openstack-specs) for how to get it to where we want to
> go.
> 
> Also, speaking of the meeting -- Since we'll all be meeting on Tuesday
> at the PTG, the meeting for next week is cancelled.