----- Original Message -----
From: "Sven Kieske" <s.kieske(a)mittwald.de>
Sent: Thursday, April 30, 2015 2:12:55 AM
Subject: Re: [ovirt-users] oVirt HA.
On 29/04/15 21:53, Dan Yasny wrote:
> There is always room for improvement, but think about it: ever since
> SolidICE, there has been a demand to minimize the amount of hardware used
> in a minimalistic setup, thus the hosted engine project. And now that we
> have it, all of a sudden, we need to provide a way to make multiple
> engines work in active/passive mode? If that capability is provided, I'm
> sure a new demand will arise, asking for active/active engines, infinitely
> scalable, and so on.
of course you wan't active/active clusters for an enterprise product,
rather sooner than later
No doubt there, however, that's not *just* HA any longer :)
> The question really is, where the line is drawn. The engine downtime can be
> a few minutes, it's not that critical in setups of hundreds of hosts.
> oVirt's raison d'etre is to make VMs run, everything else is just plumbing
> around that.
ovirt is a provider of critical infrastructure
(vms and their management) for modern it business.
imagine a large organisation just using ovirt for their virtualization,
with lots of different departments which at will can spawn their own
vms, maybe even from different countrys with different time zones (just
like red hat ;) ).
of course, if just the engine service is down for some reason and you
can just restart it with an outage of some seconds, or maybe a minute -
but everything above a minute could become critical for large orgs
relying on the ability to spawn vms at any given time.
I think you're getting away from the point here. If the hosted engine's HA
isn't fast enough, you can cluster the engine in other ways, that were available way
before hosted engine came to be.
or imagine critical HA vms running on ovirt:
you can't migrate them, when the engine is not running.
you might not even want a downtime of a single second for them, that's
why you implemented things like live migration in the first place.
the bottom line is:
if you manage critical infrastructure, the tools to manage
this infrastructure have to be as reliable as the infrastructure itself.
Mit freundlichen Grüßen / Regards
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
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
Users mailing list