tripleo-heat-templates/environments/manila-cephfsnative-config.yaml
Dan Prince 4a9f2ac052 Move Manila backends into deployment
Change-Id: I6d500a3d7a1d24c13649734bc99707c37e133c2b
Related-Blueprint: services-yaml-flattening
2019-04-22 08:44:39 -04:00

21 lines
1019 B
YAML

# A Heat environment file which can be used to enable a
# a Manila CephFS Native driver backend.
resource_registry:
OS::TripleO::Services::ManilaApi: ../deployment/manila/manila-api-container-puppet.yaml
OS::TripleO::Services::ManilaScheduler: ../deployment/manila/manila-scheduler-container-puppet.yaml
# Only manila-share is pacemaker managed:
OS::TripleO::Services::ManilaShare: ../deployment/manila/manila-share-pacemaker-puppet.yaml
OS::TripleO::Services::ManilaBackendCephFs: ../deployment/manila/manila-backend-cephfs.yaml
parameter_defaults:
ManilaCephFSBackendName: cephfs
ManilaCephFSDriverHandlesShareServers: false
ManilaCephFSCephFSAuthId: 'manila'
ManilaCephFSCephFSEnableSnapshots: false
ManilaCephFSCephVolumeMode: '0755'
# manila cephfs driver supports either native cephfs backend - 'CEPHFS'
# (users mount shares directly from ceph cluster), or nfs-ganesha backend -
# 'NFS' (users mount shares through nfs-ganesha server)
ManilaCephFSCephFSProtocolHelperType: 'CEPHFS'