Difference between revisions of "Meetings/Swift"

Revision as of 19:50, 26 February 2020

2100 UTC Meeting
Next meeting: February 26, 2020
Chair: timburke
Vancouver PTG (June 8-11) https://www.openstack.org/events/opendev-ptg-2020/ Object GET timings, EC, and concurrent GETs Should we add random delay when returning 503

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 1: / Line 1: @@
-Meeting Time: Every other Wednesday at 19:00 UTC
+{| class="wikitable"
+|-
+! '''2100 UTC Meeting'''
+|-
+| '''Next meeting:''' February 26, 2020
+|-
+| '''Chair:''' timburke
+|-
+|
+<!-- List 2100UTC meeting items below here -->
-Next Meeting: September 4, 2013
+* Vancouver PTG (June 8-11)
+** https://www.openstack.org/events/opendev-ptg-2020/
+* Object GET timings, EC, and concurrent GETs
+* Should we add random delay when returning 503
-Agenda:
+<!-- End 2100UTC meeting items -->
+|}
-  * I don't want swift to depend on swiftclient any more (torgomatic)
+{| class="wikitable"
+|-
+| '''Meeting Logs''' || http://eavesdrop.openstack.org/meetings/swift/2020/
+|-
+|'''Useful Commands'''|| #link #info #agreed #topic and #startmeeting
+|}
-Two parts here: first, move swift-bench out to its own repository, and second, make container-sync not depend on swiftclient. Then we can do crazy things in swiftclient like py3.3 compatibility, or new dependencies (like "six", which helps with py3 compatibility) without transitively doing crazy stuff in swift.
+----
+When adding an item, please include your IRC nickname with it.
+----
+[[Category:ObjectStorage]]