Hello Everyone, I'm new to oVirt so I was hoping I could pick the brains of those that may have been around the product longer than myself. To start, I am leveraging oVirt 4.2, so all questions will be centered around them. 1. I am looking to utilize the ovirt engine for managing potentially thousands of datacenters, has anyone experienced large scale deployments or many-multi datacenter installations all managed under the same engine? FWIW: There will only be 1-2 servers per datacenter, with one cluster and 5-10 vNic assignments per cluster. 2. Has anyone dealt with the auto registration/approval process with oVirt engine? I'm finding various documentation from different generations of oVirt, but haven't felt comfortable with what i've found since my instance doesn't seem to have features that i'm reading about. My goal is to ship servers to a site with a basic image and when it boots up it reaches out to our ovirt engine, in turn I can automate a validation of pending approval requests based on host criteria, i'm just struggling to figure out if the automatic registration is even a thing in the latest version. thank you in advance, I appreciate any feedback on the matter. -Brad
Il giorno gio 20 set 2018 alle ore 22:15 <brad.riemann@cloud5.com> ha scritto:
Hello Everyone,
I'm new to oVirt so I was hoping I could pick the brains of those that may have been around the product longer than myself.
Welcome to oVirt community!
To start, I am leveraging oVirt 4.2, so all questions will be centered around them.
1. I am looking to utilize the ovirt engine for managing potentially thousands of datacenters, has anyone experienced large scale deployments or many-multi datacenter installations all managed under the same engine? FWIW: There will only be 1-2 servers per datacenter, with one cluster and 5-10 vNic assignments per cluster.
I would suggest to use ManageIQ to manage multiple oVirt datacenters from a single entry point
2. Has anyone dealt with the auto registration/approval process with oVirt engine? I'm finding various documentation from different generations of oVirt, but haven't felt comfortable with what i've found since my instance doesn't seem to have features that i'm reading about.
Adding Ryan to assist on this
My goal is to ship servers to a site with a basic image and when it boots up it reaches out to our ovirt engine, in turn I can automate a validation of pending approval requests based on host criteria, i'm just struggling to figure out if the automatic registration is even a thing in the latest version.
So the use case here is having an oVirt engine managing geographically distributed datacenters right? Would it fit your case an hyper-converged setup (3 hosts + 1 hosted engine + local glusterfs storage on the same hosts) and access to those managers through single ManageIQ instance?
thank you in advance, I appreciate any feedback on the matter.
-Brad _______________________________________________ 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/KCADYPT6A3R2OW...
-- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f2000000RgRyAAK>
Thanks Sandro! I saw ManageIQ, it might be a better solution if we had more nodes in each datacenter which resulted in a larger footprint, however my use case would only see one oVirt node per datacenter where we were looking at a possibility of 3k nodes, would that be too many for an oVirt engine to handle? (we wouldn't have resource limitations due to using with a cloud provider for scale-ability). If I ended up having to put oVirt engine instances in each datacenter we'd have basically a 1:1 node to engine ratio, not the end of the world and possibly easier to use but it would induce some complexities to the deployment strategy i'm working on. Again, thank you! -Brad
Il giorno ven 21 set 2018 alle ore 16:24 <brad.riemann@cloud5.com> ha scritto:
Thanks Sandro!
I saw ManageIQ, it might be a better solution if we had more nodes in each datacenter which resulted in a larger footprint, however my use case would only see one oVirt node per datacenter where we were looking at a possibility of 3k nodes, would that be too many for an oVirt engine to handle? (we wouldn't have resource limitations due to using with a cloud provider for scale-ability).
If I ended up having to put oVirt engine instances in each datacenter we'd have basically a 1:1 node to engine ratio, not the end of the world and possibly easier to use but it would induce some complexities to the deployment strategy i'm working on.
I've no official documentation in oVirt for this, but looking at Red Hat Virtualization product (the downstream packaging of oVirt supported by Red Hat) documentation I see a limit of 200 hosts per ovirt-engine instance ( https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/htm... ) This means you'll need at least 15 engine instances, possibly managed by ManageIQ to ease access to them, to handle 3000 hosts. Using a single node per deployment seems you don't have requirement on high availability of the VMs running on it and no migrations between the nodes right?
Again, thank you!
-Brad _______________________________________________ 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/BD6KSHQ2NW7RYM...
-- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f2000000RgRyAAK>
Sandro, Thank you for the link, that question is answered. I'll clearly have to figure out a solution that works around our particular requirements and constraints. -Brad
Il giorno ven 21 set 2018 alle ore 16:24 <brad.riemann@cloud5.com> ha scritto:
Thanks Sandro!
I saw ManageIQ, it might be a better solution if we had more nodes in each datacenter which resulted in a larger footprint, however my use case would only see one oVirt node per datacenter where we were looking at a possibility of 3k nodes, would that be too many for an oVirt engine to handle? (we wouldn't have resource limitations due to using with a cloud provider for scale-ability).
If I ended up having to put oVirt engine instances in each datacenter we'd have basically a 1:1 node to engine ratio, not the end of the world and possibly easier to use but it would induce some complexities to the deployment strategy i'm working on.
I've no official documentation in oVirt for this, but looking at Red Hat Virtualization product (the downstream packaging of oVirt supported by Red Hat) documentation I see a limit of 200 hosts per ovirt-engine instance ( https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/htm... )
In 4.2 we made various changes and that resulted in at least 400 hosts per engine. We stopped testing for more because we didn't see use case above
On Fri, 21 Sep 2018 at 17:53 Sandro Bonazzola <sbonazzo@redhat.com> wrote: that. With few tweaks you can get there, and there is a chance it would suite your needs. but no one tested that kind of a stretched setup with thousands of datacenters. If you want to test it you can use nested virtualization. Create VMs that would serve as nodes, and add those as hosts for each single host datacenter you want. And report back with your finding! This means you'll need at least 15 engine instances, possibly managed by
ManageIQ to ease access to them, to handle 3000 hosts. Using a single node per deployment seems you don't have requirement on high availability of the VMs running on it and no migrations between the nodes right?
Again, thank you!
-Brad _______________________________________________ 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/BD6KSHQ2NW7RYM...
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f2000000RgRyAAK> _______________________________________________ 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/E2T2DMFIQOBVPQ...
Thanks for the feedback guys, knowing that up to 400 was tested was a huge bump for my purposes. I've gotten ManageIQ online and connected to the ovirt engine, thanks for that suggestion this will work just fine. Hopefully autoregistration is still feasible, ill be going off assumptions that i'll have to create something to automate the registration process for now. Again, thank you for the responses, incredibly helpful! -Brad
participants (3)
-
brad.riemann＠cloud5.com -
Roy Golan -
Sandro Bonazzola