22:02:09 <mtreinish> #startmeeting qa
22:02:10 <openstack> Meeting started Thu Oct  2 22:02:09 2014 UTC and is due to finish in 60 minutes.  The chair is mtreinish. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:02:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:02:13 <openstack> The meeting name has been set to 'qa'
22:02:17 <mtreinish> hi who do we have here today?
22:02:26 <masayukig> o/
22:02:29 <mtreinish> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_October_2nd_2014_.282200_UTC.29
22:02:33 <mtreinish> ^^^ Today's agenda
22:03:50 <dpaterson> o/
22:04:04 <mtreinish> ok well let's get started and maybe more people will trickle in
22:04:17 <dkranz> mtreinish: hi
22:04:20 <mtreinish> #topic tempest-2 tag (mtreinish)
22:04:22 <gmann> hi
22:04:48 <mtreinish> so now that havana is eol, I'm planning to push the next tag
22:05:00 <mtreinish> but since the juno release is so close I was wondering if we should just wait until that
22:05:28 <mtreinish> because it's not like this tag will really be dropping havana support (which would be the point of doing it at an eol)
22:05:34 <dkranz> mtreinish: I would vote to wait
22:05:57 <dkranz> mtreinish: I think we said at each release and halfway between, right?
22:06:11 <mtreinish> dkranz: no, each release and stable eol
22:06:41 <mtreinish> although based on the new stable schedule that would probably be about each release and halfway between
22:06:46 <dkranz> ok
22:07:13 <mtreinish> dkranz: the idea was to frame which releases are supported by the tag
22:07:16 <dtroyer> o/ here now…
22:08:09 <mtreinish> ok, well I guess since there are no nays I'll just make the tempest-2 tag at the Juno release
22:08:21 <mtreinish> #info tempest-2 tag going to wait until the Juno release
22:08:35 <mtreinish> ok let's move on, unless someone else has something to add
22:09:18 <mtreinish> #topic Blueprints
22:09:41 <mtreinish> #link https://blueprints.launchpad.net/tempest/juno
22:10:00 <mtreinish> so we're basically at the end of the cycle
22:10:16 <mtreinish> I'm thinking we'll end up deferring a bunch of open bps
22:10:27 <mtreinish> although andreaf left a status update on some of the bps he's been working on
22:10:46 <mtreinish> and I think we'll be able to close out a couple more before the end of the cycle
22:11:02 <mtreinish> that being said, does anyone have any status updates on an open bp?
22:11:04 <dkranz> mtreinish: Does deferring really mean anything other than changing the release field?
22:11:42 <mtreinish> dkranz: no, not really
22:12:12 <mtreinish> although we haven't figure out how we want to handle the specs
22:12:28 <dkranz> https://blueprints.launchpad.net/tempest/+spec/client-checks-success is nearly done except for nova
22:12:31 <mtreinish> some of the other projects are making people resubmit for new cycles, although I'm not sure we want to do that
22:13:01 <dkranz> mtreinish: but since we are really talking about changing the client interface to return one value, there is no point in finishing it as is
22:13:13 <mtreinish> dkranz: ok, yeah nova is the big one
22:13:30 <mtreinish> dkranz: well doing the status code in the clients would still be a part of that right?
22:13:31 <dkranz> mtreinish: But when we change to return one value, it touches all the same code in the tests, so might as well wait
22:13:52 <mtreinish> oh yeah, good point
22:14:16 <dkranz> I am  eager to get going on removing _, x = () crap
22:14:33 <dkranz> We now have a ton of it :)
22:14:51 <masayukig> dkranz: agreed :)
22:14:58 <mtreinish> dkranz: well, throw up a quick spec for the new return format. We may not need to wait until summit to start that
22:15:27 <dkranz> mtreinish: sure, I will just propose what Sean put out
22:16:00 <mtreinish> dkranz: ok, I think I'll be fine with that
22:16:11 <mtreinish> I think everyone else liked it too
22:16:22 <dkranz> mtreinish: BTW, I am continuing to work on the config_tempest thing. But doing it in a way that works with all deployments is touch and needs a lot of internal testing.
22:16:33 <dkranz> mtreinish: I will put up a WIP soon.
22:16:46 <dkranz> mtreinish: I mean is tough
22:17:02 <mtreinish> dkranz: ok, I'm be curious to take a look at that
22:17:09 <dkranz> mtreinish: By internal testing I mean on clouds that we don't have in the gate
22:17:11 <mtreinish> especially because the spec never really went anywhere
22:17:33 <dkranz> mtreinish: I just went with the comments I had made
22:17:49 <dkranz> mtreinish: I needed to do it anywat
22:18:08 <mtreinish> yeah, there were enough comments there from everyone to have a spec just from that :)
22:18:53 <mtreinish> ok are there any other bps to discuss?
22:19:04 <gmann> mtreinish: deferred BP can be worked immediately or needs to wait till tempest tag etc?
22:19:46 <mtreinish> gmann: work can continue, the tag is just a mark to coincide when we dropped or added support for a release
22:19:58 <mtreinish> gmann: although I haven't deffered anything yet :)
22:20:09 <gmann> ohk
22:20:32 <mtreinish> masayukig: I think we're ready to close the scenario migration bp too, unless there's something we missed
22:20:54 <mtreinish> the reason the cli tests still worked with the requirements drop is because devstack installs them from git, and the gate runs with site-packages=True
22:21:26 <mtreinish> although the last part doesn't matter, because it's just looking for the binary :)
22:21:40 <masayukig> mtreinish: yeah, ok. I got it. I agree to close it.
22:22:50 <mtreinish> masayukig: ok cool, can you take care of that on lp?
22:22:57 <dkranz> mtreinish: that reminds me that we should really have a test that installs tempest on a machine that does not have devstack on it.
22:23:18 <mtreinish> dkranz: the unit tests don't have devstack
22:23:41 <dkranz> mtreinish: oh, ok. great.
22:24:27 <mtreinish> ok, last call for any other bps to discuss
22:25:29 <mtreinish> #topic Devstack
22:25:40 <mtreinish> dtroyer: ok, you're up, anything new in the world of devstack?
22:26:22 <dtroyer> I'm starting to get the cleanup-type stuff going before we cut the stable/juno release
22:27:22 <dtroyer> that includes cosmetic stuff like docs bugs and comment cleanups
22:28:15 <dtroyer> we are also backporting the re-worked process handling to stable/icehouse so we can get grenade off using screen.
22:28:39 <dtroyer> (looking) I think they all finally merged…
22:28:56 <mtreinish> dtroyer: yeah I think they did
22:28:57 <dtroyer> that's pretty much it
22:29:12 <mtreinish> dtroyer: ok cool, thanks
22:29:36 <mtreinish> dtroyer: oh, I was curious has there been any updates on making devstack.org more up-to-date?
22:29:46 <mtreinish> someone was asking about that recently
22:31:04 <dtroyer> that's basically me doing the update by hand…
22:31:33 <dtroyer> work has begun to move the hosting to infra-managed server so that should eventually be automated
22:31:59 <mtreinish> dtroyer: sry, I meant the infra-hosted automation part
22:33:27 <dtroyer> ah, ok.  not sure, anteaya has been handling that.  I understand the domain transfer has happened so they're willing to do something now
22:33:44 <anteaya> o/
22:33:48 <anteaya> what did I do?
22:34:01 <dtroyer> anteaya: devstack.org rehosting
22:34:02 <anteaya> yes the devstack.org under infra thing?
22:34:20 <mtreinish> anteaya: yeah, is there anything going on there?
22:34:23 <anteaya> yeah so fungi is getting the foundation owned domain name on the correct rackspace server
22:34:39 <anteaya> so we can point it where we need to point it, when we have something to point it at
22:35:02 <anteaya> right now one of the two parties has a ticket, something about that name in use as a subdomain
22:35:12 <anteaya> fungi is working to get that straigtened out
22:35:23 <anteaya> then make a server, or put it on one we have
22:35:32 <anteaya> and create publish jobs to publish it and host
22:35:42 <anteaya> is how I am envisioning things thus far
22:35:54 <anteaya> but hey, y'know, obstacles
22:36:00 <anteaya> that's what I have
22:36:17 <mtreinish> anteaya: ok, very cool. Yeah, that seems like a good approach
22:36:23 <anteaya> okay
22:36:29 <mtreinish> I was just curious where we stood on that stuff
22:36:32 <anteaya> happy to share status updates as I have them
22:36:41 <anteaya> of course, thanks for letting me update
22:36:59 <mtreinish> ok, then does anyone else have anything else to discuss on devstack?
22:38:03 <mtreinish> #topic Grenade
22:38:21 <mtreinish> jogo, sdague: anything new on grenade?
22:38:35 <mtreinish> I've seen some changes going through around javelin
22:38:56 <mtreinish> and I know progress has been made on stopping screen usage with grenade
22:39:08 <fungi> i hope to get the dns situation worked out for it in the next day or so
22:39:15 <fungi> (oh, new topic)
22:39:21 <mtreinish> fungi: heh, no worries
22:40:50 <mtreinish> ok well, I guess we can come back to grenade later...
22:41:03 <mtreinish> #topic Bugs
22:41:16 <mtreinish> gmann: how does are bug backlog look this week?
22:41:21 <mtreinish> s/are/our
22:41:54 <gmann> Its pretty good progress last week.  new bug went down to 30  - https://etherpad.openstack.org/p/Tempest-bug-report
22:42:03 <sdague> mtreinish: sorry, on grenade front I did land the icehouse patches that should let us get there. cdent is looking in the morning
22:42:37 <mtreinish> sdague: ok cool, thanks
22:42:59 <mtreinish> gmann: yeah, I saw a lot of things being closed out by maurosr this week
22:43:19 <mtreinish> I think he took this week's rotation
22:44:10 <gmann> mtreinish: yes
22:45:09 <mtreinish> gmann: ok, cool. We're slowly getting there. I'm looking forward to 0 new bugs and hopefully we'll be able to maintain it
22:45:22 <dkranz> mtreinish: ++
22:45:32 <gmann> mtreinish: + we keep monitoring the new bugs coming to triage those earlier which is always easy to do for old ones
22:46:02 <gmann> mtreinish: yes. hopefully soon  we will be at 0 :)
22:46:28 <mtreinish> gmann: are there any bugs that stick out that could use some extra eyes on them?
22:47:30 <gmann> mtreinish: currently nothing, but I will let you guys know if something there.
22:47:39 <mtreinish> gmann: ok cool, thanks
22:47:50 <mtreinish> does anyone have anything else to discuss about bugs?
22:48:46 <mtreinish> #topic Critical Reviews
22:49:13 <mtreinish> ok, does anyone have any reviews that they'd like to get some extra eyes on?
22:49:30 <dkranz> mtreinish: It is not mine, but the one I put in the agenda
22:49:59 <mtreinish> dkranz: ah, ok yeah
22:50:09 <mtreinish> #link https://review.openstack.org/#/c/112581/
22:50:15 <mtreinish> that is one large patch
22:50:24 <dkranz> mtreinish: It has two +2 from afazekas and me
22:50:41 <dkranz> mtreinish: I don't see how it could have been smaller. It does what it does.
22:51:07 <mtreinish> well he could have broken the functionality of cleanup_server into a series based on functional groups
22:51:20 <mtreinish> it looks like it's fairly modular to handle new resource types already
22:51:20 <dkranz> mtreinish: It is proportional to the number of resources we have
22:51:42 <dkranz> mtreinish: Yes, that was my main review comment on the first round
22:51:59 <mtreinish> dkranz: yeah, but reading a 1000+ line file takes a lot of time and will be error prone
22:52:34 <dkranz> mtreinish: I guess it is a matter of style. I would rather read 1000 lines than 10 files with 100 lines in different patches
22:53:27 <dpaterson> mtreinish: It's pretty cookie cutter stuff
22:54:06 <mtreinish> it looks that way, but its just a matter of what's easily consumable in a sitting
22:54:18 <mtreinish> but I'm not going to block it on that if it already has 2 +2s
22:54:32 <mtreinish> anyway does anyone else have any other reviews?
22:54:45 <mtreinish> I have a couple this week myself:
22:54:47 <mtreinish> #link https://review.openstack.org/122538
22:54:54 <mtreinish> and
22:54:56 <mtreinish> #link https://review.openstack.org/125735
22:56:31 <mtreinish> ok if there aren't any other reviews I guess we can end early
22:56:46 <mtreinish> I did have summit brainstorming on the agenda
22:56:56 <mtreinish> but there isn't a lot of time left to discuss any topics on the list
22:57:11 <mtreinish> but I guess I'll push for people to add any topics to that list
22:57:31 <mtreinish> even if it's something small given the new summit format it'll be good to just note it beforehand
22:57:44 <mtreinish> #link https://etherpad.openstack.org/p/kilo-qa-summit-topics
22:58:30 <mtreinish> ok, thanks everyone
22:58:36 <dpaterson> tx
22:58:38 <mtreinish> #endmeeting