Differences between revisions 11 and 23 (spanning 12 versions)
Revision 11 as of 2017-10-10 21:36:12
Size: 1426
Editor: shran
Comment:
Revision 23 as of 2017-10-11 20:29:30
Size: 985
Editor: scott
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Its all about uptime! = Its all about uptime! =
Line 5: Line 5:
These are our worst foes: == These are our worst foes ==
Line 14: Line 14:
Configure your system == Configure your system ==
Line 16: Line 16:
 * [[KVM host|KVM host]]
  *
 *
KVM guest
 * [[KVM Host|KVM Host]]
 * [[KVM Guest|KVM Guest]]
Line 20: Line 19:
== Manage Virtual Machines ==
Line 21: Line 21:
 * [[Creating|Creating]]
 * [[Destroying|Destroying]]
 * [[Cloning|Cloning]]
 * [[Migrating|Migrating]]
Line 22: Line 26:
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. == Configure a Redundant Service ==
Line 24: Line 28:
 * [[DHCP|DHCP]]
 * [[DNS|DNS]]
 
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 etc. is required to use this guide.
Line 25: Line 33:

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.

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.
[[TODO|TODO]]

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 Machines

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 etc. is required to use this guide.

TODO

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