tripleo-image-elements

History

Martin André 91c4996685 Properly format markdown code blocks The YAML configuration examples were being parsed as markdown, which resulted in poorly formatted documents. Also convert tempest element README file to markdown for consistency. Change-Id: Id6def1c8bcb86e37f10a74bf85361a9da0d151b6 Closes-Bug: 1328304		2014-11-12 10:31:01 +09: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	SELinux: Allow swift access to ephemeral ports	2014-09-29 18:54:36 -07:00
README.md	Properly format markdown code blocks	2014-11-12 10:31:01 +09:00
element-deps	Migrate to package-installs scripts	2014-11-05 01:38:05 -08: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