-
Notifications
You must be signed in to change notification settings - Fork 19
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
Use the refactored runner manager #351
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.
Reviewed untiol tests/unit/test_charm.py, looks good so far! Thanks for working on it!
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.
Reviewed until tests
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.
Some nit comments, otherwise looks good.
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!
Test coverage for 14aedab
Static code analysis report
|
Overview
Use the refactored runner manager for OpenStack runner in charm.py.
Rationale
The refactored interface should be used in the charm.
Juju Events Changes
The
get-runners
juju action returns with some new fields ("busy", and "busy-runners").This provides info on busy runners.
Added since it makes tests easier.
Module Changes
Add a RunnerScaler class. This class uses the RunnerManager and provides the APIs the charm.py needs, e.g., scale up/down, flush runners, get runner infos.
Checklist
src-docs
urgent
,trivial
,complex
)