08:00:19 #startmeeting vitrage 08:00:20 Meeting started Wed Feb 1 08:00:19 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:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:24 The meeting name has been set to 'vitrage' 08:00:32 hi 08:00:48 \o 08:01:06 hi everyone! 08:01:14 Hi guys 08:04:29 Today’s agenda: 08:04:38 • Ocata Release 08:04:42 • Status and Updates 08:04:47 • Pike Design sessions 08:04:54 • Boston CFP 08:05:02 #topic Ocata Release 08:05:56 Last week I tagged vitrage modules: 08:06:01 vitrage 1.4.0 08:06:07 python-vitrageclient 1.1.0 08:06:12 vitrage-dashboard 1.1.0 08:06:29 For each module, I incremented the minor release number. A major release should be incremented only in case we break an API, which we didn’t (We modified the format of the static datasource, but in Ocata we are still supporting the old format). 08:06:50 Yesterday I added release notes for all the important features we had in Ocata. Please go over my changes and make sure I didn’t miss anything important: 08:06:57 #link https://review.openstack.org/#/c/427311/ 08:07:02 #link https://review.openstack.org/#/c/427130/ 08:07:08 #link https://review.openstack.org/#/c/427121/ 08:07:33 Tomorrow I’m going to tag Vitrage release candidate, and ask to create stable/ocata branches 08:07:53 After that, we will be able to push to Ocata only bug fixes. The master will be used for Pike development 08:08:03 The full Ocata schedule can be found here: 08:08:09 #link https://releases.openstack.org/ocata/schedule.html 08:08:20 Any comments regarding the release process? 08:08:48 Hi Vitrage people :) 08:09:22 #topic Status and Updates 08:09:33 I sent you the new Giraffe illustration I got, but only a few responded. I assume it means the Giraffe is ok 08:09:45 ;-) 08:10:38 My updates: I was mostly busy with release issues and with Boston CFPs. 08:10:48 I did not progress with Doctor. I still need to modify Doctor’s test script so that it will test Vitrage in a similar way to the Congress test. 08:11:10 Other tasks I have for Doctor – document how Vitrage can be manually installed in OPNFV environment, and also backport the new “event post API” to Newton… as OPNFV D-release is based on OpenStack Newton. 08:11:39 Another issue is regarding Aodh. As you might have noticed, we are in continuous discussions with them about the Aodh-Vitrage integration 08:11:45 I don’t have anything to add, but if you are interested then follow the mails in this subject 08:11:58 Who else wants to update? 08:12:08 i will update 08:12:43 spec file for vitrage was merged in rdo 08:12:53 cool!!! 08:13:14 I uploaded also the initial spec file for the vitrage-dashboard 08:13:20 still need to work on it 08:13:43 I still need to update the rdo.yaml for newton and ocata 08:13:57 it fails now 08:13:59 What is the rdo.yaml? 08:14:19 it a yaml files that describe the version supported 08:14:29 it was under review for vitrage 08:14:35 Ocata is not supported yet. We will branch tomorrow 08:15:11 I changed it to support ocata and newton 08:15:29 Great 08:15:34 thats all 08:15:49 I think we might be able to start and progress with the TripleO installation and Apex 08:16:03 At least for Doctor tests scripts, they do not need the vitrage-dashboard 08:16:09 I hope so :-) 08:16:10 And the installer is very important for them 08:16:15 These are great news 08:16:50 I finished the collectd and pushed the code 08:17:10 still waiting to be merged because of a gate problem 08:18:23 Updating on behalf of alexey_weyl, who can not join now: he is trying to fix the gate problem now. The problem is that we stopped getting notifications from Cinder 08:18:59 my update 08:19:09 I pushed some changes to the processor, allowing for interchangeable graph class for the entity graph 08:19:14 #link https://review.openstack.org/#/c/425592/ 08:19:19 #link https://review.openstack.org/#/c/423976/ 08:19:27 This will allow for future additions of graph driver implementations supporting different databases. 08:19:34 New configuration in the conf - entity_graph/graph_driver can be used, default (and currently only option) is networkx. 08:19:42 To add more options, use the setup.cfg file and specify the desired class. 08:20:17 idan_hefetz: This is great. Hopefully we will add an alternative graph database, which is persistent, in Pike 08:20:37 Anyone else wants to update? 08:21:44 I have an update... 08:23:14 I pushed 2 days ago fix for the entities graph to show an updated alarm 08:24:07 And we had a critical issue, that the UI wasn't functional. That was because of Horizon updated their Angular-UI botstrap xstatic package. 08:24:12 I fixed it also 08:24:16 That's all 08:24:29 Alon: thanks 08:24:47 Anyone else? 08:26:14 #topic Pike Design Sessions 08:26:29 We will hold Pike Design Sessions in Israel, on the week of March 6th. You are all invited to participate and to suggest topics for the discussions 08:26:57 Per ZTE request, we will hold some of the design sessions in hours that are suitable for China, so some of our colleagues from ZTE can participate remotely. It means that the design sessions will be not only on March 6th-7th, but also on Marth 8th-9th around 7:00-9:30 UTC 08:27:14 The design session etherpad: 08:27:20 #link https://etherpad.openstack.org/p/vitrage-pike-design-sessions 08:27:34 Any comments regarding the design sessions? 08:28:29 #topic Boston CFP 08:28:53 Boston CFP is still open until February 6th 08:29:04 #link https://www.openstack.org/summit/boston-2017/call-for-presentations/ 08:29:10 #link https://etherpad.openstack.org/p/vitrage-boston-session-proposals 08:29:24 If you have other ideas, you can still suggest them 08:29:36 Any other issues you would like to discuss? 08:31:08 See you next week :-) 08:31:23 bye 08:31:43 thanks, bye 08:31:52 #endmeeting