Difference between revisions of "Meetings/Swift"
< Meetings
| Line 25: | Line 25: | ||
*** need to be on the etherpad this week! | *** need to be on the etherpad this week! | ||
* Agnostic implementation for "object store" (a.k.a. diskfile) (alecuyer) | * Agnostic implementation for "object store" (a.k.a. diskfile) (alecuyer) | ||
| − | ** | + | ** Etherpad link : https://etherpad.openstack.org/p/swift-losf-base |
** Goal: having an agnostic interface for DiskFileManager | ** Goal: having an agnostic interface for DiskFileManager | ||
*** eg: _get_hashes(self, partition_path, ...) => _get_hashes(self, device, policy, partition, ...) | *** eg: _get_hashes(self, partition_path, ...) => _get_hashes(self, device, policy, partition, ...) | ||
Revision as of 17:27, 22 March 2017
| Meeting Time | Every Wednesday at 21:00 UTC in #openstack-meeting |
| Meeting Logs | http://eavesdrop.openstack.org/meetings/swift/2017/ |
| Chair | notmyname |
Next meeting: March 22, 2017 2100 UTC
- Follow-up from last week
- object server tests scratch pad: done! https://etherpad.openstack.org/p/swift-object-server-tests
- Undelete accounts patch, needs eyes from a "new API" perspective. https://review.openstack.org/#/c/445160/
- https://review.openstack.org/#/c/444604/ closes critical bug https://bugs.launchpad.net/swift/+bug/1657246
- done! (but notmyname will backport)
- Composite rings - how best to expose composite ring building as CLI?
- FYI stuff
- nightly gate stable branch failures [timburke]
- assert:never-breaks-compat TC resolution
- https://review.openstack.org/#/c/446561/
- do we want to assert this for Swift?
- Boston Forum topics https://etherpad.openstack.org/p/BOS-Swift-brainstorming
- need to be on the etherpad this week!
- Agnostic implementation for "object store" (a.k.a. diskfile) (alecuyer)
- Etherpad link : https://etherpad.openstack.org/p/swift-losf-base
- Goal: having an agnostic interface for DiskFileManager
- eg: _get_hashes(self, partition_path, ...) => _get_hashes(self, device, policy, partition, ...)
- 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
- Idea: call your patches
- 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.
