It feels like Heat serves some overlapping purposes, though it adds more orchestration than I can get with Chef out of the box today. Would the Heat template really only serve to document run lists?
Using Chef with OpenStack, what would encourage me to use Heat templates?
302 views Asked by danehammer At
1
Chef has drifted into the same functional space as heat with its new "provisioning" feature (formerly known as chef metal):
I would suggest trying both. Chef provisioning is more chef friendly and designed to work across multiple cloud technologies, whereas Heat is specific to Openstack. Ultimately this is what will influence your decision I think.