<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">+1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Depending on the OS image being used it may be necessary to shutdown the GuestOS before taking the snapshot to get a recoverable image. That kind of logic
doesn’t belong in Nova.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Phil<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Doug Davis [mailto:dug@us.ibm.com]
<br>
<b>Sent:</b> 01 May 2013 05:00<br>
<b>To:</b> OpenStack Development Mailing List<br>
<b>Subject:</b> Re: [openstack-dev] [Nova][Heat] scheduled-images blueprint<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">+1</span><br>
<span style="font-size:10.0pt;font-family:"Arial","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.
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","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 | <a href="mailto:dug@us.ibm.com">dug@us.ibm.com</a><br>
The more I'm around some people, the more I like my dog.</span><br>
<br>
<img border="0" width="16" height="16" id="_x0000_i1025" src="cid:image001.gif@01CE4670.6B206650" alt="Inactive hide details for Russell Bryant ---04/30/2013 05:49:28 PM---Greetings, The following blueprint was proposed for the ha"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#424282">Russell
Bryant ---04/30/2013 05:49:28 PM---Greetings, The following blueprint was proposed for the havana series:</span><br>
<br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">From:
</span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">Russell Bryant <<a href="mailto:rbryant@redhat.com">rbryant@redhat.com</a>></span><br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">To: </span>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif"">OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>,
</span><br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Date:
</span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">04/30/2013 05:49 PM</span><br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Subject:
</span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">[openstack-dev] [Nova][Heat] scheduled-images blueprint</span><o:p></o:p></p>
<div class="MsoNormal">
<hr size="2" width="100%" noshade="" style="color:#8091A5" align="left">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<tt><span style="font-size:10.0pt">Greetings,</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
<tt>The following blueprint was proposed for the havana series:</tt><br>
<br>
<tt> <a href="https://blueprints.launchpad.net/nova/+spec/scheduled-images">https://blueprints.launchpad.net/nova/+spec/scheduled-images</a></tt><br>
<br>
<tt>Based on the current design, I think the nova part of this needs to be</tt><br>
<tt>deferred. It does not seem appropriate to add an API extension that</tt><br>
<tt>talks to a service that is not an integrated project, or at least incubated.</tt><br>
<br>
<tt>Beyond that, I'm curious about the choice to implement this as a new</tt><br>
<tt>service. I definitely agree that this is not something that should be</tt><br>
<tt>implemented inside of Nova. However, I wonder if it makes sense as a</tt><br>
<tt>feature in Heat. It seems like an orchestration feature.</tt><br>
<br>
<tt>Thoughts?</tt><br>
<br>
<tt>-- </tt><br>
<tt>Russell Bryant</tt><br>
<br>
<tt>_______________________________________________</tt><br>
<tt>OpenStack-dev mailing list</tt><br>
<tt><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a></tt><br>
<tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt><br>
<br>
</span><o:p></o:p></p>
</div>
</body>
</html>