|Zane Bitter||Oct 23, 2012 10:46 am|
|Subject:||[Openstack] Heat version 7 released|
|From:||Zane Bitter (zbit...@redhat.com)|
|Date:||Oct 23, 2012 10:46:28 am|
Good news, everyone! The Heat developers are pleased to announce a new version (v7) of Heat.
You may remember Heat as the project that allows you to launch AWS CloudFormation templates on OpenStack. If you're not already familiar with it, CloudFormation is a programmable interface and templating system for orchestrating multiple cloud applications.
This version adds an OpenStack-native ReST API, so you'll never need to deal with RPC again. But rest assured (uh, no pun intended) that we intend to continue to maintain and support the existing CloudFormation-compatible API indefinitely.
Try it out on Fedora 17:
Or Ubuntu 12.04:
What's new in version 7:
* An OpenStack-native ReST API - A platform for future innovation, unique to OpenStack. - Currently, support is limited to stack operations - support for Resources and Events is coming soon - Documentation at https://github.com/heat-api/heat/blob/master/docs/api.md#readme
* CloudWatch-compatible Metric Collection - Running instances now report their metrics via Heat's CloudWatch-compatible API - Metric collection is now secure (authenticated/signed)
* Fixes for integration with the Folsom versions of Keystone and Glance
* A CLI option for fetching templates from Swift
* Unit tests - More! Better! Faster!
* heat-keystone-setup handles upgrades
* Numerous bug fixes and enhancements
Note that the implementation of cfn-push-stats has changed in this version, so you will need to rebuild your JEOS images using the latest version of heat-jeos. Prebuilt images will be available as soon as we find somebody with write access to that repo.
Also note that if you wish to use the features of the CloudWatch-compatible API (this means any templates that use HA or Autoscaling), you will need a firewall rule to allow instances access to that API (previously only access to heat-metadata was required). See the Getting Started guide for details.
Keystone endpoints have also changed, so if you are upgrading from an existing version of heat, be sure to re-run the bin/heat-keystone-setup script.