14:05:29 #startmeeting monasca 14:05:30 Meeting started Wed Nov 1 14:05:29 2017 UTC and is due to finish in 60 minutes. The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:05:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:05:34 The meeting name has been set to 'monasca' 14:05:40 \o/ 14:05:40 hopefully i got the right time slot 14:05:43 o/ 14:05:52 rhochmuth: perfect ;-) 14:05:59 i thought someone else might kick it off today 14:06:17 but at 5 minutes past the hour i started to worry 14:06:48 Hi all 14:06:50 I was waiting for you to start, you were waiting for me ... hahahah 14:06:58 o/ 14:07:05 i was wondering if that is what was going on 14:07:15 deadlock 14:07:55 no agenda is posted today 14:08:18 I have a request for help 14:08:47 ok, please proceed 14:08:58 Witek and myself setup the hands-on for next summit 14:09:21 when? 14:09:34 it would be usefull to have someone else to test it before we go and tell OVH to create 50VMs 14:09:46 before Monday next week 14:10:15 did you create a vm to run in vagrant? 14:10:38 or does it just run in the ovh environment 14:10:53 rhochmuth: the second 14:10:58 thx 14:11:28 there are instructions about how to setup the environment 14:11:42 do you have a link? 14:11:44 copy & pasting in a ubuntu 16.04 works 14:12:38 https://github.com/scanepa/monasca-bootcamp 14:12:54 this contains the most updated jupyter notebook 14:13:01 Hej 14:13:06 cool 14:13:14 https://github.com/witekest/monasca-bootcamp/blob/master/setup/setup_procedure 14:13:33 this ^^ contains the instructuions 14:14:02 we can provide VMs on OVH but we are waiting for OVH to expanda our quota 14:14:12 we are running out of RAM 14:14:33 we already have a ticket open with OVH 14:15:20 hej 14:15:25 I want to add an item to the agenda 14:15:27 rhochmuth: follow the forks and you'll find familiar code 14:15:43 regarding the openstack ansible project and the dependencies into monasca 14:15:45 ok 14:15:53 Neptu_: let me finish 14:16:17 Ive been talking witht he openstack-ansible community (osa) and since no one has claimed the ownership of the repos into this project 14:16:18 if anybody in interest please drop me an email: sc@linux.it 14:16:22 I'm finished 14:16:43 they are marking all as unmaintained 14:16:53 thx sc 14:17:06 so technically that means we are diverging more and more form the openstack-ansible world 14:17:08 Neptu_: I missed this 14:17:49 I think you need to talk with them donno who is the responsable for those repos neigther is not clear 14:18:16 is not clear on the etherpad for the mid cycle or when i ask on the monasca channel no one can really answer me 14:18:46 im heavily use the monasca agent osa repo to deploy the agent as part of the osa install 14:19:13 Neptu_: could you take ownership? 14:19:41 I could I need to ask the team if we want to get that responsability 14:19:51 but certainly im interested 14:20:26 specially because i seem to be the only one using it atm 14:20:28 :D 14:21:09 Neptu_: I used OSA for a while, to create test environment, so I'm interested too 14:21:33 sc maybe we can jump in together what will make it easier 14:21:34 but I don't have time ... 14:22:24 you do the talking i do the coding 14:22:27 Neptu_: drop me an email, this is the best way to remind me things 14:22:29 would be good with an official maintained of deploying the agent... 14:22:39 Neptu_: deal 14:22:40 *way 14:22:49 sc: give me your mail 14:22:56 sc@linux.it 14:23:00 ok 14:23:12 cool domain 14:23:19 rhochmuth: I also have a question 14:23:35 but can wait till the others have finished :) 14:24:01 Neptu_: Are you done? 14:24:09 can we change topics 14:24:26 rhochmuth: pretty much yes 14:24:49 rhochuth: re the Grafana - keystone fork 14:24:59 yes 14:25:00 is this worth picking up? 14:25:07 absolutely 14:25:37 I remember we had a talk about soliciting interest to split this somehow if OP5 would take charge 14:26:01 i think we had talked about adding it to, https://github.com/monasca 14:26:12 but I never heard back from you, it would've been interesting to see how far we got along and not starting from scratch 14:26:15 since we have a monasca organization in github 14:26:19 ...in terms of negotiations.. 14:27:03 how do you believe would be the best way to move this forward? 14:27:40 as we discussed, there are logistical issues coordinating 14:27:52 i will check again to see what can be accomplished 14:28:24 perhaps you and I need to take this offline in a separate discussion? Our intent is also to move this to the monasca github 14:28:27 but in general, these sorts of partnerships present some logistical challenges 14:28:36 sure 14:28:39 sounds good 14:29:07 if you still have my details propose a couple of time slots and I'll make sure at least one of them works 14:29:17 otherwise I can ping you 14:29:21 ok 14:29:35 great, I'm done 14:29:55 are there other topics for todays meeting 14:30:07 yes, 14:30:24 Fouad_Benamrane: you have the floor 14:30:46 I would like to discuss my congestion plugin, https://review.openstack.org/#/c/513391/ 14:30:57 do you have any comments 14:32:10 I looked at it and looks good, I used all my "weekly monasca time" to set up thing for the summit so I still need to test it 14:32:22 it's in my todo list 14:32:33 sc: ok 14:32:35 i haven't looked at the review, but it looks very interesting 14:32:40 i will try and take a look 14:32:51 rhochmuth: thank you 14:32:55 but if sc doesn't have any comments, i'm probably good 14:33:09 looks like a good contribution 14:33:27 i've never considred this before, so this is new ground for me 14:33:44 this is smart idea 14:34:17 rhochmuth: It fits with monasca logic, monitor all compute and VM that could destroy the netwok perfomance 14:34:50 agree 14:35:03 and react (in the future) by limiting their bandwidh or other reaction 14:36:26 I plan to propose a new one for congestion reaction. 14:36:44 Fouad_Benamrane: what do you mean with reaction? 14:37:55 When the congestion is detected and the source is identified, monasca must (based on it alarm config) react to it by taking actions. 14:38:26 Which keeps the performance high 14:40:15 That's it, rhochmuth. 14:40:42 this is something new, I don't remember any other pluigin to do something like this 14:41:00 sc: yes. 14:42:13 I need your support guys to finish it. 14:43:26 should we wrap it up? 14:45:30 yes 14:45:32 nothing from here 14:45:35 so yes 14:45:42 ok, thanks everyone 14:45:46 i'll end the meeting 14:45:50 ty 14:46:06 #endmeeting