08:00:03 #startmeeting vitrage 08:00:04 Meeting started Wed Jan 24 08:00:03 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:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:07 The meeting name has been set to 'vitrage' 08:00:20 \o/ 08:00:22 Hi :-) 08:00:36 Hi! 08:00:40 hi 08:03:01 Agenda: 08:03:10 • Status and Updates 08:03:17 • Open Discussion 08:03:31 #topic Status and Updates 08:03:40 python-vitrageclient 2.0.0 was released this morning 08:03:54 It includes changes in the templates API, and new APIs: webhooks, alarm show and get alarm count 08:04:09 Later today I’ll ask to release vitrage 2.0.0 and vitrage-dashboard. All important features are merged: graph and event persistency; templates CRUD and webhooks support. 08:04:24 The release candidate deadline is February 5-9, so we will have another release of vitrage (and maybe vitrage-dashboard) near that date. 08:04:33 Hi 08:04:50 But for python-vitrageclient, today’s release should be the final Queens release 08:05:01 I’ll soon ask to update it in the global-requirements 08:05:12 Note that stable/queens branch was created for python-vitrageclient, but I won’t ask to create it for vitrage yet (unless you think that I should) 08:05:22 It means that master will be used for Rocky for python-vitrageclient and for Queens for vitrage – quite confusing 08:05:50 Please try not to push changes to python-vitrageclient in the coming two weeks… 08:05:57 That’s it for me 08:07:51 Any other updates? 08:08:19 I don't have much update recently. Stuck at some internal urgent issues. 08:08:33 Ok 08:08:44 So some blueprint on my side will probably be postponed to Rocky 08:09:04 And we may have further clarification on the coming PTG 08:09:22 No problem. There are no releases to vitrage-specs, so you can move the blueprints when you have the time 08:09:29 Besides, I had a look at the healthcheck propoal 08:09:34 Sure, that’s a good time to put the link again: 08:09:42 #link https://etherpad.openstack.org/p/vitrage-ptg-rocky 08:09:46 #link https://review.openstack.org/#/c/531456/ 08:10:06 Do you think the proposal is good? 08:10:27 Currently, there are not much discussion yet. And it looks a bit sophisticated. Trying to understand more. 08:10:33 btw, i added a new ideas" 08:11:01 btw, i added a "new ideas" section to the etherpad, welcome to add there... 08:11:37 Great. You mean “ideas for discussion” or just “ideas for Rocky”? 08:11:44 I believe oslo team is also attending the PTG, so I suppose there would be some relevant discussion. 08:12:12 I guess for Rocky would be nice 08:12:32 That's all from me 08:13:00 Ok. Because we could have ideas that are simple and don’t require a discussion :-) 08:13:31 i am still struggling with the tempest :-( 08:13:47 I saw the patchset reaches 60 ! 08:13:52 60 patches ... 08:13:58 It is the largest one I have ever seen 08:14:09 yes and it will be bigger 08:14:20 Eyal might have reached #1 place in OpenStack… 08:14:39 :-) 08:14:39 I'm curious what makes it so difficult? 08:14:51 tests are failing 08:15:12 and also because our tempest test were written wrong 08:15:20 decoupling is hard 08:15:30 we need to refactor all the tests 08:15:49 thats it for me 08:16:19 This is already a topic in the PTG etherpad… 08:16:29 Any other updates? 08:16:33 Can it be finished in this release? 08:16:43 dont think so 08:16:51 OK 08:17:10 Should we tag a release for the new tempest-plugin repo? even if it’s not working? 08:18:02 I have no idea 08:18:10 I will need to ask someone 08:18:12 Ok, I’ll check what other teams are doing 08:18:27 So far I think most of them only released the client libraries 08:19:20 Anyone else wants to update? 08:21:22 #topic Open Discussion 08:21:27 Reminder - Vancouver CFP is open! 08:21:33 #link http://lists.openstack.org/pipermail/openstack-dev/2018-January/126192.html 08:21:38 We can submit session proposals until February 8th. 08:22:18 Any other issue for discussion? 08:24:19 Bye, see you next week 08:24:27 bye 08:24:28 bye 08:24:30 bye 08:24:36 #endmeeting