09:00:58 #startmeeting vitrage 09:00:59 Meeting started Wed Jan 27 09:00:58 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:01:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:01:03 The meeting name has been set to 'vitrage' 09:01:17 Hi everyone :-) 09:01:36 hi all :) 09:01:59 hello 09:02:35 Hi 09:03:23 Hi 09:05:42 hi 09:05:48 hi 09:06:06 hi 09:06:10 #topic Current status and progress 09:07:25 I don’t have many updates today 09:07:36 hi 09:07:46 I started checking Aodh solution that gordc suggested when I talked with him on their IRC channel. Still in progress 09:07:51 hi 09:08:06 updates anyone? 09:08:12 I will update 09:08:35 I added tests to the vitrage api 09:08:47 at the moment only get version 09:09:01 will add the get topology later 09:09:32 Hello :) 09:09:37 with authentication later 09:09:46 that it 09:09:52 great, thanks 09:09:52 My update: Liat and I worked on the Vitrage Template (for RCA and deduced alarms, etc.) format, and uploaded it to github for review. 09:10:09 looks good, I already reviewed it 09:10:24 let's wait for other reviews before we approve it 09:10:47 Got a few comments over the past few days, which will be updated there as well, hopefully in the next few days 09:11:09 sure. will wait to get more before approving. 09:11:20 that's it 09:11:29 I will update 09:12:00 we add installation process for vitrage-dashboard in devstack 09:12:03 thanks elisha_r 09:12:04 I think we should start to work on it.. no need to wait for approving 09:12:22 omer_etrog: cool! this is an important progress 09:12:45 lhartal: right. you can start working, and if there are minor changes in the design you can change it later 09:13:16 omer_etrog: any other updates on the ui? 09:14:08 lhartal: I agree 09:14:31 sorry, need to check the installation of python-vitrage in horizon 09:14:55 I have no updates today 09:15:07 emalin: thanks 09:15:41 Alon is adding Legend to the sunburest 09:16:07 and I`m done.. 09:16:17 omer_etrog_: thanks 09:16:24 who else wants to update? 09:16:45 me 09:16:57 I want 09:17:03 We have published our first use case demo 09:17:19 You can find it in Vitrage Wiki 09:17:34 alexey_weyl: cool!! 09:17:46 do you have a link? 09:18:00 alexey_weyl: you can write it with #link in the beginning 09:19:05 my updates: last week I worked on new design for the transformers 09:19:27 I did a POC and it looks very good 09:19:37 the main idea is that the transformers will be a YAML configuration files (instead of python code) 09:19:52 a transformer engine will load the files, parse them and create Entity Transformer object (per transformer file) 09:20:07 the problem was when we needed to add logic to each transformer. This makes the change too complicated and it requires to create a new blueprint 09:20:31 it becomes a complicated change requires us to open blueprint 09:20:40 lhartal: do you have an example for such a logic? 09:21:07 yes 09:22:18 when the value is composed of several fields 09:22:42 when the key is the value itself 09:23:07 when the path to the vallue is dynamic 09:23:25 lhartal: ok... makes sense to create a blueprint indeed 09:24:05 Also I started to work on loading the templates files into vitrage 09:24:17 thats all :) 09:24:20 lhartal: thanks 09:24:23 The first tempest test for graph waiting in git review for approve 09:24:36 mkoushnir: great!! 09:26:53 next step is e2e scenario - with real setup or simulator - create several instanses and hosts - create graph and full validation 09:27:13 mkoushnir: this is an important step. we must have these tempest working in order to say we really completed a use case 09:27:34 once the first one-two tests work, other people might write more tempest tests 09:27:55 any other updates anyone? 09:29:25 ok, let's move on 09:29:27 #topic Review action items 09:29:43 • ifat_afek continue discussions with Aodh 09:29:47 this is in progress 09:30:13 #action ifat_afek_ check aodh integration and update the blueprints 09:30:27 • finalize get topology API 09:30:39 we are waiting for PinPoint response. No action on our side for now 09:30:48 #topic Next Steps 09:31:23 I think it's a good time to review our next use case, go over the blueprints, and re-prioritize them 09:31:54 I agree with you 09:32:02 so do i :-) 09:32:24 #action review our use cases, blueprints and priorities 09:34:13 yes I agree, we need to start work on plug-in for Nagios and HW failures such as switch failure, etc 09:34:34 Ohad: right 09:34:39 #topic Open Discussion 09:35:00 anything someone wants to talk about? 09:36:12 so I guess we are done for today 09:36:29 goodbye everybody 09:36:53 bye 09:37:35 bye 09:38:12 #endmeeting