<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 22, 2015 at 4:06 PM, Duan, Li-Gong (Gary@HPServers-Core-OE-PSC) <span dir="ltr"><<a href="mailto:li-gong.duan@hp.com" target="_blank">li-gong.duan@hp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi Angus,<u></u><u></u></span></p><span class="">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">> We are currently fleshing out a spec for Mistral resource types that should do<br>
> what you suggest above: <a href="https://review.openstack.org/#/c/143989/12/specs/kilo/mistral-resources.rst" target="_blank">
https://review.openstack.org/#/c/143989/12/specs/kilo/mistral-resources.rst</a><u></u><u></u></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">> (see the example on line 108).<u></u><u></u></p>
</span><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thank you for provide this info.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Mistral seems to provide workflow/workbook functions which OpenStack lacks.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Will Mistral will go into OpenStack or have it become an openstack integrated or incubated project?</span></p></div></div></blockquote><div><br></div><div>Hopefully!<br><br></div><div>-Angus<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link="blue" vlink="purple" lang="EN-US"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Gary<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> Angus Salkeld [mailto:<a href="mailto:asalkeld@mirantis.com" target="_blank">asalkeld@mirantis.com</a>]
<br>
<b>Sent:</b> Wednesday, January 21, 2015 8:00 AM<br>
<b>To:</b> Duan, Li-Gong (Gary@HPServers-Core-OE-PSC)<br>
<b>Cc:</b> Steven Hardy; <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a></span></p><div><div class="h5"><br>
<b>Subject:</b> Re: [Openstack] [Heat] Heat supports OpenStack operation<u></u><u></u></div></div><p></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<p class="MsoNormal">On Tue, Jan 20, 2015 at 5:54 PM, Duan, Li-Gong (Gary@HPServers-Core-OE-PSC) <<a href="mailto:li-gong.duan@hp.com" target="_blank">li-gong.duan@hp.com</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">Hi Steven,<br>
<br>
Thanks for your explanation on Heat.<br>
<br>
> -----Original Message-----<br>
> From: Steven Hardy [mailto:<a href="mailto:shardy@redhat.com" target="_blank">shardy@redhat.com</a>]<br>
> Sent: Friday, January 16, 2015 5:12 PM<br>
> To: Duan, Li-Gong (Gary@HPServers-Core-OE-PSC)<br>
> Cc: <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
> Subject: Re: [Openstack] [Heat] Heat supports OpenStack operation<br>
><br>
> On Fri, Jan 16, 2015 at 08:34:47AM +0000, Duan, Li-Gong (Gary@HPServers-<br>
> Core-OE-PSC) wrote:<br>
> > Does Heat support executing an OpenStack operation, such as migrating<br>
> an<br>
> > Nova instance, powering off a Nova instance?<br>
><br>
> We call state changes which don't affect the definition of the stack an<br>
> "action", and we only support suspend and resume at present (e.g heat<br>
> action-suspend <stack name>)<br>
<br>
It does make sense in that Heat centers around stack and does a great job<br>
In stack operation.<br>
<br>
> It may be possible to add support for more actions (until now nobody has<br>
> asked for them), but note it only really makes sense to drive such actions via<br>
> heat when dependencies/ordering are important.<br>
<br>
> For example, when suspending then resuming a stack containing a<br>
> WebServer instance and a DatabaseServer instance, you want<br>
> DatabaseServer to be resumed before WebServer (same order as on stack<br>
> create)<br>
><br>
> So, it might make sense to have an action which can power-off a whole stack,<br>
> turning off each nova node in the right order (you could write a little script<br>
> which does the same thing quite easily though..).<br>
<br>
It is an easy job to write a script to implement such actions as turning off each<br>
Nova node. But I would like to figure out a more elegant way to do it, for<br>
example, automatically turning off each Nova node at a specified condition.<br>
This can be implemented by using Ceilometer::Alarm to implement triggering<br>
this operation, but it seems that there is no appropriate place/component to<br>
implement the action (say, turning off each nova node). That's the reason why<br>
I want to see whether Heat can supports such operations.<u></u><u></u></p>
</blockquote>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">We are currently fleshing out a spec for Mistral resource types that should do<br>
what you suggest above: <a href="https://review.openstack.org/#/c/143989/12/specs/kilo/mistral-resources.rst" target="_blank">
https://review.openstack.org/#/c/143989/12/specs/kilo/mistral-resources.rst</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">(see the example on line 108).<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">-Angus<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal"><br>
> It probably doesn't make much sense for heat to support things like<br>
> migrating an instance, since it's an operation which isn't scoped to the stack<br>
> and it's dependencies, it's likely an operator wants to migrate a workload off<br>
> a specific compute node, which is something Heat has no visibility of at all.<br>
><br>
> > I know currently Heat does a good job on launching cloud cluster or<br>
> > application, such as deploying a Nova instance with specified network<br>
> > configuration, but not sure how to control(not launch or delete) a Nova<br>
> > instance or cinder volume.<br>
><br>
> Right now, the easiest answer is write a little script which uses information<br>
> from heat (e.g to get the UUID's for the resources you want to<br>
> control) then e.g calls nova.<br>
<br>
As mentioned above, the basic idea is to trigger a specified set of operations<br>
once a specified condition is reached. In this case, monitoring the condition<br>
and trigger action can be implemented with Ceilometer::Alarm, but I want to<br>
see whether it is possible to implement the set of operations in Heat template.<br>
<br>
Considering that Heat is dealing with sets of resources(stack), I am wondering<br>
whether it can deal with sets of operations, too.<br>
<br>
> > If Heat does not support these OpenStack operation, what is the best<br>
> Heat<br>
> > way if we want to execute some operations, such as powering off a Nova<br>
> > instance, in Heat template?<br>
><br>
> As mentioned above, these lifecycle operations affect the stack state, but<br>
> not it's definition, so it probably doesn't make sense to expose actions like<br>
> powering off an instance in the heat template.<br>
<br>
Now I understand that it doesn't make much sense to implement operation set<br>
in heat template and I need to figure other way to implement the set of<br>
operations.<br>
<br>
Regards,<br>
Gary<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><br>
_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><u></u><u></u></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div></div></div>
</div>
</div>
</blockquote></div><br></div></div>