From 6ea6cebc827c13c4f87c4b949edcfc30d2a8698d Mon Sep 17 00:00:00 2001 From: Adam Merka <405417@muni.cz> Date: Tue, 11 Dec 2018 15:54:12 +0100 Subject: [PATCH] Updates 5-images/README.md Auto commit by GitBook Editor --- 5-images/README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/5-images/README.md b/5-images/README.md index 7c99de6..95f747e 100644 --- a/5-images/README.md +++ b/5-images/README.md @@ -6,15 +6,15 @@ HOW TO via CLI: h[ttps://docs.openstack.org/mitaka/user-guide/cli\_use\_snapshot store metadata: [https://docs.openstack.org/mitaka/user-guide/cli\_config\_drive.html](https://docs.openstack.org/mitaka/user-guide/cli_config_drive.html) -## Replikace +## Replication -Replication is the act of continuous copying of the instance content \(more specifically \) to a separate +Replication is the act of continuous copying of the instance content \(more specifically \) to a separate storage. In case of hardware failure of the underlying infrastructure it is possible to spin-up your VM from this copy. This copy is not entirely identical to the original instance Although the copy is recorded periodically, there usually is a few minutes delay compared to the state of the live instance. This is an asynchronnous process. -PĹ™i replikaci se prĹŻběžnÄ› kopĂruje obsah \(respektive probĂhajĂcĂ zmÄ›ny\) virtuálnĂho serveru na oddÄ›lenĂ© ĂşloĹľištÄ›. V pĹ™ĂpadÄ› poruchy hardwaru, na kterĂ©xm virtuálnĂ server běžĂ, je moĹľnĂ© virtuálnĂ server nastartovat z takto udrĹľovanĂ© repliky. Tato replika nenĂ zcela identická s pĹŻvodnĂm virtuálnĂm serverem. Je v nĂ uloĹľen snĂmek provozovanĂ©ho virtuálnĂho serveru, s urÄŤitĂ˝m \(obvykle nÄ›kolikaminutovĂ˝m\) zpoĹľdÄ›nĂm oproti aktuálnĂmu stavu provozovanĂ©ho virtuálnĂho serveru. Jedná se o asynchronnĂ proces. -**High Availability**– běžĂcĂ virtuálnĂ server je nepĹ™etrĹľitÄ› monitorován a v pĹ™ĂpadÄ› vĂ˝padku fyzickĂ©ho hardwaru jsou postiĹľenĂ© virtuálnĂ servery automaticky spuštÄ›ny na jinĂ©m fyzickĂ©m serveru. -**Fault Tolerance**– tato vlastnost umoĹľĹuje běžet jeden virtuálnĂ server na dvou fyzickĂ˝ch serverech. Jedná se o vlastnost funkÄŤnÄ› blĂzkou výše popsanĂ© replikaci. KlĂÄŤovĂ˝m rozdĂlem je to, Ĺľe se jedná o synchronnĂ proces. tj. obÄ› repliky jsou identickĂ©. PouĹľitĂ tĂ©to vlastnosti pĹ™inášà jistá technická omezenĂ. V pĹ™ĂpadÄ› zájmu nás kontaktujte pro upĹ™esnÄ›nĂ. +**High Availability**– the live instance is monitored non-stp and in case of physical hardware failure is immediately spinned up on another physical server. + +**Fault Tolerance**– This feature enables to run one virtual machine on multiuple physical servers. This feature is functionally close to replication and differs in the fact that it is implemented as a synchronnous process. This means that both replicas are identical all of the time. This feature brings about certain technical limitations. Please contact support in case you are interested in this feature, as some things need to be specified and negotiated. ## Public images -- GitLab