A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/07/02 01:09
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=13…
New Revision: http://wiki.x2go.org/doku.php/wiki:advanced:x2gobroker:loadbalancing
Edit Summary:
User : sunweaver
@@ -58,9 +58,16 @@
<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)
+ host=s-1.pool-e.local (10.0.2.11),s-2.pool-e.local (10.0.2.12),s-3.pool-e.local (10.0.2.13),s-4.pool-e.local (10.0.2.14),s-5.pool-e.local (10.0.2.15)
name=XFCE - pool-C
command=XFCE
broker-session-autologin=true
</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):
+
+ <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)
+ </file>
+
--
This mail was generated by DokuWiki at
http://wiki.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=13…
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/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/07/02 00:49
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=13…
New Revision: http://wiki.x2go.org/doku.php/wiki:advanced:x2gobroker:loadbalancing
Edit Summary:
User : sunweaver
@@ -1,5 +1,7 @@
====== Load Balancing with X2Go ======
+
+ ===== Preparations =====
The X2Go load balancing setup requires several installation steps.
- Install more than one X2Go Servers
@@ -10,4 +12,13 @@
* make sure DNS works well and all X2Go Servers resolve and reverse resolve fine
- Install PostgreSQL on a non-X2Go Server (i.e. on the machine that runs the LDAP service)
- [[wiki:advanced:multi-node:x2goserver-pgsql|Hook all X2Go Servers' session databases into the
PostgreSQL database server]]
+ You should now be able to log into each X2Go Server separately by using their IP addresses or (local) DNS names.
+
+ If you are logged into several of your X2Go Servers under the same user account and then run
+
+ <code bash>
+ <user>@<x2goserverN>:~$ x2golistsessions --all-servers
+ </code>
+
+ you should get all current active/suspended X2Go sessions listed.
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/07/02 00:46
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=13…
New Revision: http://wiki.x2go.org/doku.php/wiki:advanced:x2gobroker:loadbalancing
Edit Summary:
User : sunweaver
@@ -8,6 +8,6 @@
* central LDAP server with user accounts as authentication backend and user base (PAM, libnss)
* central NFS server for provisioning of home directories
* make sure DNS works well and all X2Go Servers resolve and reverse resolve fine
- Install PostgreSQL on a non-X2Go Server (i.e. on the machine that runs the LDAP service)
- - [[Hook all X2Go Servers' session databases into the PostgreSQL database server|wiki:advanced:multi-node:x2goserver-pgsql]]
+ -
[[wiki:advanced:multi-node:x2goserver-pgsql|Hook all X2Go Servers' session databases into the PostgreSQL database server]]
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/07/02 00:46
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=13…
New Revision: http://wiki.x2go.org/doku.php/wiki:advanced:x2gobroker:loadbalancing
Edit Summary:
User : sunweaver
@@ -1,3 +1,13 @@
====== Load Balancing with X2Go ======
- Soon to come...
+ The X2Go load balancing setup requires several installation steps.
+
+ - Install more than one X2Go Servers
+ - Install all X2Go Servers identically (FAI and/or puppet are good tools here)
+ - Hook them together:
+ * central LDAP server with user accounts as authentication backend and user base (PAM, libnss)
+ * central NFS server for provisioning of home directories
+ * make sure DNS works well and
all X2Go Servers resolve and reverse resolve fine
+ - Install PostgreSQL on a non-X2Go Server (i.e. on the machine that runs the LDAP service)
+ - [[Hook all X2Go Servers' session databases into the PostgreSQL database server|wiki:advanced:multi-node:x2goserver-pgsql]]
+
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/07/02 00:36
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/x2gobroker:inifilebackend?rev=1372725406
New Revision: http://wiki.x2go.org/doku.php/x2gobroker:inifilebackend
Edit Summary:
User : sunweaver
@@ -24,8 +24,21 @@
height=768
</file>
Note that every X2Go Client parameter not given here gets filled in from a [[http://code.x2go.org/gitweb?p=x2gobroker.git;a=blob;f=x2gobroker/defaults.p… default configuration]].
+
+ ===== Special Broker Functionalities =====
+
+ Some options in the ''x2gobroker-sessionprofiles.conf'' file are used to tweak the broker itself. The options are:
+
+ ==== Provisioning of SSH keys to X2Go Client / Servers ====
+
+ X2Go Session Broker normally requires two consecutive
logins. One against the session broker, the second against the X2Go Server that the X2Go session will be launched on. The second login (SSH login against X2Go Server) can be automated via the session broker and its agent. For activation of this feature, the special session profile option ''broker-session-autologin'' has to be set to ''true''.
+
+ * ''broker-session-autologin'': send a private SSH key to X2Go Client that the client then internally uses for SSH pub/priv key based authentication. The X2Go Session Broker will send the SSH public key via the X2Go Session Broker Agent to the X2Go Server
+ * ''broker-authorized-keys'' (optional, normally defaults are ok): full path to the server-side ''authorized_keys'' file (on the X2Go server)
+
+ If ''broker-session-autologin'' is activated, the session broker will create a temporary SSH pub/priv key pair, deploy the private key to X2Go Client and the public key to the X2Go Server that is targeted for X2Go session login.
=====
Filtering through Access Control List =====
If a user has been successfully authenticated against the X2Go Session Broker (or a user name has been given via the http request for cases where ''check-credentials'' in ''x2gobroker.conf'' is set to ''false'') you can use the user's UID, GID and the client address from that the user connects to filter out session profiles.
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/07/02 00:36
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/x2gobroker:inifilebackend?rev=1372725059
New Revision: http://wiki.x2go.org/doku.php/x2gobroker:inifilebackend
Edit Summary: [Special Broker Options]
User : sunweaver
@@ -86,12 +86,6 @@
* ''acl-clients-deny = ALL''
- ===== Special Broker Options =====
-
- Some options in the ''x2gobroker-sessionprofiles.conf'' file are used to tweak the broker itself. The options are:
-
- * ''broker-session-autologin'': send a private SSH key to X2Go Client that the client then internally uses for SSH pub/priv key based authentication. The X2Go Session Broker will send the SSH public key via the X2Go Session Broker Agent to the X2Go Server
- *
''broker-authorized-keys'': full path to the server-side ''authorized_keys'' file (on the X2Go server)
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/07/02 00:30
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/x2gobroker:inifilebackend?rev=1372725040
New Revision: http://wiki.x2go.org/doku.php/x2gobroker:inifilebackend
Edit Summary: [List of ACL rules]
User : sunweaver
@@ -81,9 +81,9 @@
* ''acl-groups-deny = ALL''
**Client ACLs:**
- * ''acl-clients-allow = <subnet-or-ip>, <or-dns-hostname>
+ * ''acl-clients-allow = <subnet-or-ip>, <or-dns-hostname>''
* ''acl-clients-deny = ALL''
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/07/02 00:30
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/x2gobroker:inifilebackend?rev=1372725007
New Revision: http://wiki.x2go.org/doku.php/x2gobroker:inifilebackend
Edit Summary: [List of ACL rules]
User : sunweaver
@@ -83,8 +83,9 @@
**Client ACLs:**
* ''acl-clients-allow = <subnet-or-ip>, <or-dns-hostname>
* ''acl-clients-deny = ALL''
+
===== Special Broker Options =====
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/07/02 00:30
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/x2gobroker:inifilebackend?rev=1372724985
New Revision: http://wiki.x2go.org/doku.php/x2gobroker:inifilebackend
Edit Summary: [List of ACL rules]
User : sunweaver
@@ -83,8 +83,9 @@
**Client ACLs:**
* ''acl-clients-allow = <subnet-or-ip>, <or-dns-hostname>
* ''acl-clients-deny = ALL''
+
===== Special Broker Options =====
Some options in the ''x2gobroker-sessionprofiles.conf'' file are used to tweak the broker itself. The options are:
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/