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

Allow for registration/isolation virtual IP to be on 1st node of cluster #6849

Closed
julsemaan opened this issue Jan 27, 2022 · 0 comments · Fixed by #6853
Closed

Allow for registration/isolation virtual IP to be on 1st node of cluster #6849

julsemaan opened this issue Jan 27, 2022 · 0 comments · Fixed by #6853
Assignees
@julsemaan
Labels
Type: Feature / Enhancement
Milestone
PacketFence-11.3

Comments

@julsemaan
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
When creating a dedicated load-balancer in a cluster, having the VIP for reg/isol on the 2nd server defeats the purpose of that use-case. We should have an option to make all VIP (mgmt+reg+isol+inline) to be on the 1st server of the cluster like it used to be

This new option would be disabled by default and would leave the reg+isol VIP on the 2nd server unless enabled which keeps the current behavior

Describe the solution you'd like
Add the setting to have all VIP be on the 1st server
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@julsemaan julsemaan

Labels
Type: Feature / Enhancement
Projects
None yet
Milestone
PacketFence-11.3
Development

Successfully merging a pull request may close this issue.

Allow to centralize the virtual IPs on the same server inverse-inc/packetfence
1 participant
@julsemaan