-
Notifications
You must be signed in to change notification settings - Fork 0
Adding scheduling decision CRD: "why/why not" api #307
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
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.
Maybe add a test step in the github workflows like it was done for the reservations operator
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.
Worked for me while building the nova UI!
Approved from my side. |
Test Coverage ReportCoverage in main module (internal/): 73.2%
Coverage in reservations module (reservations/internal/): 74.6%
Coverage in decisions module (decisions/internal/): 84.1%
|
This contribution adds an api to cortex that describes why a virtual machine has been placed on a specific compute host. It exposes the raw pipeline weights with a kubernetes custom resource, and the associated operator calculates a human-readable description from the provided values. The resource is also connected to the nova visualizer so that decisions can be spectated in the browser removing this dependency on the mqtt broker.