07:59:30 #startmeeting vitrage 07:59:31 Meeting started Wed Apr 5 07:59:30 2017 UTC and is due to finish in 60 minutes. The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:59:32 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 07:59:34 The meeting name has been set to 'vitrage' 07:59:36 hio 07:59:41 Hi :-) 07:59:47 Hi! 08:00:45 \0/ 08:03:06 Hi! 08:05:23 Today’s agenda: 08:05:30 • Status and Updates 08:05:37 • Boston Summit 08:05:45 • Open Discussion 08:06:05 #topic Status and Updates 08:06:25 My update: I worked a little on the persistent database design. Checked OrientDB and ArangoDB. I tend to prefer OrientDB – it is more commonly used and has a wider set of features. 08:06:41 While working on this, the question of how to support RCA history was raised again 08:06:50 One of the main goals of implementing a persistent graph DB was to support the RCA history, but it is not clear that this is the ideal implementation 08:07:01 There might be other ways to store and replay the history (e.g. as an event list). 08:07:15 At the moment I’m not sure that we will have the design ready by Pike-1 (the end of next week). 08:08:11 Who else wants to update? 08:08:20 Hi Guys 08:08:23 I'll update 08:08:33 Didn't work on Vitrage ID for some time now. 08:09:03 Got back to it, and after some merge conflict, and partially lost code (my vm died), I'm back to working on passing tempest tests 08:09:14 Once it's done, we have Vitrage ID. 08:09:30 Too bad that you lost your code :-( 08:10:01 Yup, but at least we are back to working on it 08:10:20 So, most of the tempest failures are currently due to the cluster node 08:10:29 What do you mean? 08:11:24 Hello 08:11:24 The vertex ID / Vitrage ID are no longer fixed keys, instead, they are standard UUIDs. Almost all failed tempest tests (a few dozen) are using the previously hard coded cluster vitrage ID. 08:11:26 Fixing it 08:11:28 Hello Friends 08:11:44 Ok, thanks 08:11:51 That's it 08:12:09 Cool. Who else wants to update ? 08:12:43 I'll update. I finished implementing the resource list API and posted to gerrit for review. 08:13:49 #link https://review.openstack.org/#/c/451778/ 08:13:50 Great, I saw that 08:14:12 Your blueprint was already approved, right? (I don’t remember) 08:15:06 let me check.. 08:15:40 Found it 08:15:42 #link https://specs.openstack.org/openstack/vitrage-specs/specs/pike/resource-list-api.html 08:15:52 approved 08:16:02 Great 08:16:07 Any other update? 08:16:14 * yujunz still working on entity equivalence spec https://review.openstack.org/#/c/451216/ 08:16:30 I wonder if I should start coding or wait for final agreement on the spec 08:16:59 Looking 08:18:42 I’m fine with what you wrote 08:18:51 Hi yujunz, i see you have new changes, but i havent looked yet, i will do so today 08:19:04 idan_hefetz: you were the last one to respond 08:19:07 OK, thanks. That's all from me 08:19:20 Thanks 08:19:27 #topic Boston Summit 08:19:34 I submitted four suggestions for Vitrage forum sessions: 08:19:40 #link http://forumtopics.openstack.org/ 08:19:44 (look for Vitrage) 08:19:54 I don’t know when we will get the selection results. 08:20:05 Besides that, I’m working on two presentations: the Vitrage Story and the Vitrage project updates. 08:20:44 We have had some progress with the Vitrage-collectd demo. Intel succeeded to install Vitrage and raise a collectd alarm 08:21:06 Next eyalb and I plan to configure their environment so the alarm will be raised on the right core and be deduced to the vm 08:21:11 That’s it for me 08:21:48 Is anyone here is coming to Boston? 08:22:40 I am :-) 08:23:20 I know that a few other team members plan to come 08:24:16 #topic Open Discussion 08:24:30 Most of Vitrage core developers will be on vacation next week (April 10-17), so I think we should cancel the next meeting on April 12 08:24:38 Any objection? 08:25:37 Ok, I’ll send a cancellation mail 08:25:42 Anything else? 08:26:15 Goodbye then :-) 08:26:21 bye 08:26:22 bye 08:26:27 bye 08:26:36 bye 08:26:38 bye bye 08:26:46 bye 08:26:47 #endmeeting