[opnfv-tech-discuss] [KVM] Weekly meeting for KVM enhancements for NFV - Agenda 3/2/2017

[Reddy, Raghuveer]

Meeting logistics - https://wiki.opnfv.org/nfv-kvm
Weekly on Thursday at 
2330 
UTC (4:30PM PDT)
Goto Meeting Link

Agenda:

1)  Milestone check

2)  Testing update

3)  Scenario Debugging update

4)  Documentation

5)  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] reply: Quick follow-up from the Plugfest planning call

[Tianhongbo]

Hi Trevor:

One information sharing:

In the previous plugfest. The performance test projects have participated such 
as the yardstick, storperf and bottlenecks.

Best regards

hongbo

发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Cooper, Trevor
发送时间: 2017年3月2日 7:16
收件人: Raymond Paik; MORTON, ALFRED C (AL)
抄送: opnfv-tech-discuss@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] Quick follow-up from the Plugfest planning call

I support Al’s suggestion. As a goal for the Danube Plugfest I think we should 
define at least one performance oriented test that we run using different 
deployments / configurations … with an objective to define a range of good vs 
bad performance in order to get started with performance as a dimension of CVP. 
Plugfest is a good opportunity for accelerating this IMO … we can discuss it in 
the Test Working Group and try to make an initial proposal.

/Trevor



From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Wednesday, March 01, 2017 1:36 PM
To: MORTON, ALFRED C (AL) mailto:acmor...@att.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Quick follow-up from the Plugfest planning 
call

Al,

I'm not sure if performance testing has been specifically excluded in OPNFV 
Plugfests.  A number of projects like Storperf participated in past two 
Plugfests.  Of course we can't get into things like Storperf results were 
better on X vs. Y discussions, but there's no reason why performance testing 
can't be done during the Plugfest.

Thanks,

Ray

On Wed, Mar 1, 2017 at 5:24 AM, MORTON, ALFRED C (AL) 
mailto:acmor...@att.com>> wrote:
Hi Ray and Plugtesters,

Apologies for missing Monday’s meeting
(Jury Duty is a Civic responsibility,
but makes attending some meetings impossible).

Regarding test cases, I wonder if the Scope of
testing has been decided, and whether a
*performance-oriented* test case might be entertained
this time?  This topic has been out of scope in the
previous Plugfests and ETSI CTI’s Plugtest™, AFAIK.

It may still be too soon, but it’s worth asking now.

regards,
Al

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org]
 On Behalf Of Raymond Paik
Sent: Wednesday, March 01, 2017 1:21 AM
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Quick follow-up from the Plugfest planning call

All,

A few things after our call on Monday

First, I realized that I had sent out a recurring weekly meeting for Plugfest 
planning when this is supposed to be a bi-weekly meeting.  I will go ahead and 
cancel the current series and start a new one that starts on March 13th.  (so 
the upcoming meetings are March 13/27 plus April 10th).  Apologies for the 
thrash, but you can also find the upcoming meeting info. at 
https://wiki.opnfv.org/display/EVNT/Plugfest+-+Danube+Release#Plugfest-DanubeRelease-PlugfestPlanningMeetings

Second, I started a test cases page at 
https://wiki.opnfv.org/display/EVNT/Danube+Plugfest+Test+Cases.
  I followed the template from the last Plugfest, but as you can see it's just 
a skeleton.  I encourage everyone (esp. those who were on the call yesterday) 
to contribute ideas/suggestions for what we should focus on for the upcoming 
Plugfest.

Finally, a reminder that the Plugfest is open to both members & non-members of 
OPNFV.  You can register at 
https://www.regonline.com/OPNFVPlugfestApril2017

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] [Bottlenecks] Minutes of Bottlenecks Discussion on March 2, 2017

[Yuyang (Gabriel)]

Minutes of Bottlenecks Discussion on March 2, 2017

  *   Date and Time
 *   Thursday at 
0100-0200
 UTC, March 2, 2017
 *   Thursday at 0900-1000 Beijing, March 2, 2017
 *   Wednesday at 1800-1900 PDT, March 2, 2017
  *   Minutes
 *   Yang (Gabriel) Yu
  *   Participants (3 peoples):
 *   Ace Lee
 *   Yang (Gabriel) Yu
 *   Prakash Ramchandran
Agenda:
* Bottlenecks D Release Discuss
* Stress Testing Discuss
* Action Items Review
Discussion & Action Item

1. Bottlenecks Danube Release Discuss

a)An agreement on documentation structure in testing project repo has 
been reached.

 i.  Bottlenecks will follow the agreement 
and make changes of the project repo

   ii.  The action item is assigned to Gabriel

b)New test suite POSCA and the new testing framework is online in CI

 i.  Stress tests are introduced

   ii.  Support calling yardstick

1. Support environment configuration

2. Support run yardstick in docker and by API

3. Support result and debug log collecting

 iii.  ELK for result displaying

2. Stress test Discussion

a)2 Stress tests are introduced

 i.  Baseline test for dataplane traffic

1. Baremetal scenario pass

2. Virtual deploy scenario pass

   ii.  Perfomance-life cycle event for ping

1. Baremetal scenario fail

a)Environment issue may be caused by Quota setting, need to determine

b)An action item is assigned to Prakash to dig more on Quota.

2. Virtual deploy scenario pass

b)In order not to occupying too much CI resources, current tress tests 
are configured to run within 1 hour

 i.  To make through test, stress test 
maybe runs in hours or days

   ii.  Dedicated PODs for stress test maybe 
needed for E release which has been briefly discussed in testperf meeting

c) Prakash mentioned there is a new project in Openstack dealing with 
tests for system availability/robustness. Maybe Bottlenecks could integrate.

 i.  An action item is assigned to Prakash 
and Gabriel to find out about this project

3. Action Item Review

a)https://wiki.opnfv.org/display/bottlenecks/Release+Plan
  Danube:
Action before MS6
[ ] Stress test
  [√] Test document for stress test before MS6 - Yang @done (17-02-23 09:49)
  [√] CI build job for ping stress test before MS6 - Yang @done (17-02-23 
09:49)
  [√] CI cleaning process for posca - Yang @done (17-02-16 09:19)
[√] docker-compose down [CONFIG] --rmi all @done (17-02-16 09:19)
[√] docker -f rmi tutum/influxdb:0.13 @done (17-02-16 09:19)
  [√] check if docker-compose should be installed in CI PODS - Yang @done 
(17-02-23 09:49)
  [ ] Debugging Stress test
  [ ] Ping stress - Ace
[√] testing code @done (17-02-16 09:29)
[√] dashboard @done (17-02-23 09:49)
[√] Newton Quotas configuration (Nova, Neutron) @done (17-02-23 09:45)
[ ] Yardstick Newton debugging
  [√] Data-plane traffic @done (17-02-09 09:21)
[ ] POSCA testsuite
  [√] POSCA jenkins job - Yang @done (17-02-09 09:19)
  [√] POSCA refactoring - Ace @done (17-02-16 09:20)
[√] Testing code @done (17-02-16 09:20)
[√] Dashboard code @done (17-02-16 09:20)
  [ ] Documentation for POSCA - Yang
[√] CLI @done (17-02-09 09:22)
[ ] Test Framework refactoring (80%)
[ ] Test report
  [√] MongoDB reporting @done (17-02-16 09:21)
  [ ] Landing page (on-going)
[√] File header fixing @done (17-02-23 09:51)
[ ] How to use Quota - Prakash
[ ] Reliability project in Openstack - Prakash
  Bottlenecks:
[√] Apex POD build - Ace @done (17-02-16 09:21)
[√] 1+1 virtual installation @done (16-12-13 12:31)
[√] 3+2 physical installation  (Pending) @done (17-02-16 09:21)
[√] Virtual 3+2 installation @done (17-01-05 09:24)
[ ] Different installers support
[ ] Added in landing page of testing group
[√] Jenkins job for POSCA @done (17-02-09 09:22)
[ ] MongoDB reporting  (on-going)
[ ] CI refactoring - Gabriel
[ ] Unitttest for POSCA
[√] Adding flake8 to POSCA @done (16-12-19 17:33)
[ ] Adding unittest & coverage to POSCA
[ ] Frame refactoring & common functions
[ ] Decoupling Bottlenecks eviroment preparation logics in releng
[√] Adding POSCA to CI Pipeline @done (17-02-09 09:23)
[ ] Bottlenecks testing framework refactoring - Ace
[√] Newton support & Envir

[opnfv-tech-discuss] HA project meeting

[Fu Qiao]

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 15.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
ATTENDEE;CN="'stpierre, edgar'";RSVP=TRUE:mailto:edgar.stpie...@dell.com
ATTENDEE;CN="'Leon Wang'";RSVP=TRUE:mailto:wang...@8hutech.com
ATTENDEE;CN='wanghui71';RSVP=TRUE:mailto:wanghu...@huawei.com
ATTENDEE;CN='opnfv-tech-discuss';RSVP=TRUE:mailto:opnfv-tech-discuss@lists.
	opnfv.org
ATTENDEE;CN='Ian.Jolliffe';RSVP=TRUE:mailto:ian.jolli...@windriver.com
ATTENDEE;CN="'Stefan Arntzen'";RSVP=TRUE:mailto:stefan.arnt...@huawei.com
ATTENDEE;CN='greg.waines';RSVP=TRUE:mailto:greg.wai...@windriver.com
ATTENDEE;CN='14_ykl';RSVP=TRUE:mailto:14_...@tongji.edu.cn
ATTENDEE;CN='juan_qiu';RSVP=TRUE:mailto:juan_...@tongji.edu.cn
ATTENDEE;CN='mathi.naickan';RSVP=TRUE:mailto:mathi.naic...@oracle.com
ATTENDEE;CN='jonas.arndt';RSVP=TRUE:mailto:jonas.ar...@hpe.com
ATTENDEE;CN=wanghui71l...@gmail.com;RSVP=TRUE:mailto:wanghui71l...@gmail.co
	m
ATTENDEE;CN='yuan.yue';RSVP=TRUE:mailto:yuan@zte.com.cn
ATTENDEE;CN='jniu';RSVP=TRUE:mailto:j...@redhat.com
ATTENDEE;CN="'Peng Liu'";RSVP=TRUE:mailto:p...@redhat.com
CLASS:PUBLIC
CREATED:20170302T021649Z
DESCRIPTION:Update info for next week’s project meeting. We will have to 
	switch back to GTM due to connection problem in certain facilities in the 
	US.\n\nMeetings for High Availability Project\nNext Meeting on 13:00-14:00
	 UTC\, Wednesday\, Mar. 8th\nhttps://global.gotomeeting.com/join/772448949
	\n \nToll free NO.\nUSA: +1 (646) 749-3117\n \nMeeting ID: 772-448-949\nAg
	enda\nHA API doc updates – Greg\n\n
DTEND;TZID="China Standard Time":20170308T22
DTSTAMP:20170302T021649Z
DTSTART;TZID="China Standard Time":20170308T21
LAST-MODIFIED:20170302T021649Z
ORGANIZER;CN="Fu Qiao":mailto:fuq...@chinamobile.com
PRIORITY:5
SEQUENCE:2
SUMMARY;LANGUAGE=zh-cn:HA project meeting
TRANSP:OPAQUE
UID:04008200E00074C5B7101A82E008306ACB74E782D201000
	01000B997547D3F02F84FADF138D3A31B0F31
X-ALT-DESC;FMTTYPE=text/html:\n\n\n\n\n\n\n\n\nUpdate info for next week’s project m
	eeting. We will have to switch back to GTM due to connection problem in ce
	rtain facilities in the US.\n\nMeetings for High Availability Project\n\nNext Meeting on 13:00-14:00 UTC\, Wednes
	day\, Mar. 8th\n\n<
	SPAN LANG="en-us">https://global.gotomeeting.com/join/7724
	48949">https://global.gotomeeting.com/join/772448949\n\n \n\n<
	FONT COLOR="#33" FACE="Arial">Toll free NO.\n\nUSA: +1 (646) 
	749-3117\n\n \n\nMeeting ID: 772-448-949<
	/P>\n\n
	Agenda\n\nHA API doc updates –<
	FONT COLOR="#33" FACE="Arial"> Greg\n\n\n\n\n
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MS-OLK-APPTLASTSEQUENCE:1
X-MS-OLK-APPTSEQTIME:20170209T071615Z
X-MS-OLK-AUTOSTARTCHECK:FALSE
X-MS-OLK-CONFTYPE:0
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] [availability] Change in availability[master]: Updating Commit based on initial review during OPNFV HA meet...

[Fu Qiao]

Hi, Greg. Thank you! Will put you on the agenda for next week.

And to the team, please review the new update before our next meeting so that 
we could have an efficient discussion. 

Thanks to everyone.

 

发件人: Waines, Greg [mailto:greg.wai...@windriver.com] 
发送时间: 2017年3月1日 21:45
收件人: fuq...@chinamobile.com
抄送: Ulrich Kleber; Hui Wang; Stefan Arntzen; Jolliffe, Ian; Edgar StPierre; Yue 
Yuan
主题: Re: Change in availability[master]: Updating Commit based on initial review 
during OPNFV HA meet...

 

Qiao Fu,

 

FYI … I have just submitted an update to the Overview document of the HA Guest 
API work.

 

Is it possible to get another discussion of the Overview document on the Agenda 
for next week ?

 

thanks,

Greg.

 

 

 

From: "Qiao Fu (OPNFV Code Review)" mailto:ger...@opnfv.org> 
>
Reply-To: "fuq...@chinamobile.com  " 
mailto:fuq...@chinamobile.com> >
Date: Thursday, February 23, 2017 at 3:07 AM
To: Greg Waines mailto:greg.wai...@windriver.com> >
Cc: Ulrich Kleber mailto:ulrich.kle...@huawei.com> 
>, Hui Wang mailto:wanghu...@huawei.com> >, Stefan 
Arntzen mailto:stefan.arnt...@huawei.com> >, 
"Jolliffe, Ian" mailto:ian.jolli...@windriver.com> 
>, Edgar StPierre mailto:edgar.stpie...@dell.com> >, 
Yue Yuan mailto:yuan@zte.com.cn> >
Subject: Change in availability[master]: Updating Commit based on initial 
review during OPNFV HA meet...

 

Qiao Fu has posted comments on this change. ( 
https://gerrit.opnfv.org/gerrit/26663 )

 

Change subject: Updating Commit based on initial review during OPNFV HA 
meeting, as well as submitted comments on the review.

..

 

 

Patch Set 2:

 

(6 comments)

 

sorry for the late reply. I was out of office last week.

 

https://gerrit.opnfv.org/gerrit/#/c/26663/2/Support_For_HA_Guest_APIs/OPNFV_HA_Guest_APIs-Overview_HLD.rst

File Support_For_HA_Guest_APIs/OPNFV_HA_Guest_APIs-Overview_HLD.rst:

 

Line 40: - VM Event Notification and Acknowledgement

Please explain the difference to the notifications in doctor project.

I think these is some misunderstanding here. Probably because the entry here is 
a little bit misleading. The event notification here does not mean VM notify 
the guest os or the MANO, but indicates the other way round. I suggest to 
change this entry as "Infrustructure event notification and VM ack"

 

 

Line 42: - VM Resource Scaling

Yeah agree that the next 'iteration' of the Overview Document needs to "bri

Greg. I think some explaination should be made here. I think the HA API is kind 
of misleading. People may consider the VM directly uses these APIs and get the 
info that they need. However from your reply above, I see that the NFVO and 
VNFM are the entities that use these. The NFVO and VNFM use the nova restful 
API to trigger certain action, and the nova proxy kidnaps these command, 
trigger some interaction between the host and VM using these API, then give the 
command back to the real nova. (don't know if I understand right about these). 
if so, I think we may not call these as API but rather should be message flow 
between VM and the host OS.

for each entry listed above, I suggest to add a short explaination or example 
about how to use the capability by NFVO and VNFM.

 

 

PS2, Line 52: M Heartbeating and Health Checking

which entity should use this API. Is it nova or nova proxy? my understanding is 
the API is used by nova or nova proxy, to indicate the daemon to work and reply 
to nova about the health of the VM. Am I right?

 

 

PS2, Line 88:  a corrective action that overrides the default 

:corrective action specified at regist

this corrective action should be override by the VM or the VNFM?

I think the VNFM should do such decision. or at least the VNFM should have such 
capability

 

 

PS2, Line 155: In addition to notifications, there is also an opportunity for 
the VM

 :to vote on any proposed event.  Voting precedes all 
notifications,

 :and offers the VM a chance to reject the event that the 
OpenStack Cloud 

 :wishes to initiate.

The USE CASE here is that the we are providing a mechanism for the Guest VM

I think there should be a scheme to notify the nova proxy which operation is 
strong and should be forced without consideration of the VM, and which 
operation can be postponed and wait for the VM to prepare smoothly.So there 
could be 3 situations.

1) the action is not urgent, nova proxy asks the vm to vote and the VM agrees 
to take the action

2) the action is not urgent, nova proxy asks the vm to vote, the vm rejects the 
action. nova proxy hand the action to nova after the vm finishes preparing

3) the action is urgent. nova proxy directly hands this action to nova without 
asking the vm to vote.

 

 

PS2, Line 182: VM Peer State Notification and Messaging

who should take action when the peer state message fail

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

[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:Hi\,\n\nThe Bottlenecks weekly meeting will be h
 eld 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 m
 eeting are shown below.\n\n\nAgenda:\n1.  Bottlenecks D Rel. Discussio
 n\n2.  Stress testing Discussion\n3.  Action Item Review\n\nMeetin
 g Resources\n\nPlease join the meeting from your computer\, tablet or smar
 tphone.\nhttps://global.gotomeeting.com/join/882532573\n\nYou can also dia
 l 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\n\n
SUMMARY;LANGUAGE=zh-CN:[Bottlenecks] Bottlenecks weekly meeting 3-2 (1:00-2
 :00 UTC\, Thursday\, 9:00-10:00 Beijing Time\, Thursday\, PDT 18:00-19:00 
 Wednesday )
DTSTART;TZID=China Standard Time:20170302T09
DTEND;TZID=China Standard Time:20170302T10
UID:04008200E00074C5B7101A82E008D0AF29B23293D201000
 01000B403BEC2D9C9634DAE3532D9BD4E8BB4
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170302T005509Z
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:-152946719
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:-PT5M
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] [JOID] Can JOID Installer run in a VM?

[SULLIVAN, BRYAN L]

I got confirmation today in the JOID meeting that in principle there should not 
be a problem with the JOID installer running in a VM on the jumphost. The only 
prerequisite is that for every host NIC or interface that is used for the OPNFV 
deploy (minimum two), there must be a bridge defined that the VM can attach to.

Exactly how to do that (setup bridges and VM NIC interfaces which connect to 
them, for all host interfaces) will be investigated. Any hints are much 
appreciated!

Thanks,
Bryan Sullivan | AT&T

From: SULLIVAN, BRYAN L
Sent: Monday, February 27, 2017 8:44 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [JOID] Can JOID Installer run in a VM?

Hi Narinder and other JOID project members:

In the Infra call today I took the action to check with you whether the JOID 
installer can be run in a VM on the jumphost. This is a goal of the Infra team 
so we can help ensure some strategic things for CI/CD:

-  Jumphosts are stable, i.e. installers do not pollute the jumphost 
(sometimes resulting in need to redeploy the jumphost)

-  Jumphosts are consistent, e.g. we can use a common Jumphost host OS 
(e.g. Ubuntu) and run all installer ISOs in VMs on the jumphost

-  We can migrate to dynamic POD allocation, given the two capabilities 
above

This is a key need of development lab users also, who probably don't have the 
automated tools for POD deployment such as OPNFV CI/CD uses, and who can spend 
a lot of time having to reinstall jumphosts to switch between OPNFV distros.

Does JOID support the installer ISO being booted:

1)  in a libvirt (qemu+kvm) VM

2)  on a generic jumphost (i.e. Ubuntu or Centos)


Thanks,
Bryan Sullivan | AT&T

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

Re: [opnfv-tech-discuss] Quick follow-up from the Plugfest planning call

[Cooper, Trevor]

I support Al’s suggestion. As a goal for the Danube Plugfest I think we should 
define at least one performance oriented test that we run using different 
deployments / configurations … with an objective to define a range of good vs 
bad performance in order to get started with performance as a dimension of CVP. 
Plugfest is a good opportunity for accelerating this IMO … we can discuss it in 
the Test Working Group and try to make an initial proposal.

/Trevor



From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Wednesday, March 01, 2017 1:36 PM
To: MORTON, ALFRED C (AL) 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Quick follow-up from the Plugfest planning 
call

Al,

I'm not sure if performance testing has been specifically excluded in OPNFV 
Plugfests.  A number of projects like Storperf participated in past two 
Plugfests.  Of course we can't get into things like Storperf results were 
better on X vs. Y discussions, but there's no reason why performance testing 
can't be done during the Plugfest.

Thanks,

Ray

On Wed, Mar 1, 2017 at 5:24 AM, MORTON, ALFRED C (AL) 
mailto:acmor...@att.com>> wrote:
Hi Ray and Plugtesters,

Apologies for missing Monday’s meeting
(Jury Duty is a Civic responsibility,
but makes attending some meetings impossible).

Regarding test cases, I wonder if the Scope of
testing has been decided, and whether a
*performance-oriented* test case might be entertained
this time?  This topic has been out of scope in the
previous Plugfests and ETSI CTI’s Plugtest™, AFAIK.

It may still be too soon, but it’s worth asking now.

regards,
Al

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org]
 On Behalf Of Raymond Paik
Sent: Wednesday, March 01, 2017 1:21 AM
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Quick follow-up from the Plugfest planning call

All,

A few things after our call on Monday

First, I realized that I had sent out a recurring weekly meeting for Plugfest 
planning when this is supposed to be a bi-weekly meeting.  I will go ahead and 
cancel the current series and start a new one that starts on March 13th.  (so 
the upcoming meetings are March 13/27 plus April 10th).  Apologies for the 
thrash, but you can also find the upcoming meeting info. at 
https://wiki.opnfv.org/display/EVNT/Plugfest+-+Danube+Release#Plugfest-DanubeRelease-PlugfestPlanningMeetings

Second, I started a test cases page at 
https://wiki.opnfv.org/display/EVNT/Danube+Plugfest+Test+Cases.
  I followed the template from the last Plugfest, but as you can see it's just 
a skeleton.  I encourage everyone (esp. those who were on the call yesterday) 
to contribute ideas/suggestions for what we should focus on for the upcoming 
Plugfest.

Finally, a reminder that the Plugfest is open to both members & non-members of 
OPNFV.  You can register at 
https://www.regonline.com/OPNFVPlugfestApril2017

Thanks,

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] Quick follow-up from the Plugfest planning call

[Raymond Paik]

Al,

I'm not sure if performance testing has been specifically excluded in OPNFV
Plugfests.  A number of projects like Storperf participated in past two
Plugfests.  Of course we can't get into things like Storperf results were
better on X vs. Y discussions, but there's no reason why performance
testing can't be done during the Plugfest.

Thanks,

Ray

On Wed, Mar 1, 2017 at 5:24 AM, MORTON, ALFRED C (AL) 
wrote:

> Hi Ray and Plugtesters,
>
>
>
> Apologies for missing Monday’s meeting
>
> (Jury Duty is a Civic responsibility,
>
> but makes attending some meetings impossible).
>
>
>
> Regarding test cases, I wonder if the Scope of
>
> testing has been decided, and whether a
>
> **performance-oriented** test case might be entertained
>
> this time?  This topic has been out of scope in the
>
> previous Plugfests and ETSI CTI’s Plugtest™, AFAIK.
>
>
>
> It may still be too soon, but it’s worth asking now.
>
>
>
> regards,
>
> Al
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Raymond Paik
> *Sent:* Wednesday, March 01, 2017 1:21 AM
> *To:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* [opnfv-tech-discuss] Quick follow-up from the Plugfest
> planning call
>
>
>
> All,
>
>
>
> A few things after our call on Monday
>
>
>
> First, I realized that I had sent out a recurring weekly meeting for
> Plugfest planning when this is supposed to be a bi-weekly meeting.  I will
> go ahead and cancel the current series and start a new one that starts on
> March 13th.  (so the upcoming meetings are March 13/27 plus April 10th).
> Apologies for the thrash, but you can also find the upcoming meeting info.
> at https://wiki.opnfv.org/display/EVNT/Plugfest+-+Danube+Release#Plugfest-
> DanubeRelease-PlugfestPlanningMeetings
> 
>
>
>
> Second, I started a test cases page at https://wiki.opnfv.org/
> display/EVNT/Danube+Plugfest+Test+Cases
> .
> I followed the template from the last Plugfest, but as you can see it's
> just a skeleton.  I encourage everyone (esp. those who were on the call
> yesterday) to contribute ideas/suggestions for what we should focus on for
> the upcoming Plugfest.
>
>
>
> Finally, a reminder that the Plugfest is open to both members &
> non-members of OPNFV.  You can register at https://www.regonline.com/
> OPNFVPlugfestApril2017
> 
>
>
>
>
> 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] ODL SFC with multiple compute nodes

[Srikanth Lingala]

Hi guys,
I am able to run SFC usecase successfully with single Compute Node.
Now, I am trying SFC usecase across multiple computes with Opendaylight, 
Openstack and OVS with NSH patches by Yi Yang. For that, I deployed a Openstack 
setup with OPNFV Colorado 3.0.
My setup includes:

* One Openstack Controller with ODL controller and tacker

* Two Compute Nodes

For validating SFC usecase, I am using tacker. Following are the sequence of 
commands to configure SFC attributes, in my usecase:

neutron net-create net_mgmt --provider:network_type=vxlan 
--provider:segmentation_id 1005
neutron subnet-create net_mgmt 123.123.123.0/24
tacker vnfd-create --vnfd-file /root/sfc-random/test-vnfd-1.yaml
tacker vnfd-create --vnfd-file /root/sfc-random/test-vnfd-2.yaml
tacker vnf-create --name testVNF1 --vnfd-name test-vnfd-1 (SFC VM1 on Compute 1)
tacker vnf-create --name testVNF2 --vnfd-name test-vnfd-2 (SFC VM2 on Compute 2)
nova boot --flavor custom --image SFC-VM --nic net-id=$(neutron net-list | awk 
'/ net_mgmt / {print $2}') --availability-zone compute1 http_server 
(http_server VM on Compute 2)
nova boot --flavor custom --image SFC-VM --nic net-id=$(neutron net-list | awk 
'/ net_mgmt / {print $2}') --availability-zone compute2 http_client 
(http_client VM on Compute 1)
tacker sfc-create --name mychain --chain testVNF1,testVNF2
tacker sfc-classifier-create --name myclass --chain mychain --match 
source_port=2000,dest_port=80,protocol=6


All the above commands are successful. SFC flows are added in the respective 
compute nodes.
Flows on Compute Node1:
http://pastebin.com/R1ZkvpHt

Flows on Compute Node2:
http://pastebin.com/WcCLeQTH

Here comes the issue

I am able to see packets on SFC Flows in Compute Node1. And also, I am able to 
see VxLAN packets (vxlan_tool.py) on SFC VM launched on Compute Node 1.
But, I am not able to see any packets on SFC flows in Compute Node 2. 
Obviously, not getting VxLAN packets on SFC VM in Compute Node2.
I think packets are not getting from 'vxgpe' port in Compute Node1 to Compute 
Node 2. When I execute the command ovs-appctl ofproto/trace on br-int of 
Compute Node1, I got the following trace information:
Here, vxgpe port number is 1. So, I gave flow trace for in_port as '1'.

Compute_Node1#> ovs-appctl ofproto/trace br-int nsi=254,nsp=35,in_port=1
Bridge: br-int
Flow: 
in_port=1,vlan_tci=0x,dl_src=00:00:00:00:00:00,dl_dst=00:00:00:00:00:00,dl_type=0x

Rule: table=0 cookie=0x14 priority=250,nsp=35
OpenFlow actions=goto_table:152

Resubmitted flow: 
in_port=1,vlan_tci=0x,dl_src=00:00:00:00:00:00,dl_dst=00:00:00:00:00:00,dl_type=0x
Resubmitted regs: reg0=0x0 reg1=0x0 reg2=0x0 reg3=0x0 reg4=0x0 reg5=0x0 
reg6=0x0 reg7=0x0 reg8=0x0 reg9=0x0 reg10=0x0 reg11=0x0 reg12=0x0 reg13=0x0 
reg14=0x0 reg15=0x0
Resubmitted  odp: drop
Resubmitted megaflow: 
recirc_id=0,nsi=254,nsp=35,in_port=1,dl_type=0x
Rule: table=152 cookie=0x14 priority=550,nsi=254,nsp=35
OpenFlow actions=load:0xc0a8001a->NXM_NX_TUN_IPV4_DST[],goto_table:158

Resubmitted flow: 
tun_src=0.0.0.0,tun_dst=192.168.0.26,tun_ipv6_src=::,tun_ipv6_dst=::,tun_gbp_id=0,tun_gbp_flags=0,tun_gpe_np=0,tun_gpe_flags=0,tun_tos=0,tun_ttl=0,tun_flags=0,in_port=1,vlan_tci=0x,dl_src=00:00:00:00:00:00,dl_dst=00:00:00:00:00:00,dl_type=0x
Resubmitted regs: reg0=0x0 reg1=0x0 reg2=0x0 reg3=0x0 reg4=0x0 
reg5=0x0 reg6=0x0 reg7=0x0 reg8=0x0 reg9=0x0 reg10=0x0 reg11=0x0 reg12=0x0 
reg13=0x0 reg14=0x0 reg15=0x0
Resubmitted  odp: drop
Resubmitted megaflow: 
recirc_id=0,nsi=254,nsp=35,tun_dst=0.0.0.0,in_port=1,dl_type=0x
Rule: table=158 cookie=0xba5eba110101 
priority=655,nsi=254,nsp=35,in_port=1
OpenFlow 
actions=move:NXM_NX_NSH_MDTYPE[]->NXM_NX_NSH_MDTYPE[],move:NXM_NX_NSH_NP[]->NXM_NX_NSH_NP[],move:NXM_NX_NSH_C1[]->NXM_NX_NSH_C1[],move:NXM_NX_NSH_C2[]->NXM_NX_NSH_C2[],move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],load:0x4->NXM_NX_TUN_GPE_NP[],IN_PORT
output to native tunnel
native tunnel routing failed

Final flow: 
tun_src=0.0.0.0,tun_dst=192.168.0.26,tun_ipv6_src=::,tun_ipv6_dst=::,tun_gbp_id=0,tun_gbp_flags=0,tun_gpe_np=0x4,tun_gpe_flags=0,tun_tos=0,tun_ttl=0,tun_flags=0,in_port=1,vlan_tci=0x,dl_src=00:00:00:00:00:00,dl_dst=00:00:00:00:00:00,dl_type=0x
Megaflow: 
recirc_id=0,nsi=254,nsh_mdtype=0,nsh_np=0,nsp=35,nshc1=0,nshc2=0,tun_id=0/0x,tun_dst=0.0.0.0,tun_gpe_np=0,in_port=1,dl_type=0x
Datapath actions: drop

Please help me to resolve the issue.

Regards,
Srikanth.


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

[opnfv-tech-discuss] [netready] meeting minutes, March 1

[Georg Kunz]

Hi all,

Slides: 2017-03-01 weekly 
meeting.pptx

Minutes: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-netready/2017/opnfv-netready.2017-03-01-17.01.html
Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-netready/2017/opnfv-netready.2017-03-01-17.01.txt
Log: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-netready/2017/opnfv-netready.2017-03-01-17.01.log.html
Best regards
Georg
___
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-project-leads] [opnfvdocs] Documentation update for Danube release

[Serg Melikyan]

Sofia,

we have almost completed documentation for Fuel for Danube release (only
release notes update left): https://gerrit.opnfv.org/gerrit/29507

I've updated main documentation to link to the new Fuel docs:
https://gerrit.opnfv.org/gerrit/29523, please review.

On Sun, Feb 19, 2017 at 11:01 PM, Yujun Zhang (ZTE) <
zhangyujun+...@gmail.com> wrote:

> The url seems wrong. Fix proposed in https://gerrit.opnfv.org/
> gerrit/#/c/29027/
>
> On Fri, Feb 17, 2017 at 7:24 AM Stuart Mackie 
> wrote:
>
> Hi Sofia
>
>
>
> I am attempting to check out the docs toolchain.
>
>
>
> There’s an instruction in 1.8.1 of http://artifacts.opnfv.org/
> opnfvdocs/docs/how-to-use-docs/documentation-example.html that you have
> to submit a patch for jjb/opnfv/opnfv-docs.yml.
>
>
>
> Where is this file?
>
>
>
> Thanks
>
>
>
> Stuart
>
> -914 886 2534 <(914)%20886-2534>
>
>
>
> *From: * on behalf of Sofia
> Wallin 
> *Date: *Tuesday, February 14, 2017 at 10:40 AM
> *To: *"TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org)" <
> opnfv-tech-discuss@lists.opnfv.org>, "opnfv-project-le...@lists.opnfv.org"
> 
> *Subject: *Re: [opnfv-project-leads] [opnfv-tech-discuss] [opnfvdocs]
> Documentation update for Danube release
>
>
>
> Here is an example based on SFC for mapping existing documents to the new
> structure,
>
> https://docs.google.com/presentation/d/1_PszNevu1J7KK_
> 46p8K9L4y5AjbnDWnXfsxQN-SmETI/edit#slide=id.g20d735f830_0_0
>
>
>
> *Thanks Brady!*
>
>
>
> BR,
>
> Sofia
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Sofia Wallin
> *Sent:* den 7 februari 2017 14:26
> *To:* TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org) <
> opnfv-tech-discuss@lists.opnfv.org>; opnfv-project-le...@lists.opnfv.org
> *Subject:* [opnfv-tech-discuss] [opnfvdocs] Documentation update for
> Danube release
>
>
>
> *To all projects that plans to contribute with documentation to the Danube
> release.*
>
>
>
> Hi,
>
> As a reminder that documentation is part of the release even this time,
> following email contains some useful information and links.
>
>
>
> Since we are moving to read the docs
>  (NOTE: this page is still work
> in progress) for the Danube release some structural changes has been made.
> Please have a look at the wiki page linked below to make sure that you
> store your documentation according to directives.
>
>
>
> *Wiki*
>
> Information on general documentation handling can be found here
> 
>
>
>
> *Milestones relevant for documentation is MS6 and MS10.*
>
> MS6 17/2 – Preliminary documentation completed
>
> Documentation outlines or placeholders committed to repo for all project
> and release documentation
>
> MS10 24/3 – Documentation completed
>
> All project and release documentation reviewed and approved.
>
>
>
> Since we still haven’t manage to establish or communicate a review process
> for release related documentation it is important to always add one or two
> members from the docs project as reviewer on documentation related
> additions or changes.
>
>
>
> Everyone is welcome to join the docs meeting
>  held every second
> week.
>
>
>
> Regards,
>
> Sofia
> ___
> opnfv-project-leads mailing list
> opnfv-project-le...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-project-leads
>
> --
> Yujun Zhang
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>


-- 
Serg Melikyan, Customer Success Manager at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com | +1 (650) 440-8979
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [announce] E-release name survey

[Raymond Paik]

A quick reminder that the poll for E-release naming closes this Sunday

Thanks to Uli for noting that the top banner in the survey said "D-release"
and this has been corrected :-)  If you already voted, there's no need to
vote again.

Again the survey link is: https://www.surveymonkey.com/r/FCZ9C3L

Cheers,

Ray

On Sun, Feb 26, 2017 at 8:24 PM, Raymond Paik 
wrote:

> All,
>
> Here's the survey link for the E-release name: https://www.
> surveymonkey.com/r/FCZ9C3L
>
> Eleven E-river names were nominated, so you can rank your preference from
> 1 (top choice) to 11 (last choice).  The survey will remain open until 5pm
> Pacific Time on March 5th (Sunday).
>
> Happy voting
>
> 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] [SFC] Weekly meeting minutes, March 1

[Brady Allen Johnson]

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.2017-03-01-14.59.html


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

Re: [opnfv-tech-discuss] [daisy] Does Daisy Installer run in a VM?

[Julien]

Hi Fatih

Daisy can run on both environments. In OPNFV, it runs on a libvirt VM by
default. It has no requirements on the host OS, Ubuntu and CentOS both are
OK.

Thanks,
Julien



Fatih Degirmenci 于2017年3月1日周三 上午6:18写道：

Hi Daisy Team,



Can you please let us know if you run Daisy installer directly on Jumphost
or in a VM?



The reason for this question is that this is a goal of the Infra team so we
can help ensure some strategic things for CI/CD:

-  Jumphosts are stable, i.e. installers do not pollute the
jumphost (sometimes resulting in need to redeploy the jumphost)

-  Jumphosts are consistent, e.g. we can use a common Jumphost host
OS (e.g. Ubuntu) and run all installer ISOs in VMs on the jumphost

-  We can migrate to dynamic POD allocation, given the two
capabilities above



This is a key need of development lab users also, who probably don’t have
the automated tools for POD deployment such as OPNFV CI/CD uses, and who
can spend a lot of time having to reinstall jumphosts to switch between
OPNFV distros.



Does Daisy support the installer ISO being booted:

1)   in a libvirt (qemu+kvm) VM

2)   on a generic jumphost (i.e. Ubuntu or Centos)



/Fatih
___
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] [Compass4NFV] weekly meeting of Mar.2

[Justin chi]

Hi team,

Agenda of Mar.2 2017

   - Danube release ready
  - Danube release documentation review
 -
 
http://artifacts.opnfv.org/compass4nfv/docs/release_installation/index.html
 http://artifacts.opnfv.org/compass4nfv/docs/release_FAQ/index.html

 
http://artifacts.opnfv.org/compass4nfv/docs/release_release-notes/index.html
  - Stable branch date discuss
   - feature integration documentation draft review
   https://gerrit.opnfv.org/gerrit/#/c/29401/
   - K8s integration progress
   - Open discuss
   Weekly on Thursday at 0900 UTC
   IRC channel: #opnfv-compass4nfv


https://wiki.opnfv.org/display/meetings/Compass4nfv

Regards
Justin
___
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-project-leads] [release][danube][ovsnfv] MS6 compliance assessment

[Gray, Mark D]

Hi David,

Apologies for the delay. Here is the update for OVSNFV

Feature Projects

Please provide a list of commits for the following:

· Enabling testing for your project in the Functest repo (or other test 
framework repo if you are not using functest)
oWe don’t add any new test cases, we just run the standard functest and 
yardstick

· Test case implementation in your project repo.
oN/A. No new test cases are added. OVSNFV leverages standard OPNFV test 
cases

· Please indicate whether the scenarios with which your project is 
integrated are visible on the Functest dashboard 
(http://testresults.opnfv.org/dashboard/)   If not, why?
· Fuel scenarios are there, Apex are not (we will investigate)

Test Framework Projects
N/A

Preliminary Documentation Requirement
Document link(s):
http://artifacts.opnfv.org/ovsnfv/docs/buildprocedure/index.html
http://artifacts.opnfv.org/ovsnfv/docs/release/index.html
http://artifacts.opnfv.org/ovsnfv/docs/release_scenarios_os-nosdn-ovs/index.html
http://artifacts.opnfv.org/ovsnfv/docs/development_design/index.html
http://artifacts.opnfv.org/ovsnfv/docs/release_userguide/index.html
http://artifacts.opnfv.org/ovsnfv/docs/release_configguide/index.html
http://artifacts.opnfv.org/ovsnfv/docs/release_scenarios_os-nosdn-ovs-noha/index.html
http://artifacts.opnfv.org/ovsnfv/docs/release_release-notes/index.html


From: opnfv-project-leads-boun...@lists.opnfv.org 
[mailto:opnfv-project-leads-boun...@lists.opnfv.org] On Behalf Of David McBride
Sent: Wednesday, February 22, 2017 8:30 PM
To: opnfv-project-le...@lists.opnfv.org; TECH-DISCUSS OPNFV 

Subject: [opnfv-project-leads] [release][danube] MS6 compliance assessment

Team,

I'd like to request that the PTLs for projects participating in Danube respond 
to the following questions, designed to assess compliance with MS6.
Feature Projects
1.Please provide a list of commits for the following:
a. Enabling testing for your project in the Functest repo (or other test 
framework repo if you are not using functest)
b.Test case implementation in your project repo.
2.Please indicate whether the scenarios with which your project is 
integrated are visible on the Functest dashboard.  If not, why?
Test Framework Projects
1.Please provide a list of commits for your self-validation tests.
Preliminary Documentation Requirement
1.Please provide a link to the preliminary documentation for your project.


Let me know if you have any questions.

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [opnfvdocs] Feedback wanted on docs.opnfv.org

[Sofia Wallin]

Hi Georg,
We haven't really reached a final decision on the theme of the page. I have 
received some feedback on the current look and feel and I have also reached out 
to the marketing team. We should strive for a common way of publishing our 
documentation within OPNFV, meaning that colors and font should be aligned. My 
intention is that we already for the Danube release will reach some level of 
agreement and have all teams use a common look and feel.

BR,
Sofia

From: Georg Kunz
Sent: den 24 februari 2017 17:05
To: Sofia Wallin ; TECH-DISCUSS OPNFV 
(opnfv-tech-discuss@lists.opnfv.org) 
Subject: RE: [opnfv-tech-discuss] [opnfvdocs] Feedback wanted on docs.opnfv.org

Hi Sofia,

No immediate feedback on the structure, but the looks of the document.

Assuming that the current color theme is also meant for the final release of 
the documentation, I would like to ask if it is possible to choose a different 
color for the links (and potentially the text itself)? In the current color 
theme, it is quite hard to find the reddish links in the grey text. Yes, 
partially color blind person here. :)

Best regards
Georg

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Sofia Wallin
Sent: Thursday, February 23, 2017 5:05 PM
To: TECH-DISCUSS OPNFV 
(opnfv-tech-discuss@lists.opnfv.org) 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [opnfv-tech-discuss] [opnfvdocs] Feedback wanted on docs.opnfv.org

Hi all,
As communicated the docs project has the intention to divide the documentation 
into three different areas Release documentation, Test documentation and 
Development documentation [1].
I'm happy to see that we have received feedback around this and we want to 
broaden the discussion to agree on the best approach.
One suggestion that has been brought up is to divide the documentation into two 
areas, User documentation and Development documentation [2].

Please share your views and feedback to make sure that we together make 
docs.opnfv.org as useful as possible to those 
consuming our documentation!

Let me know what you think!

Thanks,
Sofia

[1]
Release documentation
Documentation aimed for OPNFV releases such as overview, installation guides, 
user guides, configuration guides.

Test documentation
To promote well-structured and well-written documentation

Development documentation
Project specific documentation such as design documentation, project overview 
or requirement documentation etc.

[2]
User documentation
Documentation aimed for OPNFV releases such as overview, installation guides, 
user guides, configuration guides including test documentation.

Development documentation
Project specific documentation such as design documentation, project overview 
or requirement documentation


___
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] [Danube] [Documentation] Organization of testing section

[morgan.richomme]

And just to precise - the last table from my first mail could be
mlisleading (we will exchange tomorrow during the weekly meeting)
you shall now create a docs/testing directory reflecting the target view
and put your docs there (as shown in Jose's patch)

in your repo
docs
├── release
│   └── release-notes
└── testing
├── developer
└── user

on docs.opnfv.org
we will get


Testing Documentation

  * Overview
  * User
  * Developper

In Overview we will have our umbrella document

in User, all the documents generated from /docs/testing/user

  * OPNFV FUNCTEST user guide


  * Bottlenecks - user guide


  * Yardstick Overview


  * VSPERF

  * .


in Developer, all the documents generated from /docs/testing/developer

we probably should also adopt some conventions for the title to be as
consistant as possible...

  user guide

 configuration guide

 developer guide

to be agreed tomorrow

/Morgan


 Le 01/03/2017 à 14:38, Jose Lausuch a écrit :
>
> Hi,
>
>  
>
> Functest already following this approach:
> https://gerrit.opnfv.org/gerrit/#/c/29151/
>
>  
>
> Thanks,
>
> Jose
>
>  
>
> *From:*Sofia Wallin
> *Sent:* Wednesday, March 01, 2017 14:11 PM
> *To:* morgan.richo...@orange.com; David McBride
> *Cc:* opnfv-tech-discuss@lists.opnfv.org; Yujun Zhang;
> mark.bei...@emc.com; Jose Lausuch; Cooper, Trevor; Yuyang (Gabriel);
> Gaoliang (D)
> *Subject:* RE: [OPNFV] [Danube] [Documentation] Organization of
> testing section
>
>  
>
> Hi Morgan,
>
> Yes – This is consistent with what we decided yesterday.
>
>  
>
> Thank you,
>
> Sofia
>
>  
>
> *From:*morgan.richo...@orange.com 
> [mailto:morgan.richo...@orange.com]
> *Sent:* den 1 mars 2017 08:27
> *To:* Sofia Wallin  >; David McBride
> mailto:dmcbr...@linuxfoundation.org>>
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> ; Yujun Zhang
> mailto:zhangyujun+...@gmail.com>>;
> mark.bei...@emc.com ; Jose Lausuch
> mailto:jose.laus...@ericsson.com>>;
> Cooper, Trevor  >; Yuyang (Gabriel)
> mailto:gabriel.yuy...@huawei.com>>;
> Gaoliang (D) mailto:jean.gaoli...@huawei.com>>
> *Subject:* [OPNFV] [Danube] [Documentation] Organization of testing
> section
>
>  
>
> Hi,
>
> during the last release meeting we had a discussion on the structure
> of the testing documentation for Danube
>
> we suggest to adopt the following approach for the test projects
>
> |/docs|
>
> ||_ release|
>
> |...|
> |   |_ release-notes // release note of the projects involved in the
> release|
> | reference
> http://testresults.opnfv.org/reporting snapshot of the status at the
> release date|
> |...|
> ||_ testing|
>
> |testing overview // umbrella document => figure, description of
> the testing ecosystem, pointers to project documentation|
> ||__ user // will collect the documentation of the test
> projects allowing the end user to perform testing towards a OPNFV SUT|
> | e.g.
> Functest/Yardstick/Vsperf/Storperf/Bottlenecks/Qtip
> installation/config & user guides|
> ||__ developer// will collect documentation to explain how to
> create your own test case and leverage existing testing frameworks|
> | e.g. devloper guides|
>
>
>
> the umbrella testing documentation "testing overview" is under
> opnfvdocs => will be put into /testing
>
> the other documents are in the project repos under
> /docs
> /installation guide
> /config guide
> /user guide
> /release note
> /development
> /development guide
> / interships
>
> --
> |  Test Project Repo   |   Target in
> docs.opnfv.org  |   
> --
> | installation, config, user guide| 
> testing/user  |
> | development guide |  testing/developer |
> | release note| 
> release-notes/testing   |
> --
>
> @Sofia, David: is it OK for you?
>
> Morgan
>
> _
>  
> Ce message et ses pieces jointes peu

Re: [opnfv-tech-discuss] [OPNFV] [Danube] [Documentation] Organization of testing section

[Jose Lausuch]

Hi,

Functest already following this approach: 
https://gerrit.opnfv.org/gerrit/#/c/29151/

Thanks,
Jose

From: Sofia Wallin
Sent: Wednesday, March 01, 2017 14:11 PM
To: morgan.richo...@orange.com; David McBride
Cc: opnfv-tech-discuss@lists.opnfv.org; Yujun Zhang; mark.bei...@emc.com; Jose 
Lausuch; Cooper, Trevor; Yuyang (Gabriel); Gaoliang (D)
Subject: RE: [OPNFV] [Danube] [Documentation] Organization of testing section

Hi Morgan,
Yes – This is consistent with what we decided yesterday.

Thank you,
Sofia

From: morgan.richo...@orange.com 
[mailto:morgan.richo...@orange.com]
Sent: den 1 mars 2017 08:27
To: Sofia Wallin mailto:sofia.wal...@ericsson.com>>; 
David McBride 
mailto:dmcbr...@linuxfoundation.org>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org; 
Yujun Zhang mailto:zhangyujun+...@gmail.com>>; 
mark.bei...@emc.com; Jose Lausuch 
mailto:jose.laus...@ericsson.com>>; Cooper, Trevor 
mailto:trevor.coo...@intel.com>>; Yuyang (Gabriel) 
mailto:gabriel.yuy...@huawei.com>>; Gaoliang (D) 
mailto:jean.gaoli...@huawei.com>>
Subject: [OPNFV] [Danube] [Documentation] Organization of testing section


Hi,

during the last release meeting we had a discussion on the structure of the 
testing documentation for Danube

we suggest to adopt the following approach for the test projects
/docs
|_ release
...
   |_ release-notes // release note of the projects involved in the release
 reference http://testresults.opnfv.org/reporting 
snapshot of the status at the release date
...
|_ testing
testing overview // umbrella document => figure, description of the testing 
ecosystem, pointers to project documentation
|__ user // will collect the documentation of the test projects 
allowing the end user to perform testing towards a OPNFV SUT
 e.g. Functest/Yardstick/Vsperf/Storperf/Bottlenecks/Qtip 
installation/config & user guides
|__ developer// will collect documentation to explain how to create 
your own test case and leverage existing testing frameworks
 e.g. devloper guides


the umbrella testing documentation "testing overview" is under opnfvdocs => 
will be put into /testing

the other documents are in the project repos under
/docs
/installation guide
/config guide
/user guide
/release note
/development
/development guide
/ interships

--
|  Test Project Repo   |   Target in docs.opnfv.org  |
--
| installation, config, user guide|  testing/user  |
| development guide |  testing/developer |
| release note|  release-notes/testing   |
--

@Sofia, David: is it OK for you?

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

[opnfv-tech-discuss] [SFC] Weekly meeting agenda, March 1

[Brady Allen Johnson]

Here's the agenda for today's weekly meeting:


  *   CI stability
  *   symmetric_chain testcase problems, and way forward
  *   Milestone 7 preparations
  *   Current tasks/status
  *   Upcoming OPNFV PlugTest in Paris

Brady

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

Re: [opnfv-tech-discuss] Quick follow-up from the Plugfest planning call

[MORTON, ALFRED C (AL)]

Hi Ray and Plugtesters,

Apologies for missing Monday’s meeting
(Jury Duty is a Civic responsibility,
but makes attending some meetings impossible).

Regarding test cases, I wonder if the Scope of
testing has been decided, and whether a
*performance-oriented* test case might be entertained
this time?  This topic has been out of scope in the
previous Plugfests and ETSI CTI’s Plugtest™, AFAIK.

It may still be too soon, but it’s worth asking now.

regards,
Al

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Wednesday, March 01, 2017 1:21 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Quick follow-up from the Plugfest planning call

All,

A few things after our call on Monday

First, I realized that I had sent out a recurring weekly meeting for Plugfest 
planning when this is supposed to be a bi-weekly meeting.  I will go ahead and 
cancel the current series and start a new one that starts on March 13th.  (so 
the upcoming meetings are March 13/27 plus April 10th).  Apologies for the 
thrash, but you can also find the upcoming meeting info. at 
https://wiki.opnfv.org/display/EVNT/Plugfest+-+Danube+Release#Plugfest-DanubeRelease-PlugfestPlanningMeetings

Second, I started a test cases page at 
https://wiki.opnfv.org/display/EVNT/Danube+Plugfest+Test+Cases.
  I followed the template from the last Plugfest, but as you can see it's just 
a skeleton.  I encourage everyone (esp. those who were on the call yesterday) 
to contribute ideas/suggestions for what we should focus on for the upcoming 
Plugfest.

Finally, a reminder that the Plugfest is open to both members & non-members of 
OPNFV.  You can register at 
https://www.regonline.com/OPNFVPlugfestApril2017

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] [netready] Agenda for today's meeting

[Georg Kunz]

Hi all,

This is the agenda for today's meeting:


* Gluon integration

* OPNFV documentation

* Update on requirements document

* Gluon lab status

* PoC planning for OpenStack and OPNFV summit

* Hackfest planning

* AOB

Best regards
Georg
___
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] [Danube] [Documentation] Organization of testing section

[Sofia Wallin]

Hi Morgan,
Yes – This is consistent with what we decided yesterday.

Thank you,
Sofia

From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com]
Sent: den 1 mars 2017 08:27
To: Sofia Wallin ; David McBride 

Cc: opnfv-tech-discuss@lists.opnfv.org; Yujun Zhang ; 
mark.bei...@emc.com; Jose Lausuch ; Cooper, Trevor 
; Yuyang (Gabriel) ; 
Gaoliang (D) 
Subject: [OPNFV] [Danube] [Documentation] Organization of testing section


Hi,

during the last release meeting we had a discussion on the structure of the 
testing documentation for Danube

we suggest to adopt the following approach for the test projects
/docs
|_ release
...
   |_ release-notes // release note of the projects involved in the release
 reference http://testresults.opnfv.org/reporting 
snapshot of the status at the release date
...
|_ testing
testing overview // umbrella document => figure, description of the testing 
ecosystem, pointers to project documentation
|__ user // will collect the documentation of the test projects 
allowing the end user to perform testing towards a OPNFV SUT
 e.g. Functest/Yardstick/Vsperf/Storperf/Bottlenecks/Qtip 
installation/config & user guides
|__ developer// will collect documentation to explain how to create 
your own test case and leverage existing testing frameworks
 e.g. devloper guides


the umbrella testing documentation "testing overview" is under opnfvdocs => 
will be put into /testing

the other documents are in the project repos under
/docs
/installation guide
/config guide
/user guide
/release note
/development
/development guide
/ interships

--
|  Test Project Repo   |   Target in docs.opnfv.org  |
--
| installation, config, user guide|  testing/user  |
| development guide |  testing/developer |
| release note|  release-notes/testing   |
--

@Sofia, David: is it OK for you?

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

[opnfv-tech-discuss] [multisite]weekly meeting of Mar.2

[joehuang]

Hello, team,

Agenda of Mar.2 2017

* Functest issue.
* D-release preparation.
* 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

[opnfv-tech-discuss] [dovetail]dovetail weekly meeting 3/3

[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=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='Shobhan A
 yyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Canio Cil
 lis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Marco Var
 lese':MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Kedalagud
 de, Meghashree Dattatri'":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Lawrence 
 Lamers':MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Georg Kun
 z':MAILTO:georg.k...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Maria Toe
 roe':MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Rathnakum
 ar Kayyar':MAILTO:rkay...@lcnpl.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Gabor Hal
 ász':MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Pierre Lyn
 ch:MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=rgrigar@li
 nuxfoundation.org:MAILTO:rgri...@linuxfoundation.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ganesh Raj
 an:MAILTO:gan...@pensanetworks.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ahmed Elbo
 rnou (amaged):MAILTO:ama...@cisco.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Csatari, G
 ergely (Nokia - HU/Budapest)":MAILTO:gergely.csat...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
DESCRIPTION;LANGUAGE=zh-CN:时间: 2017年3月3日星期五 22:00-23:00(UTC
 +08:00)北京，重庆，香港特别行政区，乌鲁木齐。\n\n注意
 : 以上 GMT 时差并不反映夏令时调整。\n\n*~*~*~*~*~*~*~*~*~*\n
 \nHi all:\n\nLast week\, we have hot topic for the discussion on the dovet
 ail plan. Let us continue and have efficient plan for dovetail.\n\nThe age
 nda for this week:\n\n1）  dovetail development plan\na)  CVP str
 ategy\, cooperation with OPNFV and inter WG of opentstack. Test result col
 lection mechanism---Chris price Jose\nb)  Dovetail Danube plan-wenjing
 \ni.  https://etherpad.opnfv.org/p/Dovetail_Danube_Planning\nc)  j
 ira consensus and approach-bryan and Lincoln\n2）Test case run results hi
 story info gathering and display - Matthew\n3）update of authentication f
 or dovetail tool --leo\n4）jenkins jobs reqirement for dovetail--
 -uli from infra group\n5）Other open issues: https://etherpad.opnfv.org/p
 /collabrationofd