Skip to content

Add Volume Health Support to CSI - #415

Merged
saad-ali merged 1 commit into
container-storage-interface:masterfrom
xing-yang:volumehealth
Apr 15, 2020
Merged

Add Volume Health Support to CSI#415
saad-ali merged 1 commit into
container-storage-interface:masterfrom
xing-yang:volumehealth

Conversation

@xing-yang

@xing-yangxing-yang commented Feb 10, 2020

Copy link
Copy Markdown
Contributor

This PR adds volume health support to CSI spec.

Fixes: #410

Comment threadcsi.proto Outdated

@jdefjdef left a comment

Copy link
Copy Markdown
Member

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?

Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
@xing-yang

Copy link
Copy Markdown
ContributorAuthor

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

jdef commented Feb 11, 2020 via email

Copy link
Copy Markdown
Member

@xing-yang

Copy link
Copy Markdown
ContributorAuthor

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.

@xing-yangxing-yang left a comment

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Addressed review comments. Thanks.

Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
@msau42

Copy link
Copy Markdown

cc @bswartz

Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
@xing-yang

Copy link
Copy Markdown
ContributorAuthor

Addressed Ben's comments. Thanks.

@xing-yangxing-yang changed the title WIP: Add Volume Health Support to CSIAdd Volume Health Support to CSIFeb 13, 2020
@xing-yang

Copy link
Copy Markdown
ContributorAuthor

@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-yangforce-pushed the volumehealth branch 2 times, most recently from dcd82db to da542ddCompareFebruary 13, 2020 14:37

@bswartzbswartz left a comment

Copy link
Copy Markdown
Contributor

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.

Comment threadcsi.proto Outdated
@xing-yang

Copy link
Copy Markdown
ContributorAuthor

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

Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated

@julian-hjjulian-hj left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

👍

@jdef

jdef commented Feb 24, 2020

Copy link
Copy Markdown
Member

@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.

Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated

@jdefjdef left a comment

Copy link
Copy Markdown
Member

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
Copy Markdown
ContributorAuthor

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

@xing-yang

Copy link
Copy Markdown
ContributorAuthor

@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
Copy Markdown
ContributorAuthor

Rebased.

@xing-yang

Copy link
Copy Markdown
ContributorAuthor

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

@xing-yang

Copy link
Copy Markdown
ContributorAuthor

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

Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated

@jieyujieyu left a comment

Copy link
Copy Markdown
Member

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

Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadcsi.proto Outdated
Comment threadcsi.proto Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
@xing-yang

Copy link
Copy Markdown
ContributorAuthor

All comments are addressed. Please take a look again.

Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
@xing-yang

Copy link
Copy Markdown
ContributorAuthor

@saad-ali Addressed your comments. PTAL.

@saad-alisaad-ali left a comment

Copy link
Copy Markdown
Member

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
Copy Markdown
Member

@jdef@jieyu@julian-hj all good?

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

@xing-yang

Copy link
Copy Markdown
ContributorAuthor

Thanks @saad-ali. Squashed commits into 1.

Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
Comment threadspec.md Outdated
@xing-yang

Copy link
Copy Markdown
ContributorAuthor

Thanks @jdef. Addressed your comments.

@jdef

jdef commented Apr 13, 2020

Copy link
Copy Markdown
Member

LGTM

@saad-ali

Copy link
Copy Markdown
Member

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

@jieyujieyu left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

lgtm

@xing-yang

xing-yang commented Apr 13, 2020

Copy link
Copy Markdown
ContributorAuthor

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

@saad-ali

Copy link
Copy Markdown
Member

Thanks. Merging.

Sign up for freeto 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

@xing-yang@jdef@msau42@saad-ali@bswartz@jieyu@julian-hj