21:00:18 #startmeeting ceilometer 21:00:19 Meeting started Wed Jul 17 21:00:18 2013 UTC. The chair is jd__. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:23 The meeting name has been set to 'ceilometer' 21:00:51 o/ 21:00:53 #link https://wiki.openstack.org/wiki/Meetings/MeteringAgenda 21:01:13 o/ 21:01:21 o/ 21:01:25 o/ 21:01:37 o/ 21:01:42 * dhellmann is on a flakey connection 21:01:52 o/ 21:02:17 #topic action from previous meeting: nealph to track tempest QA efforts 21:02:25 * jd__ looks at nealph 21:02:34 So, I've created a new tempest bp at https://blueprints.launchpad.net/tempest/+spec/basic-tempest-integration-for-ceilometer 21:02:46 o/ 21:03:07 I think it makes sense for lilu to make it a dependancy in his cm blueprint as well 21:03:31 is this matcher mechanism used by the Heat Tempest tests also I wonder? 21:03:48 not sure 21:03:57 Perhaps...still looking at it. I'll follow the general approach taken by other tempest bp's including heat 21:04:04 if so, there would be some experience to leverage 21:04:08 cool 21:04:12 that'd be great. 21:04:29 the question is timeline...do we have to have this for h2/h3? 21:04:43 ask stevebaker (he did all of the Heat tempest work) 21:04:43 not for h2 certainly 21:04:50 h3 more reasonable 21:05:00 * nealph sighs in relief 21:05:04 nealph: only if someone is committing to it 21:05:42 okay, will finish looking into it asap and try to scope it. 21:05:56 nealph: do we need to #action this again? 21:06:01 #openstack-tempest 21:06:01 yep. 21:06:31 #action nealph to finish looking into tempest QA efforts 21:06:42 perfect...you typed faster than I did. 21:06:46 :d 21:06:50 nealph, is the "read the full specification" link on that bp right? 21:07:52 which one would that be? 21:08:05 the tempest spec? no. 21:08:20 yes, that's the one I meant 21:08:43 you may want to edit that indeed :) 21:09:15 will do...currently points to the ceilometer testing docs. 21:09:43 #topic Add logging to our IRC channel? 21:09:50 #vote yes 21:10:00 #vote yes 21:10:17 the infra team is going to be offering to turn on logging for channels that want it (if jeblair hasn't already sent that email and I just missed it) 21:10:17 why? 21:10:26 if we'd like to have it logged, I can take care of it 21:10:36 #vote no 21:10:45 (i don't think it's been sent) 21:10:45 * eglynn logs locally when online, great to have backup logs though for out-of-TZ traffic 21:11:20 i'm indifferent 21:11:30 how long do they get kept 21:11:30 would logging change the way people interact? 21:11:39 i.e. make folks more guarded? 21:11:45 asalkeld: afaik, indefinitely 21:11:56 asalkeld: is that the objection? ^^^ 21:11:56 eglynn, no spontaneous tirades? 21:12:03 eglynn, I think that is an issue 21:12:07 gordc: LOL 21:12:11 eglynn: I hope not, but that's why I suggested infra ask instead of just doing it 21:12:15 asalkeld: yeah, you could have a point 21:12:27 I think there's a lot of good info lost though... 21:12:40 maybe this is something to think about? 21:12:45 well could try it 21:12:54 can we turn it on/off? 21:12:56 we have time; maybe vote next week? 21:13:04 yeah, a vote for is that i don't think anyone is on the west coast of north america 21:13:15 asalkeld: it's a setting in the config file for the bot, and goes through change review 21:13:16 dhellmann: +1 for more thought 21:13:17 often see random questions popping up late 21:13:22 so we can turn it off, but not quickly or easily 21:13:37 dhellmann: they should implement a #offtherecord command :) 21:13:44 jd__: patches welcome? 21:13:50 hehe 21:13:56 that's a good idea 21:14:20 let's settle on voting next week then? 21:14:21 well one good thing is the ablity to see over time what questions get asked 21:14:23 well, maybe not -- you can always move the tirade to another room :-) 21:14:37 (i.e. what needs documenting) 21:14:40 asalkeld: yeah, I think that's going to prove to be more important for us over time 21:15:22 (but still a little weird) 21:15:28 been recorded 21:15:37 1984-ish? 21:15:54 asalkeld: a lot of people already log the channel, me included 21:15:57 I tend to assume text chats are recorded anyway, but maybe that's just me 21:16:02 dhellmann: me too 21:16:11 well I guess everything is recorded by government 21:16:13 NSA is watching everything anyway ;) 21:16:20 :-) 21:16:31 NSA is the cloud. 21:16:39 D= 21:16:48 nsa use openstack at least;) 21:17:11 but are they metering there usage? 21:17:29 * jd__ waits for an agent to pop in any minute now 21:18:02 there's probably been someone in deep cover here all along ;) 21:18:10 so do we already say yes to dhellmann or do you want vote next week? 21:18:11 btw: huge thanks to all for helping with the alarm stuff 21:18:26 it's almost all working end to end 21:18:33 yay! 21:18:34 nice :-) 21:18:43 \o/ 21:19:02 I guess the beauty is doing that for h2 so we've time to polish 21:19:23 I have to wait for h3 to get the heat side in 21:19:27 #topic Review Havana-2 milestone 21:19:37 switching topic since we're disrgressing 21:19:44 when was milestone-proposed cut? 21:19:50 earlier today 21:19:55 (dhellmann: I let the log stuff on the agenda for next week) 21:19:56 your mailbox didn't overflow like mine? 21:20:01 it did 21:20:06 jd__: ok 21:20:19 * eglynn jumped the gun so on assigning https://bugs.launchpad.net/ceilometer/+bug/1202143 to h2 21:20:20 the branch's cut and tomorrow Ceilometer shall be released 21:20:22 Launchpad bug 1202143 in ceilometer "sample POST fails on pipeline publish if user & project IDs not explicitly set" [Critical,Fix committed] 21:20:40 eglynn: did you see the backlog on -dev about that bug with ttx? 21:20:40 are backports still being accepted> 21:20:42 ? 21:20:57 * eglynn reads backs ... 21:20:58 eglynn: yes that was our point with ttx, you'll need to backport this one to the milestone-proposed branch 21:21:08 eglynn: but you sure can 21:21:11 jd__: k, I'll do straight after meeting 21:21:27 eglynn: thumps up 21:21:31 cool 21:21:53 so h2's done congrats everyone 21:21:59 we didn't push so many stuff to h3 21:22:06 so h3 is a lot of low priority bp mainly 21:22:13 heaps done 21:22:20 #link https://launchpad.net/ceilometer/+milestone/havana-3 21:22:51 the group-by one 21:23:25 asalkeld: ? 21:23:41 #link https://blueprints.launchpad.net/ceilometer/+spec/api-group-by 21:23:42 don't worry j 21:24:14 that one has been pushed back for a while 21:24:48 terriyu will be working on it starting now 21:24:49 I'm supposed to be working on that blueprint ... 21:24:55 cool 21:25:23 so feel free to exchange with her if you feel so :) I'm sure she'll be happy to get help 21:26:01 yes, I have no idea what I'm doing, so I'm always interested in talking 21:26:11 btw: we should have someone from new zealand joining the dev team soon (not from red hat) 21:26:37 asalkeld: great 21:27:02 asalkeld: moving the project centre of gravity down-under :) 21:27:08 #topic Release python-ceilometerclient? 21:27:23 need to wait for asalkeld sample-create patch to land 21:27:26 Needed by https://review.openstack.org/#/c/36905/ to uncap keystoneclient dep 21:27:37 https://review.openstack.org/#/c/37410/ 21:27:42 that would be nice 21:27:50 asalkeld: who? 21:28:14 Aurynn Shaw 21:28:33 (catalyst) 21:29:28 I'll have a few comments on that one eglynn 21:29:36 as soon as it lands, who's up for releasing? 21:30:06 I can do it 21:30:16 asalkeld: ha! I know her 21:30:30 stevebaker, cool 21:30:33 (the client relase that is ...) 21:30:49 eglynn: thanks (lo) 21:30:52 *lol 21:31:29 * nealph is rethinking logging ^^^^ 21:31:29 #action eglynn release python-ceilometerclient as soon as https://review.openstack.org/#/c/37410/ gets in and unblock https://review.openstack.org/#/c/36905/ 21:31:49 #topic Open discussion 21:33:28 if anyone has time, there's two patches: https://review.openstack.org/#/c/31969 and https://review.openstack.org/#/c/36213/ 21:33:47 first patch is just the specs... 21:33:49 nah, time to sleep here :) 21:33:59 gordc: so they're ready? 21:34:12 i should warn that the code is size is... large. 21:34:19 :( 21:34:37 jd__, i think its there, probably will change based on feedback. 21:34:42 not targeted at h2 surely? 21:35:15 i thought we cut it today. 21:35:57 no way for h2 21:36:02 h2 is tomorrow morning 21:36:03 gordc: well miletsone-proposed is cut hope to still get https://review.openstack.org/37574 in on that 21:36:30 but yeah, take your time. just thought i'd bring it up. the first patch is just specs so don't let the 2000 lines throw you...its mostly just notes. 21:37:09 eglynn, yeah, this would be too big for h2... i don't have enough money to pay you guys to get it in. 21:37:18 gordc: cool :) 21:37:52 but if you want to do it out of pure kindness... don't let me stop you guys. 21:39:04 (ending the meeting in a minute) 21:40:23 #endmeeting