<div dir="ltr">This might be related but we have a talk/demo about recursive containers on Thursday which allows you to build complex app topologies from simpler ones (like lego blocks). The idea is old, is way-pre-HEAT (Boston summit) but this current talk is more of how to visually/interactively provision such topologies with openstack (and quantum). <div>
<br></div><div>debo</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 2, 2013 at 4:23 PM, 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"><div class="HOEnZb"><div class="h5">On 02/04/13 22:46 +0000, Adrian Otto wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
Rackspace has resourced two dedicated development teams for the sole purpose of contributing new features and capabilities to OpenStack's HEAT project. We are very excited, and would like to share with you what we plan to design and contribute together with you:<br>
<br>
1) Open API & DSL - This allows templates to be agnostic to the underlying cloud and encourages community contribution for the betterment of all users across all cloud providers. We want a solution that does not depend on semantics from any single service provider. We think there is a way for HEAT to work equally well with CloudFormation templates, and a completely open template format as well.<br>
<br>
2) Declarative Model - Although CloudFormation Templates were designed to be declarative, in practice the templates are very imperative artifacts (for example, those that embed shell scripts). Templates that are expressed using a declarative approach are compact, simple, and portable between clouds that have different services available. We want the cloud implementation specific details to be handled by modules, not wired into the templates. Declarative modeling encourages broad contribution from the user base to improve the overall community library of available solutions. While modeling may be easy to implement, they are more difficult to expand to support generic cloud portable use cases.<br>
<br>
3) Modular Implementation - We want HEAT to be modular in a way that's consistent with the level of modularity offered in Nova, Quantum, Cinder and others where a common, extendable API is offered and a variety of extensions may be added for various back-end services and features. We want to keep the architecture as simple as possible while allowing individual cloud operators to add features and capabilities in a way that keeps templates crisp and portable.<br>
<br>
4) Auto-Scale Implementation - The solution will allow deployments to scale up and down dynamically based on demand. We want to design and implement this with you. We have considerable experience and resources to bring with us. We have a dedicated team to contribute solutions here.<br>
<br>
We look forward to discussing more with you at the Summit in Portland. Leaders from each of our new teams will be there ready to work with you on implementation details.<br>
</blockquote>
<br></div></div>
Welcome to the Heat community!<br>
<br>
Great news, it will be good to see you at summit.<br>
<br>
-Angus<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Regards,<br>
<br>
Adrian Otto<br>
</blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>-Debo~<br>
</div>