File:
[LON-CAPA] /
loncom /
html /
adm /
help /
tex /
Domain_Configuration_Load_Balancing.tex
Revision
1.4:
download - view:
text,
annotated -
select for diffs
Thu Mar 30 02:08:31 2017 UTC (7 years, 4 months ago) by
raeburn
Branches:
MAIN
CVS tags:
version_2_12_X,
version_2_11_X,
version_2_11_5_msu,
version_2_11_5,
version_2_11_4_uiuc,
version_2_11_4_msu,
version_2_11_4,
version_2_11_3_uiuc,
version_2_11_3_msu,
version_2_11_3,
version_2_11_2_uiuc,
version_2_11_2_msu,
version_2_11_2_educog,
version_2_11_2,
HEAD
- Document option to host user sessions on a load balancer node.
1: \label{Domain_Configuration_Load_Balancing}
2:
3: A ``Dedicated Load Balancer(s)'' option will be included in the list of modifiable domain settings if your LON-CAPA domain contains more than one server or VM.
4:
5: If you chose to designate one of your servers/VMs as a load balancer, you can configure balancing behavior as follows:
6:
7: \begin{itemize}
8:
9: \item Default destinations
10:
11: This determines which of your servers/VMs will host user sessions (by default) after log-in via the load balancer server/VM. You can separate destinations into ``primary'' and ``default''.
12: The least loaded of the primary servers/VMs will be selected, unless all primary servers/VMs are considered 100\% loaded, in which case the least loaded of the default servers/VMs will be selected.
13:
14: You can also permit hosting on the load balancer node itself, by selecting primary or default for ``Hosting on balancer itself'', in which case determination of least loaded for the particular grouping will also include the load balancer.
15:
16: \item User affiliation -- overrides
17:
18: The choice of server/VM to host user sessions for particular types of user can be further configured, by choosing an action for particular user types. The chosen action will override the default behavior. The choice of user types includes the various affiliations defined for the institution (e.g., Faculty, Staff etc.). If users are not affiliated with any institutional group, they can be accommodated within the default {}``Other users'' type which is provided automatically. If no status types are defined for your domain, this default group is entitled {}``All users''.
19:
20: In addition to type based on affiliation, there are additional types:
21:
22: \begin{itemize}
23:
24: \item Advanced users from domain (i.e., users with author, coordinator, instructor or administrator roles)
25:
26: \item Users from domain with author role
27:
28: \end{itemize}
29:
30: If an institution runs a library server with multiple domains, the server selected to be the load balancer can be different from the particular domain for which balancing is being configured. Two other additional types are available where the load balancer's domain and domain being configured match:
31:
32: \begin{itemize}
33:
34: \item Users not from domain, but with a home server matching institution's web address (e.g., yourcollege.edu)
35:
36: \item Users not from domain or with a home server matching institution's web address web address
37:
38: \end{itemize}
39:
40: In all but the last case, the options available are:
41:
42: \begin{itemize}
43:
44: \item Offloads to default destinations
45:
46: \item Offloads to user's home server
47:
48: \item Offloads to a specific server in the user's domain (select froma dropdown list)
49:
50: \item No offload
51:
52: \end{itemize}
53:
54: In the last case (i.e., users whose home domain is not on any of the servers/VMs you manage), the options are:
55: (a) Offloads to default destinations, (b) Offloads to user's home server, (c) Offloads to Load Balancer in user's domain,
56: (d) No offload
57:
58: \item User's remote IP address changes between log-in to load balancer server, and session initialization on offload server
59:
60: LON-CAPA expects the remote IP address of the client web request to be the same at the authentication stage on the load balancer, and then subsequently, following
61: attempted session migration to the offload server. Where IPs do not match (e.g., a user is accessing LON-CAPA using an internet connection provided by a
62: cellular network, where IP addresses are pooled and can change between requests), you can set how that situation should be handled. The options are:
63:
64: \begin{itemize}
65:
66: \item Session hosted on Load Balancer, after re-authentication
67:
68: \item Session hosted on offload server, after re-authentication
69:
70: \item Session hosted on a specified server (selected from the domain's servers), after re-authentication
71:
72: \end{itemize}
73:
74: If the load balancing server's domain and the domain being configured are the same, you will select one of these options separately for
75: (a) Single Sign On (SSO) users from your domain, and also (b) for both non-SSO users from your domain, and for users from other domains in the LON-CAPA network (if you have joined a cluster). If your institution maintains multiple domains then a load balancer can have a different domain from the domain you are currently configuring. In that instance you will select one of these options separately for (a) SSO users from your domain and (b) non-SSO users from your domain.
76:
77: \end{itemize}
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>