forked from rook/rook
The activeStandby property was being ignored when deciding how many mds daemons to start. 2x the active count of mds daemons were always being created. If the standby is not desired, the standby can be removed, and it was unexpected that it was not removed. Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
28 lines
1.2 KiB
YAML
28 lines
1.2 KiB
YAML
---
|
|
apiVersion: ceph.rook.io/v1
|
|
kind: CephFilesystemSubVolumeGroup
|
|
metadata:
|
|
name: group-a
|
|
namespace: rook-ceph # namespace:cluster
|
|
spec:
|
|
# The name of the subvolume group. If not set, the default is the name of the subvolumeGroup CR.
|
|
# name: group-a
|
|
# filesystemName is the metadata name of the CephFilesystem CR where the subvolume group will be created
|
|
filesystemName: myfs
|
|
# reference https://docs.ceph.com/en/latest/cephfs/fs-volumes/#pinning-subvolumes-and-subvolume-groups
|
|
# only one out of (export, distributed, random) can be set at a time
|
|
# by default pinning is set with value: distributed=1
|
|
# for disabling default values set (distributed=0)
|
|
pinning:
|
|
distributed: 1 # distributed=<0, 1> (disabled=0)
|
|
# export: # export=<0-256> (disabled=-1)
|
|
# random: # random=[0.0, 1.0](disabled=0.0)
|
|
# Quota size of the subvolume group.
|
|
#quota: 10G
|
|
# data pool name for the subvolume group layout instead of the default data pool.
|
|
#dataPoolName: myfs-replicated
|
|
# ClusterID to be used for this subvolume group in the CSI configuration.
|
|
# It must be unique among all Ceph clusters managed by Rook.
|
|
# If not specified, the clusterID will be generated and can be found in the CR status.
|
|
# clusterID: group-a
|