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

Zimfarm worker: add support for multiple outgoing IPs #959

Open
benoit74 opened this issue May 4, 2024 · 4 comments
Open

Zimfarm worker: add support for multiple outgoing IPs #959

benoit74 opened this issue May 4, 2024 · 4 comments

Comments

@benoit74
Copy link
Collaborator

benoit74 commented May 4, 2024

Currently, Zimfarm worker does not manage at all the outgoing traffic, meaning it uses whatever default route is configured in the OS.

When a worker has multiple public IP, we would benefit from taking advantage of that by spreading the task on the various public IPs available (which would be exposed as various adapters at the host level).

Not sure how much effort it would necessitate, and I think that we've just encountered the first worker which make take benefit from this new functionality, might well be an edge case.

@rgaudin
Copy link
Member

rgaudin commented May 4, 2024

Are the multiple IPs causing issues regarding whitelisting?

@benoit74
Copy link
Collaborator Author

benoit74 commented May 6, 2024

I don't think they are causing any issues, we are just defaulting to one of them in fact. Which is a bit of a pity since having multiple might help to run multiple tasks in // from multiple IPs

@rgaudin
Copy link
Member

rgaudin commented May 6, 2024

Sure, I just wanted to rule out any pressing issue that required an immediate fix

@benoit74
Copy link
Collaborator Author

benoit74 commented May 6, 2024

No immediate fix needed, not even sure it is worth it to implement at all, at least for the coming years. Quite an open question in fact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants