<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<br>
<div>
<div>On Jun 13, 2013, at 11:58 AM, Thomas Hervé <<a href="mailto:th@rackspace.com">th@rackspace.com</a>></div>
<div> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><br>
<br>
<div class="gmail_quote">On Thu, Jun 13, 2013 at 2:44 AM, Angus Salkeld <span dir="ltr">
<<a href="mailto:asalkeld@redhat.com" target="_blank">asalkeld@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 12/06/13 22:42 +0000, Randall Burt wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On Jun 12, 2013, at 5:06 PM, Christopher Armstrong <<a href="mailto:chris.armstrong@rackspace.com" target="_blank">chris.armstrong@rackspace.com</a><u></u><mailto:<a href="mailto:chris.armstrong@rackspace.com" target="_blank">chris.armstrong@<u></u>rackspace.com</a>>>
<div class="im"><br>
wrote:<br>
<br>
I believe the consensus is that the work on the new HOT format and underlying design changes is a prerequisite for the autoscaling work that Thomas and I are to do, so we'll definitely help with that. I'll let someone with a better understanding chime in about
that.<br>
<br>
I would like to have some more details around that dependency as well. Is there something specific we should be focused on around HOT that would facilitate easier Otter->Heat AS transition?<br>
<br>
</div>
</blockquote>
<br>
Seems odd that AS is dependant on the template format. I would have<br>
thought that you could just make a native resource type for the new<br>
autoscaler and we could start using it, then migrating the AWS style<br>
one over too. I agree the AWS autoscaling resource might not be able to<br>
make full use of the awesomeness of our new one but that's ok.<br>
</blockquote>
<div><br>
</div>
<div>It's not about making it dependent on the template format, but rather making independent of any template. Right now resources and stack are pretty tied together, and I'm hoping the new DSL will separate things up a bit. Otter doesn't have a template system
but drives resources directly via the API, and I think it'll be easier to see if it's possible once we move away from CFN, if it makes sense. We're still evaluating how that will work, though.</div>
</div>
</blockquote>
<div><br>
</div>
<div>I'm not sure how we'd separate resources and stacks, or if it even makes sense to. The stack describes the relationships between resources and provides the essential framework around orchestration. Even today you can query a stack's resources. There certainly
is a little work to do around exposing attributes/properties better there, but that's not a template thing. </div>
<div><br>
</div>
<div>WRT autoscale, it makes sense to me that the eventual goal would be to able to:</div>
<div><br>
</div>
<div>1. Via my template, define autoscale thresholds that kick off stack-updates. The template simply provides a mechanism to declare how I want to integrate autoscale with my infrastructure, no different that what we do for nova, swift, etc.</div>
<div><br>
</div>
<div>2. Use it independently of any template and provide my own thresholds and scaling rules via api calls and leverage my own custom scripts/images/orchestration logic.</div>
<div><br>
</div>
<div>Neither of these seem to have direct impact on the template structure other than any delta between today's scaling group's properties and attributes and what it will look like tomorrow.</div>
<br>
<blockquote type="cite">
<div class="gmail_quote">
<div>-- </div>
<div>THomas</div>
<div> </div>
</div>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>
</blockquote>
</div>
<br>
</body>
</html>