17:02:33 <mtreinish> #startmeeting qa
17:02:34 <openstack> Meeting started Thu Jan 21 17:02:33 2016 UTC and is due to finish in 60 minutes.  The chair is mtreinish. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:02:35 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:02:37 <openstack> The meeting name has been set to 'qa'
17:02:46 <jordanP> hi
17:02:51 <mtreinish> hi who's here today?
17:02:53 <jordanP> I'll be a bit afk today
17:02:57 <dwalleck> o/
17:03:00 <slowrie> .
17:03:14 <mtreinish> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_January_21st_2016_.281700_UTC.29
17:03:17 <mtreinish> ^^^ today's agenda
17:03:21 <cdent> o/
17:04:11 <mtreinish> ok, lets get started
17:04:22 <mtreinish> #topic QA Code Sprint
17:04:30 <mtreinish> #link https://wiki.openstack.org/wiki/QA/CodeSprintMitakaBoston
17:04:43 <mtreinish> this is just a reminder about the code sprint next month
17:05:00 <mtreinish> if you plan to attend be sure to put your name on the registration table at the bottom of the wiki
17:05:35 <mtreinish> that's all I had on this topic, is there anything else on it?
17:06:32 <mtreinish> ok, then lets move on
17:06:42 <mtreinish> #topic Specs Reviews
17:06:49 <mtreinish> #link https://review.openstack.org/#/q/status:open+project:openstack/qa-specs,n,z
17:07:00 <mtreinish> does anyone have any open spec reviews they'd like to discuss?
17:07:21 <dwalleck> I do. I put up the tempest run spec earlier this week - https://review.openstack.org/#/c/269934/
17:07:42 <dwalleck> I'd appreciate any comments or feedback. This is all based on what we talked about in Tokyo
17:07:55 <mtreinish> #link https://review.openstack.org/#/c/269934/
17:08:22 <jlanoux> o/
17:09:07 <mtreinish> yeah, I need to take a look at that
17:09:43 <dwalleck> Also, if there's any higher priority stuff that needs to be done, let me know. I've got a lot of open bandwidth
17:09:59 <jordanP> yeah, I haven"t read that spec either :(
17:11:22 <mtreinish> ok, are there any other specs to discuss?
17:11:45 <slowrie> mtreinish: I updated the centralized workspaces (https://review.openstack.org/#/c/266094/2) based on your comments in the first patch set
17:11:58 <mtreinish> #link https://review.openstack.org/#/c/266094/2
17:12:43 <mtreinish> ok, I'll have to swing back to that one too
17:14:40 <mtreinish> ok, lets move on
17:14:52 <mtreinish> #topic Priority Items
17:14:59 <mtreinish> #link https://etherpad.openstack.org/p/mitaka-qa-priorities
17:15:10 <mtreinish> so this week is m-2
17:15:19 <mtreinish> and there were a couple of m-2 targetted items on the list
17:15:58 <mtreinish> starting from the top, sc68cal and the neutron devstack rewrite (or at least part of it)...
17:16:41 <mtreinish> there's also the service client migrations which oomichi has his name next to
17:16:52 <mtreinish> which I think is making progress but isn't quite done yet
17:17:01 <mtreinish> I'll follow up with him about that later
17:17:12 <mtreinish> next on the list is jordanP and the tempest-lib migrations
17:17:18 <mtreinish> jordanP: any update on that?
17:17:37 <jordanP> yeah, not really, quite frankly I have very little time now
17:17:52 <mtreinish> ok, no worries
17:18:07 <jordanP> if someone would want to take over this item
17:18:13 <jordanP> that would be fine with me
17:18:19 <jordanP> not the most sexy work though
17:18:33 <mtreinish> ok, I'll make a note on the etherpad, and see if someone else will take it over
17:18:44 <jordanP> ok
17:18:53 <dwalleck> jordanP: I might be able to help you out there. Can I ping you later?
17:19:10 <jordanP> it will be late now here, but tomorrow for sure
17:19:16 <jlanoux> I'm on the ss validation one but I don't think it will make m-2
17:19:22 <jlanoux> *ssh
17:19:30 <mtreinish> the last m2 targetted item is Finalize ssh-auth bp (andreaf, jlanoux)
17:19:33 <jordanP> yep, that's in the review list
17:19:43 <jordanP> Consolidate SSH code (jordanP): https://review.openstack.org/#/c/264323/
17:19:52 <jordanP> no
17:19:53 <mtreinish> #link https://review.openstack.org/#/c/264323/
17:19:54 <jordanP> my bad
17:19:58 <jlanoux> mtreinish: I have a couple of patch that needs to go in
17:19:58 <jordanP> wrong review :(
17:20:04 <mtreinish> heh, ok
17:20:08 <mtreinish> #undo
17:20:09 <openstack> Removing item from minutes: <ircmeeting.items.Link object at 0x97bfbd0>
17:20:24 <mtreinish> jordanP: do you have a link?
17:20:25 <jlanoux> actually this is one of them
17:20:37 <mtreinish> s/jordanP/jlanoux
17:20:52 <jlanoux> #link https://review.openstack.org/#/c/264323/
17:21:00 <jlanoux> #link https://review.openstack.org/#/c/259515/
17:21:47 <jlanoux> When those 2 are in, I think we can close the ssh-blueprint, if andreaf is ok
17:22:02 <jlanoux> And I can migrate compute and remote_client in tempest_lib
17:22:12 <mtreinish> ok, I'll take a look
17:22:41 <jlanoux> thanks
17:22:44 <jordanP> I have a comment on patchset 6 for the file remote_client.py
17:22:51 <jordanP> on 264323
17:23:23 <jordanP> my point is, should the remote client, given it is passed a "server" argument
17:23:36 <jordanP> should inspect that server argument to detect and connect to a floating ip
17:23:45 <jordanP> ?
17:24:05 <jordanP> or, do we want  to have an extra argument named "floatingip" for that RemoteClient ?
17:24:13 <mtreinish> jordanP: I think we should just look at the server object
17:24:17 <jordanP> me too
17:24:17 <mtreinish> it's all in there anyway
17:24:28 <jlanoux> I don't think we should
17:24:48 <mtreinish> also I think nova has an api for specifying the ip to use on a server. accessIP or soemthing like that
17:24:49 <jordanP> the thing is, on some super rare cases not exerciced in Tempest,  a server could have 2 floating IP (because it has 2 NICs)
17:24:55 <jlanoux> discovery will be a complex mechanism to implement and it doesn't bring anyting
17:25:21 <jordanP> it's super easy, we are already iterating on the ADDRESSES attribute of the server, to detect its fixed ip
17:25:33 <dwalleck> mtreinish: The AccessIPv* is just a copy of the public (if you have a public network) IP adress
17:25:34 <jordanP> just do the same for the FIP
17:25:37 <jlanoux> on a customer point of view, this is not realistic
17:25:47 <jlanoux> jordanP: if you have multiple FIP, it is not
17:25:58 <mtreinish> dwalleck: right, but it tells the user which IP to use
17:26:30 <mtreinish> which is the problem here
17:26:42 <jordanP> jlanoux,  yeah but then in that case we can read the conf.network_for_ssh
17:26:47 <dwalleck> To me the question from a separation of concerns standpoint is if the remote client should be making that decision. It really feels like something outside the remote client should decide that
17:26:59 <jordanP> jlanoux, ok, you are the owner of that patch anyway, if you don"t feel like it, I am fine
17:27:13 <jordanP> the current code does not do inspection, so no change required
17:27:31 <jordanP> I think it would be nice, but not mandatory for that patch to go in
17:28:02 <jlanoux> jordanP: ok
17:28:17 <mtreinish> dwalleck: there are too many layers right now, I don't think it's so clear cut
17:28:40 <jlanoux> I don't see the point for a discovery of any IP. As a user I create an IP and I want to use it.
17:29:27 <dwalleck> mtreinish: That's very true. It would be nice to re-design the process from scratch with a design in mind, but I don't know if there's an appetite for that
17:29:39 <jlanoux> I'm thinking of extending the scope of the remote_client, perhaps let it deal with ssh resources
17:30:12 <jlanoux> so the creating and association happens in the remote and we don't need to pass 10000 arguments
17:31:39 <jordanP> jlanoux, later maybe
17:31:45 <jordanP> enough layer for now :)
17:31:54 <mtreinish> heh
17:32:05 <jlanoux> jordanP: of course - but it will remove layers :)
17:32:12 <mtreinish> ok, is there anything else on mitaka priorities?
17:32:23 <mtreinish> oh ttx had an openstack-health m2 goal
17:32:39 <mtreinish> but that was half a joke
17:33:50 <mtreinish> #topic Tempest
17:34:18 <mtreinish> so there are quite links on the agenda for tempest
17:34:26 <mtreinish> jordanP: want to tackle yours first
17:35:21 <jordanP> yep
17:35:37 <jordanP> so https://review.openstack.org/#/c/259859 was +A now
17:35:43 <jordanP> so it's not relevant to discuss anymore
17:35:59 <mtreinish> ok
17:36:05 <jordanP> and Consolidate SSH code (jordanP): https://review.openstack.org/#/c/264323/
17:36:17 * andreaf sneaks in
17:36:30 <mtreinish> heh, didn't we just discuss that one :)
17:36:35 <jordanP> after discussion with jlanoux right now, he doesn"t want to do discovery of the floating IP
17:36:43 <jordanP> yeah, exactly
17:36:50 <jordanP> so I am good now :)
17:37:01 <jordanP> I will +2 that patch
17:37:16 <mtreinish> ok, that was easy :)
17:37:21 <jlanoux> thanks jordanP :)
17:37:31 <mtreinish> the other link on the agenda was:
17:37:33 <mtreinish> #link https://review.openstack.org/#/c/255161/
17:37:45 <mtreinish> I don't know who added that one though
17:38:05 <jordanP> someone from Japan
17:38:11 <jordanP> i added it to the wiki
17:38:16 <jordanP> but the patch is from someone in japan
17:38:33 <jordanP> so that patch seems related to tempest plugin obviously
17:38:51 <jordanP> it could conflict with what andreaf is doing
17:39:36 <jordanP> as far as I understand the 2-line patch, it should help people writting plugin, so that they could use their custom clientsManager
17:39:54 <mtreinish> well, I don't know if it conflicts with that. I don't see the harm with it
17:40:19 <mtreinish> yeah, it just lets a subclass override the clientManager class a bit more easily
17:40:51 <mtreinish> I mean I don't like encouraging using tempest internals externally, but I don't think we need to go out of way to make it hard
17:40:58 <mtreinish> especially since tempest-lib isnt all there yet
17:40:58 <andreaf> jordanP, mtreinish: ok - well it doesn't help removing the dependency from tempest
17:41:24 <andreaf> jordanP, mtreinish: but I'm not specifically against it either
17:42:22 <mtreinish> ok, is there anything else on tempest for this week?
17:43:11 <jordanP> not from me
17:43:28 <mtreinish> ok, then let's move on
17:43:32 <mtreinish> #topic DevStack + Grenade
17:43:42 <mtreinish> does anyone have anything to discuss on devstack or grenade this week?
17:45:40 <mtreinish> ok, I guess not
17:45:44 <mtreinish> let's move on then
17:45:58 <mtreinish> #topic Critical Reviews
17:46:07 <mtreinish> Does anyone have any reviews they'd like to get extra eyes on?
17:47:39 <mtreinish> really, no reviews this week? :)
17:48:00 <jlanoux> :) I gave mine earlier
17:48:58 <mtreinish> ok, if there aren't any reviews I'll guess we'll open the floor
17:49:02 <mtreinish> #topic Open Discussion
17:49:16 <mtreinish> does anyone have anything else they'd like to discuss
17:49:21 <mtreinish> now is the change to bring it up
17:49:27 <mtreinish> s/change/chance
17:52:31 <mtreinish> ok, if there isn't anything else to discuss today, I guess we'll end here
17:52:34 <mtreinish> thanks everyone
17:52:37 <mtreinish> #endmeeting