<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>High Availability on</title><link>https://docs.opennebula.io/7.2/product/control_plane_configuration/high_availability/</link><description>Recent content in High Availability on</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 17 Feb 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://docs.opennebula.io/7.2/product/control_plane_configuration/high_availability/index.xml" rel="self" type="application/rss+xml"/><item><title>Overview</title><link>https://docs.opennebula.io/7.2/product/control_plane_configuration/high_availability/overview/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/control_plane_configuration/high_availability/overview/</guid><description>&lt;!--# Overview --&gt;
&lt;p&gt;No host or service is absolutely reliable; we experience failures across various areas every day. To avoid the down-time and the consequent damages, we try to avoid a single point of failure by running several instances of the same service. Failure of one instance doesn’t mean complete service unavailability, as there are other instances that can handle the workload. Such deployment is &lt;strong&gt;highly available&lt;/strong&gt; and resilient to partial failure.&lt;/p&gt;</description></item><item><title>Front-end HA</title><link>https://docs.opennebula.io/7.2/product/control_plane_configuration/high_availability/frontend_ha/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/control_plane_configuration/high_availability/frontend_ha/</guid><description>&lt;p&gt;&lt;a id="frontend-ha-setup"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a id="oneha"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# OpenNebula Front-end HA --&gt;
&lt;p&gt;OpenNebula provides a built-in mechanism to ensure high availability (HA) of the core Front-end daemon, &lt;code&gt;oned&lt;/code&gt;. Services need to be deployed and configured across several hosts, and a distributed consensus protocol enforced to provide fault-tolerance and state consistency across them. Such deployment is resilient to the failure of at least a single host, depending on the total number of hosts.&lt;/p&gt;
&lt;p&gt;In this section, you learn the basics of how to bootstrap a distributed highly available OpenNebula Front-end.&lt;/p&gt;</description></item><item><title>VM HA</title><link>https://docs.opennebula.io/7.2/product/control_plane_configuration/high_availability/vm_ha/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/control_plane_configuration/high_availability/vm_ha/</guid><description>&lt;p&gt;&lt;a id="ftguide"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a id="vm-ha"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Virtual Machines High Availability --&gt;
&lt;p&gt;The goal of this section is to provide information to prepare for failures of the Virtual Machines or Hosts and to recover from them. These failures are categorized depending on whether they come from the physical infrastructure (Host failures) or from the virtualized infrastructure (VM crashes). In both scenarios, OpenNebula provides a cost-effective failover solution to minimize downtime from server and OS failures.&lt;/p&gt;</description></item></channel></rss>