<font size=2 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"><font size=3 color=blue><u>https://blueprints.launchpad.net/nova/+spec/query-scheduler</u></font></a><font size=3>)</font><font size=2 face="sans-serif">.
Scheduler and conductor (respectively) seemed like a reasonable choice.</font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br><font size=2 face="sans-serif">Alex<br>
</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Lau Jay <jay.lau.513@gmail.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Michael Still <mikal@stillhq.com>,
</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">OpenStack general mailing
list <openstack@lists.launchpad.net></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">01/06/2013 06:19 PM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [Openstack]
Benefits for moving live migration/resize/code migration/provision to conductor</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"Openstack"
<openstack-bounces+glikson=il.ibm.com@lists.launchpad.net></font>
<br>
<hr noshade>
<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 size=3 color=blue><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 size=3 color=blue><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 size=3 color=blue><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 size=3 color=blue><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 size=3 color=blue><u>openstack@lists.launchpad.net</u></font></a><font size=3><br>
> Unsubscribe : </font><a href=https://launchpad.net/~openstack target=_blank><font size=3 color=blue><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 size=3 color=blue><u>https://help.launchpad.net/ListHelp</u></font></a><font size=3><br>
></font>
<br>
<br><tt><font size=2>_______________________________________________<br>
Mailing list: </font></tt><a href=https://launchpad.net/~openstack><tt><font size=2>https://launchpad.net/~openstack</font></tt></a><tt><font size=2><br>
Post to : openstack@lists.launchpad.net<br>
Unsubscribe : </font></tt><a href=https://launchpad.net/~openstack><tt><font size=2>https://launchpad.net/~openstack</font></tt></a><tt><font size=2><br>
More help : </font></tt><a href=https://help.launchpad.net/ListHelp><tt><font size=2>https://help.launchpad.net/ListHelp</font></tt></a><tt><font size=2><br>
</font></tt>
<br>