Mahmoud Ramadan schrieb am 05.09.2015 19:27:
> I have NO problem to deploy one server in each remote site to push the
> Thin/Fat client images to the clients in the LAN just to preserve more
> bandwidth on the WAN then i place the LTSP servers in the cloud.
>
> In other words, I'm thinking to deploy TFTP and PXE in each remote site so
> the clients in the LAN can PXE boot and download their images locally,then
> point them in the configuration file to LTSP servers in the cloud BUT i do
> NOT know what modifications i need to do to point the Thin / Fat clients to
> LTSP servers other than the servers running the TFTP service? If anyone can
> clear that it will be appreciated !
I have separated all these services for years, and I like it. :^)
1. dhcp
The client's PXE/dhcp requests are served by a separate dhcp server. In the
dhcpd.conf file I have an entry like this:
group {
# tsi2, Image ist Debian Jessie 32-bit (i386):
next-server 10.1.3.30;
option root-path "/opt/ltsp/i386";
if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
filename "/ltsp/i386/pxelinux.0";
} else {
filename "/ltsp/i386/vmlinuz";
}
host otc3 { hardware ethernet 00:e0:c5:45:2b:85; fixed-address otc3; }
host c474 { hardware ethernet 00:01:2e:64:b5:3e; fixed-address c474; }
host hp7 { hardware ethernet c8:cb:b8:2e:0b:6e; fixed-address hp7; }
}
2. ltsp image
The dhcp server points to my image server (tsi2, 10.1.3.30). This server
provides the nbd image (or nfs if you prefer), the tftp service, and keeps the
configuration file lts.conf.
In the lts.conf on tsi2 I have entries like:
[c474]
LTS_SERVERS = lts2 lts3
[otc3]
LTS_SERVERS = lts3
3. ltsp application server
On my LTSP application servers (lts2, lts3), where all users work on, I have
these
(Debian) packages installed:
ldm-server
ldm-themes
ltsp-docs
ltsp-server
ltspfs
4. Selecting the least loaded terminal server at thin client boot time for
some basic load balancing (maybe you don't need/want this):
Note: The variable LTS_SERVERS is home brewed, not standard. It is used by the
script /opt/ltsp/i386/usr/share/ltsp/get_hosts. Maybe the default ltsp variable
LDM_SERVER is for just this purpose. Can someone confirm this?
Anyway, here's my script (shamelessly stolen from some nice guy):
#!/bin/bash
##############################################################################
# /opt/ltsp/i386/usr/share/ltsp/get_hosts
##############################################################################
echo `date` >/tmp/lts-serverlist
LIST=""
# Load query on all servers
for i in $LTS_SERVERS; do
LOAD=`nc $i 9571|grep rating|cut -d: -f2`
if test $LOAD; then
# add to the list
LIST="$LIST$LOAD $i\n"
fi
done
# Now LIST contains the list of servers sorted by load
LIST=`echo -e $LIST | sort -nr`
echo $LIST >>/tmp/lts-serverlist
# Check if the 1st items have the same load. If so, randomly choose one.
OLDIFS=$IFS
IFS="
"
BESTLIST=( )
I=0
for LINE in $LIST ;do
LOAD=`echo $LINE|cut -f 1 -d " "`
if [ "$OLDLOAD" -a "$LOAD" != "$OLDLOAD" ] ;then
break
fi
BESTLIST[$I]="$LINE"
OLDLOAD=$LOAD
I=$((I+1))
done
RAND=$(( $RANDOM % $I ))
# print the choosen host
echo ${BESTLIST[$RAND]} | cut -f 2 -d " "
# and once again into a file for logging:
echo The Best: >>/tmp/lts-serverlist
echo ${BESTLIST[$RAND]} | cut -f 2 -d " " >>/tmp/lts-serverlist
exit 0
##############################################################################
HTH
Regards
Helmut
--
-------------------------------------------------------------------------
Helmut Lichtenberg <helmut.lichtenb...@fli.bund.de> Tel.: 05034/871-128
Institut für Nutztiergenetik (FLI) 31535 Neustadt Germany
-------------------------------------------------------------------------
------------------------------------------------------------------------------
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
