Re: [ovs-dev] reg: OpenVswitch Fields Implementation

2016-12-21 Thread Ben Pfaff
I'm trying to understand you here.  You're saying that you added some
code to Open vSwitch.  It didn't work.  Now, you're asking what's wrong
with it.  How can we know?  We didn't write the code.

On Wed, Dec 21, 2016 at 10:54:17PM +0530, Satyavalli Rama wrote:
>  
>   Could you please let us know, because of which this type of issues can come 
> or we missing anything.
> 
> Thanks
> Satya Valli
> 
>  -Ben Pfaff <b...@ovn.org> wrote: -
> 
>  ===
>  To: Satyavalli Rama <satyavalli.r...@tcs.com>
>  From: Ben Pfaff <b...@ovn.org>
>  Date: 12/21/2016 10:44PM 
>  Cc: ovs-dev@openvswitch.org
>  Subject: Re: [ovs-dev] reg: OpenVswitch Fields Implementation
>  ===
>Why are you telling us this?
> 
> On Wed, Dec 21, 2016 at 10:38:08PM +0530, Satyavalli Rama wrote:
> >  Hi Ben,
> > 
> > Currently we are implementing OXS as an independent infrastructure.  
> > While sending OXS Flow Stat Request,  we are facing the below issue.
> > We have dumped and verified the packet is in proper format only, but we are 
> > not receiving the Reply.
> > 
> > 2016-12-21T06:46:56Z|00016|vconn|DBG|unix:/usr/local/var/run/openvswitch/br0.mgmt:
> >  sent (Success): OFPST_OXS_FLOW request (OF1.5) (xid=0x2): 
> > 2016-12-21T06:46:56Z|00017|poll_loop|DBG|wakeup due to 0-ms timeout
> > 2016-12-21T06:47:55Z|00018|poll_loop|DBG|wakeup due to [POLLIN] on fd 4 
> > (<->/usr/local/var/run/openvswitch/br0.mgmt) at lib/stream-fd.c:155
> > 2016-12-21T06:47:55Z|00019|vconn|DBG|unix:/usr/local/var/run/openvswitch/br0.mgmt:
> >  received: OFPT_ECHO_REQUEST (OF1.5) (xid=0x0): 0 bytes of payload
> > 2016-12-21T06:47:55Z|00020|ofctl|DBG|received reply with xid  != 
> > expected 0200
> > 2016-12-21T06:48:55Z|00021|poll_loop|DBG|wakeup due to [POLLIN][POLLHUP] on 
> > fd 4 (<->/usr/local/var/run/openvswitch/br0.mgmt) at lib/stream-fd.c:155
> > ovs-ofctl: OpenFlow packet receive failed (End of file)
> > 
> > Thanks and Regards
> > Satya Valli
> >   
> > 
> >  -Ben Pfaff <b...@ovn.org> wrote: -
> > 
> >  ===
> >  To: Satyavalli Rama <satyavalli.r...@tcs.com>
> >  From: Ben Pfaff <b...@ovn.org>
> >  Date: 12/16/2016 10:23PM 
> >  Cc: ovs-dev@openvswitch.org
> >  Subject: Re: [ovs-dev] reg: OpenVswitch Fields Implementation
> >  ===
> >On Fri, Dec 16, 2016 at 03:33:11PM +0530, Satyavalli Rama wrote:
> > > We are working on Openflow 15 EXT-334 i.e OpenFlow Extensible Flow Entry 
> > > Statistics,  as per OpenvSwitch fields implementation in the meta-flow.h, 
> > > the key-value pairs for "OXS fields" to be added/declared separately or 
> > > do 
> > > we need to follow the existing NXM/OXM  key-value pairs.
> > > 
> > > Please clarify us, and please refer us some guidelines that we need to 
> > > follow for implementing this Openvswitch fields.
> > 
> > I don't think that OXS defines fields at all, so I'd expect their
> > implementation to be independent of existing infrastructure.
> > 
> > =-=-=
> > Notice: The information contained in this e-mail
> > message and/or attachments to it may contain 
> > confidential or privileged information. If you are 
> > not the intended recipient, any dissemination, use, 
> > review, distribution, printing or copying of the 
> > information contained in this e-mail message 
> > and/or attachments to it are strictly prohibited. If 
> > you have received this communication in error, 
> > please notify us by reply e-mail or telephone and 
> > immediately and permanently delete the message 
> > and any attachments. Thank you
> > 
> > 
> > 
> 
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev


Re: [ovs-dev] reg: OpenVswitch Fields Implementation

2016-12-21 Thread Ben Pfaff
Why are you telling us this?

On Wed, Dec 21, 2016 at 10:38:08PM +0530, Satyavalli Rama wrote:
>  Hi Ben,
> 
> Currently we are implementing OXS as an independent infrastructure.  
> While sending OXS Flow Stat Request,  we are facing the below issue.
> We have dumped and verified the packet is in proper format only, but we are 
> not receiving the Reply.
> 
> 2016-12-21T06:46:56Z|00016|vconn|DBG|unix:/usr/local/var/run/openvswitch/br0.mgmt:
>  sent (Success): OFPST_OXS_FLOW request (OF1.5) (xid=0x2): 
> 2016-12-21T06:46:56Z|00017|poll_loop|DBG|wakeup due to 0-ms timeout
> 2016-12-21T06:47:55Z|00018|poll_loop|DBG|wakeup due to [POLLIN] on fd 4 
> (<->/usr/local/var/run/openvswitch/br0.mgmt) at lib/stream-fd.c:155
> 2016-12-21T06:47:55Z|00019|vconn|DBG|unix:/usr/local/var/run/openvswitch/br0.mgmt:
>  received: OFPT_ECHO_REQUEST (OF1.5) (xid=0x0): 0 bytes of payload
> 2016-12-21T06:47:55Z|00020|ofctl|DBG|received reply with xid  != 
> expected 0200
> 2016-12-21T06:48:55Z|00021|poll_loop|DBG|wakeup due to [POLLIN][POLLHUP] on 
> fd 4 (<->/usr/local/var/run/openvswitch/br0.mgmt) at lib/stream-fd.c:155
> ovs-ofctl: OpenFlow packet receive failed (End of file)
> 
> Thanks and Regards
> Satya Valli
>   
> 
>  -Ben Pfaff <b...@ovn.org> wrote: -
> 
>  ===
>  To: Satyavalli Rama <satyavalli.r...@tcs.com>
>  From: Ben Pfaff <b...@ovn.org>
>  Date: 12/16/2016 10:23PM 
>  Cc: ovs-dev@openvswitch.org
>  Subject: Re: [ovs-dev] reg: OpenVswitch Fields Implementation
>  ===
>On Fri, Dec 16, 2016 at 03:33:11PM +0530, Satyavalli Rama wrote:
> > We are working on Openflow 15 EXT-334 i.e OpenFlow Extensible Flow Entry 
> > Statistics,  as per OpenvSwitch fields implementation in the meta-flow.h, 
> > the key-value pairs for "OXS fields" to be added/declared separately or do 
> > we need to follow the existing NXM/OXM  key-value pairs.
> > 
> > Please clarify us, and please refer us some guidelines that we need to 
> > follow for implementing this Openvswitch fields.
> 
> I don't think that OXS defines fields at all, so I'd expect their
> implementation to be independent of existing infrastructure.
> 
> =-=-=
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain 
> confidential or privileged information. If you are 
> not the intended recipient, any dissemination, use, 
> review, distribution, printing or copying of the 
> information contained in this e-mail message 
> and/or attachments to it are strictly prohibited. If 
> you have received this communication in error, 
> please notify us by reply e-mail or telephone and 
> immediately and permanently delete the message 
> and any attachments. Thank you
> 
> 
> 
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev


Re: [ovs-dev] reg: OpenVswitch Fields Implementation

2016-12-21 Thread Satyavalli Rama
 Hi Ben,

Currently we are implementing OXS as an independent infrastructure.  
While sending OXS Flow Stat Request,  we are facing the below issue.
We have dumped and verified the packet is in proper format only, but we are not 
receiving the Reply.

2016-12-21T06:46:56Z|00016|vconn|DBG|unix:/usr/local/var/run/openvswitch/br0.mgmt:
 sent (Success): OFPST_OXS_FLOW request (OF1.5) (xid=0x2): 
2016-12-21T06:46:56Z|00017|poll_loop|DBG|wakeup due to 0-ms timeout
2016-12-21T06:47:55Z|00018|poll_loop|DBG|wakeup due to [POLLIN] on fd 4 
(<->/usr/local/var/run/openvswitch/br0.mgmt) at lib/stream-fd.c:155
2016-12-21T06:47:55Z|00019|vconn|DBG|unix:/usr/local/var/run/openvswitch/br0.mgmt:
 received: OFPT_ECHO_REQUEST (OF1.5) (xid=0x0): 0 bytes of payload
2016-12-21T06:47:55Z|00020|ofctl|DBG|received reply with xid  != 
expected 0200
2016-12-21T06:48:55Z|00021|poll_loop|DBG|wakeup due to [POLLIN][POLLHUP] on fd 
4 (<->/usr/local/var/run/openvswitch/br0.mgmt) at lib/stream-fd.c:155
ovs-ofctl: OpenFlow packet receive failed (End of file)

Thanks and Regards
Satya Valli
  

 -Ben Pfaff <b...@ovn.org> wrote: -

 ===
 To: Satyavalli Rama <satyavalli.r...@tcs.com>
 From: Ben Pfaff <b...@ovn.org>
 Date: 12/16/2016 10:23PM 
 Cc: ovs-dev@openvswitch.org
 Subject: Re: [ovs-dev] reg: OpenVswitch Fields Implementation
 ===
   On Fri, Dec 16, 2016 at 03:33:11PM +0530, Satyavalli Rama wrote:
> We are working on Openflow 15 EXT-334 i.e OpenFlow Extensible Flow Entry 
> Statistics,  as per OpenvSwitch fields implementation in the meta-flow.h, 
> the key-value pairs for "OXS fields" to be added/declared separately or do 
> we need to follow the existing NXM/OXM  key-value pairs.
> 
> Please clarify us, and please refer us some guidelines that we need to 
> follow for implementing this Openvswitch fields.

I don't think that OXS defines fields at all, so I'd expect their
implementation to be independent of existing infrastructure.

=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you



___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev


Re: [ovs-dev] reg: OpenVswitch Fields Implementation

2016-12-16 Thread Ben Pfaff
On Fri, Dec 16, 2016 at 03:33:11PM +0530, Satyavalli Rama wrote:
> We are working on Openflow 15 EXT-334 i.e OpenFlow Extensible Flow Entry 
> Statistics,  as per OpenvSwitch fields implementation in the meta-flow.h, 
> the key-value pairs for "OXS fields" to be added/declared separately or do 
> we need to follow the existing NXM/OXM  key-value pairs.
> 
> Please clarify us, and please refer us some guidelines that we need to 
> follow for implementing this Openvswitch fields.

I don't think that OXS defines fields at all, so I'd expect their
implementation to be independent of existing infrastructure.
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev


[ovs-dev] reg: OpenVswitch Fields Implementation

2016-12-16 Thread Satyavalli Rama
Hi Ben,

We are working on Openflow 15 EXT-334 i.e OpenFlow Extensible Flow Entry 
Statistics,  as per OpenvSwitch fields implementation in the meta-flow.h, 
the key-value pairs for "OXS fields" to be added/declared separately or do 
we need to follow the existing NXM/OXM  key-value pairs.

Please clarify us, and please refer us some guidelines that we need to 
follow for implementing this Openvswitch fields.

Thanks & Regards
Satya Valli
Tata Consultancy Services
Mailto: satyavalli.r...@tcs.com
Website: http://www.tcs.com

Experience certainty.   IT Services
Business Solutions
Consulting

=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you


___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev