15:02:49 #startmeeting ceilometer 15:02:49 Meeting started Thu Jul 2 15:02:49 2015 UTC and is due to finish in 60 minutes. The chair is gordc. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:50 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:52 The meeting name has been set to 'ceilometer' 15:02:55 o/ 15:02:57 o/ 15:02:59 hi 15:03:05 hi 15:03:07 o/ 15:03:14 o/ 15:03:25 #topic virtual Midcycle Meetup (https://etherpad.openstack.org/p/ceilometer-liberty-midcycle-agenda) 15:03:33 so 15:03:44 we did some vote gathering to figure out what topics people care about 15:03:52 that information is at 15:04:00 #link https://docs.google.com/spreadsheets/d/1mKLlRtTUWEq62ZrIi4Xr7EoV7SwGUNPORa7yauXYCbk/edit#gid=0 15:04:43 we didn't get a ton of voters, so there's been some discussion if we should allow people who haven't voted to register some input on that list (there on the spreadsheet) 15:05:23 but we're not sure if that kills the process we wanted to have which was to register _committed_ interest as opposed to drive by interest 15:05:29 cdent: seems like the 'open' way... i'ver heard this open word used a ot 15:05:32 alot* 15:05:58 I missed all this this past week :( 15:06:02 o/ 15:06:11 but that's the stuff I wanna see 15:06:22 the other main question on that list is where do we cut it off. is 2 votes enough to be in the schedule or should it be 3, or even 4 15:06:36 I think we should have a smaller number of quality sessions, rather than many sessions 15:06:47 but I'd prefer it we make that decision here 15:07:04 <_nadya_> o/ 15:07:08 cdent: agreed 15:07:11 to me 3+ is reasonable.. 2 == 1:1 discussion and can be done outside of meetup? 15:07:11 I like 4+ but it cuts off the API one 15:07:19 prad: ++ 15:07:19 for reference the topic definitions are here:  15:07:24 #link: https://etherpad.openstack.org/p/ceilometer-liberty-midcycle-agenda 15:07:27 i don't think we realistically could tackle even the 3 votes 15:07:30 cdent: it can be even 4, regarding to the number of topics IMHO 15:07:44 jasonamyers: i just voted for api 15:07:46 cool, that soulds like something resembling a consensus 15:08:00 the next thing that we need is for people to review their votes on their time availability 15:08:13 this the "what days" doodle poll: 15:08:17 #link http://doodle.com/6vfksdu38wcwqqd3 15:08:22 this is the "what hours": 15:08:28 #link http://doodle.com/gzhumwaakrqds38h 15:08:43 cdent: we configured it to align with viewers timezone right? 15:08:55 no, it is in UTC and it says so 15:09:04 "Pick hours of the day (in UTC) that you are willing and able to be available for the virtual midcycle." 15:09:15 does not read above 15:09:26 * cdent does not give gordc a cookie 15:09:29 is this one day we are aiming for? 15:09:32 two 15:09:35 ok 15:10:05 when I was reviewing the data it seemed to make sense for a few of the topics to be split across the two days: get brains filled with ideas on day one, decide things on day two 15:10:15 we don't have to do it that way but it seems like it could work well 15:10:41 if we can stick with fewer topics we can have room for that, I think 15:10:47 it sounds like a good idea to me 15:11:14 maybe not specify the topic right now, just leave room for that 15:11:51 next question: if we find that we can make the time fit, is the beginning of next week okay or is that too soon, and we should set something like wednesday as the earliest possible start? 15:11:57 (or even later than that?) 15:12:25 if we can schedule the agenda based on interest(and TZs) it would be better .. vs open agenda 15:12:39 yes, there is _not_ going to be an open agenda 15:12:50 good 15:12:51 cdent: i'm assuming holiday weekend will make people sluggish start of week 15:12:53 the entire purpose of doing this planning was to be able to have an in advance agenda 15:13:01 roger that gordc 15:13:06 cdent: that said, we don't have many americans... 15:13:29 * cdent looks at prad and jasonamyers 15:13:32 tuesday? 15:13:51 I'm willing to do odd hours 15:13:57 yea early next week is too soon i think.. i'm not planning on working this weekend, want to watch fireworks like gordc did in canada :) 15:14:06 if we start on tuesday that kills off jd__ unless he's will to change his schedule 15:14:21 wed+ works i think 15:14:23 which Tuesday? 15:14:23 and since jd seems a requirement on two of the more popular topics he's holding power 15:14:27 gives us a day or two to prep 15:14:30 7th and 8th 15:14:46 gordc claims to unavailable the 9th and 10th 15:14:49 (thursday and friday) 15:14:52 really can't be there, I'll be on vacation 15:15:22 gordc you have thursay friday flexibility? 15:15:34 16th, 17th ? 15:15:37 or jd__ you have flexibility 13, 14, 15? 15:15:41 the hours doodle for me is not the same for all days, but I will do my best with parallel meetings 15:15:46 cdent: i'll be here for most part... probably not later in day but that doesn't affect euro people 15:15:54 cdent: neither, vacation again :( 15:16:02 or 8-9 15:16:07 cdent: I really didn't lie in the poll :D 15:16:11 k so either 9/10 or 16/17 seem the best choices 15:16:15 so we can have one day with each :) 15:16:19 yep 15:16:19 jd__: everyone lies, all the time ;) 15:16:31 cdent: hmmm that would make a good show 15:16:33 cdent: true story 15:16:36 ha! 15:17:04 okay, let's put it this way: if anyone lied on the doodle, fix it 15:17:13 haha 15:17:14 cdent: you have original doodle for availability days? 15:17:17 and then prad and I will figure it out, using wednesday as the earliest possible date 15:17:21 hehe 15:17:48 gordc I have no idea what you mean? 15:18:08 the doodle where everyone put what days they were availabile 15:18:13 http://doodle.com/6vfksdu38wcwqqd3#table 15:18:15 that's what we're talking about 15:18:33 cdent: updated 15:18:37 thanks 15:19:02 <_nadya_> I have two entities of myself 15:19:02 cdent: it does not mean I lied, when I first filled it :) 15:19:45 I lied I'm actually not there the 16th :> just fixed 15:19:49 _nadya_: it shows an option to delete, if I saw correctly 15:20:05 <_nadya_> ildikov: yep, fixed :) 15:20:10 cdent: then maybe let's not try to have consecutive days? 15:20:22 cdent, 9/10 looks promising to me.. most people are available 15:20:25 that would be fine jd__ if everyone is cool with that 15:20:30 _nadya_: now we know that option works too :) 15:20:35 I'm cool with that 15:20:37 I was just worried that people might lose momentum or forget stuff or something 15:20:47 I think I would probably prefer that 15:20:51 time to reflect 15:20:58 cdent: 9/10 seems best. 15:21:11 even though you claim to be gone 15:21:23 my available didn't really reflect euro timezone 15:21:31 i vote 9/10 unless jd__ cant make it 15:21:33 availibility 15:21:37 cdent: maybe that's the reason :) 15:21:57 9/10 works for me 15:22:13 right let's run with it 15:22:20 because otherwise we'll be here all day 15:22:28 cdent: +1 15:22:28 +1 9/10 15:22:31 cdent: yep 15:22:32 #agreed 9/10 virt sprint yeah mojitos 15:22:49 please update the other doodle poll as well, we don't need to discuss that part, we'll just use it for schedule: http://doodle.com/gzhumwaakrqds38h 15:22:59 and with that I think we can move on because we also: 15:23:06 #agreed 4 is the cuttoff 15:23:15 thanks everyone 15:23:41 cdent: prad: thanks for all the prep 15:23:42 since prad will be bbq and beers tomorrow I'll either make some mail tomorrow or wait for him until monday and we'll send some mail 15:24:12 cdent: cool cool. thanks to both of you for organising. 15:24:44 one question, which tool will us use? 15:24:56 good point 15:25:08 does hangout work for everyone? 15:25:08 hangouts got the most votes 15:25:19 it does not 15:25:19 or should we setup blue jeans? 15:25:27 last i heard its blocked in china 15:25:30 webex got a "please no" 15:25:35 haha 15:25:42 haters gonna hate 15:25:47 hmm, it usually does not work for me from the office, but I will see whether I can do some hacks 15:25:47 hehe 15:25:47 google is a pain in China. 15:25:48 from the redhat side of the house we can set up public bluejeans thingie 15:26:06 <_nadya_> folks, are you sure about cutting func tests off? maybe one more vote :)? 15:26:29 (I'd like to see it in) 15:26:32 yea we can setup bluejeans.. might not be the most open thing but it works i think 15:26:48 _nadya_: we can put '3' topics as 'if we have time' 15:26:54 I can try hangout with VPN 15:27:08 looks like bluejeans needs service fee? 15:27:13 we can schedule an initial "does any of this tech actually work session" 15:27:17 bluejeans is free 15:27:31 llu-laptop, we can setup a publich session.. no fee 15:27:31 prad/cdent can one of you try it out with llu? 15:27:37 sure 15:27:47 cool cool. 15:28:09 <_nadya_> gordc: ok, maybe it's interesting only to our team indeed... 15:28:52 oh one more thing: if you feel like you would be a suitable facilitator/leader for topic, put yourself in the spreadsheet 15:28:53 thanks 15:29:00 _nadya_: i think it's more that we're all in agreement of it. :) if there's things to discuss than we can bump it up 15:29:03 _nadya_: does it need more discussion or more hands to actually do it? 15:29:10 if we close up this topic in the next minute we'll be the winners of the internet 15:29:24 :) 15:30:33 <_nadya_> let it be the first in queue 'if we have time', ok? 15:30:43 (somebody already pushed it over the 4 vote limit) 15:30:49 so it's in there 15:31:27 cdent: your open google sheet is flawed.lol... lock it down. 15:31:41 <_nadya_> ok, so I have to prepare a show for it :) 15:31:53 dood, man, you said you wanted some open man, I was all like "Lemme be a fascist" and you were all "cool your jets goose" 15:32:01 _nadya_: ppt, cdent requests it. 15:32:10 cdent, it was me i missed to vote for it earlier 15:32:17 idegtiarov++ 15:32:23 cdent: yeah, true. i give you permission to take absolute control... that ends well always. 15:32:23 just tried, hangout works on my VPN. but no objection to bluejeans either 15:32:45 llu-laptop: it works... for now.lol 15:33:30 hangouts always disconnects on my laptop periodically 15:33:36 let's try hangouts i guess and fall back on bluejeans if needed and then fall back on no visual/audio of llu... 15:33:43 although we can start with one and have the other as fall-back 15:33:49 * cdent nods 15:33:52 gordc: snap :) 15:33:59 great minds... 15:34:02 or slow minds... 15:34:28 gordc: my vote is on the first one :) 15:34:35 gordc: good plan :) 15:35:13 any other questions regarding midcycle? 15:35:25 WHO IS BRINGING THE SNACKS 15:35:44 I'll ship cookies to everyone who gives me a mailing address 15:35:44 is there a chance to decide on the M one regarding dates before Aug 17? 15:35:51 allergies? 15:36:03 jasonamyers, beers? 15:36:04 ildikov: I'd love to do that 15:36:15 prad: I don't drink 15:36:23 jasonamyers: cool :) 15:36:27 jasonamyers: we have a doodle up? 15:36:31 yes 15:36:50 shouldn't we have a Doodle as a Service? 15:36:53 * gordc will give headsup. i'm not sure i'm available all of early dec 15:36:57 https://wiki.openstack.org/wiki/Meetings/Ceilometer/M*_Mid-Cycle 15:37:22 I'm game for late november it's just hard to miss turkey time 15:37:35 which might only be a US thing 15:37:38 gordc: not all of or none of? 15:37:41 o/ 15:38:12 ildikov: none of? i tend to take holiday around early dec. 15:38:41 gordc: usually me too 15:38:48 I'm unclear on the constraints: Is January too late? Also, is Msummit coming early this year? 15:39:02 gordc: but understood 15:39:30 this is Dublin or Paris? 15:39:42 cdent: I guess we are trying hard to avoid the it's too late in the cycle issue 15:39:44 eglynn said we should do before jan 15:39:50 prad dublin 15:40:04 cdent: i don't think it's too late but i guess it links back to reason why we scrapped this midcycle. 15:40:07 ildikov: yeah that's what I assumed just wanted to be clear 15:40:26 let's all skip summit, and just go to a midcyle in early november :) 15:40:50 okay 15:41:09 * jasonamyers isn't gonna make tokyo 15:42:24 let's see how the doodle plays out for decemeber. if we have nothing we might as well try for january... and then we can always do virtual one again 15:42:37 I think early Jan can work too 15:43:04 I can do a hosted on in Jan 15:43:13 I wanna make sure we get together once a year 15:43:27 jasonamyers: yeah, that'd be good. 15:43:30 jasonamyers: +1 15:43:48 #action vote on december doodle for now (http://doodle.com/hmukqwzvq7b54cef) 15:44:07 check back on the Doodle next week and decide whether it's Dec or Jan? 15:44:32 ildikov: 2 weeks? we won't have meeting next week because of midcycle 15:45:12 gordc: yeap, two weeks is fine too, forgot about 9th is Thursday 15:45:43 ildikov: cool cool. we'll see then 15:45:55 other midcycle comments? 15:46:57 there will be COOKIES! 15:47:06 #topic gnocchi status 15:47:14 * cdent cookiecoptrs 15:47:19 jasonamyers: no raisins 15:47:29 jd__: cdent: anything? 15:47:55 not really; jd__ has been on aodh and I've been on devstack plugin stuff and the previous topic 15:48:04 there have been some fixes and such but nothing revolutionary 15:48:06 cdent: cool. next! 15:48:13 <_nadya_> we continue active work on InfluxDB driver 15:48:15 there's some progress on influxdb, but not ready yet 15:48:32 _nadya_: awesome. any blockers we need to raise to pauldix? 15:48:39 what cdent said 15:49:28 gordc: release 0.9.0 have some critical failing from the rest requests, but first versions of 0.9.1 looks better 15:49:43 <_nadya_> gordc: IlyaT is managing with blockers using different hacks :) 15:50:14 <_nadya_> cdent: are you working on influx driver too? 15:50:27 ityaptin: cool cool. let me know if you need anything prioritised. pauldix seemed receptive to prioritising the issues we run into 15:50:38 _nadya_: no, I was trying to give an overview of everything I was aware of including what ityaptin is up to 15:50:51 <_nadya_> cdent: ok! 15:51:33 #topic open discussion 15:51:33 gordc: ok, cool! I have some suggestions for InfluxDb team) 15:51:45 <_nadya_> btw, I've started alarming on Influx. looks optimistic 15:52:15 ityaptin: kk. maybe we can forward him a list of suggestions. 15:52:57 i jumped the gun on topic change. but i guess this falls into open discussion as well 15:53:22 gordc: Good! I prepare they to the start of next week) 15:53:58 ityaptin: awesome. 15:54:13 any other topics? or we can end this 5-6 min early. 15:54:25 Would appreciate more eyes on reloadable pipeline review - https://review.openstack.org/#/c/190842/ 15:54:58 Folks, how do you think, will we ends work on API V3 to end of a liberty cycle? 15:55:12 rjaiswal: will take a second look today. 15:55:18 I looked into our UI in Horizon and was scared 15:55:29 ityaptin: we won't implement it... but we can start to plan it. 15:55:41 ityaptin: because they are using it incorrectly? 15:56:20 Yep) but in some place our api do not provide requirement functionality 15:56:23 ityaptin: it's impossible to get it implemented for Liberty, but we surely need to start design it for M 15:56:39 ildikov, I'm agree with it 15:57:16 ityaptin: there were some queries and statistics they wanted to do but there wasn't a good way with our API IIRC, are youreferring to smth similar? 15:57:20 ityaptin: i'm not sure there's any logic/use case to what horizon does with ceilometer. it's just hitting available apis blindly it seems 15:57:57 Thanks gordc, wishing for more participation:) 15:57:59 gordc, for example, I think Horzion UI need a Api endpoint for querying stats filtered by some same fields (n resource ids in query for example) 15:58:03 maybe we need a liason for ceilometer/horizon 15:58:32 gordc: probably 15:58:47 ityaptin: this is a gap in our current api or something horizon doesn't do? 15:58:58 gordc: we could start with the question whether anyone complained about the Ceilo UI 15:59:02 gordc: our api 15:59:19 ityaptin: ok. maybe open a bug for it. 15:59:24 gordc: just to see how much it is used at the moment 15:59:40 ildikov: i don't think anyone uses horizon ceilometer interface... it was pretty non-sensical last time i looked at it. 15:59:41 <_nadya_> ildikov: it's just not used I guess 16:00:02 carry on in main channel... times up 16:00:09 thanks folks 16:00:12 #endmeeting