Re: [ovirt-devel] [ovirt-users] oVirt HA.
On 28/04/15 16:20, Dan Yasny wrote:
HA does not mean multiple running instances of the same service. It means if the service is gone, it will automatically be restored on a working server.
That is a pretty narrow definition of HA, which is not shared by most parts of the community (and the world), leading to much confusion of users on this very ML. HA in general means your service downtime gets minimized, today mostly realized through load balancing and clustering software services. just restarting a service (in this case ovirt-engine vm) on a different host is not what todays user expect under the term "HA" imho. in theory it should be possible as a design goal to make multiple ovirt-engine share one remote data base (remote database support is already there). I think this would be a huge feature for ovirt, but also requires quite some design and coding to be done. thus adding the devel list. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
On 04/29/2015 10:39 AM, Sven Kieske wrote:
On 28/04/15 16:20, Dan Yasny wrote:
HA does not mean multiple running instances of the same service. It means if the service is gone, it will automatically be restored on a working server. That is a pretty narrow definition of HA, which is not shared by most parts of the community (and the world), leading to much confusion of users on this very ML.
HA in general means your service downtime gets minimized, today mostly realized through load balancing and clustering software services.
just restarting a service (in this case ovirt-engine vm) on a different host is not what todays user expect under the term "HA" imho.
in theory it should be possible as a design goal to make multiple ovirt-engine share one remote data base (remote database support is already there).
I think this would be a huge feature for ovirt, but also requires quite some design and coding to be done.
thus adding the devel list.
Please open RFE with this and we can consider that for future versions. -- Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: ydary@redhat.com IRC : ydary
On 29-04-2015 20:17, Yaniv Dary wrote:
On 04/29/2015 10:39 AM, Sven Kieske wrote:
On 28/04/15 16:20, Dan Yasny wrote:
HA does not mean multiple running instances of the same service. It means if the service is gone, it will automatically be restored on a working server. That is a pretty narrow definition of HA, which is not shared by most parts of the community (and the world), leading to much confusion of users on this very ML.
HA in general means your service downtime gets minimized, today mostly realized through load balancing and clustering software services.
just restarting a service (in this case ovirt-engine vm) on a different host is not what todays user expect under the term "HA" imho.
in theory it should be possible as a design goal to make multiple ovirt-engine share one remote data base (remote database support is already there).
I think this would be a huge feature for ovirt, but also requires quite some design and coding to be done.
thus adding the devel list.
Please open RFE with this and we can consider that for future versions.
See: http://www.ovirt.org/Features/Engine_High_Availability Engine's PostgreSQL DB should also be replicated in a master-master fashion.
participants (3)
-
Christopher Pereira -
Sven Kieske -
Yaniv Dary