Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add msg to clarify usage #529

Closed

Conversation

xing-yang
Copy link
Contributor

What type of PR is this?
This PR adds a message to clarify how VOLUME_CONDITION is used.

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?:

none

@xing-yang
Copy link
Contributor Author

@jdef Please take a look. Thanks.

@@ -1056,6 +1056,8 @@ message ControllerServiceCapability {
// If for some reason Controller and Node Plugins report
// misaligned volume conditions, CO SHALL assume the worst case
// is the truth.
// Note that `VolumeCondition` can be used to generate events and
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"events" .. smells like k8s lingo.

also, I specifically called out use of the message field of VolumeCondition. and how it's not clear what the intended use is for it. can you please attempt to clarify? we cannot assume k8s semantics/terminology in this spec - it should be very clear to all users of all COs what message means. and whether it is for humans or machines to interpret

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The message field of VolumeCondition is intended for humans, not for machines to interpret. The abnormal field can be used for automation.

message VolumeCondition {
  // Normal volumes are available for use and operating optimally.
  // An abnormal volume does not meet these criteria.
  // This field is REQUIRED.
  bool abnormal = 1;

  // The message describing the condition of the volume.
  // This field is REQUIRED.
  string message = 2;
}

@xing-yang
Copy link
Contributor Author

Closing this one. See this: #530

@xing-yang xing-yang closed this Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants