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

compute nodes with fixed ip or shutdown instead of terminating compute nodes #6620

Open
cezfer opened this issue Dec 11, 2024 · 5 comments
Open

Comments

@cezfer
Copy link

cezfer commented Dec 11, 2024

I have an HPC cluster that uses licensed software and one of the licensing parameters is the IP of the compute nodes. I read the documentation and I didn't find a way to specify the IP that the compute node should be created on or instead of terminating the node just turn it off. Is there any way to configure this?

@hgreebe
Copy link
Contributor

hgreebe commented Jan 2, 2025

Hello,
There is no way to specify the ip address of a compute node, but you can use pre/post install scripts to assign secondary ip to the compute node.

Currently, our configuration is to terminate compute nodes if they are down, so they can not just be "turned off".

@cezfer
Copy link
Author

cezfer commented Jan 2, 2025 via email

@hgreebe
Copy link
Contributor

hgreebe commented Jan 7, 2025

If you manually change the launch template, and subsequent update may change it back. I believe slurm allows other ways to license: https://slurm.schedmd.com/licenses.html

@cezfer
Copy link
Author

cezfer commented Jan 13, 2025 via email

@hanwen-cluster
Copy link
Contributor

Even if you stop and start the instance, the IPs will change. The best way is to use secondary IP addresses or keep the compute nodes running all the time.

Would you like this to become a feature request? If yes, could you provide more context (e.g. cluster configuration file, why secondary IP addresses cannot solve the problem)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants