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

Add reference documentation outlining the cluster architecture #31

Open
NucciTheBoss opened this issue Feb 5, 2025 · 0 comments
Open
Assignees
Labels
C-filesystem Component: Filesystem C-idm Component: Identity Management C-slurm Component: Slurm P-high Priority: Issue needs addressed within a two week pulse

Comments

@NucciTheBoss
Copy link
Member

Now that we have the Underlying projects and dependencies reference documentation which paints a better picture of all the different bits and bytes that come together to form a Charmed HPC cluster, we also need reference documentation that helps users create an accurate mental model of what a Charmed HPC cluster looks like. We should have a diagram that outlines how the Kubernetes and Machine clouds play together, and where the different Juju applications are located within the cluster.

Mermaid currently isn't an option because the accessibility isn't great, so we'll have to come up with something for rendering what the Charmed HPC cluster architecture is. I have this diagram from previous presentations that outlines where we're going:

Image

However, it would be great to have something that maps out all the integrations between the different deployed applications and how they talk to each other.

@NucciTheBoss NucciTheBoss added C-filesystem Component: Filesystem C-idm Component: Identity Management C-slurm Component: Slurm P-high Priority: Issue needs addressed within a two week pulse labels Feb 5, 2025
@NucciTheBoss NucciTheBoss self-assigned this Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-filesystem Component: Filesystem C-idm Component: Identity Management C-slurm Component: Slurm P-high Priority: Issue needs addressed within a two week pulse
Projects
None yet
Development

No branches or pull requests

1 participant