21:00:01 #startmeeting swift 21:00:02 Meeting started Wed Jul 3 21:00:01 2019 UTC and is due to finish in 60 minutes. The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:05 The meeting name has been set to 'swift' 21:00:31 who's here for the swift meeting? 21:00:36 o/ 21:01:07 o/ 21:01:51 more like 🥳 time!!! 21:02:24 agenda's at 21:02:25 #link https://wiki.openstack.org/wiki/Meetings/Swift 21:02:33 #topic py3 21:02:44 we're soooo clooose! 21:02:57 sounds awesome. 21:03:04 mattoliverau's started looking at https://review.opendev.org/#/c/662546/ already 21:03:05 patch 662546 - swift - py3: Be able to read and write non-ASCII headers - 5 patch sets 21:03:15 which is good, as it's the one i'm more nervous about 21:03:34 https://review.opendev.org/#/c/653548/ can be looked at in parallel 21:03:35 patch 653548 - swift - py3: add swift-dsvm-functional-py3 job - 14 patch sets 21:04:03 between those two, you can get py2 tests running against py3 services 21:04:17 which we start gating on in https://review.opendev.org/#/c/666942/ 21:04:18 patch 666942 - swift - Run all func tests under py2 against services runn... - 1 patch set 21:04:25 o/ 21:05:32 i've already put py3 in my release notes - https://review.opendev.org/#/c/668990/ - so let's get those last few landed! 21:05:33 patch 668990 - swift - Authors/changelog for 2.22.0 - 1 patch set 21:05:35 hello! 21:05:43 +1 21:05:49 o/ 21:05:54 who can commit to reviewing patches? 21:07:11 i review stuff sometimes 21:07:30 1 patch, I might be able to review in the next week 21:07:47 clayg or kota_, want to take on https://review.opendev.org/#/c/653548/ ? 21:07:48 patch 653548 - swift - py3: add swift-dsvm-functional-py3 job - 14 patch sets 21:08:08 ok 21:08:14 i'm guessing mattoliverau will keep working on https://review.opendev.org/#/c/662546/ ;-) 21:08:15 patch 662546 - swift - py3: Be able to read and write non-ASCII headers - 5 patch sets 21:08:27 yup 21:09:06 i think i'm ok with moving forward on the release after *just those two* 21:09:55 that's about it for py3 21:10:00 #topic losf 21:10:39 I wrote more tests, 21:10:43 https://review.opendev.org/#/c/666378/ 21:10:44 patch 666378 - swift (feature/losf) - Add tests for vfile.py - 3 patch sets 21:10:47 yay! 21:10:49 alecuyer85: nice!!! 21:11:04 I think there are a few corner cases I want to handle or test better (a few comments about it in the test code) 21:11:34 also, i think our dsvm job isn't happy on the branch any more :-( 21:11:48 i've been trying to sort out why 21:11:51 oh 21:11:59 +1414, -373 :D 21:12:18 those RETRY_LIMITs seem pretty consistent 21:12:32 Ill look at it also 21:12:52 bumped into it while trying to get https://review.opendev.org/#/c/664424/ and https://review.opendev.org/#/c/668007/ in 21:12:53 patch 664424 - swift (feature/losf) - Get new unit tests running under py3 - 2 patch sets 21:12:54 patch 668007 - swift (feature/losf) - Merge remote-tracking branch 'gerrit/master' into ... - 1 patch set 21:12:55 i see. did we change something on dsvm? 21:13:18 i see 21:13:56 i think it's something external to us, but i'm not sure what. that first patch was happy Jun 17, but failed Jun 26 21:14:58 ok. let's clarify what causes the problem. 21:16:41 http://logs.openstack.org/24/664424/2/gate/swift-dsvm-functional/5f4859d/controller/logs/screen-s-proxy.txt.gz seems to be the cause 21:17:58 looks like distribution error on urllib3 which is from... requests module maybe? 21:18:27 but the version of requests (which i *think* is the only thing that would bring in urllib3) that gets installed doesn't have that version constraint: https://github.com/kennethreitz/requests/blob/v2.22.0/setup.py#L47 21:18:33 i saw the problem recently on requests... but not sure. 21:19:49 if anyone has ideas on how to further diagnose that, i'd love to hear them... but maybe after the meeting, in #openstack-swift 21:20:07 alecuyer85, is there anything else we should be aware of or helping with? 21:20:21 https://opendev.org/openstack/requirements/src/branch/master/upper-constraints.txt#L190 ? 21:20:57 timburke, taking a look at the patch would be great, see if that's going OK even if I know I still need a few changes 21:21:00 clarkb, yeah, but requests (https://opendev.org/openstack/requirements/src/branch/master/upper-constraints.txt#L249) should be happy with that 21:21:11 timburke: ya looks like both versions are fine 21:21:18 or rather they don't conflict with each other 21:21:25 right 21:22:07 alecuyer85, can do 21:22:40 #topic autosharding 21:22:52 mattoliverau, looks like you've been busy :-) 21:23:10 So last week was hackweek at SUSE, so I spent some time playing with a new implementation of auto sharding 21:23:38 It's still a WIP but have even written a rambly doc on it (and it's on the ideas page) 21:23:44 #link https://docs.google.com/document/d/15yG9zOatwPyXCA3YLNLdNIue9qDR4wLyMPIbypcbALc/edit?usp=sharing 21:24:05 Just wanted to bring it to peoples attention. 21:24:38 If your interested take a look at the current iplementation. It's just a first parse at the version + index 0 attempt 21:24:39 nice doc! thanks 21:24:48 ta 21:25:31 There is a possible edge case ( 1of many I'm sure) I talk about at the end, and possible ways to eliviate it. 21:26:09 not 100% it is a problem, that just comes from a white board session I had had trying to brain storm issues. 21:26:55 I need to go and refamilarise myself with the sharding replication changes to really confirm, or better make a probe test :) 21:27:54 Anyway, if your interest take a look. I made some interesting asumptions and moves in the patch, which may or may not be right (like adding an ELECT verb to the container-server so they can vote and keep the code simple 21:28:14 That's all I got for now :) 21:28:25 i like new verbs for new behaviors 21:28:52 but then, you may have noticed that from https://review.opendev.org/#/c/659162/ ;-) 21:28:53 patch 659162 - swift - Add operator tool to async-delete some or all obje... (MERGED) - 7 patch sets 21:29:12 I did ;) 21:30:21 i'll at least read through the doc by next meeting, try to form some opinions 21:30:36 ta, can't ask for any more then that ;) 21:30:46 mattoliverau, anything else we should know or do? 21:31:13 nope, the doc points to the bottom of the patch set (currently of 2 patches) 21:31:37 if it interests you in reviewing.. but also feel free to leave comments in the doc. 21:32:05 all right 21:32:08 #topic open discussion 21:32:14 anything else to bring up? 21:34:10 so has anyone else ever seen container replicator lockups since we did sharding? 21:34:36 i noticed a missing timeout that prompted https://review.opendev.org/#/c/668963/ last night/this morning... 21:34:37 patch 668963 - swift - container-replicator: Add a timeout for get_shard_... - 1 patch set 21:37:26 huh. just us, i guess... seems suspicious :-/ 21:38:10 how does everyone feel about the py3 support? do we think this is going to go well, or terribly, or somewhere in between? 21:38:36 in between :P 21:38:43 +1 :) 21:39:04 but experimental label for a release would make be feel better. 21:39:35 going to go well, maybe? 21:40:25 i hope it genuinely results in better outcomes :-) i kinda worry that people will see experimental, not really use it yet, and then we won't have the extra testing we wanted 21:40:40 the py3 gate prevent me to push incompatible patch. it may make slow down but the compatibility will be required anyway? 21:41:46 yeah, then there's that aspect. and it's going to be a bit until we can drop py2 21:42:02 Drop it!!! 21:42:30 clayg, not *yet*! we have to *at least* have py3 support first! 21:42:41 well I hope when we have it running we all could run in SAIO or at least 1 SAIO and iron out any obivous shortcomings :) 21:42:47 😂 21:42:50 I think clayg wanted to use tauthon 21:43:06 Or that yes. 21:43:41 This is fine. When we merge LOSF we’ll have 3 languages. 21:43:44 I think we can switch some test clusters to use py3 and hopefully catch some things (if there is anything to catch!) 21:44:27 hmm... i should look at dropping the devstack exclusion to make sure swift runs on py2 even when everything else is on py3... 21:44:34 alecuyer85, that'll be great! thanks 21:44:56 I think we’re going to have a pretty big lift to get py3 going. We might do it on NEW distros only e.g. rhel8 21:45:17 i'm sure there's some bugs lurking in the non-client-path 21:46:00 But we’ll probably be importing Swift code in py3 as ecosystem stuff starts to add more py3 support. I’ll probably default vsaio to py3 21:46:33 This’ll be great. 21:46:38 👍 21:46:43 +1 21:47:06 all right, does anyone have anything else to bring up? 21:48:09 i think i'm going to call it then 21:48:25 thank you all for coming, and thank you for working on swift! 21:48:31 #endmeeting