09:00:51 #startmeeting vitrage 09:00:51 Meeting started Wed May 4 09:00:51 2016 UTC and is due to finish in 60 minutes. The chair is ifat_afek_. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:52 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:54 The meeting name has been set to 'vitrage' 09:01:05 Hi!! 09:01:20 he everyone :-) 09:01:24 Hi 09:02:30 hey 09:02:50 Hello guys ;) 09:03:27 hi all.. long time :) 09:04:45 hi everyone 09:04:59 hi 09:05:23 Our agenda today will be slightly different: 09:05:46 * Austin recap, by alexey_weyl and Ohad 09:05:52 * Newton release planning 09:06:15 Before we begin – we are going to move Vitrage IRC meeting one hour earlier, to 8:00 UTC. It will be on a different channel. We will send an update email with the final details. 09:06:33 #topic Austin recap 09:06:50 hi 09:07:12 update from Austin: 09:07:34 Great week for Vitrage! we introduced Vitrage to the OpenStack community and we got very positive feedback. thanks for everyone for the hard work before the summit, everything worked perfect and very stable. 09:08:51 Activities: 09:09:16 1. sessions: we had 2 sessions: 09:10:02 (a) Project Vitrage How to Organize, Analyze and Visualize your OpenStack Cloud I presented Vitrage and Alexey did a great live demo including switch failure coming from Nagios and CPU failure from AODH.of course both use cases included raising deduced alarms, deduced states and showing root cause analysis. 09:10:18 #link https://www.youtube.com/watch?v=9Qw5coTLgMo 09:10:48 (b) On the Path to Telco Cloud Openness: Nokia CloudBand Vitrage & OPNFV Doctor collaboration Gerald.K from Doctor OPNFV project presented Doctor requirements for fault management and I presented Vitrage 09:11:04 #link https://www.youtube.com/watch?v=ey68KNKXc5c 09:11:57 2. Vitrage Booth: we had a booth in the market place. we did a lot of live demos (3-5 demos every hour!) and again we got very good feedback. 09:14:40 I think ohad was disconnected... 09:15:02 hi 09:15:53 3. Meetings: 09:16:04 (a) design session with AODH 09:16:46 alexey_weyl: can update on our meeting with AODH? 09:16:53 Yes, of course 09:17:16 First of all, we can see here the summary of the design session with AODH in the etherpad 09:17:18 https://etherpad.openstack.org/p/newton-telemetry-vitrage 09:17:33 #link https://etherpad.openstack.org/p/newton-telemetry-vitrage 09:17:50 A quick update about all the details 09:18:17 1. We have talked with the team about adding external notifications from aodh 09:18:54 They agreed that such a feature needs to be in AODH, and they might even have that, they only need to understand how to configure it 09:20:06 2. Alarm name uniqueness - In aodh 2 alarms with the same name can't be defined. They said that this was a Wrong API feature, and that we can send them a patch to change it 09:21:07 3. New alarm type - We have showed to aodh that we need a new alarm type in aodh ("custom alarm"), so Vitrage will be able to push new alarms to aodh 09:21:14 which aren't event or threshold 09:21:52 they agreed as well that we should have such an alarm, and that we should contribute it to AODH 09:22:27 In addition, we have explained the team about Vitrage and showed the a demo of 2 use cases of Nagios and aodh alarms 09:22:34 That's it for now 09:22:54 sorry, I had connectivity issue 09:23:13 thanks 09:23:48 (b) Doctor OPNFV project - we have discussion to kick off preparations for the joint booth demo planned for OPNFV summit in Berlin in June. 09:25:03 (c) Monasca - discussion on possible integration for Newton. Monasca can be additional data source for Vitrage. we will continue to work together on this. 09:25:26 (d) Congress - discussion on possible integration for Newton. 09:25:36 I will add some more 09:26:16 We also had a meeting with the OPNFV \ NFV team in Red Hat 09:26:45 It was a good meeting, we showed and explained them about Vitrage, and they were really excited about that 09:26:54 Had very good feedbacks as well 09:27:19 ohad, alexey_weyl: sounds great! thanks for the update 09:27:34 #topic Newton release planning 09:27:50 Since there was no Vitrage design session in Austin, we are going to use the next one-two meetings for the planning. I opened an etherpad for this purpose: 09:28:05 #link https://etherpad.openstack.org/p/vitrage-newton-planning 09:28:31 Also, everyone is welcome to add blueprints in our lanuchpad: 09:28:39 #link https://blueprints.launchpad.net/vitrage 09:29:17 go ahead and add stuff :-) I wrote just a few 09:29:27 i will add another task: 09:29:27 Multi-tenancy support - Admin adds templates, tenants can have a view only of tenant scope 09:30:02 another one: Overlapping Templates Support (critical usability improvement) 09:30:53 I want to update that we pushed code to fix python 3.4 support 09:31:08 both vitrage and vitrage client 09:33:28 I added puppet installation 09:33:40 Heat plugin for Vitrage 09:34:38 I would add support of multiple transformers to one datasource 09:34:57 I mean requirement for support of multiple transformers to one datasource 09:35:22 emalin: sure, you can edit our etherpad directly. I sent a link earlier 09:35:32 https://etherpad.openstack.org/p/vitrage-newton-planning 09:39:10 ifat_afek_ 10x 09:39:51 Looks good :) 09:39:52 it's a good start, let's continue to fill it and agree on the plan for Newton in the next meeting 09:42:49 Coming along nicely - nice and colorful etherpad :) 09:43:21 lots of work :-) Newton release will be interesting 09:44:21 cool, so let's take the time to think about it, and continue the discussion next time. I'll send a link to openstack ML, so other people might add their ideas 09:44:28 #topic Open Discussion 09:44:43 anyone wants to raise anything? 09:45:01 if not - then I have an issue 09:45:31 we should consider when would be a good time to apply to the TC and ask them to accept Vitrage as an official project 09:45:39 your thoughts? 09:45:45 I feel we are ready :-) 09:46:06 Sounds great :) I think we are on the right path :) 09:46:12 +1 09:46:24 we are more than ready 09:46:28 +1 09:46:33 +100 09:47:17 ok, if you are all for it, then I'll check the exact procedure and update you next week 09:47:22 any other discussions? 09:48:13 so I guess we are done. goodbye everybody 09:48:34 bye 09:48:55 #endmeeting