-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Switch to globally available Hetzner instance type #14762
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
base: master
Are you sure you want to change the base?
Conversation
The old cx* Intel instance type was only available in EU data centers. The cpx* AMD type is available in the US and Asia as well.
config.cfg
Outdated
@@ -206,7 +206,7 @@ cloud_providers: | |||
image: Ubuntu 22.04 Jammy Jellyfish | |||
arch: x86_64 | |||
hetzner: | |||
server_type: cx22 | |||
server_type: cpx21 |
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.
We should probably use CPX11 instead of CPX21 by default. People who need more resources can opt for an upgrade.
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'm not sure what the resource requirements are, and they don't map neatly between Intel and AMD types, so I guessed the cpx21 was the closest to the cx22.
CI is failing but it looks unrelated. It's complaining about dpkg locks. Want me to retrigger it with a dummy commit? |
The old cx* Intel instance types are only available in EU data centers. The cpx* AMD types are available in the US and Asia as well.
Description
Motivation and Context
Fixes #14562 for the moment.
How Has This Been Tested?
I replaced the default with cpx11 and verified that that the cpx type worked in Hetzner's US data center.
Types of changes
Checklist: