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.

Sign up for GitHub

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

Jump to bottom

Production variable control_ip_address is not implemented #642

Open
priteau opened this issue Apr 4, 2025 · 3 comments · May be fixed by #643
Open

Production variable control_ip_address is not implemented #642

priteau opened this issue Apr 4, 2025 · 3 comments · May be fixed by #643
Assignees
@priteau

Comments

@priteau
Copy link
Member

priteau commented Apr 4, 2025

The variable control_ip_address described in the Production Deployments documentation is not implemented.

It should also support multiple networks rather than a single fixed IP.
@priteau priteau self-assigned this Apr 4, 2025
priteau added a commit that referenced this issue Apr 4, 2025
@priteau
Support fixed IP addresses for control node
b3f0147 
The variable control_ip_address was documented but not implemented.
Since we support multiple networks, change it to control_ip_addresses
and implement it.

Closes #642.
@priteau priteau linked a pull request Apr 4, 2025 that will close this issue
Open
@sjpb
Copy link
Collaborator

sjpb commented Apr 4, 2025

No, as it says it is a new variable you'd have to add. I'm not actually sure the controi node needs to have a fixed ip. And logins only did because of ssh at a client without FIPs, which is unusual. I would like to discuss this internally before progressing, the linked PR I think is not right.

@sjpb
Copy link
Collaborator

sjpb commented Apr 4, 2025

Actually apologies I'd misread the ternary on the PR, it is functionally OK. Think it needs discussion though on whether this is actually the right thing to be doing.

@sjpb
Copy link
Collaborator

sjpb commented Apr 4, 2025

We did need to add fixed IPs for all nodes for a GPFS remotemount cluster. But I don't really want to support that in the default appliance, its too weird to do for multiple networks, I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@priteau priteau

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support fixed IP addresses for control node stackhpc/ansible-slurm-appliance
2 participants
@priteau @sjpb