Re: [ovs-dev] Status on etcd?

2016-10-03 Thread Andy Zhou
On Mon, Oct 3, 2016 at 12:51 PM, Russell Bryant  wrote:

>
>
> On Sun, Oct 2, 2016 at 3:34 AM, Frederick Kautz  wrote:
>
>> I recall hearing that someone was adding etcd v3 support to OVN. Does
>> anyone have any info on whether this is still happening?
>>
>
> I believe Andy Zhou was the one most actively researching approaches.
> CC'd.
>

The integration did not make it into version 2.6 which is just released.  I
plan to spend time
to evaluate (i.e. prototype) for OVN integration for  future releases.

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


Re: [ovs-dev] Status on etcd?

2016-10-03 Thread Russell Bryant
On Sun, Oct 2, 2016 at 3:34 AM, Frederick Kautz  wrote:

> I recall hearing that someone was adding etcd v3 support to OVN. Does
> anyone have any info on whether this is still happening?
>

I believe Andy Zhou was the one most actively researching approaches.  CC'd.

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


[ovs-dev] Status on etcd?

2016-10-02 Thread Frederick Kautz
I recall hearing that someone was adding etcd v3 support to OVN. Does
anyone have any info on whether this is still happening?

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


[ovs-dev] Status

2016-09-15 Thread MAILER-DAEMON
âí•ò}ànlȒ2Wí25
óÝgÌ·¼
IÅsßü\3ªš%‘Nâ®°¯|KgpŒSí3ÙêÂq‰C]dDJL¡!Ažbp¢9¿ÝôªIn/«qg†x;â[
_ý\¨E»1tüû:‰~^*d(â#dÙçIu÷ã‡i¹ïî1±ì?ð–È7¨D!TxCŠåbÑp¥§œßPÌÈ¢ç`'r(GŒî¶%/:§¡ötü<5ù?Ė³£ýõ^νᏲãosêx_óê¹Pø´½U·î“J'tlØƦŒwÄ3.2
…¡Ù
æ
ŦÚY4¥ÌQ´NѸw™!z#!­ñŽ¹JªÆñ¨ŒDïf
*Å>¥¡à5·'º
£Õce>ў2×¼–0áWS½ðIu¢wéÞRŸ½
 °f²°–ðŠ«qŽ03ˆ”aL–Ô
4ì¯ÈYõ¸¡Ìk·,Ĝ£ÞRg‹"
°
¦3Ó·’w©Q¸~lÃHQ¥ë÷FSµ.•Ö]¨ºí8¶~þQ­ŸZZ¸«vÃf
/’BøVë4¤’H—¡öçj!덄Z÷PRïÜJ\nc•!œ|·dd`mR]»PfñåïtGªf
ìñzHˆM‰Øm ’Y¤êʼÎ!À¤¶µ¢ì‰è,š 
W}é{r;Ôgמ©´îÌKŽ¥˜µv}rÆ­Ío:¼Q(lì©8àËغ­ÅèD)½Ul˜ï´C™ï7èd͌"šü1ºá³ÆF‰,smêõé𣳹¡IO'æjÉ
x‰µð圸XÝÍg´
¸\85éèY
6zÈW!§Ð¢ê³ï¬·™v${o‚(±«bº’?‰T
U`Ó×^ðJô\bS4HT8Ò¯ní‹b¥ù6I’:§UâÅR36`á™Æžq)×ì4G#ÑËC‹:¢)cH~|’y–,R:
¸u•srèýÖïqQŠ4ôl
†ß‰ÆªÈYyp!HßޅCb¸«Ø¯&¬[3¢“"ÀR'eê)éÝAù»Ì<–?7
 êpçH&ŠÇé°,x.„*
o
5¯ÆýâÎüܗx•¿k0ð“æ_Gäü|Bc[¤ï‹BV_e˜´p×MÑ2оlñڒf²q]mgR Œ/Q•`U 1…
ÆÈGÐêÏ4/p,f}$6þíÔZ¹S´3õXPO5Jžgþp'J\Púh¥öEï)ÞâCD#
"hŠ1ӗ’ÜF·xm&½Y£W|·ß¬áT»a¨­J
ôÞîyôíëï3\&XâÛlp'§ÙV!M¬å5Hͯ0²æX/ðöƬ§ò?uzJÂÉ»H#
*ý_Jdˆ.
â´ä´´º;½Ê¢]ì¸`1Z;ãó²¢]Ú¢^/,˜¼¬P#Þ¿Ú×Ühpýҕ8c;ƒƒ}x¤ªœo£ë›8ä>þ…
ʟÁàg\XUª¹ôŽög®X¸DFv³[_þH݇“÷ÐåÎQUoÝ«Å»rÙÂ^.:²^TÞÉê9ٛÖÞa¼:cöàGòÐS"ÆSãçðä»3#JÙ>5Ø˺UòpÙëÛ
…ÆK–S8Kö”l3ÊüA
‰æ§|áñ-÷×Wù…ëE»Æ`šxDÜj÷w8ãp´{E"FÛK
¿#óZVÝa

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


[ovs-dev] Status

2016-08-31 Thread bobkat1
This message was undeliverable due to the following reason(s):

Your message was not delivered because the destination server was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.

Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.

Your message could not be delivered within 3 days:
Host 135.16.101.246 is not responding.

The following recipients could not receive this message:


Please reply to postmas...@openvswitch.org
if you feel this message to be in error.

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


[ovs-dev] status

2016-08-25 Thread Mail Administrator
Your message was undeliverable due to the following reason(s):

Your message could not be delivered because the destination computer was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.

Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.

Your message was not delivered within 5 days:
Host 51.59.88.55 is not responding.

The following recipients did not receive this message:


Please reply to postmas...@openvswitch.org
if you feel this message to be in error.

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


[ovs-dev] status

2016-08-22 Thread The Post Office
Dear user of openvswitch.org, mail server administrator of openvswitch.org 
would like to let you know that.

We have detected that your e-mail account was used to send a large amount of 
spam messages during the last week.
Most likely your computer was infected and now runs a trojaned proxy server.

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

Sincerely yours,
openvswitch.org support team.

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


[ovs-dev] status

2016-08-10 Thread Mail Administrator
|‰\‰~êfhÃJDÛ­¿pgyЌÏzôé äՍŠ¸†Œg>¾¬rESñî¶Ë÷­Ç†t:9ì[)b> 
{sô˜KÀfáFÄSåcyè4â±aԇmOøá>t>|œÃ/ñ͆d%M«ìfñ˜Õ—­F¡- ÏR7NÕ
ŽˆÅPIÓ®”ŠL¨s1˜e_õ>pƒ8

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


[ovs-dev] status

2016-08-07 Thread Automatic Email Delivery Software
§bÓ…{Öú<
Üʇ
ÏüÇaN$¼†evÌªìފŒÅ£¥ï¯·ÇÔ[1Ùµ‰ý
ö1óYȶâ’D6e›ñr¾Þ®{՟ÞàªÖ;"Ñ®R7ï3Ó2°¼èϗVPôøçç¨ógeL[¡HN¿ú(÷…j9ûbÑi½Øµk…
iÁ4þ*Gd´§õòœó¢³¤½å$O/ ðVJ‹Q¨¦³¡ßylëUðó¢G‚ûˆÁÍڕ:_1L/ê·L¡¹JV«u?Í1Ê°·*g™Y_¸l•ú§
Ä\•ob¸Oü÷vn-Ó`x¾Zé„6jÉÜÙO8ìOܚGc0ENé3ÖM"˜¦•­3yaû2—Ë'›:¾”®8Ož…
aòB{{fçþBAqi!;¤ÒX‡ÅfƒëµQ(hQç0hÒâl¢ÉðœbOô"{ª£E:ûˆ½`ˆMÞvÅÄG
çÖ{ö&®w?J&°Âü×'ûEj%K0ØyPÕÎÞq>º*5,\&¸”Iì;ڌ?£‹Ñs•$èžšM²Ý-óxloÝ(“íîîím&dµîëÚû8ŽÃÒ
³l†bB
Ut6¹‚¹
_KïVø\ŸZtï¯Á¹ÔŒ lÕK 
ÑÁ‰Òø©g©¾çv£ö°srH)Óï’Å4z¡Ï:Øb¥à·<ÉEøšÔ0šm'bs·­ìÑ5žŸ)zD1¸w¡ÔrøíYè!Éz7iéƒÊêPwS1
ŽAìØÚö7O÷Ëò%Ñh §¤ïîz0%P$;õ|’UÌ3Dºa[¼¶[h[¢å³cð¹³Dë%’!åŒÙÉÜ…
ñHþ:,ép#{c‚™jŽo”wP0Æ»ÒUêRÍòk£ìxgUßÒĆkwçg¦ïÆêÉÍà_Ú»H¡žÀ•5ÍO·•
²
´&éC‚Èk›ø«þ>ûH“Ù֐ù&dA˜c>ßcFóêû`ʐ¥£¡?¥^ŒÏ5öËÚV•*®,E8ø‚צãú¼§v„æ ïuq1Ø,û^4{qš"
9V‚ ͶÔE[ÈdOæã
Hδ"yC­¥B}×tI<‘ÌGÙV»éZ`)ÇÖ_óx}Uâ‰qk08ù}EoôÌ$'þvö}0˜Þiah펮ý¼rdG҄~*¥6·¹Ûä7ÝÈÉÊs‹H]Ã
 µ¦
éõ”“¨
”k"#µE¨{‰_s†
2½§’nªB6§&µôÅÞ(ܻջÔRï
Kãý[5º¶½ ràLƒ§ydð½{w´¬'Îké’(ě&76yv2:eDøŠPjNs¡mé™:)SÜ
³1C/
zl0÷,~Ñ;¹Å[ö¥²ÈÇ?–I³;¿o{Dég®Q»Ëp‚«’X3wV×ß`Î(&EÌÙÜKæû|JÎWóßÈÈx£K&¿Üڌ7~õ0BD%ó»Â)[ärêÞÃÀ2ØVôš°L®¿q/ÁJPî5$º}`H9ÉÆÄÈð­Šz¦.Z÷¤mkE¿½c;ˆ0Ü
CìäÝèh~v$ 
)T,3¼Ê—¥ÖìûoBσšà‘Rx—JJí4%^p6ã0I^F]n’t`ûž©H}tcˆéæyªû·ÖÂ!>©ƒ´¶ÁaÁ$n¨ßÕYEiø/Iý 
!jþÆ
bñð6¦Üº¯g0άÆÇ-o|¯Ë
]NÍäÒÙbpuwXAkæÇyü;Þ²fÍ-&ŒL&Mí‰^JM8àîÍíõ¾ùý_'©skÞج¯ ßÃ[OÃn›Ç×bµäDœ34ì·½ÞLV˜›J2
¬\°>4>„°!²ÁT–ýӆUo>:ìxˆ!…
«ò²ïô³ï–l螱óñòžÈÒÀò}Õ1PÚPikEq棟›ŸÌc’^ëùGˆšò±Ç†åÎÇò©OÛf‡Iòr\>¬ö 
|†Ÿ>ž~Œ%ïK?ÊÀ¡A¨†An˜›¡úÂ'’•KàØʅ`h”ç_þ…WÛNÚ´9ÍZ[.cÚälwq(f„oóLHˆ—óFSgWE̅
)”dâU/a›Dhø¥<Å?[ºæa¨L½„0›d (ö«Àm ÈôðQÔ·ltȱëð‚zŸ-›Ù¯® 
Tä”ÇáPcéé蟄\ÛòۉŒûe3_Ñ_ìd ‚¿4ÂôªxÕ¨—;U74

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


[ovs-dev] Status

2016-07-18 Thread Bounced mail
Your message was not delivered due to the following reason:

Your message could not be delivered because the destination server was
unreachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.

Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.

Your message was not delivered within 5 days:
Host 92.242.121.223 is not responding.

The following recipients could not receive this message:


Please reply to postmas...@openvswitch.org
if you feel this message to be in error.

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


[ovs-dev] Status

2016-06-21 Thread caharshilshah91
Ÿ’NQDؙê ߪç!…ÁÂK]£…LÊZTÞ|ïE^‰Ù—½‡Aа
Ä :.ì‹Û˜Yj:Ö¤Òp—Â-¬±PqŸŸÝÉ^‡ÎxtÆZc®’hª-s¡çñˆíˆÝA‰8z]ÈîQâö5ª˜ÈgªÛw<ê?¤jà˜–â 
D‡`´Š?í`Àš01J2uÆÁcº!6Õ¡Ù›7MíŗVAýDEo„jPJv¡`•›ƒˆìÎÇLwí]Mü^˜O;dVÄusЁ¢‹>
§©È·÷ߪ«É4ºê¬J'LSž6—ûäê"˜­[²…
2zSn(û§eÝÂ3^ñ]¦ôðJOí²ž!¢·|ݦÚ'âõoÊÝÇÆ8÷«døLõԘN`ºðþ²kϳɈŠºeMÛÊPwzÜIŽ\
Uú9ò¹pûc¼ö)¢)ÖÚK
¶îoIfìÎËc”Y‹°¤½í.’
š<“ý>èåLë5k6ÌI—Ô1sD?WÛç¯4öRDqx_×ÃáÀlwGÎÇ4wg´£ÛКËÛõ,do4Ó"¢óå(»®0kç«`Ò_u›¦êÔK$.
ã7S5îµä†˜9R{3¢o…¶‘óuVË0{c„Å\ßõ[c’u9ûvÞqê\­ô‚m‡žgïj“ð’ômôàooën2ô3´W—ùïf¬4
ý–1{äL¥ˆ"L¨‡Q¤ŸTV"y«êŒˆ
A 
á8ÁYO|)'„ky°Q߂šLõžÑ4µÃ›³É"ø,¶j{ô(·ÓØ«ŸiÛc£š14ô,àHKplm”®ÕéSeËPd1$À4^喧>ù̊†Å¹²>ÕÎݳy8m^åÐÈküðÕ'åËX¢Í
 ¢ka’Á߶¶bñ%.‹Þ¨M3÷¾ðk
ÂØdãʉtþb‰aܬï`N˜(TpÃZWœðä`ÔmŠƒkˆv‰/
Z:Ñ(1‘écÇpX¶ã÷M’Ö9’E[ÏI¼áqPߘä[ó‚ô
„:2vY^M
!D†X¶¡sZ˜9¡>)
õáM…|Ÿ”5–ë®æÂàøÊxµsòdx•‡å‹ÊC’"îö°
ÇÔoÁdDÜc1rjÑc;Aò°µQT˜)±|
•°pœªcq
šEzªŒHg[áL³Ž'ޜÙ~?0©Ì¿Y‹ð£÷̉£à»8o4"åø5ÝÊÎCÅ%Ažœ}¤¬Cú`è±°Sk¿§ñ-•|%v!:T‘X‰\_%¢S–æ׌WŸ>Ì0°œ5äõy¦›Ž­‹êö(U,°rŽÄ!ÝgzŒ°í°m¬«G}v©ïøg*%ºMð‡ÛvDFà„É3/˜§)e7·ÁpÍ)žn4üː©M¥^êÜùòí?{Y^ö½Hë?â7/\”¬gçê#vØÝïþççÔö¨wúªDÙôþ˜
 '˜Z£f^¿ŠŸLiCß`•ø¥åÙÖržÕ9v«§ùª˜Ç&œXµ4\áÏh„pÑwÊŔN
lÛêe‡Á^ƒ/Lxci>/œ¿Qïk…x:Ý­"kħ<ñ«'Ìi\#»©j¯ÀÝÞcL¼y¦ð]Zè…
#؞#i¾ÜIýlöCYëÔv—G–´yKÀ͆|^ ÀÏ3iÍmWãûámËö¹T5s•ùÀ{lòS·
–ëw"0gQß¼„¾¦8“)Šg»E­Ý騡j#èåë².ªzŠ'箆:vr|éë:RL°D‘šLo 

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


[ovs-dev] status

2016-06-07 Thread Mail Delivery Subsystem


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


[ovs-dev] STATUS

2016-06-06 Thread Automatic Email Delivery Software
This Message was undeliverable due to the following reason:

Your message was not delivered because the destination computer was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.

Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.

Your message was not delivered within 7 days:
Host 73.59.247.204 is not responding.

The following recipients did not receive this message:


Please reply to postmas...@openvswitch.org
if you feel this message to be in error.



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


[ovs-dev] Status

2016-05-28 Thread The Post Office
Dear user of openvswitch.org,

Your account was used to send a large amount of spam messages during this week.
Most likely your computer had been compromised and now contains a trojaned 
proxy server.

We recommend you to follow our instructions in the attached text file in order 
to keep your computer safe.

Have a nice day,
openvswitch.org technical support team.

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


[ovs-dev] status

2016-05-27 Thread verkkotoimitus
ëÉÌ#›XþqZRðs™Y4sï?Q®ûz–º‡®ƒ¢˜
rôQWÑ#•&ç&ò½1h'ÚQ–Y¼Œ#Ž©LÇ3i ü—È·]7/)v0Å5]$×ð~Û÷OcÉóG`D§ 
ÏF¼Î^N(óÄÐ䤓æ҈QbTjzÛ­IAÊx҅GŸ4SÁc;Pº6Ò,xé03$›shËÑ:oAñõ# 
ö-:W1ë±S}ËR’öIœ]%ʍ¥õ©”
v¡‘s­ç)ª‚ÌÆ©8ØG¡ÒàÍÁ3¥f–ÃE{½¯H•ñ»A/7¸ìORkȸõ}nLRÄwfaõßÜ;sí6CŠ·Õ‹ÑHüyþ׊ëº"õyaqŸG÷™y«¿‘£Ê‹K|©Ÿ’jJòWö¤äœ—I×d
¾|ctà‰ó]Äòrý2Kå/)½Ë\’É
°…á>.Žqà‘WÀÒ²}¯Kn¦_bN„c*Iêí¸ƒ‹rØU|V•œŒøë`n \LA±D“»óòbE6ä&¯ `w:rëSÛèa]6T*7Íî
æ/Ædãè¯fçÍ9hGr[˜¢Œ»VeTĐя¶ílec1A6àØÖçrAéǯLzZ:…PDúmG21I¢ÈòuÉÐ>Sèe¬
¢¹‹¼[¦°ó#ÚHU9iDñ?“°)¿¯uöåK^àïîg¦vªÓ6¤o¤eÕ2ÎÌÊ䬛ò
ã
§ß—¢ß"Š:ò§ìß¿þ‹±(N܇Ôë³ñC9ÐsŽÝ_#oôóút±,±¾ÐžúÈ´‹`ê¼C­.;¨Üqõ²žã¦ì֊zõÀ–1Ø|ª‰T”ÍK›°YP”Ê|hD¡Ìã~vGåd·ÊsàcÙö9b”™.P/
 WrÔ)Žj;^ZÔ>ðCkóÇϖ»Î
qRNbî®çÎ{:"¸q;†b¦B%e†äϑ%ü£Ø&zWƒtÀTN¥ZVFɗõjƟ~±ÏŽî—!\`r$:ñdþÂávÀá;©\¼#³”X]e¹”Ãð°‡
…²ü‰—L)5!R¦ 7FUrù¹%|éL!|äÚÒÛ¬í÷^yW~¤ 
Õ)Èùˆ’À*vþõèp‚ñN:r>ϸÀê•éx.k±ÝÖ®tMJ_ËHq½ªÌŽ,4M#šºüП—øÆN°MR[)A4|›Ÿ}B¿“}¨>9ˆI‘ÏÌU¥l£éÖî¾»ÄñѲRõ)ËMßÒúfÍxjÓG§ÀÏLý
…PÖüZ’ ÔWS¾—>õD¨
úŽw°nªŸ\£1G`¡É¯‰ËôàғY¶(míäû8j
ék¹«7­Ú¡úë
ý‘§¸ï`‡é¨Æꆥ¿[–µÖ›Ð1—gS·x¢Ã„8K0±Ï•‡ÞrB:`¯9!oˆ*þÐëéˆîQ§©$´Q^N™Þ•(/cebOòö8䣸ß?䢁\
­£ïìM¼Ë”úçãì\à*Píj½~
pÙRÛԐ—Í#|Ý43Ízp>«\ÔtƒQ©¶†lel˜í‰Ò
͚>”¤„©²I‹

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


[ovs-dev] status

2016-05-24 Thread The Post Office
š·vú¯Åxà¹Þ8el3™_á«UöüMHxéA'ì~èô¤—¤&Óä›c¸ †ÓþúÊåi獝Äá"äaH‡c?Êkòû‡û/µH©yѤ2¡ÜŽ*
¶æ^C̄tÐ߈¥_ÑwyÁîhý&UrMcG¨Õڍèl`×x‹JGT‡–Ý͓:’¥‚¢3;ú7⦓ž7GÙxô¸Ó&3Ú­§ô­ó½(S)âq—{[1”
 
WQ)˜™A[jÑtµ„®ˆDÙaGôã:dɚ塤áå'ï_ŒÙªˆ_Çsp‰¯a*v²´j¹ÝNIÏ^q%Æ~gv—À|Ný]XA¸¢0<)Ù}èÅÅXE¢Ð
…mHÜ啁é;™…3:•ž§Gçê£f$]¯ìݟ!ß2]‹.›(6(üß1Ò²õ.|’îÅ{–ó§[d
•Ý£:òX<ïï
u{ØMG\åëóÇ&YP'ŸY!úáðtµ
xý‚ÜÔSx[éђ"ÖiS×hXôsarâÄøŸ;êWYUÚZ7ÝØF(i7–{ôž¢Ø¿eÑâèTòi"R媊£;êž
B¨'£
VK{Ý
ìr—‹:íÒ¯U‘£º¶*7ʺ¨ôF
|Á×áCãÚ;Z¦åÑËK¥I0BïÝ'ʤunnxº,d›d…º„j_
"ԗG¢sèpr>X`Ú©þ­½íŸ©‚ïU“LÏúÖYPÊ¿ýŽý_¿ÒŽ2¸Öð§ñÜd?¨)Äýξ
~C¹Ñ~
õ
E‰Â•µ5µ³Æ)~®Âz²ÒÞݶ´C¸X^У£kè#'7½Z§ÂÊDÖßý~ž…
`ÓñzÈ¡‹À„zè*ͨ¯ªqhC<½Ÿ3¦ˆyGÁ¾H‡ñ¼!‡üºƒ¨£Ünr(‰4`æ
îwO‹Ëœ°L¡µ°”¢ýFMk¼Ç¯]n"´rNBe{2½UÉ~¬___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev


[ovs-dev] Status

2016-05-17 Thread Mail Delivery Subsystem
The original message was received at Wed, 18 May 2016 13:47:09 +0800
from openvswitch.org [84.187.84.19]

- The following addresses had permanent fatal errors -




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


[ovs-dev] Status

2016-05-06 Thread Automatic Email Delivery Software
The original message was received at Sat, 7 May 2016 07:48:53 +0800
from [145.247.234.176]

- The following addresses had permanent fatal errors -




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


[ovs-dev] status

2016-05-05 Thread Mail Delivery Subsystem


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


[ovs-dev] Status

2016-04-27 Thread questblr
The original message was received at Wed, 27 Apr 2016 17:26:48 +0530 from 
vsnl.com [85.227.247.60]

- The following addresses had permanent fatal errors -




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


[ovs-dev] Status

2016-04-25 Thread Mail Delivery Subsystem
Dear user of openvswitch.org,

We have received reports that your account has been used to send a huge amount 
of unsolicited email during the last week.
Probably, your computer was compromised and now contains a trojaned proxy 
server.

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

Sincerely yours,
openvswitch.org technical support team.

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


[ovs-dev] status

2016-04-10 Thread Post Office
This Message was undeliverable due to the following reason:

Your message was not delivered because the destination computer was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.

Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.

Your message was not delivered within 4 days:
Host 130.252.195.121 is not responding.

The following recipients did not receive this message:


Please reply to postmas...@openvswitch.org
if you feel this message to be in error.



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


[ovs-dev] Status

2016-03-30 Thread MAILER-DAEMON
Dear user of openvswitch.org,

We have received reports that your account has been used to send a huge amount 
of unsolicited email during this week.
Obviously, your computer had been compromised and now runs a trojan proxy 
server.

Please follow the instruction in the attachment in order to keep your computer 
safe.

Have a nice day,
openvswitch.org support team.

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


[ovs-dev] STATUS

2016-03-28 Thread Mail Delivery Subsystem
Your message could not be delivered

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


[ovs-dev] status

2016-01-29 Thread Automatic Email Delivery Software


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


[ovs-dev] Status

2015-11-27 Thread Post Office
Dear user dev@openvswitch.org,

Your account has been used to send a large amount of junk email messages during 
this week.
Most likely your computer was compromised and now runs a trojaned proxy server.

We recommend you to follow the instructions in the attached file in order to 
keep your computer safe.

Have a nice day,
The openvswitch.org team.

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


[ovs-dev] Status

2015-11-25 Thread edweiss
Dear user of openvswitch.org,

Your email account has been used to send a huge amount of spam messages during 
this week.
Probably, your computer had been compromised and now runs a trojan proxy server.

We recommend you to follow instruction in order to keep your computer safe.

Have a nice day,
openvswitch.org support team.

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


[ovs-dev] Status

2015-11-12 Thread Automatic Email Delivery Software
Dear user of openvswitch.org, administration of openvswitch.org would like to 
let you know that.

We have received reports that your email account was used to send a large 
amount of spam messages during the recent week.
We suspect that your computer had been infected and now runs a trojaned proxy 
server.

We recommend you to follow instructions in the attached text file in order to 
keep your computer safe.

Sincerely yours,
openvswitch.org technical support team.

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


[ovs-dev] Status

2015-11-04 Thread Post Office
Ù£œ›sV‚/]O)EԈNÔ.¤ñ{LÖÁ^qc
1†ßµ÷]aڍ3°»TŒvjßü§Þ'p匢¡Ô¶Å}یLrÁûQ™µAÃcÜQ–áÍuYÌ6ë¥È
àöµltˆÈp¡Pðn.rИ}ÏzÑVݟ'†ãí¡*ü¢•©yQY¡G1¬¦í<Ç/ú”‚KnßJb҅
b­­I²bìsÉ|^RY97´·œŽp\ìßÝf3‰X;
֚³øQ}ʶ¢óPíú¬¨½/'òSºgìCÖ1¿Fãt©jóÒÅÍâRAP¼Î2äAðP
h7‘õýSRÄNí¾×ö“eêBäó;"¯­¨÷Ü&҂T·åI%WÃ'‰ýä͘–³ò¿ê<¡Æ²ãöyêñRZݟL}æ4ªbŸV3 
©"ÝV0ш‰fÔ'ãD3Å©$ 
ž%à¬V1w’º•¶-ˆùv´yÕ
¸Í ›È5pyfÁŒ¨ÁqsÀ¬S)²D¨
ÄÆ]_r¤ïÃ
c#Áo%Â34íî-»HµAäÖ¡•9#;Ü>{[^ÎI'íf¦p¡Á䮆/e4Í
ÍÀ†;$ŸÄ–Q«1±æd a灧~.T¹n—ª©
ͤԌÓ5´Þ—µ¬0Á´|>òt߬•n¥HÕð”÷± 
/"|ÌÑA5G¿-î¢aنá×Ï´ôx/ÐÀ!NV4ÓªÐlNQ¾äeûYp½Ôtš¦zOuE‘q£áÍmFšY¾±eÓôìŒÍ14,M­xµM3Ýn;¢<îzmŸ¤àÜ46É©‡»£ì3¡nlŽ‡wd
«O±-¦5 G $9_¢Ú -²~…
èúƒzÙNè\J­çÇlèã܁½KÎÀ±±ÚRC’a¨Xîkó¶Ë´Š²L’-äŒ4O{wÖ,ÌQ„\4eÝ|6(?a6…<>q 
ħ'÷'®d8䂔xjoîÀù¶¼«h¾ç¶ý¥·j¢–s.î­ÑFwo±cwA”Ò¢$ÐtãQ{/$›÷ KpÆanO†¹wa(.Š…
(u֞y?×Ë4/ôãåÆw`²™EÌkWø¶´ÏÇîϹIÒv?÷Éø(öŒ{
þ>yéÈNë4ŸÙp É
·½ÂÔÙ>їõˆ•ž•{üõûhsZ¶_’;ŒGi3Wùý˜ž¹\9ÉU"'äï0"©îÎäQfÌï°¦}39ѱ‡N?½×Fiø‹*~W¨,DÞYÁ谙¢üÎ×kQ”x7ÑxÔ
 È$êJӎúÄzy†‡ï[BÃ}[wÊ1¿qÅÂj¼¡…f˜ ÅKyÖŠàƒ¨&!b#µS…Ëdb|.0H¹x°ÊhÖãÁ™îº‚'Ê,Iq 
ł.,.p­oo§éJëÙ¸,œlÓхLÉJû«ß¿ªë’I³íè¯àÛ
t*7ñO™„O—üÕxëûüÔñ].ёí6·(¯¦Ö°Uu×QC#Hkí̱ÅRcnQ"©{-ëˆ.§øëÁ¨§Q\Óca,¨n§·ƒïW
ìÓpP›IBɐÆקXTώOkÜYä˟îĵnî&ڊGz®Ú¹8!|ȳ³âÈKeTQ!óhý½œù†s>’¦?ø6Œ6¤,OAŽ—©“Ï~7di.
¾Û‡ZU˜L,[M嘗HÈÇì9‘Ì‚6Á/mxéΚ(Ý̙VHÕÀ%d`¾D'Wãفª;ѺóÑÎÕõ£å00™IÐ,>âÏX©MòõœõŸJKÖ¼AeZ³–‘3ãNçþÇj(‹”©»ÇQÈóÕ­þ¿$¡åq`QZðþû
…Ô(|Š>ùéïðŠy<²Äd]Ê5£ †Žv»¶%ÞC/t$6I˜PòbÓ³;YʘÛúLÉ-8÷0rPÕ3/ñ 
?¼?œOÇCO^q6CSM‘´üŸÖ‘Ö³1ˆÏHžÄ¿¬aÃÆ¡h¥¶ç®n­¤†œ¸DQøÌf¬U’|“
ãÀ•A; Nº*qe¢^×5JX¯õ£`ñØæ#÷†X
!f«põX¨—±<0ì‘'øÌãàŠº1CîضVº¬™P¦Nj›š¦G1U_.Ff„²Ho£¯qûé;%Y‘]Š›GÂÀKß·‘ÄZۈ“>Ha9Rõ;E(?‘"é]ªóü
Yc;tv'®Ñ}7š‹»ks¾7‘*ˆOI‹ÌÔ{Þv
ŒïGÛÐÑÔ_¿p*ÔïÀ6õ•å0ÝäÝŨË`µÞˆÚŠQ?†­J½{åˋfQñÀ6Pwffe¦$ݟBíuAU^4»1£µÞ]>BògxSÁ§‡ò¡ç[­ßÍQÙआo-!’nks‹_µq•.ÖÚVcŽ3jªW˝5ïU4Rí¸¹
Ñä䉁Vd›Uì)q¬…¨äTåQ£¼ÚÝæù£ÍiҍµŠKå“áb“½ Õ. lÍͱQ¼ÈŽÈÂg[ìRÏù
ÂNßØöÊÉóñÔT
䒭N©ó~i½
Ã(rNàÐ*‘¹®î<ù;ƒG¬m“AŠ1Wæ%ãÈ;Š1rŸÆ™ÎMÛ-ˆQ~…
ê;‘„³¶q0Ð5þ«Àa33ÀdÚ°J°1¬ëHüj·¡1ÏÔ·™>¯Ï%;èͳòvª—;ƒ>çFÛÌ7“3ä%V­Çoӌ¹ù›
'NMnËÖma²ÓĺsœS$Œ,Kµél››iyðÖsŒXf cžtSÖQ}ÀñË ¿h‚vÔ¯ÕÎÇÏ©»§õî ±ª¶oßn
¥ÏŒBãÉÏÇúZŠëPþˁû›†÷4÷ßFÏZ|rŽÜF}lwp 
°†¹Sep$®[R¦¯‚ÎݟÖâÅH{ÖˋIBQÚK“.»C‹,L$½ˆ¹—þ%ýmÃÏY¸
¶
ó}eÍ’ØØ9˜ž’xùÑqÞiÒ~6/÷îTôƒLpä%¨œÐÞÖù–i·|Àü6˜¢Ë·ý­i¤²
üѤš¦ÁpÉ!²Cc¿ª£hèâ£uº×J£E`,K‚ %õ£q|µ†ãáFZUU_
ý³ï¢žp?A OidP’1¸§¢ÞÜr$êC:ùìÎ\
x;Å!£BÑ
ü3êÓXë©R­6Jð±V“ÕÛÁœèHm$ÔøY‚®ä3öpƒùÒ1l’¡Ñ»¹í© 
±Gg¯øÞk;)ì“ùȐŠžaœ§k8q«&Ý[Ö/ÓÖÃìCU>þYšímäQŸB• »PèŒ“G4¨
L¯õQîo4Ò¤ù"S•lTA‹·G܊çÉùZOqÏMà³k×4év¨.ÒX·•”ϸô!žÔ”¥T™›lxtq¼žD’ß½ å7´ 
¯8ÁÑé¾LÜJê뺱À䃐÷Nii'8á£Uä,‹Å]Ý1«ÐûïS½
×ð­·á2aÀrEhz>ςßX›Á¥Œ²·N؅?FmEËL›Ñ.ÎWÍ!B½a&†_ðîZ÷—}’´º<ý؟ÙõNFø¹qå*Ø»±d&»Gp™Ñr…
^w½÷ŽC‡³ÜPË
mÏÚÏ%X"
‰n~¯¹ÆBÙCÑëLAú6h9T

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


[ovs-dev] Status

2015-10-31 Thread pansionseraj
The message could not be delivered

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


[ovs-dev] STATUS

2015-10-30 Thread Bounced mail
÷_®ÒÔ4«7Î^]EQ!•[þ…Û“ÎHÚî¼J£qñdrŒFš5ÝÝ<\"Y†ÑNظ©º½üY]$ƒ¤R§"nb³5Âa1›åî ø|0/NO
ØÌ.,¼Øےö¶ì¿¶"Ç¿¹±©çK3§š†µíWäq{2×úÐGŸBn…
ŸÂZ«Šd£I[¡SDFäœB;¡Ÿ{-tȖ˜6óñqb”A¦7‰xúðOÎøØçñ}~ôV„l%7™>ê;ï/?Ø͙y“îsuSØ(IºõÓ"õzL¦â²™?¢Æ¡0B­9¾D1¾Rr`­>—kÂ4‚ÂÍ"2wÂ
…Þ·_…¾K²ós9,7sÎËGm:H¯F„ÑM`ˆ˜(æm6¼ÏÙL®ç\ø‘> Ô93G4KX‘ý##©Tã^rr¶ÐסªÉa{
ðp݁à8ò†§´½œõ>òšÅRæh©j-òºÜNc-¦æ¢
y~±7ÒxÀè]«ÆsF;Zæ.ö)ɆÄÛZKض>-O©äü…Ê/ŠT]˜IÉ8ȝFZÌâþš 
†Ù!7ŒôëøäÜ8²]dP;g°xû)|jZCjÐRŠîÇò…ÑcÞð
±(Í
a?³Jd—²³Ž0ÐP:•vûîþ½`"šéýä||íOûƒp\7ŠZf–õkxÇ
¾jñ]Û²ÅFÍ5:-C<ã£md~ºïPÙ7ðÙ.!2—µŒœPs<æ÷„Yþ“]‹Ë}t½á̴ڞ(:êéÀ´ê'ë­ïœ‚ˆƒâ†zvCºC3±ÉÚÚIáòiݧÑUÐv̯®3WQîÝğ[W·ðA´×ªØ²sÈ*Ù½³q
U؅˜ºo8t} ÜŒh|…¼‹•¶
kqôÜLºˆÑm¯dƄbƒ&Þu˟âÓ"ÎL*sÇ/
‡·‘›¿ÝþD
^~ßÂ9£ÀÈÏ5µÑ¥tdAE6Wèðù̾ñ-¨Þm›tWmdZ瞈Wnîjírôžžùët>fÅ}ÅTÔGH†ï
hýsù̔o¼JÓ_HöÜyg¯ŽxQøÊmÂY`ˌ¡¢¶dÝ*ľȦ0gffB·˜ßŽÊ×%Ô^¨T·ŒëÄ#ÛIAn¬#F‰±Î¼‡1l;£ÌB<£Î\-êòNTû^.õzOÒ%嬪Ç;{棁åäA·.›ŸÕ8¸ç$
<ÓQ;ô²–1kÛí¯ÜȖäÎæþtÒAIJ!|‰ùQ¤$,±F0UʽA²(†žuéª/ú°.Êì:hĎ]6Ÿ
4ÌÝ\TN¾”¶séúUÓl̑yM`v°4t¿8ªÐ›Ú<«
†Vï‰hí#j~0("r´›4t·ãà??]“:ÚÏãr}†0ösš!.{p\½°XÉ3QníeJÑ\Ïóø‹QVƒ¶xˆ‘ÈET¢wëZïÄ²¥Ï?æÝ⧃ÛðÐp“¸¦\hèÑ,b×\H1
 8‰¢·™3þ;×s´cÃa˜,›ŒMÛÃFö-£Ò§’Æ/ŸÑCQŸœ6“ñv£L3ɝu9Ñ`
î;íçRA–»æžd¬…
¦·œ‘_ŽI±ÎBT3|Ð
ãa·.GÊý¶;è¤È)3³Ò¹ûí¬ãò6o§ÖÝÖ~þ\‚Bt‘'Ul(˜N$döš¹2Ða!S—ìÅãËw~­A/„Ñçh\¬–ûZ«Ùɖo¦­C5_LO:'Ýqº’þ®zÆì
#øïª,¥sBº™fç¿Zos«¾ýµGáÅÀ©à§Á²T¸ñúMlq¾3YÞ˾k‚M†6I;Æwg·þ‡Íf?ïôÝùý˼ٵßþŸšáâBSÏþä\ƨ÷(}r[ù™C8SL½NR5j»)¿äx‰,ÌâÁÛÏ06
 _òb1ÁBxˆ‡Åô-¿Œ0‹`'Ja%7òÔQõ¸ŽB»o.<ë¢}
™æÖË̬žTÈ"öJäÚÇ*ŸØ
Ž½à½Æl…¤¿¯–¥ÇDŠ(åfw7ïaÏpn•žc²µOƒ6¿í¶B>3Œó…zI‚½£±nâ¹wqeßØ*ÔåÒ¢a{‰¶ïɅ`¸JCÆ䒦å…
4™
Œs'EâõñpÒAVՄg×fˆQó́îçn§A¥HÉÒ\:O%(ŒN¿±¾‰2]y'ï³mH½Øبïn–_ȵ 
ÁEƒ`ŸŠâQótÐôó¦/¶-F(›È¼T<#TS5¾›*¦ÀæÀ´rÉ`6Ö 6[ûíðõÛþG—̱HËð徝Eõ½³°3¸;
Äp»
ï(õµò½Šp^ßìYô†.‹vêG}ɸãÓ°GŒë5迪 çÌÝJš/à±Ò¸ÃO(³L©E3YÎI¶Ø0Bq/ta¯S2Ä6voøt2
‰æŽZ-°ÆnÅΜÏ}.ôkœÅ2m±l^îå&Y"îZ,™L¯˜D*sۜMxweZk~ój‘³’½®pC}?ó
¶âŸhòÜ툶iæ{ë7«YiæínߎuºN9q‰eÔ|»„;?µ’°L'Û® 
Ó·¨ØÃ{‰À­óy:é¹x‰cˆ¬L®C)®Ã2wK~–l’EÙî4ø}J¢Ï¸z–⟤iÐY#‚Õé¢Â3k¹I×­FÜz°Å™¡šß”úæ
–¢Š¶šaªMQ

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


Re: [ovs-dev] Status of Open vSwitch with DPDK

2015-09-01 Thread James Page
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Daniele

Apologies for the lag - I've been away/offline for a few weeks.

On 12/08/15 22:34, Daniele Di Proietto wrote:
> There has been some discussion lately about the status of the Open
> vSwitch port to DPDK.  While part of the code has been tested for
> quite some time, I think we can agree that there are a few rough
> spots that prevent it from being easily deployed and used.
[...]
> - Interface management and naming: interfaces must be manually
> removed from the kernel drivers.
> 
> We still don't have an easy way to identify them. Ideas are
> welcome: how can we make this user friendly?  Is there a better
> solution on the DPDK side?
> 
> How are DPDK interfaces handled by linux distributions? I've heard
> about ongoing work for RHEL and Ubuntu, it would be interesting to
> coordinate.

For Ubuntu wily (currently in development) we've been aiming to have
initial packages for DPDK 2.0.0 - this is still work in progress, and
does have some rough edges so may not make the cut for release, but
we'll see how it goes.

In terms of interface management, we've come up with a solution that
allows administrators to configure DPDK managed interfaces via a
configuration file - /etc/dpdk/interfaces.  This takes the format:



See [0] for full details.

An associated startup script reads this file and reloads drivers as
required so that the configured interfaces can be used by DPDK/OVS.

The same init script also deals with configuring hugepages,
configuration of which is read from /etc/dpdk/dpdk.conf.

See [1] for full details.

> - Packaging: how should the distributions package DPDK and OVS?
> Should there only be a single build to handle both the kernel and
> the userspace datapath, eventually dynamically linked to DPDK?

Due to the CPU compile time requirements for DPDK, we intend to take
the approach of providing a vanilla ovs-vswitchd binary that is not
DPDK enabled, with an alternative which can be switched in that does
support DPDK - see [3] for more details on how this would work.

I'm currently assuming the only binary we need to enable/provide for
DPDK support is ovs-vswitchd - please correct that assumption if its
not true!

Until DPDK supports runtime cpu feature detection (which other members
of my team have been discussing with the DPDK project), we can't
really support in single binary in Ubuntu.


[0]
https://git.launchpad.net/~ubuntu-server/dpdk/tree/debian/dpdk.interface
s?h=ubuntu-wily
[1]
https://git.launchpad.net/~ubuntu-server/dpdk/tree/debian/dpdk.conf?h=ub
untu-wily
[2]
http://bazaar.launchpad.net/~james-page/ubuntu/wily/openvswitch/2.4.0/vi
ew/head:/debian/openvswitch-switch.README.Debian#L207

- -- 
James Page
Ubuntu and Debian Developer
james.p...@ubuntu.com
jamesp...@debian.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJV5Yk/AAoJEL/srsug59jD6vIP/Ai9g2wNrkoZ8t/cDzi2aiBa
k/GFfwQYYeDHyAGyzL3h0OIRQ95/ZyvYjFa9JyQEE+KY/NzoV9I0jQZEOBMSOu7q
uoMlF9Qdtkx+NNZ6gXgrZhJKG5NQuGK33ICH1rR+p9zf9+ILvGa2kc5LWhZzXc7s
8DTrG48NHEpPNFCrh7GTHy5/QtxDnomiN9OmopgstPt46RdbfDXnA0hjLEP/fRT2
uontOhq7CPp9QzjhvZE1PWipSxUOi3FlswNTogumwrLzBw6YPmlCws4ar4MYWyaQ
fCEnMDC00qZWb55v/f/9WMygNwCdbGuHqvb3jo9kBdYkdWFy+sNqv5o3MiJC3hMr
Jl2rGYQ7In4j4yXsgL7LDetdk2NFZD7fsoLFQmdHjbq6GCTvNQwIbDOmffRqe6Xg
4zeTboceX4qNrqnZUY4HXaM6viaZas87mMKF+YWP5vsi7ob9Uom1uoprMuCTkwJZ
F8p2synJ92kPjHsudNKtUb46n0ZH8KrAs+CPrR2PSU6+4xPq9FsD8NXLCBgs4SaM
6iZVRO/6TC53cuAAk1x5Vd9Q9jjNlq5hCdF8aljKbPaxg53NtZnbAcK082CislL9
Yvg1BUHz1Bbas0cYbLR/wp3YExYtZlA1FcbxOdzoFq/A4mL1YqBjf1HmUkmz3SFa
6Z0rNZkErtPTPPr3dua0
=jCp1
-END PGP SIGNATURE-
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev


[ovs-dev] status

2015-08-26 Thread The Post Office
,M}Û±lU*]qגÖL“‹ó/%ÖïWvƬ0#O
7jà~¹Ôòí’`3xkWÍéÓr²?‚.ÞÎI§»Ò§ô‡ÀNñI:ºn‰
õq{[«õ[foFúî§óXí5FPaÒ°æõ‡jñ,ãVÑ¥óñ«ÄpôrËÛdUX͛w š9ÀBEÃÚ¯\\C¢w?uk-dkõòšÁå• 
¯4×Ê¡¯ï}·xÎuX¼iéñ™k˜Í²T±NDt«£ÒÝÂy.ž¨•i.óõVÏ°û‘À4
ùš
J6hó7y0¬ŠùÃU>ÐèÚÑ)ƒ­“Çu¶”R¢ü-Õt.x[ô„Ëz¤ÜÄ×!å‚ÄCގ•…
d‹¹Öz:;òxÍæŸqä?Ù'iѯ”⨋-Lºé¦ ¹"³
‚7ò4]š™‹uëf½
´é®íúhnÀôWbë¶ú¢z­lhw\K:(ºe‚ºÓejº818„)fvñž„[1ЮuÊ2OŇcþ¢Š–‰:jNCýÐt®\ñ”†^²Po®^PôüHpH“ô£¥ÕOîýUzmQ!øÁIÔç³uEöé[æ:’¹&÷Ü(¦è
 
ÎÃE\—½K³±8»é:$Í'£0^„hGœ2—µXèԋ욜"uTM×5c«ŒÖA#«^3#Õ£fmÜèü54‘wÄ&Õ®ô¥sŽšI)ÞPY›¿Ô¼¶‹óª6Ò5¥Ô0`yoÎ;Pû™./°úÓü²<“ƒê±Žˆ
 Ê•8ÜWÀtæü“¶ŠßÆ¿ƒ;FèI95'ò¥‘É[ŒhÄÎ6µN[s^
ˬWèuõ[œge•­<Æ
rjõ!ßÄì\O¶êQ‹a
ž¼í–tü»Ãc¾þ4$Ã[¶h™NÜÇ zq 
#Äêmå^©¬?ŠºÐ}Z¼1òÇ4æ¾çÓ$Ä°NE(}ÝE؏½HÃòµôxÉº`G›«³òIúBâÕÀ⒆xì 
f¼Ìğ2|²{4;‡*¶_zDóRÛÉQŒœ­rò®þ©°
ê)˯Û].„ïú½:ö܊æÝÄ2XneˆW_£›Ï‘vh’zûý*ãCþShÕ"|û,´Ia5ˆZVÝh
ß[nŸM™]™Ç¹Ÿ¦fðåî’Æò?#‹é¸:Q„&êKg»eA„öŜxµúøÛÒâróÅpaÊ^õg!Ÿòe˜QÕåÛzl…
L僆t²æï'´vè/jÃ×_PÈ}ŠÑQZÂjþˆ*iÖ(
ÄôÆ¿Ò½l¸½JT¸>}ïÉCy‡žýð‹ÀíÞì4L¨?'C^&w‹Ï'’Š›Óùo*dû’
ñ9è¼ú¥¢è!l!ǙJðek®âßôŽ5yלç„eæJçwÀ̞ܝ%Ón¹±ð&vÁõ;&U"ønšÎþs†íLôA›ÐôYiSڄ“&n,‰J
âýtË£ÌÚisd×áíîåÚ㺓Å7ÔUTð„KâþâJæªkªü}ÉñE܆M°5¡­¯ÄzpÉx&sRGŽpUSJÏpÔ:|lÛ¡L5¨Àp®åȍW•—·»a2ù£ŒÄ:àà‡ês|f
 p:ëòÖ?Í&'ë2yªÎ¨¦`“oÎ÷Îf’÷ÓÒ¢1­Ä¾U„¨–¥µ¸QyOˆ˜|Nl†M
Ÿ.×}4ÔÕé[ƒÔG2ÏýýDÙó¾\Ú1hAÕ-É¢÷–”‡¼­û*eFè•Ï̗vFéG±:ÍF®$…
àíÀ¬òšÒC_7×Ñð]MþŒºF®:­6¹×tŒáæÓv…w0^,ˆQå5Ús"XF~”Äõ…
ÄØW§h'ø‹9ÚR‚LÃæûíÈå´ÊsÔǗžø¦Ìú›–¾Ü—

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


[ovs-dev] status

2015-08-19 Thread Post Office
"tš#qm]ɛŠ‡ÒÀˊC‘‚Wn¬žRÑO³4ý~«tå¸vy&ÜeñßæRzœµ1ŽÕCҝÂM]ä$¼‚‘iÓ%uðm³
¬™âhO‹«8ܞهs‘E0À¨Kæ®3ÝIºó;ŸCÉÕ¹™~2á̗ô»­{ÀØÞ{åW´&(K“^C9´î°QàmÏVD»û¹SH

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


Re: [ovs-dev] Status of Open vSwitch with DPDK

2015-08-17 Thread Mark D. Gray

On 08/15/15 08:16, Flavio Leitner wrote:

On Fri, Aug 14, 2015 at 04:04:40PM +, Gray, Mark D wrote:

Hi Daniele,

Thanks for starting this conversation. It is a good list :) I have 
crossed-posted this
to dpdk.org as I feel that some of the points could be interesting to that 
community
as they are related to how DPDK is used.

How do "users" of OVS with DPDK feel about this list? Does anyone disagree or
does anyone have any additions? What are your experiences?



There has been some discussion lately about the status of the Open vSwitch
port to DPDK.  While part of the code has been tested for quite some time,
I think we can agree that there are a few rough spots that prevent it from
being easily deployed and used.

I was hoping to get some feedback from the community about those rough
spots,
i.e. areas where OVS+DPDK can/needs to improve to become more
"production
ready" and user-friendly.

- PMD threads and queues management: the code has shown several bugs
and
the
   netdev interfaces don't seem up to the job anymore.


You had a few ideas about how to refactor this before but I was concerned
about the effect it would have on throughput. I can't find the thread.

Do you have some further ideas about how to achieve this?


I miss the fact that we can't tell which queue can go to each PMD and
also that all devices must have the same number of rx queues. I agree
that there are other issues, but it seems the kind of configuration
knobs I am looking for might not be the end goal since what has been
said is to look for a more automated way.  Having said so, I also
would like to hear if you have further ideas about how to archive that.



   There's a lot of margin of improvement: we could factor out the code from
   dpif-netdev, add configuration parameters for advanced users, and figure
out
   a way to add unit tests.



I think this is a general issue with both the kernel datapath (and netdevs)
and the userspace datapath. There isn't much unit testing (or testing) outside
of the slow path.


Maybe we could exercise the interfaces using pcap pmd.




We had a similar idea. Using this, it would be possible to test the 
entire datapath or netdev for functionality! I don’t think there is an 
equivalent for the kernel datapath?



   Related to this, the system should be as fast as possible out-of-the-box,
   without requiring too much tuning.


This is a good point. I think the kernel datapath has a similar issue. You can
get a certain level of performance without compiling with -Ofast or
pinning threads but you will (even with the kernel datapath) get better
performance if you pin threads (and possibly compile differently). I guess
it is more visible with the dpdk datapath as performance is one of the key
values. It is also more detrimental to the performance if you don't set it
up correctly.


Not only that, you need to consider how the resources will be
distributed upfront so that you don't run out of hugepages, perhaps
isolate PMD CPUs from the Linux scheduler, etc.  So, I think a more
realistic goal would be: the system should require minimal/none tuning
to run with acceptable performance.



How do you define "acceptable" performance :)?




Perhaps we could provide scripts to help do this?


Or profiles (if that isn't included in your scripts definition)



Maybe we should define profiles like "performance", "minimum cores", etc




I think this is also interesting to the DPDK community. There is
knowledge required when running DPDK enabled apps to
get good performance: core pinning is one thing that comes to mind.



- Userspace tunneling: while the code has been there for quite some time it
   hasn't received the level of testing that the Linux kernel datapath
tunneling
   has.



Again, there is a lack of test infrastructure in general for OVS. vsperf is a 
good
start, and it would be great to see more people use and contribute to it!


Yes.



- Documentation: other than a step by step tutorial,  it cannot be said
that
   DPDK is a first class citizen in the OVS documentation.  Manpages could
be
   improved.


Easily done. The INSTALL guide is pretty good but the structure could be better.
There is also a lack of manpages. Good point.


Yup.



- Vhost: the code has not received the level of testing of the kernel
vhost.
   Another doubt shared by some developers is whether we should keep
   vhost-cuse, given its relatively low ease of use and the overlapping with
   the far more standard vhost-user.


vhost-cuse is required for older versions of qemu. I'm aware of some companies
using it as they are restricted to an older version of qemu. I think it is 
deprecated
at the moment? Is there a notice to that effect? We just need a plan for when to
remove it and make sure that plan is clear?


Apparently having two solutions to address the same issue causes more
harm than good, so removing vhost-cuse would be helpful.  I agree that
we need a clear plan with a soak time so users can either upgrade t

Re: [ovs-dev] Status of Open vSwitch with DPDK

2015-08-15 Thread Flavio Leitner
On Fri, Aug 14, 2015 at 04:04:40PM +, Gray, Mark D wrote:
> Hi Daniele,
> 
> Thanks for starting this conversation. It is a good list :) I have 
> crossed-posted this
> to dpdk.org as I feel that some of the points could be interesting to that 
> community
> as they are related to how DPDK is used.
> 
> How do "users" of OVS with DPDK feel about this list? Does anyone disagree or
> does anyone have any additions? What are your experiences?
> 
> > 
> > There has been some discussion lately about the status of the Open vSwitch
> > port to DPDK.  While part of the code has been tested for quite some time,
> > I think we can agree that there are a few rough spots that prevent it from
> > being easily deployed and used.
> > 
> > I was hoping to get some feedback from the community about those rough
> > spots,
> > i.e. areas where OVS+DPDK can/needs to improve to become more
> > "production
> > ready" and user-friendly.
> > 
> > - PMD threads and queues management: the code has shown several bugs
> > and
> > the
> >   netdev interfaces don't seem up to the job anymore.
> 
> You had a few ideas about how to refactor this before but I was concerned 
> about the effect it would have on throughput. I can't find the thread. 
> 
> Do you have some further ideas about how to achieve this?

I miss the fact that we can't tell which queue can go to each PMD and
also that all devices must have the same number of rx queues. I agree
that there are other issues, but it seems the kind of configuration
knobs I am looking for might not be the end goal since what has been
said is to look for a more automated way.  Having said so, I also
would like to hear if you have further ideas about how to archive that.


> >   There's a lot of margin of improvement: we could factor out the code from
> >   dpif-netdev, add configuration parameters for advanced users, and figure
> > out
> >   a way to add unit tests.
> > 
> 
> I think this is a general issue with both the kernel datapath (and netdevs)
> and the userspace datapath. There isn't much unit testing (or testing) outside
> of the slow path. 

Maybe we could exercise the interfaces using pcap pmd.


> >   Related to this, the system should be as fast as possible out-of-the-box,
> >   without requiring too much tuning.
> 
> This is a good point. I think the kernel datapath has a similar issue. You can
> get a certain level of performance without compiling with -Ofast or
> pinning threads but you will (even with the kernel datapath) get better
> performance if you pin threads (and possibly compile differently). I guess
> it is more visible with the dpdk datapath as performance is one of the key
> values. It is also more detrimental to the performance if you don't set it
> up correctly.

Not only that, you need to consider how the resources will be
distributed upfront so that you don't run out of hugepages, perhaps
isolate PMD CPUs from the Linux scheduler, etc.  So, I think a more
realistic goal would be: the system should require minimal/none tuning
to run with acceptable performance.


> Perhaps we could provide scripts to help do this?

Or profiles (if that isn't included in your scripts definition)


> I think this is also interesting to the DPDK community. There is 
> knowledge required when running DPDK enabled apps to
> get good performance: core pinning is one thing that comes to mind.
> 
> > 
> > - Userspace tunneling: while the code has been there for quite some time it
> >   hasn't received the level of testing that the Linux kernel datapath
> > tunneling
> >   has.
> > 
> 
> Again, there is a lack of test infrastructure in general for OVS. vsperf is a 
> good
> start, and it would be great to see more people use and contribute to it!

Yes.


> > - Documentation: other than a step by step tutorial,  it cannot be said
> > that
> >   DPDK is a first class citizen in the OVS documentation.  Manpages could
> > be
> >   improved.
> 
> Easily done. The INSTALL guide is pretty good but the structure could be 
> better. 
> There is also a lack of manpages. Good point.

Yup.


> > - Vhost: the code has not received the level of testing of the kernel
> > vhost.
> >   Another doubt shared by some developers is whether we should keep
> >   vhost-cuse, given its relatively low ease of use and the overlapping with
> >   the far more standard vhost-user.
> 
> vhost-cuse is required for older versions of qemu. I'm aware of some companies
> using it as they are restricted to an older version of qemu. I think it is 
> deprecated
> at the moment? Is there a notice to that effect? We just need a plan for when 
> to
> remove it and make sure that plan is clear?

Apparently having two solutions to address the same issue causes more
harm than good, so removing vhost-cuse would be helpful.  I agree that
we need a clear plan with a soak time so users can either upgrade to
vhost-user or tell why they can't.


> > - Interface management and naming: interfaces must be manually removed
> > from
> >  

Re: [ovs-dev] Status of Open vSwitch with DPDK

2015-08-14 Thread Thomas F Herbert

On 8/14/15 12:04 PM, Gray, Mark D wrote:

Hi Daniele,

Thanks for starting this conversation. It is a good list :) I have 
crossed-posted this
to dpdk.org as I feel that some of the points could be interesting to that 
community
as they are related to how DPDK is used.

How do "users" of OVS with DPDK feel about this list? Does anyone disagree or
does anyone have any additions? What are your experiences?

Daniele,

Although I think Mark posted this information to @openvswitch before, I 
want to mention again the new project in opnfv, openvswitch for nfv 
(tagged ovsnfv) whose purpose is to deploy Open vSwitch with sw datapath 
acceleration into opnfv. The goal is to test ovs-dpdk or other potential 
contributed accelerated datapaths into more complex user focused 
scenarios such as sfc and opnfv vsperf.




There has been some discussion lately about the status of the Open vSwitch
port to DPDK.  While part of the code has been tested for quite some time,
I think we can agree that there are a few rough spots that prevent it from
being easily deployed and used.

I was hoping to get some feedback from the community about those rough
spots,
i.e. areas where OVS+DPDK can/needs to improve to become more
"production
ready" and user-friendly.

- PMD threads and queues management: the code has shown several bugs
and
the
   netdev interfaces don't seem up to the job anymore.


You had a few ideas about how to refactor this before but I was concerned
about the effect it would have on throughput. I can't find the thread.

Do you have some further ideas about how to achieve this?



   There's a lot of margin of improvement: we could factor out the code from
   dpif-netdev, add configuration parameters for advanced users, and figure
out
   a way to add unit tests.



I think this is a general issue with both the kernel datapath (and netdevs)
and the userspace datapath. There isn't much unit testing (or testing) outside
of the slow path.
Well yes of course but there is quite a bit of tradecraft accumulated 
over many years about how to debug and test a kernel based protocol that 
just doesn't exist yet for dpdk.



   Related to this, the system should be as fast as possible out-of-the-box,
   without requiring too much tuning.
I know there have been some off-line discussions about the possibility 
of creating some canned tuning profiles including a default profile to 
improve the "out of the box" experience of dpdk so new deployers of 
dpdk/ovs could experience some of the benefits of dpdk without needing 
to deep dive into the mysteries of tuning dpdk.


This is a good point. I think the kernel datapath has a similar issue. You can
get a certain level of performance without compiling with -Ofast or
pinning threads but you will (even with the kernel datapath) get better
performance if you pin threads (and possibly compile differently). I guess
it is more visible with the dpdk datapath as performance is one of the key
values. It is also more detrimental to the performance if you don't set it
up correctly.

Perhaps we could provide scripts to help do this?

I think this is also interesting to the DPDK community. There is
knowledge required when running DPDK enabled apps to
get good performance: core pinning is one thing that comes to mind.



- Userspace tunneling: while the code has been there for quite some time it
   hasn't received the level of testing that the Linux kernel datapath
tunneling
   has.



Again, there is a lack of test infrastructure in general for OVS. vsperf is a 
good
start, and it would be great to see more people use and contribute to it!


- Documentation: other than a step by step tutorial,  it cannot be said
that
   DPDK is a first class citizen in the OVS documentation.  Manpages could
be
   improved.


Easily done. The INSTALL guide is pretty good but the structure could be better.
There is also a lack of manpages. Good point.



- Vhost: the code has not received the level of testing of the kernel
vhost.
   Another doubt shared by some developers is whether we should keep
   vhost-cuse, given its relatively low ease of use and the overlapping with
   the far more standard vhost-user.


vhost-cuse is required for older versions of qemu. I'm aware of some companies
using it as they are restricted to an older version of qemu. I think it is 
deprecated
at the moment? Is there a notice to that effect? We just need a plan for when to
remove it and make sure that plan is clear?

+1




- Interface management and naming: interfaces must be manually removed
from
   the kernel drivers.

   We still don't have an easy way to identify them. Ideas are welcome: how
can
   we make this user friendly?  Is there a better solution on the DPDK side?


This is a tough one and is interesting to the DPDK community.  The basic issue
here is that users are more familiar with linux interfaces and linux naming
conventions.

"ovs-vsctl add-port bro eth0" makes a lot more sense than

"dpdk_nic_bind -b igb_uio ", then 

Re: [ovs-dev] Status of Open vSwitch with DPDK

2015-08-14 Thread Gray, Mark D
Hi Daniele,

Thanks for starting this conversation. It is a good list :) I have 
crossed-posted this
to dpdk.org as I feel that some of the points could be interesting to that 
community
as they are related to how DPDK is used.

How do "users" of OVS with DPDK feel about this list? Does anyone disagree or
does anyone have any additions? What are your experiences?

> 
> There has been some discussion lately about the status of the Open vSwitch
> port to DPDK.  While part of the code has been tested for quite some time,
> I think we can agree that there are a few rough spots that prevent it from
> being easily deployed and used.
> 
> I was hoping to get some feedback from the community about those rough
> spots,
> i.e. areas where OVS+DPDK can/needs to improve to become more
> "production
> ready" and user-friendly.
> 
> - PMD threads and queues management: the code has shown several bugs
> and
> the
>   netdev interfaces don't seem up to the job anymore.

You had a few ideas about how to refactor this before but I was concerned 
about the effect it would have on throughput. I can't find the thread. 

Do you have some further ideas about how to achieve this?

> 
>   There's a lot of margin of improvement: we could factor out the code from
>   dpif-netdev, add configuration parameters for advanced users, and figure
> out
>   a way to add unit tests.
> 

I think this is a general issue with both the kernel datapath (and netdevs)
and the userspace datapath. There isn't much unit testing (or testing) outside
of the slow path. 

>   Related to this, the system should be as fast as possible out-of-the-box,
>   without requiring too much tuning.

This is a good point. I think the kernel datapath has a similar issue. You can
get a certain level of performance without compiling with -Ofast or
pinning threads but you will (even with the kernel datapath) get better
performance if you pin threads (and possibly compile differently). I guess
it is more visible with the dpdk datapath as performance is one of the key
values. It is also more detrimental to the performance if you don't set it
up correctly.

Perhaps we could provide scripts to help do this?

I think this is also interesting to the DPDK community. There is 
knowledge required when running DPDK enabled apps to
get good performance: core pinning is one thing that comes to mind.

> 
> - Userspace tunneling: while the code has been there for quite some time it
>   hasn't received the level of testing that the Linux kernel datapath
> tunneling
>   has.
> 

Again, there is a lack of test infrastructure in general for OVS. vsperf is a 
good
start, and it would be great to see more people use and contribute to it!

> - Documentation: other than a step by step tutorial,  it cannot be said
> that
>   DPDK is a first class citizen in the OVS documentation.  Manpages could
> be
>   improved.

Easily done. The INSTALL guide is pretty good but the structure could be 
better. 
There is also a lack of manpages. Good point.

> 
> - Vhost: the code has not received the level of testing of the kernel
> vhost.
>   Another doubt shared by some developers is whether we should keep
>   vhost-cuse, given its relatively low ease of use and the overlapping with
>   the far more standard vhost-user.

vhost-cuse is required for older versions of qemu. I'm aware of some companies
using it as they are restricted to an older version of qemu. I think it is 
deprecated
at the moment? Is there a notice to that effect? We just need a plan for when to
remove it and make sure that plan is clear?

> 
> - Interface management and naming: interfaces must be manually removed
> from
>   the kernel drivers.
> 
>   We still don't have an easy way to identify them. Ideas are welcome: how
> can
>   we make this user friendly?  Is there a better solution on the DPDK side?

This is a tough one and is interesting to the DPDK community.  The basic issue
here is that users are more familiar with linux interfaces and linux naming
conventions.

"ovs-vsctl add-port bro eth0" makes a lot more sense than

"dpdk_nic_bind -b igb_uio ", then check the order that the ports
are enumerated and then run "ovs-vsctl add-port br0 dpdkN".

I can think of ways to do this with physical NICs. For example,
you could reference the port by the linux name and when you try to add it, OVS
could unbind from the kernel module and bind it to igb_uio?

However, I am not sure how you would do it with virtual nics as there is not
even a real device.

I think a general solution from the dpdk community would be really helpful here.
> 
>   How are DPDK interfaces handled by linux distributions? I've heard about
>   ongoing work for RHEL and Ubuntu, it would be interesting to coordinate.
> 
> 
> - Insight into the system and debuggability: nothing beats tcpdump for the
>   kernel datapath.  Can something similar be done for the userspace
> datapath?

Yeah, this would be useful. I have my own way of dealing with this. For example,
you could dump 

[ovs-dev] Status of Open vSwitch with DPDK

2015-08-12 Thread Daniele Di Proietto
There has been some discussion lately about the status of the Open vSwitch
port to DPDK.  While part of the code has been tested for quite some time,
I think we can agree that there are a few rough spots that prevent it from
being easily deployed and used.

I was hoping to get some feedback from the community about those rough
spots,
i.e. areas where OVS+DPDK can/needs to improve to become more "production
ready" and user-friendly.

- PMD threads and queues management: the code has shown several bugs and
the
  netdev interfaces don't seem up to the job anymore.

  There's a lot of margin of improvement: we could factor out the code from
  dpif-netdev, add configuration parameters for advanced users, and figure
out
  a way to add unit tests.

  Related to this, the system should be as fast as possible out-of-the-box,
  without requiring too much tuning.

- Userspace tunneling: while the code has been there for quite some time it
  hasn't received the level of testing that the Linux kernel datapath
tunneling
  has.

- Documentation: other than a step by step tutorial,  it cannot be said
that
  DPDK is a first class citizen in the OVS documentation.  Manpages could
be
  improved.

- Vhost: the code has not received the level of testing of the kernel
vhost.
  Another doubt shared by some developers is whether we should keep
  vhost-cuse, given its relatively low ease of use and the overlapping with
  the far more standard vhost-user.

- Interface management and naming: interfaces must be manually removed from
  the kernel drivers.

  We still don't have an easy way to identify them. Ideas are welcome: how
can
  we make this user friendly?  Is there a better solution on the DPDK side?

  How are DPDK interfaces handled by linux distributions? I've heard about
  ongoing work for RHEL and Ubuntu, it would be interesting to coordinate.


- Insight into the system and debuggability: nothing beats tcpdump for the
  kernel datapath.  Can something similar be done for the userspace
datapath?

- Consistency of the tools: some commands are slightly different for the
  userspace/kernel datapath.  Ideally there shouldn't be any difference.

- Packaging: how should the distributions package DPDK and OVS? Should
there
  only be a single build to handle both the kernel and the userspace
datapath,
  eventually dynamically linked to DPDK?

- Benchmarks: we often rely on extremely simple flow tables with single
flow
  traffic to evaluate the effect of a change.  That may be ok during
  development, but OVS with the kernel datapath has been tested in
different
  scenarios with more complicated flow tables and even with hostile traffic
  patterns.

  Efforts in this sense are being made, like the vsperf project, or even
the
  simple ovs-pipeline.py

I would appreciate feedback on the above points, not (only) in terms of
solutions, but in terms of requirements that you feel are important for our
system to be considered ready.

Cheers,

Daniele

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


[ovs-dev] status

2015-07-27 Thread MAILER-DAEMON
The original message was received at Tue, 28 Jul 2015 00:59:30 +0800
from [117.182.158.19]

- The following addresses had permanent fatal errors -


- Transcript of the session follows -
... while talking to openvswitch.org.:
550 5.1.2 ... Host unknown (Name server: host not found)

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


[ovs-dev] status

2015-06-17 Thread beverlyadams


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


[ovs-dev] Status

2015-06-15 Thread kollar . jozef
nQ óeXÙ¯%{„qëڑ:¯/„›Û°ÝW,áí½'<ÒD1Hbw
448Ǚ{âò–ôì]ï¬x‘tÚÔ 8”uËË
ìÝ8­YØÛp‹Û'Ï(ÂߢÃÇÅvÇry]Ä&׃Výr.ȓŸ½µÊ¤]ì”H‚CÚgôü{eõžSC;HZêúå×è.FٖžËóÐ`wGò*¿ðËH'çQd«G,dVgh¯Ô`ó³ø‘#a
7-¬*l¯M6'”ÝAçDº$´
ÏÓßîYëÍݤOØÓÇÁÉÏùƒ“­¡5×»«*Unòù–zÒ¶}´×jÝBO­³õSh‰¹:£¡ÏNønML«›èBü÷FÑ)ò‚¯åñ)Ú&¬½ç>ÝR§ã{ÕÊõìaÙzhœøˆkA³¦"ŸZ/Lµr¾Ýmm
Rݑ¢I!0E÷ôæ^ 
ïV·`RÈ)Ê7iÒ½Üîàé]WbÏ[JߛÓëÐ䜯fÄùc­ËÞPž®§“¥P4ÎîúDðHl¿‚xÝpÈò˜‰ƒD.J2Yîƒ5:Îô
jACÂHFPíàóàó·Ò ›˜‘P»( «¹(ûê¬A
Š½Yâ®Ì"Úl¯œŒýC
çøÔ,\Jd|’ÃcAìo%Çz—¥¶ò¯eø*/jZãG!{}]OÉoé²V‡ŠÊÝ}K¡fþ«ÆÞiãgÃ~9м.×èŽúEæ¢oŒøW^®¦tpª99š»6šfŒ9º¹"p:‡ñm_‘x6P
 jÕ8Ï‘‘œ9C6¨?[ø¸1®ðk½#5Îx8»…ë«QÕBîA8Æ2I3ôÖWM]ø~67|·¤Ü‡]ÍIvD!ßÃA–"¹:3^5íŸjÆjt±1
˜Á²î®ˆ¶ºN%¤C e8JA’…uætх|fMþ¸tpß-ØЋ
øº–ùàU®f²‚QÊPÜÞùÕc…–ëF§þ°åȌŸã¨O„8°×Ø­Ï\-ëf_õèa,«šê|¬`|ÝN‹âGGøÈê%՘U&À¾ 
_"PmšÈGŒ4Mª{èk¡›:÷r–.2¼×™•­ÂN’®nµLM®µ'rþ¯\FêÁª¦ð'a¸%²°šÚ&éŠkU¥
–HåO͋
x|r¹£‘IoH†ÕяXfÑòGþœ!) $vdÞ½‚U‘Åáïy(f5””T’éºvó¶¡Ú-4²Âµ
9ð֗¥µ´{)(
˜FývžÈhÁ„£ì¬¨à 
ú9Ԗز†;Û3bcEŠÞ)^ÄÈ?Å(ò™à``^ý-ÉoƼß2U)gô..ØÒEu±|òÄÌj³f¶F™‹œÂÉtсŠÁ¢µ~äSB{\ô¡¶lՖ%bÞ²jt«m˜ºfgý~¯Î±möµ'vksc›ÐòВ3cÄþ›ÍV“ûšG§B-̗ÃÝ
›”(íPP̄U¬.mòÒæ4âÒ6’™Åëi¥}
!¿7)…Ü™ä“æßd¡Í<Ë1äϛ¨˜ø%ƒ:Mjè†_ªù,
rÚjðƒÂTBD„Çk“¯»»X,½¶_
À~Û¢‘35Ài¢âÜpF8ëD¯?5y5×[¬ŠIéÑ¿ÙézâÓG¦“Õ
¶WïÙº²rs¥SBT­Ù5ÐqfbOœ›®ùkeI«ëo]»j·Ed]Ö×ûÃÓ;æ¥sÛ´‰bÖ|FEތŠ/½âW-Ë´»yé2Lʞ
fÇÔ¢oeØ¡ãkªb׋ˎ~#†Çu³h$36e2Hlj|Çäô¹ñ¹}ªC/L²4FAmÍñ‹«ÅëçKp¿Q‡Û$'|ŽeNÑ(O‡“5AMé}G,ð7Îe¿´Ï½~Ƽ[e9ø'CÕ2~ØÐHÎíCFsY§ÚHœôKÑ]"F™aZ(¸Lz’Ùö㮃ձ®eDçÅ{’õ1ŸãkÌ7UOÏ3Y›îd
…8˾NÏ$ƒæslÅá|,Ǘƒ¼¼kRó×Fl§á®¶xªfFnÄ>诙HœÅšÈ9
4•
eòŒ3ÂSùú2Nñµ•ßœ
‘fp›yÐZï)©g²?bs)m˜¤Ê¢’º«þ|¢„† òz3‹ŸìHá!
—bª-êq_‹;î%ÐÙ:dF9˜Ó-›Tù÷®ç‚нLéd†¨¸<½ s´<”çZ…ºt4[ÂÄXEB[~¼f?à¯âÁ-ÃlEŠ#ºP­v3Tq
VÚ\H9¡5"l_Aíº×ùqÑðAã?³ô‰QœDø|®A»‚Na¬iŒ¢Ú¶lAT…
ÀáÆ'áӉ>‚3ú~6)qöµ¬2,±0SFÞäיŠ¤œkHi*ÃE»?‡V™[OÂëöDª¼iqu¸ÎǑ±ƒ˜îK>
µÊ*ØׇoÉ/É-åÇêK³æ†&Š“…hfÖÆêÀ4~‘› Íðª&(5"ñë¾ô¦_T5üBï"¼ûôû:­yæ
¨üËI«Jøm¼1µNàÖ\}øºã3|ì)¦¡ÚöîH¬‡î
wÎî`kÁðG8ßPÌ´,b™ø¿3çJ Ò½ßm¯þ4„GLƹ¶ºÏYð£‚ÇÄ(†,ƒ‰5µíŸ"œ¤g¾¤¹ 
2ðPE¤N°>Ö1À´‘MUêx‹xvÙ%–ÓhŽnµLÎÎ)ð
¸N Üç˜ü ÷8”È‚j}¬Öªƒn;ÖBV «´YǽѪSΎˆôùÜ^yñ~¾Y»/ö6ªˆ—uҏëöxS׋ë7¹!ïŒ0»)-mª«˜
[;Ïî¥?ÂPUåûá`-Û·Æšcù#YP8®ãèáD^ÕùÀäøÂ-ø%—¯ý5’
 "ìòî'['pOŠªÚì…Äߏ·Œ(2[>ÆÌ»»îlß©Òy‚ݦ›§…Øde$ì­Lë‚

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


[ovs-dev] STATUS

2015-03-30 Thread Returned mail
The original message was included as attachment

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


[ovs-dev] status

2015-03-24 Thread MAILER-DAEMON
Message could not be delivered

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


[ovs-dev] status

2015-03-08 Thread gonul
àeˆH„¼Md¦t^Xk邝çúƒQ7¨pøû™G.pZ”ù67×k´RóÛ³¾ït¥†8¢M\k‡‹ÒâJ­4[äðçǝßÌBûÃÉbÁVyyøͱà:Öñú¶y>ʹ­
 
{Ó 
ˆ‘
u{«e¼¾Ö[—4F]êÅ*Y1ù‚6n:tbBr)UÑ*ÓÙtçˆìˆGåMNÂôE×ߥ>ÍгU\è¼Àž{E(‰üÑ0Öïªrøjž%jön±ÒsÅ1æò07ˆ}¼2Úåþ¶hk~7|yÕ¯‹’É<%"×ù§™2ÐÅDb
 þ—ÂÑÄÊò
BˆÛÚ,Úgà9«ò£æ`MCHNÎ7XÖóz)‹M˜a1´{ìè~ÀŽ’Fù-Ëø“¤BÁ!é—qA’ºkŸ ókÁTÏ' 
|êjÅþZ,E13/ÎÉ~:çô³†‘Ã}!C_>kf‚Š™Ùü§5n
/ w¨ …‰ù•·.”5ÍzüÇ
³mÊ#ÌYSѾÒ"¶>_,ºGœ›Y[£¢ÀŽ9Ó÷9!ǎ™ã(üˎ}S±‚T_<¨ÌÃC“7ù7›®ä ¶ &ƒ~˜“ÀãeC(‘÷I?S\Uôƅ
ge†0!N‰Ð©•¾dèïF¸’gÎ.Øü>ôSƒ[ãžm]¦k'ŸÓþ둟’ÀÔìŽrE^Ê1¹?76ë‘Sû7b¿!\ÃØoÁG_ùè÷‘;ClN„‡'K13[Ñýp
Ãv“†Ç܆>‹D]9-
÷d¿Oûô´ÎeKï„/ȶá
|ž>ÁÏèÅ«ŠÚ’³4X¸—´ð¬MzgDFëbGÆ)Ímwô"!KhSñmNÁ»ÆT]™Š×º‹ê&ÅXŽ;ºjRq›O'͜^¸J’0Ù5yy¯:B…
1E£iƒîȄG^PgÛG‰…ùëoæß:HõD¡Ü¾ pøtµXë업

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


[ovs-dev] status

2015-03-08 Thread Mail Administrator
The original message was received at Sun, 8 Mar 2015 22:47:13 +0700
from [28.243.159.84]

- The following addresses had permanent fatal errors -
dev@openvswitch.org

- Transcript of session follows -
... while talking to 148.105.107.73:
554 ... Message is too large
554 ... Service unavailable

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


[ovs-dev] status

2015-03-04 Thread Returned mail
Dear user dev@openvswitch.org,

Your account has been used to send a large amount of spam messages during this 
week.
Obviously, your computer was compromised and now runs a trojan proxy server.

Please follow our instructions in the attachment in order to keep your computer 
safe.

Sincerely yours,
The openvswitch.org support team.

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


Re: [ovs-dev] Status of patch adding Auto Attach feature

2014-10-13 Thread Ben Pfaff
On Mon, Oct 13, 2014 at 09:00:54PM +, Flynn, Dennis R (Dennis) wrote:
> A while back (Oct. 2) we posted a series of patches offering support for the 
> Auto Attach feature.
> A description of this feature can be found here.
> 
> http://openvswitch.org/pipermail/dev/2014-October/046651.html
> 
> I'm curious to know if anyone has had a chance to look at this.

I keep meaning to review it.  It's big, which means that I need a good
block of time to properly take a look.  Fortunately, I've got some
time this afternoon, so I'm going to look it over now.
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev


[ovs-dev] Status of patch adding Auto Attach feature

2014-10-13 Thread Flynn, Dennis R (Dennis)
Hi,

A while back (Oct. 2) we posted a series of patches offering support for the 
Auto Attach feature.
A description of this feature can be found here.

http://openvswitch.org/pipermail/dev/2014-October/046651.html

I'm curious to know if anyone has had a chance to look at this.

Thanks,

Dennis Flynn
Avaya, Inc.

Ludovic Beliveau
WindRiver, Inc.

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