On Thu, Aug 8, 2019 at 8:04 PM Strahil <hunter86_bg@yahoo.com> wrote:
I think poison pill-based fencing is easier to implement but it requires either Network-based (iSCSI or NFS) or FC-based shared storage.
It is used in corosync/pacemaker clusters and is easier to implement.
Corosync/pacemake uses completely different way how to perform fencing and this is not applicable for oVirt.
But oVirt also uses shared storage information (we call it storage leases) which can detect that host is still running and only connection between enigne and host is broken. For details about VM leases please take a look:
Best Regards,
Strahil NikolovOn Aug 8, 2019 11:29, Sandro Bonazzola <sbonazzo@redhat.com> wrote:Il giorno ven 2 ago 2019 alle ore 10:50 Sandro E <feeds.sandro@gmail.com> ha scritto:Hi,
i hope that this hits the right people i found an RFE (Bug 1373957) which would be a realy nice feature for my company as we have to request firewall rules for every new host and this ends up in a lot of mess and work. Is there any change that this RFE gets implemented ?
You can specify custom firewalld rules, which are applied during host installation/reinstallation:
So is there anything you are missing?
Thanks for any help or tipsThis RFE has been filed in 2016 and didn't got much interest so far. Can you elaborate a bit on the user story for this?
BR,
Sandro
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UP7NZWXZBNHM7B7MNY5NMCAUK6UBPXXD/
--Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
