Re: [Engine-devel] Bug 1076530 – engine shouldn't kill the vds running the VM with the hosted engine
----- Original Message -----
From: "Yedidyah Bar David" <didi(a)redhat.com>
To: "Sandro Bonazzola" <sbonazzo(a)redhat.com>
Cc: "engine-devel" <engine-devel(a)ovirt.org>
Sent: Monday, March 17, 2014 10:21:39 AM
Subject: Re: [Engine-devel] Bug 1076530 – engine shouldn't kill the vds running the
VM with the hosted engine
> >>>>>> I'm not keen on adding hosted-engine logic into the
engine code.
> >>>>>
> >>>>> Not sure about that. Not that it would help much, because the
root
> >>>>> problem will still have to be solved, but in principle it might
be
> >>>>> a good thing if the engine knows that killing some host will
kill
> >>>>> itself,
> >>>>> and so try harder to not do that and just leave it in some
zombie,
> >>>>> requires-manual-action state. This is obviously more important
during
> >>>>> normal operation than during installation.
BTW, no-one addressed the original point in the bug.
We might solve the specific compatibility level issue, but the general
question still remains: Should the engine treat differently the VM and host
that are running itself? Knowing that killing them means committing suicide
(or, in other words, probably require manual cli action from the user)?
This is what I'm trying to avoid. It is possible but will add special logic
we should try to avoid. If the setup makes sure you have a running deployment
you can leave it as is. the user will always be able to do bad things in the
system and we should not nanny them, as long as they are aware of what they do.
--
Didi