is there any feature of load balancing for engine??
Hello, given massive oVirt environment, I think single engine looks too small to deal with all workloads. so, I want to make active-active engine cluster for distributing workloads. is it possible for an oVirt environment to be made up of multiple engines & DBs for load balancing?
WIth an engine on bare-metal, and highly specced bare-metal, I find it hard to imagine a scenario where it would be too overwhelming for the engine to handle. If you are that worried, I would block it into logical areas, either by City, DC, Cluster etc. But unless you are talking about an international major CDN / Cloud provider with multiple racks of servers in many major cities, I think you would be fine. On 8/1/20 12:51 pm, yam yam wrote:
Hello,
given massive oVirt environment, I think single engine looks too small to deal with all workloads. so, I want to make active-active engine cluster for distributing workloads. is it possible for an oVirt environment to be made up of multiple engines & DBs for load balancing? _______________________________________________ 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/XCO5DJS63YKC63...
thanks for your reply! :) I was skeptical because only an engine should handle "many requests" toward it as front-end, periodic communication to each VDSM, VM scheduling and so on. but, as you said, highly specced bare-metal is enough to cover that, right??
On Wed, Jan 8, 2020 at 10:19 AM yam yam <hyunooudy@gmail.com> wrote:
thanks for your reply! :)
I was skeptical because only an engine should handle "many requests" toward it as front-end, periodic communication to each VDSM, VM scheduling and so on. but, as you said, highly specced bare-metal is enough to cover that, right??
You might want to look at "Supported Limits for Red Hat Virtualization", which I think should apply to oVirt more-or-less as-is: https://access.redhat.com/articles/906543 Also: oVirt Survey 2019 results https://lists.ovirt.org/archives/list/announce@ovirt.org/thread/4N5DYCXY2S6Z... Several people reported there managing more than 2000 VMs in a single engine. Best regards,
_______________________________________________ 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/4GN3ZRFG276PLM...
-- Didi
Thanks David, I've just checked it and that's what I want. an engine seems quite enough in the usual case. Best regards,
participants (3)
-
Joseph Goldman -
yam yam -
Yedidyah Bar David