e0ed4b315a
By default MongoDB enables a journaling system that prevents loss of data in case of an unexpected shut-down. When journaling is enabled, MongoDB will create the journal files before actually starting the daemon[1]. The journaling feature is useful in production environment, but not really on a CI-like system, where we only want to make sure MongoDB is setup correctly and running, hence here we allow a user to enable/disable MongoDB journaling. [1] http://docs.mongodb.org/manual/core/journaling/ Change-Id: I0e4e65af9f650c10fdf5155ff709b4eb984cf4e1 Closes-bug: #1468246 |
||
|---|---|---|
| .. | ||
| README.md | ||
| cinder-netapp-config.yaml | ||
| mongodb-nojournal.yaml | ||
| net-bond-with-vlans.yaml | ||
| net-single-nic-with-vlans.yaml | ||
| network-isolation.yaml | ||
| overcloud-steps.yaml | ||
| puppet-ceph-devel.yaml | ||
| puppet-pacemaker.yaml | ||
| puppet-tenant-vlan.yaml | ||
README.md
This directory contains Heat environment file snippets which can be used to enable features in the Overcloud.
Configuration
These can be enabled using the -e [path to environment yaml] option with heatclient.
Below is an example of how to enable the Ceph template using devtest_overcloud.sh:
export OVERCLOUD\_CUSTOM\_HEAT\_ENV=$TRIPLEO\_ROOT/tripleo-heat-templates/environments/ceph_devel.yaml