08:00:07 <ifat_afek> #startmeeting vitrage
08:00:08 <openstack> Meeting started Wed Jul 25 08:00:07 2018 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:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:00:12 <openstack> The meeting name has been set to 'vitrage'
08:00:12 <ifat_afek> Hi:-)
08:00:27 <eyalb> \o/
08:01:06 <annarez> Hi :)
08:01:10 <idan_hefetz> hi
08:02:06 <MinWookKim> Hi : )
08:02:16 <dwj_> hi
08:04:02 <ifat_afek> #topic Status and updates
08:04:11 <ifat_afek> By tomorrow we must tag the final release of python-vitrageclient.
08:04:25 <ifat_afek> In addition, tomorrow is Rocky-3 milestone and the Rocky official feature freeze. Since our release mode is cycle-with-intermediary, we are able to extend the feature freeze a little.
08:04:37 <ifat_afek> And since we are behind schedule with some main features… we will do it
08:04:44 <ifat_afek> Hopefully we will release vitrage early next week.
08:04:53 <ifat_afek> Regarding python-vitrageclient, we must release it by tomorrow. We will release the client with the new API changes, but they will work only after we tag vitrage.
08:05:00 <ifat_afek> Next milestones:
08:05:05 <ifat_afek> Release candidate on August 9
08:05:09 <ifat_afek> Final release on August 23
08:05:16 <ifat_afek> #link https://releases.openstack.org/rocky/schedule.html
08:05:25 <ifat_afek> Vitrage board, where you can see our status:
08:05:30 <ifat_afek> #link https://storyboard.openstack.org/#!/board/90
08:05:54 <ifat_afek> My updates: I finished the implementation of the Vitrage resource in Heat. My changes are under code review.
08:06:00 <ifat_afek> #link https://review.openstack.org/#/c/584863/
08:06:00 <ifat_afek> \
08:06:06 <ifat_afek> #link https://review.openstack.org/#/c/578786/
08:06:07 <ifat_afek> #link https://review.openstack.org/#/c/583217/
08:06:08 <ifat_afek> #link https://review.openstack.org/#/c/583951/
08:06:25 <ifat_afek> I am also helping annarez with implementing the CLI for the alarm history.
08:06:34 <ifat_afek> And I’m working on a fix/workaround for entities deletion on top of the fast failover change.
08:06:39 <ifat_afek> That’s it for me.
08:07:00 <idan_hefetz> Cool, nice work with heat!
08:07:09 <ifat_afek> :-)
08:07:24 <idan_hefetz> i'll update
08:07:30 <idan_hefetz> There was quite a mess with networkx version updated to 2.1 at the last minute.
08:07:50 <idan_hefetz> But we managed to solve it, and the gate is back up
08:09:01 <idan_hefetz> The BP for fast fail-over will be closed soon, as the main commit was merged yesterday (could have been sooner without the gate problems)
08:09:28 <idan_hefetz> Still have some minor additions to add in the next days
08:10:05 <idan_hefetz> Also, i'll update the BP spec, so it is inline with the actual implementation.
08:10:24 <idan_hefetz> That's me
08:10:58 <annarez> I'll update
08:12:11 <annarez> the work on API for alarms history is almost done, so does the work on vitrage-dashboard (thanks to Alon) and cli (thanks to ifat_afek)
08:12:35 <annarez> so we will be ready for python-vitrageclient release
08:13:28 <annarez> now I'm handling some problems with writing to DB, hope It wont take long
08:13:36 <annarez> that's it
08:13:54 <MinWookKim> I'll update
08:14:11 <MinWookKim> According to the comments,I'm classifying each action. These actions inherit the abstract class (base_action.py).
08:14:28 <MinWookKim> Perhaps users just add their own action class to the "api / contrib" folder.
08:14:48 <MinWookKim> That's it : )
08:15:12 <ifat_afek> MinWookKim: sounds good. Did you find a solution for the vitrage_rest_api file?
08:15:36 <ifat_afek> I’m less familiar with this area
08:16:34 <MinWookKim> ifat_afek: I'm looking for it, but it's not easy : (
08:17:16 <ifat_afek> I understand… unfortunately we are all too busy these days, but I hope that if you don’t find a solution then we can try to help next week
08:18:49 <MinWookKim> ifat_afek: Thanks:) I hope I find the solution.
08:18:59 <ifat_afek> Good luck :-) and keep us updated
08:19:42 <ifat_afek> Maybe you can look at how we handle our datasource plugins (in vitrage repo) or notifiers. But I’m not sure the same would work in the dashboard
08:21:02 <MinWookKim> ifat_afek: Okay i'll take a look. Thank you. : )
08:21:19 <dwj_> No, they have no plan to attend the VPTG
08:21:28 <dwj_> Sorry
08:21:35 <nivo> hi
08:21:59 <nivo> my update: finished adding support for more AODH alarm types and added some tempest tests
08:22:00 <dwj_> mistake~
08:22:53 <ifat_afek> Ok, thanks
08:23:55 <ifat_afek> BTW, all - please make sure there are release notes for your major changes before we tag the next releases
08:24:08 <ifat_afek> Anyone else wants to update?
08:25:22 <ifat_afek> #topic Open discussion
08:26:18 <ifat_afek> Well, dwj_ reminded me of our Vitrtual PTG :-) I’ll try to schedule the date next week, when I have some free time. I’ll probably create a doodle poll, so we can make sure that the time suits everyone
08:27:02 <ifat_afek> Meanwhile, if you have any comments/requests/whatever, let me know
08:27:22 <ifat_afek> Any other issues we should discuss?
08:28:09 <dwj_> Our colleages may not attend the Virtual PTG.
08:29:36 <ifat_afek> dwj_: thanks for the update. BTW, do you know if your colleagues plan to continue working on the Vitrage specs they started back then?
08:31:26 <dwj_> No ideas, they have no human resource to work on community now, busy on internal project.
08:31:57 <ifat_afek> Ok, no problem
08:32:17 <ifat_afek> Anyone wants to raise anything else before we end the meeting?
08:33:36 <ifat_afek> Bye then, see you next week
08:33:47 <eyalb> bye
08:33:49 <dwj_> Bye~
08:33:52 <idankin> bye
08:33:54 <MinWookKim> See you : )
08:34:02 <ifat_afek> #endmeeting