Skip to content

Commit 0600cb2

Browse files
committed
GetCapacityResponse: volume size range
The minimum volume size may also be relevant. Another advantage is that the existing CapacityRange type can be used.
1 parent e09188b commit 0600cb2

File tree

3 files changed

+288
-337
lines changed

3 files changed

+288
-337
lines changed

csi.proto

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -948,23 +948,19 @@ message GetCapacityResponse {
948948
// The value of this field MUST NOT be negative.
949949
int64 available_capacity = 1;
950950

951-
// The largest size that may be used in a CreateVolume call
951+
// The supported volume size that may be used in a CreateVolume call
952952
// to create a volume with the same parameters as those in
953-
// GetCapacityRequest.
953+
// GetCapacityRequest, given as a lower bound (`required_bytes`)
954+
// and an upper bound (`limit_bytes`).
954955
//
955956
// If `volume_capabilities` or `parameters` is
956957
// specified in the request, the Plugin SHALL take those into
957-
// consideration when calculating the maximum volume size of the
958+
// consideration when calculating the supported volume size of the
958959
// storage.
959960
//
960961
// This field is OPTIONAL. COs MAY use it to make decision about
961962
// where to create volumes.
962-
Capacity maximum_volume_size = 2 [(alpha_field) = true];
963-
}
964-
965-
message Capacity {
966-
// Number of bytes. MUST NOT be negative.
967-
int64 value = 1;
963+
CapacityRange volume_size = 2 [(alpha_field) = true];
968964
}
969965
message ControllerGetCapabilitiesRequest {
970966
// Intentionally empty.

0 commit comments

Comments
 (0)