[X2Go-Commits] page changed: wiki:advanced:x2gobroker:loadbalancing

[wiki-admin at x2go.org]

A page in your DokuWiki was added or changed. Here are the details:

Date        : 2013/07/02 01:05
Browser     : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1
IP-Address  : 87.180.204.24
Hostname    : p57B4CC18.dip0.t-ipconnect.de
Old Revision: http://wiki.x2go.org/doku.php/wiki:advanced:x2gobroker:loadbalancing?rev=1372726149
New Revision: http://wiki.x2go.org/doku.php/wiki:advanced:x2gobroker:loadbalancing
Edit Summary: 
User        : sunweaver

@@ -1,4 +1,6 @@
+ 
+ 
  ====== Load Balancing with X2Go ======
  
  ===== Preparations =====
  
@@ -21,4 +23,44 @@
  <user>@<x2goserverN>:~$ x2golistsessions --all-servers
  </code>
  
  you should get all current active/suspended X2Go sessions listed.
+ 
+ ===== X2Go Session Broker Daemon / WSGI =====
+ 
+ Install X2Go Session Broker [[doc:installation:x2gobroker|as described]]. Use a non-X2Go Server for this as installation host (e.g. the central LDAP server). Choosing the right machine on your
network for providing X2Go session brokerage heavily depends on your site setup.
+ 
+ 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: ''x2gobroker-wsgi''). For small companies the standalone daemon should probably be fine (package: ''x2gobroker-daemon'').
+ 
+ After you have installed the session broker, additionally run the script ''x2gobroker-keygen'' as super-user root:
+ 
+ <code bash>
+ $ sudo x2gobroker-keygen
+ </code>
+ 
+ This script will (if the defaults are not touched) create an RSA public/private SSH key pair in ''~x2gobroker/.ssh/authorized_keys''.
+ 
+ ===== X2Go Session Broker Agent =====
+ 
+ On every X2Go Server install the package ''x2gobroker-agent''. This agent has to be handled with much care, as it gets installed setuid root. Be aware of that and read
its code before you deploy it. If you find any bugs or security issues with it, please [[wiki:bugs|contact the X2Go developers immediately (by sending a bug report)]] so that we can get things fixed for all as soon as possible.
+ 
+ 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)://<broker-server>:<port>/<basepatch>/pubkeys/
+ </code>
+ 
+ 
+ ===== X2Go Session Profile for Load Balanced Sites =====
+ 
+ In the session profile configuration of the session broker (e.g. ''/etc/x2go/x2gobroker-sessionprofiles.conf'') you now simply have to list all your X2Go Servers in a comma separated list with the ''host='' option of that session profile.
+ 
+ Example:
+ 
+ <file>
+ [pool-C-XFCE]
+ user=
+ host=s-E1 (10.0.2.11),s-E2 (10.0.2.12),s-E3 (10.0.2.13),s-E4 (10.0.2.14),s-E5 (10.0.2.15)
+ name=XFCE - pool-C
+ command=XFCE
+ broker-session-autologin=true
+ </file>



-- 
This mail was
generated by DokuWiki at
http://wiki.x2go.org/