22:01:42 <mtreinish> #startmeeting qa
22:01:42 <openstack> Meeting started Thu Apr 30 22:01:42 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:43 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:01:45 <openstack> The meeting name has been set to 'qa'
22:01:49 <mtreinish> hi who's here today
22:01:58 <masayukig> o/
22:01:59 <mtreinish> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_April_30th_2015_.282200_UTC.29
22:02:01 <dkranz> o/
22:02:01 <oomichi> hi
22:02:04 <mtreinish> ^^^ today's agenda
22:02:42 <mtreinish> jogo, dtroyer, sdague: around?
22:03:43 <mtreinish> well let's get started and maybe more people will trickle in later
22:03:51 <jogo> o/
22:03:58 <mtreinish> #topic Design summit planning
22:04:09 <mtreinish> so we've got a fair amount of topics listed on the etherpad:
22:04:14 <mtreinish> #link https://etherpad.openstack.org/p/liberty-qa-summit-topics
22:04:35 <mtreinish> I think we should probably start trying to work out which ones would be good for summit
22:04:55 <mtreinish> it doesn't look like too many people filled out interested this time on the etherpad
22:05:16 <mtreinish> I guess to start does anyone have a topic listed there that stands out as being one we definitely should have?
22:05:42 <dkranz> mtreinish: Tempest Scope Revisited
22:05:51 <mtreinish> dkranz: ok
22:06:01 <mtreinish> I was wondering if we should combine that with the qa in the big tent
22:06:05 <mtreinish> or leave it separate
22:06:34 <dkranz> mtreinish: I think we may run out of time if we combine but could combine into a double session
22:06:59 <Rockyg> ++
22:07:14 <mtreinish> dkranz: ok well I'll put them as back to back fishbowls then
22:07:26 * mtreinish hopes he can come up with enough etherpad notes for 2 sessions
22:07:26 <dkranz> mtreinish: ++
22:08:11 <oomichi> +1 for them and combining
22:08:28 <mtreinish> oomichi: combined as one session or 2?
22:08:44 <oomichi> for 2 :)
22:08:53 <mtreinish> oomichi: heh, ok :)
22:09:10 <mtreinish> well the next on the list is the grenade session
22:09:14 <mtreinish> which we don't need to have
22:09:15 <oomichi> they will be big/important topics
22:09:23 <mtreinish> because sdague already did it
22:09:49 <mtreinish> oh, although there is a note to have an explanatory session on using it
22:10:28 <mtreinish> are there any others that stand out to people?
22:10:44 <dtroyer> o/
22:11:09 <mtreinish> dtroyer: so your devstack session do you think a fishbowl or a workroom is a better fit?
22:11:13 <mtreinish> I'm leaning towards fishbowl
22:12:16 <dtroyer> I thnk so too, devstack seems to draw a crowd
22:12:34 <dtroyer> not a docker-size crowd, but more than the workrooms
22:13:19 <mtreinish> dtroyer: I dunno devstack is totally as hip as docker
22:14:50 <mtreinish> hmm, ok are there any other proposals people want to discuss? we don't have to decide everything today
22:16:17 <mtreinish> I'll also try to do some culling over the next week
22:16:28 <mtreinish> like I don't think we need a session on upgrading cirros versions
22:16:52 <sigmavirus24> "devstack seems to draw a crowd" well what do you expect from the most popular project used to deploy openstack
22:17:23 <mtreinish> sigmavirus24: heh, that's a good point :)
22:17:51 <mtreinish> ok, does anyone else have anything else to discuss on summit sessions?
22:18:18 <mtreinish> I'll try to come up with a draft schedule on my own if there isn't other feedback
22:18:20 <Rockyg> I would think you could combine some of the specific sessions on passwords, system program, etc into a "how do we move tempest tobe installable and runnable on any OpenStack cloud?
22:18:51 <mtreinish> Rockyg: that's actually conflating a couple different things
22:19:12 <mtreinish> the system program topic is about how tempest is designed to be run and end users interact with it
22:19:24 <mtreinish> it wouldn't really effect the mission to run against any cloud
22:19:29 <mtreinish> but I get what your going at
22:19:33 <Rockyg> Ah.  Thanks for the clarification
22:19:49 <mtreinish> combining sessions is a good idea
22:20:03 <Rockyg> Back in atlanta there was a session about making the "test server"  You have the library, so.....
22:20:20 <mtreinish> I was planning to do that where it made sense like for oomichi's tempest service client and the schema one from gmann
22:20:25 <mtreinish> that'll be one session
22:20:30 <mtreinish> and probably a work room
22:20:55 <Rockyg> cool
22:21:08 <mtreinish> Rockyg: well we decided not to do rest interface part of the server for the time being, because there are other things like jenkins to do that
22:21:20 <oomichi> yeah, maybe one work room/session is enough for them
22:21:41 <mtreinish> but subunit2sql was designed to fill the backend part of the proposal for that server topic back in atlanta
22:21:50 <mtreinish> oomichi: ok, I'll make that a work room
22:21:57 <Rockyg> and is being used by refstack
22:22:07 <Rockyg> And rally, I think
22:22:08 <oomichi> and will write the detail later
22:22:26 <mtreinish> oomichi: ok thanks
22:22:53 <mtreinish> Rockyg: subunit2sql? to my knowledge neither of those are using it
22:23:26 <Rockyg> Refstack is.  Or at least was.  I think it still does.
22:24:17 <mtreinish> ok, well is there anything else to discuss on summit sessions? oomichi, masayukig if we pick this up for next week's meeting I want to make sure your thoughts on this are represented
22:24:46 <Rockyg> Another possible session to consider:  How to generate scenario tests from Use Cases (telco, etc).  Define structure and process.
22:25:02 <mtreinish> Rockyg: I did a quick grep and didn't see anything. I think you might be confusing subunit and subunit2sql. But we can pick that up after the meeting
22:25:14 <Rockyg> yup
22:25:23 <oomichi> ok, I will write my name on the etherpad to represent my thinking
22:25:30 <mtreinish> oomichi: ok cool thanks
22:25:30 <masayukig> mtreinish: sure
22:25:33 <oomichi> mtreinish: thanks for considering
22:25:47 <mtreinish> Rockyg: that would probably be something to put on the sprint day list
22:25:55 <Rockyg> ++
22:26:13 <masayukig> mtreinish: I'll put my name on the pad of my thinking.
22:26:17 <mtreinish> masayukig: ok thanks
22:26:22 <Rockyg> Thanks for the considertion!
22:26:39 <mtreinish> then is everyone ok if we make next week's meeting the final decision date for picking topics?
22:28:03 <mtreinish> ok well if there isn't any objection I guess that's what we'll do :)
22:28:23 <mtreinish> #info next weeks meeting will finalize design summit topics for qa
22:28:28 <mtreinish> ok let's move on
22:28:36 <mtreinish> #topic Blueprints
22:28:44 <mtreinish> does anyone have any open bps they'd like to discuss
22:30:12 <mtreinish> heh, I'll take that as a no :)
22:30:26 <mtreinish> I guess I should mention that I pushed the tempest-4 tag yesterday
22:30:38 <mtreinish> not that it's really a bp, but this seems like a good a time as any
22:31:56 <mtreinish> ok, well lets move on then
22:32:03 <mtreinish> #topic Devstack
22:32:22 <mtreinish> dtroyer: anything new for devstack this week?
22:32:45 <dtroyer> I don't have much, been playing new kid at school this week,
22:33:00 <dtroyer> I see Sean C's dual-stack default change merged
22:33:10 <mtreinish> dtroyer: heh, long onboarding process?
22:33:21 <mtreinish> dtroyer: yeah that landed earlier this week, which is awesome
22:33:25 <mtreinish> sc68cal: ^^^
22:33:26 <dtroyer> delayed, apparently remote is hard
22:33:57 <dtroyer> I should be jumping back on the neutron rewrite next week, hoping to get the basic services running
22:34:22 <dtroyer> and then the platform for all of the layered plugins
22:34:51 <dtroyer> nothing else from me
22:35:01 <mtreinish> dtroyer: ok cool, that'll be good to have in place. How much longer after that is done do you expect to keep neutron-legacy around?
22:35:16 <mtreinish> is there a longer deprecation cycle because of grenade I guess is what I'm asking
22:35:51 <dtroyer> longer than I want.  grenade is part of it, but also just migrating all of those plugins either to the new bits or into external trees will take a while
22:36:18 <mtreinish> ah ok
22:37:00 <mtreinish> ok is there anything else on devstack?
22:38:03 <mtreinish> ok let's move on
22:38:09 <mtreinish> #topic Grenade
22:38:17 <mtreinish> jogo: anything on grenade this week?
22:39:36 <mtreinish> I guess not
22:39:55 <mtreinish> let's move on
22:39:59 <mtreinish> #topic Critical Reviews
22:40:16 <jogo> mtreinish: more of the sdague changes
22:40:23 <mtreinish> does anyone have any reviews they'd like to bring up
22:40:27 <mtreinish> jogo: perfect timing :)
22:40:38 <mtreinish> jogo: ah, yeah some of the post refactor cleanups
22:40:40 <jogo> I try
22:40:50 <dkranz> mtreinish: https://review.openstack.org/158198
22:40:59 <mtreinish> #link https://review.openstack.org/#/c/158198/
22:41:14 <dkranz> mtreinish: This is the trusts thing from jamie
22:41:55 <mtreinish> dkranz: yeah it looks like a good thing to fix as we move into a real v3 world
22:42:09 <dkranz> mtreinish: I don't quite get the trusts stuff enough to give +A
22:42:30 <dkranz> mtreinish: and the domain scoping details
22:42:53 <mtreinish> dkranz: heh, know one said the v3 world was simple :)
22:43:03 <dkranz> mtreinish: it's been sitting like that for two weeks
22:43:05 <mtreinish> I blame morganfainberg...
22:43:17 <mtreinish> dkranz: sure I'll review it after the meeting
22:43:22 <dkranz> mtreinish: we could ask morganfainberg to give it a proxy +2 :)
22:43:46 <dkranz> mtreinish: ok, if you are comfortable with that then great
22:43:47 <mtreinish> dkranz: oh, sure that's a good idea
22:43:51 <morganfainberg> let me finish with a phone call.
22:43:55 <morganfainberg> and i can look
22:44:00 <mtreinish> morganfainberg: heh, cool thanks
22:44:10 <mtreinish> #link https://review.openstack.org/#/c/174671/
22:44:17 <mtreinish> #link https://review.openstack.org/#/c/174473/
22:44:36 <mtreinish> #link https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:python3-support,n,z
22:44:39 <morganfainberg> for the record: I do tend to trust jamielennox's judgement on this stuff [if it needs to go in sooner]
22:45:01 <mtreinish> those should all be pretty straightforward reviews
22:45:13 <mtreinish> the python 3 branch will probably bit rot quickly
22:45:17 <dkranz> mtreinish: oh, sorry I did not get back to the second one which I said I was +2
22:45:24 <mtreinish> dkranz: oh no worries
22:45:40 <mtreinish> after all those patches land and the tempest-lib migration patches for tempest-lib 0.5.0 land
22:45:43 <dkranz> morganfainberg: It can wait for your review
22:45:49 <mtreinish> we're down to like 8 unit tests that don't pass on python3
22:45:58 <morganfainberg> ok will ping mtreinish or dkranz once i review
22:46:11 <dkranz> morganfainberg: thx
22:46:47 <mtreinish> ok are there any other reviews to bring up?
22:48:28 <mtreinish> ok then let's open the floor
22:48:31 <mtreinish> #topic Open Discussion
22:48:59 <mtreinish> dsoes any one have anything else to discuss this week?
22:49:40 <dkranz> mtreinish: I wanted to finish the chat about the filter ip list failure but we can do that in qa channel
22:49:49 <mtreinish> dkranz: ok sure
22:49:57 <mtreinish> well then I guess we can end here
22:50:01 <mtreinish> thanks everyone
22:50:05 <dkranz> bye
22:50:12 <oomichi> thanks
22:50:13 <masayukig> thanks
22:50:17 <mtreinish> #endmeeting