Support host-based NFS replication#466
Conversation
- adding prefix detection and parsing to the parsing function had unintended side effects during testing. - updating method of prefix detection to isolate detection only during replication calls.
| // host-based nfs volumes should have the "csi-nfs" parameter | ||
| // and a "nfs-" prefix in the volume ID that we need to remove | ||
| // for gopowerstore queries to succeed. | ||
| // Remove the prefix here and restore when building the response. |
There was a problem hiding this comment.
I see that we are adding the prefix to the remote volume only. Should the comment be updated?
There was a problem hiding this comment.
The prefix is actually part of the volume handle for both local and remote.
When the request comes into the driver to CreateRemoteVolume() the local volume handle already contains the prefix, and we want to make sure the volume handle returned by this same function also adds the prefix, so the driver on the remote side knows it is a host-based nfs volume.
I'm open to suggestions on better wording to communicate the idea to the reader tho.
Merging this branch will not change overall coverage
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. Changed unit test files
|
Description
These changes bring csi-powerstore host-based NFS volumes into scope for replication via csm-replication.
Main changes are in pkg/controller/replication.go.
Other changes include:
VolumeHandlestruct with members defining the different parts of the volume handle.GitHub Issues
List the GitHub issues impacted by this PR:
Checklist:
How Has This Been Tested?