-
Notifications
You must be signed in to change notification settings - Fork 185
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
add VolumeGroupSnapshotClass for CephFS and RBD #2859
base: main
Are you sure you want to change the base?
add VolumeGroupSnapshotClass for CephFS and RBD #2859
Conversation
acdabd0
to
de40e7b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See kubernetes-csi/external-snapshotter#1150 for the BETA status PR. |
we might need to have a VGSC CRD check as ocs-operator 4.18 needs to run on OCP 4.16 without any problem for EUS to EUS upgrade? @iamniting @Nikhil-Ladha thoughts? |
metrics/vendor/github.com/red-hat-storage/ocs-operator/v4/controllers/util/csi_options.go
Outdated
Show resolved
Hide resolved
Yep, as going forward the plan will be updgrade ODF first, it is advisable to have these checks in place for new changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Break the PR into multiple commits, where as keep the generated changes into 1 commit, and the code changes into another.
I agree we should have such checks, But let's not use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pls have a generated changes in the separate commit.
de40e7b
to
be56914
Compare
3ec52f3
to
6c2c34e
Compare
6c2c34e
to
1a7d990
Compare
I have added a plain check for VGSC CRD as well. Please do review it. @Madhu-1 @iamniting @Nikhil-Ladha |
6379d30
to
71316e5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you pls fix tests?
71316e5
to
7b37de4
Compare
42781ed
to
dba5744
Compare
dba5744
to
58917de
Compare
bd9d6ce
to
b4de5dc
Compare
b4de5dc
to
1b08d24
Compare
@ShravaniVangur Is the code tested? Also, is updating the GroupSnapshotClass allowed? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ShravaniVangur Is this intended to go in 4.18? If yes we would need a Jira Bug.
If this is intended for 4.19 then if there is a Jira Story/Upstream Issue for this please attach it here.
Please mark as resolved the conversations which have been already resolved, Normally that should be done by the reviewer but here too many open conversations is making it confusing to take a final look.
@Madhu-1 still has a hold on this PR, please discuss with him about the reason & get it resolved.
1b08d24
to
fd009f3
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, @iamniting PTAL
|
fd009f3
to
2b5f754
Compare
Yes I have tested the code with the beta version and have updated the results in the description. |
2b5f754
to
8cd6c52
Compare
for _, vgsc := range vgscs { | ||
sc := vgsc.groupSnapshotClass | ||
existing := groupsnapapi.VolumeGroupSnapshotClass{} | ||
err := r.Client.Get(r.ctx, types.NamespacedName{Name: sc.Name, Namespace: sc.Namespace}, &existing) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really need to do a GET call? We can just make a DELETE call, and if it is not found, we can ignore it. There is no need for a GET and DELETE call.
type GroupSnapshotClassConfiguration struct { | ||
groupSnapshotClass *groupsnapapi.VolumeGroupSnapshotClass | ||
reconcileStrategy ReconcileStrategy | ||
disable bool |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest adding a comment for the disable field saying it was added for a future purpose. When we add an API or some other mechanism to disable the VGSC, this field will be used to control it.
return "pool", generateNameForCephBlockPool(instance) | ||
} | ||
return "fsName", generateNameForCephFilesystem(instance) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did not understand what change is expected here?
CSI-drivers requires VolumeGroupSnapshotClass for VolumeGroupSnapshot. Signed-off-by: ShravaniVangur <[email protected]>
Updates the go mod dependencies. Signed-off-by: ShravaniVangur <[email protected]>
8cd6c52
to
ac57cc4
Compare
Testing creation of VolumeGroupSnapshotClass and related functionalities
(BETA Version):