08:00:15 #startmeeting vitrage 08:00:16 Meeting started Wed Mar 13 08:00:15 2019 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:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:19 The meeting name has been set to 'vitrage' 08:00:22 Hi :-) 08:01:05 Good morning 08:01:44 hi 08:01:58 good morning :) 08:02:23 #topic Status and updates 08:02:28 We are past Stein feature freeze. python-vitrageclient is already frozen. 08:02:44 We should finish our work and prepare for the release candidate next Thursday (March 21). In a few days I will ask to create the stable/stein branches. 08:02:51 Other than that, I have no special updates 08:03:40 Anyone else wants to update? 08:03:57 for me nothing new for vitrage :) 08:04:11 Nothing for me as well :) 08:04:44 ifat_afek have you checked the template issue we talked about ? 08:05:04 Sure, I submitted a fix, it’s on the gate now 08:05:25 great :) 08:05:26 #link https://review.openstack.org/#/c/642780/ 08:06:17 Once merged, we will be able to test end to end with your UI changes 08:07:05 Anything else that is missing for Stein release? 08:07:42 Before releasing, we should run our manual tests.. 08:08:31 idan_hefetz: of course 08:08:37 idan_hefetz: do we have a list of these tests somewhere? 08:08:44 actually, maybe we should start them this week… 08:09:10 e0ne: I have a list, it’s not published in gerrit… do you think that it should be? 08:09:48 ifat_afek: It's supposed to be open for sure 08:10:59 e0ne: do you have an example of what other teams do? I have no problem publishing it, I just wonder where 08:11:20 ifat_afek: I don't have anything in the mind 08:11:41 ifat_afek: usually, all teams use tempest or some automatic functional tests 08:12:17 we have the tempests as you know, but we also like to do manual tests before the release 08:12:58 IMO, we should implement tempest tests instead 08:13:31 I think most, if not all, is already covered in tempest tests. and yet… 08:13:44 ifat_afek: some manual closed tests makes project not 100% openL( 08:13:44 the ui must be tested manually 08:13:53 There's nothing like seeing that everything actually works :) 08:14:15 So maybe I can add a .rst in vitrage with the test plan 08:14:30 although I’ve never seen other teams doing it 08:14:54 because nobody can be sure that manual tests will be executed 08:15:25 it could work in your case, because all team was from one company 08:15:40 writing it in .rst doesn’t promise that it will be executed, of course. this is why I keep my own list for things that I plan to do myself ;-) 08:16:24 the solution is tempest tests, of course, but I really believe that manual tests should be executed before the release. mainly because of ui issues, I think 08:16:37 ifat_afek: IMO, in such case, we should not mention such tests in IRC 08:16:38 which the integration tests might solve in the future, but not now 08:17:04 upstream project could not be partially open 08:17:30 ifat_afek: I do understand that vendors could have additional tests in their distro 08:17:52 this is not the purpose, my tests are for regular devstacks 08:18:01 ifat_afek: but such tests must not affect upstream at all 08:18:10 e0ne: I think you miss understood, it's just double checking, and checking for log errors, or whatever :) 08:18:41 idan_hefetz: no, you missed my point 08:19:31 idan_hefetz: you've got some test cases for vitrage and you're discussing it in upstream IRC meeting 08:20:08 idan_hefetz: I have no idea what is it because these tests are closed and available only for one vendor 08:20:57 if the team would like to execute some manual test - we should keep the test cases and/or tests scenarios open 08:21:05 e0ne: these tests are quite trivial, it’s just a long list of “do not forget to test this and that”. I’ll publish it after the meeting 08:21:09 or it will be some vendor-specific tests 08:21:44 I got what you mean, but you are wrong these are plain devstack tests... testing the exact same features as tested on the tempest.. 08:22:16 I see 2 options here 08:22:28 1) do not mention these tests on meetngs 08:22:38 2) keep them open 08:22:53 personally, I agree with any of them 08:23:02 We’ll go for 2 then 08:23:11 e0ne: NP, i agree off course 08:23:31 but in such case, any contributor outside of Nokia feels like he/she missed something important 08:23:46 in what case? 08:24:22 ifat_afek: in case of talking about some manual tests cases which are available only inside some team 08:25:15 ok, we’ll solve it. the tests will be upstream from now on 08:25:29 ifat_afek: thanks 08:26:08 ok, moving on 08:26:15 #topic Denver Summit 08:26:24 We got two more sessions – Vitrage project update and Vitrage project onboarding 08:26:31 The project update conflicts with our lab, so I asked to reschedule it 08:26:37 I also asked to remove Yuval from the list of speakers, as he will not attend the summit. 08:26:43 #link https://www.openstack.org/summit/denver-2019/summit-schedule/global-search?t=vitrage 08:26:56 And a reminder: you can add topics to the PTG etherpad.: 08:27:01 #link https://etherpad.openstack.org/p/vitrage-train-ptg 08:27:05 that’s it for me 08:28:44 anything else? 08:31:39 have a nice day :-) 08:32:10 see you next week! 08:32:30 cheers 08:32:32 #endmeeting