Skip to content

Commit

Permalink
Address review comments
Browse files Browse the repository at this point in the history
  • Loading branch information
xing-yang committed Apr 13, 2020
1 parent 843742f commit f3133c6
Show file tree
Hide file tree
Showing 3 changed files with 15 additions and 10 deletions.
7 changes: 4 additions & 3 deletions csi.proto
Original file line number Diff line number Diff line change
Expand Up @@ -991,7 +991,8 @@ message ControllerServiceCapability {
// ListVolumesResponse.entry.published_nodes field
LIST_VOLUMES_PUBLISHED_NODES = 10;

// Indicates the SP supports controller level volume condition.
// Indicates that the Controller service can report volume
// conditions.
// An SP MAY implement `VolumeCondition` in only the Controller
// Plugin, only the Node Plugin, or both.
// If `VolumeCondition` is implemented in both the Controller and
Expand Down Expand Up @@ -1364,7 +1365,7 @@ message VolumeUsage {
Unit unit = 4;
}

// VolumeCondition represents the current condition of a volume
// VolumeCondition represents the current condition of a volume.
message VolumeCondition {
option (alpha_message) = true;

Expand Down Expand Up @@ -1399,7 +1400,7 @@ message NodeServiceCapability {
GET_VOLUME_STATS = 2;
// See VolumeExpansion for details.
EXPAND_VOLUME = 3;
// Indicates the SP supports node level volume condition.
// Indicates that the Node service can report volume conditions.
// An SP MAY implement `VolumeCondition` in only the Node
// Plugin, only the Controller Plugin, or both.
// If `VolumeCondition` is implemented in both the Node and
Expand Down
7 changes: 4 additions & 3 deletions lib/go/csi/csi.pb.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

11 changes: 7 additions & 4 deletions spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -1548,7 +1548,9 @@ message ControllerGetVolumeResponse {

##### ControllerGetVolume Errors

If the plugin is unable to complete the ControllerGetVolume call successfully, it MUST return a non-ok gRPC code in the gRPC status. If the conditions defined below are encountered, the plugin MUST return the specified gRPC error code. The CO MUST implement the specified error recovery behavior when it encounters the gRPC error code.
If the plugin is unable to complete the ControllerGetVolume call successfully, it MUST return a non-ok gRPC code in the gRPC status.
If the conditions defined below are encountered, the plugin MUST return the specified gRPC error code.
The CO MUST implement the specified error recovery behavior when it encounters the gRPC error code.

| Condition | gRPC Code | Description | Recovery Behavior |
|-----------|-----------|-------------|-------------------|
Expand Down Expand Up @@ -1646,7 +1648,8 @@ message ControllerServiceCapability {
// ListVolumesResponse.entry.published_nodes field
LIST_VOLUMES_PUBLISHED_NODES = 10;
// Indicates the SP supports controller level volume condition.
// Indicates that the Controller service can report volume
// conditions.
// An SP MAY implement `VolumeCondition` in only the Controller
// Plugin, only the Node Plugin, or both.
// If `VolumeCondition` is implemented in both the Controller and
Expand Down Expand Up @@ -2365,7 +2368,7 @@ message VolumeUsage {
Unit unit = 4;
}
// VolumeCondition represents the current condition of a volume
// VolumeCondition represents the current condition of a volume.
message VolumeCondition {
option (alpha_message) = true;
Expand Down Expand Up @@ -2419,7 +2422,7 @@ message NodeServiceCapability {
GET_VOLUME_STATS = 2;
// See VolumeExpansion for details.
EXPAND_VOLUME = 3;
// Indicates the SP supports node level volume condition.
// Indicates that the Node service can report volume conditions.
// An SP MAY implement `VolumeCondition` in only the Node
// Plugin, only the Controller Plugin, or both.
// If `VolumeCondition` is implemented in both the Node and
Expand Down

0 comments on commit f3133c6

Please sign in to comment.