[New GRPC] Allow modifying volume topology #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
iltyty
changed the title
Owner
Author
|
详细描述下Attach、ModifyTopology不同阶段，ModifyTopology的表现
|
Owner
Author
|
不要手动输入topology，作为ControllerModifyVolume的superset。 |
iltyty
force-pushed
the
kep-5381-new-grpc
branch
from
6d9cf20 to
7984786
Compare
mowangdk
reviewed
Jun 24, 2025
spec.md
Outdated
| **ALPHA FEATURE** | ||
|
|
||
| A Controller plugin MUST implement this RPC call if the plugin has the MODIFY_VOLUME_TOPOLOGY controller capability. | ||
| This RPC allows the CO to change mutable key attributes and the accessible topology of a volume. |
There was a problem hiding this comment.
Do you mean Allows the CO change the accessible topology of a volume by mutable key attributes?
iltyty
force-pushed
the
kep-5381-new-grpc
branch
2 times, most recently
from
6bc8ad2 to
cf0b28d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce an API-breaking change?: