Repository navigation
M #-: Open OnDemand guide in the Slurm chapter - #1013
Merged
Merged
Conversation
3 tasks
3 tasks done
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>
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
approved these changes
Oct 13, 2026
mattrowe-opennebula
approved these changes
Oct 14, 2026
rsmontero
pushed a commit
that referenced
this pull request
Oct 14, 2026
This adds the Open OnDemand guide to the Slurm chapter, under a new Integrations section, as in the OneSlurm documentation structure proposed on 5 October. Open OnDemand is now a one-VM appliance in the OpenNebula Public Marketplace that works as a web portal for OneSlurm clusters (OpenNebula/one-apps#400, OpenNebula/marketplace#177). The page covers how the portal works, the requirements, the deployment from Sunstone and the CLI, what users see, adding users and clusters, security, troubleshooting and the known limitations. Every step was tested on OpenNebula 7.4 with two OneSlurm clusters, and the screenshots come from that test. It also removes the old Open OnDemand blueprint under Solutions, which described the earlier OneFlow service from the Community Marketplace. Its URLs redirect to the new page with Hugo aliases. The marketplace link on the page works once OpenNebula/marketplace#177 is merged. Co-authored-by: mattrowe-opennebula <mrowe@opennebula.io> (cherry picked from commit 2d5d84c)
rsmontero
pushed a commit
that referenced
this pull request
Oct 14, 2026
This adds the Open OnDemand guide to the Slurm chapter, under a new Integrations section, as in the OneSlurm documentation structure proposed on 5 October. Open OnDemand is now a one-VM appliance in the OpenNebula Public Marketplace that works as a web portal for OneSlurm clusters (OpenNebula/one-apps#400, OpenNebula/marketplace#177). The page covers how the portal works, the requirements, the deployment from Sunstone and the CLI, what users see, adding users and clusters, security, troubleshooting and the known limitations. Every step was tested on OpenNebula 7.4 with two OneSlurm clusters, and the screenshots come from that test. It also removes the old Open OnDemand blueprint under Solutions, which described the earlier OneFlow service from the Community Marketplace. Its URLs redirect to the new page with Hugo aliases. The marketplace link on the page works once OpenNebula/marketplace#177 is merged. Co-authored-by: mattrowe-opennebula <mrowe@opennebula.io> (cherry picked from commit 2d5d84c)
2 tasks done
rsmontero
pushed a commit
that referenced
this pull request
Oct 16, 2026
This splits the Open OnDemand guide of #1013 into five pages (Overview, Requirements, Quick Start, Operations, and Troubleshooting and Limitations), one for each document type of the wiki. The content is the same. The deployment steps now use `## Step N:` headings, and each page links to the next one. The current URL is now the index of the section, and the aliases of the old Open OnDemand blueprint point to the matching page. Co-authored-by: mattrowe-opennebula <mrowe@opennebula.io>
rsmontero
pushed a commit
that referenced
this pull request
Oct 16, 2026
This splits the Open OnDemand guide of #1013 into five pages (Overview, Requirements, Quick Start, Operations, and Troubleshooting and Limitations), one for each document type of the wiki. The content is the same. The deployment steps now use `## Step N:` headings, and each page links to the next one. The current URL is now the index of the section, and the aliases of the old Open OnDemand blueprint point to the matching page. Co-authored-by: mattrowe-opennebula <mrowe@opennebula.io> (cherry picked from commit e74cd69)
rsmontero
pushed a commit
that referenced
this pull request
Oct 16, 2026
This splits the Open OnDemand guide of #1013 into five pages (Overview, Requirements, Quick Start, Operations, and Troubleshooting and Limitations), one for each document type of the wiki. The content is the same. The deployment steps now use `## Step N:` headings, and each page links to the next one. The current URL is now the index of the section, and the aliases of the old Open OnDemand blueprint point to the matching page. Co-authored-by: mattrowe-opennebula <mrowe@opennebula.io> (cherry picked from commit e74cd69)
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>
mattrowe-opennebula
added a commit
that referenced
this pull request
Oct 22, 2026
This adds the Open OnDemand guide to the Slurm chapter, under a new Integrations section, as in the OneSlurm documentation structure proposed on 5 October. Open OnDemand is now a one-VM appliance in the OpenNebula Public Marketplace that works as a web portal for OneSlurm clusters (OpenNebula/one-apps#400, OpenNebula/marketplace#177). The page covers how the portal works, the requirements, the deployment from Sunstone and the CLI, what users see, adding users and clusters, security, troubleshooting and the known limitations. Every step was tested on OpenNebula 7.4 with two OneSlurm clusters, and the screenshots come from that test. It also removes the old Open OnDemand blueprint under Solutions, which described the earlier OneFlow service from the Community Marketplace. Its URLs redirect to the new page with Hugo aliases. The marketplace link on the page works once OpenNebula/marketplace#177 is merged. Co-authored-by: mattrowe-opennebula <mrowe@opennebula.io>
mattrowe-opennebula
added a commit
that referenced
this pull request
Oct 22, 2026
This splits the Open OnDemand guide of #1013 into five pages (Overview, Requirements, Quick Start, Operations, and Troubleshooting and Limitations), one for each document type of the wiki. The content is the same. The deployment steps now use `## Step N:` headings, and each page links to the next one. The current URL is now the index of the section, and the aliases of the old Open OnDemand blueprint point to the matching page. 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 adds the Open OnDemand guide to the Slurm chapter, under a new Integrations section, as in the OneSlurm documentation structure proposed on 5 October. Open OnDemand is now a one-VM appliance in the OpenNebula Public Marketplace that works as a web portal for OneSlurm clusters (OpenNebula/one-apps#400, OpenNebula/marketplace#177).
The page covers how the portal works, the requirements, the deployment from Sunstone and the CLI, what users see, adding users and clusters, security, troubleshooting and the known limitations. Every step was tested on OpenNebula 7.4 with two OneSlurm clusters, and the screenshots come from that test.
It also removes the old Open OnDemand blueprint under Solutions, which described the earlier OneFlow service from the Community Marketplace. Its URLs redirect to the new page with Hugo aliases. The marketplace link on the page works once OpenNebula/marketplace#177 is merged.
Branches to which this PR applies