On Wed, Jan 8, 2020 at 10:19 AM yam yam <hyunooudy(a)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/4N5DYCXY2...
Several people reported there managing more than 2000 VMs in a single engine.
Best regards,
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)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/4GN3ZRFG276...
--
Didi