diff options
| author |   Yanis Guenane <yanis.guenane@enovance.com> | 2015-07-13 09:12:51 +0200 |
|---|---|---|
| committer |   Yanis Guenane <yguenane@redhat.com> | 2015-07-13 10:29:38 +0200 |
| commit | e0ed4b315a5e12703a1e1dfc538863425e6ab81e (patch) | |
| tree | 74ae70984e81c2c220e67b540f2a044c83834d4f /overcloud-without-mergepy.yaml | |
| parent | b7400f95a4c185c6c1b3294c11af828d799939d0 (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 'overcloud-without-mergepy.yaml')
| -rw-r--r-- | overcloud-without-mergepy.yaml | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/overcloud-without-mergepy.yaml b/overcloud-without-mergepy.yaml index 4258fe0d..88002381 100644 --- a/overcloud-without-mergepy.yaml +++ b/overcloud-without-mergepy.yaml @@ -174,6 +174,10 @@ parameters: NtpServer: type: string default: '' + MongoDbNoJournal: + default: false + description: Should MongoDb journaling be disabled + type: boolean PublicVirtualFixedIPs: default: [] description: > @@ -757,6 +761,7 @@ resources: NeutronTunnelTypes: {get_param: NeutronTunnelTypes} NovaPassword: {get_param: NovaPassword} NtpServer: {get_param: NtpServer} + MongoDbNoJournal: {get_param: MongoDbNoJournal} PcsdPassword: {get_resource: PcsdPassword} PublicVirtualInterface: {get_param: PublicVirtualInterface} RabbitPassword: {get_param: RabbitPassword} |