date:20170118

[opnfv-tech-discuss] Canceled: [VSPERF] Weekly Call

2017-01-18 Thread Cooper, Trevor

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Cooper, Trevor":MAILTO:trevor.coo...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='opnfv-te
 ch-disc...@lists.opnfv.org':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Andrew V
 eitch':MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Bill Mic
 halowski':MAILTO:bmich...@redhat.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Mario To
 rrecillas Rodriguez':MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Sen, Pro
 dip'":MAILTO:prodip@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Alan McN
 amee':MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Murthy, K
 rishna J":MAILTO:krishna.j.mur...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Tomasini
 , Lorenzo'":MAILTO:lorenzo.tomas...@fokus.fraunhofer.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Devlin, M
 ichelle":MAILTO:michelle.dev...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Pierre Ly
 nch:MAILTO:ply...@ixiacom.com
DESCRIPTION;LANGUAGE=en-US:VSPERF Weekly Meeting - Wednesday UTC 16h00\, Ir
 eland 16h00\, Pacific 8h00\n\n•   IRC:\n•   freenode https://f
 reenode.net/\n•   IRC channel: #opnfv-vswitchperf http://webchat.fre
 enode.net/?channels=opnfv-vswitchperf\n•   MeetBot: http://meetbot.o
 pnfv.org/meetings/opnfv-vswitchperf/2015/\n\nPlease join my meeting from y
 our computer\, tablet or smartphone.\nhttps://global.gotomeeting.com/join/
 915183117\n\nYou can also dial in using your phone.\nUnited States +1 (571
 ) 317-3129\n\nAccess Code: 915-183-117\n\nMore phone numbers\nAustralia +6
 1 2 8355 1040\nAustria +43 7 2088 0034\nBelgium +32 (0) 28 93 7018\nCanada
  +1 (647) 497-9350\nDenmark +45 69 91 88 64\nFinland +358 (0) 923 17 0568\
 nFrance +33 (0) 170 950 592\nGermany +49 (0) 692 5736 7210\nIreland +353 (
 0) 15 360 728\nItaly +39 0 247 92 13 01\nNetherlands +31 (0) 208 080 219\n
 New Zealand +64 9 909 7888\nNorway +47 75 80 32 07\nSpain +34 955 32 0845\
 nSweden +46 (0) 853 527 836\nSwitzerland +41 (0) 435 0167 13\nUnited Kingd
 om +44 (0) 330 221 0086\n\n\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=WE;WKST=SU
EXDATE;TZID=Pacific Standard Time:20161207T08,20161228T08
SUMMARY;LANGUAGE=en-US:Canceled: [opnfv-tech-discuss] [VSPERF] Weekly Call
DTSTART;TZID=Pacific Standard Time:20161109T08
DTEND;TZID=Pacific Standard Time:20161109T09
UID:04008200E00074C5B7101A82E008B0A87F15B439D201000
 010007467EEA0909BBF46903658F8C0CBFD35
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170119T043838Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:4
LOCATION;LANGUAGE=en-US:GTM and #opnfv-vswitchperf
X-MICROSOFT-CDO-APPT-SEQUENCE:4
X-MICROSOFT-CDO-OWNERAPPTID:-420956192
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Canceled: [opnfv-tech-discuss] [VSPERF] Weekly Call
DTSTART;TZID=Pacific Standard Time:20161130T08
DTEND;TZID=Pacific Standard Time:20161130T09
UID:04008200E00074C5B7101A82E008B0A87F15B439D201000
 010007467EEA0909BBF46903658F8C0CBFD35
RECURRENCE-ID;TZID=Pacific Standard Time:20161130T00
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170119T043838Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:4
LOCATION:GTM and #opnfv-vswitchperf
X-MICROSOFT-CDO-APPT-SEQUENCE:4
X-MICROSOFT-CDO-OWNERAPPTID:-420956192
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Canceled: [opnfv-tech-discuss] [VSPERF] Weekly Call
DTSTART;TZID=Pacific Standard Time:20170118T08
DTEND;TZID=Pacific Standard Time:20170118T09
UID:04008200E00074C5B7101A82E008B0A87F15B439D201000
 010007467EEA0909BBF46903658F8C0CBFD35
RECURRENCE-ID;TZID=Pacific Standard Time:20170118T00
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170119T043838Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:4
LOCATION:GTM and #opnfv-vswitchperf
X-MICROSOFT-CDO-APPT-SEQUENCE:4
X-MICROSOFT-CDO-OWNERAPPTID:-420956192
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

2017-01-18 Thread Wenjing Chu

Good discussions. 

Another area that we need to consider is the availability of good quality test 
cases in OPNFV. It is one thing to consider if a particular feature itself is 
"mature', we also need a set of test cases that can adequately evaluate the 
feature as part of Dovetail. Projects (and testing projects functest/yardstick) 
should also evaluate the "maturity" of their test suites as one of the criteria.

Morgan,
The old thread on percentage of scenarios is not without valid points, but the 
relevance/significance of scenarios is a disqualifying issue IMO. I'll 
illustrate with an example,
E.g. I looked into all the scenarios in Colorado in the wiki, and filter them 
with 
1) participates in at least one of C-1.0, 2.0, 3.0
2) supports ha
2) supports 2 or more installers

If the above hypothetical criteria sounds reasonable, then there are only 6 
scenarios remain. One can imagine a case where someone pass all the other 
scenarios (39 out of total 45 scenarios = 87%) , but not really address what we 
think as important. This is the state we found ourselves in at Colorado, which, 
I hope, future releases can evolve/improve.

Here are the 6 scenarios I was able to find. I used this table for source (may 
have inaccuracy in it - I didn’t try to verify):  
https://wiki.opnfv.org/display/SWREL/Colorado+Scenario+Status

os-odl_l3-nofeature-ha  Apex,Compass,Fuel
os-nosdn-nofeature-ha   Apex,Compass,Fuel, Joid
os-odl_l2-nofeature-ha  Apex,Compass,Fuel, Joid
os-onos-nofeature-haApex,Compass,Joid
os-odl_l2-bgpvpn-ha Apex,Fuel
os-onos-sfc-ha  Compass,Fuel,Joid

Regards,
Wenjing

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 
morgan.richo...@orange.com
Sent: Wednesday, January 18, 2017 6:50 PM
To: Tapio Tallgren ; Jose Lausuch 
; Christopher Price ; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed 
fully in C release

Le 18/01/2017 à 11:07, Tapio Tallgren a écrit :
> Good topic, I also felt that the criteria were not too clear.
>
> My interpretation was that if we are testing a feature that should be 
> in all OPNFV platforms and which is generally available in the 
> industry, and which does not require a specific installation tool, 
> then many OPNFV installers would support it. Perhaps even all of them.
part of the feature alignment for "mature" features evoked in the discussion on 
priorities not realistic for Danube, but could be for E and somehow linked to 
the discussion on scenario refactoring it is a richness to have several 
installers until a feature is not mature, it makes fully sense to focus on only 
1 installer in specific scenario(s) but when the integration is done and 
available since 1 or 2 OPNFV versions, the feature should be adopted by most 
of/all the installers in generic scenario(s)

it will be useful for certification (and we are back to an old thread...
when we say we cannot certify a feature that is not supported by 80% of the 
scenarios we are releasing...today that is the case of lots of features that 
are installer dependant)

/Morgan

>
> -Tapio
>
>
> On 01/18/2017 11:38 AM, Jose Lausuch wrote:
>> Me neither. If that were the case, that feature Was tested only in 
>> Fuel during Colorado.
>>
>> Let's follow up on Friday.
>>
>> - Jose -
>>
>>
>> -Original Message-
>> From: opnfv-tech-discuss-boun...@lists.opnfv.org
>> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 
>> Christopher Price
>> Sent: Wednesday, January 18, 2017 9:32 AM
>> To: Tapio Tallgren; opnfv-tech-discuss@lists.opnfv.org
>> Subject: Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is 
>> completed fully in C release
>>
>> Hmm,
>>
>> I was not aware that “all installers must support” a feature for 
>> there to be a dovetail suite to validate it.
>> Maybe we should review the “qualification criteria” again on Friday’s 
>> call.
>>
>> Completely agree that we need to do this in Gerrit.
>>
>> / chris
>>
>> On 2017-01-18, 08:59, "Tapio Tallgren"
>> > tapio.tallg...@nokia.com> wrote:
>>
>>  On 01/18/2017 12:53 AM, Dave Neary wrote:
>>  > Hi Hongbo, Jose,
>>  >
>>  > As I was saying on the Dovetail calls, I have some concerns 
>> about moving
>>  > tests into the Dovetail test suite too early.
>>  >
>>  > In the Dovetail test requirements, we have:
>>  >
>>  > "* Test cases must pass on OPNFV reference deployments
>>  >* Tests must not require a specific NFVi platform
>> composition or
>>  > installation tool
>>  >* Tests must not require unmerged patches to the relevant
>> upstream
>>  > projects"
>>  >
>>  > And in the CVP requirements, we have the following section:
>>  >
>>  > "The overall CVP

[opnfv-tech-discuss] [IPv6] Project Meeting #55

2017-01-18 Thread HU, BIN

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="HU, BIN":MAILTO:bh5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:https://global.gotomeeting.com/join/819733085\n+
 1 (312) 757-3126 / Access Code: 819-733-085\n\nPlease NOTE the NEW GOTOMEE
 TING INFORMATION.\n\nHello team\,\n\nHere is the information of our IPv6 p
 roject meeting #55 to check the status update. Sorry that I have to move i
 t around and start 30 minutes earlier than our regular time to accommodate
  my another appointment. Because our bridge is for even hours\, it shouldn
 ’t conflict with other meetings at 7am-8am which use bridge for odd hour
 s.\n\nWe will focus on discussing gap analysis related topics for Danube r
 elease.\n\n-   When: Friday 7:30-8:15 PST (15:30-16:15 UTC) January 20
 th\, 2017\no   Your local time\n-   Bridge: GoT
 o Meeting:\no   Web Conferencing: https://global.gotomeeting.com/join/
 819733085\no   Dial-in only:\n•   United States (Long distance):
  +1 (312) 757-3126 / Access Code: 819-733-085\n•   More phone number
 s: https://global.gotomeeting.com/819733085/numbersdisplay.html\n-   M
 eeting page: https://wiki.opnfv.org/display/meetings/ipv6 for agenda and m
 inutes\n-   Project wiki page: https://wiki.opnfv.org/display/ipv6/IPv
 6+Home for all information and resources related to IPv6 project\n\nLook f
 orward to working with everyone.\n\nThanks\nBin\n\n
SUMMARY;LANGUAGE=en-US:[IPv6] Project Meeting #55
DTSTART;TZID=Pacific Standard Time:20170120T073000
DTEND;TZID=Pacific Standard Time:20170120T081500
UID:04008200E00074C5B7101A82E00860C58C49B471D201000
 010007669A75DC0B14849AFF250FF6424F0E3
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170119T015912Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US: +1 (312) 757-3126 / Access Code: 819-733-085
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-17688607
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] New OPNFV Website Now Live

2017-01-18 Thread Brandon Wick

OPNFV Technical Community,

The new OPNFV website has arrived! You can access it here:
*https://www.opnfv.org/
*

We've added a new section for end users, added new content from our vibrant
community, streamlined the navigation, and gave it a fresh look. I
encourage you to check it out and see what's new. If you have any
suggestions, or find any issues, please email me directly. Thanks!

Best,

Brandon Wick
OPNFV Head of Marketing, The Linux Foundation
Mobile: +1.917.282.0960  Skype: wick.brandon
Email / Google Talk: bw...@linuxfoundation.org
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [Bottlenecks] Bottlenecks weekly meeting 1-19 (1:00-2:00 UTC, Thursday, 9:00-10:00 Beijing Time, Thursday, PDT 18:00-19:00 Wednesday )

2017-01-18 Thread Yuyang (Gabriel)

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Yuyang (Gabriel):MAILTO:gabriel.yuy...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Tianhongbo
 :MAILTO:hongbo.tianhon...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lijun (Mat
 thew):MAILTO:matthew.li...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=liangqi (D
 ):MAILTO:liang...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Liyiting:M
 AILTO:liyit...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='mrebellon
 @sandvine.com':MAILTO:mrebel...@sandvine.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wangyaogua
 ng (A):MAILTO:sunshine.w...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='michael.a
 .ly...@intel.com':MAILTO:michael.a.ly...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=limingjian
 g:MAILTO:limingji...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=邓灵莉/
 Lingli Deng:MAILTO:denglin...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='qwyang012
 6...@gmail.com':MAILTO:qwyang0...@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Prakash Ra
 mchandran:MAILTO:prakash.ramchand...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=zh-CN:时间: 2017年1月19日 9:00-10:00。 (UTC+08:0
 0)北京，重庆，香港特别行政区，乌鲁木齐\n位置: https://
 global.gotomeeting.com/join/882532573\n\n*~*~*~*~*~*~*~*~*~*\n\nHi\,\n\nTh
 e Bottlenecks weekly meeting will be held at 1:00-2:00 UTC\, Thursday\, 9:
 00-10:00 Beijing Time\, Thursday\, PDT 18:00-19:00 Wednesday.\nWelcome to 
 join our discussion. Details of this meeting are shown below.\n\n\nAgenda:
 \n  1.  Bottlenecks D Rel. Discussion\n  2.  Stress testing from Testperf 
 meeting\n  3.  Action Item Review\n\nMeeting Resources\n\nPlease join the 
 meeting from your computer\, tablet or smartphone.\nhttps://global.gotomee
 ting.com/join/882532573\n\nYou can also dial in using your phone.\nUnited 
 States (Toll-free): 1 877 309 2070\nUnited States : +1 (312) 757-3119\n\n\
 nAccess Code: 882-532-573\n\n\nBest\,\nYang\n
SUMMARY;LANGUAGE=zh-CN:[Bottlenecks] Bottlenecks weekly meeting 1-19 (1:00-
 2:00 UTC\, Thursday\, 9:00-10:00 Beijing Time\, Thursday\, PDT 18:00-19:00
  Wednesday )
DTSTART;TZID=China Standard Time:20170119T09
DTEND;TZID=China Standard Time:20170119T10
UID:04008200E00074C5B7101A82E00879DD77E4EF71D201000
 0100065148302B84C364A88CE13D95BCCBC0F
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170119T010349Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=zh-CN:https://global.gotomeeting.com/join/882532573
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115082873
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:P
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

2017-01-18 Thread HU, BIN

Thanks for background information.

I think the challenge is how to quantify "widely available". 50% or less is 
certainly not "widely available". Maybe 80%? 90%? If 100% is excessive. Then it 
tranlates to 4 installers (given current 5 in total), and relevant combinations.

Thanks
Bin
-Original Message-
From: Dave Neary [mailto:dne...@redhat.com] 
Sent: Wednesday, January 18, 2017 12:41 PM
To: HU, BIN ; Christopher Price ; Tapio 
Tallgren ; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed 
fully in C release

Hi,

For my part, my understanding of this when Chris, Hongbo and myself wrote it in 
New Hampshire, our intention was to communicate that a feature was not 
elligible if it was only done for one specific stack or one installer - this 
was our best guess at communicating "widely available". I think all installers 
and all possible stack combinations would be excessive.

Thanks,
Dave.

On 01/18/2017 03:37 PM, HU, BIN wrote:
> Maybe wordsmithing, but I think "2 installers  and 2 SDN controllers" still 
> means "specific". It is just slightly loosened from "specific one" to 
> "specific two".
> 
> I believe that the essence of, and also logically, "must not require a 
> specific ..." really means "any currently available" in OPNFV.
> 
> Thanks
> Bin
> 
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org 
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dave 
> Neary
> Sent: Wednesday, January 18, 2017 12:20 PM
> To: Christopher Price ; Tapio Tallgren 
> ; opnfv-tech-discuss@lists.opnfv.org
> Subject: Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is 
> completed fully in C release
> 
> Hi,
> 
> On 01/18/2017 03:31 AM, Christopher Price wrote:
>> I was not aware that “all installers must support” a feature for there to be 
>> a dovetail suite to validate it.  
>> Maybe we should review the “qualification criteria” again on Friday’s call.
> 
> The wording we came up with in the test requirements was:
> * Tests must not require a specific NFVi platform composition or 
> installation tool
> 
> In other words, not all, but at least 2 installers and 2 SDN controllers 
> should support the feature.
> 
> Dave.
> 
>> Completely agree that we need to do this in Gerrit.
>>
>> / chris
>>
>> On 2017-01-18, 08:59, "Tapio Tallgren" 
>> > tapio.tallg...@nokia.com> wrote:
>>
>> On 01/18/2017 12:53 AM, Dave Neary wrote:
>> > Hi Hongbo, Jose,
>> >
>> > As I was saying on the Dovetail calls, I have some concerns about 
>> moving
>> > tests into the Dovetail test suite too early.
>> >
>> > In the Dovetail test requirements, we have:
>> >
>> > "* Test cases must pass on OPNFV reference deployments
>> >* Tests must not require a specific NFVi platform composition or
>> > installation tool
>> >* Tests must not require unmerged patches to the relevant upstream
>> > projects"
>> >
>> > And in the CVP requirements, we have the following section:
>> >
>> > "The overall CVP compliance verification scope tied to an OPNFV release
>> > is determined by the Committee. The OPNFV TSC defines and maintains the
>> > compliance verification procedures and associated tools. The scope is
>> > constrained to features, capabilities, components, and interfaces
>> > included in an OPNFV release that are generally available in the
>> > industry (e.g., through adoption by an upstream community)."
>> >
>> >
>> > I wonder if this functionality is sufficiently widely adopted in
>> > commercial NFVi and VIM solutions to pass this bar.
>> >
>> > Thanks,
>> > Dave.
>> 
>> I have no opinion about L3VPN as such, but I read this to mean that the 
>> code should be part of a released upstream projects and that OPNFV 
>> installers should all support it.
>> 
>> What would be the best way to discuss these? Currently, the test cases 
>> are on a wiki page which makes it a little difficult to comment them. 
>> Would it make sense to copy the whole test areas and test cases wiki 
>> page to an Etherpad? Or should the whole page be put to gerrit for 
>> commenting?
>> 
>> -Tapio
>> 
>> ___
>> opnfv-tech-discuss mailing list
>> opnfv-tech-discuss@lists.opnfv.org
>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>> 
>>
>>
>> ___
>> opnfv-tech-discuss mailing list
>> opnfv-tech-discuss@lists.opnfv.org
>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>>
> 
> --
> Dave Neary - NFV/SDN Community Strategy Open Source and Standards, Red 
> Hat -

Re: [opnfv-tech-discuss] Models Weekly Meeting A

2017-01-18 Thread Beierl, Mark

Hello, Bryan.

I unfortunately was only able to attend a portion of this meeting.  Was there a 
recording of what GigaSpaces presented, or is the Google Doc the only thing 
that can be reviewed at this time?

Regards,
Mark

Mark Beierl
Advisory Solutions Architect
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

On Jan 16, 2017, at 12:14, SULLIVAN, BRYAN L 
> wrote:

Notes from today:

2017-Jan-16 Models Project Meeting #22
Attendees:

  *   Bryan Sullivan, AT
  *   Aimee Ukasick, AT
  *   Amir Levy, Gigaspaces
  *   Arthur Berezin, GigaSpaces
  *   Christopher Price, Ericsson
  *   Alok Gupta, AT
  *   Krzysztof Frujacz, Gigaspaces
  *   Larry Lamers, VMWare
  *   Pasi Vaananen, Stratus
  *   Trinath Somanchi, NXP

Minutes:

  *   Cloudify/Aria discussion

  *   Arthur provided an overview of the Aria project (Apache Foundation)
  *   
https://docs.google.com/presentation/d/1PemGjFnEh-5QJUy_D1Mz4rHEL7kxdGD9XMc4RQsr6Zo/edit?usp=sharing
  *   Plan to support all Cloudify plugins

  *   Execution plugin is being worked on first (SSH and execution of scripts 
as "implementation" hooks)

  *   How does it manage stateful as well as static blueprint data

  *   Both need to be auditable (give me the current state in some easily 
usable/comparable form, e.g. JSON)
  *   Stateful data needs to be reliably stored - is this a database sync issue 
only?

  *   How does it support update of the deployed instances, e.g. to add a new 
node in the graph or update a node
  *   Plans beyond CLI and Python libraries

  *   The vision discussed at the ODL Summit was for a RESTful API thru which 
we can onboard blueprints, deploy, and interact with the deployed instances as 
objects (e.g. JSON-based), for a completely modeled/object-based abstraction 
layer

  *   Basic VDU properties supported?

  *   Intend to support TOSCA profile CSD03 (all nodes): current YAML 
implementation of the schema
  *   
https://github.com/apache/incubator-ariatosca/tree/8ee1470e314cfd3cac5cc4e17c80ea6ab67bad8a/extensions/aria_extension_tosca/profiles/tosca-simple-nfv-1.0

  *   Discussions with Tacker on reuse?

  *   Some time ago, need to refresh the discussion

  *   Bryan's goal for Danube is to create an experimental test using Aria as a 
VNFM for the basic hello-world level test ala 
vHello_Tacker.sh and 
the related blueprint 
tosca-vnfd-hello-world-tacker

  *   As soon as there is a stable Aria version that can be used to develop 
such a starter test, we will work on it.

Thanks,
Bryan Sullivan | AT

_
From: SULLIVAN, BRYAN L
Sent: Monday, January 16, 2017 7:42 AM
To: 
'opnfv-tech-discuss@lists.opnfv.org' 
>
Subject: RE: Models Weekly Meeting A

Hi all,

Agenda for today is that the Gigaspaces team will give us an update on Cloudify 
and Aria. That will help us get those tools better integrated into the Models 
tests etc.

Thanks,
Bryan Sullivan | AT

-Original Appointment-
From: SULLIVAN, BRYAN L
Sent: Monday, July 18, 2016 10:12 AM
To: 
'opnfv-tech-discuss@lists.opnfv.org'
Cc: 'Dan Westerberg'; 'Tal Barenboim'; 'Vul, Alex'; 'Henry Fourie'; 'Andrew 
Veitch'; 'a...@gigaspaces.com'; GUPTA, ALOK; 'Ola 
Liljedahl'; MORTON JR., AL; 'Ulas Kozat'; 'David Suarez Fuentes'; 'Mario 
Torrecillas Rodriguez'; 'Ramia, Kannan Babu'; 'Sen, Prodip'; 'Kuppuswamy, 
Prabu'; DRUTA, DAN; 'Gabor Halász'; 'Seiler, Glenn'; 'S, Deepak'; 'Lawrence 
Lamers'; 'ramki_krish...@dell.com'; 'Vandris, 
Steve'; 'yaohelan'; 'Canio Cillis'; Shobhan AyyadevaraSesha (sayyadev); Trinath 
Somanchi; Zhangyi (ZHANG YI, SCC); Ahmed Elbornou (amaged); Randy Levensalor; 
Alan McNamee; Tomasini, Lorenzo; Daniel Smith; Edna Ganon; Reid Cheng 
(xincheng); Pauls, Michael; Malla, Malathi; Pierre Lynch
Subject: Models Weekly Meeting A
When: Monday, January 16, 2017 4:00 PM-5:00 PM (UTC) Coordinated Universal Time.
Where: https://global.gotomeeting.com/join/865421325

Updating this invite to be UTC-based as intended on the wiki, so we limit 
confusion during the seasonal change.

https://wiki.opnfv.org/display/models/Models+Meetings
IRC: #opnfv-models, e.g.  
https://www.irccloud.com/#!/ircs://irc.freenode.net:6697/%23opnfv-models

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

2017-01-18 Thread Dave Neary

Hi,

For my part, my understanding of this when Chris, Hongbo and myself
wrote it in New Hampshire, our intention was to communicate that a
feature was not elligible if it was only done for one specific stack or
one installer - this was our best guess at communicating "widely
available". I think all installers and all possible stack combinations
would be excessive.

Thanks,
Dave.

On 01/18/2017 03:37 PM, HU, BIN wrote:
> Maybe wordsmithing, but I think "2 installers  and 2 SDN controllers" still 
> means "specific". It is just slightly loosened from "specific one" to 
> "specific two".
> 
> I believe that the essence of, and also logically, "must not require a 
> specific ..." really means "any currently available" in OPNFV.
> 
> Thanks
> Bin
> 
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org 
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dave Neary
> Sent: Wednesday, January 18, 2017 12:20 PM
> To: Christopher Price ; Tapio Tallgren 
> ; opnfv-tech-discuss@lists.opnfv.org
> Subject: Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed 
> fully in C release
> 
> Hi,
> 
> On 01/18/2017 03:31 AM, Christopher Price wrote:
>> I was not aware that “all installers must support” a feature for there to be 
>> a dovetail suite to validate it.  
>> Maybe we should review the “qualification criteria” again on Friday’s call.
> 
> The wording we came up with in the test requirements was:
> * Tests must not require a specific NFVi platform composition or installation 
> tool
> 
> In other words, not all, but at least 2 installers and 2 SDN controllers 
> should support the feature.
> 
> Dave.
> 
>> Completely agree that we need to do this in Gerrit.
>>
>> / chris
>>
>> On 2017-01-18, 08:59, "Tapio Tallgren" 
>> > tapio.tallg...@nokia.com> wrote:
>>
>> On 01/18/2017 12:53 AM, Dave Neary wrote:
>> > Hi Hongbo, Jose,
>> >
>> > As I was saying on the Dovetail calls, I have some concerns about 
>> moving
>> > tests into the Dovetail test suite too early.
>> >
>> > In the Dovetail test requirements, we have:
>> >
>> > "* Test cases must pass on OPNFV reference deployments
>> >* Tests must not require a specific NFVi platform composition or
>> > installation tool
>> >* Tests must not require unmerged patches to the relevant upstream
>> > projects"
>> >
>> > And in the CVP requirements, we have the following section:
>> >
>> > "The overall CVP compliance verification scope tied to an OPNFV release
>> > is determined by the Committee. The OPNFV TSC defines and maintains the
>> > compliance verification procedures and associated tools. The scope is
>> > constrained to features, capabilities, components, and interfaces
>> > included in an OPNFV release that are generally available in the
>> > industry (e.g., through adoption by an upstream community)."
>> >
>> >
>> > I wonder if this functionality is sufficiently widely adopted in
>> > commercial NFVi and VIM solutions to pass this bar.
>> >
>> > Thanks,
>> > Dave.
>> 
>> I have no opinion about L3VPN as such, but I read this to mean that the 
>> code should be part of a released upstream projects and that OPNFV 
>> installers should all support it.
>> 
>> What would be the best way to discuss these? Currently, the test cases 
>> are on a wiki page which makes it a little difficult to comment them. 
>> Would it make sense to copy the whole test areas and test cases wiki 
>> page to an Etherpad? Or should the whole page be put to gerrit for 
>> commenting?
>> 
>> -Tapio
>> 
>> ___
>> opnfv-tech-discuss mailing list
>> opnfv-tech-discuss@lists.opnfv.org
>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>> 
>>
>>
>> ___
>> opnfv-tech-discuss mailing list
>> opnfv-tech-discuss@lists.opnfv.org
>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>>
> 
> --
> Dave Neary - NFV/SDN Community Strategy
> Open Source and Standards, Red Hat - http://community.redhat.com
> Ph: +1-978-399-2182 / Cell: +1-978-799-3338 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> 

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

2017-01-18 Thread HU, BIN

Maybe wordsmithing, but I think "2 installers  and 2 SDN controllers" still 
means "specific". It is just slightly loosened from "specific one" to "specific 
two".

I believe that the essence of, and also logically, "must not require a specific 
..." really means "any currently available" in OPNFV.

Thanks
Bin

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dave Neary
Sent: Wednesday, January 18, 2017 12:20 PM
To: Christopher Price ; Tapio Tallgren 
; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed 
fully in C release

Hi,

On 01/18/2017 03:31 AM, Christopher Price wrote:
> I was not aware that “all installers must support” a feature for there to be 
> a dovetail suite to validate it.  
> Maybe we should review the “qualification criteria” again on Friday’s call.

The wording we came up with in the test requirements was:
* Tests must not require a specific NFVi platform composition or installation 
tool

In other words, not all, but at least 2 installers and 2 SDN controllers should 
support the feature.

Dave.

> Completely agree that we need to do this in Gerrit.
> 
> / chris
> 
> On 2017-01-18, 08:59, "Tapio Tallgren" 
>  tapio.tallg...@nokia.com> wrote:
> 
> On 01/18/2017 12:53 AM, Dave Neary wrote:
> > Hi Hongbo, Jose,
> >
> > As I was saying on the Dovetail calls, I have some concerns about moving
> > tests into the Dovetail test suite too early.
> >
> > In the Dovetail test requirements, we have:
> >
> > "* Test cases must pass on OPNFV reference deployments
> >* Tests must not require a specific NFVi platform composition or
> > installation tool
> >* Tests must not require unmerged patches to the relevant upstream
> > projects"
> >
> > And in the CVP requirements, we have the following section:
> >
> > "The overall CVP compliance verification scope tied to an OPNFV release
> > is determined by the Committee. The OPNFV TSC defines and maintains the
> > compliance verification procedures and associated tools. The scope is
> > constrained to features, capabilities, components, and interfaces
> > included in an OPNFV release that are generally available in the
> > industry (e.g., through adoption by an upstream community)."
> >
> >
> > I wonder if this functionality is sufficiently widely adopted in
> > commercial NFVi and VIM solutions to pass this bar.
> >
> > Thanks,
> > Dave.
> 
> I have no opinion about L3VPN as such, but I read this to mean that the 
> code should be part of a released upstream projects and that OPNFV 
> installers should all support it.
> 
> What would be the best way to discuss these? Currently, the test cases 
> are on a wiki page which makes it a little difficult to comment them. 
> Would it make sense to copy the whole test areas and test cases wiki 
> page to an Etherpad? Or should the whole page be put to gerrit for 
> commenting?
> 
> -Tapio
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> 
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> 

--
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338 
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Canceled Event: OpenDaylight - OPNFV community sync meeting @ Thu Jan 19, 2017 10am - 11am (EST) (opnfv-tech-discuss@lists.opnfv.org)

2017-01-18 Thread dneary

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/New_York:20170119T10
DTEND;TZID=America/New_York:20170119T11
DTSTAMP:20170118T150733Z
ORGANIZER;CN=Dave Neary:mailto:dne...@redhat.com
UID:ded30137-1257-45b4-ab14-97b4dedb69db
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ar
 obin...@advaoptical.com;X-NUM-GUESTS=0:mailto:arobin...@advaoptical.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=mc
 3...@att.com;X-NUM-GUESTS=0:mailto:mc3...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=sh
 a...@brocade.com;X-NUM-GUESTS=0:mailto:sha...@brocade.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=tn
 ad...@brocade.com;X-NUM-GUESTS=0:mailto:tnad...@brocade.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=bh
 5...@att.com;X-NUM-GUESTS=0:mailto:bh5...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=pa
 parao.palacha...@us.fujitsu.com;X-NUM-GUESTS=0:mailto:paparao.palacharla@us
 .fujitsu.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=kk
 ous...@brocade.com;X-NUM-GUESTS=0:mailto:kkous...@brocade.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ta
 pio.tallg...@nokia.com;X-NUM-GUESTS=0:mailto:tapio.tallg...@nokia.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=co
 ntroller-...@lists.opendaylight.org;X-NUM-GUESTS=0:mailto:controller-dev@li
 sts.opendaylight.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=gr
 oupbasedpolicy-...@lists.opendaylight.org;X-NUM-GUESTS=0:mailto:groupbasedp
 olicy-...@lists.opendaylight.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=fz
 dar...@redhat.com;X-NUM-GUESTS=0:mailto:fzdar...@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ma
 rc.rapop...@ericsson.com;X-NUM-GUESTS=0:mailto:marc.rapop...@ericsson.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ro
 va...@cisco.com;X-NUM-GUESTS=0:mailto:rova...@cisco.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=op
 nfv-tech-disc...@lists.opnfv.org;X-NUM-GUESTS=0:mailto:opnfv-tech-discuss@l
 ists.opnfv.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=Ke
 ith Burns;X-NUM-GUESTS=0:mailto:alaga...@noironetworks.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=wa
 ngjin...@chinamobile.com;X-NUM-GUESTS=0:mailto:wangjin...@chinamobile.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ja
 mes.luhr...@hp.com;X-NUM-GUESTS=0:mailto:james.luhr...@hp.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ya
 fit.ha...@ecitele.com;X-NUM-GUESTS=0:mailto:yafit.ha...@ecitele.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=af
 red...@redhat.com;X-NUM-GUESTS=0:mailto:afred...@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=gm
 ain...@contextream.com;X-NUM-GUESTS=0:mailto:gmain...@contextream.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ja
 ck.pugaczew...@centurylink.com;X-NUM-GUESTS=0:mailto:jack.pugaczewski@centu
 rylink.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=vz
 elc...@cisco.com;X-NUM-GUESTS=0:mailto:vzelc...@cisco.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=dk
 ute...@cisco.com;X-NUM-GUESTS=0:mailto:dkute...@cisco.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ne
 utron-...@lists.opendaylight.org;X-NUM-GUESTS=0:mailto:neutron-...@lists.op
 endaylight.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=jo
 hn.b...@hp.com;X-NUM-GUESTS=0:mailto:john.b...@hp.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=yu
 nchao...@huawei.com;X-NUM-GUESTS=0:mailto:yunchao...@huawei.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=mi
 chael.a.ly...@intel.com;X-NUM-GUESTS=0:mailto:michael.a.ly...@intel.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=th
 inri...@vmware.com;X-NUM-GUESTS=0:mailto:thinri...@vmware.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=di
 rk.kutsc...@neclab.eu;X-NUM-GUESTS=0:mailto:dirk.kutsc...@neclab.eu

[opnfv-tech-discuss] [releng] Nomination of Markos Chandras as committer to Releng

2017-01-18 Thread Fatih Degirmenci

Hi Releng Committers,

I would like to nominate Markos Chandras as committer to Releng.

Markos has been one of the main contributors to Cross Community CI activities 
we have been working on in OPNFV. 
His contributions include but not limited to introducing SuSe support to 
openstack/bifrost. [1] Thanks to his past (and future) contributions, Cross 
Community CI will support SuSe on top of Ubuntu and Centos. Apart from making 
code contributions to upstream, he has been in close contact with OpenStack 
Infra people to bring OPNFV and OpenStack Infra closer, making OPNFV cummunity 
visible there for Infra parts as well. 

On top of contributing to OpenStack directly in upstream, he also made 
contributions to OPNFV Releng. [2] One of the contributions I want to highlight 
is that he stabilized/improved the jobs we use for running patchset 
verification against openstack/bifrost patches upstream, making it possible for 
us to start discussions with Bifrost PTL to get the voting rights for OPNFV for 
openstack/bifrost which is a great first step towards future. [2]

Please cast your vote on Gerrit: https://gerrit.opnfv.org/gerrit/#/c/27167/

I'll close the vote on 2017-01-2017.

[1] https://review.openstack.org/#/q/owner:mchandras%2540suse.de
[2] https://gerrit.opnfv.org/gerrit/#/q/owner:%22Markos+Chandras%22

/Fatih

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

2017-01-18 Thread morgan.richomme

Le 18/01/2017 à 11:07, Tapio Tallgren a écrit :
> Good topic, I also felt that the criteria were not too clear.
>
> My interpretation was that if we are testing a feature that should be
> in all OPNFV platforms and which is generally available in the
> industry, and which does not require a specific installation tool,
> then many OPNFV installers would support it. Perhaps even all of them.
part of the feature alignment for "mature" features evoked in the
discussion on priorities
not realistic for Danube, but could be for E and somehow linked to the
discussion on scenario refactoring
it is a richness to have several installers
until a feature is not mature, it makes fully sense to focus on only 1
installer in specific scenario(s)
but when the integration is done and available since 1 or 2 OPNFV
versions, the feature should be adopted by most of/all the installers in
generic scenario(s)

it will be useful for certification (and we are back to an old thread...
when we say we cannot certify a feature that is not supported by 80% of
the scenarios we are releasing...today that is the case of lots of
features that are installer dependant)

/Morgan

>
> -Tapio
>
>
> On 01/18/2017 11:38 AM, Jose Lausuch wrote:
>> Me neither. If that were the case, that feature Was tested only in
>> Fuel during Colorado.
>>
>> Let's follow up on Friday.
>>
>> - Jose -
>>
>>
>> -Original Message-
>> From: opnfv-tech-discuss-boun...@lists.opnfv.org
>> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of
>> Christopher Price
>> Sent: Wednesday, January 18, 2017 9:32 AM
>> To: Tapio Tallgren; opnfv-tech-discuss@lists.opnfv.org
>> Subject: Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is
>> completed fully in C release
>>
>> Hmm,
>>
>> I was not aware that “all installers must support” a feature for
>> there to be a dovetail suite to validate it.
>> Maybe we should review the “qualification criteria” again on Friday’s
>> call.
>>
>> Completely agree that we need to do this in Gerrit.
>>
>> / chris
>>
>> On 2017-01-18, 08:59, "Tapio Tallgren"
>> > tapio.tallg...@nokia.com> wrote:
>>
>>  On 01/18/2017 12:53 AM, Dave Neary wrote:
>>  > Hi Hongbo, Jose,
>>  >
>>  > As I was saying on the Dovetail calls, I have some concerns
>> about moving
>>  > tests into the Dovetail test suite too early.
>>  >
>>  > In the Dovetail test requirements, we have:
>>  >
>>  > "* Test cases must pass on OPNFV reference deployments
>>  >* Tests must not require a specific NFVi platform
>> composition or
>>  > installation tool
>>  >* Tests must not require unmerged patches to the relevant
>> upstream
>>  > projects"
>>  >
>>  > And in the CVP requirements, we have the following section:
>>  >
>>  > "The overall CVP compliance verification scope tied to an
>> OPNFV release
>>  > is determined by the Committee. The OPNFV TSC defines and
>> maintains the
>>  > compliance verification procedures and associated tools. The
>> scope is
>>  > constrained to features, capabilities, components, and interfaces
>>  > included in an OPNFV release that are generally available in the
>>  > industry (e.g., through adoption by an upstream community)."
>>  >
>>  >
>>  > I wonder if this functionality is sufficiently widely adopted in
>>  > commercial NFVi and VIM solutions to pass this bar.
>>  >
>>  > Thanks,
>>  > Dave.
>>   I have no opinion about L3VPN as such, but I read this to
>> mean that the
>>  code should be part of a released upstream projects and that OPNFV
>>  installers should all support it.
>>   What would be the best way to discuss these? Currently, the
>> test cases
>>  are on a wiki page which makes it a little difficult to comment
>> them.
>>  Would it make sense to copy the whole test areas and test cases
>> wiki
>>  page to an Etherpad? Or should the whole page be put to gerrit for
>>  commenting?
>>   -Tapio
>>   ___
>>  opnfv-tech-discuss mailing list
>>  opnfv-tech-discuss@lists.opnfv.org
>>  https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>> 
>>
>> ___
>> opnfv-tech-discuss mailing list
>> opnfv-tech-discuss@lists.opnfv.org
>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


-- 
Morgan Richomme
Orange/ IMT/ OLN/ CNC/ NCA/ SINA 

Network architect for innovative services
Future of the Network community member
Open source Orange community manager


tel. +33 (0) 296 072 106
mob. +33 (0) 637 753 326
morgan.richo...@orange.com

[opnfv-tech-discuss] [ovsnfv] Weekly Meeting

2017-01-18 Thread O Mahony, Billy

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:GMT Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T01
TZOFFSETFROM:+
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="O Mahony, Billy":MAILTO:billy.o.mah...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='opnfv-tec
 h-disc...@lists.opnfv.org':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Daniel Sm
 ith':MAILTO:daniel.sm...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Hesham El
 Bakoury':MAILTO:hesham.elbako...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Paul-Andr
 e Raymond':MAILTO:paul-andre.raym...@nexius.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Skip Boot
 h (ebooth)':MAILTO:ebo...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Coppola, S
 imona":MAILTO:simona.copp...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Gabor Hal
 ász':MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Winn, Sea
 n'":MAILTO:sean.w...@emc.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Matt Gill
 ies (mgillies)':MAILTO:mgill...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tim Dalto
 n':MAILTO:t.dal...@networkfx.net
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Alan McNa
 mee':MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Sen, Prod
 ip'":MAILTO:prodip@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Agarwal, 
 Anshu'":MAILTO:anshu.agar...@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Phil Chen
 ':MAILTO:phil.c...@citrix.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Nicolas B
 OUTHORS':MAILTO:nicolas.bouth...@qosmos.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='forerunne
 r...@etri.re.kr':MAILTO:forerun...@etri.re.kr
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'DRUTA, DA
 N'":MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='jamil.cha
 w...@orange.com':MAILTO:jamil.cha...@orange.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tal Baren
 boim':MAILTO:t...@amdocs.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Bharat Bh
 ushan':MAILTO:bharat.bhus...@nxp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Venkatesan
 , Venky":MAILTO:venky.venkate...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'CHIOSI, M
 ARGARET T'":MAILTO:mc3...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Radhakris
 hnan Govindan':MAILTO:gradh...@sandvine.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Palacharl
 a, Paparao'":MAILTO:paparao.palacha...@us.fujitsu.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Lawrence 
 Lamers':MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Duarte Car
 doso, Igor":MAILTO:igor.duarte.card...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='guo bingl
 i':MAILTO:gblal...@hotmail.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Levine, I
 dit'":MAILTO:idit.lev...@emc.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Scott Man
 sfield':MAILTO:scott.mansfi...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Thomas F.
  Herbert':MAILTO:thomasfherb...@gmail.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Henry Fou
 rie':MAILTO:louis.fou...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Mario Tor
 recillas Rodriguez':MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Damena, M
 ichael Melesse'":MAILTO:michael.mel.dam...@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Tahhan, Ma
 ryam":MAILTO:maryam.tah...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Huangkun 
 (Gareth, Cloud OS)'":MAILTO:gareth.hu...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ryan Davi
 s':MAILTO:ryan.da...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Sun, Jimin
 g":MAILTO:jiming@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ian Wells
  (iawells)':MAILTO:iawe...@cisco.com

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

2017-01-18 Thread Tapio Tallgren

Good topic, I also felt that the criteria were not too clear.

My interpretation was that if we are testing a feature that should be in 
all OPNFV platforms and which is generally available in the industry, 
and which does not require a specific installation tool, then many OPNFV 
installers would support it. Perhaps even all of them.

-Tapio

On 01/18/2017 11:38 AM, Jose Lausuch wrote:

Me neither. If that were the case, that feature Was tested only in Fuel during 
Colorado.

Let's follow up on Friday.

- Jose -

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Christopher 
Price
Sent: Wednesday, January 18, 2017 9:32 AM
To: Tapio Tallgren; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed 
fully in C release

Hmm,

I was not aware that “all installers must support” a feature for there to be a 
dovetail suite to validate it.
Maybe we should review the “qualification criteria” again on Friday’s call.

Completely agree that we need to do this in Gerrit.

/ chris

On 2017-01-18, 08:59, "Tapio Tallgren"  wrote:

 On 01/18/2017 12:53 AM, Dave Neary wrote:
 > Hi Hongbo, Jose,
 >
 > As I was saying on the Dovetail calls, I have some concerns about moving
 > tests into the Dovetail test suite too early.
 >
 > In the Dovetail test requirements, we have:
 >
 > "* Test cases must pass on OPNFV reference deployments
 >* Tests must not require a specific NFVi platform composition or
 > installation tool
 >* Tests must not require unmerged patches to the relevant upstream
 > projects"
 >
 > And in the CVP requirements, we have the following section:
 >
 > "The overall CVP compliance verification scope tied to an OPNFV release
 > is determined by the Committee. The OPNFV TSC defines and maintains the
 > compliance verification procedures and associated tools. The scope is
 > constrained to features, capabilities, components, and interfaces
 > included in an OPNFV release that are generally available in the
 > industry (e.g., through adoption by an upstream community)."
 >
 >
 > I wonder if this functionality is sufficiently widely adopted in
 > commercial NFVi and VIM solutions to pass this bar.
 >
 > Thanks,
 > Dave.

 I have no opinion about L3VPN as such, but I read this to mean that the

 code should be part of a released upstream projects and that OPNFV
 installers should all support it.

 What would be the best way to discuss these? Currently, the test cases

 are on a wiki page which makes it a little difficult to comment them.
 Would it make sense to copy the whole test areas and test cases wiki
 page to an Etherpad? Or should the whole page be put to gerrit for
 commenting?

 -Tapio

 ___

 opnfv-tech-discuss mailing list
 opnfv-tech-discuss@lists.opnfv.org
 https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]Weekly meeting of Jan.19

2017-01-18 Thread joehuang

Hello, team,

Agenda of Jan.19 2017

* Multisite deployment environment.
* Kingbird feature development.
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

2017-01-18 Thread Christopher Price

Hmm,

I was not aware that “all installers must support” a feature for there to be a 
dovetail suite to validate it.  
Maybe we should review the “qualification criteria” again on Friday’s call.

Completely agree that we need to do this in Gerrit.

/ chris

On 2017-01-18, 08:59, "Tapio Tallgren" 
 wrote:

On 01/18/2017 12:53 AM, Dave Neary wrote:
> Hi Hongbo, Jose,
>
> As I was saying on the Dovetail calls, I have some concerns about moving
> tests into the Dovetail test suite too early.
>
> In the Dovetail test requirements, we have:
>
> "* Test cases must pass on OPNFV reference deployments
>* Tests must not require a specific NFVi platform composition or
> installation tool
>* Tests must not require unmerged patches to the relevant upstream
> projects"
>
> And in the CVP requirements, we have the following section:
>
> "The overall CVP compliance verification scope tied to an OPNFV release
> is determined by the Committee. The OPNFV TSC defines and maintains the
> compliance verification procedures and associated tools. The scope is
> constrained to features, capabilities, components, and interfaces
> included in an OPNFV release that are generally available in the
> industry (e.g., through adoption by an upstream community)."
>
>
> I wonder if this functionality is sufficiently widely adopted in
> commercial NFVi and VIM solutions to pass this bar.
>
> Thanks,
> Dave.

I have no opinion about L3VPN as such, but I read this to mean that the 
code should be part of a released upstream projects and that OPNFV 
installers should all support it.

What would be the best way to discuss these? Currently, the test cases 
are on a wiki page which makes it a little difficult to comment them. 
Would it make sense to copy the whole test areas and test cases wiki 
page to an Etherpad? Or should the whole page be put to gerrit for 
commenting?

-Tapio

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [dovetail]dovetal weekly meeting 1/20

2017-01-18 Thread Tianhongbo

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Tianhongbo:MAILTO:hongbo.tianhon...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='TECH-DISC
 USS OPNFV':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Christoph
 er Price':MAILTO:christopher.pr...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Dave Near
 y':MAILTO:dne...@redhat.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='marko.a.k
 ui...@nokia.com':MAILTO:marko.a.kui...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Rautakump
 u, Mika (Nokia - FI/Espoo)'":MAILTO:mika.rautaku...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='sheng-ann
 .y...@ericsson.com':MAILTO:sheng-ann...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='yangjiany
 j...@chinamobile.com':MAILTO:yangjian...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='zhang.jun
 3...@zte.com.cn':MAILTO:zhang.ju...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'HU, BIN'":
 MAILTO:bh5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='lma@biigr
 oup.cn':MAILTO:l...@biigroup.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tetsuya N
 akamura':MAILTO:t.nakam...@cablelabs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Wenjing Ch
 u:MAILTO:wenjing@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Christophe
 r Donley (Chris):MAILTO:christopher.don...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Jose Laus
 uch':MAILTO:jose.laus...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Vedran Ko
 salec':MAILTO:vedran.kosa...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=xudan (N):
 MAILTO:xuda...@huawei.com
DESCRIPTION;LANGUAGE=zh-CN:时间: 2017年1月20日星期五 22:00-23:00(UT
 C+08:00)北京，重庆，香港特别行政区，乌鲁木齐。\n\n注
 意: 以上 GMT 时差并不反映夏令时调整。\n\n*~*~*~*~*~*~*~*~*~
 *\n\nHi all:\n\nLast dovetail meeting\, the feedback from the C and boar
 d was mentioned. This dovetail meeting has invited the Christopher Donley 
 to join us for the discussion.\n\nWelcome to join the dovetail meeting\n\n
 Agenda:\n1)  Feedback from the C and board  Christopher Donley\n2)  
 L3VPN feedback   Jose\n3)  Feedbacks for Dovetail tool Authenticat
 ion  leo\n4)  test areas review hongbo\n\nMeeting information:\n\n• 
   Weekly on Friday at 1400-1500 UTC\n•   Gotomeeting Access\n•
https://global.gotomeeting.com/join/969604901\n•   United Sta
 tes +1 (224) 501-3318\n•   Access Code: 458-547-813\n•   IRC c
 hannel\n•   #opnfv-meeting@ Freenode (Web Chat)\n•   For more 
 detail\, please refer to :\n•   https://wiki.opnfv.org/display/dovet
 ail\n\nBest Regards\n\nhongbo\n\n\n\n
SUMMARY;LANGUAGE=zh-CN:[dovetail]dovetal weekly meeting 1/20
DTSTART;TZID=China Standard Time:20170120T22
DTEND;TZID=China Standard Time:20170120T23
UID:04008200E00074C5B7101A82E0084075D65D9471D201000
 0100091247F4CC3E8D544A0CAFCA13E915C20
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170118T081036Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:3
LOCATION;LANGUAGE=zh-CN:
X-MICROSOFT-CDO-APPT-SEQUENCE:3
X-MICROSOFT-CDO-OWNERAPPTID:-502130719
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

2017-01-18 Thread Tapio Tallgren


On 01/18/2017 12:53 AM, Dave Neary wrote:

Hi Hongbo, Jose,

As I was saying on the Dovetail calls, I have some concerns about moving
tests into the Dovetail test suite too early.

In the Dovetail test requirements, we have:

"* Test cases must pass on OPNFV reference deployments
   * Tests must not require a specific NFVi platform composition or
installation tool
   * Tests must not require unmerged patches to the relevant upstream
projects"

And in the CVP requirements, we have the following section:

"The overall CVP compliance verification scope tied to an OPNFV release
is determined by the Committee. The OPNFV TSC defines and maintains the
compliance verification procedures and associated tools. The scope is
constrained to features, capabilities, components, and interfaces
included in an OPNFV release that are generally available in the
industry (e.g., through adoption by an upstream community)."


I wonder if this functionality is sufficiently widely adopted in
commercial NFVi and VIM solutions to pass this bar.

Thanks,
Dave.


I have no opinion about L3VPN as such, but I read this to mean that the 
code should be part of a released upstream projects and that OPNFV 
installers should all support it.


What would be the best way to discuss these? Currently, the test cases 
are on a wiki page which makes it a little difficult to comment them. 
Would it make sense to copy the whole test areas and test cases wiki 
page to an Etherpad? Or should the whole page be put to gerrit for 
commenting?


-Tapio

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Canceled: [VSPERF] Weekly Call

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

[opnfv-tech-discuss] [IPv6] Project Meeting #55

[opnfv-tech-discuss] New OPNFV Website Now Live

[opnfv-tech-discuss] [Bottlenecks] Bottlenecks weekly meeting 1-19 (1:00-2:00 UTC, Thursday, 9:00-10:00 Beijing Time, Thursday, PDT 18:00-19:00 Wednesday )

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

Re: [opnfv-tech-discuss] Models Weekly Meeting A

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

[opnfv-tech-discuss] Canceled Event: OpenDaylight - OPNFV community sync meeting @ Thu Jan 19, 2017 10am - 11am (EST) (opnfv-tech-discuss@lists.opnfv.org)

[opnfv-tech-discuss] [releng] Nomination of Markos Chandras as committer to Releng

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

[opnfv-tech-discuss] [ovsnfv] Weekly Meeting

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

[opnfv-tech-discuss] [multisite]Weekly meeting of Jan.19

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

[opnfv-tech-discuss] [dovetail]dovetal weekly meeting 1/20

Re: [opnfv-tech-discuss] [dovetail]if the l3vpn feature is completed fully in C release

18 matches

Site Navigation

Mail list logo

Footer information