<html><body>
<p><tt><font size="2">Clint Byrum <clint@fewbar.com> wrote on 10/11/2013 12:40:19 PM:<br>
<br>
> From: Clint Byrum <clint@fewbar.com></font></tt><br>
<tt><font size="2">> To: openstack-dev <openstack-dev@lists.openstack.org></font></tt><br>
<tt><font size="2">> Date: 10/11/2013 12:43 PM</font></tt><br>
<tt><font size="2">> Subject: Re: [openstack-dev] [Heat] HOT Software orchestration <br>
> proposal for workflows</font></tt><br>
<tt><font size="2">> <br>
> > 3. Ability to return arbitrary (JSON-compatible) data structure from config<br>
> > application and use attributes of that structure as an input for other<br>
> > configs<br>
> <br>
> Note that I'd like to see more use cases specified for this ability. The<br>
> random string generator that Steve Baker has put up should handle most<br>
> cases where you just need passwords. Generated key sharing might best<br>
> be deferred to something like Barbican which does a lot more than Heat<br>
> to try and keep your secrets safe.<br>
</font></tt><br>
<tt><font size="2">I had seen a deployment scenario that needed more than random string generator. It was during the deployment of a system that has clustered application servers, i.e., a cluster of application server nodes + a cluster manager node. The deployment progresses by all the VMs (cluster-manager and cluster-nodes) starting concurrently. Then the cluster-nodes wait for the cluster-manager to send them data (xml) to configure themselves. The cluster-manager after reading its own config file, generates config-data for each cluster-node and sends it to them. </font></tt><br>
<br>
<tt><font size="2">Thanks,</font></tt><br>
<tt><font size="2">LN</font></tt><br>
</body></html>