08:00:44 <ifat_afek> #startmeeting vitrage
08:00:45 <openstack> Meeting started Wed Nov  9 08:00:44 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:46 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:00:49 <openstack> The meeting name has been set to 'vitrage'
08:01:02 <ifat_afek> Hi everyone :-)
08:01:40 <idan_hefetz> Hi!
08:01:58 <danoffek> Hi guys
08:04:32 <ifat_afek> #topic Status and Updates
08:04:42 <ifat_afek> I’m working on arranging Vitrage documentation.
08:04:55 <ifat_afek> I want to update vitrage-specs page. Please go over my change:
08:05:03 <ifat_afek> #link https://review.openstack.org/#/c/394550/
08:05:14 <ifat_afek> This is how the page looks like at the moment, with only Mitaka blueprints:
08:05:21 <ifat_afek> #link https://review.openstack.org/#/c/394550/
08:06:03 <ifat_afek> Another change I’ve made is to publish vitrage documentation under http://docs.openstack.org/developer/vitrage . I’m waiting for the infra to approve my change:
08:06:11 <ifat_afek> #link https://review.openstack.org/#/c/394550/
08:06:38 <idan_hefetz> The developer/vitrage link
08:06:43 <idan_hefetz> does not work
08:06:52 <ifat_afek> of course… this is the change I am trying to make
08:07:15 <ifat_afek> all other official projects have their developer guides in this site. I want to add vitrage as well
08:07:27 <ifat_afek> sorry for resending the same link few times…
08:08:04 <ifat_afek> this is vitrage-specs:
08:08:06 <ifat_afek> http://specs.openstack.org/openstack/vitrage-specs/
08:08:20 <ifat_afek> and this is the change for adding vitrage developer guide:
08:08:33 <ifat_afek> #link https://review.openstack.org/#/c/394181
08:08:58 <idan_hefetz> Cool!
08:09:06 <ifat_afek> in addition, I plan to start going over some gerrit issues that are open for a while. We need to decide what to do about them.
08:09:42 <ifat_afek> will be happy to get help on that :-)
08:10:17 <danoffek> I'll update for @noambloom
08:10:35 <idan_hefetz> I can help with that, let me know which ones
08:10:37 <danoffek> Noam is continuing to develop templates list / show ui
08:10:45 <ifat_afek> idan_hefetz: great, thanks
08:10:58 <danoffek> In the details (show) options, there are now 2 viewing options :
08:11:24 <danoffek> Simple view, for quick reference
08:11:46 <danoffek> Yaml view, which is the exact representation of the Yaml file
08:12:17 <danoffek> In addition, Simple view has been adapted to handle large template files.
08:13:02 <danoffek> It's the same as a tree (file manager) representation, to enable seeing the "macro"
08:13:30 <danoffek> To see inner branches (inner details) you click the node.
08:13:44 <danoffek> That's a very cool feature added by NoamBloom
08:14:06 <ifat_afek> danoffek: thanks for the update!
08:14:25 <elisha_r> hi - sorry for being late
08:16:48 <elisha_r> So, I'll just update
08:17:53 <elisha_r> Eyal could not join today, but he's been making progress in getting the Vitrage RDO approved.
08:18:39 <elisha_r> Once this is done, installing Vitrage via puppet in the standard manner will be available.
08:18:56 <danoffek> Good to hear
08:19:01 <danoffek> That will simplify things
08:19:38 <elisha_r> Moving on, just wanted to update that I recently entered an important fix to the overlapping-template support. (forgot to put it in launchpad... sorry)
08:20:34 <elisha_r> basically, if there were active template scenarios when vitrage is restarted, these scenarios will never be undone after the restart
08:21:59 <elisha_r> to fix this, we needed to make some minor changes to the overlapping templates tracker.
08:22:11 <elisha_r> This was pushed a few days ago.
08:22:17 <elisha_r> that;s it for updates from me...
08:22:35 <ifat_afek> elisha_r: great, thanks
08:23:01 <nofarsch> elisha_r: so after a restart what
08:23:12 <nofarsch> will happen exactly?
08:23:52 <danoffek> You will have Vitrage
08:24:09 <nofarsch> all scenarios will be deactivated?
08:24:26 <elisha_r> nofarsch: if there are active scenarios before the restart, they will still be active after restart. But unlike before, their undo
08:24:33 <elisha_r> will work as it should
08:25:01 <nofarsch> elisha_r: awesome
08:25:25 <elisha_r> the problem originally was that during restart, the consistency process checks and activates templates for EACH node in the graph, not just the last one the completed the pattern of the scenario
08:25:54 <nofarsch> and now?
08:25:55 <elisha_r> so if the scenario pattern had three vertices, the scenario was activated three times
08:26:10 <elisha_r> and the overlapping templates support had three entries for this action
08:26:35 <elisha_r> then, a single undo would not undo the action, only remove one of these entries (sort of like soft-pointer implementation)
08:27:19 <elisha_r> the fix was to make sure that during "undo", of the same exact pattern triggered an action, even if it happened several times, all these "pointers" are removed from the system, solving the bug
08:27:27 <elisha_r> hope that clarifies things
08:27:54 <ifat_afek> elisha_r: thanks for the detailed exaplanation
08:28:02 <ifat_afek> moving on
08:28:11 <nofarsch> elisha_r: thanks!
08:28:19 <ifat_afek> #topic Plans for Ocata
08:28:57 <ifat_afek> Now that Barcelona summit is over, we should plan Ocata
08:29:06 <ifat_afek> I will try to estimate the effort needed for implementing the Vitrage -> Aodh integration.
08:29:14 <elisha_r> nofrasch: sure - always :)
08:29:20 <ifat_afek> We already have Vitrage datasource that polls alarms from Aodh, and dwj is working on receiving notifications from Aodh.
08:29:31 <ifat_afek> We need to implement the other direction as well. First, we should write code in Aodh for custom alarms (that can be triggered by an external project like Vitrage)
08:29:39 <ifat_afek> Then, we should rewrite aodh notifier in Vitrage to generate these alarms in Aodh.
08:30:30 <nbloom> Hi all :)
08:32:17 <nbloom> I really want that for Ocata we'll extend the capabilities regarding templates along with a matching UI for creation of new templates via an editor(perhaps add some snippets for easy creation), saving them, editing them and making it more accessible to people to write new templates and change them
08:33:14 <ifat_afek> nbloom: I agree it will be a very big enhancement to Vitrage
08:34:41 <ifat_afek> other things we would like to do for Ocata are: handle alarms history, and for that we need to have a persistent graph database
08:34:52 <ifat_afek> also improve our multi tenancy solution
08:35:31 <ifat_afek> and fully support Doctor use case - we need to support Vitrage installation as part of OPNFV Apex installer
08:35:38 <ifat_afek> anything else that I missed?
08:37:07 <danoffek> We are starting to plan Vitrage history
08:37:51 <danoffek> Everybody is invited to contribute ideas / blueprints / code
08:38:08 <ifat_afek> danoffek: +1
08:38:22 <ifat_afek> any other issues before we end this meeting?
08:40:13 <ifat_afek> goodbye then
08:40:22 <nbloom> bye
08:40:48 <ifat_afek> #endmeeting