08:00:18 <ifat_afek> #startmeeting vitrage
08:00:19 <openstack> Meeting started Wed Dec 21 08:00:18 2016 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:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:00:22 <openstack> The meeting name has been set to 'vitrage'
08:00:28 <ifat_afek> Hi everyone!
08:00:33 <eyalb> hi
08:01:16 <elisha_r> hi
08:02:22 <alexey_weyl> hello thereeeee
08:04:31 <ifat_afek> #topic Status and Updates
08:04:47 <ifat_afek> I received a mail that Boston CFP is now open
08:04:54 <ifat_afek> #link https://www.openstack.org/summit/boston-2017/call-for-presentations/
08:05:10 <ifat_afek> We should start thinking about interesting Vitrage sessions for the Boston summit. We can submit proposals until February 6th.
08:05:32 <ifat_afek> Note that as the summits are now split between main summit and PTG, there will not be design sessions in Boston. But – there will be “forum sessions”, which I believe are quite similar.
08:05:50 <ifat_afek> #link https://wiki.openstack.org/wiki/Forum
08:06:29 <ifat_afek> As far as I understood, we should register speaking sessions now, and think about the forum sessions at a later time.
08:07:06 <ifat_afek> Note that our meeting next week will be canceled due to the holidays season. We will meet again on Wednesday, January 4.
08:07:17 <ifat_afek> My updates: I’m working on implementing Vitrage as a Doctor Inspector, specifically on writing a Doctor datasource for Vitrage, that will implement Doctor SB API. Not much progress yet.
08:07:24 <ifat_afek> #link https://gerrit.opnfv.org/gerrit/#/c/12179
08:07:33 <ifat_afek> Who else wants to update?
08:08:08 <alexey_weyl> I will update
08:08:30 <alexey_weyl> I am working on adding a new type of alarm to aodh called generic alarm.
08:08:53 <alexey_weyl> I have pushed blueprint https://review.openstack.org/#/c/408060/
08:09:07 <alexey_weyl> #link https://review.openstack.org/#/c/408060/
08:09:55 <alexey_weyl> and yesterday I have pushed some code to the aodhclient and hopefully to today or tommorow code to aodh itself
08:10:19 <alexey_weyl> I wait for feedbacks from the aodh team to see what they think
08:10:20 <ifat_afek> alexey_weyl: this is great. Did Aodh team review it already?
08:10:26 <ifat_afek> ok
08:10:34 <alexey_weyl> Thats it for now
08:10:50 <ifat_afek> alexey_weyl: thanks
08:12:51 <danoffek> I'm changing Vitrage ID to act as a real ID, derived from Openstack's UUID generating utils. Same as ther services.
08:13:28 <elisha_r> doffek: sounds great. but what will you do about non-openstack entities, such as zabbix alarms?
08:13:29 <ifat_afek> danoffek: great
08:13:51 <elisha_r> sorry, meant danoffek
08:14:32 <danoffek> Every alarm Vitrage generates is "non openstack " alarm.
08:14:42 <danoffek> It still need's it own ID.
08:14:51 <danoffek> AODH has IDs on alarms
08:14:55 <danoffek> Monaska too,
08:15:18 <elisha_r> I know. The question is what to do about IDs for non-openstack entities. A simple solution would be to append the alarm details (name, timestamp) to the resource the alarm is raised on - assuming every alarm has a resource.
08:15:38 <elisha_r> but that might not be the most elegant solution. Food for thought.
08:15:47 <ifat_afek> elisha_r: but why not generate a new UUID/
08:15:49 <danoffek> We have metadata.
08:15:52 <ifat_afek> UUID
08:16:06 <danoffek> We will generate UUID
08:16:26 <elisha_r> oh - perhaps I misunderstood. you want to use the same UUID generating tool? that sounds better
08:17:30 <danoffek> Yup
08:17:33 <danoffek> See example at :
08:17:43 <danoffek> zabbix_vitrage
08:17:57 <danoffek> message_id : uuidutils.generate_uuid()
08:18:03 <danoffek> It's not practical in this context
08:18:05 <nofarsch> can you send a link to gerrit?
08:18:19 <danoffek> but it will be on real IDs
08:19:30 <danoffek> @nofarsch https://review.openstack.org/
08:19:33 <danoffek> Here you go :)
08:19:47 <nofarsch> awesome, thanks
08:19:58 <elisha_r> thanks
08:20:28 <ifat_afek> Anyone else has updates?
08:22:08 <ifat_afek> Or any other issue you would like to discuss?
08:22:28 <nofarsch> danoffek:  I meant a link to that part of code *facepalm*
08:24:51 <danoffek> @nofarsch Once I have something pushed, I'll update. I updated I'm working on it, not "finished".
08:26:07 <nofarsch> I meant the zabbix example, never mind
08:27:35 <danoffek> Vitrage -> datasources -> zabbix -> auxiliary -> zabbix_vitrage
08:28:29 <nofarsch> thanks!
08:29:03 <ifat_afek> Any other issue?
08:29:07 <danoffek> Bye guys
08:29:28 <nofarsch> any new updates about the giraffe?
08:29:59 <ifat_afek> nofarsch: thanks for the reminder :-) I emailed Heidi yesterday about this issue, got no reply yet
08:30:15 <nofarsch> great!
08:30:25 <ifat_afek> I told her we filled the feedback a while ago, and that most of us were not satisfied with the mascot design
08:30:32 <ifat_afek> Now I’m waiting...
08:31:04 <nofarsch> I will look for an update next week :P
08:31:12 <ifat_afek> sure :-)
08:31:49 <ifat_afek> See you next week then
08:31:59 <nbloom> bye :)
08:31:59 <eyalb> bye
08:32:01 <nofarsch> yep, see you
08:32:04 <nofarsch> bye
08:32:11 <ifat_afek> #endmeeting