19:01:10 <dtroyer> #startmeeting OpenStackClient
19:01:11 <openstack> Meeting started Thu Oct 15 19:01:10 2015 UTC and is due to finish in 60 minutes.  The chair is dtroyer. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:01:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:01:15 <openstack> The meeting name has been set to 'openstackclient'
19:01:18 <dtroyer> who is here?
19:01:19 <stevemar_> \o/
19:01:30 <stevemar_> gotta send out the courtesy ping
19:01:47 <dtroyer> courtesy ping: briancurtin, terrylhowe, lhcheng, sigmavirus24, dstanek
19:01:54 <dtroyer> I can only c-n-p so fast...
19:02:00 <stevemar_> oh dstanek too now
19:02:02 <lhcheng> o/
19:02:10 <Megan_> o/
19:02:42 <dtroyer> Megan_: if you want to be added to that ping list, add yourself to the list on the meeting page at https://wiki.openstack.org/wiki/Meetings/OpenStackClient
19:02:59 <Megan_> thank you, I will
19:03:43 <stevemar_> whats on the agenda dtroyer?
19:04:05 <stevemar_> or we just winging it as usual :)
19:04:14 <dtroyer> Megan_: also, if no one else shows up it'll be up to you to break up the fights between stevemar_ and I over the ALCS that starts tomorrow night…
19:04:30 <dtroyer> stevemar_: winging it… you always try to slip in those references
19:04:37 <stevemar_> ha
19:04:45 <dtroyer> basically today, it's summit and release
19:04:55 <dtroyer> let's start with...
19:04:57 <stevemar_> wasn't even trying to do so
19:05:03 <dtroyer> #topic summit schedule
19:05:36 <stevemar_> #link https://mitakadesignsummit.sched.org/overview/type/openstackclient#.Vh_4-hNVhBc
19:05:38 <dtroyer> The OSC track is at https://mitakadesignsummit.sched.org/overview/type/openstackclient, still just the defaults that I'll fill in after the meeting
19:05:47 <stevemar_> :)
19:06:21 <dtroyer> working backwards, Friday's meetup is probably going to be filed with whatever comes up earlier in the week.
19:06:48 <stevemar_> makes sense
19:06:55 <dtroyer> The work session immediately follows the fishbowl session, but in a really small room IIRC
19:07:25 <stevemar_> is there anything that we really want to accomplish by working as a group?
19:07:32 <dtroyer> I imagine that may be session followup stuffs
19:08:00 <dtroyer> in YVR we did get some useful work out of sitting around and hashing out things like the argument precedence, etc.
19:08:29 <dtroyer> I think the command namespacing may be one of those this time?  or others?
19:08:29 <terrylhowe> could just do a bug bash or something
19:08:44 <dtroyer> terrylhowe: Hi!  that's also a great idea
19:09:04 <stevemar_> terrylhowe: for the work session?
19:09:07 <dtroyer> I started through the list today and…there are a bunch that would be easiest to talk about in a room i think
19:09:20 <dtroyer> maybe thats meetup stuff?
19:09:39 <dtroyer> I think it also depends on schedule.  stevemar_ do you have big conflicts?
19:09:45 <stevemar_> yeah, i think so, lets tackle bigger things during the work session
19:10:12 <stevemar_> dtroyer: pfft, probably
19:10:46 <stevemar_> keystone and osc meetups are conflicting :(
19:10:52 <stevemar_> i might jump in and out of rooms
19:11:00 <stevemar_> but i might be required to be in keystone
19:11:21 <stevemar_> osc work session conflicts with a talk i'm giving
19:11:34 <dtroyer> stevemar_ goes and wins an election just to get out of osc meetings
19:11:53 <stevemar_> and fishbowl conflicts with keystone fishbowl (policy)
19:11:56 <stevemar_> pretty much
19:12:27 <dtroyer> ok, I saw there were session overlaps, didn't know what topics yet
19:12:36 <stevemar_> i might have to bow out and meet up with you before or after this stuff, i don't think i can get out of these easily
19:12:55 <dtroyer> ok
19:13:35 * stevemar_ grumbles mightily
19:14:09 <dtroyer> so how about the topic list… I'll put what we've talked about into this etherpad now: https://etherpad.openstack.org/p/tokyo-osc-session
19:15:23 <stevemar_> thanks for the topic list, i'm adding now
19:17:04 <stevemar_> are the goals of ksa adoption == untangling the mess that is osc-occ-ksa
19:17:09 <dtroyer> so that's more than 45 minutes worth
19:17:13 <dtroyer> I don't think so
19:17:26 <dtroyer> I think ksa adoption can stand alone
19:17:39 <stevemar_> hmm okay
19:18:10 <stevemar_> i regret not asking for a x-project session about osc
19:18:18 <dtroyer> since occ insists on loading ksa plugins, we need to just bite it and do that too
19:18:58 <dtroyer> I want to push more of the arg handling down because of that
19:19:21 <stevemar_> whatcha mean?
19:19:37 <dtroyer> but staying backward-compatible is going to continue to be a problem since both ksa/ksc and occ have some bits that aren't for us
19:20:03 <dtroyer> I've contended that occ shouldn't be loading plugins or anything like that.  it should have been just a config file layer
19:20:23 <dtroyer> but I've lost that layering battle so let's make it the arg handling layer as much as possible
19:20:32 <dtroyer> the duplication is killing us because the oder is all wrong
19:20:38 <dtroyer> order*
19:21:08 <stevemar_> if we're going to be backwards compatible maybe it's finally time for a rename :D
19:21:32 <dtroyer> yeah, 2.0 is our chance to fix that
19:21:50 <dtroyer> I added https://review.openstack.org/233268 as the first step to doing things in the order we need
19:21:54 <dtroyer> to occ
19:22:03 <dtroyer> I'm guessing there will be more
19:22:49 <dtroyer> anyway, this also gets us headed down the rabbit hole of actually using ksa for auth everywhere (correctly), which isn't as simple as I thought
19:23:01 <dtroyer> so by then I should have the list of what needs to be done yet
19:23:32 <stevemar_> lemme see when the sdk guys have their sessions
19:23:40 <stevemar_> dtroyer: are you going to be in those?
19:23:51 <dtroyer> if I can
19:24:11 <dtroyer> I didn't think that was official yet, did they get space?
19:24:18 <stevemar_> they appear to not have sessions
19:24:24 <stevemar_> ^'
19:24:54 <dtroyer> and my talk on Tuesday was going to cover both osc and sdk, but the sdk bits will be much smaller than I had hoped
19:25:10 <dtroyer> we can't introduce it without a 1.0
19:25:41 <stevemar_> dtroyer: boourna
19:25:43 <stevemar_> boourns
19:26:03 <stevemar_> dtroyer: sdk integration seems so far away
19:26:35 <dtroyer> yeah, unfortunately
19:27:02 <dtroyer> so for #1, is there design/impleemntation questions or is it just a SMOP
19:27:07 <dtroyer> (small matter of programming)
19:27:28 <terrylhowe> there was no space for sdk sessions, so we were going to wing it
19:27:40 <terrylhowe> piggy back on osc sessions if possible
19:27:52 <stevemar_> dtroyer: it's not "small", but there aren't any contentious issues there
19:28:01 <dtroyer> I didn' tthink so
19:28:16 <dtroyer> terrylhowe: Friday morning is probably the best time for doubling up
19:28:17 <stevemar_> write a token to cache, local disk, blah
19:28:38 <stevemar_> dtroyer: jamie had some code in ksc for handling stuff there
19:28:41 <terrylhowe> cool
19:28:59 <dtroyer> #2 and #5 are related
19:29:17 <dtroyer> #3 and #4 are project relations more than technical IMO
19:29:40 <dtroyer> #9 is the one that's gotten a lot of noice in the last month or two
19:29:43 <dtroyer> yay plugins!
19:30:25 <stevemar_> #3 and #4 can be done by asking the PTLs
19:31:02 <dtroyer> right
19:31:36 <stevemar_> why does neutron depend on sdk integration?
19:32:19 <dtroyer> that's how we're going to get it.  I _REALLY_ don't want more neutronclient stuffs so we can remove the dependency
19:32:28 <dtroyer> that's also why replacing glacneclient is second on my list
19:33:10 <dtroyer> terrylhowe seems to have the network bits fleshed out in the SDK
19:33:27 <dtroyer> that's the first pain point of delaying adoption
19:34:16 <dtroyer> anything else about the summit?
19:34:26 <stevemar_> sec...
19:34:29 <terrylhowe> I’d be a lot further along right now, but I got pulled off on an internal project, hence I’ve been afk for the couple weeks kind of
19:34:45 <dtroyer> terrylhowe: I know how that feels…
19:35:03 <stevemar_> you guys and your internal projects
19:35:31 <stevemar_> should be carry some neutron sdk/api stuff in OSC, like we do with swift?
19:35:35 <dtroyer> remember, this was an evenings-only project for me for 2 years.  I feel fricking free now…
19:35:48 <stevemar_> enough to perform some basic operations
19:35:53 <dtroyer> stevemar_: maybe
19:36:22 <stevemar_> i think it's worth it
19:36:26 <dtroyer> part of the KSA work I started is working up that api.* chain updating the sessions so that should be ready
19:37:03 <stevemar_> the reaction that OSC has barely any network support isn't good :(
19:37:30 <dtroyer> unfortunately thatls not a one-item list either
19:38:38 <stevemar_> understood
19:38:46 <dtroyer> if the api.* stuff stays, we need to consider it to be an interface that can be used by plugins
19:39:10 <stevemar_> but i would think, like most things, most folks want a few basic network commands, not the whole shebang
19:39:33 <dtroyer> right.  we maybe should start with the typical user commands
19:39:33 <stevemar_> enough so that they can use osc as their main cli, and not swap all the time
19:39:54 <dtroyer> thinking users, not admin/ops
19:39:59 <terrylhowe> unfortunately there is a fairly large set of commands needed to stand up a network
19:40:16 <stevemar_> 10% of the stuff is run 90% of the time :P
19:40:17 <terrylhowe> but maybe we could minize it by only providing list adn create to start
19:40:25 <dtroyer> for aproject though, that's usualy only done once? or by a small number of people?
19:40:29 <terrylhowe> at best stevemar_
19:41:01 <stevemar_> i think carrying that support, until the sdk is baked is fair
19:42:15 <stevemar_> anywho
19:42:22 <stevemar_> release talk time?
19:42:29 <dtroyer> hows about we move on to…
19:42:35 <dtroyer> #topic next release
19:42:59 <dtroyer> anticipating a 1.8.0 release on Monday, is there anything outstanding you think we should wait on yet?
19:43:11 <dtroyer> there are a few that I'd like to hold off until after 1.8.0 is cut
19:43:20 <stevemar_> what's your list?
19:43:54 <dtroyer> the first KSA review: https://review.openstack.org/233344
19:44:19 <dtroyer> compute service delete: https://review.openstack.org/231812
19:44:23 <dtroyer> that's it
19:45:17 <dtroyer> maybe identity v3 default?   that just makes me nervous…timing wise at least
19:45:31 <dtroyer> is it better to break during hte summit or after? ;)
19:45:49 <stevemar_> dtroyer: meh, either way is fine
19:45:58 <stevemar_> we're just starting M, so the really bad part is over
19:46:11 <stevemar_> during the summit, not too many patches going through :)
19:46:40 <dtroyer> actually it's seemed sometimes things happen/get fixed faster when we're together
19:46:42 <stevemar_> compute service delete can go in
19:47:00 <dtroyer> I want that to work like compute set service before it goes into a release
19:47:17 <dtroyer> one uses service/host, the other uses ID only
19:47:24 <stevemar_> ah
19:47:31 <stevemar_> this maybe: https://review.openstack.org/#/c/211839/
19:48:07 <stevemar_> dtroyer: up to you if you want the first ksa review in there, it adds a requirement but doesn't do anything
19:48:12 <dtroyer> I'm not sure I ever looked at it, first because August, then the Jenkins -1
19:48:35 <dtroyer> I don't want to add the requirement just yet, that's why the wait in ksa
19:48:42 <stevemar_> dtroyer: i fixed it up, guess i forgot to pep8 it
19:48:48 <stevemar_> yeah, wait on ksa then
19:49:28 <dtroyer> I'll look at the volume list filter after the meeting, it'll probably be ok to go in
19:50:00 <dtroyer> so my plan is to do the 1.8.0 release notes tomorrow and merge them, but waituntil Monday to cut the relase, because weekend
19:50:15 <dtroyer> that will let us resume merging the other stuffs
19:50:43 <dtroyer> I don't think that breaks any testing paths
19:51:13 <stevemar_> dtroyer: fixed up the volume one
19:51:22 <dtroyer> cool, thanks
19:51:29 <stevemar_> dtroyer: cool with me
19:51:35 <stevemar_> let me know if you need a review or two
19:51:51 <dtroyer> will do.
19:52:07 <dtroyer> I think I have launchpad cleaned to now too.
19:52:14 <stevemar_> dtroyer: saw that
19:52:16 <stevemar_> nice job
19:52:24 <dtroyer> have the release team been making the milestones and targeting bugs or did you do that stevemar_?
19:52:39 <stevemar_> dtroyer: release team
19:52:49 <stevemar_> i just propose a new change to openstack/releases
19:52:52 <stevemar_> and magic happens
19:53:15 <dtroyer> hmmm…ok, I'll check with dhellmann then if I did it right.  so far I've medded up both releases I've tried under the new process
19:53:17 <stevemar_> i think it scans bugs in LP that are fix committed and sets them to release
19:53:29 <dtroyer> I wanted a place to target the committed bugs to extract them for the release notes
19:53:56 <stevemar_> dtroyer: i think doing less might be better in this case
19:54:16 <stevemar_> just find the fix-committed bugs and make your release notes from that, don't change the state though
19:54:41 <dtroyer> except that it pulls based on milestone
19:55:09 <dtroyer> I did kinda like the ability to track via the milestones.
19:55:26 <dtroyer> especially now that we'll have stable release bugs mixed in
19:55:39 <dtroyer> will ask the gurus for guidance
19:55:55 <dtroyer> anything else on reviews/bugs for release?
19:56:41 <stevemar_> nope
19:56:51 <dtroyer> #topic open discussion
19:57:01 <stevemar_> go jays go!
19:57:05 <dtroyer> we've got 5 minutes left, what's on y'alls minds?
19:57:15 <dtroyer> go Royals go!
19:57:27 <dtroyer> Cueto proved he can still pitch at least one good game a year
19:57:43 <stevemar_> we need briancurtin in here for a `go cubs go`
19:58:11 <stevemar_> hopefully ventura doesn't bean 3 of our players again
19:58:12 <dtroyer> ah, good, I was afraid he might be a TX baseball fan drowning sorros now
19:58:42 <stevemar_> TX has baseball fans?
19:58:46 <stevemar_> :P
19:58:48 <dtroyer> Early season grips never go away ;)
19:58:54 <dtroyer> they have 2
19:59:01 <dtroyer> one for each team
19:59:01 <stevemar_> 2 fans
19:59:03 <stevemar_> hehe
19:59:05 <diazjf> stevemar_ Astros "had" a good season
19:59:25 <stevemar_> diazjf: until last night :(
19:59:40 <stevemar_> i was hoping they would win, royals make me nervous
19:59:45 <stevemar_> anywho
19:59:48 <dtroyer> as well they should
19:59:51 <stevemar_> good use of open discussion :)
20:00:03 <dtroyer> ok, let's call it a meeting then
20:00:14 * dtroyer testing the 'open' in open discussion
20:00:18 <dtroyer> #endmeeting