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:23]
sunweaver [X2Go Session Profile for Load Balanced Sites]
wiki:advanced:x2gobroker:loadbalancing [2016/02/23 16:09]
ionic Make the note a real note.
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 71: Line 73:
 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.txt ยท Last modified: 2016/02/23 16:09 by ionic