-
Notifications
You must be signed in to change notification settings - Fork 315
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
Decouple api-server from controller framework #574
Decouple api-server from controller framework #574
Conversation
Signed-off-by: leonwanghui <wanghui71leon@gmail.com>
Signed-off-by: leonwanghui <wanghui71leon@gmail.com>
please fix the CI error. |
Signed-off-by: leonwanghui <wanghui71leon@gmail.com>
Currently this PR has passed unit test and integration test, @xxwjj please take a look at it and update |
Signed-off-by: leonwanghui <wanghui71leon@gmail.com>
Signed-off-by: leonwanghui <wanghui71leon@gmail.com>
Hi @xing-yang @wisererik , please take a review at this patch, thanks! |
// NOTE:The real volume group deletion process. | ||
// Volume group deletion request is sent to the Dock. Dock will remove | ||
// volume group record after volume group deletion operation is completed. | ||
if err = v.CtrClient.Connect(CONF.OsdsLet.ApiEndpoint); err != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should let controller update the database, not Dock.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I will update the code in next PR.
Signed-off-by: leonwanghui <wanghui71leon@gmail.com>
Signed-off-by: leonwanghui <wanghui71leon@gmail.com>
Signed-off-by: leonwanghui <wanghui71leon@gmail.com>
Signed-off-by: leonwanghui <wanghui71leon@gmail.com>
@xing-yang Please take a look at this patch, thanks! |
I will merge this patch for now, and start the second step of design proposal |
What this PR does / why we need it:
See design spec for detailed information.
Please notice that this PR would address
Phase 1
of the design spec.Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
@xing-yang @wisererik Please take a review at this PR, thanks!
Release note: