Differences between revisions 2 and 36 (spanning 34 versions)
Revision 2 as of 2017-10-10 21:07:14
Size: 562
Editor: shran
Comment:
Revision 36 as of 2017-12-08 15:31:43
Size: 1223
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
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. = Its all about uptime! =
Line 3: Line 3:
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. 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 ==

 * [[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]]
 
''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 and understand this guide.''

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

TODO

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