Allow a user to disable MongoDB journaling
authorYanis Guenane <yanis.guenane@enovance.com>
Mon, 13 Jul 2015 07:12:51 +0000 (09:12 +0200)
committerYanis Guenane <yguenane@redhat.com>
Mon, 13 Jul 2015 08:29:38 +0000 (10:29 +0200)
commite0ed4b315a5e12703a1e1dfc538863425e6ab81e
tree74ae70984e81c2c220e67b540f2a044c83834d4f
parentb7400f95a4c185c6c1b3294c11af828d799939d0
Allow a user to disable MongoDB journaling

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
controller.yaml
environments/mongodb-nojournal.yaml [new file with mode: 0644]
overcloud-without-mergepy.yaml
puppet/controller-puppet.yaml
puppet/hieradata/controller.yaml