<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><br>Thanks so much for your commits.<div><br><div>> Date: Wed, 4 Jun 2014 14:39:30 -0400<br>> From: zbitter@redhat.com<br>> To: openstack-dev@lists.openstack.org<br>> Subject: Re: [openstack-dev] [heat] Resource action API<br>> <br>> On 04/06/14 03:01, yang zhang wrote:<br>> > Hi all,<br>> > Now heat only supports suspending/resuming a whole stack, all the<br>> > resources of the stack will be suspended/resumed,<br>> > but sometime we just want to suspend or resume only a part of resources<br>> <br>> Any reason you wouldn't put that subset of resources into a nested stack <br>> and suspend/resume that?</div><div><br></div><div> I think that using nested-stack is a little complicated, and we can't build a nested-stack</div><div><span style="font-size: 12pt;">for each resource, hope this bp could make it easier. </span></div><div><span style="font-size: 12pt;"> </span></div><div>> <br>> > in the stack, so I think adding resource-action API for heat is<br>> > necessary. this API will be helpful to solve 2 problems:<br>> <br>> I'm sceptical of this idea because the whole justification for having <br>> suspend/resume in Heat is that it's something that needs to follow the <br>> same dependency tree as stack delete/create.<br>> </div><div>> Are you suggesting that if you suspend an individual resource, all of <br>> the resources dependent on it will also be suspended?</div><div><br></div><div> I thought about this, and I think just suspending an individual resource <span style="font-size: 12pt;">without </span><span style="font-size: 12pt;">dependent</span><span style="font-size: 12pt;"> </span></div><div><span style="font-size: 12pt;">is ok, now the resources that can be suspended are very few, and almost all of those resources</span></div><div><span style="font-size: 12pt;">(Server, alarm, user, etc) could </span><span style="font-size: 12pt;">be suspended </span><span style="font-size: 12pt;">individually.</span></div><div><br>> <br>> > - If we want to suspend/resume the resources of the stack, you need<br>> > to get the phy_id first and then call the API of other services, and<br>> > this won't update the status<br>> > of the resource in heat, which often cause some unexpected problem.<br>> <br>> This is true, except for stack resources, which obviously _do_ store the <br>> state.<br>> </div><div>> > - this API could offer a turn on/off function for some native<br>> > resources, e.g., we can turn on/off the autoscalinggroup or a single<br>> > policy with<br>> > the API, this is like the suspend/resume services feature[1] in AWS.<br>> <br>> Which, I notice, is not exposed in CloudFormation.</div><div><br></div><div><div> I found it on AWS web, It seems a auotscalinggroup feature, this may be not</div><div> exposed in CloudFormation, but I think it's really a good idea.</div><div><br></div>> <br>> > I registered a bp for it, and you are welcome for discussing it.<br>> > https://blueprints.launchpad.net/heat/+spec/resource-action-api<br>> <br>> Please propose blueprints to the heat-specs repo:<br>> http://lists.openstack.org/pipermail/openstack-dev/2014-May/036432.html<br>> </div><div><br></div><div>I'm sorry for it, I didn't notice the mail, and I will do it soon.</div><div><br>> thanks,<br>> Zane.<br>> <br><br></div></div><div>Regards.</div><div>Zhang Yang</div> </div></body>
</html>