-
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
Upgrade guide #39
Comments
Upgrade is complex, we will have to support a lot of scenarios, and most of the time this will breaks the cluster. Perhaps include some tips will be a good idea |
It sounds like a guide is warranted, then. When you say that most of the time upgrading will break the cluster, does that mean that it can break for surprising and unforeseen reasons (so it's better to avoid upgrading)? Or does it just mean that you have to be very careful when upgrading because there are lots of known problems (that we can describe ways to avoid)? |
We can probably list the issue that can occured. There is not so much in fact, but really depends on the setup already used in the cluster. |
When you have some time, could you provide info on the upgrade scenarios and the issues that can happen? No rush - this is low priority compared to the installation guide. |
Would it be worth having an Upgrade Guide?
The first step would just be a link to the SLES Upgrade Guide, but then Slurm needs to be upgraded manually. Are there any other HPC-specific upgrade or post-upgrade tasks that would make a guide (or article) worthwhile? Maybe you can use pdsh to help upgrade the compute nodes?
The text was updated successfully, but these errors were encountered: