<div><br></div>The relationship between ManageIQ and CloudForms seems the same as the one between oVirt and RHEVM, right?<div><br></div><div>Thank you so much for all your hard work and good<span></span> information. </div><div><br></div><div>Sunny<br><br><br>2016년 3월 6일 일요일, Yaniv Kaul<<a href="mailto:ykaul@redhat.com">ykaul@redhat.com</a>>님이 작성한 메시지:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Mar 5, 2016 at 4:48 AM, Sunny Shin <span dir="ltr"><<a href="javascript:_e(%7B%7D,'cvml','sunny4s.git@gmail.com');" target="_blank">sunny4s.git@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><br></div>It seems one engine has limitation such as not supporting over thousands or ten thousands of hosts. I heard that openstack supports unlimited(?) hosts with engine clustering similar to active-active ha. So, I thought that if active-active ha is supported, much more hosts are supported with one engine set. </blockquote><div><br></div><div>As for OpenStack, I'll just advise that you don't believe everything you hear. </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><br></div><div>With current ovirt engine, if we want to deploy thousands of hosts, we may need multiple separate engines with hundreds of hosts each. And each engine has its own admin portal without one combined user interface.<span></span> Am I right?</div></blockquote><div><br></div><div>Correct, though you can and should use ManageIQ[1] for example to manage multiple oVirt engines. We are eagerly working on improving our integration with it.</div><div>We are looking both into the next generation of oVirt engine to allow higher scale as well as the coming release to improve the scale somewhat.</div><div>Y.</div><div><br></div><div>[1] <a href="http://manageiq.org/" target="_blank">http://manageiq.org/</a></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><br></div><div>Sunny</div><div><div> <br><br>2016년 3월 5일 토요일, Yaniv Kaul<<a href="javascript:_e(%7B%7D,'cvml','ykaul@redhat.com');" target="_blank">ykaul@redhat.com</a>>님이 작성한 메시지:<div><div><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Mar 4, 2016 at 11:48 AM, Sunny Shin <span dir="ltr"><<a>sunny4s.git@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><br></div><div>Yaniv,</div><div><br></div><div>Could you a little bit more elaborate what you are working on for engine scailability? I thought that active-active ha is the only way for that.</div></blockquote><div><br></div><div>Active Active is useful for both HA (where we believe hosted-engine is a good solution) as well as scalability. If we improve the current scalability, then we are good there too.</div><div>I've given several items below - it'd be difficult to enumerate all of them - I suggest going through the gerrit commits in the last 2 months or so and look at some of the work that has taken and is taking place, across all areas of the product. Few random examples:</div><div><a href="https://gerrit.ovirt.org/#/c/36593/" target="_blank">https://gerrit.ovirt.org/#/c/36593/</a><br></div><div><a href="https://gerrit.ovirt.org/#/c/51235/" target="_blank">https://gerrit.ovirt.org/#/c/51235/</a><br></div><div><br></div><div><br></div><div>Is there anything specifically you are looking for?</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><span></span></div><div><br></div><div>Sunny</div><br><br>2016년 3월 4일 금요일, Yaniv Kaul<<a>ykaul@redhat.com</a>>님이 작성한 메시지:<div><div><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 4, 2016 at 10:45 AM, Sunny Shin <span dir="ltr"><<a>sunny4s.git@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi Yaniv,<div><br></div><div>Is there a plan to implement active-active HA in the near future? Is there any progress on it since the discussion in August 2013?</div></div></blockquote><div><br></div><div>No, not at the moment. We feel that Self-Hosted Engine (SHE) is a great solution thus far.</div><div>We are working on improving the performance and scale of the engine, to be able to handle more load, more hosts, more VMs, etc.</div><div>This is an ongoing work across all components, from VDSM, to engine core, REST API, database calls and more.</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><span><font color="#888888"><div><br></div><div>Sunny</div></font></span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2016-03-04 17:38 GMT+09:00 Yaniv Kaul <span dir="ltr"><<a>ykaul@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Fri, Mar 4, 2016 at 2:03 AM, Sunny Shin <span dir="ltr"><<a>sunny4s.git@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>Hi All,</div><div><br></div><div>In the new architecture page (<a href="http://www.ovirt.org/documentation/architecture/architecture/" target="_blank">http://www.ovirt.org/documentation/architecture/architecture/</a>), overall architecture picture shows that engine supports active-active high availability.</div></div></blockquote><div><br></div></span><div>This is inaccurate - the engine is not highly available in A/A architecture. I'd appreciate if you could file an issue for it so we'll fix this page.</div><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>However, as per engine HA page (<a href="http://www.ovirt.org/develop/release-management/features/engine/engine-high-availability/" target="_blank">http://www.ovirt.org/develop/release-management/features/engine/engine-high-availability/</a>), active-active HA is not supported yet and there are several implementation issues.</div><div><br></div><div>So, could anyone give me a brief explanation about discrepancy between these two pages, and about the plan to implement this feature if not implemented yet?</div></div></blockquote><div><br></div></span><div>I suggest looking at self-hosted engine, which provides non-A/A high availability for the engine.</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><span><font color="#888888"><div><br></div><div>Sunny</div></font></span></div>
<br>_______________________________________________<br>
Devel mailing list<br>
<a>Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/devel</a><br></blockquote></div><br></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>
</blockquote>
</div></div></blockquote></div><br></div></div>
</blockquote></div></div></div></div>
</blockquote></div><br></div></div>
</blockquote></div>