F #-: Add the Open OnDemand platform service chapter - #942
Closed
pablodelarco wants to merge 30 commits into
Closed
pablodelarco wants to merge 30 commits into
pablodelarco wants to merge 30 commits into
Conversation
…reenshots, configuration, operations
… and keeping the home
…he architecture diagram
… provider, GPU role prepared
…x pages with the Sunstone wizard
…eenshots The quick start now explains the two Virtual Networks before the wizard and shows how to create the compute one in Sunstone. The Service Inputs step is described tab by tab with the redesigned inputs of appliance 1.0.0-20260916, where every input is optional and each optional feature sits behind a switch. Configuration regroups the inputs by tab and adds the advanced attributes. Screenshots retaken on the rebuilt appliance. (cherry picked from commit af37441)
… help icons mentioned (cherry picked from commit 217bfc3)
…s, two-column input tables, access from outside the management network (cherry picked from commit 63fef7f)
…nt network, uid optional in the initial users (cherry picked from commit 4536111)
…he service The portal runs the controller and the accounting, every worker joins as a dynamic node, the forms ask for cores, memory and GPUs, the pool grows on pending jobs and the oldest worker drains before OneFlow removes it. The wizard loses the Slurm tab and an external cluster becomes an advanced attribute. (cherry picked from commit 061b03e)
…rm design, shorter Networks section (cherry picked from commit 702f2a1)
…apter pattern Shorter sentences and common words on the six pages, every value, command and heading kept. Dates removed from the measurements. The chapter index carries one paragraph in the body, as the Elastic Slurm chapter does, and says that the service runs its own Slurm cluster.
2 tasks
…U model, faster scale up The overview explains Slurm, munge and MPI for a reader who does not know them, the configuration page shows an MPI job on two workers, the scale up cooldown is 180 seconds and the requirements name the host CPU passthrough. Two troubleshooting cases added: a service stuck in DEPLOYING_NETS and a worker started before its portal.
…erval recommended
Contributor
Author
|
Replaced by #951 against master, where the Solutions section for the blueprint lives. |
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
1 participant
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.
Adds the Open OnDemand chapter under Platform Services, in the structure of the OneKS and Slurm chapters: Overview, Service Architecture, Quick Start, Configuration, Operations, and Monitoring and Troubleshooting.
The chapter documents the Open OnDemand appliance and OneFlow service proposed for the Community Marketplace in OpenNebula/marketplace-community#132. It covers the three roles (storage, portal, worker), the two Virtual Networks, the Sunstone wizard with screenshots, the Slurm cluster the service runs (the portal as controller, every worker a dynamic node, every session a Slurm job with its own cores and memory), the elasticity of the worker pool driven by the Slurm queue, an external Slurm cluster as a second target, the metrics exporter, and the troubleshooting paths. Everything described was run on an OpenNebula 7.4 testbed.
Files touched:
content/platform_services/open_ondemand/andassets/images/open_ondemand/. The architecture diagram is an SVG with light and dark variants. The branch builds clean withhugoon top ofone-7.4, and every internal link resolves; the same commits apply tomasterwithout conflicts if you want it in devel as well.