21:01:02 <notmyname> #startmeeting swift
21:01:03 <openstack> Meeting started Wed May  3 21:01:02 2017 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:01:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:01:07 <openstack> The meeting name has been set to 'swift'
21:01:08 <notmyname> who's here for the swift team meeting?
21:01:09 <timburke> o/
21:01:12 <mattoliverau> o/
21:01:13 <m_kazuhiro> o/
21:01:13 <jrichli> o/
21:01:17 <patchbot> hi
21:01:18 <rledisez> hi o/
21:01:30 <pdardeau> hi
21:01:33 <tdasilva> hello
21:01:38 <kota_> hello
21:01:42 <mathiasb> o/
21:02:08 <notmyname> clayg: cschwede_: acoles: ping
21:02:24 <acoles> hello
21:02:27 <clayg> lets do it
21:02:36 <notmyname> welcome everyone
21:02:56 <notmyname> relatively short agenda for this week (although I left off one topic)
21:02:58 <notmyname> #link https://wiki.openstack.org/wiki/Meetings/Swift
21:03:10 <notmyname> since the last meeting...
21:03:17 <notmyname> Swift 2.14.0 has been released. done!
21:03:24 <joeljwright> oops, missed the start, sorry
21:03:43 <notmyname> joeljwright: just in time :-)
21:03:51 <notmyname> #topic follow up from last week
21:03:58 <mattoliverau> \o/
21:04:04 <notmyname> last week we talked about https://review.openstack.org/#/c/456205
21:04:04 <patchbot> patch 456205 - python-swiftclient - WIP: Use keystone session when possible
21:04:16 <notmyname> and joeljwright said he'd write something up and put it on the ideas page
21:04:20 <joeljwright> https://wiki.openstack.org/wiki/Swift/ideas/swiftclient-keystone-session
21:04:22 <notmyname> joeljwright: did you get a chance to do that?
21:04:26 <notmyname> nice!
21:04:39 <joeljwright> some background information and links to related patches
21:04:45 <notmyname> thank you
21:04:58 <joeljwright> np
21:05:35 <jungleboyj> o/
21:05:40 <notmyname> joeljwright: looks like a decent write up that we can use for pointing people at when this comes up in the future
21:06:00 <notmyname> and for working through on this patch (for this patch author) and other current work
21:06:10 <joeljwright> thanks to jaosorior for the WIP and taking the time to talk to me and they keystone peeps
21:06:29 <acoles> joeljwright: nice writeup, thanks
21:07:00 <joeljwright> the patch really is just a pointer in the right direction, but the background is largely from conversations with timburke and jaosorior
21:07:02 <clayg> *through* the Keystone session!?
21:07:29 <joeljwright> clayg: yeah, but timburke already make a plugin for v1auth…
21:07:35 <notmyname> clayg: yeah, the keystone session handles reauth etc. I expect some complexity when we do "keystone or other auth systems"
21:07:52 <notmyname> joeljwright: oh! so maybe the keystone v1 plugin works for other auth systems too?
21:08:00 <notmyname> the call signatures should be the same
21:08:22 <joeljwright> the session would need to be instantiated by specifying the plugin to use… but… maybe...
21:08:25 <joeljwright> timburke?
21:08:30 <notmyname> guess it depends on what we can plumb through that might be different (endpoints, catalogs or not, etc)
21:08:33 <timburke> i fully expect the v1 auth plugin to work against swauth
21:08:44 <notmyname> point is... a lot of work left to be done
21:08:49 <joeljwright> yes
21:09:03 <joeljwright> and probably a breaking API change unless we're really clever
21:09:30 <notmyname> definitely something to keep in mind
21:09:32 <mordred> notmyname: just eavesdropping/crashing the meeting - but I'd be happy to help figure out keystoneauth/swauth things
21:09:58 <notmyname> mordred: ok. thanks. the link above from joeljwright is a great place to start with a summary of the state of things
21:10:02 <timburke> we *might* be able to avoid some of that if we also pull in the token_endpoint plugin?
21:11:00 <mordred> notmyname: yah - was just reading through that - looking good - I'll try to get up to speed on state and see if I can be of any assistance
21:11:09 <notmyname> mordred: thank you
21:11:21 <joeljwright> mordred: thanks
21:11:57 <notmyname> next topic
21:12:03 <notmyname> #topic openstack summit in boston
21:12:13 <notmyname> this is the one I left off the agenda by accident
21:12:21 <notmyname> (of course we'll talk about the summit. it's next week)
21:12:29 <notmyname> schedule updates from last week
21:12:45 <notmyname> last week I said it looked like we had a really good block of time on tuesday
21:13:07 <notmyname> however, that is no longer true
21:13:19 <notmyname> if you look at tuesday's schedule...
21:13:21 <notmyname> #link https://www.openstack.org/summit/boston-2017/summit-schedule/#day=2017-05-09
21:13:32 <notmyname> ...you'll see that we have 3 Forum sessions
21:13:51 <notmyname> from 2pm to 5:20pm
21:14:35 <notmyname> because of this severely constrained schedule, I've blocked some time on the "hacking rooms" schedule
21:14:36 <notmyname> #link
21:14:39 <notmyname> #link https://ethercalc.openstack.org/Boston_Forum_Hacking_Rooms
21:14:50 <notmyname> I've blocked out wednesday from 10:30 to 12:30
21:14:54 <mattoliverau> oh nice work on the hacking rooms
21:15:07 <notmyname> this is the largest single block of time that conflicts the least with other stuff on the general schedule
21:15:44 <notmyname> so in total, we've got about 5 hours of time together in a room scheduled to talk about swift things
21:16:15 <mattoliverau> great
21:16:19 <kota_> nice
21:16:31 <notmyname> we'll stick close-ish to the published schedule for tuesday (ops feedback, container sharding, small files optimizations), but on wednesday, we'll do our best to be more ad hoc (like we've done at previous events)
21:17:13 <notmyname> I expect we'll get a lot of good discussions done, but the reality is that we have vastly less time than we've had at previous openstack events
21:17:27 <notmyname> so keep that in mind, and we'll need to be very careful to not get too distracted
21:17:48 <mattoliverau> just makes the beer track more important ;)
21:17:53 <notmyname> of course, there's also the other unscheduled time in the hacking rooms, any hallway/bar conversations, and whatever else comes up
21:18:40 <notmyname> during the main conference time there's also a lot of good talks about swift or something related to swift. so be sure to mark stuff down on your schedule before you go :-)
21:18:56 <notmyname> or not. do what you want. *I'm* going to prepare ahead of time ;-)
21:18:59 <tdasilva> we can hack at boston common or copley square
21:19:03 <tdasilva> ;)
21:19:08 <notmyname> tdasilva: that sounds great :-)
21:19:09 <tdasilva> library is next door
21:19:19 <notmyname> tdasilva: what's the weather like? hot cold rain sun?
21:19:27 <tdasilva> rain :(
21:19:31 <timburke> tdasilva: i think we're *much* too loud for a library :P
21:19:44 <jungleboyj> notmyname: Forecast is for cool and rainy next week.
21:19:45 <notmyname> timburke: heh
21:19:48 <tdasilva> timburke: i think they have meeting rooms
21:20:28 <notmyname> also, we will not be having this meeting next week
21:20:44 <notmyname> are there any questions about the summit next week?
21:21:11 <mattoliverau> nope, look forward to seeing y'all
21:21:19 <joeljwright> have fun peeps!
21:21:21 <notmyname> me too
21:22:04 <notmyname> ok, please feel free to ask me if you have any questions
21:22:28 <notmyname> also, I think most of you have my cell, but if not it's 254-722-3321. feel free to call or text if you need something before or during the summit
21:22:41 <notmyname> moving on...
21:22:45 <notmyname> #topic TC goals
21:22:58 <notmyname> remember that the TC has set some whole-openstack goals for everyone
21:23:06 <notmyname> #link https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html
21:23:12 <notmyname> #link https://governance.openstack.org/tc/goals/pike/python35.html
21:23:53 <notmyname> note that as of yesterday, the first one (the wsgi one) has been redefined for uwsgi instead of mod_wsgi. I don't know the full impact of that for us, but at least be aware of that change if you've previously looked at it
21:24:05 <notmyname> so here's what we need to do
21:24:44 <notmyname> we need to write down our plans to get these done. ie a list of stuff we've got to solve or what's blocking us
21:24:58 <notmyname> then we need to add that (or a link to it) to the governance doc
21:25:28 <notmyname> then at the end of the pike cycle (in a few months) we need to link something similar that shows what if any progress we've made or how we've satisfied it
21:25:57 <notmyname> eg on the wsgi one, we might have been able to satisfy the previous one by simply linking to our "run in apache" docs. (that might need to change now)
21:27:13 <notmyname> the wsgi one is not one I'm too concerned about. IIRC the definition is that the proxy can be deployed and run with apache and uwsgi. and AIUI, that's already a test thats' set up and available in devstack
21:27:42 <notmyname> the py3 one is more concerning simply because the impact is more undefined and significantly more complicated
21:27:59 <notmyname> timburke and I have been tracking the py3 challenges in a gist
21:28:00 <notmyname> #link https://gist.github.com/tipabu/833b03a865dba96e9fa2230b82f5d075
21:28:33 <notmyname> but that's a stream-of-conciousness format and probably not too great for whatever needs to be linked in teh governance repo
21:29:17 <notmyname> this is how I'd like to make progress on the governance document requirements
21:29:57 <notmyname> I would like a volunteer to investigate the wsgi goal, including yesterday's redefinition, and see if our current docs satisfy it
21:30:32 <notmyname> then, ideally, that person will be in boston next week, and we sit down together and write up what's needed for the governance repo (but if not in boston, then we work together in irc)
21:31:10 <notmyname> for the py3 goal, timburke and I will continue on the gist and do the same (but all comments are welcome on the gist, if you know of other py3 porting challenges)
21:31:42 <notmyname> so (1) does that makes sense and sound good and (2) who can volunteer to work on teh wsgi goal one?
21:33:13 <mattoliverau> I would, but not really in a stable environment to make too many promises :(
21:33:24 <notmyname> clearly I can see that this is top priority for everyone ;-)
21:33:31 <notmyname> mattoliverau: yeah, you're off the hook
21:33:37 <acoles> notmyname: I'll try
21:33:38 <mattoliverau> also, rackspace is taking all my equipment today.. which is going to feel weird
21:34:13 <jungleboyj> mattoliverau:  :-(
21:34:36 <notmyname> acoles: ok, thanks. I expect that it should be a quick 30 minute look. please let me know if it turns out to be a lot more than that
21:34:57 <notmyname> #topic open discussion
21:35:01 <acoles> notmyname: ok
21:35:04 <notmyname> anything else to bring up this week?
21:35:21 <notmyname> anything else to discuss, or shall we adjourn until we see each other in person in boston?
21:36:16 <acoles> everyone who's not going to Boston - we'll miss you :(
21:36:24 <mattoliverau> very talkative bunch today
21:36:43 <jungleboyj> Everyone is trying to get presentations done for Boston.  ;-)
21:36:54 <mattoliverau> what acoles said +1
21:36:58 <mattoliverau> jungleboyj: lol
21:37:02 <jrichli> i'll miss seeing you all as well.  have fun!
21:37:18 <jungleboyj> jrichli:  :-(
21:37:58 <notmyname> ok, let's end (not early, but right on time, since we have nothing else to discuss in the meeting)
21:38:09 <notmyname> thank you for coming to the meeting. thank you for working on swift
21:38:13 <jungleboyj> Thanks!
21:38:16 <notmyname> I'll see (half of) you next week!
21:38:21 <notmyname> #endmeeting