tripleo-image-elements

History

Michael Kerrin c5690f6553 Remove /opt/stack/{repo} files Reduce the size of the images and remove git information. Co-Authored-By: nicholas.randon@hp.com Co-Authored-By: michael.kerrin@hp.com Change-Id: I168fa2b1d36e6f9e0a281bc284be8bb24076e1a2		2015-02-03 09:50:31 +00:00
..
cleanup.d	Remove /opt/stack/{repo} files	2015-02-03 09:50:31 +00:00
environment.d	Wire in _EXTRA_INSTALL_OPTS...	2014-04-19 08:08:45 -04:00
install.d	Migrate to package-installs scripts	2014-11-05 01:38:05 -08: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	Don't rebuild swift rings if already exist	2014-12-10 12:18:31 +00:00
element-deps	Migrate to package-installs scripts	2014-11-05 01:38:05 -08:00
README.md	Properly format markdown code blocks	2014-11-12 10:31:01 +09: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<zone number>-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<N>.  The appropriate zone is calculated as:
        zone = N % swift.zones + 1.
      - To enable this calculation, the devices data takes the form of:
          r1z%<controller or SwiftStorage><N>%-192.0.2.6:%PORT%/d1
    hash: randomstring
      - A hash used to salt paths on storage hosts