satellit_installer:
An automated installation script for bwLehrpool satellite server


1. Preface 

The satellit_installer script automatically installs a bwLehrpool satellite 
server on top of a naked Linux OS. Currently supported is Debian 7.5 wheezy. 

It may also work on other Debian based Linux systems as long as packages 
(especially Mysql better or equal to Mysql 5.5) are installable via apt-get.
We have tested the script under Debian testing 8.x, but your mileage may vary 
- we have not tested intensive enough to give any guarantee. By the way: We 
do not give any guarantee in any way.

So at least now it would be wise perhaps to use the way better tested Debian 
7.x branch.

Please keep in mind that several packages will be installed via internet and 
some more data files will be fetched via http, so an internet connection is 
vital.

This means of course a viable sources.list including entries equal to this 
example:
| deb http://ftp.de.debian.org/debian/ wheezy main
| deb-src http://ftp.de.debian.org/debian/ wheezy main
| deb http://security.debian.org/ wheezy/updates main
| deb-src http://security.debian.org/ wheezy/updates main

While it may be wise to update the Debian base system before installing the 
bwLehrpool satellite server, the installation should in no way interfere with 
any system services so you can (and should!) keep your server always up to date.

Please remember that a database entry in the master server is needed for any 
satellite server to function, as the bwSuite clients will first connect to the 
master server which will forward connecting clients via username resolution to 
an appropriate satellite server. Or, in other words: If this master server 
database entry is missing, your satellite server will never see any connect.

IMPORTANT NOTICE: This script may interfere with server functions, so do NOT 
execute in on any production servers!


2. Getting the satellit_installer script

While this point seems a litte moot, as you are obviously reading this 
documentation now and the documentaion here is part of the package, possibly 
you got the script as an archive and would like to know how to get an 
actualized git version.

You may verify whether there are updates at the web interface 
http://git.openslx.org/slx-admin.git. If you want to check out an actualized 
git version use git://git.openslx.org/openslx-ng/slx-admin.git (or 
git@git.openslx.org:openslx-ng/slx-admin.git, if your key is known to the 
server).


3. Using the script

Using the script should be pretty straight forward. Just change into the 
script directory, and start it without options. It will download and install 
any needed system packages and helper files needed to function.

So:

1. change into the script directory (.../setup-scripts/satellit_installer).
2. Start the script: ./satellit-installer
3. Read script output for eventual warnings.
4. Log out and re-log in to trigger the dropped script, or simply reboot
   and re-login (a reboot is not quite necessary, but will not hurt either)
5. At the end of the dropped script choose 'y' to reboot, or do some other 
   stuff, as long as you do not forget to reboot prior using the satellite.


4. What to do if the script has thrown any errors?

Well, the error handling and especially the re-entry features are somewhat 
rudimentary. If you use a virtual machine it would be perhaps fastest to just 
reset the machine and try again. Please let us know about any errors 
encountered.

If resetting the machine to the prior state is not feasible, take following 
steps in a terminal (commands to enter are denoted between '': 'command'):

1. 'source includes/00-variables.inc'
2. 'source includes/10-uninstall_packages.inc'
3. 'source includes/10-purge_install.inc'
4. call the function purge_install: 'purge_install' (CAUTION: This will purge 
   the packets given in 00-variables.inc: PACKAGELIST_SERVER and 
   PACKAGELIST_SCRIPT without regard whether they were installed prior the 
   first script run and it will kill/delete any Mysql databases / Mysql 
   installation most brutally).
5. re-run the script.
6. As said: Let us know about any errors.


5. Contact

Please write any annotations, bug notices etc. to: 
christian.roessler@rz.uni.freiburg.de