OpenAthens LA support ended on 31 March 2020

Search

Skip to end of metadata
Go to start of metadata

Your licence allows you to use as many runtimes as you need to so things like test infrastructures, load balancing and disaster recovery do not have any constraints.

In the case of test infrastructure, you will want a dedicated administration console for it, but for things like load balancing or disaster recovery the same administration console can publish to as many runtimes as you want to connect - it is up to you which of them you route traffic to at any given time.

Sharing session information

If you are load balancing, you can use memcache to share session information between runtimes so that the user only has to authenticate once.

This is set up on each of the IdP runtimes as follows:

  1. Access the runtime with the maint account

  2. Open the openathensla-runtime.conf.local file for editing

    sudo nano /etc/httpd/conf.d/openathensla-runtime.conf.local
  3. Towards the end of the file you should see this text:

    #Use local memcached server as session store
     
    OASessionBackend memcached
     
    OAMemcachedServers 127.0.0.1
  4. Replace the home IP (127.0.0.1) with a list of all the machines which will be sharing session information. This list must be in the same order on each machine and ports may be specified if necessary, e.g:

    OAMemcachedServers 192.168.33.112, 192.168.33.113, runtime1.oala.example, runtime2.oala.example:12345
  5. Restart Apache

    sudo service httpd restart

You do not need to share session information with or amongst dedicated proxy runtimes as they will reference the IdP server(s).

A simple method of load balancing runtimes is a DNS round robin.

Dedicated proxy runtimes

If you wish to load balance proxy servers, you do not have to make any changes to the runtime but your load balancer should either maintain the session information for the user, or route the user to a consistent server for the duration of their session.

  • No labels