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

[Debian Wiki]

Dear Wiki user,

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

The "DebianEdu/Documentation/Stretch/Architecture" page has been changed by HolgerLevsen:
https://wiki.debian.org/DebianEdu/Documentation/Stretch/Architecture?action=diff&rev1=6&rev2=7

Comment:
squash another instance of thin-client-server and slightly reword

  A Skolelinux network needs one main server (also called "tjener" which is Norwegian and means "server") which per default has the IP address 10.0.2.2 and is installed by selecting the main server profile. It's possible (but not required) to also select and install the LTSP-server and workstation profiles in addition to the main server profile.
  
  === Services running on the main server ===
- With the exception of the control of the thin-clients, all services are initially set up on one central computer (the main server). For performance reasons, the thin-client-server should be a separate machine (though it is possible to install both the main server and LTSP server profiles on the same machine). All services are allocated a dedicated DNS-name and are offered exclusively over IPv4. The allocated DNS name makes it easy to move individual services from the main-server to a different machine, by simply stopping the service on the main-server, and changing the DNS configuration to point to the new location of the service (which should be set up on that machine first, of course).
+ With the exception of the control of the thin-clients, all services are initially set up on one central computer (the main server). For performance reasons, the LTSP-server(s) should be separate (though it is possible to install both the main server and LTSP server profiles on the same machine). All services are allocated a dedicated DNS-name and are offered exclusively over IPv4. The allocated DNS name makes it easy to move individual services from the main-server to a different machine, by simply stopping the service on the main-server, and changing the DNS configuration to point to the new location of the service (which should be set up on that machine first, of course).
  
  To ensure security all connections where passwords are transmitted over the network are encrypted, so no passwords are sent over the network as plain text.