-
Notifications
You must be signed in to change notification settings - Fork 618
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
[cinder-csi-plugin] Add http endpoint of CSI container #1398
Conversation
Build failed.
|
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
Build failed.
|
Build failed.
|
Build failed.
|
Build failed.
|
90476d0
to
38c3d65
Compare
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
Build failed.
|
Build failed.
|
Build succeeded.
|
Build failed.
|
Build failed.
|
Build failed.
|
Build failed.
|
Build failed.
|
the result looks like this |
/retest |
Build succeeded.
|
Build succeeded.
|
/retest |
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
Build failed.
|
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
Build succeeded.
|
/test cloud-provider-openstack-acceptance-test-csi-manila |
@jichenjc: The specified target(s) for
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Build failed.
|
/test cloud-provider-openstack-acceptance-test-csi-manila |
@jichenjc: The specified target(s) for
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Build failed.
|
@jichenjc: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/close please feel free to reopen , if you would like to work on it in future |
@ramineni: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@ramineni @jichenjc @chrigl it looks like discussion around cinder csi metrics started in year 2020. However, one reason why we do not have metrics yet is comment #1392 (comment) it is pretty difficult to implement. As I see it: we have already multiple components (occm+cinder-csi), why we should have common endpoint to retrieve metrics from all components? Why we cannot have own metrics endpoints for csi and occm? So I am kind of asking: could we just use different way to provide metrics? Now we do not have anything. For instance, AWS EBS CSI is using similar solution that was implemented in this PR. I think we should use this as starting point |
few things that we should think of:
|
I am not sure this is best practice, at least I think metics comes from its own endpoint..
should this be similar way? I don't see any reason we should be different on OCCM and CSI |
What this PR does / why we need it:
Add http endpoint of CSI container , it will be used for metris later
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:
Release note: