-
Notifications
You must be signed in to change notification settings - Fork 7
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
recipe for cluster which does not use virtualbox, uses an alternative, possibly lighter-weight provider #18
Comments
a lighter-weight node would be cool for running a lot of nodes on Neutron, but this is lower priority for me than node recipes. |
kvm/libvirt is desirable, based on user input |
#18 programmatically compile Vagrantfile & cluster-internal from virtualization provider
libvirt is functional, and provides the desirable feature of less context switching, less I/O and possibly others, at the expense of some existent libvirt bugs (#158 "Waiting for domain to be assigned IP address") |
future functionality will address aspects of this:
|
The ideal provider would be able to be run within an existing HPC job allocation, on an existing, unmodified HPC cluster.
Use case: on-going in-pipeline validation of upcoming, scheduled HPC changes
The text was updated successfully, but these errors were encountered: