[ovirt-devel] Engine High Availability

Yaniv Kaul ykaul at redhat.com
Fri Mar 4 09:29:54 UTC 2016


On Fri, Mar 4, 2016 at 10:45 AM, Sunny Shin <sunny4s.git at gmail.com> wrote:

> Hi Yaniv,
>
> Is there a plan to implement active-active HA in the near future? Is there
> any progress on it since the discussion in August 2013?
>

No, not at the moment. We feel that Self-Hosted Engine (SHE) is a great
solution thus far.
We are working on improving the performance and scale of the engine, to be
able to handle more load, more hosts, more VMs, etc.
This is an ongoing work across all components, from VDSM, to engine core,
REST API, database calls and more.
Y.


>
> Sunny
>
> 2016-03-04 17:38 GMT+09:00 Yaniv Kaul <ykaul at redhat.com>:
>
>>
>>
>> On Fri, Mar 4, 2016 at 2:03 AM, Sunny Shin <sunny4s.git at gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> In the new architecture page (
>>> http://www.ovirt.org/documentation/architecture/architecture/), overall
>>> architecture picture shows that engine supports active-active high
>>> availability.
>>>
>>
>> This is inaccurate - the engine is not highly available in A/A
>> architecture. I'd appreciate if you could file an issue for it so we'll fix
>> this page.
>>
>>
>>>
>>> However, as per engine HA page (
>>> http://www.ovirt.org/develop/release-management/features/engine/engine-high-availability/),
>>> active-active HA is not supported yet and there are several implementation
>>> issues.
>>>
>>> So, could anyone give me a brief explanation about discrepancy between
>>> these two pages, and about the plan to implement this feature if not
>>> implemented yet?
>>>
>>
>> I suggest looking at self-hosted engine, which provides non-A/A high
>> availability for the engine.
>> Y.
>>
>>
>>>
>>> Sunny
>>>
>>> _______________________________________________
>>> Devel mailing list
>>> Devel at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20160304/b56cee69/attachment-0001.html>


More information about the Devel mailing list