10.4.5. Bundle Storage Properties

A bundle may optionally contain one <storage> element. A <storage> element has no properties of its own, but may contain one or more <storage-mapping> elements.

Table 10.17. Properties of a Bundle’s Storage-Mapping Element

Field	Default	Description
`id`		A unique name for the storage mapping (required)
`source-dir`		The absolute path on the host’s filesystem that will be mapped into the container. Exactly one of `source-dir` and `source-dir-root` must be specified in a `storage-mapping`.
`source-dir-root`		The start of a path on the host’s filesystem that will be mapped into the container, using a different subdirectory on the host for each container instance. The subdirectory will be named the same as the bundle host name, as described in the note for `ip-range-start`. Exactly one of `source-dir` and `source-dir-root` must be specified in a `storage-mapping`.
`target-dir`		The path name within the container where the host storage will be mapped (required)
`options`		File system mount options to use when mapping the storage

Note

Pacemaker does not define the behavior if the source directory does not already exist on the host. However, it is expected that the container technology and/or its resource agent will create the source directory in that case.

Note

If the bundle contains a primitive, Pacemaker will automatically map the equivalent of source-dir=/etc/pacemaker/authkey target-dir=/etc/pacemaker/authkey and source-dir-root=/var/log/pacemaker/bundles target-dir=/var/log into the container, so it is not necessary to specify those paths in a storage-mapping.

Important

The PCMK_authkey_location environment variable must not be set to anything other than the default of /etc/pacemaker/authkey on any node in the cluster.