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

accommodate multinode HPC allocation rather than single-node VM instantiation #237

Open
ssenator opened this issue Jan 26, 2021 · 0 comments
Assignees
Labels
beneficial/enabler Fixing this issue will enable multiple capabilities or provide benefit beyond the immediate problem. enhancement New feature or request

Comments

@ssenator
Copy link
Collaborator

To run a full model of an HPC cluster on an HPC cluster, we need to be able to create VMs on multiple nodes. However, the VM's on each node must be able to communicate with each other. Changes necessary:

  1. Change private network to a bridged interface, of the public host's NIC
  2. Allocate IP addresses systematically based on which node the VM will be created
  3. Create the infrastructure nodes on the first node allocated
  4. Create the compute nodes on other nodes in the allocation
  5. Consider removing the vcgate node and/or changing it to be a vcrtr heartbeat verification node
  6. Create additional verification tests, as required, mostly in prereq
@ssenator ssenator added enhancement New feature or request beneficial/enabler Fixing this issue will enable multiple capabilities or provide benefit beyond the immediate problem. labels Jan 26, 2021
@ssenator ssenator self-assigned this Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
beneficial/enabler Fixing this issue will enable multiple capabilities or provide benefit beyond the immediate problem. enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant