Difference between revisions of "Swift/ideas"
< Swift
(→Ideas for OpenStack Swift: -1 on automatic config reload) |
(→Ideas for OpenStack Swift) |
||
| Line 6: | Line 6: | ||
* reverse listings | * reverse listings | ||
* stdin streaming to swiftclient | * stdin streaming to swiftclient | ||
| − | * reload swift config files when a change is detected (like current ring behavior) | + | * 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 | * ring validator (in swift-recon): eg test that something is running on the ports in the ring | ||
* deep health check to test all the way to drives (? or at least storage servers) | * deep health check to test all the way to drives (? or at least storage servers) | ||
* 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 | ||
Revision as of 21:21, 1 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
- 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
