15:00:43 #startmeeting monasca 15:00:43 Meeting started Wed Feb 8 15:00:43 2017 UTC and is due to finish in 60 minutes. The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:44 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:46 The meeting name has been set to 'monasca' 15:01:02 https://etherpad.openstack.org/p/monasca-team-meeting-agenda 15:01:18 Agenda for Wednesday February 8 2017 (15:00 UTC) 15:01:19 1. Ocata Dates 15:01:19 1. We create stable branches. Are there any high prio changes for Ocata? 15:01:19 2. Ocata Final Release candidate deadline: 16 Feb 15:01:19 2. Monasca Mid-cycle 15:01:19 3. Alarms Blueprints 15:01:19 1. new api resource: https://blueprints.launchpad.net/monasca/+spec/alarm-manager-resource 15:01:20 2. grouping: https://blueprints.launchpad.net/monasca/+spec/alarm-grouping 15:01:20 3. silencing: https://blueprints.launchpad.net/monasca/+spec/alarm-silencing 15:01:21 4. inhibition: https://blueprints.launchpad.net/monasca/+spec/alarm-inhibition 15:01:21 4. New owner for monasca-grafana fork 15:01:22 5. Reviews 15:01:22 5.1 => https://review.openstack.org/#/c/356403/ 15:01:22 o\ 15:01:23 5.2 => https://review.openstack.org/#/c/416325/ vs https://review.openstack.org/#/c/422330 15:01:30 o/ 15:01:30 o/ 15:01:32 o/ 15:01:32 hi 15:01:35 o/ 15:01:40 timasz: you made it 15:01:46 tomasz ^^^ 15:01:46 funny.... :P 15:02:01 o/ 15:02:10 so we have a good agenda to work through today 15:02:14 again 15:02:27 so, without further delay, let's get started 15:02:37 #topic Ocata Dates 15:02:49 witek: u there? 15:02:50 we have to create stable branches 15:03:22 when is the final date again 15:03:23 has anyone high-prio changes which have to make it to Ocata? 15:03:33 good point? 15:03:46 if there are any important bug fixes this would be a good time to push them through 15:03:52 and priortize them 15:04:30 I think you wanted psutil < 2.0.0 to enter 15:04:33 witek, I mean 15:04:34 Is this one ready, https://review.openstack.org/#/c/424242/ 15:04:44 that's the psutil one? 15:04:51 i'm good on it 15:04:59 works for me 15:05:01 tomasz: are you good 15:05:15 I did not spotted anything suspicious apart from keystone and this kafka things 15:05:33 but again, kafka detection worked anyway even though plugin said that it did not locate kafka @ 9092 port 15:05:47 for other issue (keystone) created a bug 15:05:57 do we hold up the merge for that 15:06:00 so I think this is ok for now to merge it 15:06:12 it did locate, there was no IP assigned 15:06:13 I'd add a bug to keep it in mind 15:06:21 ahm 15:06:24 ok, i'm going to +2 then 15:06:27 so I guess, we're fine 15:06:37 oh so we are now talking about the changes that we have made 15:06:51 I thought we were talking about what we are going to do 15:07:29 so, I would like to apply for stable branches tomorrow 15:07:36 anqi: we have a meeting agenda which included several things, like managing the ocata release 15:07:43 we are going to get to your topic too 15:07:58 if someone has high-prio changes, please let Roland and me know 15:08:15 yeah I am trying to get followed 15:08:26 craig bryant has a number of bug fixes in the works 15:08:33 that are worth looking at 15:08:51 also, there is this one in works, https://review.openstack.org/#/c/428810/ 15:08:54 ok, I'll wait for green light then 15:09:01 how long do you have? 15:09:07 we have? 15:09:14 16th is the deadline 15:09:32 hmm, don't want to wait until last minute 15:09:39 for final release candidate 15:09:41 but if we can get done by Friday, that would probably be OK 15:10:19 I am trying to verify what I can...that I can say, I will put more focus on Craig's changes...maybe some of them I will be able to merge 15:10:20 that would give you on Monday a few days to get the branches created 15:10:31 thanks tomasz 15:10:33 that would be great 15:10:45 for you.... 15:10:46 always 15:10:48 :D 15:10:58 there is a long list of reviews, so i'll try and get through it 15:11:15 tomasz: you better be careful with all those reviews and commits 15:11:21 you could be the next ptl 15:11:35 power....unlimited power.... 15:11:35 :D 15:11:47 ok, so let's change topics 15:12:01 #topic Monasca Mid-cycle 15:12:22 Are we still good for the 22nd and 23rd? 15:12:35 I should send out a notice to openstack-dev 15:12:36 works for me 15:12:41 i can make the 1st day, not the 2nd 15:13:02 but not suggesting to change dates... 15:13:08 so, another option is to splt the mid-cycle across two weeks 15:13:12 february? 15:13:19 correct 15:13:41 okay for me 15:13:42 will it be still possible to online that ? 15:14:04 yes, it will all be online via skype/lync 15:14:08 thx 15:14:09 video conferencing 15:14:21 start at same time IRC meeting starts 15:14:26 just goes longer in the day 15:14:41 we usually do 5 hours 15:14:53 that works out from 8 AM to 1 PM my time 15:15:19 i can make the first two hours 15:15:27 thanks anqi 15:15:45 so, we can cover your areas earlier 15:15:57 is everyone ok with that 15:16:09 it end-up in a late night for everyone in europe 15:16:16 and even later for japan 15:16:19 yeah, I will try to join but might be tricky for me 15:16:24 it's fine. that will be 11 pm to 4 pm for me 15:16:29 but if you put it earliear 15:16:37 it won't be good for you area 15:16:44 fine for me (utc) 15:16:53 11 pm to 4 am * 15:17:08 if we start at 7 AM, then that might be better 15:17:18 i don't think we have anyone on the west coast 15:17:26 that will be attending 15:17:35 so, i can make 7 AM start time 15:17:53 thanks for the change. would be great for me 15:17:55 which give east coaster and europeans a better start time 15:18:07 are folks ok starting earlier 15:18:13 ok by me 15:18:28 thanks bklei, you and i are in the same timezone 15:18:35 yep 15:18:49 witek: does that work better for you? 15:18:53 sure 15:19:07 so, it sounds like we are good then 15:19:26 i'll send a notice 15:19:46 i believe we'll have good represenation and a lot of topics 15:20:08 will you create etherpad with agenda? 15:20:09 #topic blueprints 15:20:18 witek: yes, i will 15:20:22 thanks for reminder 15:20:22 thanks 15:20:27 i'll put that in the notice 15:21:04 so, before we cover anqi's topic, i wanted to cover the alarms blueprints 15:21:19 kaiyan and andrea: u there? 15:21:28 yes :) 15:21:30 yes! 15:21:37 you have the floor 15:21:51 We have 4 new blueprints 15:21:58 to implement alarm inhibition 15:22:05 and alarm silencing and alarm grouping 15:22:14 also adding a new resource in the api 15:22:31 the blueprints are still in the planing phase 15:23:01 The links are in the agenda. So if we can get some reviews on those and suggestions that would be great! 15:23:33 thanks kaiyan and aadams_m, so, this is an area that we can go into more detail at the mid-cycle 15:23:45 but, we wanted to let everyone know what is going on 15:24:10 and get early feedback if possible as they want to start writing code 15:24:36 1st question is: only python or also java ? 15:24:39 also, if you want to be involved in the effort, that would be good to know 15:24:46 we are planning on only python 15:25:17 tomasztrebski: are you interested in working on this? 15:25:46 rhochmuth: I am, but I won't be able we got other things to attend in Fujitsu 15:26:01 :-( 15:26:06 we have to check with Cristiano 15:26:31 ok, let us know if there is interest 15:26:42 we have the time right now so would like to proceed 15:27:13 if it was up to me, I'd code it all down [rotfl], but as Witek said, this is not our decision and Cristiano is the one who needs to be asked about that :D 15:27:16 and aadams_ and Kaiyan can cover more in a couple of weeks at mid-cycle 15:27:16 at the moment we are little blocked 15:27:47 yeap 15:27:53 Sounds good 15:28:00 ok, let's shift over to aq 15:28:32 aq: we got your email this morning 15:28:39 great 15:28:59 i want to know further details about the feature 15:29:12 so, is the metric-counts bp you are interested in? 15:29:18 yes 15:29:32 or if there was something higher priority, would that be better? 15:29:48 ok i am checking 15:30:01 I think, I don't follow 15:30:06 i'm just trying to understand if this featyre is something you need 15:30:10 but all of those with high prior seem to be taken 15:30:41 no i am just trying to get started with this project 15:30:54 ok, so you looked at the list and found a bp that wasn't take that looked good 15:31:03 so i pick a bp seems simplest to me, to get started 15:31:16 yes 15:31:26 so, this might be an area where getting involved in some of the other work might be better 15:32:24 do you mean kafka related work? 15:32:26 I can't quite recall why https://blueprints.launchpad.net/monasca/+spec/count-metrics, was created 15:32:48 ok 15:32:50 kafka would be one area 15:32:55 but that isn't a new feature 15:33:42 yea i know. i mentioned it because i knew you were talking about some patches related to kafka just before 15:33:47 btw...I think that bps should be reviewed becuase those bps proposed now seems strangly similar in features like the ones that are already there - muting for instance or this maintenance I think I submitted 15:34:15 which bp do you suggest i start with? 15:34:24 I mean if those from anqi are closer to start working on them, older might be deleted 15:34:38 not start with, just that we might have duplicated bps in launchpad 15:35:04 okay 15:35:05 tomasztrebski: i don't think i can delete bps 15:35:32 rhochmuth: hmm, that's rather unfortunate 15:35:53 anqi: how about i take a look at the list more closely and we excachange some emails 15:36:03 i just wan't prepared for this discussion today 15:36:16 great 15:36:37 if anyone comes up with a good idea/area please let us know 15:36:38 i'll discuss it with you in email 15:36:43 just to give an example, this => https://blueprints.launchpad.net/monasca/+spec/maintenance-periods seems similar to https://blueprints.launchpad.net/monasca/+spec/alarm-silencing 15:37:06 btw, are we still going to finish those bps at the bottom of the list? 15:37:15 tomasztrebski: thanks for pointing out 15:37:42 anqi: probably not 15:37:54 it isn't uncommon to create bps, and then not work on them 15:38:11 in general, that occurs quite often in OpenStack 15:38:16 at least it used too 15:38:18 it's my specialty 15:38:25 lol 15:38:35 :) 15:38:37 that is why i want to sift through it and find something reasonable 15:38:48 well...ideas are ideas, sometimes they don't work out I guess 15:38:54 anqi: u good for today? 15:38:58 and using email? 15:39:16 sorry i cant 15:39:19 could you guys use mailing list to keep everyone else in loop ? 15:39:26 since it's 11:39 pm now 15:39:42 but i will reply you as soon as i get up 15:39:52 tomasztrebski: yes 15:40:05 anqi: ok, will send some ideas your way 15:40:10 rhochmuth: thx 15:40:12 good night 15:40:18 ok :) 15:40:24 sweet dreams :) 15:40:38 haha but i am still at meeting 15:40:48 why you are like sending me to sleep 15:40:56 thanks Kaiyan, aadams and anqi 15:40:56 ups... 15:41:00 will move on to next topic 15:41:05 #topic New owner for monasca-grafana fork 15:41:09 uhhh ohhh 15:41:13 That's mine 15:41:28 Charter has owned the grafana fork with keystone auth. 15:41:37 But we won't be working on Grafana anymore 15:41:42 :( 15:41:45 So we need someone else to take that. 15:42:03 how soon? 15:42:17 and now nightmares 15:42:54 the sooner the better, we're moving on to greener pastures 15:43:17 I can pick that up for now 15:43:17 ok, i'll look for a new home 15:43:33 dhague: awesome 15:43:40 We have sapcc/grafana with our extras on top of rbak's stuff anyway 15:43:42 thank you 15:43:58 dhague: Thanks for doing that. If you need anything from me let me know. 15:44:09 thank you dhague 15:44:11 does it mean transferring twc-openstack/grafana to new home ? 15:44:26 for sure 15:44:43 rbak and bklei: how far did you go with grafana discussion and better integration? 15:44:55 just update the README.md at twc-openstack to refer to sapcc/grafana and we're good 15:44:57 Not much farther than you were involved in 15:44:57 we also have some interest in this area 15:45:01 well, from devstack POV that will be just changing repo URL, so kind of transparent 15:45:29 devstack and docs are probably the only changes we need 15:46:29 dhague: Do you want to make those changes? 15:46:48 Will you guys still be involved in the datasource plugin? My current work may involve extending it 15:47:04 rbak: if you could point me to where to make the changes via email, I'll make it happen 15:47:14 Sounds good, I'll do that. 15:47:40 on a related note, I guess we heard nothing new from Raintank this year? 15:47:43 stevejims no, we'll pull back from that too 15:47:44 stevejims: We won't be involved in grafana at all. The datasource is in the open stack repo though so that should be a problem 15:48:13 One bit of good Grafana news, the monasca plugin is now published and official. https://grafana.net/plugins/monasca-datasource 15:48:29 dhague: Raintank is now Grafana Labs 15:48:39 OK thanks 15:48:51 good news about the plugin being published too 15:49:12 rbak: thanks, that looks good 15:49:33 so, we've been exchanging some emails with Grafna Labs 15:50:10 i'm hoping that we will proceed with additional integration of monasca into grafana 15:50:26 but, we aren't exactly a start-up 15:50:43 so, these disucssion take a litlle time to work through 15:51:09 i'll keep folks informed as we proceed 15:51:29 and now that charter isn't involved, this will be more important 15:52:09 i may revisit this bp as a fallback for our client: https://blueprints.launchpad.net/monasca/+spec/grafana-auth-workarounds 15:53:15 in that case, where does the username/password go 15:53:21 is it in a config file? 15:53:42 in the datasource config screen - it is how the gnocchi datasource works 15:54:07 stevejims: thanks 15:54:25 agree, that might be a good fallback 15:54:29 to have 15:54:51 ok, so are we ok with that topic 15:54:53 I'm happy to take a look 15:55:16 thanks rbak and bklei for all your great work!!! 15:55:36 yes, thank you both 15:55:40 yes, it's a pitty 15:56:29 it's been fun! 15:56:32 thanks dhague for taking it over 15:56:50 yes, it has been fun! 15:57:31 #topic review 15:57:40 https://review.openstack.org/#/c/356403/ 15:57:47 is it ready? 15:57:52 i didn't get to this last week 15:57:54 sorry 15:58:37 tomasz: artur says it is ready to go 15:59:37 I didn't manage to test it last days 15:59:50 i haven't tested either 15:59:57 my next chance will be tonight 16:00:21 i'll also comment on the other two reviews that are competing for who foes first 16:00:27 i think i need to end meeting 16:00:33 will send out mid-cycle details 16:00:40 coordinate with anqi 16:00:43 thanks everyone 16:00:48 ok, thanks anyway :) 16:00:49 thanks rbak and bklei 16:00:49 thank you 16:00:51 thank you 16:00:55 just wanted to get it merged before ocata and/or new features that include db mods 16:01:03 #endmeeting