08:59:36 #startmeeting qa 08:59:37 Meeting started Thu Mar 10 08:59:36 2016 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:59:38 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:59:40 The meeting name has been set to 'qa' 08:59:52 hi, who all here today? 09:00:03 o/ Hi gmann ;) 09:00:13 hi 09:00:17 o/ 09:00:23 dmellado: jlanoux masayukig hi 09:01:23 hi o/ 09:01:31 hey jordanP 09:01:32 jordanP: hi 09:01:38 let's start 09:01:52 https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_March_10th_2016_.280900_UTC.29 09:02:03 ^^ today agenda: 09:02:18 #topic Specs Reviews 09:02:28 #link https://review.openstack.org/#/q/status:open+project:openstack/qa-specs,n,z 09:02:39 So we have many specs ready for review 09:03:03 I saw andreaf ready for client refactor one as per his discussion with mtreinish 09:03:05 andreaf, is pretty active 09:03:15 #link https://review.openstack.org/#/c/92804/ 09:03:19 I still needs to look 09:03:30 I'll need to have a look too 09:03:36 masayukig is already +2 09:03:38 great 09:03:44 dmellado: Thanks 09:03:59 added myself as a reviewer, will try to find some time today 09:04:03 I will put this in list may be tomorrow if i get time 09:04:05 gmann: yeah, it's a nice spec, i think 09:04:17 masayukig: yea 09:05:33 and second priority one from code sprint was resource.yaml one 09:05:38 #link https://review.openstack.org/#/c/173334/ 09:05:59 I think andreaf and John started working on that 09:06:09 but not sure ab out spec is updated accordingly or not 09:06:18 we can check later 09:06:37 saw patches already for that - 09:06:39 #link https://review.openstack.org/#/q/topic:bp/tempest-resources 09:07:42 anyways let's check with andreaf later 09:07:48 souds good to me 09:07:50 any other spec anyone want to discuss 09:08:11 I +A'ed to https://review.openstack.org/#/c/266094/ (Centralized Workspaces) today, actually. 09:08:31 well, not a spec but I'd like to discuss some patches about the consistent-services-names 09:08:39 we can do that later in the tempest section 09:08:48 masayukig: ok, i did not even look into that 09:09:01 masayukig: can you briefly describe that 09:09:17 dmellado: yea we will discuss in Tempest topic 09:09:34 gmann: ok, 09:10:36 it's introducing a manager for tempest workspaces. 09:10:55 I don"t even know what a tempest workspace is 09:11:07 and the BP doesn't describe it either 09:11:27 jordanP: we can initialize the tempest folder/workspace and run tests in that 09:11:27 but that's fini, that BP seems rather small and doesn't have a lot of impact on the rest of tempest 09:11:42 in isolated manner with diff diff conf 09:11:42 *fine 09:11:56 jordanP: i see 09:12:14 masayukig: so tempest workspace register command is same as tempest init ? 09:12:28 no, i don't think so 09:12:46 what would the difference be? 09:13:02 would it have a separated .testrepository? 09:13:08 masayukig: in example it created another workspace named 'staging' in parallel to 'devstack' 09:13:13 we can manage workspaces with the command. 09:13:25 I'll read the spec alter but it'd be great have that summarized ;) 09:13:33 dmellado: yes, separate .testrepository, separate testr run separate tempest.conf 09:13:37 oops, 09:13:44 gmann: true. 09:14:04 masayukig: so with tempest init we used to create separate workspace 09:14:44 masayukig: what i understood with that spec is, it enables to manage workspace like rename, list etc 09:15:05 masayukig: but did not get Register means and how it is different than tempest init 09:15:30 gmann: 'tempest init' makes a workspace and register it to a .tempest. 09:16:21 maybe we should move on ? :) 09:16:32 gmann: I think we don't have it yet, so we need a register command, probably. 09:16:42 masayukig: i see, tempest init too register 09:16:46 jordanP: gmann: yeah, let's move on 09:16:48 masayukig: ok 09:16:52 jordanP: yea:) 09:17:00 anything on spec ? 09:17:26 #topic Priority Items 09:17:38 #link https://etherpad.openstack.org/p/mitaka-qa-priorities 09:17:55 first one is mine - Tempest Microversion support 09:18:18 Framework is ready in tempest and i have added patches to move it to tempest/lib 09:18:29 #link https://review.openstack.org/#/c/284387/ 09:18:43 added release notes and library interface doc 09:18:55 please review 09:19:24 and along with that modifying compute service clients to support microversion 09:19:26 will do 09:19:28 all set here -https://review.openstack.org/#/q/topic:bp/api-microversions-testing-support+status:open 09:19:32 dmellado: Thanks 09:19:50 we run v2.2 tests already on gate 09:19:58 and v2.10 and v2.20 patches are up 09:20:01 all works fine 09:20:11 #link https://review.openstack.org/#/c/258391/ 09:20:24 jlanoux: i updated that patch and it hits in 2.20 version now 09:20:30 its ready to review 09:21:02 hoping to merge all framework patch soon so that we can implement other microversion too 09:21:05 gmann: Yeah, that looks good - thanks. I might need to change the scenario a bit but that's cool it's working! 09:21:11 It is for M1 but got too delayed 09:21:29 jlanoux: please add comment about that. 09:21:37 that will helpful 09:21:47 gmann: will do 09:22:07 jlanoux: Thanks 09:22:13 next is - Health Dashboard 09:22:31 masayukig: you want to talk anything on that 09:22:47 ok, 09:22:49 may be new feature. 09:23:03 which is always helpful for debugging 09:23:21 http://status.openstack.org/openstack-health/ is the dashboard page. 09:23:37 (but now, it has something wrong..) 09:24:10 yea taking time to load 09:24:28 anyway, now, we are improving UI to useful for debuging etc. 09:24:35 ok 09:25:08 I saw this- "Failed Tests in Last 10 Failed Runs" 09:25:24 added fancy bar graphs to project status, failed job informations, etc. 09:26:13 that will give failed tests of last 10 failure of same tests or job 09:26:14 so if you have comments/feedbacks, please notify to the IRC channel, adding bug, emails 09:26:24 masayukig: sure, thanks 09:26:50 bug page is https://bugs.launchpad.net/openstack-health 09:27:03 #link https://bugs.launchpad.net/openstack-health 09:27:35 I will check new graph once it is loaded. 09:27:51 gmann: thanks, that's all from me. 09:27:55 masayukig: Thanks. 09:27:59 next is - -Service Client Migrations 09:28:14 we will take in Tempest topic as dmellado mentioned 09:28:14 on this we're pretty much done 09:28:18 https://etherpad.openstack.org/p/mitaka-tempest-service-clients 09:28:28 dmellado: yea, but still lot of client s we need to move 09:28:57 its huge work so might take more time 09:28:58 gmann: maybe we should open an etherpad for that too 09:29:06 adding it to the split one 09:29:28 dmellado: i think same etherpad is for that 09:29:39 on this I'd appreciate comments on https://review.openstack.org/#/c/286573/ 09:29:47 for the tokens_client and token 09:30:05 and we should think about 'what to do' with the remaining non-applicable to split methods 09:30:08 at least for keystone 09:30:14 dmellado: yea, i still feel to keep it in identity client 09:30:38 I've been keeping it there for comments, but if we all agree on that I'll abandon the patches 09:30:58 we should keep those in common clients like identity_client for all generic interface for keystone API 09:31:08 any other suggestion? 09:31:11 sounds fine for me 09:31:28 anyways let's oomichi too have a look into those 09:31:47 and once we will split almost all then we can have better view about remaining methods 09:31:53 sure, anyway gmann, as you said, huge work so it'll get delayed 09:32:04 dmellado: yea 09:32:05 but we can start migrating keystone as it is now ;) 09:32:44 any more topic on tempest? 09:32:44 dmellado: sure, but before that we can iterate the interface are all cleanup as per all points in that etherpad 09:32:53 gmann: +1 09:32:54 and start migrating those and review carefully there 09:33:03 lets move on 09:33:09 next in priority item is - Tempest Lib Migrations 09:33:16 jlanoux: anything you have on ssh thing 09:33:40 othersie we directly move on to - Tempest CLI Improvements 09:34:47 on that, I'd like to revisit the tempest-config stuff I posted. I think it'll be great to have this integrated, but it won't go for mitaka 09:34:56 so we can discuss that in the Austin sessions 09:35:15 dmellado: auto generation of config ? 09:35:35 gmann: yep, I sent an email about this before to the ML 09:35:43 yea, ok 09:35:55 let's talk on Tempest CLI Improvements 09:36:10 anything on this. may be masayukig you again :) 09:36:12 that'd be integrated on tempest-cli 09:36:26 that's why I brought it on here 09:36:37 DPaterson was also intereseted, but anyway, I'll bring this later on ;) 09:36:56 dmellado: honesty saying i still on same side but yea lets discuss later 09:37:04 gmann: I think we're about to close the bp with andreaf 09:37:17 jlanoux: ok 09:37:30 gmann: dmellado: yeah, old commands were already integrated. 09:37:49 masayukig: yea, i always use cleanup :) 09:38:04 masayukig: cool ;) 09:38:10 which is very helpful for me as i always do CTR C on running tests 09:38:29 let's move on to next topic 09:38:35 #topic Tempest 09:38:42 one i have on this 09:38:49 i still need to add big for that 09:39:10 actually there are failure hitting on plugin tests in many projects 09:39:32 that was due to fwaas tempest plugin has import error 09:39:35 #link http://logs.openstack.org/50/289650/4/check/gate-congress-dsvm-api/6a27be7/console.html 09:39:54 yep just saw it on #openstack-infra 09:39:56 fix is already up for fwaas 09:39:57 #https://review.openstack.org/#/c/290983/ 09:40:35 but here issue is if any plugin has import error etc it will leads all plugin tests to fail 09:40:47 while discovery the tests import error hits 09:41:09 gmann: so if it hits discovery error then all the tests fail? 09:41:10 my suggestion is to make that log only and say ok this plugin has error and run others 09:41:23 dmellado: yea error in listing the tests 09:41:39 +1 on that, there was something similar happening in sahara, IIRC 09:41:53 basically any plugin should not lead error to other plugins if they do not run that 09:42:09 I am checking where we can hadnle that better 09:42:23 i will add bug and put fix if i found good 09:42:33 thats all on that 09:42:41 I'm working on the neutron tempest plugin 09:42:46 and would appreciate reviews on this 09:42:47 dmellado: you want to discuss 09:42:52 https://review.openstack.org/#/c/274023/ 09:43:09 dmellado: cool 09:43:16 as there's some stuff already done by amuller but couldn't get him to comment 09:43:18 thanks in advance! 09:43:20 dmellado: any issue you are facing or all going fine 09:43:36 just not really sure about the config part 09:43:50 it works, I've tested it but unsure on the integration for the config part 09:44:25 dmellado: ok, you can check other example and ping if still you face issue 09:44:38 gmann: I followed heat/manila 09:44:53 dmellado: main issue i observed for those is if config are register twice 09:44:56 but in this specific case for neutron my doubts are for that 09:45:07 dmellado: you have patch up for that? 09:45:14 gmann: could you comment there? I'll fix and follow with patchsets ;) 09:45:30 dmellado: on https://review.openstack.org/#/c/274023/ ? 09:45:41 yep, please 09:45:44 dmellado: but that is just adding dir structure 09:45:53 no config register i can see 09:46:01 oh, got a local one 09:46:12 I'll push it and pls comment on the config stuff 09:46:20 or I can follow-up on the main qa channel 09:46:20 dmellado: if you can put up even WIP there i can check 09:46:22 no worries 09:46:29 dmellado: sure, Thanks 09:46:46 anything else on Tempest? 09:47:32 nothing from my side ;) 09:47:42 ok. let's directly jump to Critical Reviews 09:47:45 #topic Critical Reviews 09:47:53 any critical review here? 09:48:25 I will add microversion patches again :) 09:48:27 #link https://review.openstack.org/#/q/topic:bp/api-microversions-testing-support+status:open 09:49:14 gmann: I added me as a reviewer for them :) 09:49:27 masayukig: Thanks 09:49:57 on base patch, took time on autodoc thing. 09:50:09 finally it was on shape :) 09:50:17 good suggestion by mtreinish. 09:50:23 #topic open discussion 09:50:37 anything else needs to be discussed from anyone 09:51:05 we still have ~9 min 09:51:33 will there be a bbq at Austin? xD 09:51:49 :) 09:51:51 dmellado: nice :) 09:52:07 besides joking, is there any plan to set up a meeting there, like you did at Tokyo? 09:52:46 dmellado: nice idea, may be but we can see during summit planing 09:53:06 cool ;) 09:53:11 mainly for AI for PTL (mtreinish ) :P 09:53:18 dmellado: I think we had like it every summit. 09:54:05 ok. let's close the meeting 09:54:06 3... 09:54:08 2.. 09:54:10 1. 09:54:17 Thanks All for joining 09:54:19 #endmeeting