tripleo-image-elements

History

Jenkins 6d63227f20 Merge "Place swift-servers in appropriate zones"		2014-04-29 10:31:03 +00:00
..
environment.d	Wire in _EXTRA_INSTALL_OPTS...	2014-04-19 08:08:45 -04:00
install.d	Merge "Add swift-get-nodes, swift-recon and swift-recon-cron"	2014-04-25 10:13:22 +00:00
os-config-applier/etc/swift	Update swift element to install from source	2013-11-18 13:23:25 +00:00
os-refresh-config/configure.d	Place swift-servers in appropriate zones	2014-04-16 16:40:59 +01:00
README.md	Place swift-servers in appropriate zones	2014-04-16 16:40:59 +01:00
element-deps	Create pip manifest files of installed packages	2014-03-25 12:22:59 +00: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