Skip to content

Commit 36cf850

Browse files
authored
Merge pull request #78757 from danielclowers/CNV-34493
CNV#34493: StorageProfile default behavior clarification
2 parents 96bde1d + ea99c8a commit 36cf850

File tree

2 files changed

+24
-3
lines changed

2 files changed

+24
-3
lines changed

modules/virt-customizing-storage-profile.adoc

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ You can use storage profiles to set a default cloning method for a storage class
7777

7878
Cloning strategies can be specified by setting the `cloneStrategy` attribute in a storage profile to one of these values:
7979

80-
* `snapshot` is used by default when snapshots are configured. This cloning strategy uses a temporary volume snapshot to clone the volume. The storage provisioner must support Container Storage Interface (CSI) snapshots.
80+
* `snapshot` is used by default when snapshots are configured. The CDI will use the snapshot method if it recognizes the storage provider and the provider supports Container Storage Interface (CSI) snapshots. This cloning strategy uses a temporary volume snapshot to clone the volume.
8181
* `copy` uses a source pod and a target pod to copy data from the source volume to the target volume. Host-assisted cloning is the least efficient method of cloning.
8282
* `csi-clone` uses the CSI clone API to efficiently clone an existing volume without using an interim volume snapshot. Unlike `snapshot` or `copy`, which are used by default if no storage profile is defined, CSI volume cloning is only used when you specify it in the `StorageProfile` object for the provisioner's storage class.
8383

@@ -108,3 +108,24 @@ status:
108108
<1> Specify the access mode.
109109
<2> Specify the volume mode.
110110
<3> Specify the default cloning strategy.
111+
112+
[id="virt-customizing-storage-profile-providers-and-default-behaviors_{context}"]
113+
.Storage providers and default behaviors
114+
115+
[cols="1,1",options="header"]
116+
|===
117+
|Storage provider|Default behavior
118+
|rook-ceph.rbd.csi.ceph.com|Snapshot
119+
|openshift-storage.rbd.csi.ceph.com|Snapshot
120+
|csi-vxflexos.dellemc.com|CSI Clone
121+
|csi-isilon.dellemc.com|CSI Clone
122+
|csi-powermax.dellemc.com|CSI Clone
123+
|csi-powerstore.dellemc.com|CSI Clone
124+
|hspc.csi.hitachi.com|CSI Clone
125+
|csi.hpe.com|CSI Clone
126+
|spectrumscale.csi.ibm.com|CSI Clone
127+
|rook-ceph.rbd.csi.ceph.com|CSI Clone
128+
|openshift-storage.rbd.csi.ceph.com|CSI Clone
129+
|cephfs.csi.ceph.com|CSI Clone
130+
|openshift-storage.cephfs.csi.ceph.com|CSI Clone
131+
|===

virt/storage/virt-configuring-storage-profile.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,9 @@ toc::[]
88

99
A storage profile provides recommended storage settings based on the associated storage class. A storage profile is allocated for each storage class.
1010

11-
If the Containerized Data Importer (CDI) does not recognize your storage provider, you must configure storage profiles.
11+
The Containerized Data Importer (CDI) recognizes a storage provider if it has been configured to identify and interact with the storage provider's capabilities.
1212

13-
For recognized storage types, CDI provides values that optimize the creation of PVCs. However, you can configure automatic settings for a storage class if you customize the storage profile.
13+
For recognized storage types, the CDI provides values that optimize the creation of PVCs. You can also configure automatic settings for the storage class by customizing the storage profile. If the CDI does not recognize your storage provider, you must configure storage profiles.
1414

1515
ifndef::openshift-rosa,openshift-dedicated[]
1616
[IMPORTANT]

0 commit comments

Comments
 (0)