<div dir="ltr"><div><div>Thanks Alex, clear now.<br><br></div>Cheers,<br></div>Jay<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/6/2 Alex Glikson <span dir="ltr"><<a href="mailto:GLIKSON@il.ibm.com" target="_blank">GLIKSON@il.ibm.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font face="sans-serif">One of the goals was to separate between
instance placement calculation logic and the orchestration logic, having
each in a separate runtime (see </font><a href="https://blueprints.launchpad.net/nova/+spec/query-scheduler" target="_blank"><font color="blue" size="3"><u>https://blueprints.launchpad.net/nova/+spec/query-scheduler</u></font></a><font size="3">)</font><font face="sans-serif">.
Scheduler and conductor (respectively) seemed like a reasonable choice.</font>
<br>
<br><font face="sans-serif">Regards,</font>
<br><font face="sans-serif">Alex<br>
</font>
<br>
<br>
<br>
<br><font color="#5f5f5f" face="sans-serif" size="1">From:
</font><font face="sans-serif" size="1">Lau Jay <<a href="mailto:jay.lau.513@gmail.com" target="_blank">jay.lau.513@gmail.com</a>></font>
<br><font color="#5f5f5f" face="sans-serif" size="1">To:
</font><font face="sans-serif" size="1">Michael Still <<a href="mailto:mikal@stillhq.com" target="_blank">mikal@stillhq.com</a>>,
</font>
<br><font color="#5f5f5f" face="sans-serif" size="1">Cc:
</font><font face="sans-serif" size="1">OpenStack general mailing
list <<a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a>></font>
<br><font color="#5f5f5f" face="sans-serif" size="1">Date:
</font><font face="sans-serif" size="1">01/06/2013 06:19 PM</font>
<br><font color="#5f5f5f" face="sans-serif" size="1">Subject:
</font><font face="sans-serif" size="1">Re: [Openstack]
Benefits for moving live migration/resize/code migration/provision to conductor</font>
<br><font color="#5f5f5f" face="sans-serif" size="1">Sent by:
</font><font face="sans-serif" size="1">"Openstack"
<openstack-bounces+glikson=<a href="mailto:il.ibm.com@lists.launchpad.net" target="_blank">il.ibm.com@lists.launchpad.net</a>></font>
<br>
<hr noshade><div class="HOEnZb"><div class="h5">
<br>
<br>
<br><font size="3">Hi Michael and other Stackers,<br>
<br>
Sorry one more question, for provision VM instance, there is no interaction
between compute nodes, why also move provision logic to conductor?<br>
</font>
<br><font size="3">Thanks,</font>
<br><font size="3">Jay</font>
<br><font size="3"><br>
</font>
<br><font size="3">2013/6/1 Lau Jay <</font><a href="mailto:jay.lau.513@gmail.com" target="_blank"><font color="blue" size="3"><u>jay.lau.513@gmail.com</u></font></a><font size="3">></font>
<br><font size="3">Thanks Michael for the answer, just want to dig more.<br>
</font>
<br><font size="3">From your answer, it seems that we do not want libvirt
on one node opens up a connection to the other, but from the Gerrit code
diff, I did not notice any change on nova compute, but only move the logic
of live migraiton/resize/code migration from scheduler to conductor, and
conductor still call nova compute directly and once the request cast to
nova compute, libvirt on one node still opens up a connection to the another,
so what is the difference?<br>
<br>
Thanks,<br>
Jay</font>
<br>
<br><font size="3"><br>
</font>
<br><font size="3">2013/6/1 Michael Still <</font><a href="mailto:mikal@stillhq.com" target="_blank"><font color="blue" size="3"><u>mikal@stillhq.com</u></font></a><font size="3">></font>
<br><font size="3">IIRC the discussion from the summit, there was concern
about compute<br>
nodes talking directly to each other. The way live migration works in<br>
libvirt is that the libvirt on one node opens up a connection to the<br>
other and then streams the instance across. If this is bounced off a<br>
conductor, then it makes firewall rules much easier to construct.<br>
<br>
Cheers,<br>
Michael</font>
<br><font size="3"><br>
On Sat, Jun 1, 2013 at 2:53 PM, Lau Jay <</font><a href="mailto:jay.lau.513@gmail.com" target="_blank"><font color="blue" size="3"><u>jay.lau.513@gmail.com</u></font></a><font size="3">>
wrote:<br>
> Hi Stackers,<br>
><br>
> I noticed that there are some blueprints trying to move the logic
of live<br>
> migration/resize/code migration/provision from nova scheduler to nova<br>
> conductor, but the blueprint did not describe clearly the benefits
of doing<br>
> so, can some experts give some explanation on this?<br>
><br>
> I know the original design for nova conductor is for a non-db nova
compute,<br>
> but what's the reason of moving scheduling logic to nova conductor?<br>
><br>
> Thanks,<br>
><br>
> Jay<br>
></font>
<br><font size="3">> _______________________________________________<br>
> Mailing list: </font><a href="https://launchpad.net/~openstack" target="_blank"><font color="blue" size="3"><u>https://launchpad.net/~openstack</u></font></a><font size="3"><br>
> Post to : </font><a href="mailto:openstack@lists.launchpad.net" target="_blank"><font color="blue" size="3"><u>openstack@lists.launchpad.net</u></font></a><font size="3"><br>
> Unsubscribe : </font><a href="https://launchpad.net/~openstack" target="_blank"><font color="blue" size="3"><u>https://launchpad.net/~openstack</u></font></a><font size="3"><br>
> More help : </font><a href="https://help.launchpad.net/ListHelp" target="_blank"><font color="blue" size="3"><u>https://help.launchpad.net/ListHelp</u></font></a><font size="3"><br>
></font>
<br>
<br><tt><font>_______________________________________________<br>
Mailing list: </font></tt><a href="https://launchpad.net/~openstack" target="_blank"><tt><font>https://launchpad.net/~openstack</font></tt></a><tt><font><br>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : </font></tt><a href="https://launchpad.net/~openstack" target="_blank"><tt><font>https://launchpad.net/~openstack</font></tt></a><tt><font><br>
More help : </font></tt><a href="https://help.launchpad.net/ListHelp" target="_blank"><tt><font>https://help.launchpad.net/ListHelp</font></tt></a><tt><font><br>
</font></tt>
<br></div></div></blockquote></div><br></div>