08:00:06 #startmeeting vitrage 08:00:07 Meeting started Wed Jan 17 08:00:06 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:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:10 The meeting name has been set to 'vitrage' 08:00:18 Hi :-) 08:00:23 hi 08:00:41 Hi 08:00:41 hi 08:01:34 \o/ 08:02:01 Today’s agenda: 08:02:05 • Status and Updates 08:02:09 • Open Discussion 08:02:13 #topic Status and Updates 08:02:49 Queens feature freeze is at the end of next week. For python-vitrageclient, we should create our final release next week. I hope to do it on Tuesday or Wednesday 08:03:11 We should finish our features next week, but that’s not a must 08:03:27 And we can continue fixing bugs for 2-3 weeks until the release 08:03:36 Release candidate - February 5-9 08:03:55 My updates: I pushed the last change that was needed in order to finish the Vitrage-Mistral integration – template functions support 08:04:00 #link https://review.openstack.org/#/c/532274/ 08:04:45 An update on behalf of Niv: he finished the implementation of the webhooks, but there is a merge conflict. He won’t be at work today and tomorrow, so I’ll try to handle it myself 08:04:48 That’s it for me 08:05:23 My update 08:05:29 I'm working with Kinory on final code refactoring and failing tests for template crud. 08:05:35 No need to review yet :) 08:05:39 #link https://review.openstack.org/#/c/530640/ 08:06:06 That's it 08:07:51 My updates: finished to deploy undercloud, now working on build image to deploy overcloud. 08:08:04 Sounds good 08:08:22 :-) 08:08:35 Do you have an estimation on how much work it is? 08:08:50 To finish everthing? (I’m not even sure what everything means) 08:10:21 I'm not family with TripleO how it works. I don't know whether feature freeze in TripleO 08:10:32 Ok 08:11:19 Anything else? 08:12:01 Maybe I can put the task in rocky roadmap in TripleO, I saw that they send mail to collect the feature 08:12:19 Might be a good idea 08:13:08 #link https://etherpad.openstack.org/p/tripleo-ptg-rocky 08:13:40 You mean you want to discuss it in the PTG? 08:14:53 Yes, maybe discuss with their team first is more suitable. 08:15:01 I agree 08:16:13 Which reminds me that I still don’t know the time of our PTG discussions… didn’t get any mail on this issue 08:16:17 But here is the etherpad: 08:16:26 #link https://etherpad.openstack.org/p/vitrage-ptg-rocky 08:16:59 dwj: Any other update? 08:17:09 No, thanks~ 08:17:34 i will update 08:18:12 the community goal of seperating the tempest is still on going work 08:18:49 the tempest now pass but we are not using the tempest to run the tests but using testr 08:19:12 when using the tempest our test are failing and I dont know why 08:19:38 also we need to add the gate jobs to the tempest repo 08:19:57 so we can run the tempest when we do changes to the tests 08:20:02 thats it 08:20:22 And after all this is done, we will be able to run the tempests also from python-vitrageclient, right? 08:20:37 I guess yes 08:20:45 Hope so 08:21:21 One more update, on behalf of Muhamad: he finished the graph persistor, and the code is merged. However, one critical thing is missing: deletion of old data… if we let the users use this feature, their DB will explode :-( And since we didn’t implement the graph loading yet, I think it might be best to completely disable this feature for Queens, and continue the implementation as soon as Rocky starts. 08:21:56 Any other updates? 08:22:07 Oops. Can we disable the feature by some configuration? 08:22:37 It is already disabled by deafult in the configuration, but I’m worried that someone might decide to enable it… so I’m thinking of hard-coding it 08:22:56 but will the tests in the gate pass ? 08:23:01 This code is very important, but is not usable uyet 08:23:03 yet 08:23:19 you need to enable it when running tempest 08:23:25 I’m not sure about the tests, maybe we should disable them as well 08:23:40 We can disable everything in Queens, just for a week or two until the master becomes Rocky 08:24:16 Or we can leave it as is and hope that no one decides to check the new configuration… 08:25:32 Your thoughts? 08:25:52 And hide the configuration options? 08:26:21 Yes, that’s one option. We can’t let anyone use it 08:26:44 Or we can try to implement the deletion of old data, but I doubt if we can make it on time 08:28:12 Let’s look at the Queens roadmap 08:28:18 #link https://etherpad.openstack.org/p/vitrage-ptg-queens 08:28:42 Networkx is in risk. I believe the global requirements won’t be changed for Queens, but I’ll try to handle it by next week anyway 08:29:16 Tempest tests Queens goal - I think it is also at risk 08:29:34 Moving to “Important” 08:29:43 Improving the temest tests - partially donw 08:29:44 done 08:30:03 Configurable notifications - will be finished by next week 08:30:27 HA - the persisting is done, but not the reload 08:30:55 And medium priority - the template CRUD will be done by next week 08:30:58 That’s it 08:31:03 from Nokia side 08:32:09 Any other updates? 08:33:41 #topic Open Discussion 08:33:48 Vancouver CFP is open! 08:33:55 #link http://lists.openstack.org/pipermail/openstack-dev/2018-January/126192.html 08:34:09 We can submit session proposals until February 8th. 08:34:29 If there is no other issue, then let’s close the meeting 08:35:16 bye 08:35:26 bye 08:35:31 Bye 08:35:35 bye 08:35:47 #endmeeting