17:00:52 <mtreinish> #startmeeting qa
17:00:54 <openstack> Meeting started Thu Sep 25 17:00:52 2014 UTC and is due to finish in 60 minutes.  The chair is mtreinish. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:55 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:58 <openstack> The meeting name has been set to 'qa'
17:01:08 <mtreinish> hi who's here today?
17:01:12 <mlavalle> hi
17:01:14 <dpaterson> y0
17:01:16 <jlanoux> o/
17:01:16 <andreaf> o/
17:01:20 <mtreinish> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_September_25th_2014_.281700_UTC.29
17:01:23 <mtreinish> ^^^ Today's agenda
17:01:54 <asselin> hi
17:02:11 <mtreinish> ok, let's get started
17:02:17 <mtreinish> #topic Specs Review
17:02:37 <mtreinish> so I don't think there's been any change here, I haven't seen any new specs proposals
17:02:51 <mtreinish> andreaf: and sry I haven't gotten a chance to look at ssh-auth yet
17:03:03 <andreaf> mtreinish, np
17:03:20 <mtreinish> does anyone have a pending spec review they'd like to bring up?
17:04:13 <mtreinish> I think I'm going to drop this topic from the agenda until kilo opens up
17:04:34 <dpaterson> +1
17:04:36 <mtreinish> because I don't see anymore specs going through until we're into summit planning
17:04:36 <andreaf> mtreinish, sounds good
17:04:41 <mtreinish> ok let's move on
17:04:49 <mtreinish> #topic Blueprints
17:05:02 <mtreinish> #link https://blueprints.launchpad.net/tempest/juno
17:05:23 <mtreinish> so I've seen some good progress on bps the last week
17:05:34 <mtreinish> does anyone have any updates on an open bp?
17:05:37 <andreaf> yes
17:05:49 <andreaf> well as masayukig is probably not here
17:06:06 <dpaterson> #link https://blueprints.launchpad.net/tempest/+spec/post-run-cleanup
17:06:08 <andreaf> for the tempest-client-scenario one, all tests are now migrated
17:06:17 <dpaterson> I should be done with one more iteration around doc changes
17:06:19 <mtreinish> andreaf: \o/
17:06:50 <dpaterson> Any more comments before I push another patch set are welcome
17:07:13 <mtreinish> dpaterson: so, when I took a quick look before it looked good. But realize that a patchset that big is very reviewer unfriendly
17:07:24 <mtreinish> so it might be a while before it gets approved
17:07:47 <andreaf> dpaterson, I'll try to have a look tomorrow
17:07:54 <dpaterson> tx
17:08:45 <mtreinish> ok, does anyone else have a bp to bring up?
17:08:49 <andreaf> mtreinish: regarding https://blueprints.launchpad.net/tempest/+spec/tempest-client-scenarios
17:09:12 <andreaf> mtreinish, I now started the cleanup phase, there's a nice series of patches up for review
17:09:42 <andreaf> #link https://review.openstack.org/#/q/topic:bp/tempest-client-scenarios,n,z
17:09:52 <mtreinish> andreaf: yeah, those will be good to land. We can finally get rid of those official workaround paths
17:10:06 <andreaf> it's 1500 LoC less in tempest
17:10:22 <andreaf> next #link https://blueprints.launchpad.net/tempest/+spec/resource-cleanup
17:10:55 <mtreinish> well, sort of. You're not really counting that you duplicated a lot for the tempest client base scenario test classes :)
17:10:55 <andreaf> I posted the first series of patches, a few already merged, others going through the gate, more pending review :)
17:11:13 <andreaf> mtreinish: yes you're right
17:11:22 <andreaf> mtreinish: but it sounded good ;)
17:11:54 <andreaf> #link https://review.openstack.org/#/q/topic:+bp/resource-cleanup,n,z
17:12:31 <andreaf> and finally regarding test accounts bp #link https://blueprints.launchpad.net/tempest/+spec/test-accounts
17:12:44 <andreaf> I solved the issues with the non-isolated jobs
17:12:45 <mtreinish> andreaf: once we get the resource cleanup stuff landed and dpaterson's cleanup tool we can start catch leaked resources in the gate easily which will be awesome
17:13:21 <andreaf> yes that will be really nice to have
17:14:09 <andreaf> gmann had some concerns on https://review.openstack.org/#/c/107685 which I addressed, so the patch is going through check again, but then it should be ready for merge
17:14:47 <mtreinish> andreaf: ok, I'll try to take a look at that today
17:15:05 <andreaf> and once scenario migration and test accounts and resource cleanup are done I'll resume work on the multi auth bp
17:15:19 <andreaf> resource cleanup first part I mean
17:15:23 <mtreinish> andreaf: heh, don't you have enough on your plate? :)
17:15:46 <andreaf> there's the second bit of the resource cleanup to be done, but I'll go around and ask for help for that one
17:16:43 <andreaf> that's all I have on bps
17:16:55 <mtreinish> ok does anyone else have a bp to discuss?
17:17:44 <mtreinish> oh, I did want to bring up tempest-lib
17:18:06 <mtreinish> right now we're blocked on using tempest lib because of global requirements freeze
17:18:36 <mtreinish> for example: https://review.openstack.org/117649 can't pass the gate until kilo opens for global requirements
17:19:15 <mtreinish> so I was curious what thoughts were on open CLI test framework patches (I think there are some)
17:19:42 <mtreinish> I'm thinking we should block everything until kilo opens and move it to tempest-lib
17:20:20 <mtreinish> does anyone have any thoughts on this?
17:20:22 <andreaf> one of the resource cleanup patches is for CLI tests as well
17:21:08 <andreaf> I'd be fine with waiting, only I cannot really enforce the hacking rule until all patches merge
17:21:22 <mtreinish> andreaf: hmm, well that should be harmless I think that can land without issues. I'll just have to rebase the migration patch
17:21:23 <andreaf> I could do an exclusion rule for CLI
17:21:38 <andreaf> mtreinish: ok
17:21:48 <mtreinish> it was more for functional changes to the cli framework. Like around bringing up the clients or the api around calling them
17:22:02 <mtreinish> the patch above shows what it looks like after we move to the lib
17:23:19 <mtreinish> well, I won't start -2 anything until yet :) but I thought I should bring it up.
17:23:35 <mtreinish> ok if there aren't any bps to discuss let's move on
17:24:24 <mtreinish> #topic Devstack
17:24:33 <mtreinish> dtroyer: are you around?
17:25:35 <andreaf> mtreinish: sorry,  I'd have to leave now, do you have anything else specific for me?
17:25:40 <mtreinish> does anyone else have anything to discuss about devstack?
17:26:02 <mtreinish> andreaf: nope your bps were probably it
17:26:30 <andreaf> mtreinish: ok
17:27:09 <mtreinish> ok well lets move on we can come back to devstack if dtroyer shows up
17:27:18 <mtreinish> #topic Grenade
17:27:39 <mtreinish> sdague, jogo: anything new on the grenade front this week?
17:28:25 <mtreinish> I've seen some patches from EmilienM on javelin2 improvments
17:28:26 <sdague> not really
17:28:34 <mtreinish> sdague: ok, thanks
17:28:49 <mtreinish> I guess let's move on to the next topic then
17:29:21 <mtreinish> #topic Bugs
17:29:30 <mtreinish> #link https://etherpad.openstack.org/p/Tempest-bug-report
17:29:47 <mtreinish> gmann pulled the numbers for this week there ^^^
17:30:02 <mtreinish> it looks like we contained growth but didn't help with the backlog on bugs
17:30:58 <mtreinish> looking at the rotation etherpad I think coolsvap|afk volunteered
17:31:17 <mtreinish> but I guess he's not around so he can't provide an update
17:31:41 <mtreinish> #link https://etherpad.openstack.org/p/qa-bug-triage-rotation
17:32:03 <mtreinish> looks like next week maurosr volunteered
17:32:33 <mtreinish> hopefully we'll be able to clear out the new bug backlog and start making better use of the tracker soon
17:32:50 <mtreinish> does anyone else have anything else to discuss about bugs?
17:33:06 <dtroyer> ugh - this schedule…sorry I'm late
17:33:31 <mtreinish> dtroyer: no worries
17:33:55 <mtreinish> oh I guess it's lunchtime for you now
17:34:23 <mtreinish> #topic Devstack
17:34:33 <mtreinish> dtroyer: so anything to discuss about devstack this week?
17:35:28 <dtroyer> I want to start preparing for juno/stable, so basically focusing on stuff we want there.  From the standpoint of what we want for grenade juno -> master
17:35:52 <dtroyer> the one major thing I'm trying to get in yet is rcrit's https://review.openstack.org/#/c/98854/ to change how we do SSL
17:36:35 <dtroyer> that configures everything for ssl, and sets us up to change the tls-proxy.  I'd like to get rid of stud and use apache for that, post stable branch
17:37:30 <mtreinish> dtroyer: yeah doing that through apache would definitely be nicer.
17:37:48 <mtreinish> so are you looking to land anything else before you start the juno branch cut?
17:38:39 <dtroyer> I don't have a specific like prepared, but what is in the queue for migrating services to mod_wsgi
17:38:46 <dtroyer> s/like/list/
17:39:19 <mtreinish> ok, I was just looking for things to prioritze reviews in the minutes
17:39:41 <mtreinish> dtroyer: is there anything else?
17:40:09 <dtroyer> oh, specifically, I'd like to get https://review.openstack.org/111734 in.  the rest of the logging cleanup will have to wait now
17:40:35 <mtreinish> #link https://review.openstack.org/#/c/111734/
17:40:51 <dtroyer> fwiw, the logging stuff is still in https://etherpad.openstack.org/p/devstack-logging, I need to move it to a blueprint and probably actually start using those
17:40:59 <dtroyer> fini
17:41:35 <mtreinish> dtroyer: oh, yeah I was going to talk to you about bps/specs for devstack in kilo
17:41:49 <mtreinish> but we can do that outside of the meeting
17:41:56 <mtreinish> dtroyer: thanks for the update
17:42:08 <dtroyer> I started cleaning up bugs, many to go yet…
17:42:35 <mtreinish> sigh, yeah bugs are a constant process
17:43:08 <mtreinish> ok, lets move on to critical reviews
17:43:12 <mtreinish> #topic Critical Reviews
17:43:29 <mtreinish> ok does anyone have any reviews that they feel could use some extra attention?
17:44:53 <mtreinish> I have 2:
17:44:55 <mtreinish> #link https://review.openstack.org/#/c/113674/
17:45:19 <mtreinish> #link https://review.openstack.org/122861
17:45:42 <sdague> #link https://review.openstack.org/#/c/124069/ is the fix from this morning, had a typo in the first revision, so it's back in check
17:45:50 <sdague> hopefully that will make debugging things easier
17:46:13 <mtreinish> sdague: cool
17:46:49 <mtreinish> ok, if there aren't any other reviews I'll open the floor
17:46:58 <mtreinish> #topic Open Discussion
17:47:13 <mtreinish> does anyone have anything else that they'd like to discuss?
17:48:15 <jlanoux> mtreinish: didn't you want to talk about the summit brainstorming?
17:48:30 <mlavalle> yeah, it's in the agenda
17:48:34 <mtreinish> jlanoux: oh yeah, thanks I missed that :)
17:48:46 <mtreinish> #link https://etherpad.openstack.org/p/kilo-qa-summit-topics
17:48:56 <mtreinish> it was more just a reminder that the etherpad is out there
17:49:10 <mtreinish> and if anyone wanted to discuss something briefly that's on the list now
17:49:22 <jlanoux> mtreinish: ok :)
17:49:48 <mlavalle> so brainstorming means do it to the etherpad and we will refine / discuss later?
17:49:49 <mtreinish> I'm planning to have a dedicated meeting or 2 closer to summit about that
17:50:06 <mtreinish> mlavalle: yep, just jot down anything you think we should discuss at summit on that list
17:50:13 <mlavalle> :-)
17:51:19 <mtreinish> because we're going to have a day which is like a mini midcycle, so even if a topic doesn't get a dedicated session it might still be good for a smaller conversation then
17:52:18 <mtreinish> ok, well if there aren't any other topics to discuss I guess we'll end it early today
17:52:21 <mtreinish> thanks everyone
17:52:38 <mlavalle> bye!
17:52:41 <mtreinish> #endmeeting