have even more trouble setting up quantum itself. The plugin support in XCP looks not as good as KVM: the first problem is python 2.6 and it's solved by adding new repository. But when I installed the openvswitch agent, it can not start, requiring some quantum python module, which then seems have dependency on libudev. And this means I have to update almost the whole dom0, including libc, udev, and blablabla to get that library. That's too risky. Maybe I shall stay with bridge plugin and see if things can be a little better...
On Sat, Nov 17, 2012 at 1:18 PM, Afef MDHAFFAR <afef.mdhaf...@gmail.com>wrote: > Hi all, > > I am also trying to install openstack, with xcp. > I used devstack to do that, since it is more simple. > However, I am still facing a network problem. > Actually, I got a private network per physical node. I am able to access > the tenant VMs from the corresponding openstack DomU. But, these tenant VMs > are not inaccessible from any other machines. > Is that normal (ie. a private network per physical node? The created > tenant VMs can access external machines, but they are invisible to other > machines? > Is there any way to let my VMs accessible, at least from other tenant VMs > (created on other physical nodes)? > How can Quantum solve this problem? > > Thank you > > Regards, > Afef > > > 2012/11/17 Yan Zhai <zhaiyan...@gmail.com> > >> Hi Robert, >> >> thanks for reply. Currently I am just looking for a way to bring it up >> for internal trial, so if Quantum is better I will move to that. The only >> reason that I am still asking for questions about nova-network is because >> of the document order: I am setting things following the install document, >> but when it comes to the network part I encountered above confusions. I >> will check the quantum document to see if anything can be simplified. >> Thanks again! >> >> best >> Yan >> >> >> On Fri, Nov 16, 2012 at 11:54 PM, Robert Garron < >> robert.gar...@access3000.net> wrote: >> >>> Yan, >>> >>> In my opinion, if you are going to spend all the time learning a new >>> product -- i.e. nova network vs quantum. And if you are only testing a >>> concept, I would spend it upon Folsom and move from Essex and/or nova >>> network and nova storage. Quantum eases many of the issues Nova network >>> has or had, but quantum is the system for support and deployment going >>> forward.... just my 2 cents... >>> >>> Robert >>> >>> >>> >>> >>> On 11/17/12 12:33 AM, Yan Zhai wrote: >>> >>> Hi, >>> >>> I am trying a proof of concept install of openstack on xen cloud >>> platform. However, I am a little confused about the network part in Folsom. >>> My architecture: >>> 1 Controller node: no Xen, only Ubuntu 12.04, everything for >>> openstack service except for nova-compute >>> 2 Compute node: XCP 1.6 beta, with nova-compute in special domU >>> (Ubuntu 12.04), xenapi plugin installed in dom0 already >>> each node has two NIC, one with public IP (Only limited floating >>> IP), and another in private network (Any IP is OK) >>> >>> My goal for network: >>> flat network or flat dhcp network. I want to use eth0 for public >>> traffic and service request, and eth1 for inter-vm traffic. >>> >>> My questions: >>> 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? >>> 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? >>> 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. >>> >>> If anyone could help me kindly, it will be quite appreciated, I >>> have been stuck with install document for several days. >>> >>> thanks a lot! >>> - Yan >>> >>> >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~openstack >>> Post to : openstack@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~openstack >>> More help : https://help.launchpad.net/ListHelp >>> >>> >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~openstack >>> Post to : openstack@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~openstack >>> More help : https://help.launchpad.net/ListHelp >>> >>> >> >> >> -- >> - Yan >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> >> > > > > -- - Yan
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
