Difference between revisions of "Heat/GrizzlySummit/HeatImplementingCloudWatch"
| Line 9: | Line 9: | ||
There is an [http://etherpad.openstack.org/grizzly-heat-cloudwatch Etherpad] to capture notes and points for discussion during this session | There is an [http://etherpad.openstack.org/grizzly-heat-cloudwatch Etherpad] to capture notes and points for discussion during this session | ||
| + | |||
| + | Here are some links describing the current state of the heat cloudwatch implementation, and roadmap for future development: | ||
| + | |||
| + | https://github.com/heat-api/heat/wiki/Using-[[CloudWatch]] | ||
| + | |||
| + | https://github.com/heat-api/heat/wiki/Cloudwatch-Architecture-rework | ||
Revision as of 17:27, 11 October 2012
Session Lead: Angus Salkeld
Session Title: Implementing CloudWatch for OpenStack
Session Description: CloudWatch is currently provided by Heat and provides monitoring and alarm features for OpenStack. In this design session, a brief description of cloudwatch is given as well as the current heat cloudwatch architecture.
Expect 75% of time spent on open community design session discussion architecture and implementation feedback.
There is an Etherpad to capture notes and points for discussion during this session
Here are some links describing the current state of the heat cloudwatch implementation, and roadmap for future development:
https://github.com/heat-api/heat/wiki/Using-CloudWatch
https://github.com/heat-api/heat/wiki/Cloudwatch-Architecture-rework
