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

Support load-balance proxy groups? #11

Open
bedroge opened this issue Jun 10, 2020 · 2 comments
Open

Support load-balance proxy groups? #11

bedroge opened this issue Jun 10, 2020 · 2 comments
Labels
configuration Improvements or additions to the configuration documentation Improvements or additions to documentation

Comments

@bedroge
Copy link
Collaborator

bedroge commented Jun 10, 2020

The current setup only allows you to specify proxy groups with one entry per group, by using semicolon separated entries for the proxy list. By using pipes, you can also define multiple proxies per group; this will then act as a load-balance group, see:
https://cvmfs.readthedocs.io/en/2.2/cpt-configure.html#proxy-lists
Do we want/need this? Only seems to make sense if you have more than two proxies per site, e.g. two clusters with two proxies per cluster.

@boegel
Copy link
Contributor

boegel commented Jun 25, 2020

This could be interesting for large sites with lots of different systems, I guess...

I can imagine that we would set up a proxy per cluster for example, but I haven't checked with our sysadmins.

For now, a single proxy is probably fine, certainly for the pilot.

The Ansible stuff is useful (both to make it easy and as "reference implementation"), but I doubt we would use this for a production setup, we would integrate the CVMFS configuration in our own system (which uses Quattor).

@rptaylor
Copy link

The 2.2 documentation is old, there are some more examples in the latest version explaining the difference between semicolon and pipe: https://cvmfs.readthedocs.io/en/latest/cpt-configure.html#proxy-list-examples

@bedroge bedroge added configuration Improvements or additions to the configuration documentation Improvements or additions to documentation labels Jan 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
configuration Improvements or additions to the configuration documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants