Difference between revisions of "Swift/ideas"
< Swift
(→Ideas for OpenStack Swift) |
(→Ideas for OpenStack Swift) |
||
| Line 11: | Line 11: | ||
* better ring deployment inside of swift itself | * better ring deployment inside of swift itself | ||
* need internal net sec enforcement - https://blueprints.launchpad.net/swift/+spec/secure-internal-network-requests | * need internal net sec enforcement - https://blueprints.launchpad.net/swift/+spec/secure-internal-network-requests | ||
| + | * change the ssync (object-replicator) design to be run as another process for concurrency | ||
| + | * durability simulator based on swift specification (e.g. # of replicas, # of devices and network speed to replicate) | ||
Revision as of 04:50, 4 September 2014
Ideas for OpenStack Swift
- use keystone api in swift client, if possible
- in multinode install docs, show mounting with a label
- change default ports - https://review.openstack.org/#/c/118200/
- reverse listings
- stdin streaming to swiftclient
- reload swift config files when a change is detected (like current ring behavior) -- please don't do the auto-reload, I often edit them in-place (zaitcev)
- ring validator (in swift-recon): eg test that something is running on the ports in the ring -- not just "something", must verify correct type, because deployers sometimes flip a/c/o and then inexplicable 400 happens
- deep health check to test all the way to drives (? or at least storage servers)
- better ring deployment inside of swift itself
- need internal net sec enforcement - https://blueprints.launchpad.net/swift/+spec/secure-internal-network-requests
- change the ssync (object-replicator) design to be run as another process for concurrency
- durability simulator based on swift specification (e.g. # of replicas, # of devices and network speed to replicate)
