summaryrefslogtreecommitdiffstats
path: root/environments
diff options
context:
space:
mode:
authorYanis Guenane <yanis.guenane@enovance.com>2015-07-13 09:12:51 +0200
committerYanis Guenane <yguenane@redhat.com>2015-07-13 10:29:38 +0200
commite0ed4b315a5e12703a1e1dfc538863425e6ab81e (patch)
tree74ae70984e81c2c220e67b540f2a044c83834d4f /environments
parentb7400f95a4c185c6c1b3294c11af828d799939d0 (diff)
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
Diffstat (limited to 'environments')
-rw-r--r--environments/mongodb-nojournal.yaml5
1 files changed, 5 insertions, 0 deletions
diff --git a/environments/mongodb-nojournal.yaml b/environments/mongodb-nojournal.yaml
new file mode 100644
index 00000000..1e13e452
--- /dev/null
+++ b/environments/mongodb-nojournal.yaml
@@ -0,0 +1,5 @@
+# A Heat environment file which can be used to disable journal in MongoDb.
+# Since, when journaling is enabled, MongoDb will create big journal file
+# it can take time. In a CI environment for example journaling is not necessary.
+parameters:
+ MongoDbNoJournal: true