08:00:17 #startmeeting qa 08:00:18 Meeting started Thu Jun 15 08:00:17 2017 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:21 The meeting name has been set to 'qa' 08:00:29 gmann: hello 08:00:30 who all here today? 08:00:39 hello 08:00:40 o/ 08:00:51 hello 08:01:41 new time and happy to see more people :) 08:01:48 o/ 08:01:49 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_Jun_15th_2017_.280800_UTC.29 08:01:50 thanks for making the meeting time an hour earlier, now it's 4 PM in China:) 08:01:56 ^^ today agenda 08:02:17 o/ 08:02:28 zhyes, 5 for me and i can join dinner with masayukig and mtreinish due to that :) 08:02:58 #topic Previous Meeting Action review 08:03:21 there was 1 action for andreaf - #link http://eavesdrop.openstack.org/meetings/qa/2017/qa.2017-06-08-17.00.html 08:03:27 and he sent mail for that 08:03:38 #link http://lists.openstack.org/pipermail/openstack-dev/2017-June/118283.html 08:03:50 nice idea about keep monitoring the gate issues 08:04:08 hope everyone saw the mail 08:04:54 yeah, I had a glance, but re-read it later.. 08:04:59 there is rotation things for gate issue categorization like bug triage 08:05:07 #link https://etherpad.openstack.org/p/pike-gate-issue-categotisation 08:06:07 gmann: ok, I'll put my names later 08:06:14 no one yet assigned the slots but as andreaf mentioned we encourage new people to start taking those tasks and we can provide mentorship program also 08:06:20 masayukig, thanks +1 08:06:55 may be few initial week we can do to give a glance of what needs to be done and how to report 08:07:42 maybe I can have a try, and I need guidance:) 08:07:58 zhufl, sure. it will be nice 08:08:34 so start putting your name on etherpad for the slot you want 08:09:02 ok, I'll put my names later 08:09:11 cool! 08:09:16 #topic PTG 08:09:37 this is just reminder about PTG schedule out #link http://lists.openstack.org/pipermail/openstack-dev/2017-May/117369.html 08:10:07 start preparing about it (mainly budget from company :)). 08:10:29 I haven't got my visa still 08:10:55 :( 08:10:55 zhufl, you applied and waiting for visa approval or it is rejected ? 08:11:22 4 months passed, it is pending,' administrative processing' 08:11:36 zhufl, ohh, thats not good 08:11:51 zhufl: you should ask the administrator(?) again.. 08:12:18 zhufl, one of my colleague had same issue and asked to return passport as travel was near and they issues 1 year visa for him 08:12:28 gmann: masayukig for visa, we need letter from where can i get it for ptg? 08:12:34 zhufl, masayukig yea may be checking with them again will help 08:12:48 chandankumar, there is link in that mail to request IL 08:12:53 oh, I 'll try 08:13:13 one of my colleague has the same situation with me 08:13:22 chandankumar, from india it is little bit difficult so try to make your application strong 08:13:35 hope you all get visa. 08:13:59 maybe travel visa is better 08:14:03 hope for best :-) 08:14:25 zhufl, yea, i also have business visa and good for conf etc 08:14:29 #topic Gate Stability - status update 08:14:40 * masayukig doesn't need visas, actually even if I go to China.. 08:15:05 gate seems stable now a days and did not find much issue if i have not missed any 08:15:22 #link https://goo.gl/ptPgEw 08:16:08 anyone aware of any critical issue? 08:16:51 gmann: http://logs.openstack.org/74/473774/5/check/gate-tempest-python27-ubuntu-xenial/0af018f/console.html 08:16:52 #link http://status.openstack.org/elastic-recheck/data/integrated_gate.html 08:17:06 added recheck let me see if it agains fail 08:17:39 chandankumar, humm 08:18:22 sorry ignore 08:18:59 chandankumar, means? 08:19:52 gmann: on one of my review, it got failed, i added recheck, if it again fails, i will let you know 08:20:18 chandankumar: the test case looks not good.. 08:20:19 chandankumar, but strange failure. ok let's check it later 08:21:28 let's move to next topic 08:21:30 yeah 08:21:32 @topic Specs Reviews 08:21:36 #topic Specs Reviews 08:22:09 #link https://review.openstack.org/#/q/status:open+project:openstack/qa-specs,n,z 08:22:51 blancos, i need to check this, was away last week - #link https://review.openstack.org/#/c/461140/ 08:22:51 patch 461140 - qa-specs - RBAC testing multiple policies 08:22:56 ll try to check this 08:23:06 gmann Okay, thank you :) 08:23:45 masayukig, your spec is +A :) #link https://review.openstack.org/#/c/471623/ 08:23:46 patch 471623 - qa-specs - Update document theme 08:24:00 gmann: heh, thanks! 08:24:31 we need to make HA testing moving as it seems stuck #link https://review.openstack.org/#/c/443504/ 08:24:32 patch 443504 - qa-specs - Added spec for high availability testing 08:24:48 i will check with samP if he need any help on this 08:24:49 gmann: hi.. 08:25:11 #action gmann to check with samP about HA testing spec 08:25:17 I will update it.. now working on it 08:25:19 samP, hi, you are here 08:25:33 gmann: hi o/ 08:25:38 samP, thanks, i will review on revised version. 08:25:49 I was working with LCOO on this. 08:25:54 #link https://openstack-lcoo.atlassian.net/wiki/display/LCOO/Working+Space+for+Exteme+Testing+and+related+topics 08:25:57 * gmann do not know how to undo action 08:26:21 gmann: its ok, leve it..:) 08:26:45 gmann: you can mark it done on next meeting :) 08:27:01 samP, can i help in implementing this ? 08:27:17 prateek: That will be great.. 08:27:17 (gmann: I think it's (#)undo action) 08:27:26 samP, thanks 08:27:33 samP, nice, what is that LCOO ? 08:27:43 ah.. 08:27:58 prateek, thanks. its great. 08:28:03 blancos: oh, I didn't know that :) 08:28:09 #link https://wiki.openstack.org/wiki/LCOO 08:28:40 #undo action 08:28:41 Removing item from minutes: #link https://wiki.openstack.org/wiki/LCOO 08:28:54 oh no 08:28:57 heh 08:29:00 #link https://wiki.openstack.org/wiki/LCOO 08:29:11 samP, thanks a lot, i will check 08:29:54 anything else on spec? 08:30:12 gmann: I will update the spc asap, so we can move forword 08:30:26 samP, cool\, thanks. 08:30:35 gmann: np 08:30:43 #topic Tempest 08:30:56 #link https://review.openstack.org/#/q/project:openstack/tempest+status:open 08:31:15 https://review.openstack.org/#/c/467483/ 08:31:16 can we use resource_type defined in clients to assemble show method/delete method, like "show_" + resource_type? 08:31:16 patch 467483 - tempest - Refactor is_resource_deleted method 08:32:10 zhufl, i did not get completely 08:32:31 masayukig: do you get it? 08:32:44 zhufl: you mean making a method dynamically? 08:32:52 yes 08:33:00 zhufl, i see, i prefer not to do that, thats too much magic 08:33:23 zhufl; gmann: yeah, I agree with gmann. 08:33:30 but if not, we have to add a method in every client 08:33:31 zhufl, we had in neutron clients which were hard to debug so we moved to plain method mapping 08:33:58 I had a question about #link https://review.openstack.org/#/c/457876 08:33:58 patch 457876 - tempest - Add token related API to Keystone v3-ext/OS-OAUTH1... 08:34:00 gmann: no, I don't mean the same as neutron ever did 08:34:20 I have moved tempest plugin sanity check code from project config to tempest https://review.openstack.org/474164 08:34:21 patch 474164 - tempest - Added script for doing tempest plugin sanity 08:34:33 feedback are welcome to improve it 08:34:52 zhufl: gmann: but I can try to think that. Or zhufl, you can take over it, if you want :) 08:35:08 zhufl, i think having explicit method in each client much better but i will check that patch tomorrow. 08:35:24 blancos, go ahead 08:35:27 Is this something that would belong in Tempest or Keystone's Tempest plugin? 08:35:35 chandankumar, 1 min please, next turn yours 08:35:41 ack 08:36:52 blancos, is it for patrole testing? 08:37:17 it is for patrole as well as keystone tempest plugin funtional tests 08:37:39 gmann: I believe there are 1 or 2 commits dependent on it (as hemanth mentioned) 08:38:08 hemanth, ok, and no API test in tempest for that? as it can be covered in keystone plugin right? 08:38:46 just one query if we have a tempest plugin for core project what tests will stay in tempest and what in tempest plugin? 08:38:48 gmann: another patch is submitted for tempest api as well 08:39:03 blancos, hemanth ok, we can have in tempest like other keystone clients no issue as patrole need it 08:39:34 gmann: can core team review the patch.. since last one month i am just rebasing :-) 08:39:51 blancos, can patrole consume clients from plugin? 08:40:16 hemanth, ohk, apologies for that. i will check that. 08:40:43 blancos, just a thought for future things but we can think later after meeting 08:40:46 gmann: We talked with andreaf about it and he didn't really like the idea 08:41:06 blancos, about consuming client from plugin? 08:41:11 chandankumar: I think scenario tests and defcore tests will stay at least. 08:41:13 gmann: Correct 08:41:23 blancos, ok, make sense. 08:41:29 blancos, hemanth i will check that patch 08:41:31 chandankumar, go ahead 08:41:43 gmann: thanks 08:41:47 gmann: on similar lines, we have federation APIs whose clients are implemented in plugin(keystone) 08:41:59 hemanth, np! 08:42:00 and hence patrole won't be able to consume those clients 08:42:11 i have moved tempest plugin sanity check code from project config to tempest with some more improvement, https://review.openstack.org/474164 08:42:12 patch 474164 - tempest - Added script for doing tempest plugin sanity 08:42:24 pradeepkumarks, ok, i think we had federation APIs thing earlier also 08:42:31 please have a look and more feedback to improve 08:42:52 pradeepkumarks, it should be configured globally right from devstack side 08:43:31 gmann: https://review.openstack.org/#/c/473458/ 08:43:31 patch 473458 - tempest - Implement tempest client for keystone v3 identity_... 08:43:44 chandankumar, you are adding script to intall plugins in tempest right? 08:43:56 chandankumar: thanks for the updating, I'll have a look tomorrow :) 08:43:58 i mean since the client is already implemented in keystone plugin, we can't let patrole consume it 08:44:24 pradeepkumarks, do you have patch up for that? 08:44:33 gmann: yes, install one project then run sanity then uninstall and again repeat for others 08:44:53 if at any step it fails, the script will exist 08:44:59 gmann: patch up for? 08:45:01 chandankumar, ok. make sense. thanks, i will add that in queue 08:45:18 gmann: i have also improved tempest plugin list script 08:45:40 pradeepkumarks, putting federation APIs client in tempest or you want feedback first 08:45:42 gmann: related patch https://review.openstack.org/#/c/473774/ 08:45:43 patch 473774 - tempest - Fixed project lists for retrieving tempest plugins 08:45:51 that's it from myside 08:45:58 masayukig: gmann thanks :-) 08:45:58 chandankumar, i saw that, should be quick.thanks 08:46:44 gmann: https://github.com/openstack/keystone-tempest-plugin/blob/master/keystone_tempest_plugin/services/identity/v3/identity_providers_client.py 08:47:10 I have one thing: https://review.openstack.org/#/c/471352/ 08:47:11 patch 471352 - tempest - Revert "Check image after unshelve" 08:47:20 this is the identity_providers_client which is already there in keystone_tempest_plugin. we wanted to implement patrole testcases for these APIs 08:47:31 pradeepkumarks, if tests and usage only in plugin then client should be plugin side only but here as you mentioned patrole need it right? 08:47:44 gmann: yes 08:48:09 gmann: patrole testcases cannot be implemented otherwise 08:48:31 pradeepkumarks, as blancos mentioned same case for other client also, we can take same approach for your case also 08:48:52 blancos, hemanth are those clients present in plugin side also - https://review.openstack.org/#/c/457876 08:48:52 patch 457876 - tempest - Add token related API to Keystone v3-ext/OS-OAUTH1... 08:49:19 gmann: incase of blancos, client wasnt already implemented at all 08:49:20 gmann: not present in plugin either 08:49:56 masayukig, thanks, interesting. i thought checking image is fine after unshelve from nova point of view 08:50:02 masayukig, ll check this 08:50:11 pradeepkumarks, ok. 08:50:30 gmann: in federation api case, we will need to add the same client (which is in keystone_tempest_plugin) into tempest as well 08:50:37 gmann: should we do that? 08:51:05 pradeepkumarks: The consensus so far has been no Patrole tests for clients in plugins 08:51:09 pradeepkumarks, it will be duplicate. if tempest going to have those then we can remove from plugin 08:51:23 gmann: thanks. 08:51:33 9 mins 08:51:46 gmann: ok 08:52:06 gmann: we can remove those client from plugin instead of duplicating..if we have consensus 08:52:07 pradeepkumarks, blancos let me think on this and we all can discuss the best way. 08:52:30 pradeepkumarks, sure, ll let you know 08:52:38 let's move 08:52:44 gmann: sure, thanks 08:52:51 pradeepkumarks, np! 08:52:54 Bug Triage & Integrated gate issue categorization: 08:53:06 thsi we already discussed in starting. 08:53:13 #topic Patrole 08:53:24 #link https://review.openstack.org/#/q/project:openstack/patrole 08:53:37 blancos, any updates or anything to discuss 08:53:46 Not in the Patrole repo, but we currently have a spec in Nova for Patrole gates: #link https://review.openstack.org/#/c/471145 08:53:47 patch 471145 - nova-specs - Patrole (RBAC) Nova Gating 08:54:10 Would appreciate QA's input/eyes :) 08:54:39 blancos, i see, but not sure it need spec :). i will check. i like to gate patrole on nova. 08:55:12 blancos, but need more feedback from johnthetubaguy 08:55:12 gmann: Okay, thank you 08:55:20 i will bring this on nova api meetin also 08:55:24 meeting 08:55:49 alex_xu, good for policy testing - https://review.openstack.org/#/c/471145 08:55:50 patch 471145 - nova-specs - Patrole (RBAC) Nova Gating 08:56:05 Keystone tempest clients porting to Tempest project 08:56:11 pradeepkumarks, this is same we discussed right? 08:57:01 Welcome lwarderley, an intern in the Outreachy program. ping us anytime for any help 08:57:03 gmann: Correct !That is what pradeep discussed now. 08:57:13 uk310y, thanks. 08:57:30 gmann, thanks :) 08:57:47 #action gmann to discuss plugin clients in tempest with team and get consensus 08:57:50 let me put action item 08:57:55 #topic Critical Reviews 08:58:00 3 min left 08:58:18 any more critical review, i think discussed lot 08:58:36 let's skip the documentation 08:58:41 heh, yeah 08:58:42 #topic Open Discussion 08:58:51 2 min left for open discussion 08:58:59 1 min.. 08:59:05 :) 08:59:14 it's first time for me to stay until the end of the meeting:) 08:59:26 zhufl, good for us also :) 08:59:27 great! 08:59:44 * gmann really happy to see many people in meeting 08:59:54 gmann: +1 08:59:59 thanks all for joining. 09:00:01 #endmeeting