Production variable control_ip_address is not implemented #642
Assignees
Comments
priteau
added a commit
that referenced
this issue
Apr 4, 2025
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.
|
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. |
|
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. |
|
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. |
sjpb
pushed a commit
that referenced
this issue
May 29, 2025
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The variable
control_ip_addressdescribed in the Production Deployments documentation is not implemented.It should also support multiple networks rather than a single fixed IP.
The text was updated successfully, but these errors were encountered: