Integation with different OpenStack releases

Asked by Dmitry Klenov on 2013-03-14

Hi Folks,

We are going to use HEAT for VM configuration and therefore would like to get more data regarding HEAT applicability for different OpenStack versions.

Can you please clarify, which OpenStack releases are supported by current HEAT version and which of them will be supported by upcoming HEAT version for Grizzly? Will HEAT for Grizzly be backward-compatible with older OpenStack releases? We are mostly interested in Essex and Folsom.


Question information

English Edit question
OpenStack Heat Edit question
No assignee Edit question
Solved by:
Dmitry Klenov
Last query:
Last reply:
Revision history for this message
Clint Byrum (clint-fewbar) said :

Hi! Welcome to the wonderful world of Heat!

Openstack's Grizzly suite of releases includes Heat only as an incubated project. Havana, due in about 6 months, will have Heat fully integrated, and should include better documentation and more specifications and backward compatibility guarantees.

I recommend you join #heat on Freenode IRC for more realtime discussions

Revision history for this message
Dmitry Klenov (dklenov) said :

Hi Clint!

Thanks for the clarification. And what is the situation with existing OpenStack releases? Does HEAT support Essex and Folsom? And if it is targeted for Grizzly mostly, how much efforts would it require to make it work with Folsom release? What is your feeling regarding this?


Revision history for this message
Steven Dake (sdake) said :


Heat is released as a component of the larger OpenStack project - so a Heat version for Gizzly is meant to work with Grizzly components (only). This is what we fully support with backports for bug fixes.

That said, many of the heat developers use Folsom as their base development environment while using the upcoming Grizzly Heat software. Most things should work, with the exception of volumes and quantum integration. Volumes may not work because there is a dependency on cinder, and quantum in Folsom was not in a state that was usable by Heat. Also you will need to install oslo-config manually, as Grizzly's heat depends on that.

We are supportive of a forward compatibility model - ie: If you run on Grizzly, you can transition to Havana easily. It is hard to offer any guarantees in reverse since Heat will integrate to new APIs/features as they become available and these may not be backward compatible.

No idea on Essex.

Revision history for this message
Dmitry Klenov (dklenov) said :

Hi Steven,

Thanks a lot for your answer. It perfectly clarifies the situation.