-
-
Notifications
You must be signed in to change notification settings - Fork 215
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
Cluster-wide baseline CPU definition for virtual machines #486
Comments
Im interested in working on this issue, can I be assigned to it please? |
This one we'll do in two stages as I'm not entirely sure about how I want to go around the second stage yet :) For the first stage, what we need is expose the CPU flags/extensions in our resources API as that will be needed to actually compare all servers and see what flags/extensions they all have in common (within one CPU architecture). So for stage one, you'll want to:
That should result in the following commits:
This one is pretty easy to test at least, once you're running an updated |
Is this still being worked on? If not, I'd love to take it! |
Yes we are still working on it 👍 |
Currently our live-migration logic assumes that all servers are the same and that instances can be migrated to any other server within the cluster so long as they are of the same CPU architecture.
That's obviously not correct as variation in CPU features will cause live-migration to fail.
To resolve this, we should do two things:
migration.stateful=true
).The text was updated successfully, but these errors were encountered: