Difference between revisions of "Meetings/Swift"

Revision as of 02:00, 20 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/ Another shift in formats; discussions in the mornings, working sessions in the afternoons Early bird prices are $299, not sure when price increases may happen Foundation wants an attendance estimate by March 2 Object GET timings, EC, and concurrent GETs

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 Wednesday at 21:00 UTC in #openstack-meeting
+{| class="wikitable"
-Meeting Logs: http://eavesdrop.openstack.org/meetings/swift/2016/
+|-
-Meeting Chair: notmyname
+! '''2100 UTC Meeting'''
+|-
+| '''Next meeting:''' February 26, 2020
+|-
+| '''Chair:''' timburke
+|-
+|
+<!-- List 2100UTC meeting items below here -->
-'''Agenda: January 13, 2016 2100 UTC'''
+* Vancouver PTG (June 8-11)
+** https://www.openstack.org/events/opendev-ptg-2020/
+** Another shift in formats; discussions in the mornings, working sessions in the afternoons
+** Early bird prices are $299, not sure when price increases may happen
+** Foundation wants an attendance estimate by March 2
+* Object GET timings, EC, and concurrent GETs
-* Patches
+<!-- End 2100UTC meeting items -->
-** Change schedule priority of daemon/server in config - https://review.openstack.org/#/c/238799/ [peterlisak? onovy?]
+|}
-*** 2 big questions in the review comments
-**** Should we even be doing this in Swift itself instead of distro init scripts. On the one hand, the ionice priority "code" has to be rewritten for every distro. On the other, ops know ionice and how/when to use it and does that actually belong in Swift? If it does, why not other ops/management tools?
-**** Does setting ionice actually improve anything? Swift's processes are rather interconnected, so it's very difficult to isolate a logical API operation by process. eg nice'ing the container server would impact object PUTs since the container is updated as part of the object write.
-** Make object-auditor storage-policy-aware - https://review.openstack.org/#/c/266599/ [notmyname]
-*** critical bug that needs to be closed for a release
-* What's going on? [notmyname]
-** https://gist.github.com/notmyname/be49b04165928fd6662f
+{| class="wikitable"
+|-
+| '''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.
 ----
 [[Category:ObjectStorage]]