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

spec: VolumeHandle replaces VolumeID, VolumeMetadata #97

Merged
merged 2 commits into from
Sep 6, 2017

Conversation

jdef
Copy link
Member

@jdef jdef commented Sep 1, 2017

Refactor volume ID and metadata; provide additional clarification.
xref #29 #88

@jdef jdef requested review from jieyu and saad-ali September 1, 2017 16:34
@jdef
Copy link
Member Author

jdef commented Sep 1, 2017

xref #71

spec.md Outdated
// example, the CO MAY generate log messages that include this data.
string id = 1;

// Metadata captures additional, possibly sensitive information about
Copy link
Member

Choose a reason for hiding this comment

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

nit: additional, possibly sensitive, information

Copy link
Contributor

Choose a reason for hiding this comment

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

I am not sure i agree with this nit. To me it reads better without the extra comma.

Copy link
Member

@saad-ali saad-ali Sep 6, 2017

Choose a reason for hiding this comment

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

Having a single comma suggests that "Metadata captures additional" is an introductory clause. But, "possibly sensitive information about..." can't stand on it's on (it is incomplete without the first part of the sentence).

Instead, "possibly sensitive" is nonessential information. And the sentence reads fine without it.

From https://owl.english.purdue.edu/owl/owlprint/607/:

Commas with Nonessential Elements

Some modifying elements of a sentence are essential, restricting the meaning of a modified term, while others are nonessential and don't restrict the modified term's meaning. These nonessential elements, which can be words, phrases, or clauses, are set off with commas.

Rule: Use commas before and after nonessential words, phrases, and clauses, that is, elements embedded in the sentence that interrupt it without changing the essential meaning.

So I would offset "possibly sensitive" with two commas.

I'm being very pedantic here, so feel free to disregard =)

Copy link
Member Author

Choose a reason for hiding this comment

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

ack

// NOT change over the lifetime of the volume and MAY be safely cached
// by the CO.
// Since this object will be passed around by the CO, it is RECOMMENDED
// that each Plugin keeps the information herein as small as possible.
Copy link
Member

Choose a reason for hiding this comment

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

Maybe add in a size requirement, like we did with credentials. Always better to start with a hard limit and loosen it in the future, then not starting with a limit and trying to add it later. e.g. The total bytes of the ID and metadata must be less than 1 Mebibyte.

Copy link
Member Author

Choose a reason for hiding this comment

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

agreed

Copy link
Member Author

Choose a reason for hiding this comment

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

xref #87

Copy link
Contributor

@julian-hj julian-hj left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@jieyu jieyu left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks @jdef !

spec.md Outdated
// Since this object will be passed around by the CO, it is RECOMMENDED
// that each Plugin keeps the information herein as small as possible.
message VolumeHandle {

Copy link
Member

Choose a reason for hiding this comment

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

nit: kill this line to be consistent with other places.

Copy link
Member Author

Choose a reason for hiding this comment

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

ack

@saad-ali
Copy link
Member

saad-ali commented Sep 6, 2017

LGTM. Thanks @jdef. Merging.

@saad-ali saad-ali merged commit 8ba18a5 into container-storage-interface:master Sep 6, 2017
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.

4 participants