Hi Ben/Team,
Thanks for the reply.
We are working on implementation of vacancy events and have developed the
module for same.
As suggested, we have made a separate test case for [ofproto -
asynchronous message control (OpenFlow 1.4)].
The commands (ovs-ofctl ofp-print
051F0018040
Hi,
we are unable to find the patch against the master branch.can you tell us
how to get it?
Thanks,
Neethi
On Thu, Dec 11, 2014 at 9:55 PM, Aman Kumar wrote:
>
> Thanks Flavio,
>
> Tomorrow i will test it and once it will over i will inform you.
>
> Thanks
> Aman Kumar
>
> On Thu, Dec 11, 20
In current recirculation implementation, the flow misses (with
'recirc_id' set) are always looked up on the receiving bridge's
internal flow table. However, the bond port may actually reside
on another bridge which gets connected to the receiving bridge
via patch port. Since the recirculation rul
Sorry, forgot to mention that this patch targets branch-2.3,
Haven't tried, but should also be applicable to master~
On Fri, Dec 12, 2014 at 1:55 AM, Alex Wang wrote:
>
> In current recirculation implementation, the flow misses (with
> 'recirc_id' set) are always looked up on the receiving bridg
On Fri, Dec 12, 2014 at 02:46:50PM +0530, Neethi Shashidhar wrote:
> Hi,
>
> we are unable to find the patch against the master branch.can you tell us
> how to get it?
I sent to the list with copies to everyone in the thread.
Here is the archive url:
http://openvswitch.org/pipermail/dev/2014-Dece
Hi,
we have cloned the master branch,but the patch doesn't seem to be a part of
it and it works same as earlier. can you please explain how do we get it
using the list that you have sent.
Thanks,
Neethi
On 12-Dec-2014 6:27 pm, "Flavio Leitner" wrote:
> On Fri, Dec 12, 2014 at 02:46:50PM +0530,
On Fri, Dec 12, 2014 at 08:25:48PM +0530, Neethi Shashidhar wrote:
> Hi,
>
> we have cloned the master branch,but the patch doesn't seem to be a part of
> it and it works same as earlier. can you please explain how do we get it
> using the list that you have sent.
You have to get the patches from
Currently, Controllers and CMSes that integrate with Open vSwitch
after following the IntegrationGuide.md, expect to start VMs after
the underlying network infrastructure is ready. I have been asked
a few times on how to handle the same with containers. This commit
provides documentation on one way
ovs-docker currently lets one add the ability to set the
IP address on an OVS interface. Ability to set the default
gateway too can be an useful addition. (orchestrators
who plan to use OVS interfaces can do this from a single
utility instead of multiple utilities)
Requested-by: Marvin Pascual
Si
For containers containing multiple ports and spawned by
orchestrators without openflow flows configured, it can be quite
useful to distinguish their traffic with vlans. This can be useful
when containers are spawned inside VMs instead of hypervisors.
Signed-off-by: Gurucharan Shetty
---
utilitie
Alex and I had an off-line discussion. He will post a simpler version
of the patch soon.
On Fri, Dec 12, 2014 at 1:53 AM, Alex Wang wrote:
> Sorry, forgot to mention that this patch targets branch-2.3,
>
> Haven't tried, but should also be applicable to master~
>
> On Fri, Dec 12, 2014 at 1:55 AM
In current recirculation implementation, the flow misses (with
'recirc_id' set) are always looked up on the receiving bridge's
internal flow table. However, the bond port may actually reside
on another bridge which gets connected to the receiving bridge
via patch port. Since the recirculation rul
In current recirculation implementation, the flow misses (with
'recirc_id' set) are always looked up on the receiving bridge's
internal flow table. However, the bond port may actually reside
on another bridge which gets connected to the receiving bridge
via patch port. Since the recirculation rul
The logic of the patch looks good to me. Thanks for fixing it.
The diff of the ofproto-dpif.h looks bigger than the actual change
(add an inline function). Do you know why?
Acked-by: Andy Zhou
On Fri, Dec 12, 2014 at 5:52 PM, Alex Wang wrote:
> In current recirculation implementation, the flow
Thx for the discussion and review,
On Fri, Dec 12, 2014 at 6:14 PM, Andy Zhou wrote:
>
> The logic of the patch looks good to me. Thanks for fixing it.
>
> The diff of the ofproto-dpif.h looks bigger than the actual change
> (add an inline function). Do you know why?
>
Sorry, i forgot to clea
> ahead of the inline function, Fixed it up and applied it to branch-2.3
Does this fix also apply to master?
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
Not quite, but there is no logic conflict,
I fixed it up and applied to master,
Thanks,
Alex Wang,
On Fri, Dec 12, 2014 at 9:17 PM, Andy Zhou wrote:
>
> > ahead of the inline function, Fixed it up and applied it to branch-2.3
>
> Does this fix also apply to master?
>
__
Thanks!
On Fri, Dec 12, 2014 at 9:44 PM, Alex Wang wrote:
> Not quite, but there is no logic conflict,
>
> I fixed it up and applied to master,
>
> Thanks,
> Alex Wang,
>
> On Fri, Dec 12, 2014 at 9:17 PM, Andy Zhou wrote:
>>
>> > ahead of the inline function, Fixed it up and applied it to bran
18 matches
Mail list logo
