|
Size: 1136
Comment: spelling+rephrasing
|
Size: 928
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| This is how the Blinkenshell shell account environment works. Behind the domain Blinkenshell.org there is a physical server: the name of this server is Saturn. | |
| Line 4: | Line 3: |
| Saturn has several virtual servers, one of which is where all the shell accounts live; Titan is the name of that virtual server. | Since the summer of 2010, Blinkenshell is based on one big physical server with lots of different virtual machines on it, and some additional virtual servers hosted at remote sites. |
| Line 6: | Line 5: |
| When you surf to Blinkenshell.org firstly Saturn checks what content you are requesting, and then either serves that content directly or sends a request to a virtual server. If you browse the main webpage, you are being served directly by Saturn. If you however request a user's webpage, then it's the webserver on Titan that's serving your request. | The main server has virtual machines for: storage (NFS), directory service (Kerberos/LDAP), web, mail, SSH/shell, firewall and monitoring. All accounts are stored on the central directory service, and can be accessed from any of the other servers. The storage server hosts the home directories and shares them via NFS, so these can also be accessed from any server. |
| Line 8: | Line 7: |
| This explains some of the behaviours of the environment. And the reason I chose this design/architecture is mostly because of the added security. If someone gets root access on Titan, he will not be able to bring down the whole server. | Having different virtual machines for each service allows for increased security because of the separation, and increased uptime because upgrading one server will not affect the other services. |
| Line 10: | Line 9: |
| . {{attachment:blinkenshell_design.png}} Between 18-19 December 2006, there were some server problems and what I did then was to replace the previous virtual server Rhea with the new one called Titan. |
The main server is a Xeon X3440, with 8 GB of ECC RAM and a RAID-Z (RAID5) for storage. [[SSH_Servers|List of SSH servers]] |
Design/Architecture
Since the summer of 2010, Blinkenshell is based on one big physical server with lots of different virtual machines on it, and some additional virtual servers hosted at remote sites.
The main server has virtual machines for: storage (NFS), directory service (Kerberos/LDAP), web, mail, SSH/shell, firewall and monitoring. All accounts are stored on the central directory service, and can be accessed from any of the other servers. The storage server hosts the home directories and shares them via NFS, so these can also be accessed from any server.
Having different virtual machines for each service allows for increased security because of the separation, and increased uptime because upgrading one server will not affect the other services.
The main server is a Xeon X3440, with 8 GB of ECC RAM and a RAID-Z (RAID5) for storage.