Open Stack

On May 1, 2013, at 12:00 AM, Doug Davis <dug at us.ibm.com<mailto:dug at us.ibm.com>> wrote:


+1
I tend to look at this blueprint from a more abstract level and so to me this is really just asking for a set of Openstack APIs to be invoked automatically.  That really isn't that fundamentally different than what a user of Heat will be trying to do - execute a set of Openstack APIs.  Whether its to stand-up an application or to perform a backup of a VM, the infrastructure to deal with the execution of those APIs shouldn't really know or care.  Especially when you consider that these set of operations could very well not be trivial in nature (ie. blindly do this, then this, then this...) but rather could require some "smarts" to them (e.g. conditional execution of certain steps), and at that point the problem become much harder than just a cron job of VM.createSnapshot().  I would hope that Heat would be able to help with these types of usecases.

Hey Doug,

To be honest, I'm a little confused by this mentality.  An absurd conclusion I could reach (if I was trying to make a point) to this is that there is no API to openstack except Heat, and I don't think that's what we want.

I don't think that you should be required to have heat deployed, or require users to use a heat template just to take a snapshot manually, and so I don't think its a foregone conclusion that you would use heat for scheduling - in particular given that heat has no concept of timing.  In addition, my gut says that  If there is a reason for multiple services to do things at a configured time, lets have a scheduling service that can, in the simple case, take a snapshot of a server, and in a more complex case pause the instance, snapshot it, and move on.

Gabe

  Now, time-based execution instead of just user initiation execution might be a twist, but I see no reason why that couldn't be added to Heat if its not already there.

thanks
-Doug
________________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug at us.ibm.com<mailto:dug at us.ibm.com>
The more I'm around some people, the more I like my dog.

<graycol.gif>Russell Bryant ---04/30/2013 05:49:28 PM---Greetings, The following blueprint was proposed for the havana series:

From: Russell Bryant <rbryant at redhat.com<mailto:rbryant at redhat.com>>
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>,
Date: 04/30/2013 05:49 PM
Subject: [openstack-dev] [Nova][Heat] scheduled-images blueprint

________________________________



Greetings,

The following blueprint was proposed for the havana series:

   https://blueprints.launchpad.net/nova/+spec/scheduled-images

Based on the current design, I think the nova part of this needs to be
deferred.  It does not seem appropriate to add an API extension that
talks to a service that is not an integrated project, or at least incubated.

Beyond that, I'm curious about the choice to implement this as a new
service.  I definitely agree that this is not something that should be
implemented inside of Nova.  However, I wonder if it makes sense as a
feature in Heat.  It seems like an orchestration feature.

Thoughts?

--
Russell Bryant

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto: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<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130501/0aacffd5/attachment.html>