openstack team mailing list archive
Mailing list archive
Re: Benefits for moving live migration/resize/code migration/provision to conductor
IIRC the discussion from the summit, there was concern about compute
nodes talking directly to each other. The way live migration works in
libvirt is that the libvirt on one node opens up a connection to the
other and then streams the instance across. If this is bounced off a
conductor, then it makes firewall rules much easier to construct.
On Sat, Jun 1, 2013 at 2:53 PM, Lau Jay <jay.lau.513@xxxxxxxxx> wrote:
> Hi Stackers,
> I noticed that there are some blueprints trying to move the logic of live
> migration/resize/code migration/provision from nova scheduler to nova
> conductor, but the blueprint did not describe clearly the benefits of doing
> so, can some experts give some explanation on this?
> I know the original design for nova conductor is for a non-db nova compute,
> but what's the reason of moving scheduling logic to nova conductor?
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp