Open Stack

Hi, we've got this summit session planned -
http://summit.openstack.org/cfp/details/428 which is really about
https://etherpad.openstack.org/p/heat-workflow-vs-convergence

We'd love feedback and questions - this is a significant amount of
work, but work I (and many others based on responses so far) believe
it is needed to really take Heat to users and ops teams.

Right now we're looking for both high and low level design and input.

If you're an operator/user/developer of/with/around heat - please take
a couple of minutes to look - feedback inline in the etherpad, or here
on the list - whatever suits you.

The basic idea is:
 - no changes needed to the heat template language etc
 - take a holistic view and fix the system's emergent properties by
using a different baseline architecture within it
 - ???
 - profit!

This can be constrasted with many other existing attempts to design
solutions which relied on keeping the basic internals of heat as-is
and just tweaking things - an approach we don't believe will work -
the issues arise from the current architecture, not the quality of the
code (which is fine).

Cheers,
Lifeless, Spamaps and Radix

-- 
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud