15:01:24 #startmeeting monasca 15:01:25 Meeting started Wed Jan 27 15:01:24 2016 UTC and is due to finish in 60 minutes. The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:30 The meeting name has been set to 'monasca' 15:01:35 o/ 15:01:37 bye .. 15:01:39 hello 15:01:42 hi 15:01:53 o/ 15:01:54 o/ 15:02:01 hi everyone 15:02:10 we have a pretty light agenda today 15:02:12 Agenda for Wednesday January 27, 2016 (15:00 UTC) 15:02:12 1. Is monasca-common published automatically to pypi ? 15:02:30 So, I'll open it up for discussion after we cover that item 15:02:45 #topic monasca-common 15:02:58 Currently, it is not published to pypi 15:03:06 that needs to get resolved 15:03:51 Is this urgent for someone to resolve? 15:05:05 0.0.4 is there 15:05:14 it is? 15:05:22 https://pypi.python.org/pypi/monasca-common/ 15:05:45 interesting, i thought it was in pypi 15:05:55 then i looked at the catalog and i cant' find it 15:06:03 so i thought i was wrong 15:06:10 but pip install works 15:06:15 and it is listed 15:06:27 so, is this just a catalog issue? 15:06:44 Is it just the pypi index/catalog isn't listing it 15:07:54 If you search for monasca-common it isn't listed 15:09:35 So, my guess is something is not completely correct, but it is in pypi 15:09:47 OK, next topic 15:09:56 I searched now, but I can't see list neither. 15:10:01 Are there other items to cover today 15:10:27 I can give a grafana update 15:10:37 #topic grafana 15:10:58 I've put up the fork with keystone authentication here: https://github.com/rbak1/grafana 15:11:06 I know some people found that already. 15:11:36 I've also solved using that authentication to provide tokens for the data source, so this is close to being done. 15:11:47 i have taken it and i have keystone v3 basically working already 15:11:51 wasn't there a directory for grafana-plugins 15:11:55 I sent an email to grafana to start talking about getting this upstream 15:12:08 how is that going 15:12:23 Haven't heard back on that, I only sent the email last night. 15:12:43 But it's getting close. 15:13:03 so, does this directory include all your code 15:13:13 tgraichen: Just submit a pull request on my branch once your v3 keystone auth is ready 15:13:15 wasn't there a grafana-plugins repo 15:13:18 #link https://github.com/rbak1/grafana Grafana fork 15:13:48 There is a separate https://github.com/rbak1/grafana-plugins repo which has the grafana datasource 15:13:53 i see one little thing for keystone v3 - for that we would need another input for the domain name in the login screen ... so far i have hardcoded the domain via config option 15:14:40 Also worth noting, the format for datasource plugins changed again. 15:15:07 rbak: is your code to use the token from auth for the datasource in the tree already? 15:15:08 So if anyone is having trouble with the latest code working with the monasca plugin, I do have a patch for that 15:15:51 tgraichen: Not yet. I haven't quite finished it, I just managed to prove I could do it yesterday. 15:15:59 so, if i pull your latest repo, does it work, or do i need the patch 15:16:36 If you install the latest release of grafana you can use the monasca datasource in grafana-plugins 15:16:48 If you pull the latest code and build, you'll need my patch 15:17:24 I'll put it up at some point, but I didn't want to mess up anyone who was using the datasource with the latest release 15:17:44 maybe we should move the monasca plugin into the grafana tree as well until we are merged to grafana upstream? 15:18:00 Sounds reasonable. I'll do that after the meeting. 15:18:40 cool - thx ... and big thx for your keystone v3 preparations in the code - it was quite easy to add by filing the gaps you left 15:18:42 I'll leave the monasca-plugin fork with the code for the latest release, and but the fully up to date monasca code in the grafana fork 15:19:18 sounds very good - will create a pull request with my keystone v3 stuff later today 15:19:28 Sounds good 15:19:41 I think that's all I had 15:19:48 thx rbak 15:20:33 #topic midcycle 15:20:45 i just want to mentiont again that the midcycle is next week 15:20:50 it will be remote via webex 15:21:00 The Agenda, data, time and location is at 15:21:01 https://etherpad.openstack.org/p/monasca_mitaka_midcycle 15:21:17 I'm the only attendees listed right now 15:21:29 It would be good if folks start filling out information 15:21:37 in the agenda section 15:21:50 I see some items related to send sms 15:21:57 and add to skype 15:22:10 so, those topics seem to be related to the notificatino engine 15:22:25 the other items listed are the logging api and performance 15:22:48 so, please fill out the etherpad with topics that you would like to cover and i'll try and organize 15:23:04 is there any conditions to join the mid-cycle? (so far i didn't contribute monasca...) 15:23:17 ho_away: there are no conditions 15:23:20 it is open to anyone 15:23:28 so your topic of anomaly detection would be a good one 15:23:31 rhochmut: cool! 15:23:47 i saw your email posting 15:24:09 i think there was only one other response asking questions around the current status of it 15:24:22 rhochmuth: yeah, i tried to get someone's interest but it failed :-) 15:24:23 current status of the monasca anomaly prediction engine 15:24:38 lol 15:24:58 well, there were some folks last week that seemed interested 15:25:02 and then there is me 15:25:39 so, if you woudl like i can go over what i've done and we can share ideas 15:26:00 i'm interested in hearing what your ideas in this area are 15:26:06 rhochmuth: really? it's appreciate 15:26:48 rhochmuth: we have some POC around IT analytics but it's not related to monasca now 15:27:12 ho_away, so please add an agenda item 15:27:23 and we can start discussions next week 15:27:27 rhochmuth: to mid-cycle? 15:27:31 yes 15:27:57 rhochmuth: i will add it :-) 15:28:01 thx 15:28:18 please also feel free to start sharing ideas via email or the openstack-dev list 15:29:10 rhochmuth: thanks! if i get no response, i might get big damage... :-) 15:29:30 well, we can talk next week 15:29:41 yep 15:29:44 so, are there other topics 15:29:54 are there reviews folks want me to llok at 15:30:08 we've recovered from the CI problems we had last week 15:30:15 so, i'm trying to catch up on reviews 15:30:24 we have a lot of outstanding ones 15:31:27 witek: Did you every look at all the reviews and pull requests to the ansible changes, that i was having trouble with 15:32:02 yes, i'm testing it 15:32:06 witek: https://review.openstack.org/#/c/251893/ 15:32:09 cool 15:32:11 i had problems with smoke tests 15:32:26 had to downgrade monasca-notification 15:32:31 hmmm, i was seeing different problems 15:32:48 let me know if you want me to test that again 15:33:10 yes, I will let you know, when I'm done 15:33:35 Also, i see that you have a proposal for the log apu batching up 15:33:37 https://review.openstack.org/#/c/273058/1/docs/monasca-log-api-spec.md 15:33:53 tsv and his team did some performane analysis 15:34:00 it's a follow-up after the chaotic discussion last week :) 15:34:09 thanks 15:34:28 tsv's analysis shows > 12X improvement going to batch 15:34:47 yes, i can believe that 15:36:07 so, if anyone wants/needs some reviews bumped up let me know and i'll see what i can do now that we are getting out of the mess we were in past week 15:36:49 we don't have restrictions in requirements any more 15:37:01 correct 15:37:07 i'm not sure, but it could be, we monasca-vagrant is not working now 15:37:22 i'm not sure, but it could be, why monasca-vagrant is not working now 15:37:42 i wasn't aware monasca-vagrant was broken 15:37:50 i'll need to take a look 15:37:57 but, that could be the reason 15:38:03 monasca-notification does not start 15:38:21 after downgrade it does 15:38:43 i'll verify here 15:39:02 nice, thanks 15:39:54 ok, i think we are done for the day 15:40:03 see everyone next week 15:40:20 thank you Roland 15:40:23 see you 15:40:36 thanks! 15:40:51 see you 15:41:13 #endmeeting