09:03:09 #startmeeting qa 09:03:10 Meeting started Thu Sep 3 09:03:09 2015 UTC and is due to finish in 60 minutes. The chair is oomichi. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:03:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:03:13 The meeting name has been set to 'qa' 09:03:20 Hi, who all here today? 09:03:24 hi 09:03:28 o/ 09:03:46 \o 09:03:53 hi mkoderer, gmann, dmellado 09:03:58 hi oomichi 09:04:23 ok, lets start meeting 09:04:48 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_September_3rd_2015_.280900_UTC.29 09:04:54 ^^^ Today's agenda 09:05:02 #topic Specs Reviews 09:05:21 so there are some qa-specs 09:05:52 and most specs get -1s and I guess there are not so many topic now 09:06:10 someone want to talk about that? 09:06:26 #link https://review.openstack.org/#/q/status:open+project:openstack/qa-specs,n,z 09:07:05 oomichi: I wanted also to know the state of the external plugins, but IIRC this is going to be covered later, isn't it? 09:07:29 dmellado: yeah, I also want to know :) 09:07:44 dmellado: and that will be the next topic ;) 09:07:52 Ok, let's move onto the next topic 09:08:08 #topic Tempest 09:08:41 according to the agenda, the first topic is from me ;) 09:09:11 I'd like to mention about current status of service client for tempest-lib 09:09:25 +1 for moving the clients to the lib 09:09:40 mkoderer: yeah, thanks 09:09:54 do you need some help? pls let me know if I can help with something 09:09:54 we are working for that on 3 topics 09:10:08 #link https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bp/consistent-service-method-names,n,z 09:10:18 # https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bp/method-return-value-and-move-service-clients-to-lib,n,z 09:10:24 #link https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bp/method-return-value-and-move-service-clients-to-lib,n,z 09:10:34 #link https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:service-client-unit-tests,n,z 09:10:57 mkoderer: much thanks, you can help the above link patches :) 09:11:18 mkoderer: yea, it will be helpful. Thanks 09:11:23 yeah I areadly reviewed a ton of them :) 09:11:30 and most part of nova service clients are done. 09:11:53 as the next step, I will migrate the compute service clients to tempet-lib 09:12:01 oomichi: almost all compute service client unit test patches are up 09:12:11 oomichi: only server client left- https://etherpad.openstack.org/p/tempest-service-client-unit-tests 09:12:17 gmann: yeah, nice progress 09:12:30 #link https://etherpad.openstack.org/p/tempest-service-client-unit-tests 09:12:38 oomichi: you are planning to working on that if not someone else can pick that up 09:12:55 gmann: yeah, thanks for pointing it out. that is difficult, and we need to implement it 09:13:48 gmann: I will try it later after https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bp/consistent-service-method-names,n,z 09:13:58 oomichi: +1 Thanks 09:14:19 ok, I will start reviewing the unit test and then have a look the the etherpad 09:14:20 #action: oomichi implements servers_client unit test 09:14:37 mkoderer: that will be very helpful 09:14:48 mkoderer: Thanks. 09:15:04 #action mkoderer starts reviewing the unit test 09:15:11 mkoderer: ^^^ ;) 09:15:27 :) 09:15:37 so I'd like to ask mkoderer for the next topic 09:15:48 ok 09:15:50 I'd like to know current status of external plugins 09:15:56 +1 ;) 09:16:10 the manila plugin is ready for merge 09:16:12 https://review.openstack.org/#/c/201955/ 09:16:24 #link https://review.openstack.org/#/c/201955/ 09:16:26 but we have a blocking novaclient bug currently in Manila :( 09:16:52 anyway.. I hope that this will be merged within this week 09:16:56 oops, you are asking novaclient release 09:17:10 can you catch someone ? 09:17:22 to release a new novaclient? 09:17:26 oomichi: not yet.. 09:17:49 ok, will check someone later 09:17:58 so in general the external plugin works fine 09:18:10 mkoderer: wow :) 09:18:10 mkoderer: that is great :) 09:18:13 open issue is currently the dependency with tempest 09:18:46 mkoderer: dependency ? 09:18:46 mkoderer: what kind of dependency? 09:18:46 mkoderer: what kind of dependency issues are you dealing with? 09:18:54 e.g. the work on the service clients broke the manila scenario tests 09:19:22 since the scenario test are using other clients and if the client is changed we have to adapt 09:19:42 oops, so we need to implement service client in tempest-lib asap, that will be helpful? 09:19:47 mkoderer: ahh, yea 09:20:02 mainly return value changes causing a lot 09:20:07 I talked to mtreinish and he doesn't like the idea to have a check job for Manila in tempest queue 09:20:19 mkoderer: so then the manila scenario test will have to be rewritten? (or at least adapted?) 09:20:33 dmellado: there are already adapted 09:20:49 mkoderer: great, thnx ;) 09:20:55 mkoderer: one question 09:21:06 but in the current state I need to checkout a commit-id from tempest to ensure that a change in tempest doesn't break the manila gate 09:21:19 mkoderer: on manila gate, do tempest tests also run? 09:21:31 mkoderer: anything from pending return value changes can affect 09:21:34 # link https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bp/method-return-value-and-move-service-clients-to-lib,n,z 09:21:41 mkoderer: or do manila original tests only run? 09:21:44 so that we can try to merge that fast 09:21:58 oomichi: no currently we only run manila api and manila scenario tests 09:22:45 mkoderer: that seems nice. and just using some service clients on manila tests, right? 09:22:48 so with the commit-id we are save and can wait until everything needed is merged to tempest-lib 09:23:36 oomichi: yeah I try to reduce the coupling as much as possible.. and scenario tests are one thing were we can't avoid it 09:23:46 but anyway I think we are on a good track 09:23:56 mkoderer: we are working for implementing nova service clients as the first step. and they will be stable for manila gate in near future 09:24:43 oomichi: yeah that's cool 09:24:55 dmellado: any other question to that topic? 09:25:02 mkoderer: so I don't have plan for the next step after nova service client. do you have any idea for the next service client? 09:25:17 mkoderer: oomichi : may be server_client will affect - https://review.openstack.org/#/c/216559/ 09:25:43 mkoderer: I was thinking about if it would affect the whole scenario test set in the future, besides from manila 09:25:46 mkoderer: ok, I will concentrate on server_client 09:26:23 mkoderer: oomichi gmann Do you know what's in the plan for it, to get them back into each project or tempest will be still having a set of its own scenario tests 09:26:25 ? 09:26:28 I'm kinda lost on that 09:27:09 oomichi: I need also network_client for the manila scneario tests 09:27:23 dmellado: After implementing external plugins in manila, basically we can use it on any projects ideally 09:27:49 dmellado: but as mkoderer said, we will face problems if using tempest code 09:28:00 we could move the scenario test also to a seperate repo 09:28:08 mkoderer: i think network client is in good shape. for return value no changes required 09:28:15 dmellado: and we are working for making these tempest code as library 09:28:18 gmann: ok fine :) 09:28:22 oomichi: that means that at some point, every new scenario test would have to go into its own 'based project' repo, isn't it? 09:28:36 mkoderer: thanks. ok, next target is neutron service client. 09:28:51 mkoderer: that'd be great, because what would happen if a scenario test makes use of more than 1 project 09:29:07 dmellado: yeah, right. 09:29:11 oomichi: thanks 09:30:15 does someone have more topic on this? 09:30:21 nope 09:30:26 it was very interesting for me :) 09:30:43 dmellado: ok for you ? 09:31:20 oomichi: yep, was just thinking about those multi-project scenario tests, but we'll see eventually, thanks! ;) 09:31:33 #action oomichi start implementing neutron service client after migrating nova service client to tempset-lib. 09:31:51 ok, lets move to the next topic 09:32:10 #topic devstack 09:32:23 jamielennox: hi 09:32:44 maybe not 09:33:13 he wrote a topic on the agenda, but no attendence. 09:33:29 do someone have any topics on devstack? 09:33:55 ok, lets move to the next topic 09:33:57 I was having again some issues with F22, will write it to the MK 09:33:59 ML 09:34:19 dmellado: that is devstack? 09:34:32 oomichi: yep 09:34:46 I was just writing when you switched topic ;) 09:34:54 dmellado: can you provide the link? 09:35:10 to share the issue 09:35:15 oomichi: not now but I'll open a bug us and send the link to the ML 09:35:44 dmellado: ah, OK. that will be nice :) 09:35:47 so we can go to the next topic ;) 09:35:56 dmellado: ok :) 09:36:14 #topic critical reviews 09:36:46 I have a couple 09:36:46 are there any patches which need reviews asap? 09:37:03 #link https://review.openstack.org/#/c/209144/ 09:37:40 and #link https://review.openstack.org/#/c/180968/. This one is infra but if you can have a look that would be great. Thanks! 09:37:43 jlanoux: yea, i forgot to review that had open only. I will look into tomorrow 09:37:50 oomichi, not really critical but I'd be great if you could review https://review.openstack.org/#/c/218367/ 09:37:55 gmann: thanks! 09:38:00 thanks! ;) 09:38:17 #link https://review.openstack.org/#/c/218367/ 09:38:50 dmellado: that is good for me, will review later 09:39:21 I also have some reviews 09:39:27 #link https://review.openstack.org/#/c/217459/ 09:39:52 #link https://review.openstack.org/#/c/218705/ 09:40:05 are there more? 09:40:50 dkranz: hi 09:41:18 oomichi: hi :) 09:41:21 dkranz: we are talking critical reviews now 09:41:44 do you have any patches about that? 09:41:57 oomichi: just a sec 09:42:23 dkranz: ok :) 09:42:55 hi dkranz ;) 09:43:17 dkranz: seems you are a real early bird :) 09:43:35 oomichi: oh, the one I wsa thinking of already merged 09:43:42 mkoderer: I am not really here 09:43:57 :) 09:44:01 dkranz: good news :) 09:44:12 Need to go back to bed 09:44:25 dkranz: +1 09:44:26 ok, lets move to the next topic 09:44:42 dkranz: yeah ;) 09:44:58 dkranz: sorry for catching you now 09:45:14 #topic Code Sprint Reminder 09:45:17 oomichi: no worries. You did not wake me up :) 09:45:31 #https://wiki.openstack.org/wiki/QA/CodeSprintLibertyFortCollins 09:45:39 dkranz: :) 09:45:51 so many people can't join the code sprint in person 09:46:06 we will have meetup on FortCollins 09:46:10 if considering the time zone, besides dkranz I guess so ;) 09:46:12 oomichi: do you know how that works remotely ? through etherpad only 09:46:25 mkoderer: yeah, it is 09:46:43 mkoderer: but mtreinish wanted that you join to it 09:46:55 mkoderer: I also 09:47:09 gmann: ah, nice question 09:47:21 oomichi: I know... he wrote me an email.. but traval approval process is hell :( 09:47:45 mkoderer: I can know the situation, I also faced such thing.. 09:48:02 I think remotley is quite probelmatic.. 09:48:10 yea thats most common issue for meetup :) 09:48:12 gmann: there is not any hint for remotely 09:48:19 humm 09:48:31 oomichi: gmann I was checking that as well, but I guess it's meant to be real-time, isn't it? 09:48:49 dmellado: yeah, that should be real-time 09:48:52 dmellado: yea 09:48:58 dmellado: with skype or something 09:49:21 I guess it would make sense to split into groups and do a google hangout for each of them 09:49:37 mkoderer: +1, that will be good 09:49:52 mkoderer: +1 on that, or either try to duplicate it in EMEA region... 09:50:18 mkoderer: nice idea 09:50:54 OK, I will ask mtreinish how to make remote acess and write it on the wiki 09:51:10 dmellado: I am not a big fan of duplication.. since how will we sync then. 09:51:16 oomichi: Thanks 09:51:20 oomichi: +1 09:51:28 #action oomichi ask mtreinish how to make remote conference and write it on the wiki 09:51:30 mkoderer: splitting the topics? 09:52:12 dmellado: ah you mean to do another meetup in EMEA? 09:52:39 mkoderer: something like that, another meetup in EMEA with maybe some of the topics to be covered in the original one 09:53:06 mkoderer: but maybe it's just too close to think about it, given that I can get enough coffee it'd be good to access it remote ;) 09:53:23 yeah we are a bit on time pressure I think 09:54:39 if there are topics you need to join, it is nice to write available time on https://etherpad.openstack.org/p/liberty-qa-code-sprint with UTC 09:54:45 for each topic 09:55:23 maybe we will write code or review except the time ;) 09:55:41 as code sprint 09:55:41 oomichi: ;) 09:56:15 ok, lets move to the next 09:56:26 #topic open discussion 09:56:53 does someone want to talk about something? 09:57:05 nothing from my side 09:57:19 me too 09:57:23 +1 here 09:57:39 mkoderer: do you ? 09:57:47 no we can close the meeting 09:57:59 nice 09:58:05 thx folks 09:58:10 thanks all 09:58:14 #endmeeting