08:02:41 <ifat_afek> #startmeeting vitrage
08:02:41 <openstack> Meeting started Wed Jun  7 08:02:41 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:02:43 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:02:45 <openstack> The meeting name has been set to 'vitrage'
08:03:16 <ifat_afek> Hi :-)
08:03:35 <annarez> Hi :)
08:05:19 <alexey_weyl> Hello
08:08:11 <eyalb> \o/
08:08:59 <ifat_afek> Today’s agenda:
08:09:04 <ifat_afek> •	Status and Updates
08:09:10 <ifat_afek> •	Open Discussion
08:09:15 <ifat_afek> #topic Status and Updates
08:09:27 <ifat_afek> We need to release a Vitrage version by tomorrow, and if possible then today
08:09:35 <ifat_afek> Since Pike-2 is next week, they would like every project to have at least one version released for Pike
08:09:55 <ifat_afek> I sent an email in the ML asking you to add release notes to the features that you have added. Thanks for everyone who already did that  I hope to mark the Vitrage release later today.
08:10:12 <ifat_afek> I started working on the integration with Mistral. Wrote an initial blueprint, but there are still some TBDs
08:10:20 <ifat_afek> #link https://review.openstack.org/#/c/470894/
08:10:35 <ifat_afek> As a first step, I want to support “external actions” in the templates. Then, the next step would be to call Mistral.
08:10:45 <ifat_afek> That’s it for me
08:11:18 <alexey_weyl> I will update
08:11:46 <alexey_weyl> I am almost finished with the refactoring of the constants.
08:11:56 <alexey_weyl> It is now in the review stage.
08:12:22 <alexey_weyl> But in addition to what I have done, we also need to do changes in the vitrage-dashboard and the python-vitrageclient
08:12:40 <alexey_weyl> in order so everything will be compatible
08:13:00 <alexey_weyl> hopefully we will push all the changes on Sunday
08:13:09 <alexey_weyl> thats it for now
08:13:10 <alexey_weyl> :)
08:13:16 <ifat_afek> Thanks :-)
08:13:34 <annarez> I will update now
08:13:45 <annarez> As part of the machine learning feature, I added resource data to all the alarms
08:13:52 <annarez> The data I added is vitrage_resource_id (in addition to the existing resource id) and vitrage_resource_type
08:13:59 <annarez> I added this in the processor
08:14:10 <danoffek> Hi guys.
08:14:24 <danoffek> Sorry anna
08:14:28 <danoffek> Hi girls
08:14:31 <annarez> later I will be able to use this data for the correlation calculations
08:14:46 <annarez> Hi Danny
08:14:54 <annarez> Thats all
08:15:15 <ifat_afek> Cool, we needed this for other purposes as well
08:15:18 <ifat_afek> Thanks Anna
08:15:32 <danoffek> I'll update
08:15:47 <danoffek> Started working on Rest API / other for notifications
08:16:16 <danoffek> I pushed an HTTP post API spec
08:16:31 <danoffek> Reviewed by Ifat, and will push again after fixing it.
08:16:36 <danoffek> In short :
08:17:06 <danoffek> One can get HTTP post notifications on any change / status update / alarm / other in Vitrage
08:17:27 <danoffek> By first supplying a regex when registering for notifications
08:18:01 <danoffek> Then he (the monitoring system) will get all notifications which meet this regex.
08:18:14 <danoffek> Will add additional specs for additional features.
08:19:08 <danoffek> This is not a "wish list" spec. Following this spec, starting development of this feature (either me / another contributor)
08:19:13 <danoffek> Done
08:19:23 <ifat_afek> Sounds great
08:19:25 <ifat_afek> Thanks
08:19:30 <eyalb> small update
08:20:39 <eyalb> working on making vitrage to work with other authentication applications e,g keycloak also to be able to work with no authentications which can be good for tests
08:21:03 <eyalb> maybe do some refactoring also
08:21:23 <eyalb> thats all
08:21:50 <ifat_afek> This is very important, we get a lot of requests for “decoupled Vitrage”, meaning Vitrage that can work without openstack
08:22:27 <ifat_afek> Anyone else wants to update?
08:22:35 <eyalb> yes hopefully vitrage can work in a non openstack environment with this feature
08:22:52 <ifat_afek> Great
08:23:38 <ifat_afek> Any other issue someone would like to discuss before closing this meeting?
08:24:09 <dwj> BTY, will you attend the OPNFV summit?
08:24:36 <ifat_afek> dwj: Hi :-) unfortunately we will not attend the OPNFV summit
08:24:40 <ifat_afek> I assume that you will?
08:24:51 <dwj> yes, i will.
08:25:26 <ifat_afek> It’s next week, right?
08:26:04 <dwj> yes, what's the progress about integration vitrage with doctor?
08:27:11 <ifat_afek> I need to get back to that… I noticed that there was some refactoring in the tests, so I guess I may need to adjust my tests as well
08:27:27 <ifat_afek> And we need to progress with TripleO and Apex installation of course
08:28:37 <dwj> Yes, refactor the test script is one of the topics in the design summit.
08:29:24 <ifat_afek> I just keep seeing changes in gerrit… we will be happy to hear about the conclusions from the design summit
08:30:55 <dwj> I think the refactoring should be a long journey. :-)
08:31:11 <ifat_afek> It usually is :-)
08:33:13 <ifat_afek> Do you see any special issue with Vitrage and the refactoring? I assume that since my code is similar to Congress test, I may just need to move it to another function or something like that. Or is it more complicated?
08:35:21 <dwj> Currently not. Maybe we can go ahead with the integration. We have not decide how to refactor the test script currently.
08:35:40 <ifat_afek> Ok, thanks
08:35:50 <ifat_afek> Any other issue someone would like to discuss?
08:36:04 <dwj> And it may be a long time to switch to the refactor test.
08:36:26 <ifat_afek> Thanks for the warning…
08:36:50 <dwj> :-)
08:37:51 <ifat_afek> Cool. Any other issue for this meeting?
08:40:12 <ifat_afek> So I guess we are done for today
08:40:21 <ifat_afek> Bye :-)
08:40:27 <annarez> Bye
08:40:30 <dwj> bye~
08:40:43 <eyalb> bye
08:40:55 <ifat_afek> #endmeeting