Jump to: navigation, search

Difference between revisions of "Meetings/Swift"

(37 intermediate revisions by 4 users not shown)
Line 3: Line 3:
 
! '''2100 UTC Meeting'''
 
! '''2100 UTC Meeting'''
 
|-
 
|-
| '''Next meeting:''' Dec 14th, 2022
+
| '''Next meeting:''' May 1, 2024
 
|-
 
|-
 
| '''Location:''' #openstack-swift on OFTC
 
| '''Location:''' #openstack-swift on OFTC
Line 11: Line 11:
 
|
 
|
 
<!-- List 2100UTC meeting items below here -->
 
<!-- List 2100UTC meeting items below here -->
* CPython parse_request bug
+
* Utils refactor - expect merge conflicts!
** https://github.com/python/cpython/issues/99220 | BaseHTTPRequestHandler.parse_request() loses client-provided information
+
** https://review.opendev.org/c/openstack/swift/+/914029
*** Still no response :-/
+
* Probe test time outs
** Causing failures in our stable branches (eg, https://review.opendev.org/c/openstack/swift/+/861763)
+
** 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
** DSVM job is currently pinned to focal: https://review.opendev.org/c/openstack/swift/+/864946
+
** Some of these make sense -- some patchesets break every probe test and our retry-failed-tests logic causes the test time to essentially double
** https://review.opendev.org/c/openstack/swift/+/863441 | Preserve client-provided paths that start '//'
+
** Others just seem to hang for an hour or more
** https://review.opendev.org/c/openstack/swift/+/866801 | Inline parse_request from cpython
+
* liberasurecode release
* Testing under py310
+
** https://review.opendev.org/c/openstack/liberasurecode/+/917784
* ring v2
+
** Nothing major, but it's been a couple years
** https://review.opendev.org/c/openstack/swift/+/865066 | WIP: Rings as zipfiles
+
* pyeclib manylinux wheels
** https://review.opendev.org/c/openstack/swift/+/866082 | Add swift-ring-packer utility
+
** https://review.opendev.org/c/openstack/pyeclib/+/817498 - Add Dockerfile to build manylinux wheels
<!--
+
** https://review.opendev.org/c/openstack/pyeclib/+/917857 - Add job to build wheels
** assorted other patches that seemed related to the investigation -- are they still relevant? please abandon if not
+
* expirer work
*** https://review.opendev.org/c/openstack/swift/+/849453 - container: broaden is_deleted method by using empty
+
** https://review.opendev.org/c/openstack/swift/+/914713 - expirer: new options to control task iteration
*** https://review.opendev.org/c/openstack/swift/+/848930 - Remove :memory: from DatabaseBrokers and unittests
+
** https://review.opendev.org/c/openstack/swift/+/916026 - distributed parallel task container iteration
*** https://review.opendev.org/c/openstack/swift/+/848962 - ContainerBroker: modify determination of object_count
+
** https://review.opendev.org/c/openstack/swift/+/912496 - add bytes of expiring objects to queue entry
*** https://review.opendev.org/c/openstack/swift/+/848909 - Make in-memory databases worse
+
* broker row insertion order py2/py3 behavior difference
*** https://review.opendev.org/c/openstack/swift/+/844553 - sharding: shard deleted containers that have shards with objects
+
* unreleased swiftclient regression
-->
+
** https://review.opendev.org/c/openstack/python-swiftclient/+/916135
 
<!-- End 2100UTC meeting items -->
 
<!-- End 2100UTC meeting items -->
 
|}
 
|}
Line 35: Line 35:
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
| '''Meeting Logs''' || http://eavesdrop.openstack.org/meetings/swift/2022/
+
| '''Meeting Logs''' || http://eavesdrop.openstack.org/meetings/swift/2024/
 
|-
 
|-
 
|'''Useful Commands'''|| #link #info #agreed #topic and #startmeeting
 
|'''Useful Commands'''|| #link #info #agreed #topic and #startmeeting

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.