<html><body>
<p><font size="2" face="sans-serif">+1</font><br>
<font size="2" face="sans-serif">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. </font><br>
<br>
<font size="2" face="sans-serif"> 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.<br>
<br>
thanks<br>
-Doug<br>
________________________________________________________<br>
STSM | Standards Architect | IBM Software Group<br>
(919) 254-6905 | IBM 444-6905 | dug@us.ibm.com<br>
The more I'm around some people, the more I like my dog.</font><br>
<br>
<img width="16" height="16" src="cid:1__=0ABBF1CDDF86BA0B8f9e8a93df938@us.ibm.com" border="0" alt="Inactive hide details for Russell Bryant ---04/30/2013 05:49:28 PM---Greetings, The following blueprint was proposed for the ha"><font size="2" color="#424282" face="sans-serif">Russell Bryant ---04/30/2013 05:49:28 PM---Greetings, The following blueprint was proposed for the havana series:</font><br>
<br>
<font size="1" color="#5F5F5F" face="sans-serif">From: </font><font size="1" face="sans-serif">Russell Bryant <rbryant@redhat.com></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">To: </font><font size="1" face="sans-serif">OpenStack Development Mailing List <openstack-dev@lists.openstack.org>, </font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Date: </font><font size="1" face="sans-serif">04/30/2013 05:49 PM</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Subject: </font><font size="1" face="sans-serif">[openstack-dev] [Nova][Heat] scheduled-images blueprint</font><br>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<tt><font size="2">Greetings,<br>
<br>
The following blueprint was proposed for the havana series:<br>
<br>
</font></tt><tt><font size="2"><a href="https://blueprints.launchpad.net/nova/+spec/scheduled-images">https://blueprints.launchpad.net/nova/+spec/scheduled-images</a></font></tt><tt><font size="2"><br>
<br>
Based on the current design, I think the nova part of this needs to be<br>
deferred. It does not seem appropriate to add an API extension that<br>
talks to a service that is not an integrated project, or at least incubated.<br>
<br>
Beyond that, I'm curious about the choice to implement this as a new<br>
service. I definitely agree that this is not something that should be<br>
implemented inside of Nova. However, I wonder if it makes sense as a<br>
feature in Heat. It seems like an orchestration feature.<br>
<br>
Thoughts?<br>
<br>
-- <br>
Russell Bryant<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
</font></tt><tt><font size="2"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></font></tt><tt><font size="2"><br>
<br>
</font></tt><br>
</body></html>