-
Notifications
You must be signed in to change notification settings - Fork 2k
qemu: add emulator allowlist to driver config and add emulator validadation #27182
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: main
Are you sure you want to change the base?
Conversation
tgross
left a comment
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.
There are some failing tests which I think cover the case where the user hasn't provided an explicit emulator argument
This change removed the fingerprint emulator config parameter and instead fingerprints all available emulators or those defined in the allowlist, and adds them to the drivers attribute, allowing placement contraints if nodes have different emulators installed.
gulducat
left a comment
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.
lookin pretty good! nice to see qemu getting some love.
couple comments for ya
Description
These changes add the ability for nomad operators to specify a qemu emulator allowlist for fingerprinting and tasks. If no allowlist is specified, the driver fingerprints all available emulators. Additionally, the emulators are added to a new node attribute
driver.qemu.emulatorswhich enables using contraints to VM's on nodes with specific emulators, as this functionality is not yet built into the scheduler.Removed the
fingerprint_emulatorconfig, which was added in #27128.Testing & Reproduction steps
Links
Contributor Checklist
changelog entry using the
make clcommand.ensure regressions will be caught.
and job configuration, please update the Nomad product documentation, which is stored in the
web-unified-docsrepo. Refer to theweb-unified-docscontributor guide for docs guidelines.Please also consider whether the change requires notes within the upgrade
guide. If you would like help with the docs, tag the
nomad-docsteam in this PR.Reviewer Checklist
backporting document.
in the majority of situations. The main exceptions are long-lived feature branches or merges where
history should be preserved.
within the public repository.
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.