15:00:34 #startmeeting ceilometer 15:00:35 Meeting started Thu Sep 10 15:00:34 2015 UTC and is due to finish in 60 minutes. The chair is gordc. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:40 The meeting name has been set to 'ceilometer' 15:00:59 purple 15:01:02 dragons 15:01:07 o/ 15:01:08 o/ 15:01:09 o/ 15:01:22 o/ 15:01:54 o/ 15:01:59 cdent, is that the theme for this mtg 15:02:13 theme for life 15:02:25 o/ 15:02:32 will give it a few more seconds. 15:02:38 ah kk 15:02:43 o/ 15:03:02 #topic liberty update 15:03:22 so we're all set... 15:03:40 we have both FFE items in now so code should be finalised from feature pov 15:03:55 bugs bugs bugs 15:03:57 we also just released Aodh 1.0.0 15:04:24 so yeah. as cdent says, find the bugs 15:04:46 i don't really have a target for rc1 release date 15:05:02 we'll see how many bugs we find originally and play it by ear. 15:05:28 that's all i have on that topic 15:05:37 anyone else? 15:06:02 short meeting? yeah? cool. 15:06:35 i'm going to skip over roadmap items but cdent has something related to it later 15:06:42 recurring: ceilometerclient release? 15:06:46 #topic recurring: ceilometerclient release? 15:07:06 we just released our first liberty candidate for ceilometerclient 15:07:18 cdent: i think you opened a bug which means we'll probably need another relsae? 15:07:20 it will want a new one after limit fixes 15:07:35 jinx 15:07:51 awesome 15:08:13 anyone else have ceilometerclient issues within past 12 hrs? 15:08:46 i assume no. let's go. 15:08:57 #topic recurring: Gnocchi status 15:09:10 cdent: jd__: sileht: anything? 15:09:44 I'm waiting for infra guys to import the gnocchiclient into the openstack namespace 15:10:14 I'm waiting from infra guys to get the integrated job merged 15:10:25 sileht: ah ok. yeah, i believe i saw that patch. i'll try to ping someone later today. 15:10:43 or get someone with the infra connections to take a look 15:11:30 I'm regulary ping them 15:11:35 we're pushing on Grafana too to improve our support 15:11:38 (devstack patch landed) 15:12:01 I've a talk about Gnocchi scheduled in 2 weeks at the next OpenStack Paris meetup 15:12:04 sileht: are they replying? 15:12:22 or is blocked because it's end of cycle? 15:12:31 yes, but I got a couple of rebase issue, and lost my +2 15:12:37 :( 15:13:15 sileht: i think you need someone with connections... or just go screaming into openstack-infra and see what happens. 15:14:06 screaming is what I do usually :p 15:14:14 sileht: :) 15:14:25 jd__: let us know how meetup goes. 15:14:41 sure. I'll count the tomatoes. 15:15:06 jd__: perfect 15:15:15 ok. let's move on. cdent i'm going to slightly hijack your topic. 15:15:36 #topic Tokyo sessions and planning (cdent) 15:15:48 just one question, do we need an etherpad 15:16:04 15:16:15 cdent: sure. you can create one. i've created a google doc for people to submit formal proposals 15:16:47 https://docs.google.com/spreadsheets/d/1ea_P2k1kNy_SILEnC-5Zl61IFhqEOrlZ5L8VY4-xNB0/edit?usp=sharing 15:16:54 similar as before. 15:17:12 cdent: but i think to brainstorm, etherpad would be better. 15:17:36 gordc: were your sessions be approved? 15:17:37 just for reference, we received 2 Fishbowl, 7 Working room, and 1 half day session 15:18:13 nadya: speaker session? no. i believe none of the dev talks were chosen. 15:18:24 gordc: yep, indeed 15:18:28 nadya: right now we're just talking about Telemetry design sessions 15:18:43 gordc: yep, I understand; just asking 15:19:00 luckily, we got roughly same as Vancouver (1 Working room less) 15:19:51 so yeah, if you have an idea, feel free to use ehterpad to brainstorm and then propose a topic to google doc... and we can vote... 15:19:56 gordc: did you send a mail about the google docs? 15:20:11 ildikov: not yet. 15:20:28 #action send link to telemtry design session proposals 15:20:39 gordc: thanks :) 15:20:40 the process ok with everyone? 15:20:51 https://etherpad.openstack.org/p/tokyo-ceilometer-design-summit 15:20:57 anyone want to change it from how we've done it previously? 15:21:31 I'm ok with how we've done it 15:21:41 seems okay 15:22:02 cool cool 15:22:46 regarding final date for design session proposals. shall we aim for Oct5th? vote ends Oct 8th? 15:23:07 we can use the above ^^ etherpad for discussions if necessary 15:23:22 that would give roughly 2.5 weeks for chosen topics to be formalised/discussed further 15:23:29 pradk: awesome 15:23:46 gordc: it's more than 3 weeks from now, sounds fine with me 15:24:11 gordc: it should be enough to collect the proposals 15:24:14 ildikov: we can set it tentatively. i don't know how busy people will be with testing. 15:24:26 ildikov: yeah, that's what i'm thinking/hoping. 15:24:31 gordc: I guess we split between modules based on the proposals, right? 15:25:12 ildikov: true. so we have a noticeable divide for 'ceilometer', gnocchi, and aodh... i hadn't considered how many spots to reserve 15:25:36 IMHO we can do that on demand 15:25:46 yeah my thoughts exactly. 15:25:48 gordc: would we need a joint component session? 15:26:18 I mean to ensure the interaction between them, how to handle old/new APIs etc is covered 15:26:41 not 100% sure it's needed, prolly it can be part of the regular planning and voting 15:26:57 ildikov: sure. that can be a possible topic (if you choose to propose it) 15:27:41 i think i'm pretty open to pretty much any 'telemetry/monitoring/metering/alarming' related topic to be proposed regardless which project it falls under 15:27:54 unicorns 15:28:07 cdent: alarming? 15:29:08 any other items we need to address? 15:29:25 gordc: ok, cool 15:29:31 gordc: tnx 15:29:32 #topic open discussion 15:29:41 party with Monasca? 15:29:46 sweet. short meeting. 15:29:56 one question, will we have a mentor for OPW internship? 15:30:13 nadya: i've mentioned to Roland already that he is welcome to propose Monasca topics as well during our session. 15:30:23 gordc: ok 15:30:29 nadya: are you volunteering to plan a party? 15:30:39 nadya: i'll support that 15:31:02 ildikov: how does that work normally? i haven't really looked/followed the OPW internship stuff. 15:31:19 gordc: come to my hometown :) I'm still not able to go to summits :( 15:31:50 gordc: don't know either 15:31:52 nadya: doesn't mean you can't plan still. ;) 15:31:58 lol 15:32:06 gordc: I got the question today, I asked back for details, no response yet 15:32:22 ildikov: DinaBelova i believe was mentor last time during Juno 15:32:26 or kilo 15:32:53 eglynn: weren't you mentor once also? 15:33:33 eglynn: do you remember how OPW internship works? 15:33:33 ildikov: for the OPW? 15:33:39 ildikov: yes indeed ... I mentored amalagon for Juno 15:33:41 eglynn: yeap 15:34:14 ildikov: I remember most of the details ... any specific questions on it? 15:34:45 I wonder what it looks like timing wise 15:36:00 it's a 13 week program 15:36:13 and well, I could ask several questions, but if you might have a link to a description and then we can come back with stupid questions :) 15:36:18 the end point basically lines up approx with the last milestone in the cycle 15:36:39 so it would start 13 weeks before mitataka-3 15:36:55 so the process is basically add project ideas to the OPW/outreachy wiki and await potential interns to express interest 15:37:10 the interns are then ranked by the mentor group on a scale of 1-5 15:37:30 the spots are limited as each one needs to be sponsored 15:37:42 (to cover the intern stipend and travel expenses) 15:38:01 a sponsorship IIRC costs circa US$6k 15:38:13 do you know what the criterias are/what the ranking is based on? 15:38:56 interest level, coding ability (not necessarily python), cloud knowledge, availability for fulltime work 15:39:12 the summer cycle is generally better for the latter 15:39:24 ildikov: you thinking of mentoring or just inquiring? 15:39:28 I guess it's better to find a mentor and then propose some topics to that wiki 15:39:37 (since students in the US and Europe are off in the summer) 15:40:17 gordc: I got a mail today from a girl, who's interested, but I do not really have the bandwidth to be a mentor, but I would like to help and support her, this is why I thought to bring up a topic as we had mentors earlier too 15:40:36 at the diveristy panel in the OpenStack day in Seattle recently someone mentioned though that most of the applications are now from India & China 15:40:46 gordc: and also if we have tasks that need to be done anyway then if we have an intern working on it seems like double benefit 15:40:49 ... not sure how the academic year works there 15:41:09 gordc: so more inquiring atm :) 15:41:53 eglynn: good to know... maybe some of our east-asian cores can help. 15:41:59 eglynn: do they need former contribution to he project? 15:42:10 ildikov: i hadn't thought about it to be honest but good to bring it up 15:43:19 gordc: we can come back to this later, I just wanted to raise the question as heads up 15:43:28 oh before i forget, we're going to give midcycle voting one last try, we'll send a mailing list for dates in Nov/Dec and January... if we don't get a response, we'll just do virtual midcycle agian 15:43:35 ildikov: sounds good 15:44:19 ildikov: yep, *some* openstack contribution helps ... but it can just be a trivial patch 15:44:32 gordc: don't get a response == not enough attendees? 15:44:43 eglynn: ok, cool, good to know 15:45:14 ildikov: well right now we don't have responses so the assumption is that there is very few attendees 15:45:45 gordc: ok 15:46:37 jasonamyers (cisco) has offered to host so it'd be nice to stop dragging process so he has firm yes/no 15:47:17 +1 15:47:45 any other discussion items? 15:48:56 thanks very much folks. happy hacking 15:48:59 #endmeeting