0b1afb48e5
To be able to support multiple Ceph cluster, an initial step is to allow for configuration of each cluster name. Depends-On: I8d5293eaaf104b6374dfa13992a67ddc37397f10 Implements: blueprint custom-ceph-cluster-name Change-Id: I1b4d51ca6a2d08fa7a68eea680eb104eff732057
23 lines
1.1 KiB
YAML
23 lines
1.1 KiB
YAML
# A Heat environment file which can be used to enable a
|
|
# a Manila CephFS-NFS driver backend.
|
|
resource_registry:
|
|
OS::TripleO::Services::ManilaApi: ../docker/services/manila-api.yaml
|
|
OS::TripleO::Services::ManilaScheduler: ../docker/services/manila-scheduler.yaml
|
|
# Only manila-share is pacemaker managed:
|
|
OS::TripleO::Services::ManilaShare: ../docker/services/pacemaker/manila-share.yaml
|
|
OS::TripleO::Services::ManilaBackendCephFs: ../puppet/services/manila-backend-cephfs.yaml
|
|
# ceph-nfs (ganesha) service is installed and configured by ceph-ansible
|
|
# but it's still managed by pacemaker
|
|
OS::TripleO::Services::CephNfs: ../docker/services/ceph-ansible/ceph-nfs.yaml
|
|
|
|
|
|
parameter_defaults:
|
|
ManilaCephFSBackendName: cephfs
|
|
ManilaCephFSDriverHandlesShareServers: false
|
|
ManilaCephFSCephFSAuthId: 'manila'
|
|
ManilaCephFSCephFSEnableSnapshots: false
|
|
# 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: 'NFS'
|