This is a multi-part message in MIME format. --------------030208090801000703070009 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 03/08/2013 05:16 AM, Dan Kenigsberg wrote:
On Thu, Mar 07, 2013 at 03:57:49PM +0100, Adrian Gibanel wrote:
Just in case it might help you please check:
http://lists.ovirt.org/pipermail/users/2012-April/001751.html This is almost 1 year old, but I did not notice it yet. I love the detailed solution! +1 on NAT network. Except that it can save ip address, it also could reduce the external physical switch's pressure on mac table. Because the VM's mac address is invisible to external switch.
But there're two limitations of NAT network compared with physically bridged network: 1. The VMs attached to the same NAT network, but on different hosts can't hear each other. It could be resolved by constructing a tunnel or tunnels among the hosts in the same cluster and centralizing the mac address management of dnsmasq on ovirt engine. 2. The VMs in NAT network are hidden behind the host. The external host can't initiate a connection to the VM. I think it's fine for a desktop VM.\ For a server VM, it can't be resolved by add a DNAT rule on demand. It's similar to the 'floating ip address' in quantum. ////
Yes, the rant there, about ovirt network being tightly-coupled with a physical interface, is 100% justified. I'm trying to address some of that in http://www.ovirt.org/Features/Nicless_Network but it's a long way to go.
I managed to implement Virtualbox-hostonly-alike networks gathering more info from: http://libvirt.org/formatnetwork.html . You might be also interested in: http://wiki.libvirt.org/page/Networking although I didn't use it myself.
You might probably already know this information but, just in case, here it is.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--------------030208090801000703070009 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 03/08/2013 05:16 AM, Dan Kenigsberg wrote:<br> </div> <blockquote cite="mid:20130307211608.GD14400@redhat.com" type="cite"> <pre wrap="">On Thu, Mar 07, 2013 at 03:57:49PM +0100, Adrian Gibanel wrote: </pre> <blockquote type="cite"> <pre wrap="">Just in case it might help you please check: <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/pipermail/users/2012-April/001751.html">http://lists.ovirt.org/pipermail/users/2012-April/001751.html</a> </pre> </blockquote> <pre wrap=""> This is almost 1 year old, but I did not notice it yet. I love the detailed solution!</pre> </blockquote> +1 on NAT network. Except that it can save ip address, it also could reduce the external physical switch's pressure on mac table. Because the VM's<br> mac address is invisible to external switch. <br> <br> But there're two limitations of NAT network compared with physically bridged network:<br> 1. The VMs attached to the same NAT network, but on different hosts can't hear each other. It could be resolved by constructing a tunnel or tunnels<br> among the hosts in the same cluster and centralizing the mac address management of dnsmasq on ovirt engine.<br> <br> 2. The VMs in NAT network are hidden behind the host. The external host can't initiate a connection to the VM. I think it's fine for a desktop VM.\<br> For a server VM, it can't be resolved by add a DNAT rule on demand. It's similar to the 'floating ip address' in quantum.<br> <br> <em></em><em></em> <blockquote cite="mid:20130307211608.GD14400@redhat.com" type="cite"> <pre wrap=""> Yes, the rant there, about ovirt network being tightly-coupled with a physical interface, is 100% justified. I'm trying to address some of that in <a class="moz-txt-link-freetext" href="http://www.ovirt.org/Features/Nicless_Network">http://www.ovirt.org/Features/Nicless_Network</a> but it's a long way to go. </pre> <blockquote type="cite"> <pre wrap=""> I managed to implement Virtualbox-hostonly-alike networks gathering more info from: <a class="moz-txt-link-freetext" href="http://libvirt.org/formatnetwork.html">http://libvirt.org/formatnetwork.html</a> . You might be also interested in: <a class="moz-txt-link-freetext" href="http://wiki.libvirt.org/page/Networking">http://wiki.libvirt.org/page/Networking</a> although I didn't use it myself. You might probably already know this information but, just in case, here it is. </pre> </blockquote> <pre wrap="">_______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <br> </body> </html> --------------030208090801000703070009--