-
Bug
-
Resolution: Done
-
Blocker
-
OADP 1.2.0
-
False
-
-
False
-
oadp-volume-snapshot-mover-container-1.2.0-37, oadp-operator-container-1.2.0-47
-
ToDo
-
-
-
Critical
-
10
-
0
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
No
Description of problem:
Users will need to set appropriate source and destination volume options per storage class. The storage class name is not standard and openshift admins will have to provide the key/value mapping that appropriately matches the storage class name.
An example DPA.
apiVersion: oadp.openshift.io/v1alpha1 kind: DataProtectionApplication metadata: name: cephfs-dpa namespace: openshift-adp spec: features: dataMover: enable: true credentialName: <secret-name> cephfs: volumeOptions: sourceVolumeOptions: accessMode: ReadOnlyMany cacheAccessMode: ReadWriteMany moverSecurityContext: true destinationVolumeOptions: cacheAccessMode: ReadWriteOnce moverSecurityContext: true gp2-csi: volumeOptions: sourceVolumeOptions: cacheAccessMode: ReadWriteOnce destinationVolumeOptions: cacheAccessMode: ReadWriteOnce
This will allow OADP to appropriate create volumes and copy data per storage class.
This feature is needed only when the User wants to use a storage class other than the source volume storage class volume options.
- is related to
-
OADP-2074 [DataMover] Mirrored PVC snapcontent-*-pvc can have inconsistent storageclass from configmap options for volsync
- Closed
- links to
- mentioned on
(3 links to, 4 mentioned on)