21:00:46 <notmyname> #startmeeting swift
21:00:47 <openstack> Meeting started Wed Feb  7 21:00:46 2018 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:48 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:50 <openstack> The meeting name has been set to 'swift'
21:00:57 <notmyname> who's here for the swift team meeting?
21:01:00 <m_kazuhiro> o/
21:01:05 <kota_> hi
21:01:14 <mattoliverau> o/
21:01:20 <tdasilva> hello
21:01:30 <rledisez> hi o/
21:01:33 <timburke> o/
21:02:14 <notmyname> welcome everyone
21:02:26 <notmyname> are we missing anyone?
21:02:34 <acoles> hello
21:03:12 <notmyname> I'd realized only an hour ago that I hadn't updated the meeting agenda from last week
21:03:16 <notmyname> (it's updated now)
21:03:19 <notmyname> #link https://wiki.openstack.org/wiki/Meetings/Swift
21:03:41 <notmyname> but since there's not much been added, it may be short. let's see what happens :-)
21:03:47 <notmyname> #topic swift 2.17.0 release
21:03:55 <notmyname> we did a release!
21:04:01 <notmyname> thanks and congrats to everyone
21:04:05 <mattoliverau> \o/
21:04:29 <notmyname> this 2.17.0 release is also our final release for the openstack queens cycle
21:04:33 <timburke> we got just about all of https://wiki.openstack.org/wiki/Swift/PriorityReviews in! best release ever
21:04:45 <mattoliverau> And symlinks are now a real thing
21:04:55 <notmyname> symlinks and data segments both!
21:04:57 <acoles> there's loads of good stuff in there, well done everyone!
21:04:58 <timburke> still have those lingering high prio bugs tho...
21:05:39 <notmyname> timburke: I don't expect we'll ever have zero high priority bugs :-)
21:05:46 <timburke> crap! and i still haven't written up the bug i found in https://review.openstack.org/#/c/530411/ !
21:05:47 <patchbot> patch 530411 - swift - Fix socket leak on 416 EC GET responses. (MERGED)
21:06:02 <joeljwright> o/
21:06:23 <notmyname> are there any questions about the release or the broader openstack cycle?
21:07:42 <tdasilva> notmyname: just to clarify, we don't expect another swift release before queens?
21:08:22 <notmyname> correct.
21:08:36 <notmyname> the deadline for a queens release is the 22nd
21:08:39 <timburke> just one: how much more awesomeness are we gonna ship in the next cycle?
21:08:41 <timburke> but i already know the answer: "as much as possible"
21:08:54 <notmyname> I don't expect to have another release in two weeks
21:09:18 <acoles> notmyname: if you do, get it into the gate queue soon ;)
21:09:23 <notmyname> lol
21:09:45 <notmyname> I know I'd mentioned it was a possibility, but we delayed the 2.17.0 release by a little bit to include some other stuff under review, and that puts us too close to the deadline to do another release
21:10:06 <tdasilva> ack
21:10:20 <notmyname> #topic PTG prep
21:10:35 <notmyname> speaking of stuff happening in just a few weeks...
21:10:41 <notmyname> the PTG is rapidly approaching
21:11:05 <notmyname> first, while I'm thinking of it, is anyone interested in doing another video interview for swift?
21:11:14 <notmyname> a few of us did it last time
21:11:23 <notmyname> I can sign us up
21:12:06 <notmyname> I see everyone is jumping at the opportunity to be filmed talking about swift :-)
21:12:20 <mattoliverau> I'm always happy to chat, but that's if no one else wants too
21:12:21 <notmyname> ok, I'll sign us up, and we'll see who's around when the time comes :-)
21:12:49 <notmyname> the topic planning etherpad is at
21:12:51 <notmyname> #link https://etherpad.openstack.org/p/Dublin_PTG_Swift
21:12:58 <acoles> notmyname: sign up and press gang us in dublin
21:13:46 <notmyname> on the one hand, it's a lot shorter (so far) than it's been for other in-person events. on the other hand, the topics that are there are pretty big and could take a lot of time
21:15:46 <notmyname> I'm curious about the py3 topic. it's one of those things we haven't spent a ton of time on (because it's really hard), but it's going to be a really big deal sooner than we realize
21:16:07 <tdasilva> yep! pretty big
21:16:16 <clayg> big deal?
21:16:16 <timburke> i threw up a few more patches... it's gonna be a mess
21:16:45 <clayg> why can't we just admit that python2 is cobal - it's a different language than py3 and it's not going away - evar.
21:17:04 <torgomatic> py3 is one of those things that needs several people all working on it at the same time; if you have just one person poking at it, then reviews take forever, and by the time they land there's more py2-isms introduced in the code you're changing anyway
21:17:06 <clayg> if someday we want to rewrite swift - maybe we pick py3?
21:17:08 <notmyname> clayg: because that's not our call to make :-(
21:17:18 <notmyname> clayg: unlikely ;-)
21:17:30 <clayg> oic, maybe I was confused then
21:17:34 <mattoliverau> Now that symlinks are in are there topics we can push forward on now, policy migration? I know that would be handy at work ATM.
21:17:40 <notmyname> rledisez: will you be able to share what's going on with LOSF? any chance you'll also be able to share code?
21:18:04 <notmyname> clayg: oh, I just mean that we wouldn't likely choose any python if we started over from scratch :-)
21:19:01 <rledisez> notmyname: sure. alecuyer was cleaning code to push something before PTG (it still won't be deduplicated with upstream diskfile, but it's a begining)
21:19:16 <notmyname> rledisez: yay!
21:19:20 <notmyname> mattoliverau: yeah, having symlinks does enable some other stuff to happen, especially the things that kota_ and especially m_kazuhiro have been working on
21:19:52 <notmyname> mattoliverau: but the trick will be to prioritize
21:19:54 <mattoliverau> Well I'm happy to talk about them too, even if it's just me and them ;)
21:20:01 <mattoliverau> +100
21:20:06 <mattoliverau> Of course
21:20:31 <mattoliverau> Top priorities first of course, just also don't want to waste some face time :)
21:21:27 <notmyname> on that point (don't want to waste face time), I'm sure there are other topics we'll want to discuss in dublin
21:21:38 <notmyname> if you've got one, please add it to the etherpad
21:22:15 <notmyname> and any detail would be helpful (eg "py3" isn't as good as "how to solve bytestring types in a migration to py3")
21:23:28 <notmyname> from the etherpad, it looks like most of us will be in dublin the full week (mon-fri)
21:23:29 <timburke> there's no solving it. there's banging your head against the keyboard until tests pass and you've got a general feeling like the tests still mean the same thing as they did before, but now in two (related, but subtly different) languages
21:24:12 <clayg> timburke: maybe more clever titles like "why Guido randomly hates you"
21:24:32 <notmyname> I think we'll have the ability to find a room on monday-tuesday
21:24:46 <notmyname> there's also other projects' topics to look at too
21:25:26 <notmyname> all the plannign etherpads should be linked from
21:25:27 <notmyname> #link https://wiki.openstack.org/wiki/PTG/Rocky/Etherpads
21:26:02 <notmyname> anything else we need to discuss about the PTG?
21:26:22 <acoles> if we have spare time we could have another bug triage session, like we did in Denver
21:26:43 <notmyname> https://bugs.not.mn/project/swift/bug_trends/None
21:27:25 <notmyname> acoles: that's a good idea
21:27:35 <mattoliverau> Yeah, if there is nowhere anyone needs to be let's bug triage :)
21:27:36 <timburke> i love when we trend toward bugs: none!
21:27:50 <timburke> aw, that's not what the link says *at all*...
21:28:01 <tdasilva> lol
21:28:06 <torgomatic> try reading right to left
21:28:22 <acoles> I think the 'None' is referring to level of hope
21:28:31 <joeljwright> :D
21:30:15 <notmyname> if you look at the "all" history, it seems like there's been a great drop recently, especially around the last denver ptg where we focused on it!
21:30:24 <notmyname> point is, we can make it better!
21:30:28 <notmyname> there is hope!
21:31:06 <notmyname> #topic open discussion
21:31:19 <notmyname> is there anything else we need to discuss in this meeting this week, or shall we end early?
21:31:45 <mattoliverau> Ahh and the dates are in weird American layout. Not international yyyy-mm-dd :p
21:32:36 <timburke> mmm... delicious middle-endian dates
21:33:01 <mattoliverau> Lol
21:33:02 <notmyname> I'm going to take that as "no, nothing else to bring up" :-)
21:33:11 <acoles> notmyname: not from me
21:33:20 <notmyname> thanks everyone for coming. thanks for your work on swift
21:33:22 <notmyname> #endmeeting