<div>Hi John,</div><div><br></div><div> thanks for your careful answer. I just backed from vacation, too and wish you have had a good time.</div><div><br></div><div> I have been reading these documents again and again to check if I missed something. My current understanding is: when I have two NIC, I should configure xenbr0 and xenbr1 as default. Then under flat network assumption, for each traffic type, I should create a vif in each control domU, with a specific flat IP address range assigned to them (These addresses should correspond to the bridge I choose to let flat condition hold). And when each guest is starting, they will can have two vif, one for VM network, and one for optional floating public address. </div>
<div> Am I right about the configuration here? If true, then is it also combine the traffic of, for example, management and public access? It may sound stupid but I just want to confirm if it works as I expected.</div>
<div><br></div><div> for multi-node nova-network I think I almost get it. I previously thought each of which works individually but from nova-manage result I think I was wrong. The only thing that still troubles me is whether I write the correct config in nova.conf. I think 'xxx_interface' should be filled with VIF name, and 'xxx_bridge' should be filled with BRIDGE name, is this correct? Looks a little confusing anyway.</div>
<div><br></div><div> I have manually patched the vif script with the 5.6 patch, but each time I start the host-rule script, the VM is then not accessible from ssh.</div><div><br></div><div> lastly for quantum, the major difficulties for me is the agent installation of OVS plugins. It seems agents will rely on quantum modules, which then try to load 'libudev'. However, libudev does not exist on CentOS 5.4 as far as I know, so that prevents me from marching on. Maybe this is not the case for Debian/Ubuntu-XCP development, but it does trouble XCP using.</div>
<div><br></div><div>thanks again for your help.</div><div><br></div>On Tue, Nov 20, 2012 at 10:59 AM, John Garbutt <span dir="ltr"><<a href="mailto:John.Garbutt@citrix.com" target="_blank">John.Garbutt@citrix.com</a>></span> wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There are docs here:<br>
<a href="http://docs.openstack.org/folsom/openstack-compute/admin/content/introduction-to-xen.html" target="_blank">http://docs.openstack.org/folsom/openstack-compute/admin/content/introduction-to-xen.html</a><br>
And networking info here:<br>
<a href="http://docs.openstack.org/folsom/openstack-compute/admin/content/xenapi-flat-dhcp-networking.html" target="_blank">http://docs.openstack.org/folsom/openstack-compute/admin/content/xenapi-flat-dhcp-networking.html</a><br>
<br>
Let me know what bits are confusing, and I will make an effort to improve the docs around that area, and help you through things.</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Firstly, quantum support in XCP (with OVS) is still a work in progress. Help to review the changes in Gerrit are very welcome!</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Now, lets look at your questions...<br>
<div class="im"><br>
> 1 Controller node: no Xen, only Ubuntu 12.04, everything for openstack service except for nova-compute<br>
> 2 Compute node: XCP 1.6 beta, with nova-compute in special domU (Ubuntu 12.04), xenapi plugin installed in dom0<br>
</div><div class="im">> each node has two NIC, one with public IP (Only limited floating IP), and another in private network (Any IP is OK)<br>
</div><div class="im">> flat network or flat dhcp network<br>
</div><div class="im">> I want to use eth0 for public traffic and service request, and eth1 for inter-vm traffic.<br>
<br>
</div>OK, but where is your management traffic, like Rabbit and MySQL going? I would have expected one nic for management network, and one nic for public traffic, with maybe with a separate VLAN for instance traffic?<br>
<div class="im"><br></div></blockquote><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
1.) does each domU need nova-network running? My understanding is it's OK to run nova-network individually, but then how to mange the floating IP globally?<br>
<br>
</div>Correct. If multi_host=true, you are running nova-network on every node, if false you just run one. It depends if you don't mind the extra overhead or not. Others can describe the trade-offs more clearly.<br>
<a href="http://docs.openstack.org/folsom/openstack-compute/admin/content/xenapi-flat-dhcp-networking.html" target="_blank">http://docs.openstack.org/folsom/openstack-compute/admin/content/xenapi-flat-dhcp-networking.html</a><br>
<div class="im"><br>
2.) in document for flatdhcp network, I saw four interfaces for each management domU. Is it OK to have only two interfaces? Say, eth0-xenbr0 for public IP and services, and eth1-xenbr1 for VM network?<br>
<br>
</div>As above, you need to think about where your management traffic like MySQL and Rabbit traffic is going. Three is certainly fine.<br>
<div class="im"><br>
3.) Is the network isolation rules a must for test install? I found the patch to vif is still for xenserver 5.6_p2, and can not be applied to vif of xcp 1.6 or xenserver 6.1, which might be a trouble.<br>
<br>
</div>It is not required for a test setup. Do bug me if you are having problems with that stuff on XCP, and I can ask the XCP guys to help me get that working for you.<br>
<br>
Sorry for the slow response. I was on holiday.<br>
<br>
Thanks,<br>
John<br>
<br>
> From: openstack-bounces+john.garbutt=<a href="mailto:citrix.com@lists.launchpad.net">citrix.com@lists.launchpad.net</a><br>
> [mailto:<a href="mailto:openstack-bounces%2Bjohn.garbutt">openstack-bounces+john.garbutt</a>=<a href="mailto:citrix.com@lists.launchpad.net">citrix.com@lists.launchpad.net</a>]<br>
> On Behalf Of Yan Zhai<br>
> Sent: 20 November 2012 7:52 AM<br>
> To: Afef MDHAFFAR<br>
> Cc: <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> Subject: Re: [Openstack] Networking issues for openstack on XCP<br>
<div class="HOEnZb"><div class="h5">><br>
> have even more trouble setting up quantum itself. The plugin support in<br>
> XCP looks not as good as KVM: the first problem is python 2.6 and it's solved<br>
> by adding new repository. But when I installed the openvswitch agent, it<br>
> can not start, requiring some quantum python module, which then seems<br>
> have dependency on libudev. And this means I have to update almost the<br>
> whole dom0, including libc, udev, and blablabla to get that library. That's<br>
> too risky. Maybe I shall stay with bridge plugin and see if things can be a<br>
> little better...<br>
><br>
> On Sat, Nov 17, 2012 at 1:18 PM, Afef MDHAFFAR<br>
> <<a href="mailto:afef.mdhaffar@gmail.com">afef.mdhaffar@gmail.com</a>> wrote:<br>
> Hi all,<br>
><br>
> I am also trying to install openstack, with xcp. I used devstack to do that,<br>
> since it is more simple.<br>
> However, I am still facing a network problem.<br>
> Actually, I got a private network per physical node. I am able to access the<br>
> tenant VMs from the corresponding openstack DomU. But, these tenant<br>
> VMs are not inaccessible from any other machines.<br>
> Is that normal (ie. a private network per physical node? The created tenant<br>
> VMs can access external machines, but they are invisible to other machines?<br>
> Is there any way to let my VMs accessible, at least from other tenant VMs<br>
> (created on other physical nodes)?<br>
> How can Quantum solve this problem?<br>
><br>
> Thank you<br>
><br>
> Regards,<br>
> Afef<br>
><br>
> 2012/11/17 Yan Zhai <<a href="mailto:zhaiyan920@gmail.com">zhaiyan920@gmail.com</a>> Hi Robert,<br>
><br>
> thanks for reply. Currently I am just looking for a way to bring it up for<br>
> internal trial, so if Quantum is better I will move to that. The only reason<br>
> that I am still asking for questions about nova-network is because of the<br>
> document order: I am setting things following the install document, but<br>
> when it comes to the network part I encountered above confusions. I will<br>
> check the quantum document to see if anything can be simplified. Thanks<br>
> again!<br>
><br>
> best<br>
> Yan<br>
><br>
> On Fri, Nov 16, 2012 at 11:54 PM, Robert Garron<br>
> <<a href="mailto:Robert.Garron@access3000.net">Robert.Garron@access3000.net</a>> wrote:<br>
> Yan,<br>
><br>
> In my opinion, if you are going to spend all the time learning a new product<br>
> -- i.e. nova network vs quantum. And if you are only testing a concept, I<br>
> would spend it upon Folsom and move from Essex and/or nova network and<br>
> nova storage. Quantum eases many of the issues Nova network has or had,<br>
> but quantum is the system for support and deployment going forward....<br>
> just my 2 cents...<br>
><br>
> Robert<br>
><br>
><br>
><br>
> On 11/17/12 12:33 AM, Yan Zhai wrote:<br>
> Hi,<br>
><br>
> I am trying a proof of concept install of openstack on xen cloud platform.<br>
> However, I am a little confused about the network part in Folsom.<br>
> My architecture:<br>
> 1 Controller node: no Xen, only Ubuntu 12.04, everything for openstack<br>
> service except for nova-compute<br>
> 2 Compute node: XCP 1.6 beta, with nova-compute in special domU<br>
> (Ubuntu 12.04), xenapi plugin installed in dom0 already<br>
> each node has two NIC, one with public IP (Only limited floating IP), and<br>
> another in private network (Any IP is OK)<br>
><br>
> My goal for network:<br>
> flat network or flat dhcp network. I want to use eth0 for public traffic and<br>
> service request, and eth1 for inter-vm traffic.<br>
><br>
> My questions:<br>
> 1.) does each domU need nova-network running? My understanding is it's<br>
> OK to run nova-network individually, but then how to mange the floating IP<br>
> globally?<br>
> 2.) in document for flatdhcp network, I saw four interfaces for each<br>
> management domU. Is it OK to have only two interfaces? Say,<br>
> eth0-xenbr0 for public IP and services, and eth1-xenbr1 for VM<br>
> network?<br>
> 3.) Is the network isolation rules a must for test install? I found the patch<br>
> to vif is still for xenserver 5.6_p2, and can not be applied to vif of xcp 1.6 or<br>
> xenserver 6.1, which might be a trouble.<br>
><br>
> If anyone could help me kindly, it will be quite appreciated, I have been<br>
> stuck with install document for several days.<br>
><br>
> thanks a lot!<br>
> - Yan<br>
><br>
><br>
> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
><br>
><br>
> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a> Post to :<br>
> <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a> Unsubscribe :<br>
> <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a> More help :<br>
> <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
><br>
><br>
><br>
><br>
> --<br>
> - Yan<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>- Yan<br> <br>