22:00:59 #startmeeting qa 22:01:00 Meeting started Thu Jun 25 22:00:59 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:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 22:01:03 The meeting name has been set to 'qa' 22:01:13 hi, who's here today? 22:01:22 hi 22:01:38 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_June_25th_2015_.282200_UTC.29 22:01:43 ^^^ today's agenda 22:02:35 jogo, dtroyer, oomichi, masayukig: around? 22:03:04 gmann: heh, it might be just us today 22:03:20 masayukig: he was working late night in office so he would not be able to join 22:03:24 heh 22:03:50 well, I guess that's a good segway into the first topic 22:04:01 dkranz: on vacation ? 22:04:04 #topic Moving 2200 UTC meeting time a little later (mtreinish) 22:04:05 gmann: yep 22:04:38 so this is something we've discussed informally before, but I wanted to get it on the agenda before I took it to the ML 22:04:50 which is attendance for the 2200 UTC meeting is light 22:05:08 it's too early for a lot of APAC 22:05:16 so I'll start a ML poll and find a better time 22:05:18 yea 22:05:30 mtreinish: sort of 22:05:33 ++ 22:05:58 mtreinish: +++ :) 22:06:37 #action mtreinish to start a ML poll to find a better time for the 2200UTC meeting 22:06:50 ok, well that settles this topic 22:07:06 o/ 22:07:15 let's move on 22:07:25 #topic Specs Reviews 22:08:04 does anyone have an open spec review they'd like to bring up? 22:08:27 #link https://review.openstack.org/184992 22:08:35 I wanted to bring that one up again 22:08:57 someone else needs to +A that, so we can get started on it 22:09:09 it depends on some of the CLI stuff being implemented 22:09:16 mtreinish: i have just one concern about admin writable resources tests in more than one places 22:09:25 I'll bug dpaterson about that tomorrow 22:09:34 after that m +A 22:10:06 gmann: so honestly I'm not sure how much of a concern that really is because we can't control what plugins are doing 22:10:09 because tempest tests + plugin tests will be running on same env and can bring conflict issue 22:10:44 that's kinda of the point. If the plugins are doing something wrong (like not protecting against global scope resources) that's a bug in the plugin 22:11:28 mtreinish: yea, that will kinda bug but i agree we can control that manually if anyone does 22:11:47 we're just using oslo.concurrency for locking so they can leverage that too. (although we probably can move the tempest specific fixture which just sets a name to the lib or something) 22:13:32 ok, is there anything else on specs? 22:13:38 can we document that somewhere? for plugin writer benefit 22:14:13 gmann: yeah, I plan to have a detailed doc in tempest on the plugin interface and writing plugins once the interface works 22:14:14 gmann: ++ a guidelines section or devref for that? 22:14:20 that make sense to me for using locking there if they want 22:14:43 I didn't think that made sense to do before we've even started working on the interface 22:15:01 mtreinish: ++ ;-) 22:15:10 mtreinish: Thanks. m will review that spec. mostly lGTM 22:15:20 gmann: ok, cool thanks 22:15:28 * afazekas checking the plugin loading costs.. 22:15:33 mtreinish: +1 after working condition we can write doc 22:15:51 afazekas: man you're online late :) 22:16:00 :) 22:16:20 afazekas: yeah I'm not sure what the overhead is for stevedore loading, but I think it'll be pretty minimal compared to everything else 22:16:20 mtreinish: It's meeting time :) 22:17:01 mtreinish: If it means all python package scan.. 22:18:54 afazekas: I'm pretty sure it uses pkg_resources to do an entry point list 22:20:13 which anyway let's move on, since I don't think there are any other specs to discuss 22:20:19 #topic Blueprints 22:20:28 does anyone have an open bp to discuss? 22:20:33 or give a status update on 22:22:34 ok I guess not :) 22:22:37 let's move on then 22:22:41 #topic Devstack 22:22:51 dtroyer: anything exciting in devstack land? 22:23:14 although, like me, you're just coming back 22:23:17 so maybe not 22:23:28 I've been out for a while, but most exciting I've seen is sc68cal getting more neutron bits working 22:23:59 also, I may have some folk to pick up the neutron re-write… film at eleven 22:24:42 heh, ok 22:25:04 yeah getting the linux bridge stuff will be cool 22:25:19 lastly, there is cleaning up some of the WSGI service implementation going on, keystone merged, I'm working on some Nova bits now 22:25:20 dtroyer: and I think everyone is looking forward to you rewriting neutron 22:26:20 dtroyer: is this to have a common way of registering wsgi services? 22:26:47 it changes where the files are loaded from (removed a copy) and makes the apache template files more common 22:26:57 ah, ok 22:27:50 ok, is there anything else on devstack? 22:27:59 not from me 22:29:31 ok, then let's move on 22:29:35 #topic Grenade 22:29:44 jogo, dtroyer: anything new for grenade this week? 22:29:58 jogo: I know you've been looking at the work required for multi-node grenade right? 22:30:17 mtreinish: mordred broke it 22:30:33 jogo: heh, good to know 22:30:41 new jobs are set up to run tempest-smoke for nova-net and neutron 22:30:55 to see how viable multinode grenade will be 22:31:01 I think keeping mordred away from grenades is probably good for everyone 22:31:04 and sdague said he will own those jobs 22:31:27 mordred broke setting of the hostname so both nodes have the same name and nova had a seizure 22:31:40 oh, that explains the really bizarre errors 22:31:46 yeah 22:32:25 and I will not be here for next weeks meeting ... or any more 22:32:44 jogo: tsk tsk 22:32:53 -1 22:33:20 jogo: what will you do if https://review.openstack.org/194774 actually lands? 22:33:35 mtreinish: we will see ;) 22:33:50 oh wait today was the spec freeze right? 22:33:57 I guess dansmith will have to put in an exception 22:34:16 ok, is there anything else on grenade? 22:35:05 it can use a new core 22:35:32 yes, I've been thinking about that ever since you told me you're leaving 22:36:07 we'll come up with something 22:36:32 which might be to just set up robo calls to spam your phone to do reviews 22:36:46 * jogo will be on IRC still 22:37:18 jogo: +1. just wanted to ask about your presence on IRC 22:38:21 ok, let's move on 22:38:34 #topic Bugs 22:38:41 #link https://etherpad.openstack.org/p/Tempest-bug-report 22:38:41 jogo: fix is up for that btw 22:38:55 greghaynes: thanks! 22:39:04 gmann: anything to report on bugs for this week? 22:39:23 nothing special, did triaged this week. 22:39:51 anything stand out during that? 22:40:07 cleaned up bugs got to new state due to abandon patches but most of them were fixed by other patches 22:40:37 mtreinish: regarding https://bugs.launchpad.net/tempest/+bug/1370086 22:40:38 Launchpad bug 1370086 in tempest "Tempest ignores its custom virtualenv location" [Low,Confirmed] - Assigned to Ghanshyam Mann (ghanshyammann) 22:41:11 mtreinish: it just need sync from oslo.incubator right or we keep tempest version of those scripts? 22:41:47 gmann: those are oslo synced iirc 22:43:17 mtreinish: i saw Temp st has old version than oslo 22:45:13 ok, then we probably just need to sync 22:45:13 mtreinish: ok thanks. I will put that today 22:45:13 mtreinish: probablye this first (https://review.openstack.org/#/c/189127/) before you sync 22:45:13 dims_: heh, good call :) 22:45:13 dims_: well except that removes the install venv bit we were talking about 22:45:13 mtreinish: ok, then i'll abandon this one 22:45:13 from because the tempest version doesn't quite work 22:45:14 gotcha 22:45:34 ok is there anything else on bugs? 22:45:50 nothing else from me 22:46:14 ok, then let's move on 22:46:18 #topic Critical Reviews 22:46:28 Does anyone have any reviews they'd like to get extra eyes on? 22:47:24 mtreinish: neutron client refactor are up 22:47:32 #link https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:refactor_neutron_client,n,z 22:47:50 gmann: oh, cool I'll take a look 22:47:58 that should be easy to review 22:48:01 mtreinish: Thanks 22:48:37 gmann: oh, you know the next step after that is to split each resource type up into it's own module 22:48:57 mtreinish: yes 22:49:20 mtreinish: actually current refactor patches will conflict with https://review.openstack.org/#/c/186559/ 22:49:49 mtreinish: m ok to land that first if you want and then ll do rebase the refactor patches 22:49:51 gmann: well dougwig wants to wait a bit longer on that, so he'll have to rebase 22:49:57 it's just a delete so it'll rebase cleanly 22:49:59 mtreinish: ok 22:50:21 mtreinish: Thanks 22:50:34 ok, are there any other reviews? 22:52:32 ok, then let's open the floor 22:52:36 #topic Open Discussion 22:52:50 does anyone have a topic they'd like to discuss that wasn't on the agenda? 22:53:45 ok, then I guess let's end here today 22:53:48 thanks everyone 22:53:54 Thansk all 22:53:56 #endmeeting