openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #24885
Re: [OpenStack] OpenStack XCP with Quantum
Hi Mate, Chandler,
i have the same problem, and now my biggest question is (where i cannot google or baidu a answer)
whether i should make port like "ovs-vsctl add-port br-int tapxxxx tag=3" manually on dom0(XCP host,compute node),
or install a openvswitch agent on dom1(control node,vm) then the openvswitch agent remote add this port on dom0,
for a new vm that run on dom0.
the xcp + openstack + quantum + openvswitch make me confused.
the following figure is our topology use kvm, do you have xcp map?
yuan
From: Mate Lakat
Date: 2013-07-03 17:19
To: Chandler Li
CC: OpenStack
Subject: Re: [Openstack] [OpenStack] OpenStack XCP with Quantum
Hi Chandler,
XenServer quantum-ovs patches did not make grizzly unfortunately. Trunk
should be fine, although remember, that it is a fast moving target.
See https://wiki.openstack.org/wiki/QuantumDevstackOvsXcp
Mate
On Wed, Jul 03, 2013 at 01:33:10PM +0800, Chandler Li wrote:
> Hi,
>
> I am trying to use OpenStack grizzly to control XCP hypervisor, and trying
> to use quantum ovs plugin to implement network function. But the official
> document makes me confused. (
> http://docs.openstack.org/grizzly/openstack-compute/install/apt/content/introduction-to-xen.html#xen-config-reference).
> Does that means XCP + OpenStack only can use nova-network? Is there any
> document can briefly describe how OpenStack + XCP with Quantum and manual
> installation guide?
>
> Thanks,
> Chandler Li
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
--
Mate Lakat
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Follow ups
References