raeburn raeburn at source.lon-capa.org
Sat Dec 14 15:33:33 EST 2013

raeburn		Sat Dec 14 20:33:33 2013 EDT

Log:
- Documentation for domain configuration of load balancing where an
institution has more than one LON-CAPA server/VM.

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.

If you chose to designate one of your servers/VMs as a load balancer, you can configure balancing behavior as follows:

\begin{itemize}

\item Default destinations

This determines which of your servers will host user sessions (by default) after log-in via the load balancer server.  You can separate destinations into primary'' and default''.
The least loaded of the primary servers will be selected, unless all primary servers are considered 100\% loaded, in which case the least loaded of the default servers will be selected.

\item User affiliation -- overrides

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 \char\"{}Other users\char\"{} type which is provided automatically. If no status types are defined for your domain, this default group is entitled \char\"{}All users\char\"{}.

\begin{itemize}

\item Advanced users from domain (i.e., users with author, coordinator, instructor or administrator roles)

\item Users from domain with author role

\end{itemize}

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:

\begin{itemize}

\item Users not from domain, but with a home server matching institution's web address (e.g., yourcollege.edu)

\item Users not from domain or with a home server matching institution's web address web address

\end{itemize}

In all but the last case, the options available are:

\begin{itemize}

\item Offloads to user's home server

\item  Offloads to a specific server in the user's domain (select froma dropdown list)

\end{itemize}

In the last case (i.e., users whose home domain is not on any of the servers/VMs you manage), the options are:

\item User's remote IP address changes between log-in to load balancer server, and session initialization on offload server

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
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
cellular network, where IP addresses are pooled and can change between requests), you can set how that situation should be handled.  The options are:

\begin{itemize}

\item Session hosted on Load Balancer, after re-authentication

\item Session hosted on offload server, after re-authentication

\end{itemize}

If the load balancer's domain and domain being configured are the same, you will select one of these options separately for
Single Sign On (SSO) users from your domain, and also for non-SSO users from your domain.  If the load balancer has a different domain you will
only set ths option for SSO users from your domain.

\end{itemize}