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

Attractor interface config to support IP ranges #321

Closed
zolug opened this issue Nov 17, 2022 · 1 comment
Closed

Attractor interface config to support IP ranges #321

zolug opened this issue Nov 17, 2022 · 1 comment

Comments

@zolug
Copy link
Collaborator

zolug commented Nov 17, 2022

Supporting multiple Trenches (Attractors) sharing the same VLAN network requires some coordination when it comes to assigning IPs to external interfaces of FEs (to avoid duplicated IPs).

Describe the solution you'd like
One possible way doing so is to split the IP network into IP ranges and distribute said ranges between the respective Attractors.

It requires changes in the Remote VLAN NSE to support IP ranges as well: networkservicemesh/cmd-nse-remote-vlan#110

Describe alternatives you've considered
A centralized NSE that would serve multiple Attractors based on some shared property (like e.g. VLAN ID and network) could work as well in theory. But It would require major changes. And it would be hard or almost impossible to coordinate independent Meridio installations.

@zolug
Copy link
Collaborator Author

zolug commented Aug 13, 2024

VLAN NSE configuration is obsolete. Network Attachment Definition based Attractor config can support this out of the box depending on the chosen IPAM CNI (e.g. Whereabouts).

@zolug zolug closed this as not planned Won't fix, can't repro, duplicate, stale Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

1 participant