Differences

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

--- wiki:components:tce [2011/06/17 23:17]
sunweaver
+++ — (current)
@@ Line 1: / Line 1: @@
-====== Installation of the X2go TCE based on Debian ======
-In the following article we will explain how to set up an X2go Thin Client environment. In the following we will use three technical terms that we want to define/explain before we start:
-  * X2go Server: a GNU/Linux application server that users can connect to with the ''x2goclient'' software. X2go servers can be situated in the LAN (local area network) or WAN (wide area network, i.e. the internet).
-  * X2go Thin Client: a user workstation in your office that boots from the network with minimal software. Only purpose is to start the ''x2goclient'' software and provide access to one (or more) X2go Server(s).
-  * X2go PXE Server: the server that serves chroot images to X2go Thin Clients via PXE, TFTP and NFS to thin client boxes. The X2go PXE Server has to be situated in your LAN. X2go PXE Server and X2go Server can be one machine, in production setups we recommend to separate these two functionalities onto two separate (virtual) servers.
-<note>The X2go TCE has been developed on/for Debian GNU/Linux. -- You can surely use any GNU/Linux distribution as X2go Server (providing that the ''x2goserver'' package is available for the server's distro). The boot environment for the X2go PXE Server has been developed on Debian GNU/Linux and also been tested on Ubuntu GNU/Linux. The X2go Thin Client chroot can be configured to use Ubuntu GNU/Linux, but it is __highly recommended__ to leave the defaults and use Debian GNU/Linux for creating the X2go TCE chroot.</note>
-===== Network setup =====
-X2go TCE requires a local area network (LAN) that is at least switched at 100MB/s. The X2go Thin Client chroot distribution is not designed to work over the internet or on low bandwidth connections, but the X2go Thin Client can possibly give access to X2go servers outside of your LAN infrastructure that is: X2go Thin Clients can be used to work on X2go servers on the WAN (e.g. on the internet, in a public cloud, etc.).
-You can combine X2go Server and X2go PXE Server functionality on one system. However, for production setups we highly recommend that you dedicate a separate server as the PXE boot server for the X2go TCE. If you have the chance of splitting these two functionalities up into two, this is a recommended way of setting up your X2go Thin Client Environment.
-<note important>Please refrain from installing the PXE boot environment for X2go Thin Clients on your in-house production server, especially for testing X2go TCE make it a separate system. Maybe you want to use virtualization (KVM, Xen, etc.) for setting up a test X2go infrastructure with X2go Thin Clients on your LAN.
-</note>
-A normal/recommended setup for testing/deploying X2go TCE then is:
-  * X2go server (Debian, Ubuntu, etc.)
-  * optional: a separate X2go PXE server (Debian or Ubuntu)
-  * X2go Thin Client hardware (can be everything from e.g. Pentium III, AMD Athlon upwards), main requirement is that the thin client hardware box contains a network card that is PXE/Etherboot capable
-===== X2go TCE / Debian squeeze =====
-<note>The current X2go TCE is based and has been tested on Debian GNU/Linux (squeeze). Since June 2011 we have working packages available in our Debian repository on ''packages.x2go.org''.</note>
-In the following description we will describe a simple X2go TCE installation, using two separate hosts as X2go Server and X2go PXE Server. The explanation presumes that you either install on Debian GNU/Linux (squeeze) or Ubuntu GNU/Linux (lucid/maverick). If you (for testing purposes) use the same machine as X2go Server and X2go PXE Server, please perform described steps for either of the machines on the same system.
-The resulting X2go Thin Client chroot will be a Debian GNU/Linux (squeeze) system by default.
-:!: **Before you continue!**
-> Please make sure that you have added the X2go repository to your package management system (on X2go server and on X2go PXE server). The required steps are described here: [[adding the X2go repository (Debian)]]  or alternatively: [[adding the X2go repository (Ubuntu)]].
-==== Installing X2go server ====
-The X2go Server installation is described in detail on [[installing_x2goserver_debian_ubuntu|this wiki page]]. Please follow instructions there first, then proceed below.
-Basically you have to install the ''x2goserver'' package and your preferred desktop environments (e.g. GNOME, KDE4):
-<code>
-$ apt-get install x2goserver gnome-desktop-environment plasma-desktop
-</code>
-==== X2go PXE server ====
-=== Summary ===
-In a nutshell you have to run the following commands from a terminal on the X2go PXE Server (or X2go Server if combining both systems in one):
-<code>
-$ aptitude install x2gothinclientmanagement
-# take a look at the X2go TCE config and modify to your needs
-$ vim /etc/x2go/x2gothinclient_settings
-$ x2gothinclient_create
-# now you have to wait for some time, loads of things
-$ x2gothinclient_preptftpboot
-# follow the instructions being shown at the end of the x2gothinclient_preptftpboot script run...
-</code>
-=== Basic installation of the X2go PXE server ===
-Now a bit more in detail...
-   - Install a Debian squeeze system from the Debian Installer (CD/DVD). For downloading Debian, please visit this site: http://www.debian.org/releases/stable/debian-installer/ (depending on your server hardware you have to download either the Debian squeeze CD/DVD for the amd64 or the i386 architecture. Most common currenlty should be amd64). Install a standard Debian with OpenSSH service enabled.
-   - Then add the X2go repository to your freshly installed X2go PXE server ([[adding the X2go repository (Debian)]]). For your convenience, make sure that you get the package ''x2go-keyring'' installed first.
-   - The only X2go related package needed on the X2go PXE server is the package: ''x2gothinclientmanagement''. Please, install this package by typing the first line shown below (the rest is the command's output that will be seen after pressing enter): <code>
-$ apt-get install x2gothinclientmanagement
-Reading package lists... Done
-Building dependency tree
-Reading state information... Done
-The following extra packages will be installed:
-  atftpd debootstrap inetutils-inetd libcrypt-passwdmd5-perl libdigest-sha1-perl libfile-copy-recursive-perl nfs-kernel-server syslinux syslinux-common update-inetd
-Suggested packages:
-  dosfstools mtools dhcp3-server dnsmasq isc-dhcp-server
-Recommended packages:
-  inet-superserver
-The following NEW packages will be installed:
-  atftpd debootstrap inetutils-inetd libcrypt-passwdmd5-perl libdigest-sha1-perl libfile-copy-recursive-perl nfs-kernel-server syslinux syslinux-common update-inetd x2gothinclientmanagement
-upgraded, 11 newly installed, 0 to remove and 0 not upgraded.
-Need to get 1855 kB of archives.
-After this operation, 5353 kB of additional disk space will be used.
-Do you want to continue [Y/n]?
-</code> The installation will drag in some other required packages onto your system, please confirm with Yes, to start the installation.
-=== Building the X2go Thin Client system (the so-called chroot environment) ===
-  - After installation of the ''x2gothinclientmanagement'' package (and required dependencies), please edit/introspect the following file with your favourite editor:<code>
-$ editor /etc/x2go/x2gothinclient_settings
-</code> and apply changes required for your local site setup to the X2go TCE configuration.
-  - When done, start the creation of a fresh X2go Thin Client chroot environment:<code>
-$ x2gothinclient_create
-</code>
-  - Now you will be able to observe a medium long installation process on your system. This installation process takes place in a chroot jail environment, it does not do anything to the X2go PXE server itself.
-  - During installation you will be asked to configure your keyboard and your thin client's default language. Please do so. Hint: make sure you use UTF-8 in your language selection (e.g. en_US.UTF-8, de_DE.UTF-8, etc.).
-  - After the chroot installation of your X2go Thin Client, you will notice a folder structure such as this on your X2go PXE server:<code>
-root@pxeserver:/opt# tree -L 3
-.
-└── x2gothinclient
-    ├── chroot
-    │   ├── bin
-    │   ├── boot
-    │   ├── dev
-    │   ├── etc
-    │   ├── home
-    │   ├── initrd.img -> boot/initrd.img-<kernel-version>
-    │   ├── lib
-    │   ├── media
-    │   ├── mnt
-    │   ├── opt
-    │   ├── proc
-    │   ├── root
-    │   ├── sbin
-    │   ├── selinux
-    │   ├── srv
-    │   ├── sys
-    │   ├── tmp
-    │   ├── usr
-    │   ├── var
-    │   ├── vmlinuz -> boot/vmlinuz-<kernel-version>
-    │   └── x2go_tc_install.sh
-    └── etc
-        ├── x2gothinclient_init
-        ├── x2gothinclient_sessions
-        └── x2gothinclient_start
-</code>
-  - Next, you may take a look at the files in the folder ''/opt/x2gothinclient/etc/''.
-    - ''**x2gothinclient_init**'': No customizations should be necessary for this file. Modify at your own risk... If a modification is necessary here, please report it as a bug/enhancement to the X2go developers.
-    - ''**x2gothinclient_start**'': This file is responsible for actually launching ''x2goclient'' as a login manager on your thin client. The default setting is to start in non-LDAP mode. In non-LDAP mode the ''x2gothinclient_sessions'' file contains the thin clients' list of available X2go session profiles. For LDAP mode there is a commented out stanza that shows possible LDAP options to pass on to the ''x2goclient'' application. //**Note:** If you edit this file, please make sure that all applications you call from this file are sent to background with the ampersand (»&«) operator, e.g.: '' x2goclient <options> &''//
-    - ''**x2gothinclient_sessions**'': This file contains a list of session profile configurations for your thin clients' ''x2goclient'' (running in logon manager mode). Surely, you can edit/customize the examplary session profiles file that comes with the ''x2gothinclientmanagement'' package in your favourite text editor. --- However, another option is using the ''x2goclient'' application on your local computer to create such a set of session profiles for your X2go Thin Client Environment. Simply configure your ''x2goclient'' in a way that want it to look on your X2go Thin Clients. When done, copy your local ''x2goclient'' session profile configuration to the X2go PXE server:<code>
-$ scp ~/.x2goclient/sessions root@<pxeserver.hostname.domain>:/opt/x2gothinclient/etc/x2gothinclient_sessions
-</code>
-  - When done with all your customizations execute the ''x2gothinclient_update'' script. This script will incorporate your changes applied the ''/opt/x2gothinclient/etc/x2gothinclient_*'' files into the X2go Thin Clients' chroot environment. Whenever you customize anything in ''/opt/x2gothinclient/etc/'' make sure your run the update command:<code>
-$ x2gothinclient_update
-</code>
-With this last step your X2go Thin Client's chroot environment is basically ready for being booted. The last step, however, is to configure the PXE boot manager itself (PXE, TFTP).
-=== Boot environment for your X2go Thin Client system (PXE, TFTP) ===
-As we do not want our software to interfere with other PXE bootable systems (like LTSP for example) we only ship an exemplary TFTP/PXE configuration in the doc section of the ''x2gothinclientmanagement'' package. You may take a look at the shipped files with these commands:
-<code>
-$ cd /usr/share/doc/x2gothinclientmanagement/examples/tftpboot
-$ ls -al
-</code>
---- WORK IN PROGRESS ---
-===== X2go TCE / Debian lenny =====
-:!: **Debian lenny currently is Debian's »oldstable« version. Do not use it anymore!**
-X2goclient can be used as a display manager. If you combine this feature with a boot environment, you'll get an easy manageable solution for your whole network. Please read the manual carefully, because some of the commands could harm your system if executed within the wrong context. The boot environment used by x2go will be able to recognize USB mass storage and CD-ROM devices automatically. Global preferences can be edited inside the KDE Control Center. You'll need 300 MB of free disk space for this installation. First of all you'll need the network services:
-<code>
-# apt-get install dhcp3-server atftpd nfs-kernel-server debootstrap
-</code>
-You'll need a directory to install the boot environment. You can choose a directory of your choice, but this manual will describe the installation inside “/opt/x2gothinclient”. This directory is also defined within some configuration files:
-<code>
-# mkdir /opt/x2gothinclient
-</code>
-You can populate the directory by running the command “debootstrap”:
-<code>
-# debootstrap --arch i386 lenny /opt/x2gothinclient/ http://ftp2.de.debian.org/debian
-</code>
-Adding a name server entry will help you accessing the Internet inside the chroot environment:
-<code>
-# cp /etc/resolv.conf /opt/x2gothinclient/etc/resolv.conf
-</code>
-You'll also need some network device:
-<code>
-# vi /opt/x2gothinclient/etc/network/interfaces:
-</code>
-<file>
-auto lo
-iface lo inet loopback
-</file>
-And a host name as well as an entry of your system inside /etc/hosts:
-<code>
-# echo x2gothinclient > /opt/x2gothinclient/etc/hostname
-# echo "127.0.0.1 localhost" >>/opt/x2gothinclient/etc/hosts
-</code>
-You also need the x2goserver inside /etc/hosts:
-<code>
-# echo "192.168.1.1 x2goserver.planetexpress.de x2goserver" >>/opt/x2gothinclient/etc/hosts
-</code>
-and access to the x2go repository:
-<code>
-# echo "deb http://x2go.obviously-nice.de/deb/ lenny main" >>/opt/x2gothinclient/etc/apt/sources.list
-</code>
-:!: **Warning!**
-> Please make sure that you continue working inside the boot environment. If you execute commands inside your real system, you may make it inaccessible!
-The following command will take you inside the boot environment
-<code>
-# chroot /opt/x2gothinclient /bin/bash
-</code>
-To get things working you'll need /proc and /dev directories. You may also use hardlinks created outside the chroot environment:
-<code>
-# mount -t proc none /proc
-# mount -t devpts none /dev/pts/
-</code>
-Debootstrap didn't install a kernel, which is needed to start the boot environment:
-<code>
-# aptitude update
-# aptitude install syslinux locales linux-image-486
-</code>
-If you would like to use a keymap other than us_US, you'll need to reconfigure the locales:
-<code>
-# dpkg-reconfigure locales
-</code>
-The system will be started via network, so it is necessary to tell the initramfs about your plans:
-<code>
-# vi /etc/initramfs-tools/initramfs.conf
-</code>
-<file>
-Modify to : BOOT=nfs
-</file>
-The new configuration needs to be applied and the initramfs needs to be newly generated:
-<code>
-# update-initramfs -u -v
-</code>
-The package x2gothinclientsystem will install a system daemon which will start x2goclient as a display manager. It will further start a deamon which will be responsible for mounting local mass storage devices automatically.
-<code>
-# apt-get install x2gothinclientsystem
-# cd /usr/share/x2gothinclientsystem/script
-# ./x2gothinclient_install.sh
-</code>
-This will finish the installation of the boot environment. Before exiting the chroot environment, you'll need to umount the /proc and /dev directories:
-<code>
-# umount /proc/
-# umount /dev/pts/
-</code>
-Set a root password. You can change this again later by entering the chroot environment.
-<code>
-# passwd
-</code>
-The command “exit” will leave the chroot boot environment. If you discover any problems, you can always go back inside the boot environment by using “chroot” as described (for example for system upgrades):
-<code>
-# exit
-</code>
-==== Configuration of DHCPD ====
-If you already have an DHCP server in your network, please make sure that you are able to setup an own range of IP addresses for the boot environment. Because of the conflict between devices that should access the boot environment and normal network nodes (MAC address binding), it is much easier to setup an own network for your thin client system. The following example assumes that you are running the DHCPD and the ATFTPD on the same system.
-<code>
-# vi /etc/dhcpd/dhcpd.conf
-</code>
-<file>
-option domain-name "planetexpress.de";
-option domain-name-servers 192.168.1.1;
-# x2go thin client range/group
-subnet 192.168.0.0 netmask 255.255.255.0 {
-range 192.168.0.100 192.168.0.199;
-filename "/pxelinux.0";
-next-server 192.168.0.250;
-}
-</file>
-Restart the DHCPD to apply the new configuration:
-<code>
-# /etc/init.d/dhcp3-server restart
-</code>
-==== Setting up atftp ====
-After receiving a network address from the DHCP daemon, a kernel will be deployed using the tftp protocoll. For this purpose, you'll need to configure the **atftpd**, so that the kernel can be found. Please make sure, that **atftp** ist started by an init script and not via inet.d.
-<code>
-# vi /etc/default/atftpd
-</code>
-<file>
-USE_INETD=false
-OPTIONS="--daemon --port 69 --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=5 /tftpboot"
-</file>
-You'll need a directory to store the necessary kernel which should be world readable (=public).
-<code>
-# mkdir /tftpboot
-# chmod 755 /tftpboot
-</code>
-If inet.d was installed and used on your system, please make sure that it is not starting or runnig **atftp** when you start it directly:
-<code>
-# /etc/init.d/atftpd restart
-</code>
-If you don't want to make copies of the kernel and initrd files, just use symbolic links – that is a good idea, if you plan to maintain the boot environment:
-<code>
-# ln -s /opt/x2gothinclient/vmlinuz /tftpboot/
-# ln -s /opt/x2gothinclient/initrd.img /tftpboot/
-</code>
-The configuration file of **atftp** needs to be created and edited. Please change the IP address if necessary!
-<code>
-# mkdir /tftpboot/pxelinux.cfg
-# touch /tftpboot/pxelinux.cfg/default
-# cp /opt/x2gothinclient/usr/lib/syslinux/pxelinux.0 /tftpboot/
-</code>
-<code>
-# touch /tftpboot/pxelinux.cfg/default
-# vi /tftpboot/pxelinux.cfg/default
-</code>
-<file>
-label linux
-kernel vmlinuz
-append root=/dev/nfs nfsroot=192.168.1.1:/opt/x2gothinclient ro initrd=initrd.img ip=dhcp
-</file>
-==== Configuration of the NFS share ====
-The root file system of the boot environment is mounted using NFS (so it can be accessed over the network). You'll need to export the needed directory by editing the NFS configuration file:
-<code>
-# vi /etc/exports
-</code>
-<file>
-/opt/x2gothinclient 192.168.1.0/24(ro,async,no_root_squash)
-</file>
-Finally restart the NFSD:
-<code>
-# /etc/init.d/nfs-kernel-server restart
-</code>
-==== Configuration of x2goclient (display manager mode) ====
-Please also edit the command line options used by the x2goclient running in display manager mode (for example: change the IP address).
-<code>
-# vi /opt/x2gothinclient/etc/default/x2gothinclient
-</code>
-<file>
-x2goclient --pgp-card -ldap="192.168.1.1:389:o=planetexpress,c=de" --external-login=/ramdrive/logins --no-menu --maximize --link=lan --kbd-layout=de --kbd-type=pc105/de --set-kbd=1 --geometry=fullscreen --add-to-known-hosts --read-exports-from=/ramdrive/export –add-to-known-hosts
-</file>
-==== Alternative configuration of x2goclient (display manager mode without LDAP) ====
-This is an optional setup if you want to avoid the needed LDAP server configuration. Please choose only one of the two display manager mode options!
-=== Create the needed sesssion ===
-You should start by creating a session with a x2goclient. You should only create the needed session if you want to deny users to choose between different sessions. If you don't use the x2goclient user inside the boot environment, please make sure to copy it inside the required directory. The created file should look like:
-<code>
-$ cat ~/.x2goclient/sessions
-</code>
-<file>
-[20070226145202980]
-host=x2goserver
-command=KDE
-fullscreen=true
-layout=de
-name=X2Go Session
-pack=16m-jpeg
-quality=9
-sound=true
-speed=2
-sshport=22
-type=pc105/de
-usekbd=true
-rootless=false
-soundsystem=pulse
-startsoundsystem=true
-soundtunnel=true
-fstunnel=true
-defsndport=true
-sndport=4713
-</file>
-<file>
-x2goclient --no-session-edit --session="X2Go Session" --pgp-card --external-login=/ramdrive/logins --no-menu --maximize --link=lan --kbd-layout=de --kbd-type=pc105/de --set-kbd=1 --geometry=fullscreen --add-to-known-hosts --read-exports-from=/ramdrive/export –add-to-known-hosts
-</file>
-There are two commandline arguments you should be aware in this configuration. **--no-session-edit** will deny any manipulation of the session by the user. **--session="X2Go Session"** needs to be identical to the name inside the x2go session file created above. Don't use the LDAP argument with this setup.
-You are done!
-PXE Boot enabled devices should now boot into the configured environment and show the x2goclient in display manager mode. If there are problems to start x.org, you may need to add missing drivers to the boot environment.

X2Go - everywhere@home

User Tools

Site Tools

Differences

Page Tools