-
Notifications
You must be signed in to change notification settings - Fork 125
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
Add limits colums to conversion_hosts table #272
Add limits colums to conversion_hosts table #272
Conversation
class AddConversionHostLimitsColumns < ActiveRecord::Migration[5.0] | ||
def change | ||
change_table :conversion_hosts do |t| | ||
t.string :limits_max_concurrent_transformations |
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.
I'm not sure about the naming and plualization here, also limit
+ max
seems redundant. Wouldn't this be clearer as concurrent_transformation_limit
?
def change | ||
change_table :conversion_hosts do |t| | ||
t.string :limits_max_concurrent_transformations | ||
t.string :limits_max_cpu |
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.
Same for these, I think they would read better as <metric>_limit
or max_used_<metric>
.
Also, just for my own curiosity, are these metrics on the conversion host or limits on the VMs this host can convert?
c3e5c6c
to
5070b58
Compare
Checked commit fabiendupont@5070b58 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
@agrare Commit squashed. |
This adds colums to model V2V throttling limits at conversion host level.