savanna-all team mailing list archive

[Nadezhda Privalova <nprivalova@xxxxxxxxxxxx>]

Jon,

Thank you so much for reviewing the documentation.

Regarding the "Savanna - Plugins interoperability" section:

- Is step 3 concerning the plugin specific configuration option?

Yes, you are right. I've updated the wiki and tried to describe it in more
details.

 - It looks like step 7 is concerning elasticity (add/remove).  Correct?
 If so, the next step (step 8) implies that in this instance, rather than
receiving a cluster object with already created VMs (as in the cluster
creation case), it is up to the plugin to actually launch the VMs?

Step 7 and 8 were about elasticity, right. But now we've decided to
postpone this feature for several weeks. So that's why I removed these
steps from wiki. As soon as our vision about scaling become formed I will
update wiki. And as to launching VMs - this is always Savanna's
responsibility. Plugin just asks Savanna to run VM.

By the way, you asked

         Though we had agreement on the list that a user_input would have a
reference to its associated config object, the documentation still
indicates a name and value attribute, rather than a config and value
attributes.

There was an error in docs. Thanks for pointing on this.

Nadya




On Wed, May 22, 2013 at 5:37 PM, Jon Maron <jmaron@xxxxxxxxxxxxxxx> wrote:

>
> On May 22, 2013, at 9:29 AM, Jon Maron <jmaron@xxxxxxxxxxxxxxx> wrote:
>
> Hi,
>
>   Thank you for posting this documentation.  I have a few questions:
>
>   Regarding the "Savanna - Plugins interoperability" section:
>
> - Is step 3 concerning the plugin specific configuration option?
> - It looks like step 7 is concerning elasticity (add/remove).  Correct?
>  If so, the next step (step 8) implies that in this instance, rather than
> receiving a cluster object with already created VMs (as in the cluster
> creation case), it is up to the plugin to actually launch the VMs?
>
>   Regarding the infrastructure request:
> - By the point update_cluster() is called, the cluster object is already
> populated with node groups that indicate the flavor, image and count.  In
> the API documentation you state that the plugin must specify the images for
> the vms?  Is your expectation that the user selection is wrong?
>
>
> Forget this second question:  I just realized that the image specification
> is up to the plugin.
>
>
>
> On May 21, 2013, at 1:06 PM, Ruslan Kamaldinov <rkamaldinov@xxxxxxxxxxxx>
> wrote:
>
>  Folks,
>
> We've updated  blueprint for pluggable mechanism:
>
> https://blueprints.launchpad.net/savanna/+spec/pluggable-cluster-provisioning
>
> Here is the direct link to the wiki page:
> https://wiki.openstack.org/wiki/Savanna/PluggableProvisioning
>
>
> It now has more details on the API, object mode, object lifecycle and
> workflows.
>
>
> Thanks,
> Ruslan
>  --
> Mailing list: https://launchpad.net/~savanna-all
> Post to     : savanna-all@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~savanna-all
> More help   : https://help.launchpad.net/ListHelp
>
>
>
>
> --
> Mailing list: https://launchpad.net/~savanna-all
> Post to     : savanna-all@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~savanna-all
> More help   : https://help.launchpad.net/ListHelp
>
>