On 11/17/2016 03:14 AM, zhi wrote:
Hi, all
I build a devstack which code from master branch. By default the OVS version is
2.0.2 when install devstack. So I reinstall the OVS 2.6.0.
I meet an exception in OVS agent when all OVS services runs okay. Exception
shows below:
2016-11-17 15:47:29.175
Thanks Mathieu for your reply and info.
On Tue, Mar 18, 2014 at 3:35 AM, Mathieu Rohon wrote:
> Hi nader,
>
> The easiest way would be to register a new RPC callback in the current
> ovs agent. This is what we have done for the l2-pop MD, with fdb_add
> and fdb_remove callbacks.
> However, it co
Hi nader,
The easiest way would be to register a new RPC callback in the current
ovs agent. This is what we have done for the l2-pop MD, with fdb_add
and fdb_remove callbacks.
However, it could become a mess if every MD adds it own callback
directly into the code of the agent. L2 agent should be a
Hi Kyle,
This observation is with OVS Plugin.
Regards,
Balaji.P
> -Original Message-
> From: Kyle Mestery (kmestery) [mailto:kmest...@cisco.com]
> Sent: Friday, October 11, 2013 4:14 PM
> To: OpenStack Development Mailing List
> Subject: Re: [openstack-dev] [Neutron] OVS
On Oct 8, 2013, at 4:01 AM, P Balaji-B37839 wrote:
> Hi,
>
> Current OVS Agent is creating tunnel with dst_port as the port configured in
> INI file on Compute Node. If all the compute nodes on VXLAN network are
> configured for DEFAULT port it is fine.
>
> When any of the Compute Nodes are co
Original Message-
>> From: Mathieu Rohon [mailto:mathieu.ro...@gmail.com]
>> Sent: Thursday, October 10, 2013 6:43 PM
>> To: OpenStack Development Mailing List
>> Subject: Re: [openstack-dev] [Neutron] OVS Agent and VxLan UDP Ports
>>
>> hi,
>>
&
Hi Rohon,
Thanks for confirmation.
We will file a bug on this.
Regards,
Balaji.P
> -Original Message-
> From: Mathieu Rohon [mailto:mathieu.ro...@gmail.com]
> Sent: Thursday, October 10, 2013 6:43 PM
> To: OpenStack Development Mailing List
> Subject: Re:
hi,
good point Balaji, the dst_port is the port on which ovs is listening
for vxlan packets, but I don't know what is the option in ovs-vsctl to
set the remote port of the vxlan unicast tunnel interface.
But it looks like a bug since you're right, tunnel_sync and
tunnel_update RPC messages should
Any comments on the below from community using OVS will be helpful.
Regards,
Balaji.P
> -Original Message-
> From: P Balaji-B37839
> Sent: Tuesday, October 08, 2013 2:31 PM
> To: OpenStack Development Mailing List; Addepalli Srini-B22160
> Subject: [openstack-dev] [Neutron] OVS Agent and
Subject: Re: [openstack-dev] [Neutron] OVS Agent and OF bridges
On Aug 2, 2013, at 7:02 AM, Addepalli Srini-B22160 wrote:
>
> Hi,
>
> As I understand, current OVS Quantum agent is assuming that there are two
> Openflow bridges (br-int and br-tun).
>
> "br_tun", I th
On Aug 2, 2013, at 7:02 AM, Addepalli Srini-B22160 wrote:
>
> Hi,
>
> As I understand, current OVS Quantum agent is assuming that there are two
> Openflow bridges (br-int and br-tun).
>
> “br_tun”, I think, is introduced to take care of overlay tunnels.
>
> With flow based tunnel selectio
11 matches
Mail list logo
