08:00:56 <ifat_afek> #startmeeting vitrage
08:00:57 <openstack> Meeting started Wed Apr 26 08:00:56 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:58 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:01:01 <openstack> The meeting name has been set to 'vitrage'
08:01:06 <ifat_afek> Hi everyone :-)
08:01:20 <eyalb> \o/
08:01:40 <alexey_weyl> Hello
08:01:58 <dwj> hi
08:04:15 <ifat_afek> Today’s agenda:
08:04:20 <ifat_afek> •	Status and Updates
08:04:25 <ifat_afek> •	Boston Summit
08:04:33 <ifat_afek> •	Open Discussion
08:04:46 <ifat_afek> #topic Status and Updates
08:05:01 <ifat_afek> I’m only working for the Boston summit, so I’ll update later
08:05:19 <ifat_afek> I know that danoffek has updates, but he will join the meeting a little late
08:05:29 <ifat_afek> Anyone else has updates that are not related to Boston?
08:05:40 <eyalb> yes
08:05:58 <eyalb> I am working on a bug in ocata release
08:06:32 <eyalb> all tempest jobs started failing in ocata
08:06:53 <eyalb> i am trying to figure out what happened
08:06:59 <eyalb> a hard one :-(
08:07:05 <eyalb> thats all
08:07:10 <yujunz> What changed? dependency ?
08:07:13 <ifat_afek> Too bad… thanks for your help
08:07:21 <eyalb> probably
08:07:22 <eyalb> yes
08:08:04 <yujunz> Is is possible to freeze the dependency when stable branch is created?
08:08:26 <ifat_afek> yujunz: As far as I understand, the dependencies change only if we approve them
08:08:34 <ifat_afek> So maybe we should look at the log to see the changes
08:09:02 <eyalb> we didnt do any change
08:09:17 <eyalb> last success build was 9 march
08:09:24 <yujunz> But I saw things like
08:09:24 <yujunz> sympy>=0.7.6 # BSD
08:09:43 <eyalb> and then tests started failing randomly
08:09:45 <yujunz> So it will upgrade to latest version during CI
08:10:04 <eyalb> no we use upper constraints when installing
08:10:33 <yujunz> OK, from global-requirements ?
08:10:38 <eyalb> yes
08:11:16 <yujunz> OK. Hope we can get it resolved soon
08:11:50 <ifat_afek> Right…
08:11:57 <ifat_afek> Anyone else wants to update?
08:12:35 <yujunz> Almost finish the supporting job for OPNFV plugfest, I think I can start working on vitrage now. That's all.
08:12:55 <ifat_afek> Are you in the plugfest now? or is it next week?
08:13:25 <yujunz> The plugfest is ongoing and I'm supporting them remotely :-)
08:13:34 <ifat_afek> Cool
08:13:50 <ifat_afek> Anyone else, before we move to Boston topic?
08:14:56 <ifat_afek> #topic Boston Summit
08:15:07 <ifat_afek> I’m still working on two presentations: the Vitrage Story and the Vitrage project updates.
08:15:22 <ifat_afek> Regarding the session with Intel, I got a presentation draft from Maryam Tahhan, and added Vitrage slides to it. I’m waiting for her feedback.
08:15:38 <ifat_afek> I’m also waiting to get access to the Intel new demo environment, so we can configure Vitrage there.
08:15:49 <ifat_afek> Another issue that I started working on is the integration with Mistral.
08:15:59 <ifat_afek> I managed to install Mistral, now I need to configure a workflow and write a POC Mistral notifier that executes it
08:16:07 <ifat_afek> I hope I’ll be able to finish it by tomorrow, as Maryam wants to start recording the demo
08:16:22 <ifat_afek> That’s it on my side. Who else wants to update regarding Boston?
08:17:16 <alexey_weyl> I will update
08:17:35 <alexey_weyl> I have finished to work on the advanced use cases demos.
08:17:40 <alexey_weyl> Everything is working.
08:17:50 <ifat_afek> Cool :-)
08:18:18 <alexey_weyl> thats it
08:19:46 <danoffek> Hi guys. Sorry I'm late. I'd like to update
08:20:03 <danoffek> It's not about Boston.
08:20:17 <danoffek> Vitrage ID feature is finally pushed.
08:20:32 <danoffek> I'd like to explain a little about the feature.
08:20:35 <ifat_afek> Yay!
08:20:42 <danoffek> Thanks.
08:20:56 <adary> and i'm here as well now. whee
08:21:34 <danoffek> So, until now Vitrage ID "str" was created by
08:21:53 <danoffek> connecting different properties to one another from the entity
08:22:15 <danoffek> For example, it could be the resource type, category, name, all connected to each other to one long "str"
08:22:28 <danoffek> Same with graph's Vertex ID
08:22:47 <danoffek> So if you'd like to question vitrage via API about a specific machine
08:23:11 <danoffek> you could just build the ID on your side, and then send it to vitrage, and get the machine
08:23:17 <danoffek> This is no longer the case.
08:23:28 <danoffek> Vitrage ID is now a standard Openstack UUID
08:23:55 <danoffek> generated by UUIDUtils.generateUUID (as far as I can remember)
08:25:06 <danoffek> This will also help save history data once we have a persistent DB, since otherwise, same alert, that would happen in 2 different hours, would be saved as the same alert on Vitrage.
08:25:35 <danoffek> Now it will have another UUID, enabling it to be saved as a different entity in the graph, while keeping the same properties as the other alert.
08:26:19 <danoffek> That's it, unless there are questions on this issue.
08:26:44 <ifat_afek> danoffek: Thanks! it’s an important fix
08:27:02 <yujunz> Is it backward compatible?
08:27:21 <yujunz> Or since we don't have persistent db at the moment, it is not an issue
08:27:31 <danoffek> You got it :)
08:27:44 <yujunz> Thanks
08:27:59 <yujunz> It is important to get it done before persistent db
08:28:08 <danoffek> It's done
08:28:25 <danoffek> or "dan" in this case ;)
08:28:32 <ifat_afek> Right, once we have the persisntent DB we will need to start talking about upgrades…
08:28:39 <yujunz> Well "dan" :-)
08:28:46 <ifat_afek> Dan is Done ;-)
08:28:47 <danoffek> thanks
08:29:20 <ifat_afek> Any other updates, regarding Boston or else?
08:30:29 <ifat_afek> #topic Open Discussion
08:30:42 <ifat_afek> Switched the topic just in case… anything you would like to talk about?
08:32:50 <ifat_afek> Let’s end the meeting
08:32:56 <ifat_afek> Bye :-)
08:33:02 <eyalb> bye
08:33:21 <ifat_afek> #endmeeting