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 Volume Health Support to CSI #415

Merged
merged 1 commit into from
Apr 15, 2020

Conversation

xing-yang
Copy link
Contributor

@xing-yang xing-yang commented Feb 10, 2020

This PR adds volume health support to CSI spec.

Fixes: #410

csi.proto Outdated Show resolved Hide resolved
Copy link
Member

@jdef jdef left a comment

Choose a reason for hiding this comment

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

Several nits and renames suggested.

Also, if a plugin supports VOLUME_HEALTH, is there any reason why the list-volumes call can't return health for each of the volumes it reports?

spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
@xing-yang
Copy link
Contributor Author

Also, if a plugin supports VOLUME_HEALTH, is there any reason why the list-volumes call can't return health for each of the volumes it reports?

Many CSI drivers don't support ListVolumes because it is expensive to make such a call. We could add a volume_id as a filter in ListVolumes but that means drivers have to implement ListVolumes in order to get information from a specific volume. During a previous review meeting, @saad-ali has suggested it is better to have a separate GetVolume RPC.

@jdef
Copy link
Member

jdef commented Feb 11, 2020 via email

@xing-yang
Copy link
Contributor Author

I think my suggestion may have been misinterpreted. I wasn't suggesting the
elimination of GetVolume. Instead, I was suggesting that, for those plugins
that already implement list-volumes, maybe they would also be interested in
reporting health information that way.

Sure, I can add volume health in ListVolumes.

Copy link
Contributor Author

@xing-yang xing-yang left a comment

Choose a reason for hiding this comment

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

Addressed review comments. Thanks.

spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
@msau42
Copy link

msau42 commented Feb 12, 2020

cc @bswartz

csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
@xing-yang
Copy link
Contributor Author

Addressed Ben's comments. Thanks.

@xing-yang xing-yang changed the title WIP: Add Volume Health Support to CSI Add Volume Health Support to CSI Feb 13, 2020
@xing-yang
Copy link
Contributor Author

@jdef I have marked the new method, message, and field experimental based on your PR (#365). Can you please take a look? 5c862b2

@xing-yang xing-yang force-pushed the volumehealth branch 2 times, most recently from dcd82db to da542dd Compare February 13, 2020 14:37
Copy link
Contributor

@bswartz bswartz left a comment

Choose a reason for hiding this comment

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

I have reviewed these changes and I'm satisfied.

csi.proto Outdated Show resolved Hide resolved
@xing-yang
Copy link
Contributor Author

@julian-hj, @msau42 addressed your your comments. PTAL. Thanks.

csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
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.

👍

@jdef
Copy link
Member

jdef commented Feb 24, 2020

@jdef I have marked the new method, message, and field experimental based on your PR (#365). Can you please take a look? 5c862b2

It looks like some, not all of the Alpha API support is being added in this PR. While the work committed here isn't misaligned with #365, it is incomplete w/ respect to what was proposed.

Suggestion: cherry-pick the following commits from #365 such that Alpha API support is added comprehensively instead of piecemeal, which will make it more clear for others looking to adopt.

Or, maybe it would be cleaner to fast-track the above, suggested commits in a separate PR, merge that, and then rebase this one on top? I'm flexible here, just looking for a clear commit stream.

spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
Copy link
Member

@jdef jdef left a comment

Choose a reason for hiding this comment

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

I should have marked my last review as "request changes" - sorry for the confusion.

@xing-yang
Copy link
Contributor Author

@jdef I submitted the alpha api support PR separately here: #417. Will rebase this PR once that one is merged.

@xing-yang
Copy link
Contributor Author

@jdef Addressed most of your comments. I'll rebase this on the alpha api PR and address your remaining comment regarding the alpha feature.

@xing-yang
Copy link
Contributor Author

Rebased.

@xing-yang
Copy link
Contributor Author

Hi @jdef, I addressed all your comments. Please take a look again. Thanks.

@xing-yang
Copy link
Contributor Author

Hi @saad-ali, I updated the PR based on what we concluded in the review meeting. Please take a look. Thanks.

csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
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.

some nits, but overall, lgtm

csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
csi.proto Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
@xing-yang
Copy link
Contributor Author

All comments are addressed. Please take a look again.

spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
@xing-yang
Copy link
Contributor Author

@saad-ali Addressed your comments. PTAL.

Copy link
Member

@saad-ali saad-ali left a comment

Choose a reason for hiding this comment

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

Thanks @xing-yang

/lgtm
/approve

@saad-ali
Copy link
Member

@jdef @jieyu @julian-hj all good?

@xing-yang Please squash commits and I can help merge.

@xing-yang
Copy link
Contributor Author

Thanks @saad-ali. Squashed commits into 1.

spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
spec.md Outdated Show resolved Hide resolved
@xing-yang
Copy link
Contributor Author

Thanks @jdef. Addressed your comments.

@jdef
Copy link
Member

jdef commented Apr 13, 2020

LGTM

@saad-ali
Copy link
Member

@xing-yang please squash one more time and I'll merge

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

@xing-yang
Copy link
Contributor Author

xing-yang commented Apr 13, 2020

Squashed commits. Thanks @saad-ali and @jieyu.

@saad-ali
Copy link
Member

Thanks. Merging.

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.

CSI changes for volume health
7 participants