Go to file
Giulio Fidente cba222c72f Pass ceph::pool arguments when calling class
Pass the ceph::pool properties as arguments to the class call
instead of setting them as class defaults.

Ceph recommends max 32 PGs and min 4 PGs per OSD so this change
also lowers the defaults to 32 which works with 1 OSD, suits well
a scenario with 3 OSDs and is easy to customize in the static
hiera if more than 8 OSDs are deployed.

More info at: https://bugzilla.redhat.com/show_bug.cgi?id=1252546

Change-Id: Ifed11d1857900b2251dfdf69d6b6f168150e6330
2015-11-13 19:20:21 +01:00
2015-09-15 15:31:43 -05:00
2015-11-05 15:44:18 +01:00
2013-10-22 17:49:35 +01:00
2015-11-05 15:44:18 +01:00
2014-01-20 11:58:20 +01:00
2015-10-01 09:50:44 -04:00
2013-10-22 17:49:35 +01:00
2015-10-08 14:11:57 -04:00
2013-10-22 17:49:35 +01:00
2015-10-08 14:11:57 -04:00
2013-10-22 17:49:35 +01:00
2015-09-15 15:31:43 -05:00

tripleo-heat-templates

Heat templates to deploy OpenStack using OpenStack.

Features

The ability to deploy a multi-node, role based OpenStack deployment using OpenStack Heat. Notable features include:

  • Choice of deployment/configuration tooling: puppet, os-apply-config, and (soon) docker
  • Role based deployment: roles for the controller, compute, ceph, swift, and cinder storage
  • physical network configuration: support for isolated networks, bonding, and standard ctlplane networking

Directories

A description of the directory layout in TripleO Heat Templates.

  • deprecated: contains templates that have been deprecated
  • environments: contains heat environment files that can be used with -e

    on the command like to enable features, etc.

  • extraconfig: templates used to enable 'extra' functionality. Includes

    functionality for distro specific registration and upgrades.

  • firstboot: example first_boot scripts that can be used when initially

    creating instances.

  • network: heat templates to help create isolated networks and ports
  • puppet: templates mostly driven by configuration with puppet. To use these

    templates you can use the overcloud-resource-registry-puppet.yaml.

  • os-apply-config: templates mostly driven by configuration w/

    os-collect-config and bash based elements (which use the Heat os-apply-config group). These will soon be deprecated and are no longer part of the upstream CI testing efforts.

  • validation-scripts: validation scripts useful to all deployment

    configurations

Description
RETIRED, Heat templates for deploying OpenStack
Readme 322 MiB