Jump to: navigation, search

Difference between revisions of "Meetings/Swift"

(One intermediate revision by the same user not shown)
Line 3: Line 3:
 
! '''2100 UTC Meeting'''
 
! '''2100 UTC Meeting'''
 
|-
 
|-
| '''Next meeting:''' Mar 20th, 2024
+
| '''Next meeting:''' May 1, 2024
 
|-
 
|-
 
| '''Location:''' #openstack-swift on OFTC
 
| '''Location:''' #openstack-swift on OFTC
 
|-
 
|-
| '''Chair:''' mattoliverau
+
| '''Chair:''' timburke
 
|-
 
|-
 
|
 
|
 
<!-- List 2100UTC meeting items below here -->
 
<!-- List 2100UTC meeting items below here -->
* s3api: Fix handling of non-ascii access keys
+
* Utils refactor - expect merge conflicts!
** 913723 | https://review.opendev.org/c/openstack/swift/+/913723
+
** https://review.opendev.org/c/openstack/swift/+/914029
* expirer grace period
+
* Probe test time outs
** 874806: Add per account grace period to object expirer | https://review.opendev.org/c/openstack/swift/+/874806
+
** https://zuul.opendev.org/t/openstack/builds?job_name=swift-probetests-centos-9-stream&job_name=swift-probetests-centos-8-stream&project=openstack%2Fswift&result=TIMED_OUT&skip=0&limit=100
** 874710: Add x-open-expired to recover expired objects | https://review.opendev.org/c/openstack/swift/+/874710
+
** Some of these make sense -- some patchesets break every probe test and our retry-failed-tests logic causes the test time to essentially double
* cooperative tokens
+
** Others just seem to hang for an hour or more
** 890174: add memcached based cooperative token mechanism | https://review.opendev.org/c/openstack/swift/+/890174
+
* liberasurecode release
** 908969: use cooperative tokens to coalesce updating shard range requests into backend | https://review.opendev.org/c/openstack/swift/+/908969
+
** https://review.opendev.org/c/openstack/liberasurecode/+/917784
* Feature/MPU feature branch
+
** Nothing major, but it's been a couple years
** It's actaully happening!
+
* pyeclib manylinux wheels
* aws-chunked transfers
+
** https://review.opendev.org/c/openstack/pyeclib/+/817498 - Add Dockerfile to build manylinux wheels
** 909049: s3api: Improve checksum-mismatch detection | https://review.opendev.org/c/openstack/swift/+/909049
+
** https://review.opendev.org/c/openstack/pyeclib/+/917857 - Add job to build wheels
** 909800: utils: Add crc32c function | https://review.opendev.org/c/openstack/swift/+/909800
+
* expirer work
** 909801: s3api: Add support for additional checksums | https://review.opendev.org/c/openstack/swift/+/909801
+
** https://review.opendev.org/c/openstack/swift/+/914713 - expirer: new options to control task iteration
*** probe tests are consistently failing in the gate, but ''why''?
+
** https://review.opendev.org/c/openstack/swift/+/916026 - distributed parallel task container iteration
** 909802: WIP: s3api: Additional checksums for MPUs | https://review.opendev.org/c/openstack/swift/+/909802
+
** https://review.opendev.org/c/openstack/swift/+/912496 - add bytes of expiring objects to queue entry
** 836755: Add support of Sigv4-streaming | https://review.opendev.org/c/openstack/swift/+/836755
+
* broker row insertion order py2/py3 behavior difference
* drive-full-checker
+
* unreleased swiftclient regression
** Run it on cron to disable(/re-enable) rsync based on disk fullness
+
** https://review.opendev.org/c/openstack/python-swiftclient/+/916135
** 907523: drive-full-checker | https://review.opendev.org/c/openstack/swift/+/907523
 
* s3api and slo Partnum support
 
** Swift chain landed!
 
** 902020: support part-num in python swiftClient | https://review.opendev.org/c/openstack/python-swiftclient/+/902020
 
* 839643: Drop support for liberasurecode<1.4.0 | https://review.opendev.org/c/openstack/pyeclib/+/839643
 
 
<!-- End 2100UTC meeting items -->
 
<!-- End 2100UTC meeting items -->
 
|}
 
|}

Revision as of 20:23, 1 May 2024

2100 UTC Meeting
Next meeting: May 1, 2024
Location: #openstack-swift on OFTC
Chair: timburke
Meeting Logs http://eavesdrop.openstack.org/meetings/swift/2024/
Useful Commands #link #info #agreed #topic and #startmeeting

When adding an item, please include your IRC nickname with it.