21:00:59 <mattoliverau> #startmeeting swift
21:01:00 <openstack> Meeting started Wed Nov 28 21:00:59 2018 UTC and is due to finish in 60 minutes.  The chair is mattoliverau. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:01:01 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:01:03 <openstack> The meeting name has been set to 'swift'
21:01:14 <mattoliverau> who's here for the swift team meeting?
21:01:21 <timburke> o/
21:01:27 <tdasilva> hello
21:01:37 <mattoliverau> \o/ hey guys
21:01:40 <rledisez> hi o/
21:02:36 <mattoliverau> this will be another status update meeting. notmyname is travelling so I'll have to try and fill his enourmous shoes.
21:02:45 <mattoliverau> agenda is at
21:02:51 <mattoliverau> #link https://wiki.openstack.org/wiki/Meetings/Swift
21:03:23 <mattoliverau> Just a few topics and mainly priority reviews and status updates on task queue and losf
21:04:07 <mattoliverau> this might be a quick meeting.
21:04:09 <clayg> mattoliverau: o/
21:04:13 <mattoliverau> clayg: o/
21:04:24 <mattoliverau> cool, let's get started
21:04:32 <mattoliverau> #topic priority reviews
21:04:41 <mattoliverau> #link https://wiki.openstack.org/wiki/Swift/PriorityReviews
21:04:54 <clayg> that list looks good - mattoliverau did you curate that?
21:05:15 <mattoliverau> nah, I'm too lazy to do that :P
21:05:17 <tdasilva> I noticed kazuhiro updated some general task queue patches
21:06:07 <mattoliverau> So last week we talked about adding my multi-kms patch to the prioirty reviews, which I forgot, but doesn't matter because thanks to timburke it's been +Aed!
21:06:29 <mattoliverau> tdasilva: yeah, wish we was here so we could ask about it's state
21:06:34 <mattoliverau> *he
21:06:39 <timburke> just needs to get through the gate ;-)
21:07:09 <mattoliverau> yeah, easier said then done. I was hoping to say it's landed.. but alas not :P
21:07:49 <mattoliverau> how are the pending s3api patches going? timburke?
21:08:23 <timburke> no real progress -- i at least did some rebasing, though!
21:08:26 <mattoliverau> any more to add? need more eyes for reviews?
21:08:36 <mattoliverau> ahh rebasing is good.
21:08:54 <mattoliverau> also, it has been Thanksgiving so a slower week then normal
21:08:57 <timburke> eyes are good. https://review.openstack.org/#/dashboard/?S3+API=status:open+file:%255Eswift/common/middleware/s3api/.*+project:openstack/swift is a handy dash to look at just s3 changes
21:09:19 <mattoliverau> also to all you Americans, happy thanksgiving and I hope your fridges are full of leftovers :)
21:09:47 <mattoliverau> #link  https://review.openstack.org/#/dashboard/?S3+API=status:open+file:%255Eswift/common/middleware/s3api/.*+project:openstack/swift
21:10:10 <timburke> oh yeah! https://review.openstack.org/#/c/609860/ is a reasonably cool patch that would open up some possibilities like https://review.openstack.org/#/c/610747/
21:10:55 <mattoliverau> ahh cool
21:10:58 <timburke> but i need to come up with a better name for the callback than "slo_validator", since it can make modifications, too...
21:11:23 <mattoliverau> slo-matic :P
21:11:43 <mattoliverau> slo-mematron
21:11:56 <mattoliverau> too early for me :P
21:12:09 <clayg> timburke: the name is always the hardest part
21:12:09 <timburke> i was thinking slo_manifest_hook but i'm certainly open to suggestions
21:12:24 <clayg> hooks are good!
21:12:38 <timburke> clayg: real handy for catching fish!
21:12:42 <mattoliverau> we (old rackspace team) used to use a project naming engine
21:13:18 <mattoliverau> it's where we got turbohipster (for some nova 3rd party api runner we wrote)
21:13:34 <mattoliverau> anyway, now I'm distracted and off topic :P
21:14:05 <mattoliverau> Anything else re:priority reviews? anything we need to add?
21:14:28 <mattoliverau> let's move on
21:15:34 <mattoliverau> #topic task queue
21:15:51 <mattoliverau> kazuhiro isn't here unfortuantly
21:16:03 <mattoliverau> So not much to really say about this.
21:16:29 <mattoliverau> rledisez: any chance you had to time to look at the follow up doc patch we want to merge in? kazuhiro wanted you to take a look.
21:17:12 <rledisez> mattoliverau: no, sorry for that, i've been busy fighting eventlet (but I won, i think…)
21:17:13 <mattoliverau> As tdasilva mentioned, kazuhiro pushed up a new change set yesterday (my time). I haven't looked closely but think it might be a rebase
21:17:34 <mattoliverau> rledisez: 1 eventlet: 0
21:18:18 <timburke> rledisez: you were right, that was a good bug :-)
21:18:23 <mattoliverau> rledisez: nps, when you get a change. it's just documentation regarding the implementation in the overview_expiring_objects section
21:18:31 <mattoliverau> *chance
21:18:36 <mattoliverau> man, I can't type today
21:19:17 <mattoliverau> let's move on so rledisez can tell us about eventlet battles and losfs :)
21:19:22 <mattoliverau> #topic LOSF
21:19:54 <mattoliverau> rledisez: any updates here, we saw the eventlet bug and patch you talked about last week
21:20:06 <mattoliverau> clayg looked at it and I think it's even landed already
21:20:23 <rledisez> so, 3 bugs this week, not all related to losf, but all related to eventlet (one fix merged), the second was in losf (finally was not always called in try/except/finally). last one was in a patch I proposed related to ssync and concurrency
21:20:28 <rledisez> we won the 3 battles :D
21:20:55 <clayg> #FTW
21:21:42 <rledisez> on pure losf side, it' quite calm, alexandre is fixing some bugs we discover from time to time. nothing really serious (aka, it's not eating data), some memory leaks & co
21:21:43 <mattoliverau> \o/ nice
21:22:19 <mattoliverau> no that's good, if your running in prod and it's nice and quite, that sounds like it's getting pretty stable, which is awesome news
21:23:11 <mattoliverau> Finally block _not_ getting called sounds.. well.. rather broken, wow.
21:23:27 <mattoliverau> anything the rest of us need to do to help losf's out?
21:23:40 <timburke> depends on how hard things fail -- i could *totally* see it not necessarily getting called
21:23:58 <timburke> SIGKILL = no finally (for example)
21:24:34 <clayg> "oh, i'm sorry were you saying something?" -kernel
21:24:38 <rledisez> the process was not crashing. alexandre could give you the details, but it was just not calling finally, and was continuing to run the function
21:24:45 <mattoliverau> well yeah I guess, but when I'm coding I tend, maybe wrongly, that my finally block would be run :)
21:24:56 <mattoliverau> lol
21:25:08 <mattoliverau> OOM
21:25:28 <clayg> mattoliverau: yeah i agree sounds wild
21:25:56 <clayg> alex may indeed have to give us the details - without some careful comments it's likely the issue would get re-introduced if we don't have a communal understanding
21:26:09 <clayg> no to mention raising concerns of other places the same issue might exists 😬
21:26:10 <mattoliverau> +1
21:26:28 <mattoliverau> but I'm sure it'll all be sorted in py3 :P
21:26:38 <mattoliverau> or go
21:27:32 <mattoliverau> rledisez: anything else? anywhere we can help?
21:28:16 <rledisez> mattoliverau: not for now I think. i'll try to get alex to join the meeting next time so he can gives more updates and ask help if he needs some
21:28:26 <mattoliverau> sweet
21:28:33 <mattoliverau> let's move on then.
21:28:40 <mattoliverau> #topic open discussion
21:28:57 <mattoliverau> The floor is open
21:29:28 <mattoliverau> anything else to bring up at the meeting, any interesting ideas, problems, patches to highlight
21:29:45 <mattoliverau> any funning holiday stories.
21:30:02 <clayg> 😁
21:30:20 <mattoliverau> *funny *sigh*
21:30:39 <mattoliverau> I really should just give up, go back to bed and start again :P
21:31:09 <mattoliverau> *chirp* *chirp*
21:31:26 <mattoliverau> Cool, a shorter meeting, we all get an early mark
21:31:32 <mattoliverau> meeting ending in...
21:31:36 <mattoliverau> 3..
21:31:42 <mattoliverau> 2..
21:31:48 <mattoliverau> 1..
21:31:53 <mattoliverau> #endmeeting