This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --1MadXg0mqwdPfQo9SDIJ0fCrrAojABM77 Content-Type: multipart/mixed; boundary="Wahn8BaEiLvgPeM35wXfBUq8Qdo6tqbSm" From: Sven Kieske <svenkieske@gmail.com> To: users@ovirt.org Message-ID: <571F7533.4070600@gmail.com> Subject: Re: [ovirt-users] Max amount of datacenters per ovirt engine References: <8DDA0C1A-7331-4880-B913-9D7769E07E30@familiealbers.nl> <2126836.ESJW3ukn0O@awels> <9913BF2A-E662-4CB6-94BC-D176912688D6@familiealbers.nl> <CAF0zDV4FzJAG458fQ+jz=bYWrOEYya82pOAm5QDdfwDHzteDeQ@mail.gmail.com> In-Reply-To: <CAF0zDV4FzJAG458fQ+jz=bYWrOEYya82pOAm5QDdfwDHzteDeQ@mail.gmail.com> --Wahn8BaEiLvgPeM35wXfBUq8Qdo6tqbSm Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 26.04.2016 14:46, Martin Sivak wrote:
I think that 1000 hosts per engine is a bit over what we recommend (and support). The fact that all of them are going to be remote might not be ideal either. The engine assumes the network connection to all hosts is almost flawless and the necessary routing and distance to your hosts might not play nice with (for example) the fencing logic.
Hi, this seems a little surprising. At least RHEV states in the documentation you support up to 200 hosts per cluster alone. There are no documented maxima for clusters or datacenters though. @awels: to add another layer of indirection via a dedicated hosted-engine per outlet seems a little much. we are talking about 500 * 4GB RAM at least in this example, so 2 TB RAM just for management purposes, if you follow engine hardware recommendations? But I agree, ovirt does not handle unstable or remote connections that well, so you might be better of with hundredths of remote engines, but it seems to be a nightmare to manage, even if you automate everything. My personal experience is, that ovirt does scale at least until about 30-50 DCs managed by a single engine, but that setup was also on a LAN (but I would say it could scale well beyond these numbers, at least on a LAN). HTH Sven --Wahn8BaEiLvgPeM35wXfBUq8Qdo6tqbSm-- --1MadXg0mqwdPfQo9SDIJ0fCrrAojABM77 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGcBAEBCAAGBQJXH3VKAAoJEAq0kGAWDrqlrU4MALclfaT9+WJgapJdMglTHE6d G8DX2Ka0fAs3rphQDYBpZW73pvgfak0cZmD+MRyHKhn3leCxi0BAwnjlFJOXyt6c XbP/2FiCbq59+sLHT4JoYvgiZLbKGGuCmXNxAmrGHNmReWyXQutoviyK8wxKzg3Q YRsGoi8tHw6aLtAznjbqZ+3WZlACSMnF0gurQrdVfWhQYSHMLkxKMCyNWQECDUc2 yoW52/JS+ghwdTvnhq8PDLZsgUAhRruCZA77vCOa62T5OsIKKISsqOSq0FoBvAi2 WRofgaDNuFgqpXlHBtOswMCWQ2rxhpYzsJqKTsMUwxql2/N/bLe7+RLnMZPqEVt0 fIEllQIUAQLxMJZ1Yi0VDNrUwL/OoAWUS3yrreigERHg/DPY9aohVvZt5+tYYXlK yWowkqSBDQr7xoOpYnekeM5F+S1ivXBlLFpi5EwJDlvArip400r70Gq3Vouifx7P 0QPjnoORNfcjUHZQpeZgJZ6qx9O2GUDCTeCJlN98FA== =zIZZ -----END PGP SIGNATURE----- --1MadXg0mqwdPfQo9SDIJ0fCrrAojABM77--