17:00:51 <oomichi> #startmeeting qa 17:00:52 <openstack> Meeting started Thu Mar 31 17:00:51 2016 UTC and is due to finish in 60 minutes. The chair is oomichi. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:53 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:55 <openstack> The meeting name has been set to 'qa' 17:01:07 <oomichi> hi, anyone here today ? 17:01:13 <dmellado> o/ 17:01:28 <tosky> hi 17:01:36 <dmellado> oh, hi tosky ;) 17:01:53 <mtreinish> o/ 17:02:03 <jswarren> o/ 17:02:03 <oomichi> hi all :-) 17:02:13 <oomichi> ok, lets get start 17:02:27 <oomichi> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_March_31th_2016_.281700_UTC.29 17:02:34 <oomichi> ^^^ today agenda 17:02:37 <luzC> o/ 17:02:45 <oomichi> #topic #Spec reviews 17:03:16 <oomichi> there are some active specs 17:03:28 <oomichi> #link https://review.openstack.org/#/q/status:open+project:openstack/qa-specs,n,z 17:03:46 <oomichi> one is o-h spec 17:03:56 <oomichi> that seems old now, is it necessary still now? 17:04:15 <oomichi> #link https://review.openstack.org/#/c/233187/ 17:04:31 <mtreinish> oomichi: I think I asked that exact question in the spec :) 17:04:33 <oomichi> most part seems already implemented, it seems unnecessary 17:04:53 <oomichi> mtreinish: to andreaf? 17:05:14 <jordanP> oomichi, no, in a comment 17:05:38 <jordanP> I mean, yes to andreaf, but on Gerrit 17:05:45 <oomichi> jordanP: ah, I see. 17:05:57 <oomichi> ok, lets wait for andreaf comment 17:06:01 <mtreinish> oomichi: yeah I left a comment on it asking why it's still need. I also screwed up with gertty and dropped my -1 by accident 17:06:40 <dmellado> gertty is dangerous, even more if there's a cat around... 17:06:43 <oomichi> mtreinish: yeah, it is nice to put -1 for getting attention 17:06:49 <oomichi> again 17:07:16 <oomichi> btw, I put another spec: https://review.openstack.org/#/c/297473/ 17:07:32 <oomichi> that is for changing json-schema format for fitting swagger 17:07:47 <oomichi> swagger is defined as standard in all openstack projects 17:08:07 <mtreinish> oomichi: is that just changing how we write the dictionaries in the schema files? 17:08:08 <oomichi> so I feel it is nice to make our json-schema also fit it 17:08:20 <oomichi> mtreinish: yeah, right. that is a small changes 17:08:33 <oomichi> in schema files 17:08:50 <jordanP> does Swagger "enforce"/check the response as json-schema does ? 17:08:51 <mtreinish> oomichi: is there something we gain by doing that? I mean sure swagger is "the direction" but it's not like we're gonna generate api docs from tempest 17:09:17 <oomichi> jordanP: sorry, I cannot catch your meanin 17:09:53 <oomichi> mtreinish: no, that is not current purpose. 17:10:17 <jordanP> I though we use json-schema because it has a python binding that checks that the responses we got match the expected response 17:10:28 <oomichi> I don't think it is nice to generate doc from tempest at this time, but that is a surper long-term direction for me 17:10:57 <oomichi> jordanP: yeah, you are right. 17:10:59 <jordanP> in Tempest we have "import jsonschema", are we going to replace this with "import swagger" ? 17:11:48 <jordanP> anyway, this looks like low priority to me, like a "nice to have" 17:11:52 <oomichi> jordanP: swagger is using jsonshema as the definition. but we defined some part of our jsonschema by our own way 17:11:56 <mtreinish> oomichi: right, so I'm wondering is all the churn necessary just to be consistent with an API WG recommendation? 17:12:02 <oomichi> I am trying to change it to swagger way 17:12:39 <jordanP> ok. If that's a relatively small/contained change, then go for it :) 17:12:47 <oomichi> mtreinish: nice point. all jsonschema definition can be changed in tempest for that. 17:13:18 <dmellado> oomichi: so then all the jsonschema will have to be changed? 17:13:32 <oomichi> dmellado: yeah, I hope so. 17:13:46 <oomichi> it is not difficult, but many ;-( 17:14:03 <dmellado> again xD 17:14:05 <oomichi> so it is nice to get some helps for that 17:14:19 <oomichi> dmellado: yeah, nice point. sorry about that 17:14:39 <dmellado> I've one question, would the API WG change (swagger) affect the tempest compatibility when it comes to previous os pversions? 17:15:03 <dmellado> I'm not really savy in terms of this swagger stuff, so I could use some explanation on this 17:15:06 <mtreinish> oomichi: right, that's why I'm asking do we really want to do this? I feel like this doesn't buy us anything really useful besides saying we use swagger 17:16:30 <oomichi> mtreinish: humm, *I* really want to buy ;_) 17:16:40 <oomichi> mtreinish: humm, *I* really want to buy ;-) 17:17:03 <mtreinish> oomichi: ok, I'll tkae up my concerns in the review 17:17:07 <mtreinish> we continue discussing there 17:17:15 <jordanP> yes 17:17:16 <dmellado> +1 17:17:19 <oomichi> mtreinish: thanks, yea, lets move on 17:17:29 <oomichi> thanks all :-) 17:17:44 <oomichi> does anyone have more topic about spec now? 17:18:04 <oomichi> ok, lets move on to the next topic 17:18:22 <oomichi> #topic priority items 17:18:39 <oomichi> #link https://etherpad.openstack.org/p/mitaka-qa-priorities 17:19:07 <mtreinish> oomichi: fwiw, there is 1 week left in mitaka :) 17:19:15 <oomichi> most targets are done in mitaka 17:19:25 <mtreinish> not a lot of time left to close any last min things 17:19:26 <oomichi> mtreinish: yeah, just one week 17:19:52 <oomichi> do we have any items before mitaka now? 17:20:10 <jordanP> I think "Finalize ssh-auth bp" is done 17:20:18 <jordanP> that's what jlanoux and andreaf said 17:20:20 <jordanP> last meeting 17:20:26 <oomichi> jordanP: cool :_) 17:21:11 <oomichi> ok, how about concentrating on the next cycle? 17:21:26 <oomichi> for the next summit topics 17:21:51 <oomichi> that is next next next topic 17:22:02 <jordanP> lol 17:22:06 <dmellado> xD 17:22:11 <jordanP> sure sure sure 17:22:12 <oomichi> ok, lets move on 17:22:21 <oomichi> #topic Tempest 17:22:53 <oomichi> there are still a lot of tempest patches 17:23:02 <oomichi> #link https://review.openstack.org/#/q/project:openstack/tempest 17:23:37 <oomichi> I dont have any topic about tempest now 17:23:41 <oomichi> do anyone have that? 17:24:15 <jordanP> my patch to replace httplib2 by urllib3 is green: https://review.openstack.org/#/c/295900/ 17:24:29 <dmellado> jordanP: saw it, I think it'd be great to have that in mitaka 17:24:34 <jordanP> other than that, my next match is going to remove our dependency on mox 17:24:42 <dmellado> and not related directly to tempest, but I'd love to have reviews on this 17:24:45 <dmellado> https://review.openstack.org/#/c/274023/ 17:24:46 <jordanP> we should use mock nowadays 17:25:13 <dmellado> jordanP: any other 'deprecated' lib? 17:25:16 <mtreinish> jordanP: we use mock in most places IIRC 17:25:20 <oomichi> jordanP: ok, will review it later 17:25:26 <mtreinish> there might be a few lingering mox usages from when I first added unit tests 17:25:28 <jordanP> yeagh, replacing mox is going to be triviial 17:25:34 <oomichi> #link https://review.openstack.org/#/c/249100/ 17:25:43 <oomichi> #link https://review.openstack.org/#/c/274023/ 17:25:47 <jordanP> I already have the patch, it's a 30 lines patch. Going to submit it soon 17:26:12 <jordanP> dmellado, you should seek support from Neutron guys on this patch 17:26:13 <oomichi> jordanP: one question 17:26:26 <dmellado> jordanP: I'm doing that too ;) 17:26:43 <oomichi> jordanP: about https://review.openstack.org/#/c/249100/ 17:27:04 <oomichi> that is adding volume test, and most volume test tends to wast the time 17:27:07 <mtreinish> the only critical thing I have for tempest this week is: https://review.openstack.org/297322 17:27:20 <oomichi> jordanP: the patch is good from the viewpoint? 17:27:23 <mtreinish> we just need to make sure that lands before we can push the next tempest release to mark mitaka 17:27:54 <oomichi> mtreinish: that contains jordanP comment, that seems reasonable 17:27:57 <jordanP> oomichi, this patch is good yes. But let's not merge it before we reach concensus about what should we do about long running tests 17:28:24 <jordanP> and tests that only touch one service 17:28:24 <oomichi> jordanP: ok, nice info. nice to mark it as WIP 17:28:54 <mtreinish> jordanP: we do have the slow tag, which will make it only run on periodic/experimental 17:29:20 <jordanP> it's not a WIP, anyway. Ahh yeah, I forgot about the slow tag. Good idea 17:29:45 <jordanP> let's not worry about this patch 17:29:49 <dmellado> yes, please it'll be nice to add that slow tag in the notes too 17:30:02 <oomichi> jordanP: hehe, ok. fine :-) 17:30:15 <jordanP> next cycle I am going to focus on reducing technical debt and complexity in tempest 17:30:22 <jordanP> and try to have faster running tests 17:30:22 <mtreinish> jordanP: awesome 17:30:36 <oomichi> jordanP: cool ;) 17:30:47 <dmellado> how about the tempest refactor? 17:30:56 <dmellado> will that be included in your goal jordanP ? 17:31:21 <oomichi> dmellado: ah nice point. 17:31:25 <jordanP> "refactor" is a big vague. what do you have in mind ? 17:31:28 <jordanP> *bit 17:31:35 <dmellado> jordanP: well, it was marked as a point for mitaka 17:31:44 <jordanP> if refactoring needs to be done, refactoring will be done 17:31:58 <jordanP> dmellado, link ? 17:32:04 <dmellado> and I was wondering about the exact meaning too 17:32:06 <oomichi> dmellado: maybe you are saying https://review.openstack.org/#/c/92804/ ? 17:32:11 <dmellado> oomichi: let me check 17:32:12 <jordanP> ah ok 17:32:22 <jordanP> https://etherpad.openstack.org/p/tempest-refactor-ideas 17:32:33 <dmellado> jordanP: yep 17:32:37 <oomichi> #link https://etherpad.openstack.org/p/tempest-refactor-ideas 17:32:59 <dmellado> maybe we can chat about the exact goal in the design summit 17:33:00 <mtreinish> oh, that etherpad I made. It was just a title, I didn't put deep meaning behind the title 17:33:01 <jordanP> yeah, there are some good ideas there 17:34:00 <oomichi> that is already put on the session proposals on the etherpad 17:34:09 <oomichi> as design session 17:34:16 <dmellado> oomichi: cool then ;) 17:34:40 <oomichi> ok, anyone have more topic about tempest now? 17:35:23 <oomichi> #topic DevStack + Grenade 17:35:43 <oomichi> dtroyer: are you there for devstack? 17:36:20 <mtreinish> the only news here I think is we've branched devstack and grenade for mitaka 17:36:44 <oomichi> mtreinish: nice news:-) 17:36:58 <oomichi> ah, one question about devstack 17:37:29 <oomichi> sometime devstack makes bugs disappear because it changes default setting values 17:37:49 <oomichi> and we faced bugs on production clouds 17:38:08 <oomichi> so I feel it is nice to make devstack small as possible 17:38:20 <mordred> oomichi: ++ 17:38:23 <oomichi> is it a right direction 17:38:23 <jordanP> that's the current direction indeed 17:38:26 <oomichi> ? 17:38:27 <jordanP> devstack plugins and stuff 17:38:28 <mtreinish> oomichi: devstack tries to use the defaults where possible, but sometimes we can't always 17:38:40 <mordred> (also, btw, devstack-gate should contain as little extra logic that's not in devstack itself) 17:38:50 <oomichi> mtreinish: yeah, that is difficult point 17:39:10 <oomichi> mordred: ah, nice advice, thanks 17:39:40 <oomichi> ok, my question is done, thanks 17:39:48 <jordanP> I didn"t see any question :) 17:39:54 <jordanP> I yes, my bad 17:40:03 <jordanP> the question mark came after 17:40:13 <oomichi> jordanP: yeah, I was not sure that is right direstion to be honest 17:40:30 <jordanP> I think it is the right direction and devstack plugins are awesome 17:40:34 <mordred> I have a question that may fit on this general topic, but it might should have come up when the topic was tempest (sorry) 17:40:35 <jordanP> we have so many of them, it works 17:41:09 <mtreinish> mordred: go for it 17:41:09 <oomichi> jordanP: ok, lets talk about it on open discussion 17:41:17 <mordred> I have been told that tempest does not do well on clouds that do not have floating ips ... is there anybody working on support for provider-network only clouds and it not would work on such a thing be acceptable? 17:41:38 <mordred> (assuming everyone knows how evil I tink fips are in the first place) 17:41:39 <mtreinish> mordred: it should work fine, but I don't think that's the default configuration 17:41:53 <mordred> mtreinish: ok. so there should be a config setting I just need to find? cool 17:42:04 <jordanP> I don"t think it should work well 17:42:07 <mordred> mtreinish: I will look harder and find you for follow up questions if I can't find it 17:42:15 <jordanP> the scenarios assume floating ip now 17:42:17 <mtreinish> mordred: likely a couple of options 17:42:21 <mordred> ah 17:42:22 <mtreinish> jordanP: really, that's broken 17:42:26 <mordred> jordanP: so I might need to update scenarios? 17:42:35 <jordanP> lemme double check, but I think so 17:42:55 <dmellado> mordred: but that could also be the case for scenarios coming from plugins... 17:43:01 <mtreinish> mordred: I was gonna point you to: http://docs.openstack.org/developer/tempest/configuration.html#enabling-remote-access-to-created-servers 17:43:29 <dmellado> let's wait for jordanP 17:43:31 <mordred> dmellado: I think right now we're just trying core stuff, but good point - I'll start looking through those next 17:43:44 <mordred> mtreinish: awesome docs thing 17:44:00 <jordanP> no I think am wrong :) 17:44:05 <jordanP> sorry about that 17:44:17 <jordanP> mordred, https://github.com/openstack/tempest/blob/master/tempest/scenario/manager.py#L644 17:44:29 <jordanP> the relevant config flag is CONF.validation.connect_method 17:44:43 <mordred> woot! that's happy making. 17:44:58 <mordred> best openstack meeting ever. thanks everybody 17:45:04 <dmellado> so that's the same as per mtreinish link ;) 17:45:33 <oomichi> mordred: cool :) 17:45:54 <oomichi> anyone have more items about devstack? 17:46:09 <oomichi> ok, lets move on 17:46:13 <oomichi> #topic Austin Summit 17:46:23 <oomichi> #link https://etherpad.openstack.org/p/newton-qa-summit-topics 17:46:33 <oomichi> we have 8 ideas now for 8 slots 17:46:41 <jordanP> pb is we have a couple of scenarios (2 or 3) that calls directly manager.create_floating_ip(). This should be fixed and use get_server_ip() instead. This is something to look at 17:46:50 <oomichi> so it is nice to get more ideas on the etherpad 17:46:53 <mtreinish> oomichi: I counted 9 :) 17:47:11 <oomichi> mtreinish: ah, miss:-( 17:47:51 <oomichi> are there any strong recommendation about the summit topic? ;) 17:48:05 <oomichi> it is nice to vote for each session by writting names 17:48:17 <mtreinish> oomichi: when will we make decisions? 17:48:45 <oomichi> mtreinish: you and me, and when..? sorry, I need to know it 17:49:07 <mtreinish> oomichi: well we've done it as part of the qa meeting in the past 17:49:20 <dmellado> what's the ETA for the decission before the summit? 17:49:53 <oomichi> that is based on the voting I feel 17:50:06 <mtreinish> oomichi, dmellado: I think we'll probably make decisions on like the 14th 17:50:22 <mtreinish> we need to have things sorted a week or 2 before summit starts 17:50:46 <oomichi> mtreinish: thanks. OK, I will send a mail to -dev about this later with the deadline 17:51:12 <oomichi> ok, lets move on 17:51:19 <oomichi> to the next topic 17:51:25 <oomichi> #topic critical reviews 17:51:39 <oomichi> please put patch links for that;-) 17:52:35 <jswarren> Not critical, but would love to get eyes on https://review.openstack.org/#/c/293052/ 17:52:44 <oomichi> jswarren: thanks 17:52:54 <oomichi> #link https://review.openstack.org/#/c/293052/ 17:53:22 <oomichi> any more? 17:53:42 <jordanP> jswarren, it would be great if you could ping andreaf about it 17:54:02 <jswarren> jordanP: Ok. Will do. 17:54:30 <mtreinish> jswarren: does that conflict with the change we pushed at the midcycle for cleaning up the aliasing in one of those files 17:55:06 <jswarren> mtreinish: trying to remember. 17:55:40 <jswarren> That was https://review.openstack.org/#/c/283806/ 17:55:46 <mtreinish> jswarren: yeah I think so 17:56:16 <jswarren> It does not conflict. 17:56:33 <mtreinish> ok cool 17:56:36 <mtreinish> was just curious 17:57:30 <oomichi> both are now by jswarren now 17:57:42 <oomichi> it is nice to write on dependency? 17:57:51 <oomichi> just an idea 17:58:03 <jswarren> They are actually not dependent. 17:58:30 <oomichi> jswarren: we can avoid some concern like mtreinish's one 17:58:47 <oomichi> jswarren: it is nice to keep it on current way also 17:59:04 <oomichi> just one idea ;) 17:59:26 <oomichi> are there any topic about this more? 18:00:01 <oomichi> ok, thanks all 18:00:05 <oomichi> #endmeeting