Repository navigation
M #-: OneSlurm guide in the Slurm chapter - #1019
Merged
Merged
Conversation
tinova
approved these changes
Oct 8, 2026
mattrowe-opennebula
approved these changes
Oct 9, 2026
rsmontero
pushed a commit
that referenced
this pull request
Oct 13, 2026
This moves the OneSlurm guide from the one-apps wiki (slurm_intro, slurm_quick and slurm_feature) to the Slurm chapter, with the structure proposed on 5 October. - Getting Started: Overview, Requirements and Preparation, Quick Start and Core Concepts. The old `slurm/overview` page moves here, and its URL redirects with a Hugo alias. - Management: Cluster Lifecycle (including scaling), Cluster Configuration, Worker Profiles and Accelerators, Identity, Shared Storage, InfiniBand and Troubleshooting. - References: Service Architecture, Configuration Parameters, CLI and API. The API page shows the OneFlow REST calls for a OneSlurm cluster. I checked every statement against `appliances/OneSlurm` on one-apps master and the marketplace YAML. On OpenNebula 7.4 I tested the Quick Start from the CLI and from Sunstone, scaling up and down, the API calls, the local LDAP example and NFS `/home`. These tests corrected a few points from the wiki: - Workers take the VM name as hostname. - The CLI asks for the inputs before the network. - With the default `root_squash`, the home directories must be created on the NFS server. - `slurm.conf` is written again at every boot. - The API needs all the service inputs, and `force` when scaling. GPU and InfiniBand are migrated as written in the wiki, because I had no hardware to test them. The Integrations section with the Open OnDemand guide comes from #1013, and the two branches merge without conflicts. EESSI, CernVM-FS, External Identity and Storage and the multi-tenant content are not included yet. Co-authored-by: mattrowe-opennebula <mrowe@opennebula.io> (cherry picked from commit 9f40707)
rsmontero
pushed a commit
that referenced
this pull request
Oct 13, 2026
This moves the OneSlurm guide from the one-apps wiki (slurm_intro, slurm_quick and slurm_feature) to the Slurm chapter, with the structure proposed on 5 October. - Getting Started: Overview, Requirements and Preparation, Quick Start and Core Concepts. The old `slurm/overview` page moves here, and its URL redirects with a Hugo alias. - Management: Cluster Lifecycle (including scaling), Cluster Configuration, Worker Profiles and Accelerators, Identity, Shared Storage, InfiniBand and Troubleshooting. - References: Service Architecture, Configuration Parameters, CLI and API. The API page shows the OneFlow REST calls for a OneSlurm cluster. I checked every statement against `appliances/OneSlurm` on one-apps master and the marketplace YAML. On OpenNebula 7.4 I tested the Quick Start from the CLI and from Sunstone, scaling up and down, the API calls, the local LDAP example and NFS `/home`. These tests corrected a few points from the wiki: - Workers take the VM name as hostname. - The CLI asks for the inputs before the network. - With the default `root_squash`, the home directories must be created on the NFS server. - `slurm.conf` is written again at every boot. - The API needs all the service inputs, and `force` when scaling. GPU and InfiniBand are migrated as written in the wiki, because I had no hardware to test them. The Integrations section with the Open OnDemand guide comes from #1013, and the two branches merge without conflicts. EESSI, CernVM-FS, External Identity and Storage and the multi-tenant content are not included yet. Co-authored-by: mattrowe-opennebula <mrowe@opennebula.io> (cherry picked from commit 9f40707)
mattrowe-opennebula
added a commit
that referenced
this pull request
Oct 22, 2026
This moves the OneSlurm guide from the one-apps wiki (slurm_intro, slurm_quick and slurm_feature) to the Slurm chapter, with the structure proposed on 5 October. - Getting Started: Overview, Requirements and Preparation, Quick Start and Core Concepts. The old `slurm/overview` page moves here, and its URL redirects with a Hugo alias. - Management: Cluster Lifecycle (including scaling), Cluster Configuration, Worker Profiles and Accelerators, Identity, Shared Storage, InfiniBand and Troubleshooting. - References: Service Architecture, Configuration Parameters, CLI and API. The API page shows the OneFlow REST calls for a OneSlurm cluster. I checked every statement against `appliances/OneSlurm` on one-apps master and the marketplace YAML. On OpenNebula 7.4 I tested the Quick Start from the CLI and from Sunstone, scaling up and down, the API calls, the local LDAP example and NFS `/home`. These tests corrected a few points from the wiki: - Workers take the VM name as hostname. - The CLI asks for the inputs before the network. - With the default `root_squash`, the home directories must be created on the NFS server. - `slurm.conf` is written again at every boot. - The API needs all the service inputs, and `force` when scaling. GPU and InfiniBand are migrated as written in the wiki, because I had no hardware to test them. The Integrations section with the Open OnDemand guide comes from #1013, and the two branches merge without conflicts. EESSI, CernVM-FS, External Identity and Storage and the multi-tenant content are not included yet. Co-authored-by: mattrowe-opennebula <mrowe@opennebula.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This moves the OneSlurm guide from the one-apps wiki (slurm_intro, slurm_quick and slurm_feature) to the Slurm chapter, with the structure proposed on 5 October.
slurm/overviewpage moves here, and its URL redirects with a Hugo alias.I checked every statement against
appliances/OneSlurmon one-apps master and the marketplace YAML. On OpenNebula 7.4 I tested the Quick Start from the CLI and from Sunstone, scaling up and down, the API calls, the local LDAP example and NFS/home. These tests corrected a few points from the wiki:root_squash, the home directories must be created on the NFS server.slurm.confis written again at every boot.forcewhen scaling.GPU and InfiniBand are migrated as written in the wiki, because I had no hardware to test them.
The Integrations section with the Open OnDemand guide comes from #1013, and the two branches merge without conflicts. EESSI, CernVM-FS, External Identity and Storage and the multi-tenant content are not included yet.
Branches to which this PR applies