Skip to content

Commit

Permalink
Updated description for the conditions
Browse files Browse the repository at this point in the history
  • Loading branch information
xing-yang committed Feb 13, 2020
1 parent c74ce24 commit ebec916
Show file tree
Hide file tree
Showing 3 changed files with 33 additions and 15 deletions.
16 changes: 11 additions & 5 deletions csi.proto
Original file line number Diff line number Diff line change
Expand Up @@ -1305,14 +1305,20 @@ message VolumeHealth {
enum Condition {
// Volume health condition is unknown; treat it as healthy.
UNKNOWN = 0;
// Volume is healthy.
// Volume is accessible and no problems are detected.
HEALTHY = 1;
// Volume is temporarily unhealthy, but will likely become healthy.
// Volume has degrading performance or is not accessible currently,
// but there's no reason to expect data loss. Examples: power
// outage, network outage, maintenance.
TEMPORARY_UNHEALTHY = 2;
// Volume will fail soon. Move your data off and replace volume or
// you may lose your data.
// Volume is accessible currently, but a problem is detected that
// could lead to eventual data loss. Examples: recoverable hardware
// failure, cooling failure, equipment significantly past end of
// life.
FATAL_IMMINENT = 3;
// Volume is unusable. Data loss is likely.
// Volume is not accessible currently, and there is reason to
// believe the outage may be permanent. Examples: unrecoverable
// hardware failure, natural disasters, damage to equipment.
FATAL = 4;
}

Expand Down
16 changes: 11 additions & 5 deletions lib/go/csi/csi.pb.go

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

16 changes: 11 additions & 5 deletions spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -2311,14 +2311,20 @@ message VolumeHealth {
enum Condition {
// Volume health condition is unknown; treat it as healthy.
UNKNOWN = 0;
// Volume is healthy.
// Volume is accessible and no problems are detected.
HEALTHY = 1;
// Volume is temporarily unhealthy, but will likely become healthy.
// Volume has degrading performance or is not accessible currently,
// but there's no reason to expect data loss. Examples: power
// outage, network outage, maintenance.
TEMPORARY_UNHEALTHY = 2;
// Volume will fail soon. Move your data off and replace volume or
// you may lose your data.
// Volume is accessible currently, but a problem is detected that
// could lead to eventual data loss. Examples: recoverable hardware
// failure, cooling failure, equipment significantly past end of
// life.
FATAL_IMMINENT = 3;
// Volume is unusable. Data loss is likely.
// Volume is not accessible currently, and there is reason to
// believe the outage may be permanent. Examples: unrecoverable
// hardware failure, natural disasters, damage to equipment.
FATAL = 4;
}
Expand Down

0 comments on commit ebec916

Please sign in to comment.