Hi Adrian,
Thanks for creating https://etherpad.openstack.org/p/solum-demystified
I am really excited to see the examples. Especially cool is how
examples 2 and 3 demonstrate using a component ("solum_glance_id") created
as part of example 1.
Some questions/comments:
1) Summarizing the sequence of events just to make sure I understand them
correctly:
a) User selects a language pack and specifies its id in the plan file
b) User creates repo with the plan file in it.
After this the flow could be:
c.1) User uses solum cli to 'create' an application by giving reference to
the repo uri
c.1.1) Solum creates a plan resource
c.1.2) Solum model interpreter creates a Heat stack and does the rest of
the
things needed to create a assembly.
(The created plan resource does not play any part in assembly creation
as such.
Its only role is being a 'trackback' to track the plan from which the
assembly was created.)
or,
c.2) User uses solum cli to 'create/register' a plan by providing reference
to the repo uri.
c.2.1) Solum creates the plan resource.
c.2) User uses solum cli to 'create' an application by specifying the
created plan
resource uri
(In this flow, the plan is actively used).
2) Addition of new solum specific attributes in a plan specification is
interesting.
I imagine those can be contributed back as "Solum" profile to CAMP spec?
3) Model interpreter for generating Heat stack from a plan is a nice idea.
For all: Are there any recommended libraries for this?
4) Just to confirm, I assume that the api-spec-review etherpad
(https://etherpad.openstack.org/p/solum-api-spec-review),
is for fyi purpose only. If someone wants to know what is the current
thinking about API, they should
just look at the solum-demystified etherpad
(https://etherpad.openstack.org/p/solum-demystified)
Thanks,
Devdatta
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
