[opnfv-tech-discuss] [KVM] Weekly meeting for KVM enhancements for NFV - Agenda 10/12/2016

2016-10-12 Thread Reddy, Raghuveer
Meeting logistics - https://wiki.opnfv.org/nfv-kvm

Agenda:

1)  D-Release Planning

2)  Opens

Regards,
-Raghu
Ph: 408 765 4620
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


[opnfv-tech-discuss] [qtip] request for comments on the Vision

2016-10-12 Thread Yujun Zhang
Dear testers,

I noticed an action had been assigned to me in last testperf meeting[1],
i.e. planning a QTIP presentation for test community.

Here is a draft of the high level vision[2], open for comments.

This will help me get a better idea on what are interested to hear about.

[1]
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-testperf/2016/opnfv-testperf.2016-10-12-08.09.html

[2] https://wiki.opnfv.org/display/qtip/Vision

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


[opnfv-tech-discuss] Nonimation of the bottlenecks committer

2016-10-12 Thread Tianhongbo
Hi:

I would like to nominate Yang Yu as committer to Bottlenecks.
He has been one of the most active Bottlenecks contributors during Colorado 
development phase. Apart from being the top contributor to Bottlenecks during 
September, he did lots of contributions to add a new Test suite(POSCA), 
organize the Bottlenecks weekly meeting ,help maintain WIKI and also improve 
Bottlenecks documentations and Flake8 scanning.


please reply to this mail with your vote (-1, 0, +1).


Achievements/Conbributions include:
https://gerrit.opnfv.org/gerrit/#/q/owner:Gabriel.yuyang%2540huawei.com+project:bottlenecks

1. Adding POSCA test suite in Bottlenecks

a) POSCA testing framework

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-92

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/20837/

b) Adding Factor Test case System_Bandwidth

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-94

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/21351/

c) Adding Factor Test case CPU_Burden

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-95

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/21355/

d) Adding Factor Test case TX PKT Size

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-99

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/21563/

e) Adding Factor Test case RX_PKT_Size

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-97

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/21401/

f)  Adding Factor Test case TX_Cache_Size

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-98

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/21561/

g) Adding Factor Test case RX_Cache_Size

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-96

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/21379/

2. Refactoring Bottlenecks documentations

a) Correcting table format error in userguide docs

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-88

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/19043/

b) Adding framework illustration in Bottlenecks docs

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-88

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/19131/

c) Adding Release Notes Doc Framework

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-88

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/22309/

3. Flake8 fix for Bottlenecks project

a) https://jira.opnfv.org/browse/BOTTLENECK-101

b) https://gerrit.opnfv.org/gerrit/#/c/22593/

4. Organizing the Bottlenecks weekly meeting and maintaining WIKI

a) Meeting minutes and meterial

 i.  
https://wiki.opnfv.org/pages/viewpage.action?pageId=6828202

   ii.  
https://wiki.opnfv.org/download/attachments/2926187/Proposals%20in%20Bottlenecks.pdf?version=7=1472176386000=v2

b) Release Planning WIKI pages

5. Design and sharing the POSCA test suite

a) POSCA test suite in Bottlenecks D release

 i.  
https://wiki.opnfv.org/download/attachments/2926187/POSCA%20in%20Bottlenecks%20D%20Release.pptx?version=1=1475983276813=v2

b) Sharing POSCA in Bottlenecks weekly meeting

 i.  
https://wiki.opnfv.org/download/attachments/2926187/2016-09-22%20Sharing%20POSCA%20in%20Bottlenecks.mp4?version=1=1475993554550=v2

___
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]dovetail weekly meeting minutes 9/30

2016-10-12 Thread Tianhongbo
Hi Wenjing:

In the requirements, it said that all test cases need to run by multiple SDN 
controllers.
But actually, some test cases cannot be used on multiple SDN controllers.
Take the SFC as example, the SFC based on the ODL will not work on the 
environment which has the ONOS.

Best Regards

hongbo

-Original Message-
From: Wenjing Chu 
Sent: 2016年10月13日 4:53
To: Dave Neary; Tianhongbo; opnfv-tech-discuss@lists.opnfv.org; Chris Price
Subject: RE: [opnfv-tech-discuss] [dovetail]dovetail weekly meeting minutes 9/30

I agree, Dave, on the need for focused attention to agree on the test case 
criteria page. It will help clarify and unblock a lot of pending tasks. Let's 
work on that this week. (I also would like to clean up the overall wiki too, so 
info is organized more logically and easy to find.)

Hongbo, can you explain or give an example of what kind of difficulty one may 
face related to multiple SDN controllers, as you noted in your comment? 

Intuitively, I think if we have two (or more) valid options in the opnfv 
reference platform for a given need/component, either should be acceptable IF 
there is no common API level in the reference platform.

Regards
Wenjing

-Original Message-
From: Dave Neary [mailto:dne...@redhat.com]
Sent: Tuesday, October 11, 2016 11:28 AM
To: Wenjing Chu ; Tianhongbo 
; opnfv-tech-discuss@lists.opnfv.org; Chris Price 

Subject: Re: [opnfv-tech-discuss] [dovetail]dovetail weekly meeting minutes 9/30

Hi Wenjing,

On 10/11/2016 01:05 PM, Wenjing Chu wrote:
> Were you trying to reply to the dovetail agenda email or the minutes email?
> 
> In either case, the topic of finalizing test case criteria was listed. In 
> last week's call, because of low attendance, we didn't take on any meaty 
> subject, and focused on reviewing what we needed improvement around the wiki 
> and meeting logistics etc. but the subject of finalizing the test case 
> criteria (was noted down in the minutes by me as "test case requirement", 
> sorry for swapping the terms, will correct it.) did come up as we were 
> looking over that wiki page.

Thank you for the clarification.

My hope was that we could agree over email, in advance of this week's meeting, 
what we need to discuss, and what we can agree on without discussion now.

My expectation is that this will allow a productive and focussed meeting on 
Friday.

> I suggest we spend a few minutes to recap of what was discussed last week as 
> we review the minutes.

I think this is a good idea. I would also like to have some discussion of the 
open items I listed earlier by email.

Thank you,
Dave.

> 
> Regards
> Wenjing
> 
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dave 
> Neary
> Sent: Tuesday, October 11, 2016 9:45 AM
> To: Tianhongbo ; 
> opnfv-tech-discuss@lists.opnfv.org; Chris Price 
> 
> Subject: Re: [opnfv-tech-discuss] [dovetail]dovetail weekly meeting 
> minutes 9/30
> 
> Apologies - replied to the wrong meeting minutes email. The email I replied 
> to was where this task was documented as a priority work item.
> 
> Thanks,
> Dave.
> 
> On 10/11/2016 12:44 PM, Dave Neary wrote:
>> Hello Hongbo,
>>
>> I see that Chris and myself were both absent last week. For my part, 
>> I was at an event and had difficulties joining.
>>
>> I also notice that one item outstanding from the previous week was 
>> not discussed, and I would like to make progress on that issue this week.
>>
>> We agree that we should finalize the test criteria for Dovetail, and 
>> that we should do this as soon as possible, before we have added too 
>> many test cases to the Dovetail test suite.
>>
>> Looking at the draft document:
>> https://wiki.opnfv.org/pages/viewpage.action?pageId=6827269
>> it seems to me that there are a number of areas where we need 
>> discussion and agreement.
>>
>> 1. Requirement that all patches be submitted upstream - there was 
>> some discussion on this point when it was proposed, we should ensure 
>> that we have agreement 2. Requirement that tests pass on multiple 
>> scenarios in OPNFV test infrastructure - You have expressed concerns 
>> that this is difficult because of multiple SDN controllers 3.
>> Required documentation for test cases - we currently do not have test 
>> cases which satisfy all of the documentation requirements - or the 
>> requested requirement from the C committee that the test case 
>> should be sufficiently well described to allow manual execution 4.
>> "Out of scope" - Chris has stated that this section should be removed 
>> from the document, we should discuss and agree whether this is correct.
>>
>> Are there any other potential areas of disagreement? If there are, we 
>> need to document them, and figure out how we converge on an agreed 
>> 

[opnfv-tech-discuss] [dovetail]dovetail weekly meeting 10/14

2016-10-12 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=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Dan Wester
 berg:MAILTO:dan.westerb...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=ruan.he@or
 ange.com:MAILTO:ruan...@orange.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Mario Torr
 ecillas Rodriguez:MAILTO:mario.rodrig...@arm.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=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Laporte, L
 aurent [CTO]":MAILTO:laurent.lapo...@sprint.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Shobhan Ay
 yadevaraSesha (sayyadev):MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Scott Mans
 field:MAILTO:scott.mansfi...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Piyush Sar
 wal:MAILTO:psar...@us.ibm.com
DESCRIPTION;LANGUAGE=en-US:Hi all:\n\nAgenda:\n1)  Approval of the last
  minutes\n2)  Update proposal for Test plan list\na)  Update the w
 iki for test cases candidate and test requirements\ni.  Requirement th
 at all patches be submitted upstream\nii. Requirement that tests pass 
 on multiple scenarios in OPNFV test infrastructure\niii.Required docum
 entation for test cases\niv. "Out of scope"\nb)  Test candidate: h
 ttps://wiki.opnfv.org/display/dovetail/Candidate+Dovetail+test+use+cases\n
 c)  Test requirements: https://wiki.opnfv.org/display/dovetail/Candida
 te+Dovetail+test+use+cases\n3)  Update proposal for Dovetail tool  pro
 totype\n4)  other issues.\n\n•   Weekly on Friday at 1400-1500 U
 TC\n•   Gotomeeting Access\no   https://global.gotomeeting.com/j
 oin/969604901\no   United States +1 (224) 501-3318\no   Access Cod
 e: 458-547-813\n•   IRC channel\no#opnfv-meeting@ Freenode (
 Web Chat)\n\nFor more
  detail\, please refer to :\nhttps://wiki.opnfv.org/display/dovetail\n\n\n
 Best Regards\n\nhongbo\n\n\n\n
SUMMARY;LANGUAGE=en-US:[dovetail]dovetail weekly meeting  10/14
DTSTART;TZID=China Standard Time:20161014T22
DTEND;TZID=China Standard Time:20161014T23
UID:04008200E00074C5B7101A82E00890A19B50C223D201000
 010008856E9F1E8CD4646B1B34B9DDDF4AD44
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161013T013920Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:1076602848
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

Re: [opnfv-tech-discuss] [dovetail]dovetail weekly meeting minutes 9/30

2016-10-12 Thread Tianhongbo
I will add these on the agenda

Hongbo

-Original Message-
From: Dave Neary [mailto:dne...@redhat.com] 
Sent: 2016年10月12日 2:28
To: Wenjing Chu; Tianhongbo; opnfv-tech-discuss@lists.opnfv.org; Chris Price
Subject: Re: [opnfv-tech-discuss] [dovetail]dovetail weekly meeting minutes 9/30

Hi Wenjing,

On 10/11/2016 01:05 PM, Wenjing Chu wrote:
> Were you trying to reply to the dovetail agenda email or the minutes email?
> 
> In either case, the topic of finalizing test case criteria was listed. In 
> last week's call, because of low attendance, we didn't take on any meaty 
> subject, and focused on reviewing what we needed improvement around the wiki 
> and meeting logistics etc. but the subject of finalizing the test case 
> criteria (was noted down in the minutes by me as "test case requirement", 
> sorry for swapping the terms, will correct it.) did come up as we were 
> looking over that wiki page.

Thank you for the clarification.

My hope was that we could agree over email, in advance of this week's meeting, 
what we need to discuss, and what we can agree on without discussion now.

My expectation is that this will allow a productive and focussed meeting on 
Friday.

> I suggest we spend a few minutes to recap of what was discussed last week as 
> we review the minutes.

I think this is a good idea. I would also like to have some discussion of the 
open items I listed earlier by email.

Thank you,
Dave.

> 
> Regards
> Wenjing
> 
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org 
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dave 
> Neary
> Sent: Tuesday, October 11, 2016 9:45 AM
> To: Tianhongbo ; 
> opnfv-tech-discuss@lists.opnfv.org; Chris Price 
> 
> Subject: Re: [opnfv-tech-discuss] [dovetail]dovetail weekly meeting 
> minutes 9/30
> 
> Apologies - replied to the wrong meeting minutes email. The email I replied 
> to was where this task was documented as a priority work item.
> 
> Thanks,
> Dave.
> 
> On 10/11/2016 12:44 PM, Dave Neary wrote:
>> Hello Hongbo,
>>
>> I see that Chris and myself were both absent last week. For my part, 
>> I was at an event and had difficulties joining.
>>
>> I also notice that one item outstanding from the previous week was 
>> not discussed, and I would like to make progress on that issue this week.
>>
>> We agree that we should finalize the test criteria for Dovetail, and 
>> that we should do this as soon as possible, before we have added too 
>> many test cases to the Dovetail test suite.
>>
>> Looking at the draft document:
>> https://wiki.opnfv.org/pages/viewpage.action?pageId=6827269
>> it seems to me that there are a number of areas where we need 
>> discussion and agreement.
>>
>> 1. Requirement that all patches be submitted upstream - there was 
>> some discussion on this point when it was proposed, we should ensure 
>> that we have agreement 2. Requirement that tests pass on multiple 
>> scenarios in OPNFV test infrastructure - You have expressed concerns 
>> that this is difficult because of multiple SDN controllers 3. 
>> Required documentation for test cases - we currently do not have test 
>> cases which satisfy all of the documentation requirements - or the 
>> requested requirement from the C committee that the test case 
>> should be sufficiently well described to allow manual execution 4. 
>> "Out of scope" - Chris has stated that this section should be removed 
>> from the document, we should discuss and agree whether this is correct.
>>
>> Are there any other potential areas of disagreement? If there are, we 
>> need to document them, and figure out how we converge on an agreed 
>> document. This document can then be used to qualify proposed test 
>> cases and verify that they fulfill the requirements.
>>
>> Thank you,
>> Dave.
>>
>>
>>
>> On 10/03/2016 09:08 PM, Tianhongbo wrote:
>>> Hi all:
>>>
>>>  
>>>
>>> That is the dovetail weekly meeting minutes:
>>>
>>>  
>>>
>>>  
>>>
>>> 11:00:09 - collabot: Minutes:   
>>> http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opn
>>> f
>>> v-meeting.2016-09-30-14.00.html
>>>
>>> 11:00:09 - collabot: Minutes (text):
>>> http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opn
>>> f
>>> v-meeting.2016-09-30-14.00.txt
>>>
>>> 11:00:09 - collabot: Log:   
>>> http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opn
>>> f
>>> v-meeting.2016-09-30-14.00.log.html
>>>
>>>  
>>>
>>> Best regards
>>>
>>>  
>>>
>>> hongbo
>>>
>>>
>>>
>>> ___
>>> 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 
> ___
> 

Re: [opnfv-tech-discuss] [mano-wg] [MANO] Discussion of how to include MANO stack components into scenarios

2016-10-12 Thread Prakash Ramchandran
Bryan,

Each Project is taking different approach and we will discuss this in next 
mano-wg meeting, about the Goals and their relevance.
The OPERA team PTL Yingjun Li had discussions on  the same last week and Jira 
tickets in OPERA reflect that.

So as part of mano-wg I will add this to discussions for best practices for us 
to work out.


The Jira tickets are created for the same as
https://jira.opnfv.org/browse/OPERA-1
https://jira.opnfv.org/browse/OPERA-2 - Specific to Compass

[cid:image001.png@01D2249A.7676B3E0]


Thanks
Prakash

Prakash Ramchandran
[logo_huawei] R USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






From: mano-wg-boun...@lists.opnfv.org [mailto:mano-wg-boun...@lists.opnfv.org] 
On Behalf Of SULLIVAN, BRYAN L
Sent: Wednesday, October 12, 2016 9:20 AM
To: opnfv-tech-discuss@lists.opnfv.org; mano...@lists.opnfv.org
Subject: [mano-wg] [MANO] Discussion of how to include MANO stack components 
into scenarios

Hi all,

Cross-posting as not all may be on the MANO-WG list yet. Subscribe here: 
https://lists.opnfv.org/mailman/listinfo/mano-wg

As noted today on the IRC for the Infra call:
bryan_att> Bryan Sullivan 
#info We 
should have a discussion on the MANO WG re the need for scenarios for MANO 
testing. IMO as noted we should have no direct dependency upon any scenario. 
MANO components can be installed and uninstalled, replaced, etc dynamically as 
part of test scripts or post-install scripts.
 Bryan Sullivan 
#info As 
noted in the Models project we will be doing this for a variety of MANO stack 
components, both to install them (a reusable capability) and then to test them 
for specific features e.g. TOSCA blueprint compatibility, from onboarding, 
deployment, lifecycle management, etc.
8:49 AM 
#info So 
far we have developed support for Tacker and Cloudify, and OpenBaton, 
ARIA+JuJu, OSM, etc all can be addressed if we have time resources. These 
should all run on any scenario.
 
#info How 
to handle MANO can be discussed within MANO WG and MANO WG can come up with a 
common way of handling these
8:50 AM
 Bryan Sullivan 
#info and 
of course, very soon (I hope) OpenECOMP!

* I started a MANO WG wiki page for the discussion at Integrating MANO 
Components in 
OPNFV.
 Some initial thoughts are shown there in a table that we can co-edit:
Goal

Assumption/Rationale/Exceptions

Comments

MANO stack component integration does not require new scenarios

VIM NBI provide a clean interface allowing MANO stack components to be added 
post-deploy, e.g. as we do today with vIMS, or as the Models project is doing 
for various VNFM/NFVO components. Exceptions might include MANO projects that 
depend (for some unclear/poor reason!) on a specific version/fork of a VIM.



Multiple MANO stack components can coexist in a single OPNFV deploy

MANO components, even those that offer the same/overlapping functions, can 
coexist as NBI consumers on OPNFV. Good use cases for this include interim 
phases toward a truly converged future, in which a SP may need to use various 
VNFMs that work with a particular VNF/service modeling toolset. In that case 
multiple MANO component deployment will be expected to work.



*
Thanks,
Bryan Sullivan | AT

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


[opnfv-tech-discuss] OPNFV Maintainance: 2016-10-16 @ 08:00 PDT (14:00 UTC)

2016-10-12 Thread Trevor Bramwell
Hello,

The Linux Foundation will be performing maintenance on the following
services: Gerrit

When: 

  2016-10-16 @ 08:00 - 09:00 PDT (14:00 - 15:00 UTC)

Why:

  The OPNFV Gerrit server configuration needs to be updated to fix the
  following issues:

   - Automatic Stale Patchset (> 6 months) Abandonment
   - Login names with uppercase characters required to be typed in all
 lowercase

  These changes requires a restart of Gerrit.

Who:

  Trevor Bramwell 
  Aric Gardner 

Impact:

  Gerrit (https://gerrit.opnfv.org) will experience a brief outage as it
  is restarted.


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


Re: [opnfv-tech-discuss] Wiki page for license/external repo discussions

2016-10-12 Thread Raymond Paik
All,

I have not seen any new topics/questions added to the page in the past
couple of days  We'll cover items on the wiki page during the call, and
I assume it'll depend on how may questions are raised, but we maybe able to
wrap up the discussion in 30-40 minutes in case there are other topics that
people want to bring up during the weekly technical discussions meeting
tomorrow.

Thanks,

Ray

On Thu, Oct 6, 2016 at 10:26 PM, Raymond Paik 
wrote:

> All just a reminder that we will be having a discussion on
> licensing/external repo's next Thursday (13th) during the weekly technical
> discussions meeting.
>
> Please add your questions/topics you'd like to be covered during the call
> on the wiki page: https://wiki.opnfv.org/display/DEV/Licensing+and+Exter
> nal+repo%27s+discussion
>
> Thanks,
>
> Ray
>
> On Fri, Sep 30, 2016 at 10:58 AM, Raymond Paik 
> wrote:
>
>> All,
>>
>> This was one of my action items from the TSC call...  I just confirmed
>> with Bin that we can use his weekly technical discussions meeting on
>> October 13th to have a discussion on licensing and external repo's
>>
>> I started a wiki page at https://wiki.opnfv.org/disp
>> lay/DEV/Licensing+and+External+repo%27s+discussion to collect discussion
>> topics and questions.  I'm sure I missed a few  that has been brought up in
>> the past several weeks.  If you see anything missing or if you want to add
>> anything, please add them to the wiki page by October 7th.
>>
>> Thanks,
>>
>> Ray
>>
>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


[opnfv-tech-discuss] Agenda for joint TSC-Board discussion

2016-10-12 Thread Raymond Paik
All,

This was one of my action items form the TSC call yesterday.  Based on our
conversations during the call, I created the following list of topics and
"topic leads".  You also can see the original list of proposed topics from
Chris' board meeting presentation at
https://wiki.opnfv.org/display/meetings/TSC#TSC-October4,2016

   - Current state of MANO activities/projects in OPNFV: Bryan Sullivan
   - Project health & community metrics: Ray/David McBride
   - TSC Activities and Scope (including development of OPNFV
   Architecture): Frank
   - OPNFV's role in fostering synergies across networking related projects
   (e.g. on infrastructure, staffing, etc.): Tapio & Chris

I did take some liberty on leads for some of the topics, so please let me
know if you have any comments or questions.

Thanks,

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


[opnfv-tech-discuss] Next Plugfest bi-weekly call

2016-10-12 Thread Raymond Paik
All,

At the end of the last bi-weekly call, we had a quick discussion on the
next meeting on October 24th (as that's the week of OpenStack).  I talked
to Lincoln earlier today, and I think it's best to keep our regular call at
7am Pacific Time.  I arrive in Barcelona that afternoon, so there's a
chance I'll be late dialing-in, but Lincoln should be able to run the
meeting.  We looked into re-scheduling the call to sometime late next week,
but Lincoln will be on the road and it's difficult to find a meeting time
that doesn't conflict with other calls (e.g. Test WG, Dovetail, etc.)

Thanks and let me know if you have any questions.

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


Re: [opnfv-tech-discuss] Jose Lausuch is the New Functest PTL

2016-10-12 Thread Luke Hinds
Perfect man for the job. Congrats Jose.


On Tue, Oct 11, 2016 at 1:00 PM,  wrote:

> Hi TSC,
>
> I would like to inform that the Functest project elected this morning
> his new PTL.
>
> We just applied the recommendations we voted in Functest
> (https://wiki.opnfv.org/display/functest/Functest+admin)
>
> Jose -  you all know him -  will take the lead of the project.
>
> He has been very active in the project (and not only in Functest...)
> since Arno and has a perfect knowledge of the OPNFV ecosystem.
>
> Eisenhower said "Leadership consists of nothing but taking
> responsibility for everything that goes wrong and giving your
> subordinates credit for everything that goes well."
>
> @José: Do not worry, we already know that most of the things that go
> well in Functest are due to you, so I am sure you will be a great PTL!
> And as Liverpool Footbal fans are used to sing: "You will never walk
> alone..."
>
> I was very happy to PTLize Functest from Arno to Colorado. Still many
> rivers to cross...
>
> I will keep on contributing in Functest in addition of my TSC/Testing
> group/EndUserGroup tasks.
>
> vote is available here:
> http://ircbot.wl.linuxfoundation.org/meetings/opnfv-functest/2016/opnfv-
> functest.2016-10-11-08.01.html
> (note I received 4 additional Yes proxies by mail)
> INFO file has been amended: https://gerrit.opnfv.org/gerrit/#/c/22969/
> I will ask for the modification of the mailing list to include Jose in
> PTL mailing list (and remove myself)
>
> /Morgan
>
>
> 
> _
>
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
> recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>



-- 
Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44
12 52 36 2483
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


[opnfv-tech-discuss] [MANO] Discussion of how to include MANO stack components into scenarios

2016-10-12 Thread SULLIVAN, BRYAN L
Hi all,

Cross-posting as not all may be on the MANO-WG list yet. Subscribe here: 
https://lists.opnfv.org/mailman/listinfo/mano-wg

As noted today on the IRC for the Infra call:
bryan_att> Bryan Sullivan 
#info We 
should have a discussion on the MANO WG re the need for scenarios for MANO 
testing. IMO as noted we should have no direct dependency upon any scenario. 
MANO components can be installed and uninstalled, replaced, etc dynamically as 
part of test scripts or post-install scripts.
 Bryan Sullivan 
#info As 
noted in the Models project we will be doing this for a variety of MANO stack 
components, both to install them (a reusable capability) and then to test them 
for specific features e.g. TOSCA blueprint compatibility, from onboarding, 
deployment, lifecycle management, etc.
8:49 AM 
#info So 
far we have developed support for Tacker and Cloudify, and OpenBaton, 
ARIA+JuJu, OSM, etc all can be addressed if we have time resources. These 
should all run on any scenario.
 
#info How 
to handle MANO can be discussed within MANO WG and MANO WG can come up with a 
common way of handling these
8:50 AM
 Bryan Sullivan 
#info and 
of course, very soon (I hope) OpenECOMP!

* I started a MANO WG wiki page for the discussion at Integrating MANO 
Components in 
OPNFV.
 Some initial thoughts are shown there in a table that we can co-edit:
Goal

Assumption/Rationale/Exceptions

Comments

MANO stack component integration does not require new scenarios

VIM NBI provide a clean interface allowing MANO stack components to be added 
post-deploy, e.g. as we do today with vIMS, or as the Models project is doing 
for various VNFM/NFVO components. Exceptions might include MANO projects that 
depend (for some unclear/poor reason!) on a specific version/fork of a VIM.



Multiple MANO stack components can coexist in a single OPNFV deploy

MANO components, even those that offer the same/overlapping functions, can 
coexist as NBI consumers on OPNFV. Good use cases for this include interim 
phases toward a truly converged future, in which a SP may need to use various 
VNFMs that work with a particular VNF/service modeling toolset. In that case 
multiple MANO component deployment will be expected to work.



*
Thanks,
Bryan Sullivan | AT

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


[opnfv-tech-discuss] [SFC] Minutes of Meeting: Fast Data Stacks intro, Oct 12

2016-10-12 Thread Brady Allen Johnson


Here are the IRC minutes of meeting:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2016/opnfv-sfc.2016-10-12-13.53.html

Regards,

Brady


On 11/10/16 11:36, Brady Allen Johnson wrote:


In this weeks' meeting, Frank Brockners will present the OPNFV Fast 
Data Stacks project with the intention of helping us integrate Fast 
Data Stacks with OPNFV SFC.


The main goal of the OPNFV Fast Data Stacks project is to integrate 
OpenStack with the FD.io VPP virtual switch. FD.io is an alternative 
to OVS. Besides the fact that they claim to be 100 times faster than 
OVS, I think its a very interesting alternative to OVS since they 
already have NSH implemented. Their main motto is "We merge patches!".


So, come prepared with your questions, as this is something I would 
like to achieve in the OPNFV SFC Danube release.


Here are some items we need to figure out in the meeting:

  * We need to see the impacts the integration will have on the
installers (see next point).
  * Scenarios
  o Would we need another scenario for this integration, or is it
enough with an installation choice: OVS or FD.io
  * Frank says they already use FuncTest, so it should be easy to add
additional tests for SFC.
  * Classifiers
  o ODL Group Based Policy already works with FD.io
  o As I understand it, ODL Netvirt is designed to only work with OVS
  * Application Coexistence: This is not an issue in FD.io
  * ODL SFC already has a FD.io VPP renderer, so no major changes
needed there.


Regards,

Brady



___
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] OpenStack Operators Telecom/NFV Functional Team on Barcelona Summit

2016-10-12 Thread Ulrich Kleber
Hi,
since many of you might be planning your participation in the OpenStack Summit 
in Barcelona now,
I like to point you to the session of the OpenStack Operators Telecom/NFV 
Functional Team
(Wednesday, October 26, 11:25am-12:05pm).
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16768/openstack-operators-telecomnfv-functional-team

This session is a great place to discuss cooperation between OPNFV and 
OpenStack (we don't have a BOF this time).
The functional team replaces the former telco-wg, you can find some meeting 
information on
https://etherpad.openstack.org/p/ops-telco-nfv-meeting-agenda .
Please let me or Curtis (serverascode - Curtis Collicutt - 
cur...@interdynamix.com) know if you would like 
to have some topic included in the agenda.
Cheers,
Uli





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


[opnfv-tech-discuss] [SFQM] Project Scope Update

2016-10-12 Thread Tahhan, Maryam
Hi TSC

I'd like to inform you that the SFQM project is adjusting its scope within 
OPNFV, where it was solely networking centric in the past, we'd like to extend 
the scope of the telemetry work we are doing to include the NVFI. As such I've 
started a project scope adjustment wiki here: 
https://wiki.opnfv.org/display/fastpath/SFQM+Scope+Adjustment+Proposal+and+Rename
 

Please note that it was recommended that we also rename the project, and this 
rename is a work in progress.

We will be kick starting the community review through the technical discussion 
forum next week.

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


Re: [opnfv-tech-discuss] [ovsnfv] [vsperf] Analysis of Microburst on VSwitch

2016-10-12 Thread Lee, Chunghan
Hi Maryam,

I'm Chunghan Lee of OVSNFV contributor.

Few weeks ago, I had the presentation related to burstiness of internal OVS to 
our OVSNFV member.
> Thanks for your presentation on Monday 
> (https://wiki.opnfv.org/download/attachments/5046510/0919_ovsnfv.pdf?version=1=1474280389000=v2
>  ). 

Our OVSNFV members are interested in the measurement results.
Billy (billy.o.mah...@intel.com) also suggests the discussion to VSPERF side.
If possible, I'd like to discuss the results to VSPERF members.
As a first step, I contact to you.

Regards,
Chunghan Lee

--
Chunghan Lee
Cloud Network Project. Fujitsu Laboratories Ltd.
4-1-1 Kamikodanaka, Nakahara-ku, 
Kawasaki-shi, Kanagawa 211-8588, Japan
E-mail: lee.chung...@jp.fujitsu.com
--


-Original Message-
From: O Mahony, Billy [mailto:billy.o.mah...@intel.com] 
Sent: Wednesday, September 21, 2016 6:26 PM
To: Lee, Chunghan/李 忠翰; opnfv-tech-discuss@lists.opnfv.org
Cc: Gray, Mark D; therb...@redhat.com; Michal Skalski
Subject: [ovsnfv] [vsperf] Analysis of Microburst on VSwitch

Hi Chunghan,

Thanks for your presentation on Monday 
(https://wiki.opnfv.org/download/attachments/5046510/0919_ovsnfv.pdf?version=1=1474280389000=v2
 ). It was very interesting to see where packets are lost when OVS is 
overloaded.

There is a vSwitch testing project in OPNFV - vsperf 
https://wiki.opnfv.org/display/vsperf/?s[]=vsperf

This has a set of standardized tests that can be run on vSwitches - currently 
it supports OVS and OVS-DPDK. The tests have been defined and codified in an 
IETF draft 
https://wiki.opnfv.org/display/vsperf/Vswitchperf+Ietf+Draft+Submission , 
though not all those tests are supported yet. It currently supports IXIA (h/w) 
and Moongen (s/w) traffic generators.

Hope you find that info useful, 
/Billy.

___
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 Oct.13

2016-10-12 Thread joehuang
Hello, team,

Let's continue the discussion on these topics

Agenda of Oct.13 2016

  *   3)Resources Sync
  *   3.1)SEG
  *   3.2)FLAVOR
  *   3.3)SSH KEY
  *   Revisit Geographical Redundancy
  *   4)cross neutron networking automation
  *   5) installation cooperation

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

if you would like to discuss other topics 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