08:04:03 <ifat_afek> #startmeeting vitrage
08:04:03 <openstack> Meeting started Wed Mar 15 08:04:03 2017 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:04:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:04:07 <openstack> The meeting name has been set to 'vitrage'
08:04:13 <ifat_afek> Hi :-)
08:04:32 <yujunz> Hi
08:04:34 <alexey_weyl> Hi
08:04:34 <eyalb> \o
08:05:28 <elisha_r> hi
08:06:04 <ifat_afek> Today’s agenda:
08:06:09 <ifat_afek> •	Pike Design Sessions
08:06:13 <ifat_afek> •	Status and Updates
08:06:18 <ifat_afek> •	Boston Summit
08:06:23 <ifat_afek> •	Open Discussion
08:06:28 <ifat_afek> #topic Pike Design Sessions
08:06:38 <ifat_afek> I think that the Pike Design Sessions were very successful. Thanks to everyone who contributed!
08:06:48 <ifat_afek> The etherpad with the discussions summary:
08:06:53 <ifat_afek> #link https://etherpad.openstack.org/p/vitrage-pike-design-sessions
08:06:54 <ifat_afek> \
08:07:32 <yujunz> Is the pike roadmap published? I mean the slides shown on the close
08:08:22 <ifat_afek> I wrote it all in the etherpad, but did not publish anywhere else. I guess it belongs in Vitrage wiki page. I’ll update it after the wiki
08:09:06 <yujunz> Got it
08:09:15 <yujunz> Starting on L184
08:09:36 <ifat_afek> Right
08:10:31 <ifat_afek> #topic Status and Updates
08:10:45 <ifat_afek> My updates: Working on Doctor stuff. I finished writing the manual installation instructions, and it was merged
08:10:54 <ifat_afek> I’m almost done with the test script as well.
08:11:03 <ifat_afek> #link https://gerrit.opnfv.org/gerrit/#/c/28593/
08:11:08 <ifat_afek> #link https://gerrit.opnfv.org/gerrit/#/c/28845/
08:11:15 <ifat_afek> Note that Andrea Wisnyei is working on the “real” Vitrage installation guide.
08:11:28 <ifat_afek> That’s it for my updates
08:11:38 <eyalb> I will update
08:12:12 <eyalb> I have been working several days now to fix the puppet-openstack-integration for vitrage
08:12:25 <eyalb> the smoke test failed
08:12:45 <eyalb> I did some fixes in vitrage tempest tests and in the puppet moudle
08:13:22 <eyalb> I am waiting for the changes to be merged to RDO ci system and then I will recheck
08:13:36 <eyalb> hopefully it will work this time :-)
08:13:39 <eyalb> thats it
08:13:45 <ifat_afek> Good luck ;-)
08:15:04 <elisha_r> I'll update for Anna Reznikov
08:15:33 <elisha_r> She pushed a BP for the Vitrage support for SNMP traps. I believe the code was pushed a week or two ago
08:16:54 <yujunz> SNMP traps as a notifier, right?
08:17:19 <elisha_r> For those who don't know, this means that if you activate this feature, you can get SNMPv2 traps sent to locations that the user defines
08:17:47 <elisha_r> yup, it's another notifier
08:18:14 <elisha_r> traps will be generated whenever a vitrage deduced alarm is generated
08:18:32 <elisha_r> not for other alarms
08:18:39 <elisha_r> like Zabbix, nagios etc
08:19:09 <elisha_r> anyhow, this feature should now be fully functional. See the BP for details.
08:19:11 <ifat_afek> Links to Anna’s changes:
08:19:13 <elisha_r> I'm done
08:19:15 <ifat_afek> #link https://review.openstack.org/#/c/437397/
08:19:24 <ifat_afek> #link https://review.openstack.org/#/c/445574/
08:19:30 <ifat_afek> elisha_r: thanks
08:20:22 <ifat_afek> Anyone else has updates?
08:20:29 <yujunz> I will
08:20:40 <alexey_weyl> I am still working on the 'not' operator for the templates and the evaluator
08:20:57 <alexey_weyl> Hopefully it ill be done till the end of the week.
08:21:14 <yujunz> Made some progress on mitmstack. It now supports multiplying the result of `nova list`
08:21:29 <alexey_weyl> I really want to finish it because it takes too much time already
08:22:02 <alexey_weyl> Done
08:22:05 <ifat_afek> alexey_weyl: Great, thanks
08:22:17 <yujunz> Ok, I'll continue
08:22:30 <ifat_afek> yujunz: So you mean it can already return 10000 fake vms?
08:22:47 <yujunz> If you have n vm, mitmstack can return n*m vms for you
08:22:55 <ifat_afek> Cool
08:23:14 <yujunz> #link https://github.com/mitmstack/cheat-the-client
08:23:25 <yujunz> #undo
08:23:27 <yujunz> #link https://github.com/mitmstack/cheat-the-client/blob/master/multiply.py
08:24:23 <yujunz> Currently the it fakes only the 'id'
08:24:23 <yujunz> So we get different 'id' on the faked list
08:24:26 <yujunz> A question on vitrage
08:24:39 <yujunz> does it supports http_proxy for the openstack endpoints
08:25:24 <eyalb> I am not aware of such a feature
08:25:49 <ifat_afek> yujunz: What do you mean exactly?
08:26:16 <yujunz> When vitrage requests vm list from nova, go through http_proxy if env var is set
08:26:26 <yujunz> nova client supports it well
08:26:54 <yujunz> #link https://github.com/mitmstack/cheat-the-client#nova-list-multiplier
08:27:10 <yujunz> Note the difference between first `nova list` and second one
08:27:22 <eyalb> what ever url you define for vitrage in the catalog it will be used
08:27:37 <eyalb> I will check the link
08:27:48 <yujunz> The same url, but go through http proxy
08:28:14 <yujunz> nova client will check the environment var http_proxy to determine how to make the request
08:28:31 <eyalb> no we don't support it
08:28:42 <yujunz> I see
08:28:49 <ifat_afek> yujunz: Is it supported in other projects?
08:28:59 <yujunz> nova client supports it well
08:28:59 <ifat_afek> Except Nova? I mean, is it something common?
08:29:08 <yujunz> I didn't test other
08:29:12 <ifat_afek> Because we were not aware of it
08:29:17 <yujunz> But I assume it is a common feature
08:29:48 <ifat_afek> And what is the goal - do you want Vitrage to call Nova via the proxy? or do you want to call Vitrage via the proxy?
08:30:01 <yujunz> The former
08:30:10 <yujunz> vitrage call nova via proxy
08:30:22 <ifat_afek> I guess in order to make it consistent with the result that mitmstack gets?
08:30:43 <ifat_afek> And to allow mitmstack to mess with the results
08:31:08 <yujunz> Kind of, force vitrage to go through mitmstack to nova
08:31:22 <yujunz> setting http_proxy is easiest to deploy
08:31:36 <ifat_afek> Ok
08:31:45 <ifat_afek> I think I understand
08:32:00 <yujunz> I'll check and submit a patch to support http_proxy in vitrage
08:32:27 <ifat_afek> Ok
08:32:29 <yujunz> It won't be too difficult since it should be supported by most client library
08:32:41 <yujunz> That's all from my side
08:32:57 <eyalb> I think it is supported by the requests library which we use
08:33:11 <eyalb> so maybe it is supported
08:33:17 <eyalb> it needs to be checked
08:33:31 <eyalb> #link http://docs.python-requests.org/en/latest/user/advanced/#proxies
08:33:48 <yujunz> Could be. Not sure about the default behavior.
08:34:45 <ifat_afek> Any other updates?
08:35:34 <usman_> Ifat: is there any comment or suggestion for virtual switch extension in Vitrage?
08:36:44 <ifat_afek> usman_: Hi, I’m sorry but I still don’t have answer. I think the suggestion makes sense, but would like to discuss it with someone else (who is not in the IRC channel now)
08:37:10 <ifat_afek> BTW, you can send it also to the general mailing list with [vitrage] in the title, if you want to hear other opinions
08:37:20 <ifat_afek> And in any case I will reply to your mail soon
08:37:31 <usman_> Ifat: okay thanks
08:38:01 <ifat_afek> Any other issues to discuss before I move on to the next topic?
08:38:45 <ifat_afek> #topic Boston Summit
08:38:54 <ifat_afek> There will be six Vitrage sessions in the Boston Summit!
08:39:01 <alexey_weyl> wohoooooooooooo
08:39:06 <eyalb> \0/
08:39:09 <ifat_afek> Here they are:
08:39:11 <alexey_weyl> Way the go Vitrage!!!
08:39:15 <ifat_afek> #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/17926/beyond-automation-taking-vitrage-into-the-realm-of-machine-learning
08:39:20 <ifat_afek> #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/17737/collectd-and-vitrage-integration-an-eventful-presentation
08:39:26 <ifat_afek> #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/17928/the-vitrage-story-from-nothing-to-the-big-tent
08:39:31 <ifat_afek> #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/17922/advanced-use-cases-for-root-cause-analysis
08:39:35 <ifat_afek> #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/18067/get-hands-on-with-vitrage-the-fault-management-service-for-root-cause-analysis-and-deduced-alarms
08:39:41 <ifat_afek> #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/18595/project-update-vitrage
08:40:09 <ifat_afek> In addition, we can (and should) suggest ideas for the Forum sessions. As far as I understood, a forum session is similar to the fishbowl session we had in Barcelona – a high level discussion, either about cross-project topics, or about a project specific issues
08:40:11 <yujunz> cool
08:40:15 <ifat_afek> #link https://wiki.openstack.org/wiki/Forum
08:40:23 <ifat_afek> I created an etherpad for gathering ideas. Please add yours:
08:40:28 <ifat_afek> #link https://etherpad.openstack.org/p/vitrage-boston-forum-ideas
08:40:55 <ifat_afek> I just created the etherpad, didn’t have time to think of ideas yet…
08:44:40 <ifat_afek> Sorry for not talking, I was writing in the etherpad…
08:45:27 <ifat_afek> Moving on
08:45:35 <ifat_afek> #topic Open Discussion
08:45:44 <ifat_afek> There is one issue I would like to raise – our review policy.
08:46:03 <ifat_afek> Usually we write our comments, and wait for the committer to fix them
08:46:12 <ifat_afek> On other OpenStack projects, people write -1/-2 when they have comments. This prevents other reviewers from mistakenly merging a change that is not ready yet
08:46:24 <ifat_afek> I think we should start replying with -1/-2 as well. What do you think?
08:46:31 <eyalb> +1
08:46:49 <eyalb> use more -1
08:46:50 <alexey_weyl> I agree
08:46:53 <alexey_weyl> +1
08:47:02 <eyalb> -2 is rarely used
08:47:32 <alexey_weyl> unless it is a very small issue I believe we can use 0 as well
08:47:44 <alexey_weyl> In my opinion
08:49:12 <ifat_afek> Ok. That’s it for me. Anyone wants to discuss anything else?
08:50:57 <ifat_afek> Goodbye then!
08:51:05 <eyalb> bye
08:51:05 <alexey_weyl> see ya
08:51:13 <usman_> bye
08:51:25 <ifat_afek> #endmeeting