22:01:34 <mtreinish> #startmeeting qa
22:01:35 <openstack> Meeting started Thu May 28 22:01:34 2015 UTC and is due to finish in 60 minutes.  The chair is mtreinish. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:01:36 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:01:39 <openstack> The meeting name has been set to 'qa'
22:01:46 <mtreinish> hi, who's around for the meeting today?
22:02:00 <masayukig> o/
22:02:00 <rockyg> o/
22:02:15 <mtreinish> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_May_28th_2015_.282200_UTC.29
22:02:19 <mtreinish> ^^^ today's agenda
22:02:26 <mtreinish> basically boilerplate this week
22:03:50 <mtreinish> dkranz, dtroyer, jogo: around?
22:04:05 <dkranz> 0/
22:04:47 <mtreinish> ok, let's get started
22:04:56 <mtreinish> #topic Specs Reviews
22:05:13 <mtreinish> does anyone have any open specs reviews to discuss?
22:05:37 <mtreinish> I put one on the agenda, but we can get to that after/if there are any others
22:06:00 <dkranz> mtreinish: not from me. I posted an update of the tempest config script
22:06:20 <dkranz> mtreinish: that spec should maybe be updated as well
22:06:23 <mtreinish> dkranz: on that spec? or the script itself?
22:06:25 <mtreinish> ah, ok
22:06:49 <mtreinish> dkranz: yeah we probably should update the spec too
22:07:08 <dkranz> mtreinish: let's see if we can get to resolution on the patch and then I"ll update the spec
22:07:16 <mtreinish> ok
22:07:23 <mtreinish> kinda backwards, but whatever :)
22:07:43 <dkranz> mtreinish: well, the high-level is still the same. Just some choices are made in the patch.
22:08:26 <mtreinish> heh, ok sure. I was just kidding :)
22:08:38 <mtreinish> well I guess we'll talk about my spec on the agenda now:
22:08:41 <mtreinish> #link https://review.openstack.org/184992
22:08:55 <mtreinish> that's the 2nd time around on the plugin interface spec
22:09:04 <mtreinish> I'd appreciate if people had any thoughts on it
22:09:11 <dkranz> mtreinish: some one said mkoderer had already put up something in manila that uses it
22:09:24 <dkranz> mtreinish: I like it.
22:09:46 <dkranz> mtreinish: There are some technical details about setuptools and the like that I am not an expert on
22:10:25 <mtreinish> dkranz: yeah we can ask dhellmann about the stevedore and entry point little details, but at the high level it should work like that
22:10:43 <dkranz> mtreinish: right, the implied and stated requirements seem right
22:11:19 <mtreinish> dkranz: yeah mkoderer already has a bp up on the manila side to use this (once it's ready)
22:11:37 <dkranz> mtreinish: I"ll take a look
22:11:44 <mtreinish> #link https://blueprints.launchpad.net/manila/+spec/tempest-plugin-interface
22:12:17 <masayukig> mtreinish, mkoderer : great!
22:13:01 <dkranz> Is there some work I could help with to move stuff into tempest lib? We don't have a real task list for that.
22:13:14 <mtreinish> I expect the code side for the actual plugin handling won't be too difficult once we have a tempest run command in place (which is the bigger blocker for this)
22:13:38 <mtreinish> dkranz: hmm, we started to list a few of the items on the priorties session etherpad
22:13:44 <mtreinish> but other than that there isn't a complete list
22:14:09 <mtreinish> that's probably something we should work on
22:14:30 <mtreinish> you should ask mkoderer what are the bits from tempest that he's still importing in manila
22:14:35 <mtreinish> because that'll be a good starting point
22:14:37 <dkranz> mtreinish: yes, and I will ping david patterson and see if he can move along with the cmd stuff
22:14:42 <dkranz> mtreinish: good idea
22:14:57 <mtreinish> dkranz: oh, that was the next spec I was going to bring up
22:15:09 <mtreinish> #link https://review.openstack.org/138785
22:15:29 <mtreinish> it's getting there there were just a few little issues with it to fix before we can merge it I feel
22:15:50 <mtreinish> feel free to pile on that review so dpaterson doesn't have to do multiple revs :)
22:16:07 <dkranz> yup
22:16:36 <dkranz> Looks like cliff does most of the work
22:16:42 <mtreinish> yep
22:16:46 <dkranz> nice
22:17:39 <mtreinish> ok, is there anything else to discuss on specs?
22:18:14 <dkranz> not from me
22:18:58 <mtreinish> ok, then let's move on
22:19:07 <mtreinish> #topic Blueprints
22:19:24 <mtreinish> does anyone have any open BPs that they'd like to bring up?
22:21:13 <mtreinish> I did update the tempest launchpad to add liberty, the target milestone dates, and switched it to the active dev branch
22:21:20 <mtreinish> because someone pointed out that was missing last week
22:21:37 <mtreinish> ok if there isn't anything else I guess we can move on
22:22:03 <mtreinish> #topic DevStack
22:22:06 <mtreinish> dtroyer: around?
22:23:29 <mtreinish> I guess not :)
22:23:45 <mtreinish> I don't have anything on devstack this week
22:23:54 <mtreinish> does anyone have anything to bring up about devstack?
22:25:13 <mtreinish> ok, then let's move on
22:25:19 <mtreinish> #topic Grenade
22:25:27 <mtreinish> jogo: around?
22:25:45 <mtreinish> the only grenade thing I have this week is sdague's patch to add the external plugin support to grenade
22:26:06 <mtreinish> #link https://review.openstack.org/185050
22:26:39 <mtreinish> that'll be good to get eyes on
22:26:51 <mtreinish> although, I haven't had a chance to look at it yet :)
22:27:05 <mtreinish> fwiw, it looks short :)
22:27:23 <mtreinish> ok, does anyone have anything else on grenade?
22:27:51 <dkranz> mtreinish: well, the periodic jobs still fail. NOt sure if that is related.
22:28:09 <dkranz> mtreinish: I asked about it on #infra but didn't get a response
22:28:30 <mtreinish> dkranz: yeah that's kinda unrelated
22:28:36 <dkranz> mtreinish: ok, later
22:28:44 <mtreinish> I talked to fungi about it briefly at summit
22:29:10 <dkranz> mtreinish: I verified that our periodic jobs, and only those, have the error
22:29:11 <mtreinish> from what I saw it looks like devstack dir isn't where it's expected to be on the periodic jobs only
22:29:21 <mtreinish> so it's either a bug in devstack-gate or the job definition for those
22:29:31 <mtreinish> since the nodepool image should be the same
22:29:34 <dkranz> mtreinish: yeah
22:29:52 <mtreinish> although that would still be weird because the bits should be the same for periodic and regular jobs
22:30:01 <mtreinish> I haven't had a chance to dig any further than that though
22:31:14 <mtreinish> ok if there isn't anything else on grenade let's move on
22:31:33 <mtreinish> #topic Bugs
22:31:55 <mtreinish> I don't have anything to discuss on bugs this week
22:32:18 <mtreinish> although I expect our new bug count has grown a bit in the past couple of weeks
22:32:28 <mtreinish> we probably should start getting better about the triage rotations again
22:32:53 <mtreinish> does anyone else have anything to discuss about bugs?
22:33:08 <dkranz> no
22:33:15 <mtreinish> heh, ok
22:33:33 <mtreinish> then let's move on
22:33:38 <mtreinish> #topic Critical Reviews
22:34:00 <mtreinish> does anyone have any reviews to bring up that could use some additional eyes?
22:34:35 <mtreinish> #link https://review.openstack.org/170272
22:35:07 <mtreinish> should be a quick one, to switch tempest-lib over to using os-testr
22:35:30 <mtreinish> the tempest patch doing the same I need to rebase, but that should be up soonish
22:35:43 <mtreinish> #link https://review.openstack.org/170270
22:36:10 <mtreinish> any other reviews?
22:36:19 <dkranz> I'll take a look at that
22:37:16 <mtreinish> at least on the tempest side it'll be partially superseded by the tempest cli
22:37:34 <mtreinish> I expect we'll change the tox job definitions to use tempest run when that's available
22:37:37 <dkranz> maybe entirely superseded
22:37:52 <dkranz> is there something in os-testr that is not expected in 'tempest run'?
22:38:18 <mtreinish> dkranz: not really, I just don't want to break people who are used to the traditional run model
22:38:26 <mtreinish> also we'll still need os-testr to pull in subunit-trace
22:38:33 <dkranz> mtreinish: which run  model?
22:38:53 <mtreinish> dkranz: the way you use tempest now, just calling the test runner on a raw checkout
22:39:17 <mtreinish> that should still work even if we move everything to default to use the cli and system program default
22:39:43 <dkranz> mtreinish: the package yes, but I'm wondering if we should introduce a new way to run if we are shortly going to recommend another new way?
22:40:16 <dkranz> mtreinish: there are people (like me) who often use pretty_tox
22:40:28 <mtreinish> dkranz: it's not really a new way. I don't know of anyone who uses pretty_tox.sh directly, it's not something that's really user facing
22:40:41 <mtreinish> (well jgriffith did for a while but that was a bug on his end :) )
22:41:19 <dkranz> mtreinish: It depends on if you are using tox or not
22:41:43 <dkranz> mtreinish: anyway, not a big deal. I'll comment in the review
22:41:50 <mtreinish> dkranz: ok, thanks
22:42:01 <mtreinish> ok, are there any other reviews to bring up?
22:43:12 <mtreinish> ok, then let's open the floor
22:43:15 <mtreinish> #topic Open Discussion
22:43:38 <mtreinish> ok, are there any topics people wish to discuss which weren't on the agenda
22:44:23 <masayukig> nothing from me at this time :-)
22:44:27 <dkranz> mtreinish: just the periodic thing
22:44:52 <mtreinish> dkranz: ok, yeah that's something to fix. But, I don't have anymore details on it right now
22:45:01 <dkranz> mtreinish:  ok
22:45:45 <mtreinish> ok, if there's nothing else let's end for today
22:45:48 <mtreinish> thanks everyone
22:45:54 <mtreinish> #endmeeting