|
Size: 1060
Comment:
|
← Revision 83 as of 2021-12-31 11:46:57 ⇥
Size: 2729
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Introduction | = It is all about uptime! = |
| Line 3: | Line 3: |
| Its all about uptime. 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: | == The Challenge == Many factors affects such a system, and usually we are not controlling all of them. |
| Line 12: | Line 14: |
| To get around this a redundant system has to be built. | Redundancy for all factors will be very expensive, so here we will focus on the software redundancy, and the physical hardware the software runs on. |
| Line 14: | Line 16: |
| 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. | Realizing that a redundant system consists of many redundant parts, virtualization naturally comes to mind. |
| Line 16: | Line 18: |
| 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. | == Configure your system == |
| Line 18: | Line 20: |
| 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. | * [[KVM Host|KVM Host]] * [[KVM Guest|KVM Guest]] == Manage Virtual Domains == * [[Domain Creation|Domain Creation]] * [[Domain Console|Domain Console]] * [[Domain Destruction|Domain Destruction]] * [[Domain Editing|Domain Editing]] * [[Domain Cloning|Domain Cloning]] * [[Domain Migration|Domain Migration]] == Network Planning == * [[Network Planning|Network Planning]] == Configure a Redundant Service == * [[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]] == Configure a Service == * [[Ansible|Ansible]] * [[Syncthing|Syncthing]] * [[Minidlna|Minidlna]] * [[Checkmk|Checkmk]] * [[Mumble|Mumble]] * [[Ansible|Ansible]] * [[Git|Git]] == Tools == === Networking === * [[nethogs|nethogs]] * [[bwm-ng|bwm-ng]] ''This project is based on the GNU/Linux software packaged by Debian. KVM hosts are running on Bullseye, guests are for the most part running on Bullseye. 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.'' [[TODO|TODO]] |
It is 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.
The Challenge
Many factors affects such a system, and usually we are not controlling all of them.
- Power outage
- Internet access
- Hardware malfunction
- Software updates
Redundancy for all factors will be very expensive, so here we will focus on the software redundancy, and the physical hardware the software runs on.
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
Configure a Service
Tools
Networking
This project is based on the GNU/Linux software packaged by Debian. KVM hosts are running on Bullseye, guests are for the most part running on Bullseye. 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.