We (the TripleO developers) use Heat as part of TripleO to manage small (40 nodes) clouds for TripleO. This means that we're using Heat to manage our bare metal nodes which are in turn managed by nova+ironic.
For the most part it is only used to bring up new nodes or change parameters (not something we do often). For that purpose, it works fine. Icehouse Heat lacks some really nice features that came out in Juno, not the least of which being that Juno's Heat can resume from failed operations where Icehouse cannot. Also, my employer, HP, is shipping Heat as part of the Helion distribution of OpenStack. I'm not certain if anybody is in full production using the Heat in Helion just yet, as it only recently released. I also know that Rackspace has been running some kind of Heat public beta/alpha/something for a while, so it might be worth asking them about their Heat. Excerpts from Ari Rubenstein's message of 2014-12-15 15:10:50 -0800: > Hi there, > My name is Ari Rubenstein, and I'm new to the list. I've been researching > Heat. I was wondering if anyone has direct experience or links to how > customers are Heat orchestration in the real world. > Use cases? Experiences? Best practices? Gotchas? > I'm working with a customer on an Icehouse based cluster. They're wondering > if Heat is ready for production or should be considered beta. I've heard > good things about Heat, but the customer is cautious. > Thanks in advance, > - Ari _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
