Difference between revisions of "Meetings/Swift"

Revision as of 17:13, 31 July 2020

2100 UTC Meeting
Next meeting: Aug 12, 2020
Chair: timburke
Py3 crypto bug and upgrades https://review.opendev.org/742033 - py3: Work with proper native string paths in crypto meta Shrinking and overlapping shard ranges https://review.opendev.org/#/c/722570/ - Matt's patch https://review.opendev.org/#/c/738149/ - Tim's patch https://review.opendev.org/#/c/741721/ - Clay's patch

Meeting Logs	http://eavesdrop.openstack.org/meetings/swift/2020/
Useful Commands	#link #info #agreed #topic and #startmeeting

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

@@ Line 3: / Line 3: @@
 ! '''2100 UTC Meeting'''
 |-
-| '''Next meeting:''' Jun 17, 2020
+| '''Next meeting:''' Aug 12, 2020
 |-
 | '''Chair:''' timburke
@@ Line 9: / Line 9: @@
 |
 <!-- List 2100UTC meeting items below here -->
-* Gate status
+* Py3 crypto bug and upgrades
-** uWSGI/grenade breakage
+** https://review.opendev.org/742033 - py3: Work with proper native string paths in crypto meta
-*** http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015432.html
+* Shrinking and overlapping shard ranges
-** pip/probe tests breakage
+** https://review.opendev.org/#/c/722570/ - Matt's patch
-*** http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015425.html
+** https://review.opendev.org/#/c/738149/ - Tim's patch
-*** https://review.opendev.org/#/c/735992
+** https://review.opendev.org/#/c/741721/ - Clay's patch
-* Memcache and container failures
-** https://bugs.launchpad.net/swift/+bug/1883211
-** https://review.opendev.org/#/c/735359/
-* Background daemons and replication servers
-** https://launchpad.net/bugs/1883302 - sharder sends ranges over same network used for client-facing requests
-** https://review.opendev.org/#/c/735751/ - fix just sharder sending ranges
-** https://review.opendev.org/#/c/735991/ - make it configurable via header in direct/internal client (keeping current behavior as default)
-** can/should we change the default behavior to prefer replication network? what other utilities have people written using these clients? would client or replication network be more appropriate?
-* Updates
-** Waterfall EC (clayg)
-*** https://review.opendev.org/#/c/733911/ - split EC / replicated
-*** https://review.opendev.org/#/c/711342/ - concurrent frag fetcher
-** LOSF updates (alecuyer, rledisez)
-*** https://wiki.openstack.org/wiki/Swift/ideas/small_files/implementation#LOSF_v2
 <!--
 ** jerasure support in libec