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

2017-06-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\nHello team\,\n\nHere is the
  information of our IPv6 project meeting #63 to check the status update.\n
 \n-   When: Friday 8:00-9:00 PDT (15:00-16:00 UTC) June 23rd\, 2017\no
Your local time\n-   Bridge: GoTo Meeting:\no  
  Web Conferencing: https://global.gotomeeting.com/join/819733085\no   
 Dial-in only:\n•   United States (Long distance): +1 (312) 757-3
 126 / Access Code: 819-733-085\n•   More phone numbers: https://glob
 al.gotomeeting.com/819733085/numbersdisplay.html\n-   Meeting page: ht
 tps://wiki.opnfv.org/display/meetings/ipv6 for agenda and minutes\n-  
  Project wiki page: https://wiki.opnfv.org/display/ipv6/IPv6+Home for all 
 information and resources related to IPv6 project\n\nLook forward to worki
 ng with everyone.\n\nThanks\nBin\n\n\n
SUMMARY;LANGUAGE=en-US:[IPv6] Project Meeting #63
DTSTART;TZID=Pacific Standard Time:20170623T08
DTEND;TZID=Pacific Standard Time:20170623T09
UID:04008200E00074C5B7101A82E008508D426C34E8D201000
 010004A14B15382DAD744B67A2C703B384EE2
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170618T201139Z
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:116549601
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] [opnfv-tsc] [dovetail] TSC and DoveTail meeting to discuss scope and needs for CVP testing

2017-06-18 Thread Dave Neary 
Hi Tim,

On 06/13/2017 05:28 PM, Tim Irnich wrote:
> In addition the Dovetail team walked through the list of OPNFV feature
> projects and concluded that currently no other projects than the already
> included ones are advanced enough for compliance verification, due to
> varying reasons (e.g. depending on midstream patches, etc.).
> 
> To provide visibility into what would be coming next, an initial list of
> work items for Euphrates was created:
> 
>   * Stress testing
>   * Include Doctor (optional/mandatory is tbd)
>   * Include Models (the OPNFV project) test cases (launch a sample
> multi-VM VNF)
>   o We need to check these against the test case requirements
>   * Incorporate more OPNFV feature projects (e.g. SFC etc.)

Again, my apologies for my conflict on Tuesday during the Dovetail team
meeting. Thank you for the notes and conclusions, Tim.

I have some issues with some of these proposed test areas, for a few
reasons. The first is that there are several areas where it is unclear
if there is critical mass adoption from Doctor, Models, to merit
inclusion in Dovetail. The second is the continued focus on project
tests and feature projects, rather than basic NFVI and VIM features for
which we do not yet have tests.

I would like to see us document some of the NFV related requirements
which are common across all RFCs from telcos, and which are available in
all viable VIM products. I see value in then identifying those areas
where we do not have tests, and implementing functional tests for these
requirements.

The focus on new features and feature projects misses all of the NFV
related features between RefStack (low bar, API tests) and current
development (too new to include in Dovetail). It seems like there is a
middle ground.

Thanks,
Dave.

-- 
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