-
Notifications
You must be signed in to change notification settings - Fork 0
HypervisorMaintenanceController: Enable/Disable compute service #177
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
Conversation
|
Draft, as it is missing other changes and conflicts with the existing code. |
1504dc1 to
3ba8b69
Compare
3ba8b69 to
4d6f80c
Compare
notandy
left a comment
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.
lgtm apart from the EventFilter
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.
❤️
4d6f80c to
84f495c
Compare
The controller only gets active after onboarding, as that one needs to take care of enabling and aggregate association depending on the tests. If maintenance is set, it will disable now the compute host in nova, and enable it, if it is unset. It will only do so on an "edge", i.e. if it hasn't done it before.
Merging this branch will increase overall coverage
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. Changed unit test files
|
The controller only gets active after onboarding, as that one needs to take care of enabling and aggregate association depending on the tests.
If maintenance is set, it will disable now the compute host in nova, and enable it, if it is unset.
It will only do so on an "edge", i.e. if it hasn't done it before.