Open Stack

2011/8/22 Rogério Vinhal Nunes <rogervn at dcc.ufmg.br>:
> Hi, I'm new to Nova and would like to clear up some issues.
>
> The Nova's compute node networking configuration creates the default bridge
> (br100), copying eth0 values and connecting the actual eth0 along with the
> VMs. Xen does almost that, it renames the physical eth0 to peth0 and creates
> a bridge named eth0 that connects the VMs and peth0.
>
> Could Nova work using the Xen's eth0 bridge? I think if it was the old
> '"xenbr0" bridge it could be easier just to change the bridge name in the
> DB, but how does that work even with the controller not habing Xen installed
> (so eth0 would be the real interface)?
>

What version of Xen do you have and on what distro?

Xen 4.1+ doesn't do this crazy renaming anymore and instead uses the
built in distro supported networking. Using the distro supported
networking is likely to work better, so it is often recommended. See:

http://wiki.xensource.com/xenwiki/HostConfiguration/Networking (this
should work with any version of Xen + Linux)

> Also, in the Administrator's Manual, it says that you need KVM + libvirt for
> live migration, would Nova work with Xen for live migration?
>

It should work the same, but I don't know how much it has been tested.
Let us know if it doesn't work.

A lot of the Xen testing up to this point has been on Citrix XenServer
and its open source counterpart XCP. We'd love to see Xen the
hypervisor work fine as it seems that is some interest there too.

libvirt works with Xen hypervisor, so it should work just like it does with KVM.

Feel free to bring xen-specific issues over to the appropriate xen
mailings lists.

Thanks,
Todd

-- 
Todd Deshane
http://www.linkedin.com/in/deshantm
http://www.xen.org/products/cloudxen.html
http://runningxen.com/