Bug 2053452

Summary: Change StorageClass name
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Chris Blum <cblum>
Component: lvm-operatorAssignee: N Balachandran <nibalach>
Status: CLOSED CURRENTRELEASE QA Contact: Shay Rozen <srozen>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.10CC: jolmomar, kramdoss, lgangava, mmuench, muagarwa, nberry, ocs-bugs, odf-bz-bot, rcyriac, sapillai
Target Milestone: ---   
Target Release: ODF 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.10.0-164 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-21 09:12:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Chris Blum 2022-02-11 11:15:07 UTC
Description of problem (please be detailed as possible and provide log
snippests):
Make sure the topolvm name does not appear in the released product wherever we can avoid it.

Version of all relevant components (if applicable):
ODF 4.10 & 4.11

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
No

Actual results:
Currently the Storage Class name is "topolvm-${VG.name}"

Expected results:
Let's change this to "odf-${LVMCluster.name}-${VG.name}" and make sure that the default LVMCluster name is short. For example: "lvmo"

Additional info:
As discussed with Nithya

Comment 2 Chris Blum 2022-02-11 12:20:34 UTC
Nithya proposed to instead set the storage class name to: "{lvmclustername}-{vgname}" and having the name of the LVMCluster be odf-lvmo by default?

That way we can keep the lvmo and odf name out of upstream.

This is fine by me too

Comment 7 Shay Rozen 2022-03-02 11:47:04 UTC
Storageclass was changed to odf-lvm-<name of vg>