You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
= Setting a default cloning strategy by using a storage profile
8
+
9
+
You can use storage profiles to set a default cloning method for a storage class by creating a cloning strategy. Setting cloning strategies can be helpful, for example, if your storage vendor supports only certain cloning methods. It also allows you to select a method that limits resource usage or maximizes performance.
10
+
11
+
Cloning strategies are specified by setting the `cloneStrategy` attribute in a storage profile to one of the following values:
12
+
13
+
* `snapshot` is used by default when snapshots are configured. The Containerized Data Importer (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.
14
+
* `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.
15
+
* `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.
16
+
17
+
[NOTE]
18
+
====
19
+
You can set clone strategies using the CLI without modifying the default `claimPropertySets` in your YAML `spec` section.
= Specifying a volume snapshot class by using the CLI
8
+
9
+
If you are creating a snapshot of a VM, a warning appears if the storage class of the disk has more than one volume snapshot class associated with it. In this case, you must specify one volume snapshot class; otherwise, any disk that has more than one volume snapshot class is excluded from the snapshots list.
10
+
11
+
You can select which volume snapshot class to use by either:
12
+
13
+
* Setting the `spec.snapshotClass` for the storage profile.
14
+
* Setting a default volume snapshot class.
15
+
16
+
.Procedure
17
+
18
+
* Set the `VolumeSnapshotClass` you want to use. For example:
= Specifying a volume snapshot class by using the web console
8
+
9
+
If you are creating a snapshot of a VM, a warning appears if the storage class of the disk has more than one volume snapshot class associated with it. In this case, you must specify one volume snapshot class; otherwise, any disk that has more than one volume snapshot class is excluded from the snapshots list.
10
+
11
+
You can specify the default volume snapshot class in the {product-title} web console.
12
+
13
+
.Procedure
14
+
15
+
. From the *Virtualization* focused view, select *Storage*.
16
+
. Click *VolumeSnapshotClasses*.
17
+
. Select a volume snapshot class from the list.
18
+
. Click the *Annotations* pencil icon.
19
+
. Enter the following *Key*: `snapshot.storage.kubernetes.io/is-default-class`.
Copy file name to clipboardExpand all lines: modules/virt-customizing-storage-profile.adoc
+7-62Lines changed: 7 additions & 62 deletions
Original file line number
Diff line number
Diff line change
@@ -4,14 +4,15 @@
4
4
5
5
:_mod-docs-content-type: PROCEDURE
6
6
[id="virt-customizing-storage-profile_{context}"]
7
-
8
7
= Customizing the storage profile
9
8
10
9
You can specify default parameters by editing the `StorageProfile` object for the provisioner's storage class. These default parameters only apply to the persistent volume claim (PVC) if they are not configured in the `DataVolume` object.
11
10
12
11
You cannot modify storage class parameters. To make changes, delete and re-create the storage class. You must then reapply any customizations that were previously made to the storage profile.
13
12
14
-
An empty `status` section in a storage profile indicates that a storage provisioner is not recognized by the Containerized Data Interface (CDI). Customizing a storage profile is necessary if you have a storage provisioner that is not recognized by CDI. In this case, the administrator sets appropriate values in the storage profile to ensure successful allocations.
13
+
An empty `status` section in a storage profile indicates that a storage provisioner is not recognized by the Containerized Data Importer (CDI). Customizing a storage profile is necessary if you have a storage provisioner that is not recognized by CDI. In this case, the administrator sets appropriate values in the storage profile to ensure successful allocations.
14
+
15
+
If you are creating a snapshot of a VM, a warning appears if the storage class of the disk has more than one `VolumeSnapshotClass` associated with it. In this case, you must specify one volume snapshot class; otherwise, any disk that has more than one volume snapshot class is excluded from the snapshots list.
15
16
16
17
[WARNING]
17
18
====
@@ -31,21 +32,7 @@ If you create a data volume and omit YAML attributes and these attributes are no
31
32
$ oc edit storageprofile <storage_class>
32
33
----
33
34
+
34
-
.Example storage profile
35
-
[source,yaml]
36
-
----
37
-
apiVersion: cdi.kubevirt.io/v1beta1
38
-
kind: StorageProfile
39
-
metadata:
40
-
name: <unknown_provisioner_class>
41
-
# ...
42
-
spec: {}
43
-
status:
44
-
provisioner: <unknown_provisioner>
45
-
storageClass: <unknown_provisioner_class>
46
-
----
47
-
+
48
-
. Provide the needed attribute values in the storage profile:
35
+
. Specify the `accessModes` and `volumeMode` values you want to configure for the storage profile. For example:
49
36
+
50
37
.Example storage profile
51
38
[source,yaml]
@@ -59,52 +46,10 @@ spec:
59
46
claimPropertySets:
60
47
- accessModes:
61
48
- ReadWriteOnce <1>
62
-
volumeMode:
63
-
Filesystem <2>
49
+
volumeMode: Filesystem <2>
64
50
status:
65
51
provisioner: <unknown_provisioner>
66
52
storageClass: <unknown_provisioner_class>
67
53
----
68
-
<1> The `accessModes` that you select.
69
-
<2> The `volumeMode` that you select.
70
-
+
71
-
After you save your changes, the selected values appear in the storage profile `status` element.
== Setting a default cloning strategy using a storage profile
75
-
76
-
You can use storage profiles to set a default cloning method for a storage class, creating a _cloning strategy_. Setting cloning strategies can be helpful, for example, if your storage vendor only supports certain cloning methods. It also allows you to select a method that limits resource usage or maximizes performance.
77
-
78
-
Cloning strategies can be specified by setting the `cloneStrategy` attribute in a storage profile to one of these values:
79
-
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.
81
-
* `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.
82
-
* `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.
83
-
84
-
[NOTE]
85
-
====
86
-
You can also set clone strategies using the CLI without modifying the default `claimPropertySets` in your YAML `spec` section.
0 commit comments