(**) Translated with www.DeepL.com/Translator
This is a complex part to explain and implement. The network architecture and the distribution of services on each of the machines must be determined. Keep in mind that you will have a unit that will break down, making its services inaccessible. Therefore you have to think about how to fix it, what will happen during this failure. The goal here is not to have a datacenter where everything is doubled, but to provide, at the very least, a solution that “stands the test”, in terms of maintenance, reliability and security.
The services allowing the Datacenter to operate are distributed on different machines, we will speak of a “distributed architecture”.
In this type of architecture, it is quite simple to move a service to another server, during the repair period. Even if this leads to an overload of the machine that will temporarily host this faulty service, the Datacenter will run in “degraded mode”.
Datacenter provisioning process
This documentation takes a lot of time and will be updated frequently.
It is imperative, to have a notion on Linux systems, in particular :
- know how to use the shell (basic)
- know how to use the “vi” editor
The first step is to install the DEBIAN system on the Datacenter servers.
The second step will allow the implementation of the “Network” part of the Datacenter, in this order:
- Initialize the Datacenter
- one DNS service - Domain Name System
- one DHCP service - Dynamic Host Configuration Protocol
- one main Router/Firewall
- A Datacenter access service by VPN
The third step will allow the implementation of tools related to the security of the Datacenter:
[…]