[ovirt-devel] design flaw in ovirt
S.Kieske at mittwald.de
Fri Jun 20 12:52:47 UTC 2014
Am 20.06.2014 14:19, schrieb Dan Kenigsberg:
>> the host was not fenced, the vms where fenced.
>> here is a link to the documentation which should explain what I mean:
> Are you refering to the paragraph: "When a required network becomes
> non-operational, the virtual machines running on the network are fenced
> and migrated to another host. This is beneficial if you have machines
> running mission critical workloads."?
>> this is about a single host in a cluster - ovirt can't even fence
>> single hosts in a single cluster yet, see my other bug report for this:
>> I could provide logs if they are really necessary, but I doubt they are.
>> This is documented behaviour, but it is poorly designed, as described
>> in the BZ.
> Apparently, I am not familiar enough with Engine's fencing logic; logs
> may help me understand the issue, for me they are necessary is this
> case. In particular, I'd like to see with my own eyes whether the VMs
> where explicitly destroyed by Engine. Migrating VMs to an operational
> destination makes a lot of sense. Destroying a running VM in attempt
> to recuperate of a host networking issue is extraordinary (and as such,
> requires exraordinary evidence).
I might be able to attach some logs later.
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
More information about the Devel