Skip to content
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

Closed
ssenator opened this issue May 16, 2020 · 4 comments
Labels
summer institute https://docs.google.com/document/d/1HEWkCig6d6-heDXwzmEO81pB8lda9ie0AXOlzVDYTGc/edit user request

Comments

@ssenator
Copy link
Collaborator

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

@ssenator ssenator added the summer institute https://docs.google.com/document/d/1HEWkCig6d6-heDXwzmEO81pB8lda9ie0AXOlzVDYTGc/edit label Jun 11, 2020
@katyfelkner
Copy link

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.

@ssenator
Copy link
Collaborator Author

ssenator commented Jul 8, 2020

kvm/libvirt is desirable, based on user input

ssenator added a commit that referenced this issue Jul 22, 2020
#18 programmatically compile Vagrantfile & cluster-internal from virtualization provider
ssenator added a commit that referenced this issue Aug 3, 2020
ssenator added a commit that referenced this issue Aug 3, 2020
ssenator added a commit that referenced this issue Aug 3, 2020
ssenator added a commit that referenced this issue Aug 3, 2020
ssenator added a commit that referenced this issue Aug 3, 2020
ssenator added a commit that referenced this issue Aug 3, 2020
ssenator added a commit that referenced this issue Aug 3, 2020
ssenator added a commit that referenced this issue Aug 3, 2020
ssenator added a commit that referenced this issue Aug 3, 2020
ssenator added a commit that referenced this issue Aug 3, 2020
@ssenator
Copy link
Collaborator Author

ssenator commented Aug 9, 2020

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")

@ssenator ssenator closed this as completed Aug 9, 2020
@ssenator
Copy link
Collaborator Author

ssenator commented Aug 9, 2020

future functionality will address aspects of this:

  1. use of whole-node or multi-node snapshots and/or vagrant box creation and
  2. porous membranes (containers) rather than virtual-machine implementations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
summer institute https://docs.google.com/document/d/1HEWkCig6d6-heDXwzmEO81pB8lda9ie0AXOlzVDYTGc/edit user request
Projects
None yet
Development

No branches or pull requests

2 participants