-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
openstack: Add flavor selection support. #788
openstack: Add flavor selection support. #788
Conversation
/retest |
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 tried this with vexxhost (which doesnt have m1.medium flavor), and it worked great.
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 would prefer not to add more prompts. OpenStack already has a few too many. We should instead default and let users override that in their install-config. AWS, for example, doesn't have a prompt for changing the instance type.
return nil | ||
}), | ||
}, | ||
"OPENSHIFT_INSTALL_OPENSTACK_COMPUTE_FLAVOR", |
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.
This is going to conflict with #861. We are removing environment variables.
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 can fix this up once that lands.
As for this being a prompt or not, the difference between AWS and OpenStack is whether it's possible to pick a sane default. With AWS, we know what the flavors are, but for OpenStack, it's not standardized at all.
12070b2
to
2646401
Compare
Rebased on master. As noted in my last comment, I still think this is required since it's a case where there's no obvious default since flavors (instance types) are not standardized across clouds. The best alternative I can think of is to write some logic to examine what flavors exist and try to pick one that looks like it has enough resources (CPU/RAM/disk). That doesn't seem great either, though. |
Hmmmm, I guess this is the best approach then. |
/lgtm |
oh, it's got a conflict 😢 |
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
2646401
to
9d21f4c
Compare
@flaper87 rebased |
oops, something is wrong with the new test code ... /hold |
9d21f4c
to
66f7ba9
Compare
/hold cancel |
OpenStack flavors (analogous to AWS instance types) are not standardized, so we can't pick a default that works across all environments. This patch adds this as one of the items that must be specified.
/retest |
66f7ba9
to
aa4fd89
Compare
/test e2e-aws |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flaper87, russellb The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Please review the full test history for this PR and help us cut down flakes. |
OpenStack flavors (analogous to AWS instance types) are not
standardized, so we can't pick a default that works across all
environments. This patch adds this as one of the items that must be
specified.