Jump to: navigation, search

Difference between revisions of "Meetings/Swift"

 
(455 intermediate revisions by 19 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/2017/
+
| '''Next meeting:''' Sep 14th, 2022
 
|-
 
|-
| '''Chair''' || notmyname
+
| '''Location:''' #openstack-swift on OFTC
 +
|-
 +
| '''Chair:''' timburke
 +
|-
 +
|
 +
<!-- List 2100UTC meeting items below here -->
 +
* OpenStack Antelope
 +
* October vPTG
 +
** PTG switched back to all-virtual: https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029879.html
 +
** We (apparently) are signed up: https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030225.html
 +
** Need to reserve timeslots, make etherpad
 +
** Register at https://openinfra.dev/ptg/
 +
* Ring v2
 +
** https://review.opendev.org/c/openstack/swift/+/857234 - Add swift-ring-info utility
 +
** https://review.opendev.org/c/openstack/swift/+/857758 - proxy: Use last-primaries table
 +
<!--
 +
** assorted other patches that seemed related to the investigation -- are they still relevant? please abandon if not
 +
*** https://review.opendev.org/c/openstack/swift/+/849453 - container: broaden is_deleted method by using empty
 +
*** https://review.opendev.org/c/openstack/swift/+/848930 - Remove :memory: from DatabaseBrokers and unittests
 +
*** https://review.opendev.org/c/openstack/swift/+/848962 - ContainerBroker: modify determination of object_count
 +
*** https://review.opendev.org/c/openstack/swift/+/848909 - Make in-memory databases worse
 +
*** https://review.opendev.org/c/openstack/swift/+/844553 - sharding: shard deleted containers that have shards with objects
 +
-->
 +
<!-- End 2100UTC meeting items -->
 
|}
 
|}
  
'''Next meeting:''' March 22, 2017 2100 UTC
+
{| class="wikitable"
 +
|-
 +
| '''Meeting Logs''' || http://eavesdrop.openstack.org/meetings/swift/2022/
 +
|-
 +
|'''Useful Commands'''|| #link #info #agreed #topic and #startmeeting
 +
|}
  
* Follow-up from last week
+
* PTG action items
** object server tests scratch pad https://etherpad.openstack.org/p/swift-object-server-tests
+
** (timburke) interop feedback on https://review.opendev.org/c/openinfra/interop/+/811049/
** Undelete accounts patch, needs eyes from a "new API" perspective. https://review.openstack.org/#/c/445160/
+
** better defaults (or at least, use better defaults in install/deployment guides)
** https://review.openstack.org/#/c/444604/ closes critical bug https://bugs.launchpad.net/swift/+bug/1657246
+
*** (mattoliverau) recommend servers-per-port
** Composite rings - how best to expose composite ring building as CLI?
+
*** (mattoliverau) make etherpad to collect more defaults that need updating
*** etherpad https://etherpad.openstack.org/p/composite_rings
+
*** Etherpad: https://etherpad.opendev.org/p/swift-better-defaults
* Idea: call your patches
+
** (acoles) dark data audit watcher patch: https://review.opendev.org/c/openstack/swift/+/787656
* FYI stuff
+
** (timburke) abandon old patches
** nightly gate stable branch failures [timburke]
+
** (mattoliverau) bug triage/squash
** assert:never-breaks-compat TC resolution
+
*** Etherpad: https://etherpad.opendev.org/p/swift-bug-triage-a-thon
*** https://review.openstack.org/#/c/446561/
+
*** Ethercalc: https://ethercalc.openstack.org/mf3yro7018m0
*** do we want to assert this for Swift?
+
** (acoles) drop logging translations - https://bugs.launchpad.net/swift/+bug/1674543
* Agnostic implementation for "object store" (a.k.a. diskfile) (alecuyer)
+
** (timburke) look into how to translate docs so seongsoocho can propose Korean translations
** Patch: <url>
+
** check continued usefulness of the ops runbook
** Goal: having an agnostic interface for DiskFileManager
+
** consolidate various admin guides
*** eg: _get_hashes(self, partition_path, ...) => _get_hashes(self, device, policy, partition, ...)
+
** write a "why swift?" doc(/README?) section
** Goal is not to have a "supported" interface that must be stable. Goal is just to ease the implementation of non-filesystem based diskfile
 
** Naming idea: BaseObjectStoreManager -> provide an interface and very generic method
 
*** BaseDiskFileManager inherit from BaseObjectStoreManager
 
*** LOSF inherit from BaseObjectStoreManager
 
** Convert non-agnostic method from BaseDiskFileManager to agnostic method in BaseObjectStoreManager by replacing listdir(path) by list(device, policy, partition=None, sfx=None, ohash=None), list() would be implementation-specific
 
* Open Discussion
 
  
 
----
 
----
 
 
'''Notes left from earlier'''
 
 
* Things happening in Swift
 
** golang object server
 
** global ec
 
** composite rings
 
** policy migration
 
** policy auto tiering
 
** sync to elasticsearch
 
** container sharding
 
** symlinks
 
** increase part power
 
** container sharding
 
 
  
 
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:37, 14 September 2022

2100 UTC Meeting
Next meeting: Sep 14th, 2022
Location: #openstack-swift on OFTC
Chair: timburke
Meeting Logs http://eavesdrop.openstack.org/meetings/swift/2022/
Useful Commands #link #info #agreed #topic and #startmeeting

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