Skip to content

add support for distributing day2 volume[group]snapshotclasses #3153

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 14, 2025

Conversation

leelavg
Copy link
Contributor

@leelavg leelavg commented Apr 10, 2025

when the volume[group]storageclass mentioned in storageconsumer doesn't match one of the known names we consider that being unmanaged day2 created v[g]sc and we update the dynamic params corresponding to the driver and then send as a resource to be created & owned by storageclient in client-op.

@rewantsoni
Copy link
Member

I think you are missing RBACs for ocs-provider-server to get V[G]SC

when the volume[group]storageclass mentioned in storageconsumer
doesn't match one of the known names we consider that being unmanaged
day2 created v[g]sc and we update the dynamic params corresponding to
the driver and then send as a resource to be created & owned by
storageclient in client-op.

Signed-off-by: Leela Venkaiah G <lgangava@ibm.com>
@leelavg
Copy link
Contributor Author

leelavg commented Apr 14, 2025

rebased on main.

Comment on lines +106 to +113
case RbdDriverName:
clientProfileName = consumerConfig.GetRbdClientProfileName()
provisionerSecretName = consumerConfig.GetCsiRbdProvisionerSecretName()
storageId = rbdStorageId
case CephFSDriverName:
clientProfileName = consumerConfig.GetCephFsClientProfileName()
provisionerSecretName = consumerConfig.GetCsiCephFsProvisionerSecretName()
storageId = cephFsStorageId
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the expectation that when the user creates this groupsnapshot class, they will provide it with "pool"/"fsName" parameters? Or do we want to fill in some default values?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

they will provide it with "pool"/"fsName" parameters

  • yes, that's the expectation which is inline w/ current documented procedures

Comment on lines +114 to +117
case NfsDriverName:
clientProfileName = consumerConfig.GetNfsClientProfileName()
provisionerSecretName = consumerConfig.GetCsiNfsProvisionerSecretName()
storageId = nfsStorageId
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NFS groupsnapshot is not supported right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

then this case will never be hit, I don't think that'll be an issue until we support that and these params will differ.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When we do declare support for this the params will NOT differ as out NFS implementatin is just a protocol layer on top of CephFS. Which means, to the best of my understanding, that storageId should and can be the same

@nb-ohad
Copy link
Contributor

nb-ohad commented Apr 14, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 14, 2025
Copy link
Contributor

openshift-ci bot commented Apr 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: leelavg, nb-ohad

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 14, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 3f085cd into red-hat-storage:main Apr 14, 2025
11 checks passed
@leelavg leelavg deleted the day-2-vg branch April 15, 2025 01:24
@leelavg
Copy link
Contributor Author

leelavg commented Apr 15, 2025

/cherrypick release-4.19

@openshift-cherrypick-robot

@leelavg: new pull request created: #3161

In response to this:

/cherrypick release-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants