OpenStack Developer Summit: Heat Followup
Posted on April 23, 2013 by oubiwann

Folks are finally starting to recover from the OpenStack Developer Summit that was held in Portland, Oregon recently. All reports indicate that it was a truly phenomenal experience, record-breaking in many ways, and something that has inspired incredible enthusiasm within the community. And that's great news, since there's an enormous amount of work to be done this release ;-)
Of particular importance to many in the community is the work around maturing the autoscaling feature in OpenStack Heat. There was a fantastic session at the summit, facilitated by the bow-tied and most dapper Ken Wronkiewicz (his notes from the Summit were published on the Rackspace blog).
In preparation for the session, the following resources were created:
- https://bl ueprints.launchpad.net/heat/+spec/heat-autoscaling
- https://etherpad.openstack.org/heat -autoscaling
http://summit.openstack.org/cfp/details/172
The discussion at the Summit indicated strong interest in building a REST API for the existing autoscaling feature. Needless to say, there is a lot involved in this, touching upon significant OpenStack components like Quantum, LBaaS, and Ceilometer. Once the appropriate code is in place, a REST API will need to be created, features will need to be expanded/added, etc., and we'll be off and running :-)
Lots to do, and lots of great energy and excitement around this to keep us all chugging through this cycle.
On that note, we'd like to send out a special "thanks" to all the countless folks who worked so hard to make ODS happen. This event anchors us in a most excellent way, providing the insight and fuel that supports future development work so well!
Author | oubiwann |
---|---|
Date | April 23, 2013 |
Time | 18:55:08 |
Category | |
Tags | autoscaling community configuration management development heat lbaas open source openstack orchestration planning rackspace |
Line Count | 1 |
Word Count | 364 |
Character Count | 3196 |
Comments?
This blog doesn't use standard (embedded) comments; however, since
the site is hosted on Github, if there is
something you'd like to share, please do so by
opening a
"comment" ticket!