User Tools

Site Tools


wiki:advanced:x2gobroker:loadbalancing

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
wiki:advanced:x2gobroker:loadbalancing [2013/07/02 01:09]
sunweaver
wiki:advanced:x2gobroker:loadbalancing [2016/02/23 16:09] (current)
ionic Make the note a real note.
Line 30: Line 30:
 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. 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'').+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: After you have installed the session broker, additionally run the script ''x2gobroker-keygen'' as super-user root:
Line 47: Line 47:
  
 <code bash> <code bash>
-$ sudo x2gobroker-pubkeyauthorizer --broker-url http(s)://<broker-server>:<port>/<basepatch>/pubkeys/+$ sudo x2gobroker-pubkeyauthorizer --broker-url http(s)://<broker-server>:<port>/<basepath>/pubkeys/
 </code> </code>
 +
 +<note>''<basepath>'' typically is empty, unless the front- and backends were moved to a specific subdirectory as part of a WSGI deployment.</note>
  
  
Line 66: Line 68:
 </file> </file>
  
-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):+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 examples above and below):
  
 <file> <file>
 host=s-1.works-with-broker.local (s-1.works-with-client.extern), s-2.works-with-broker.local (s-2.works-with-client.extern) host=s-1.works-with-broker.local (s-1.works-with-client.extern), s-2.works-with-broker.local (s-2.works-with-client.extern)
 </file> </file>
 +
 +The hostnames (no IP addresses allowed here) that work with the broker should identically match the hostnames of the X2Go Servers as found in ''/etc/hostname'' of each individual machine. The hostname also appear in the output of the ''x2golistsessions'' command. It is important that hostname patterns (FQDN, short hostnames) match here!!!
 +
 +The hostnames (or maybe IP addresses) that work with the clients must resolve via DNS. IP addresses are allowed here.
  
wiki/advanced/x2gobroker/loadbalancing.1372727382.txt.gz ยท Last modified: 2013/07/02 01:09 by sunweaver