|
Size: 1564
Comment:
|
Size: 2336
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Its all about uptime! | = Its all about uptime! = |
| Line 3: | Line 3: |
| The main goal is to go as close to no downtime as possible. | System uptime and availability is being increasingly important. Various services are expected to be accessibly at all times. The challenge is to configure and maintain such a system, with minimal downtime, and preferable no downtime at all. At first this sounds like a very complicated task, but breaking it down to its components makes it possible. Configuring and deploying one component at a time, in a redundant way, allows for added complexity in a simple way, which increasingly builds on a stable redundant platform, keeping the redundancy all the way through the component stack. As the system is comprised of redundant components, it is ensured that any component at any time can be taken down for maintenance, without compromising the uptime and availabilty of the system. |
| Line 5: | Line 5: |
| These are our worst foes: | == These are our worst foes == |
| Line 7: | Line 7: |
| Deciding the level of importance of the system really depends on the physical environment. As we can see there are | |
| Line 14: | Line 15: |
| Basic knowledge of GNU/Linux commandline tools is required to use this guide. These tools will not be explained here. Configure your system |
== Configure your system == |
| Line 19: | Line 18: |
| * * KVM Guest |
* [[KVM Guest|KVM Guest]] |
| Line 22: | Line 20: |
| == Manage Virtual Domains == | |
| Line 23: | Line 22: |
| * [[Domain Creation|Domain Creation]] * [[Domain Console|Domain Console]] * [[Domain Destruction|Domain Destruction]] * [[Domain Editing|Domain Editing]] * [[Domain Cloning|Domain Cloning]] * [[Domain Migration|Domain Migration]] |
|
| Line 24: | Line 29: |
| This project is based on the GNU/Linux software packaged by Debian, currently the stretch release. The information provided here will most likely work on other GNU/Linux systems as well. | == Network Planning == |
| Line 26: | Line 31: |
| * [[Network Planning|Network Planning]] | |
| Line 27: | Line 33: |
| == Configure a Redundant Service == | |
| Line 28: | Line 35: |
| I have had a home server running for many years now, but as time passed more and more functionality was added to it. Eventually I ended up in a situation where maintaining the server often forced me to shut down services. | * [[DNS|DNS]] * [[DHCP|DHCP]] * [[NTP|NTP]] * [[GlusterFS|GlusterFS]] * [[Corosync and HA-proxy|Corosync and HA-proxy]] * [[Mariadb|Mariadb]] * [[Redis|Redis]] * [[Apache|Apache]] * [[LDAP|LDAP]] * [[Postfix|Postfix]] * [[Dovecot|Dovecot]] * [[Nextcloud|Nextcloud]] * [[OPNsense|OPNsense]] |
| Line 30: | Line 49: |
| While trying to get my hands on a physical book on kvm based virtualization I found that there was no such book. I wanted to start using kvm, since my server ran so many different services, that they eventually began to get in the way for each other. But finding a really good beginners guide was hard, hence my decision to start this site. I call the site uptime. The whole idea about this setup is to get as high an uptime as possible. Other goals like security and speed will also be considered, but the main focus is on getting the best possible uptime. |
''This project is based on the GNU/Linux software packaged by Debian, currently the buster release. The information provided here will most likely work on other GNU/Linux systems as well. Basic knowledge of GNU/Linux commandline tools, file editing, network etc. is required to use and understand this guide.'' |
Its all about uptime!
System uptime and availability is being increasingly important. Various services are expected to be accessibly at all times. The challenge is to configure and maintain such a system, with minimal downtime, and preferable no downtime at all. At first this sounds like a very complicated task, but breaking it down to its components makes it possible. Configuring and deploying one component at a time, in a redundant way, allows for added complexity in a simple way, which increasingly builds on a stable redundant platform, keeping the redundancy all the way through the component stack. As the system is comprised of redundant components, it is ensured that any component at any time can be taken down for maintenance, without compromising the uptime and availabilty of the system.
These are our worst foes
Deciding the level of importance of the system really depends on the physical environment. As we can see there are
- Power outage
- Internet access
- Hardware malfunction
- Software updates
To get around this a redundant system has to be built. Realizing that a redundant system consists of many redundant parts, virtualization naturally comes to mind.
Configure your system
Manage Virtual Domains
Network Planning
Configure a Redundant Service
This project is based on the GNU/Linux software packaged by Debian, currently the buster release. The information provided here will most likely work on other GNU/Linux systems as well. Basic knowledge of GNU/Linux commandline tools, file editing, network etc. is required to use and understand this guide.