21:00:14 <notmyname> #startmeeting swift
21:00:15 <openstack> Meeting started Wed Mar  7 21:00:14 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:16 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:18 <openstack> The meeting name has been set to 'swift'
21:00:21 <notmyname> who's here for the swift team meeting?
21:00:24 <mattoliverau> o/
21:00:30 <kota_> o/
21:00:32 <tdasilva> hi
21:00:34 <rledisez> hi o/
21:00:48 <notmyname> rledisez: we missed you last week
21:01:11 <mattoliverau> +1
21:01:17 <timburke> o/
21:01:27 <mattoliverau> Sounds like you had quite an adventure
21:01:29 <rledisez> i wish i could make it to dublin… next time :)
21:01:38 <clayg> rledisez: we missed you!  :'(
21:01:45 <acoles> hello
21:02:19 <notmyname> agenda this week is simply catch-up after the ptg
21:02:21 <notmyname> #link https://wiki.openstack.org/wiki/Meetings/Swift
21:02:38 <notmyname> here's the team picture, if you didn't get it yet: http://d.not.mn/swift_team_dublin_ptg.jpg
21:02:40 <mattoliverau> I feel like I just got home
21:03:04 <notmyname> mattoliverau: you and me both :-)
21:03:06 <clayg> mattoliverau: 🤣
21:03:09 <notmyname> #link https://etherpad.openstack.org/p/Dublin_PTG_Swift
21:03:29 <notmyname> #topic ptg topic summary
21:03:51 <notmyname> no need to exhaustively go over everything in detail, but there's a few hightlights to summarize for everyone
21:04:12 <notmyname> we talked about checkpoint releases and/or different upgrade support policies
21:04:26 <notmyname> we did not come to an agreement, other than we need to get actual upgrade testing in the gate
21:04:39 <notmyname> speaking of gate testing, tdasilva added probe tests!!
21:04:52 <mattoliverau> \o/
21:05:00 <notmyname> I'd say it makes me unreasonably happy, but I don't think it's unreasonable at all
21:05:00 <kota_> nice
21:05:06 <timburke> yay! now we just need logs for failures ;-)
21:05:17 <acoles> tdasilva: kudos
21:05:25 <mattoliverau> Baby steps :p
21:05:44 <notmyname> we also talked about py3 compatibility. this is becoming more important since distros are having serious conversations about when they will drop py2
21:05:45 <tdasilva> timburke: was looking at this patch for ideas: https://review.openstack.org/#/c/548226/
21:05:45 <patchbot> patch 548226 - swift - DNM: Try out to pull execution logs of functests
21:06:04 <timburke> nice. go kota_!
21:06:21 <notmyname> our resident distro people (ie tdasilva and mattoliverau) have said they'll likely be able to get official permission to work on it
21:06:27 <kota_> it still goes to fail to take the log tho :/
21:07:04 <mattoliverau> Oh yeah, I'll go follow up with the powers that be about that. Thanks for the remindr
21:07:14 <notmyname> for the py3 work, we agreed that (1) one +2 will be sufficient to land it (otherwise we will not make any process) (2) it will take a while (3) we'll live with the reality that this will cause bugs
21:08:09 <notmyname> m_kazuhiro shared his work on the general task queue and using for improving the object expirer. he's continuing to work on that
21:08:26 <notmyname> acoles and clayg spent pretty much teh whole week working on container sharding
21:08:30 <timburke> and (4) prioritize having a functioning py3 proxy -- it's the func tests that will be the real proof of compatibility
21:08:41 <notmyname> timburke: +1
21:08:50 <acoles> I moved all my notes from last week to a separate etherpad https://etherpad.openstack.org/p/deep-containers-dublin-ptg
21:08:51 <clayg> I was just catching up - it's a mind warp at first.  mattoliverau knows.
21:08:55 <acoles> #link https://etherpad.openstack.org/p/deep-containers-dublin-ptg
21:09:01 <notmyname> acoles: thanks
21:09:06 <mattoliverau> ;)
21:09:29 <notmyname> personally, I've got some employer deliverables related to container sharding, so we're working on timelines for what's possible to deliver soon and what can be deferred
21:09:51 <notmyname> kota_ shared the ongoing work with the s3api integration
21:10:26 <notmyname> for s3api we agreed that we would simply work on an import of swift3. we would *not* do the further refactoring to unblock future compat work. we'll defer that to later
21:10:57 <notmyname> the goal kota_ said he could do (after adding in a few more tests) is to be done "in a month or so"
21:11:26 <notmyname> we talked about ops tools. logging, monitoring, alerting, and so on
21:12:08 <notmyname> it was hard to come up with concrete "let's do this next" items, other than simply sharing what each of us are doing more publicly
21:12:29 <notmyname> we agreed that sharing on the openstack mailing list (either -dev or -operators) would be better than doing it via IRC
21:12:44 <notmyname> mostly because of timezones, but also to include those who don't lurk in IRC
21:13:12 <clayg> pete is always telling us to use the ML more
21:13:49 <notmyname> unfortunately we missed OVH talking about "lots of small files". maybe we could get rledisez and alex to have a phone/video chat about it in the next week or so
21:14:27 <rledisez> sure, i'll talk to alecuyer about that. he's in vacation this week
21:15:01 <rledisez> we had some point to talk about like requirement patches, and to give some prod feedbacks
21:15:13 <notmyname> great
21:15:19 <notmyname> for the "improve the consistency engine" topic, swiftstack shared what we'll be working on and what we won't be working on. torgomatic has already been proposing patches related to this
21:16:07 <rledisez> is there more info on that topic?
21:16:09 <notmyname> one important thing on the consistency engine improvements is that we will not be removing rsync now nor rewriting in golang. these are both things we definitely want to do, but we won't get to them soon, as a community
21:16:28 <rledisez> i'm *very* interested
21:16:33 <notmyname> there's too much other big stuff that needs to happen first, and not enough people to make progress on all of it
21:16:47 <notmyname> rledisez: ok. let's talk more then
21:17:15 <clayg> "requirement patches" ???
21:17:25 <notmyname> and that gets us to the end of the stuff we talked about. what did I miss?
21:17:26 <timburke> rledisez: you might be interested in https://review.openstack.org/#/c/545496/,  https://review.openstack.org/#/c/545497/, https://review.openstack.org/#/c/548628/, and https://review.openstack.org/#/c/541058/
21:17:27 <patchbot> patch 545496 - swift - Make DB replicators ignore non-partition directories (MERGED)
21:17:28 <patchbot> patch 545497 - swift - Add handoffs-only mode to DB replicators.
21:17:29 <patchbot> patch 548628 - swift - Support -d <devs> and -p <partitions> in DB replic...
21:17:31 <patchbot> patch 541058 - swift - Add fallocate_reserve to account and container ser...
21:17:36 <notmyname> timburke: thanks
21:18:55 <rledisez> ok, i'll check that, thx timburke
21:19:32 <notmyname> rledisez: if you can stay just a bit after the meeting (I know it's late), I can give you a quick summary of where we are with consistency engine stuff
21:20:02 <notmyname> rledisez: what are the requirements patches you mentioned?
21:20:32 <rledisez> clayg notmyname: https://review.openstack.org/#/c/447129/ and https://review.openstack.org/#/c/548034/ and https://review.openstack.org/#/c/548589/
21:20:32 <patchbot> patch 447129 - swift - Configure diskfile per storage policy
21:20:34 <patchbot> patch 548034 - swift - Add optional parameters to common/utils fallocate()
21:20:35 <patchbot> patch 548589 - swift - WIP - Change object_audit_location_generator() to ...
21:20:39 <rledisez> notmyname: ok to talk after
21:21:05 <clayg> ah yes, i remember seeing those updated last week
21:21:23 <rledisez> these 3 patches are the base for LOSF
21:21:46 <notmyname> ah, got it. I understand now
21:21:52 <clayg> 👍
21:22:35 <notmyname> nobody has mentioned anything else, so I think that means I covered it all
21:23:41 <notmyname> anything else to bring up this week?
21:23:54 <acoles> notmyname: great summary, thanks
21:24:04 <mattoliverau> +1
21:24:36 <notmyname> I'll admit I've not been doing a great job on keeping the review dashboard and/or priority reviews updated lately. I need to get back on that. if it doesn't get better in the next few days, please gripe at me about it
21:25:30 <clayg> notmyname: CAN DO!
21:25:44 <clayg> you can always count on me to give you hard time.
21:25:56 <notmyname> broader openstack-wide discussions that I've seen that may be of interest to everyone include: "extended maintenance", python3 support, and the future of the PTG
21:26:02 <notmyname> clayg: +1
21:26:50 <notmyname> anything else from anyone?
21:27:05 <kota_> ah, add a thing to the summary, it's hard wether but very productive
21:27:07 <acoles> notmyname: did you hear if there a september PTG?
21:27:14 <kota_> it was
21:27:45 <notmyname> acoles: last I saw is that there will be another in 2018 btu the 2019 plan is what's being discussed. and that's the extent of detail I've seen
21:27:50 <kota_> weather
21:28:05 <notmyname> kota_: yep. crazy weather. but fun :-)
21:28:06 <torgomatic> do we know where the other 2018 PTG will be?
21:28:13 <notmyname> torgomatic: no, not yet
21:29:06 <notmyname> last call to bring up something else
21:29:28 <notmyname> done
21:29:45 <notmyname> thanks everyone for coming today. great to spend the week with you last week in frosty dublin
21:29:49 <notmyname> thank you for your work on swift
21:29:52 <notmyname> #endmeeting