20:00:39 <sdake> #startmeeting heat
20:00:40 <openstack> Meeting started Wed Mar 27 20:00:39 2013 UTC.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:41 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:00:41 <sdake> #topic rollcall
20:00:44 <openstack> The meeting name has been set to 'heat'
20:00:45 <sdake> yo
20:00:51 <stevebaker> !
20:01:08 <asalkeld> hallo
20:01:20 <jpeeler> hi
20:01:39 <zaneb> hey
20:02:15 <sdake> slower around?
20:02:24 <sdake> spamamps indicated he wouldn't make it
20:03:01 <sdake> #topic doc sprint
20:03:26 <sdake> spamaps had suggested a 1 day doc sprint
20:03:33 <sdake> makes sense to me since our docs are in bad shape
20:03:51 <stevebaker> might need more than a day
20:04:04 <sdake> ya, well start small build up over time
20:04:33 <sdake> would suggest getting an understanding of what the docs involve
20:04:36 <stevebaker> but yes, a doc sprint is a great idea
20:04:51 <sdake> then we can create docs in havana
20:05:21 <stevebaker> I created skeleton docs of what I thought we might need in heat/doc
20:05:32 <shardy_> sorry I'm late
20:05:37 <sdake> hey shardy_
20:06:07 <shardy_> connectivity issues
20:06:45 <sdake> re date, lets shoot for 4th
20:07:29 <asalkeld> is there any point in doing it on one day?
20:07:38 <sdake> get exposed to it
20:07:46 <asalkeld> can't we just split up the work
20:07:46 <sdake> we aren't doing the entire docs in one day
20:07:59 <asalkeld> and do it as we have time
20:08:04 <hanney> 
20:08:06 <stevebaker> it means people aren't tempted to code instead, and there isn't some poor sucker doing all the documentation ;)
20:08:26 <sdake> lol
20:08:33 <asalkeld> well we could split up the work and assign
20:08:46 <zaneb> stevebaker: pretty sure people will still be _tempted_ to code instead ;)
20:08:57 <sdake> focus on 4th for docs day
20:09:00 <asalkeld> else we get a bunch of reviews  all at the same time
20:09:11 <stevebaker> zaneb: have you tried coding while sprinting?
20:09:15 <asalkeld> merge issues etc...
20:09:35 <zaneb> stevebaker: I only ever code while sprinting
20:09:47 <stevebaker> maybe Anne will hang out while we do it too, for questions
20:10:14 <sdake> annegentle^^ 4th work for you?
20:10:15 <asalkeld> she in nz/au?
20:10:27 <stevebaker> california usually
20:10:28 <annegentle> 4/4?
20:10:36 <annegentle> Austin Tx :)
20:10:44 <stevebaker> oops ;)
20:10:48 <sdake> annegentle: ya 4/4
20:10:59 <asalkeld> I vote for doing this over a week
20:11:04 <asalkeld> easy pace
20:11:13 <annegentle> stevebaker: :) I don't say howdy or hey dude so how would you know? :)
20:11:42 <sdake> asalkeld: lets have a look at docs on the 4th see what it entails
20:12:44 <sdake> #topic update on moving cloudwatch into ceilo
20:12:46 <annegentle> asalkeld: you have now become my whip target
20:13:14 <asalkeld> annegentle, I am keen - just see little point to do it on one day
20:13:16 <annegentle> asalkeld: :)
20:14:17 <sdake> asalkeld: any updates there
20:14:36 <asalkeld> not really, just trying to impl. juju
20:14:42 <asalkeld> getting there
20:15:05 <sdake> you put on agenda?
20:15:10 <asalkeld> no
20:15:11 <stevebaker> juju?
20:15:22 <sdake> Update on moving CloudWatch functionality into ceilometer (shardy/asalkeld)
20:15:50 <asalkeld> well it's got a heap of summit sessions
20:15:53 <zaneb> this came out of a discussion I was having with shardy the other day
20:16:02 <asalkeld> so after that we will do it
20:16:24 <asalkeld> so there is a prototype patch in review
20:16:43 <asalkeld> and we just want to nail down the design
20:17:03 <asalkeld> so should have a solution soon after summit
20:17:16 <asalkeld> the main thing from heat is what api we want
20:17:16 <zaneb> the question was about how data posted from the instance should be identified to ceilometer
20:17:50 <zaneb> right now we are passing the alarm name, and that is *not* the way we want to proceed
20:17:54 <asalkeld> zaneb, for the custom metric
20:18:01 <zaneb> asalkeld: yes
20:18:15 <shardy_> Also I was hoping asalkeld could give us a status update, to gauge if we can plan this work for havanna
20:18:28 <asalkeld> so most won't need that (as ceilometer has heaps of meters)
20:18:30 <shardy_> asalkeld: how's the monitoring/alarms stuff going in CM?
20:18:41 <asalkeld> shardy_, read up
20:19:00 <asalkeld> so PoC patch in review
20:19:09 <asalkeld> and summit sessions
20:19:12 <shardy_> asalkeld: sorry, super-laggy cellphone connection
20:19:34 <asalkeld> we will have an impl. after summit
20:19:39 <zaneb> asalkeld: cool, would be great to eliminate the custom metric altogether
20:19:49 <asalkeld> but won't take long
20:19:50 <zaneb> asalkeld: link to that review?
20:20:00 <asalkeld> I'll look
20:20:45 <asalkeld> might have been pulled down
20:21:05 <asalkeld> not really the issue
20:21:09 <asalkeld> it will get done
20:21:32 <asalkeld> quickly once things are descided
20:22:37 <sdake> ok anything else on that then zane?
20:22:43 <zaneb> no, that sounds cool
20:22:46 <sdake> tx
20:22:57 <asalkeld> http://summit.openstack.org/cfp/details/69
20:23:00 <sdake> #topic open discussion
20:23:05 <asalkeld> http://summit.openstack.org/cfp/details/71
20:23:18 <asalkeld> http://summit.openstack.org/cfp/details/62
20:23:30 <asalkeld> alarm/monitoring sessions
20:24:20 <sdake> pretty quiet around here prepping for ODS
20:24:34 <sdake> if there are no other topics, I'll end meeting
20:24:39 <asalkeld> cool
20:24:54 <sdake> #endmeeting