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

chore(slurmctld): use peer relation for ingress ip #44

Conversation

jamesbeedy
Copy link
Contributor

These changes add a peer relation for the slurmctld charm and
replace using the slurmd interface to obtain the ingress_address
with the new slurmctld-peer relation.

The reason for this change is that we do not want to depend on
the existence of the slurmd relation in order to know our ip.

Using a peer relation we will always have resolvability so long as
juju knows the ip address of the unit.

These changes remove the unused "cluster_name" from the relation
data sent to slurmd on the slurmd relation. Additionally, make the
"cluster_name" property private.
These changes add a peer relation for the slurmctld charm and
replace using the slurmd interface to obtain the ingress_address
with the new slurmctld-peer relation.

The reason for this change is that we do not want to depend on
the existence of the slurmd relation in order to know our ip.

Using a peer relation we will always have resolvability so long as
juju knows the ip address of the unit.
@NucciTheBoss NucciTheBoss self-requested a review November 25, 2024 17:42
Copy link
Member

@NucciTheBoss NucciTheBoss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with merge conflicts resolved! It will be nice to have slurmctld-peer available for Slurm HA.

Will make sure second round of integration tests pass before merging.

@NucciTheBoss NucciTheBoss merged commit 70657d6 into charmed-hpc:main Nov 25, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants