[FEATURE]: Pass Volume Name off to Storage System

[oa72280emc]

Describe the solution you'd like The myvalues (values).yaml enables the naming convention of volumes carved up by the CSI. K8S is the default. This can be changed at deployment of the CSI. It could be helpful to allow the alternate name to be passed off to the storage array.

Describe alternatives you've considered Would require the storage admin to manually change the name of the volume in the UI of PowerFlex. If deploying a volume(s) for a specific app, would be good to pass this off automatically.

Additional context N/A

[ioeicicdsvc]

@oa72280emc: Thank you for submitting this issue!

The issue is currently awaiting triage. Please make sure you have given us as much context as possible.

If the maintainers determine this is a relevant issue, they will remove the needs-triage label and assign an appropriate priority label.

---

We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at [email protected].

[alikdell]

/sync

[hoppea2]

Hi @oa72280emc, the changing of the prefix in the values.yaml should be reflected in the naming of the storage volumes on the array. Are you seeing something different?

[oa72280emc]

The idea here is that a volume specific name is passed off to the PowerFlex.

Using a prefix is fine for the majority of the volumes that are created by the CSI ... it's the idea, that some volumes should be able to pass their pvc name / pv name off to the PowerFlex

Thanks Ollie

From: hoppea2 @.***> Sent: Tuesday, November 23, 2021 2:34 PM To: dell/csm Cc: Ames, Oliver; Mention Subject: Re: [dell/csm] [FEATURE]: Pass Volume Name off to Storage System (#42)

[EXTERNAL EMAIL]

Hi @oa72280emc [github.com]https://urldefense.com/v3/__https:/github.com/oa72280emc__;!!LpKI!xzE65I2plco3kVtWMMJshM4uwbPMI9DcTuh4G1z0X9RqeOggreSVHS7KtR8v21Y$, the changing of the prefix in the values.yaml should be reflected in the naming of the storage volumes on the array. Are you seeing something different?

You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub [github.com]https://urldefense.com/v3/__https:/github.com/dell/csm/issues/42*issuecomment-977067865__;Iw!!LpKI!xzE65I2plco3kVtWMMJshM4uwbPMI9DcTuh4G1z0X9RqeOggreSVHS7KnyQLY4I$, or unsubscribe [github.com]https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AUY5PTRES7VO6ETWTN5TLY3UNPUDTANCNFSM5EWOH35A__;!!LpKI!xzE65I2plco3kVtWMMJshM4uwbPMI9DcTuh4G1z0X9RqeOggreSVHS7KE9LvAg0$. Triage notifications on the go with GitHub Mobile for iOS [apps.apple.com]https://urldefense.com/v3/__https:/apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!LpKI!xzE65I2plco3kVtWMMJshM4uwbPMI9DcTuh4G1z0X9RqeOggreSVHS7KhbYZa9c$ or Android [play.google.com]https://urldefense.com/v3/__https:/play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!LpKI!xzE65I2plco3kVtWMMJshM4uwbPMI9DcTuh4G1z0X9RqeOggreSVHS7KGS2n7Bg$.

Internal Use - Confidential