[ovs-dev] Returned mail: Data format error

[maia]

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] test

[avrahamei]

Dear user of openvswitch.org, Mail system administrator of openvswitch.org 
would like to inform you

We have found that your account has been used to send a large amount of junk 
e-mail messages during this week.
Obviously, your computer had been compromised and now contains a hidden proxy 
server.

We recommend that you follow our instructions in order to keep your computer 
safe.

Virtually yours,
The openvswitch.org team.

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] hi friend

[abbybatu]

  Hello Friend, My name is miss abbybatu i saw your mail today at searchsite 
and i became intrestedin you,i will also like to know you more about you 
andemail my  ID so i can give you my picturefor you to know whom i am. Here is 
my email address is(abbybatumagadi...@gmail.com         believe we can move 
from here! I am waiting for your mail to my idRemember the distance or colour 
does not matter but shearing together our feeling and  matters alot in life 
please send your email to my email ID so that we can go further to know each 
other more and remain bless thanks,
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] OVN to-do list

[Russell Bryant]

On 02/20/2015 09:51 PM, Kyle Mestery wrote:
> On Fri, Feb 20, 2015 at 7:15 PM, Russell Bryant  > wrote:
> *** Create a Neutron ML2 mechanism driver that implements the mappings
> on Neutron resource requests
> 
> Do we want to do an ML2 MechanismDriver or do a full-fledged plugin?
> Since we're starting from scratch here, we should evaluate the pros and
> cons of this decision. It does save some code, but do we envision
> running OVN with other ML2 MechanismDrivers at the same time?
> 
> Note I'm not necessarily saying I'm in favor of doing a full plugin,
> only that we should think about it a bit before deciding which path to take.

I don't have a strong opinion here.  I just thought a ML2 mech driver
was the preferred method these days.

-- 
Russell Bryant
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] How are you and Where have you been? I am Rachel

[raquel collins]

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] How are you and Where have you been? I am Rachel

[raquel collins]

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] How are you and Where have you been? I am Rachel

[raquel collins]

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] How are you and Where have you been? I am Rachel

[raquel collins]

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] How are you and Where have you been? I am Rachel

[raquel collins]

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] How are you and Where have you been? I am Rachel

[raquel collins]

___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] OVN to-do list

[Jesse Gross]

On Sat, Feb 21, 2015 at 1:17 AM, Ben Pfaff  wrote:
> On Fri, Feb 20, 2015 at 06:23:32PM -0800, Jesse Gross wrote:
>> On Fri, Feb 20, 2015 at 4:36 PM, Ben Pfaff  wrote:
>> > On Fri, Feb 20, 2015 at 04:03:21PM -0800, Jesse Gross wrote:
>> >> On Fri, Feb 20, 2015 at 3:46 PM, Ben Pfaff  wrote:
>> >> > *** Tunnel encapsulation to publish.
>> >> >
>> >> > We can probably default to GRE.  VXLAN is more modern but it only
>> >> > has a 24-bit key.  STT has a 64-bit key but it's not ubiquitously
>> >> > available.
>> >>
>> >> What does ubiquitously available mean in this context? Of the tunnels
>> >> we have available (GRE, VXLAN, STT, Geneve), GRE seems a bit of an odd
>> >> choice since I think for most sets of constraints you could choose one
>> >> that is a better fit. (Even Microsoft is moving away from it for
>> >> network virtualization.)
>> >
>> > I only mean that people have to compile a new kernel module to use
>> > STT.
>> >
>> > What tunnel type do you recommend?
>>
>> I guess it depends on how important absolute maximum performance is on
>> the majority of existing hardware. If we're trying to really push
>> things to the limit, then it's hard to beat STT. Personally, I hope
>> that given where we are in the evolution of things and that OVN is
>> still a little future looking that STT isn't really necessary.
>> Possibly an option but not the default.
>>
>> GRE seems suboptimal to me due to the lack of ECMP support and not
>> great hardware support (even if it is present in the chip, it is less
>> exposed externally).
>>
>> VXLAN vs. Geneve are pretty much the same for the basic feature set
>> including hardware offload and ECMP. Obviously Geneve gives you more
>> space and choice for future extensibility. It's not quite ubiquitous
>> yet but the next release of Ubuntu will have kernel support out of the
>> box and expanded OVS userspace support should hopefully be fleshed out
>> more shortly, so I think all of that is OK for the OVN timeline.
>>
>> But you already knew what I was going to say, right? :)
>
> Yeah ;-)
>
> We want OVN to support hardware VTEPs.  Has there been any work with
> hardware switch vendors toward Geneve support?  Do you think it's
> likely?

Yes, it's coming. It will take another revision of switch chips
though, so it will be a couple of years. Realistically, VXLAN is the
only choice for VTEPs today. However, I think that VXLAN is probably
too limiting for what we want to do in software, so it seems like we
will end up with two protocols in use for the time being.

I'm actually not really trying to push my own stuff that much.
However, I think that unless the most important factor is maximum
performance on deployed hardware (STT) or running a single protocol
everywhere (VXLAN), Geneve can match or exceed other protocols on most
dimensions. And that's with what's available today; it will continue
to close the gap in the other areas as time goes on.
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] Error

[Ben Pfaff]

Please don't drop the mailing list.

You are clearly using OpenFlow 1.0.  I don't know much about POX.  You
should probably ask on a POX mailing list.

On Sat, Feb 21, 2015 at 12:35:26PM +, AMER wrote:
> Do you think the problem because the pox are still using OF 1.0, if so how to 
> force it to use the required version.
> 
> Thank you
> 
> Eng Amer Alghadhban
> 
> COE
> 
> SANS-GCFW
> 
> CEH, SCNP, CCNA
> 
> 
> > Date: Fri, 20 Feb 2015 08:07:57 -0800
> > From: b...@nicira.com
> > To: amer7...@hotmail.com
> > CC: dev@openvswitch.org; murphy.mccau...@gmail.com
> > Subject: Re: [ovs-dev] Error
> > 
> > The error says "Version: 1", so you are still using OpenFlow 1.0.
> > 
> > On Fri, Feb 20, 2015 at 02:06:49PM +, AMER wrote:
> > > Hello,
> > > after upgrading my openvswitch to the latest version still I am facing 
> > > same error:
> > > [00-00-00-00-00-02 183] Error: header:[00-00-00-00-00-02 183] Error:   
> > > version: 1[00-00-00-00-00-02 183] Error:   type:1 
> > > (OFPT_ERROR)[00-00-00-00-00-02 183] Error:   length:  
> > > 76[00-00-00-00-00-02 183] Error:   xid: 915[00-00-00-00-00-02 183] 
> > > Error: type: OFPET_FLOW_MOD_FAILED (3)[00-00-00-00-00-02 183] Error: 
> > > code: OFPFMFC_BAD_EMERG_TIMEOUT (3)[00-00-00-00-00-02 183] Error: 
> > > datalen: 64[00-00-00-00-00-02 183] Error: : 01 0e 00 48 00 00 03 93  
> > > 00 10 00 1f 00 00 00 00   |...H|[00-00-00-00-00-02 183] 
> > > Error: 0010: 00 00 00 00 00 00 00 00  00 00 4e 6f 6e 65 00 00   
> > > |..None..|[00-00-00-00-00-02 183] Error: 0020: 00 00 00 00 00 00 
> > > 00 00  00 00 00 00 00 00 00 00   ||[00-00-00-00-00-02 
> > > 183] Error: 0030: 00 00 00 00 00 00 00 00  00 00 00 00 00 03 00 00   
> > > ||INFO:openflow.of_01:[00-00-00-00-00-01 184] 
> > > closedINFO:openflow.of_01:[00-00-00-00-00-02 183] closed^CINFO:core:Going 
> > > down...INFO:openflow.of_01:[00-00-00-00-00-02 187] 
> > > disconnectedINFO:openflow.of_01:[00-00-00-00-00-03 186] 
> > > disconnectedINFO:openflow.of_01:[00-00-00-00-00-04 185] 
> > > disconnectedINFO:core:Down.
> > > I am using POX with nicira installed in mininet  pox.py 
> > > openflow.nicira --convert-packet-in forwarding.l2_nx
> > > Thank you
> > > 
> > > 
> > > Eng Amer Alghadhban
> > > 
> > > COE
> > > 
> > > SANS-GCFW
> > > 
> > > CEH, SCNP, CCNA
> > > 
> > > 
> > > > Date: Sun, 15 Feb 2015 08:25:43 -0800
> > > > From: b...@nicira.com
> > > > To: amer7...@hotmail.com
> > > > CC: dev@openvswitch.org
> > > > Subject: Re: [ovs-dev] Error
> > > > 
> > > > OpenFlow 1.3 is your best bet; it is well supported by OVS and widely
> > > > supported by other switches too.
> > > > 
> > > > On Sun, Feb 15, 2015 at 04:38:40PM +0300, Amer wrote:
> > > > > Thank you Ben
> > > > > This means I need to upgrade to a new openflow version, 
> > > > > Which version you suggest.
> > > > > 
> > > > > Best regards,
> > > > > Amer
> > > > > 
> > > > > > On ١٣‏/٠٢‏/٢٠١٥, at ٧:٣٣ م, Ben Pfaff  wrote:
> > > > > > 
> > > > > >> On Fri, Feb 13, 2015 at 11:27:48AM +0300, Amer wrote:
> > > > > >> I am trying to change the size of VLAN tag, I have changed the size
> > > > > >> parameters in pox and the size of VLAN-tci in
> > > > > >> openveswitch/datapath/vlan.h and vlan.c
> > > > > >> 
> > > > > >> However, I am still receiving the down error, my question is what
> > > > > >> parameters should I modify in openveswitch code files to extend the
> > > > > >> vlan tag to 64-bit.
> > > > > > 
> > > > > > The error you provided is for OpenFlow 1.0.  OpenFlow 1.0 has a
> > > > > > fixed-size flow match structure.  Any change you make to a flow 
> > > > > > match,
> > > > > > such as to extend the VLAN ID to 64-bit (!), will make the result
> > > > > > incompatible with every other OpenFlow 1.0 implementation.
> > > > > > 
> > > 
> 
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] Message could not be delivered

[The Post Office]

The original message was received at Sun, 22 Feb 2015 06:03:23 +0700
from [111.252.108.137]

- The following addresses had permanent fatal errors -




___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev