Jump to: navigation, search

Difference between revisions of "Meetings/Swift"

(761 intermediate revisions by 33 users not shown)
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/2015/
+
|-
 +
! '''2100 UTC Meeting'''
 +
|-
 +
| '''Next meeting:''' May 1, 2024
 +
|-
 +
| '''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: July 15, 2015 2100 UTC'''
+
{| class="wikitable"
 +
|-
 +
| '''Meeting Logs''' || http://eavesdrop.openstack.org/meetings/swift/2024/
 +
|-
 +
|'''Useful Commands'''|| #link #info #agreed #topic and #startmeeting
 +
|}
 +
 
 +
* PTG action items
 +
** (timburke) interop feedback on https://review.opendev.org/c/openinfra/interop/+/811049/
 +
** better defaults (or at least, use better defaults in install/deployment guides)
 +
*** (mattoliverau) recommend servers-per-port
 +
*** (mattoliverau) make etherpad to collect more defaults that need updating
 +
*** Etherpad: https://etherpad.opendev.org/p/swift-better-defaults
 +
** (acoles) dark data audit watcher patch: https://review.opendev.org/c/openstack/swift/+/787656
 +
** (timburke) abandon old patches
 +
** (mattoliverau) bug triage/squash
 +
*** Etherpad: https://etherpad.opendev.org/p/swift-bug-triage-a-thon
 +
*** Ethercalc: https://ethercalc.openstack.org/mf3yro7018m0
 +
** (acoles) drop logging translations - https://bugs.launchpad.net/swift/+bug/1674543
 +
** (timburke) look into how to translate docs so seongsoocho can propose Korean translations
 +
** check continued usefulness of the ops runbook
 +
** consolidate various admin guides
 +
** write a "why swift?" doc(/README?) section
  
* Hackathon reminder (https://www.eventbrite.com/e/swift-hackathon-tickets-17308818141)
 
* swiftclient release [notmyname]
 
* Python3 work: https://review.openstack.org/#/q/status:open+project:openstack/swift+branch:master+topic:py3,n,z
 
** Option 1: Do what we're currently doing. big patches, hard to review, little immediate payoff
 
** Option 2: Patch one module at a time and blacklist non-ported modules in the gate jobs. smaller pieces of work, measurable progress, still will take a while
 
** Option 3: Freeze the world, port everything, done. painful up front, but done all at once
 
* updates from ongoing work
 
** encryption, EC work, hummingbird?
 
** notification middleware [cschwede]
 
* Hot Bugs [notmyname]
 
** EC bugs
 
*** https://bugs.launchpad.net/swift/+bugs?field.tag=ec  (needs triage)
 
** swiftclient bugs
 
*** https://goo.gl/uO4b7l ("new" bugs that need to be looked at)
 
* Specs that are open and should land? [notmyname]
 
** https://review.openstack.org/#/q/status:open+project:openstack/swift-specs,n,z
 
* Container Sync performance. [eranrom]
 
** short deck on the what and why: http://www.slideshare.net/DmitrySotnikov1/container-sync-performanceimprovement
 
** code reference illustrating the approach (should be broken to smaller patches based on master, imho, more readable this way...): https://github.com/eranrom/swift-thoughts/blob/master/container-sync/sync.py
 
** Addressing existing bugs:
 
*** https://bugs.launchpad.net/swift/+bug/1277223
 
*** https://bugs.launchpad.net/swift/+bug/1068426
 
** Suggested patch breakdown
 
*** patch 1: split ContainerSync to two classes : (1) manager class that iterates over dbs and assigns each db to a different process (2) a sync class that does the sync work on over a db
 
*** patch 2: Introduce the process pool, and the SyncStats class that collects stats from all processes allowing the existing one aggregated report.
 
*** patch 3: Add thread pool to the db sync process
 
*** patch 4: Add the head command to the phase where the pointers are not equal, greatly mitigating the problem where each object is sent 4 times.
 
 
----
 
----
  
 
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]]

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.