Merge pull request #10263 from vbnrh/fix-storageclass-description

Bug 2006025: Rephrases description to use an existing StorageClass
openshift · Oct 20, 2021 · a8b55c5 · a8b55c5
2 parents afcf180 + b2dfef8
commit a8b55c5
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 8 deletions.
diff --git a/frontend/packages/ceph-storage-plugin/locales/en/ceph-storage-plugin.json b/frontend/packages/ceph-storage-plugin/locales/en/ceph-storage-plugin.json
@@ -158,9 +158,9 @@
   "Select a storage platform you wish to connect": "Select a storage platform you wish to connect",
   "Select external system from list": "Select external system from list",
   "Use an existing StorageClass": "Use an existing StorageClass",
-  "OpenShift Data Foundation will use an existing infrastructure StorageClass provided by your hosting platform.": "OpenShift Data Foundation will use an existing infrastructure StorageClass provided by your hosting platform.",
+  "OpenShift Data Foundation will use an existing StorageClass available on your hosting platform.": "OpenShift Data Foundation will use an existing StorageClass available on your hosting platform.",
   "Create a new StorageClass using local storage devices": "Create a new StorageClass using local storage devices",
-  "OpenShift Data Foundation will use an infrastructure StorageClass provided by the Local Storage Operator (LSO) on top of your attached drives. This option is available on any platform with devices attached to nodes.": "OpenShift Data Foundation will use an infrastructure StorageClass provided by the Local Storage Operator (LSO) on top of your attached drives. This option is available on any platform with devices attached to nodes.",
+  "OpenShift Data Foundation will use a StorageClass provided by the Local Storage Operator (LSO) on top of your attached drives. This option is available on any platform with devices attached to nodes.": "OpenShift Data Foundation will use a StorageClass provided by the Local Storage Operator (LSO) on top of your attached drives. This option is available on any platform with devices attached to nodes.",
   "Connect an external storage platform": "Connect an external storage platform",
   "OpenShift Data Foundation will create a dedicated StorageClass.": "OpenShift Data Foundation will create a dedicated StorageClass.",
   "Select capacity": "Select capacity",
@@ -679,9 +679,9 @@
   "Logical used capacity per account": "Logical used capacity per account",
   "Egress Per Provider": "Egress Per Provider",
   "I/O Operations count": "I/O Operations count",
-  "The infrastructure StorageClass used by OpenShift Container Storage to write its data and metadata.": "The infrastructure StorageClass used by OpenShift Container Storage to write its data and metadata.",
+  "The StorageClass used by OpenShift Data Foundation to write its data and metadata.": "The StorageClass used by OpenShift Data Foundation to write its data and metadata.",
   "Infrastructure StorageClass created by Local Storage Operator and used by OpenShift Container Storage to write its data and metadata.": "Infrastructure StorageClass created by Local Storage Operator and used by OpenShift Container Storage to write its data and metadata.",
-  "The amount of capacity that would be dynamically allocated on the infrastructure StorageClass.": "The amount of capacity that would be dynamically allocated on the infrastructure StorageClass.",
+  "The amount of capacity that would be dynamically allocated on the selected StorageClass.": "The amount of capacity that would be dynamically allocated on the selected StorageClass.",
   "If you wish to use the Arbiter stretch cluster, a minimum of 4 nodes (2 different zones, 2 nodes per zone) and 1 additional zone with 1 node is required. All nodes must be pre-labeled with zones in order to be validated on cluster creation.": "If you wish to use the Arbiter stretch cluster, a minimum of 4 nodes (2 different zones, 2 nodes per zone) and 1 additional zone with 1 node is required. All nodes must be pre-labeled with zones in order to be validated on cluster creation.",
   "Selected nodes are based on the StorageClass <1>{{scName}}</1> and with a recommended requirement of 14 CPU and 34 GiB RAM per node.": "Selected nodes are based on the StorageClass <1>{{scName}}</1> and with a recommended requirement of 14 CPU and 34 GiB RAM per node.",
   "Selected nodes are based on the StorageClass <1>{{scName}}</1> and fulfill the stretch cluster requirements with a recommended requirement of 14 CPU and 34 GiB RAM per node.": "Selected nodes are based on the StorageClass <1>{{scName}}</1> and fulfill the stretch cluster requirements with a recommended requirement of 14 CPU and 34 GiB RAM per node.",

diff --git a/...-storage-system/create-storage-system-steps/backing-storage-step/backing-storage-step.tsx b/...-storage-system/create-storage-system-steps/backing-storage-step/backing-storage-step.tsx
@@ -240,7 +240,7 @@ export const BackingStorage: React.FC<BackingStorageProps> = ({
         <Radio
           label={t('ceph-storage-plugin~Use an existing StorageClass')}
           description={t(
-            'ceph-storage-plugin~OpenShift Data Foundation will use an existing infrastructure StorageClass provided by your hosting platform.',
+            'ceph-storage-plugin~OpenShift Data Foundation will use an existing StorageClass available on your hosting platform.',
           )}
           name={RADIO_GROUP_NAME}
           value={BackingStorageType.EXISTING}
@@ -258,7 +258,7 @@ export const BackingStorage: React.FC<BackingStorageProps> = ({
         <Radio
           label={t('ceph-storage-plugin~Create a new StorageClass using local storage devices')}
           description={t(
-            'ceph-storage-plugin~OpenShift Data Foundation will use an infrastructure StorageClass provided by the Local Storage Operator (LSO) on top of your attached drives. This option is available on any platform with devices attached to nodes.',
+            'ceph-storage-plugin~OpenShift Data Foundation will use a StorageClass provided by the Local Storage Operator (LSO) on top of your attached drives. This option is available on any platform with devices attached to nodes.',
           )}
           name={RADIO_GROUP_NAME}
           value={BackingStorageType.LOCAL_DEVICES}

diff --git a/frontend/packages/ceph-storage-plugin/src/constants/tooltips.tsx b/frontend/packages/ceph-storage-plugin/src/constants/tooltips.tsx
@@ -4,15 +4,15 @@ import { Trans } from 'react-i18next';
 
 export const storageClassTooltip = (t: TFunction) =>
   t(
-    'ceph-storage-plugin~The infrastructure StorageClass used by OpenShift Container Storage to write its data and metadata.',
+    'ceph-storage-plugin~The StorageClass used by OpenShift Data Foundation to write its data and metadata.',
   );
 export const attachedDevicesStorageClassTooltip = (t: TFunction) =>
   t(
     'ceph-storage-plugin~Infrastructure StorageClass created by Local Storage Operator and used by OpenShift Container Storage to write its data and metadata.',
   );
 export const requestedCapacityTooltip = (t: TFunction) =>
   t(
-    'ceph-storage-plugin~The amount of capacity that would be dynamically allocated on the infrastructure StorageClass.',
+    'ceph-storage-plugin~The amount of capacity that would be dynamically allocated on the selected StorageClass.',
   );
 export const arbiterText = (t: TFunction) =>
   t(