<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/15/2013 02:48 PM, Christopher
Armstrong wrote:<br>
</div>
<blockquote
cite="mid:CAPkRfUSdf379txEqpvWxy-JuGwhD=Q5L7U9QfefO4eepk0nHpA@mail.gmail.com"
type="cite">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">The thinking
here was:<br>
- this makes the new config stuff easier to scale (config get
applied<br>
per scaling stack)<br>
- you can potentially place notification resources in the
scaling<br>
stack (think marconi message resource - on-create it sends a<br>
message)<br>
- no need for a launchconfig<br>
- you can place a LoadbalancerMember resource in the scaling
stack<br>
that triggers the loadbalancer to add/remove it from the lb.<br>
<br>
I guess what I am saying is I'd expect an api to a nested stack.<span
class="HOEnZb"><font color="#888888"><br>
<br>
</font></span></blockquote>
<div><br>
</div>
<div>Well, what I'm thinking now is that instead of "resources" (a
mapping of resources), just have "resource", which can be the
template definition for a single resource. This would then allow
the user to specify a Stack resource if they want to provide
multiple resources. How does that sound?</div>
</blockquote>
As long as this stack can be specified by URL *or* as an inline
template I would be happy.<br>
</body>
</html>