Differences between revisions 15 and 54 (spanning 39 versions)
Revision 15 as of 2017-10-10 22:51:56
Size: 1579
Editor: shran
Comment:
Revision 54 as of 2020-02-11 21:26:14
Size: 1469
Comment:
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
Basic knowledge of GNU/Linux commandline tools is required to use this guide. These tools will not be explained here.
Line 19: Line 17:
  *
 *
KVM Guest
 * [[KVM Guest|KVM Guest]]
Line 22: Line 19:
== Manage Virtual Domains ==
Line 23: Line 21:
 * [[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 28:
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 30:
 * [[Network Planning|Network Planning]]
Line 27: Line 32:
== Configure a Redundant Service ==
Line 28: Line 34:
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]]
 * [[ownCloud|ownCloud]]
Line 30: Line 47:
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 stretch 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!

The main goal is to go as close to no downtime as possible.

These are our worst foes

  • 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 stretch 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.

TODO

None: Uptime (last edited 2021-12-31 11:46:57 by Kristian Kallenberg)