Open Stack

Hi Clayton,

Thank you for creating these diagrams. They are a great starting point for discussions
around the git deploy blueprint.

Some questions/comments:

In both the diagrams, what do the arrows indicate? 
Data flow, control-flow, or some kind of ordering relationship?
Especially, the arrow from 'respond to client' to 'HEAT' box in the top diagram
is a bit confusing. Correct me if I am wrong, but my guess is that the meaning
of that arrow is, 'stack create' will happen after responding to client has happened.
Although, this may not be necessarily true (both those steps can happen in async manner).

Second, how do you envision tying together the two diagrams/high-level flows?
Specifically, once we have a built artifact (second diagram), how do we go about deploying it?

We could either have, build abstraction -> REST API -> deploy abstraction,
or, build abstraction -> deploy abstraction. What are your thoughts on this?

Best regards,
Devdatta


-----Original Message-----
From: "Adrian Otto" <adrian.otto at rackspace.com>
Sent: Wednesday, October 30, 2013 8:01pm
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [Solum] Separation of concerns for 0.1 git deploy blueprint

Clayton,

Thanks for adding the diagram illustrating the flow. I expect that "respond to client" may not be a synchronous flow, rather that if creation of a repo takes a while that the API may return a 202 Accepted, and the client can poll a status attribute to determine completion and learn the actual location of the repo created. So in that case "respond to client" also might mean "update async status". This will be particularly important in cases where an external SCM system is used (perhaps Github).

I agree that this will be a helpful reference to guide our upcoming interactive design sessions. I have created the first call for participation, which will also be separately announced:

https://wiki.openstack.org/wiki/Solum/BreakoutMeetings

Adrian

On Oct 30, 2013, at 2:45 PM, Clayton Coleman <ccoleman at redhat.com> wrote:

> In the IRC meeting yesterday [1] we discussed splitting the individual topics for the git deploy blueprint [2] into rough sub areas.  To help frame the abstractions we've been discussing I roughed out a flow based on two user inputs, REST API create and a git push and then tried to draw boxes around the related bits.  The abstractions roughly correspond to the potential areas that can be the focus of break out discussions (and if they don't a good discussion of why is always helpful).
> 
> Squiggly boxes are potential plugin points and/or strong responsibility boundaries.  Feedback desirable.
> 
> [1] http://irclogs.solum.io/2013/solum.2013-10-29-16.01.txt
> [2] https://wiki.openstack.org/wiki/Solum/FeatureBlueprints/GitIntegration#Flow_Boundaries
> 
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev