openstack/tripleo-image-elements
Code Issues Proposed changes
f9dc34aadb
tripleo-image-elements/elements/swift
History
Jenkins 4ca9b799f2 Merge "Fix swift object-server cffi version mismatch bug"
2014-09-27 04:28:54 +00:00
..
environment.d Wire in _EXTRA_INSTALL_OPTS... 2014-04-19 08:08:45 -04:00
install.d Fix swift object-server cffi version mismatch bug 2014-09-21 22:13:32 +01:00
os-apply-config/etc/swift Add passthrough to etc/swift.conf 2014-07-25 13:00:09 +01:00
os-refresh-config/configure.d Merge "Allow swift "min_part_hours" to be configurable" 2014-09-12 08:54:21 +00:00
element-deps Correct SELinux file contexts 2014-07-19 23:54:41 -07:00
README.md Place swift-servers in appropriate zones 2014-04-16 16:40:59 +01:00
source-repository-swift Don't use /cgit/ urls for git. 2014-02-21 15:25:12 +13:00

README.md

Common element for swift elements

Configuration

swift: devices: r1z-192.0.2.6:%PORT%/d1 - A comma separated list of swift storage devices to place in the ring file. - This MUST be present in order for o-r-c to successfully complete. zones: - Servers are divided amongst separate zones if the swift.zones metadata is greater than the default of 1. Servers are placed in zones depending on their rank in the scaled-out list of Swift servers in the yaml template used to build the overcloud stack. The scaleout rank N is: SwiftStorage|controller. The appropriate zone is calculated as: zone = N % swift.zones + 1. - To enable this calculation, the devices data takes the form of: r1z%%-192.0.2.6:%PORT%/d1 hash: randomstring - A hash used to salt paths on storage hosts