Open Stack

We had some recent discussions regarding the Heat mission statement and
came up with:

"To explicitly model the relationships between OpenStack resources of all
kinds; and to harness those models, expressed in forms accessible to both
humans and machines, to manage infrastructure resources throughout the
lifecycle of applications."

The ideas, iterations and some discussion is captured in this etherpad:

https://etherpad.openstack.org/heat-mission

If anyone has any remaining comments, please speak now, but I think most of
those involved in the discussion thus-far have reached the point of wishing
to declare it final ;)

Thanks,

Steve