[debian-edu-commits] [Debian Wiki] Update of "DebianEdu/Documentation/Wheezy/Architecture" by WolfgangSchweer

[Debian Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Debian Wiki" for change notification.

The "DebianEdu/Documentation/Wheezy/Architecture" page has been changed by WolfgangSchweer:
https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Architecture?action=diff&rev1=11&rev2=12

Comment:
and flavour diskless workstation to thin-client-server clients

  
  {{attachment:Debian_Edu_Network_Wheezy.png|The Debian Edu network topology|width=1024}}
  
- The figure is a sketch of the assumed network topology. The default setup of a Skolelinux network assumes that there is one (and only one) main-server, while allowing the inclusion of both normal workstations and thin-client-servers (with associated thin-clients). The number of workstations can be as large or small as you want (starting from none to a lot). The same goes for the thin-client servers, each of which is on a separate network so that the traffic between the thin-clients and the thin-client server doesn't affect the rest of the network services.
+ The figure is a sketch of the assumed network topology. The default setup of a Skolelinux network assumes that there is one (and only one) main-server, while allowing the inclusion of both normal workstations and thin-client-servers (with associated thin-clients and/or diskless workstations). The number of workstations can be as large or small as you want (starting from none to a lot). The same goes for the thin-client servers, each of which is on a separate network so that the traffic between the clients and the thin-client server doesn't affect the rest of the network services.
  
  The reason that there can only be one main server in each school network is that the main server provides DHCP, and there can be only one machine doing so in each network. It is possible to move services from the main server to other machines by setting up the service on another machine, and subsequently updating the DNS-configuration, pointing the DNS alias for that service to the right computer.