feedc0de/my-rook-config
1
0
Fork 0
forked from rook/rook
Code Pull Requests Activity

Merge pull request #14586 from ShravaniVangur/updateStorageClass

Browse Source 
csi: storageclass update to gp2-csi
This commit is contained in:
Travis Nielsen
2024-08-20 07:33:19 -06:00
committed by GitHub
parent b1f2fcf4be 9656d1963a
commit 8a437be103
6 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Documentation/CRDs/Cluster/ceph-cluster-crd.md
+1 -1
View File
@@ -322,7 +322,7 @@ The following are the settings for Storage Class Device Sets which can be config
* `preparePlacement`: The placement criteria for the preparation of the OSD devices. Creating OSDs is a two-step process and the prepare job may require different placement than the OSD daemons. If the `preparePlacement` is not specified, the `placement` will instead be applied for consistent placement for the OSD prepare jobs and OSD deployments. The `preparePlacement` is only useful for `portable` OSDs in the device sets. OSDs that are not portable will be tied to the host where the OSD prepare job initially runs.
* For example, provisioning may require topology spread constraints across zones, but the OSD daemons may require constraints across hosts within the zones.
* `portable`: If `true`, the OSDs will be allowed to move between nodes during failover. This requires a storage class that supports portability (e.g. `aws-ebs`, but not the local storage provisioner). If `false`, the OSDs will be assigned to a node permanently. Rook will configure Ceph's CRUSH map to support the portability.
* `tuneDeviceClass`: For example, Ceph cannot detect AWS volumes as HDDs from the storage class "gp2", so you can improve Ceph performance by setting this to true.
* `tuneDeviceClass`: For example, Ceph cannot detect AWS volumes as HDDs from the storage class "gp2-csi", so you can improve Ceph performance by setting this to true.
* `tuneFastDeviceClass`: For example, Ceph cannot detect Azure disks as SSDs from the storage class "managed-premium", so you can improve Ceph performance by setting this to true..
* `volumeClaimTemplates`: A list of PVC templates to use for provisioning the underlying storage devices.
* `metadata.name`: "data", "metadata", or "wal". If a single template is provided, the name must be "data". If the name is "metadata" or "wal", the devices are used to store the Ceph metadata or WAL respectively. In both cases, the devices must be raw devices or LVM logical volumes.
Documentation/CRDs/Cluster/pvc-cluster.md
+4 -4
View File
@@ -8,7 +8,7 @@ in clusters where a local PV provisioner is available.
## AWS Storage Example
In this example, the mon and OSD volumes are provisioned from the AWS `gp2` storage class. This storage class can be replaced by any storage class that provides `file` mode (for mons) and `block` mode (for OSDs).
In this example, the mon and OSD volumes are provisioned from the AWS `gp2-csi` storage class. This storage class can be replaced by any storage class that provides `file` mode (for mons) and `block` mode (for OSDs).
```yaml
apiVersion: ceph.rook.io/v1
@@ -25,7 +25,7 @@ spec:
allowMultiplePerNode: false
volumeClaimTemplate:
spec:
storageClassName: gp2
storageClassName: gp2-csi
resources:
requests:
storage: 10Gi
@@ -42,8 +42,8 @@ spec:
resources:
requests:
storage: 10Gi
# IMPORTANT: Change the storage class depending on your environment (e.g. local-storage, gp2)
storageClassName: gp2
# IMPORTANT: Change the storage class depending on your environment (e.g. local-storage, gp2-csi)
storageClassName: gp2-csi
volumeMode: Block
accessModes:
- ReadWriteOnce
Documentation/Contributing/rook-test-framework.md
+1 -1
View File
@@ -95,7 +95,7 @@ go test -v -timeout 1800s -run CephSmokeSuite github.com/rook/rook/tests/integra
```console
export TEST_ENV_NAME=openshift
export TEST_STORAGE_CLASS=gp2
export TEST_STORAGE_CLASS=gp2-csi
export TEST_BASE_DIR=/tmp
```
deploy/examples/cluster-on-pvc.yaml
+3 -3
View File
@@ -28,7 +28,7 @@ spec:
# size appropriate for monitor data will be used.
volumeClaimTemplate:
spec:
storageClassName: gp2
storageClassName: gp2-csi
resources:
requests:
storage: 10Gi
@@ -64,7 +64,7 @@ spec:
portable: true
# Certain storage class in the Cloud are slow
# Rook can configure the OSD running on PVC to accommodate that by tuning some of the Ceph internal
# Currently, "gp2" has been identified as such
# Currently, "gp2-csi" has been identified as such
tuneDeviceClass: true
# Certain storage class in the Cloud are fast
# Rook can configure the OSD running on PVC to accommodate that by tuning some of the Ceph internal
@@ -132,7 +132,7 @@ spec:
requests:
storage: 10Gi
# IMPORTANT: Change the storage class depending on your environment
storageClassName: gp2
storageClassName: gp2-csi
volumeMode: Block
accessModes:
- ReadWriteOnce
deploy/examples/cluster-stretched-aws.yaml
+3 -3
View File
@@ -37,7 +37,7 @@ spec:
- name: us-east-2c
volumeClaimTemplate:
spec:
storageClassName: gp2
storageClassName: gp2-csi
resources:
requests:
storage: 10Gi
@@ -85,7 +85,7 @@ spec:
resources:
requests:
storage: 10Gi
storageClassName: gp2
storageClassName: gp2-csi
volumeMode: Block
accessModes:
- ReadWriteOnce
@@ -118,7 +118,7 @@ spec:
resources:
requests:
storage: 10Gi
storageClassName: gp2
storageClassName: gp2-csi
volumeMode: Block
accessModes:
- ReadWriteOnce
pkg/operator/ceph/cluster/osd/create_test.go
+2 -2
View File
@@ -353,7 +353,7 @@ func Test_startProvisioningOverPVCs(t *testing.T) {
Name: "set1",
Count: 0,
VolumeClaimTemplates: []cephv1.VolumeClaimTemplate{
newDummyPVC("data", namespace, "10Gi", "gp2"),
newDummyPVC("data", namespace, "10Gi", "gp2-csi"),
},
},
},
@@ -378,7 +378,7 @@ func Test_startProvisioningOverPVCs(t *testing.T) {
Name: "set1",
Count: 2,
VolumeClaimTemplates: []cephv1.VolumeClaimTemplate{
newDummyPVC("data", namespace, "10Gi", "gp2"),
newDummyPVC("data", namespace, "10Gi", "gp2-csi"),
},
},
},