On 18/02/14 14:19 +0000, Shaunak Kashyap wrote:
Thanks Angus and Devdatta. I think I understand.
Angus -- what you said seems to mirror the Heroku CLI usage: a) User runs "app/plan
create" (to create the remote repo), then b) user runs "git push ..." (which pushes
the code to the remote repo and creates 1 assembly, resulting in a running application). If this is
the intended flow for the user, it makes sense to me.
Just to be clear, I am not totally sure we are going to glue git repo
generation to create plan (it *could* be part of create assembly).
One follow up question: under what circumstances will the user need to explicitly run
"assembly create"? Would it be used exclusively for adding more assemblies to
an already running app?
If you are not using the git-push mechanism, but the git-pull.
Here you have your own repo (say on github) and there is not
a git-repo-generation phase.
-Angus
Thanks,
Shaunak
________________________________________
From: Angus Salkeld [angus.salk...@rackspace.com]
Sent: Monday, February 17, 2014 5:54 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [solum] Question about solum-minimal-cli BP
On 17/02/14 21:47 +0000, Shaunak Kashyap wrote:
Hey folks,
I was reading through
https://wiki.openstack.org/wiki/Solum/FeatureBlueprints/CLI-minimal-implementation
and have a question.
If I’m understanding “app create” and “assembly create” correctly, the user
will have to run “app create” first, followed by “assembly create” to have a
running application. Is this correct? If so, what is the reason for “app
create” not automatically creating one assembly as well?
On that page it seems that "app create" is the same as "plan create".
The only reason I can see for seperating the plan from the assembly is
when you have "git-push".
Then you need to have something create the git repo for you.
1 plan create (with a reference to a git-push requirement) would create
the remote git repo for you.
2 you clone and populate the repo with your app code
3 you push, and that causes the assembly create/update.
Adrian might want to correct my here tho'
-Angus
Thanks,
Shaunak
_______________________________________________
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
_______________________________________________
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
