This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
wiki:advanced:x2gobroker:loadbalancing [2013/07/02 00:49] sunweaver |
wiki:advanced:x2gobroker:loadbalancing [2013/07/02 01:10] sunweaver [X2Go Session Broker Daemon / WSGI] |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | |||
+ | |||
====== Load Balancing with X2Go ====== | ====== Load Balancing with X2Go ====== | ||
Line 23: | Line 25: | ||
you should get all current active/ | you should get all current active/ | ||
+ | |||
+ | ===== X2Go Session Broker Daemon / WSGI ===== | ||
+ | |||
+ | Install X2Go Session Broker [[doc: | ||
+ | |||
+ | You certainly want to make use of SSL (https protocol) if the session broker can be accessed from the internet or if you share your network with non-trusted machines. For large scale deployments the WSGI implementation of the broker is recommended (package: '' | ||
+ | |||
+ | After you have installed the session broker, additionally run the script '' | ||
+ | |||
+ | <code bash> | ||
+ | $ sudo x2gobroker-keygen | ||
+ | </ | ||
+ | |||
+ | This script will (if the defaults are not touched) create an RSA public/ | ||
+ | |||
+ | ===== X2Go Session Broker Agent ===== | ||
+ | |||
+ | On every X2Go Server install the package '' | ||
+ | |||
+ | To give the session broker access to your X2Go Servers, you have to run (as root) | ||
+ | |||
+ | <code bash> | ||
+ | $ sudo x2gobroker-pubkeyauthorizer --broker-url http(s)://< | ||
+ | </ | ||
+ | |||
+ | |||
+ | ===== X2Go Session Profile for Load Balanced Sites ===== | ||
+ | |||
+ | In the session profile configuration of the session broker (e.g. ''/ | ||
+ | |||
+ | Example: | ||
+ | |||
+ | < | ||
+ | [pool-C-XFCE] | ||
+ | user= | ||
+ | host=s-1.pool-e.local (10.0.2.11), | ||
+ | name=XFCE - pool-C | ||
+ | command=XFCE | ||
+ | broker-session-autologin=true | ||
+ | </ | ||
+ | |||
+ | It may happen that the broker contacts the X2Go servers under a different address compared to the address that the X2Go Clients have to use for connecting the X2Go Servers. For such cases, every hostname can be written in a special format (as seen in the example above): | ||
+ | |||
+ | < | ||
+ | host=s-1.works-with-broker.local (s-1.works-with-client.extern), | ||
+ | </ | ||
+ |