Jump to: navigation, search

Difference between revisions of "Meetings/Swift"

(+tests result for ionice)
 
(668 intermediate revisions by 26 users not shown)
Line 1: Line 1:
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
| '''Meeting Time''' || Every Wednesday at 21:00 UTC in #openstack-meeting
+
! '''2100 UTC Meeting'''
 
|-
 
|-
| '''Meeting Logs''' || http://eavesdrop.openstack.org/meetings/swift/2016/
+
| '''Next meeting:''' May 1, 2024
 
|-
 
|-
| '''Chair''' || notmyname
+
| '''Location:''' #openstack-swift on OFTC
 +
|-
 +
| '''Chair:''' timburke
 +
|-
 +
|
 +
<!-- List 2100UTC meeting items below here -->
 +
* Utils refactor - expect merge conflicts!
 +
** https://review.opendev.org/c/openstack/swift/+/914029
 +
* Probe test time outs
 +
** 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
 +
** Some of these make sense -- some patchesets break every probe test and our retry-failed-tests logic causes the test time to essentially double
 +
** Others just seem to hang for an hour or more
 +
* liberasurecode release
 +
** https://review.opendev.org/c/openstack/liberasurecode/+/917784
 +
** Nothing major, but it's been a couple years
 +
* pyeclib manylinux wheels
 +
** 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
 +
* expirer work
 +
** https://review.opendev.org/c/openstack/swift/+/914713 - expirer: new options to control task iteration
 +
** https://review.opendev.org/c/openstack/swift/+/916026 - distributed parallel task container iteration
 +
** https://review.opendev.org/c/openstack/swift/+/912496 - add bytes of expiring objects to queue entry
 +
* broker row insertion order py2/py3 behavior difference
 +
* unreleased swiftclient regression
 +
** https://review.opendev.org/c/openstack/python-swiftclient/+/916135
 +
<!-- End 2100UTC meeting items -->
 
|}
 
|}
  
'''Agenda: January 20, 2016 2100 UTC'''
+
{| class="wikitable"
 +
|-
 +
| '''Meeting Logs''' || http://eavesdrop.openstack.org/meetings/swift/2024/
 +
|-
 +
|'''Useful Commands'''|| #link #info #agreed #topic and #startmeeting
 +
|}
  
* Swift release [notmyname]
+
* PTG action items
** Update eventlet https://review.openstack.org/#/c/269811/
+
** (timburke) interop feedback on https://review.opendev.org/c/openinfra/interop/+/811049/
* Hackathon [notmyname]
+
** better defaults (or at least, use better defaults in install/deployment guides)
 
+
*** (mattoliverau) recommend servers-per-port
* Patches
+
*** (mattoliverau) make etherpad to collect more defaults that need updating
** Change schedule priority of daemon/server in config - https://review.openstack.org/#/c/238799/ [peterlisak? onovy?]
+
*** Etherpad: https://etherpad.opendev.org/p/swift-better-defaults
*** 2 big questions in the review comments
+
** (acoles) dark data audit watcher patch: https://review.opendev.org/c/openstack/swift/+/787656
**** 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.
+
** (timburke) abandon old patches
**** 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?
+
** (mattoliverau) bug triage/squash
**** [https://docs.google.com/spreadsheets/d/1dzcMutNwRYcDiSMNOhKLM1tk8QX3uqFg9BJszJ6plr4/edit?usp=sharing Real tests result]
+
*** Etherpad: https://etherpad.opendev.org/p/swift-bug-triage-a-thon
** Auditor Watchers patches [Zyric]
+
*** Ethercalc: https://ethercalc.openstack.org/mf3yro7018m0
*** Object Auditor Watcher patch - https://review.openstack.org/#/c/212824/
+
** (acoles) drop logging translations - https://bugs.launchpad.net/swift/+bug/1674543
*** Account Auditors patch - https://review.openstack.org/#/c/268830/
+
** (timburke) look into how to translate docs so seongsoocho can propose Korean translations
** I would like to discuss about below patches with following summary - http://paste.openstack.org/show/484089/ [ho]
+
** check continued usefulness of the ops runbook
*** Fix posting accounts behavior when half of account servers downed - https://review.openstack.org/#/c/266190/
+
** consolidate various admin guides
*** Fix posting containers behavior when half of container servers downed - https://review.openstack.org/#/c/266193/
+
** write a "why swift?" doc(/README?) section
*** Fix deleting containers behavior when half of container servers downed - https://review.openstack.org/#/c/266199/
 
*** Fix 404 in container PUT when the majority of the accounts are missing
 
* Specs
 
** tempurls with a container-level scope - https://review.openstack.org/#/c/199607/ [cbartz]
 
  
 +
----
  
 
When adding an item, please include your IRC nickname with it.
 
When adding an item, please include your IRC nickname with it.
 
  
 
----
 
----
  
 
[[Category:ObjectStorage]]
 
[[Category:ObjectStorage]]

Latest 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.