~charmers/charms/precise/mongodb/trunk

Viewing changes to config.yaml

Committer: Stuart Bishop
Date: 2014-07-29 10:22:55 UTC
mfrom: (47.1.1 mongodb)
Revision ID: stuart@stuartbishop.net-20140729102255-ilig6wgm8wxyop54

[wesmason] Storage subordinate support for persistent storage, per https://code.launchpad.net/~wesmason/charms/precise/mongodb/add-storage-subordinate-support/+merge/223539

files added:
hooks/data-relation-changed

hooks/data-relation-departed

hooks/data-relation-joined

files modified:
README.md

config.yaml

hooks/hooks.py

metadata.yaml

Show diffs side-by-side

added added

removed removed

config.yaml

168

type: int

169

description: "Number of backups to keep. Keeps one week's worth by default."

170

#------------------------------------------------------------------------

171

# Volume management

171

# Legacy volume management (DEPRECATED)

172

# volume-map, volume-dev_regexp are only used

173

# if volume-ephemeral-storage == False

174

#------------------------------------------------------------------------

176

type: boolean

177

default: true

178

description: >

179

Deprecated, use the storage subordinate.

179

180

If false, a configure-error state will be raised if

180

181

volume-map[$JUJU_UNIT_NAME] is not set (see "volume-map"

181

182

below) - see "volume-map" below.

187

188

type: string

188

189

default: ""

189

190

description: >

191

Deprecated, use the storage subordinate.

190

192

YAML map as e.g. "{ mongodb/0: vol-0000010, mongodb/1: vol-0000016 }".

191

193

Service units will raise a "configure-error" condition if no volume-map

192

194

value is set for it - it expects a human to set it properly to resolve it.

194

196

type: string

195

197

default: "/dev/vd[b-z]"

196

198

description: >

199

Deprecated, use the storage subordinate.

197

200

Block device for attached volumes as seen by the VM, will be "scanned"

198

201

for an unused device when "volume-map" is valid for the unit.

199

202

source:

Older »