Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 28 Feb 2018 (ww57)

[Klozik, MartinX]

Hi,

so there are still no results at Fraser reporting page, even after successful 
run of Fraser specific daily job.

I’ve checked that :

1)  VSPERF successfully reported test results from fraser as PASSed:

http://testresults.opnfv.org/test/api/v1/results?project=vsperf_tag=jenkins-vswitchperf-daily-fraser-7

2)  The code takes into account version from the build tag

https://git.opnfv.org/releng-testresults/tree/reporting/reporting/vsperf/reporting-status.py#n31

Can anybody have a more detailed look, to check what is going on?

Note: I can see, that reporting pages for Euphrates and Master do not work at 
all for VSPERF and some other projects too.

Best Regards,
Martin

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Klozik, MartinX
Sent: Tuesday, April 24, 2018 9:06 AM
To: David McBride <dmcbr...@linuxfoundation.org>; Cooper, Trevor 
<trevor.coo...@intel.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 
28 Feb 2018 (ww57)

Due to issues with IXIA licenses, the vsperf CI was not working since 01/2018. 
Thus it was never executed for Fraser and there aren’t any results to be 
displayed.

Once CI run for master branch will finish successfully, then execution of 
Fraser CI daily job can be triggered manually. After that results should be 
visible at reporting page.

Regards,
Martin

From: David McBride [mailto:dmcbr...@linuxfoundation.org]
Sent: Tuesday, April 24, 2018 5:23 AM
To: Cooper, Trevor <trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>>
Cc: Klozik, MartinX 
<martinx.klo...@intel.com<mailto:martinx.klo...@intel.com>>; Rao, Sridhar 
<sridhar@spirent.com<mailto:sridhar@spirent.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 
28 Feb 2018 (ww57)

What's going on with the VSPerf test results page?

http://testresults.opnfv.org/reporting/fraser/vsperf/reporting.html

On Mon, Apr 23, 2018 at 2:48 PM, Cooper, Trevor 
<trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>> wrote:
Looks like CI is back in business, was able to resolve license issues through a 
Webex session with Ixia looking at log files :)

Trevor

From: Cooper, Trevor
Sent: Friday, March 30, 2018 2:44 PM
To: Klozik, MartinX 
<martinx.klo...@intel.com<mailto:martinx.klo...@intel.com>>; Rao, Sridhar 
<sridhar@spirent.com<mailto:sridhar@spirent.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: 'ALFRED C 'MORTON (AL)'' <acmor...@att.com<mailto:acmor...@att.com>>; 'Mars 
Toktonaliev (Nokia - US/Irving)' 
<mars.toktonal...@nokia.com<mailto:mars.toktonal...@nokia.com>>; Ferriter, Cian 
<cian.ferri...@intel.com<mailto:cian.ferri...@intel.com>>; Christian Trautman 
(ctrau...@redhat.com<mailto:ctrau...@redhat.com>) 
<ctrau...@redhat.com<mailto:ctrau...@redhat.com>>; Bill Michalowski 
(bmich...@redhat.com<mailto:bmich...@redhat.com>) 
<bmich...@redhat.com<mailto:bmich...@redhat.com>>; Elias, RichardX 
<richardx.el...@intel.com<mailto:richardx.el...@intel.com>>; Alec Hothan 
(ahothan) <ahot...@cisco.com<mailto:ahot...@cisco.com>>; 
eddie.arr...@huawei.com<mailto:eddie.arr...@huawei.com>
Subject: RE: [vsperf] Agenda for VSPERF weekly meeting - 28 Feb 2018 (ww57)

Hi Sridhar, Martin

I have installed new Ixia licenses in POD 12 and updated the tickets. I had to 
restart node-3 too and triggered the Jenkins daily job. Looks like OVS_vanilla 
test just failed to execute. Can you take a look? 
https://build.opnfv.org/ci/view/vswitchperf/job/vswitchperf-daily-master/lastBuild/console

/Trevor



From: Klozik, MartinX
Sent: Wednesday, February 28, 2018 4:00 AM
To: Rao, Sridhar <sridhar@spirent.com<mailto:sridhar@spirent.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: 'ALFRED C 'MORTON (AL)'' <acmor...@att.com<mailto:acmor...@att.com>>; 
Cooper, Trevor <trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>>; 'Mars 
Toktonaliev (Nokia - US/Irving)' 
<mars.toktonal...@nokia.com<mailto:mars.toktonal...@nokia.com>>; Ferriter, Cian 
<cian.ferri...@intel.com<mailto:cian.ferri...@intel.com>>; Christian Trautman 
(ctrau...@redhat.com<mailto:ctrau...@redhat.com>) 
<ctrau...@redhat.com<mailto:ctrau...@redhat.com>>; Bill Michalowski 
(bmich...@redhat.com<mailto:bmich...@redhat.com>) 
<bmich...@redhat.com<mailto:bmich...@redhat.com>>; Elias, RichardX 
<richardx.el...@intel.com<mailto:richardx.el...@intel.com>>; Alec Hothan 
(ahothan) <ahot...@cisco.com<mailto:ahot...@cisco.com>

Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 28 Feb 2018 (ww57)

[Klozik, MartinX]

Due to issues with IXIA licenses, the vsperf CI was not working since 01/2018. 
Thus it was never executed for Fraser and there aren’t any results to be 
displayed.

Once CI run for master branch will finish successfully, then execution of 
Fraser CI daily job can be triggered manually. After that results should be 
visible at reporting page.

Regards,
Martin

From: David McBride [mailto:dmcbr...@linuxfoundation.org]
Sent: Tuesday, April 24, 2018 5:23 AM
To: Cooper, Trevor <trevor.coo...@intel.com>
Cc: Klozik, MartinX <martinx.klo...@intel.com>; Rao, Sridhar 
<sridhar@spirent.com>; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 
28 Feb 2018 (ww57)

What's going on with the VSPerf test results page?

http://testresults.opnfv.org/reporting/fraser/vsperf/reporting.html

On Mon, Apr 23, 2018 at 2:48 PM, Cooper, Trevor 
<trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>> wrote:
Looks like CI is back in business, was able to resolve license issues through a 
Webex session with Ixia looking at log files :)

Trevor

From: Cooper, Trevor
Sent: Friday, March 30, 2018 2:44 PM
To: Klozik, MartinX 
<martinx.klo...@intel.com<mailto:martinx.klo...@intel.com>>; Rao, Sridhar 
<sridhar@spirent.com<mailto:sridhar@spirent.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: 'ALFRED C 'MORTON (AL)'' <acmor...@att.com<mailto:acmor...@att.com>>; 'Mars 
Toktonaliev (Nokia - US/Irving)' 
<mars.toktonal...@nokia.com<mailto:mars.toktonal...@nokia.com>>; Ferriter, Cian 
<cian.ferri...@intel.com<mailto:cian.ferri...@intel.com>>; Christian Trautman 
(ctrau...@redhat.com<mailto:ctrau...@redhat.com>) 
<ctrau...@redhat.com<mailto:ctrau...@redhat.com>>; Bill Michalowski 
(bmich...@redhat.com<mailto:bmich...@redhat.com>) 
<bmich...@redhat.com<mailto:bmich...@redhat.com>>; Elias, RichardX 
<richardx.el...@intel.com<mailto:richardx.el...@intel.com>>; Alec Hothan 
(ahothan) <ahot...@cisco.com<mailto:ahot...@cisco.com>>; 
eddie.arr...@huawei.com<mailto:eddie.arr...@huawei.com>
Subject: RE: [vsperf] Agenda for VSPERF weekly meeting - 28 Feb 2018 (ww57)

Hi Sridhar, Martin

I have installed new Ixia licenses in POD 12 and updated the tickets. I had to 
restart node-3 too and triggered the Jenkins daily job. Looks like OVS_vanilla 
test just failed to execute. Can you take a look? 
https://build.opnfv.org/ci/view/vswitchperf/job/vswitchperf-daily-master/lastBuild/console

/Trevor



From: Klozik, MartinX
Sent: Wednesday, February 28, 2018 4:00 AM
To: Rao, Sridhar <sridhar@spirent.com<mailto:sridhar@spirent.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: 'ALFRED C 'MORTON (AL)'' <acmor...@att.com<mailto:acmor...@att.com>>; 
Cooper, Trevor <trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>>; 'Mars 
Toktonaliev (Nokia - US/Irving)' 
<mars.toktonal...@nokia.com<mailto:mars.toktonal...@nokia.com>>; Ferriter, Cian 
<cian.ferri...@intel.com<mailto:cian.ferri...@intel.com>>; Christian Trautman 
(ctrau...@redhat.com<mailto:ctrau...@redhat.com>) 
<ctrau...@redhat.com<mailto:ctrau...@redhat.com>>; Bill Michalowski 
(bmich...@redhat.com<mailto:bmich...@redhat.com>) 
<bmich...@redhat.com<mailto:bmich...@redhat.com>>; Elias, RichardX 
<richardx.el...@intel.com<mailto:richardx.el...@intel.com>>; Alec Hothan 
(ahothan) <ahot...@cisco.com<mailto:ahot...@cisco.com>>; 
eddie.arr...@huawei.com<mailto:eddie.arr...@huawei.com>
Subject: RE: [vsperf] Agenda for VSPERF weekly meeting - 28 Feb 2018 (ww57)

Hi Sridhar,

just a note about VSPERF CI. IXIA is still not working. I’ve also noticed, that 
Windows VM 10.10.120.6 (where IxNetwork should be running) is not available.

So currently we have two INFRA tickets, which have to be solved to bring our 
daily jobs up again:

INFRA-215<https://jira.opnfv.org/browse/INFRA-215>

Ixia: License Error - No perpetual framework license found on chassis 
10.10.50.6<https://jira.opnfv.org/browse/INFRA-215>



INFRA-220<https://jira.opnfv.org/browse/INFRA-220>

Windows VM (10.10.120.6) dedicated to POD12 is not 
reachable<https://jira.opnfv.org/browse/INFRA-220>


Best Regards,
Martin

From: Rao, Sridhar [mailto:sridhar@spirent.com]
Sent: Wednesday, February 28, 2018 5:00 AM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: 'ALFRED C 'MORTON (AL)'' <acmor...@att.com<mailto:acmor...@att.com>>; 
Cooper, Trevor <trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>>; 'Mars 
Toktonaliev (Nokia - US/Irving)' 
<mars.toktonal...@nokia.com<mailto:mars.toktonal...@nokia.com

[opnfv-tech-discuss] [VSPERF] Farewell

[Klozik, MartinX]

Dear VSPERFers,

let me inform you, that both Richard and me will be transferred to a different 
project starting from May. It means that we won't be able to actively 
participate on VSPERF development anymore.

I would like to thank you for a very friendly atmosphere within VSPERF 
community. It was a pleasure to work with you.

Best Regards,
Martin & Richard

--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 28 Feb 2018 (ww57)

[Klozik, MartinX]

Hi Trevor,

as far as I can see, the root cause of the failure is still the same. It means, 
that there is something wrong with IXIA license and IXIA doesn’t work. Thus all 
testcases fail.

You could check it yourself at VM 10.10.120.6 in IxNetwork error log. You’ll 
find there a message listed in INFRA-215.

INFRA-215<https://jira.opnfv.org/browse/INFRA-215>

Ixia: License Error - No perpetual framework license found on chassis 
10.10.50.6<https://jira.opnfv.org/browse/INFRA-215>


Best Regards,
Martin

From: Cooper, Trevor
Sent: Friday, March 30, 2018 11:44 PM
To: Klozik, MartinX <martinx.klo...@intel.com>; Rao, Sridhar 
<sridhar@spirent.com>; opnfv-tech-discuss@lists.opnfv.org
Cc: 'ALFRED C 'MORTON (AL)'' <acmor...@att.com>; 'Mars Toktonaliev (Nokia - 
US/Irving)' <mars.toktonal...@nokia.com>; Ferriter, Cian 
<cian.ferri...@intel.com>; Christian Trautman (ctrau...@redhat.com) 
<ctrau...@redhat.com>; Bill Michalowski (bmich...@redhat.com) 
<bmich...@redhat.com>; Elias, RichardX <richardx.el...@intel.com>; Alec Hothan 
(ahothan) <ahot...@cisco.com>; eddie.arr...@huawei.com
Subject: RE: [vsperf] Agenda for VSPERF weekly meeting - 28 Feb 2018 (ww57)

Hi Sridhar, Martin

I have installed new Ixia licenses in POD 12 and updated the tickets. I had to 
restart node-3 too and triggered the Jenkins daily job. Looks like OVS_vanilla 
test just failed to execute. Can you take a look? 
https://build.opnfv.org/ci/view/vswitchperf/job/vswitchperf-daily-master/lastBuild/console

/Trevor



From: Klozik, MartinX
Sent: Wednesday, February 28, 2018 4:00 AM
To: Rao, Sridhar <sridhar@spirent.com<mailto:sridhar@spirent.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: 'ALFRED C 'MORTON (AL)'' <acmor...@att.com<mailto:acmor...@att.com>>; 
Cooper, Trevor <trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>>; 'Mars 
Toktonaliev (Nokia - US/Irving)' 
<mars.toktonal...@nokia.com<mailto:mars.toktonal...@nokia.com>>; Ferriter, Cian 
<cian.ferri...@intel.com<mailto:cian.ferri...@intel.com>>; Christian Trautman 
(ctrau...@redhat.com<mailto:ctrau...@redhat.com>) 
<ctrau...@redhat.com<mailto:ctrau...@redhat.com>>; Bill Michalowski 
(bmich...@redhat.com<mailto:bmich...@redhat.com>) 
<bmich...@redhat.com<mailto:bmich...@redhat.com>>; Elias, RichardX 
<richardx.el...@intel.com<mailto:richardx.el...@intel.com>>; Alec Hothan 
(ahothan) <ahot...@cisco.com<mailto:ahot...@cisco.com>>; 
eddie.arr...@huawei.com<mailto:eddie.arr...@huawei.com>
Subject: RE: [vsperf] Agenda for VSPERF weekly meeting - 28 Feb 2018 (ww57)

Hi Sridhar,

just a note about VSPERF CI. IXIA is still not working. I’ve also noticed, that 
Windows VM 10.10.120.6 (where IxNetwork should be running) is not available.

So currently we have two INFRA tickets, which have to be solved to bring our 
daily jobs up again:

INFRA-215<https://jira.opnfv.org/browse/INFRA-215>

Ixia: License Error - No perpetual framework license found on chassis 
10.10.50.6<https://jira.opnfv.org/browse/INFRA-215>



INFRA-220<https://jira.opnfv.org/browse/INFRA-220>

Windows VM (10.10.120.6) dedicated to POD12 is not 
reachable<https://jira.opnfv.org/browse/INFRA-220>


Best Regards,
Martin

From: Rao, Sridhar [mailto:sridhar@spirent.com]
Sent: Wednesday, February 28, 2018 5:00 AM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: 'ALFRED C 'MORTON (AL)'' <acmor...@att.com<mailto:acmor...@att.com>>; 
Cooper, Trevor <trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>>; 'Mars 
Toktonaliev (Nokia - US/Irving)' 
<mars.toktonal...@nokia.com<mailto:mars.toktonal...@nokia.com>>; Ferriter, Cian 
<cian.ferri...@intel.com<mailto:cian.ferri...@intel.com>>; Klozik, MartinX 
<martinx.klo...@intel.com<mailto:martinx.klo...@intel.com>>; Christian Trautman 
(ctrau...@redhat.com<mailto:ctrau...@redhat.com>) 
<ctrau...@redhat.com<mailto:ctrau...@redhat.com>>; Bill Michalowski 
(bmich...@redhat.com<mailto:bmich...@redhat.com>) 
<bmich...@redhat.com<mailto:bmich...@redhat.com>>; Elias, RichardX 
<richardx.el...@intel.com<mailto:richardx.el...@intel.com>>; Alec Hothan 
(ahothan) <ahot...@cisco.com<mailto:ahot...@cisco.com>>; 
eddie.arr...@huawei.com<mailto:eddie.arr...@huawei.com>
Subject: [vsperf] Agenda for VSPERF weekly meeting - 28 Feb 2018 (ww57)

Agenda


  1.  Development Update.
  2.  Discussion: NFVi forwarding performance & compliance (verification) 
program. Performance Efficiency scoring.

Meeting minutes

  *   WW56 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2018/opnfv-vswitchperf.2018-02-14-15.58.html
  *   WW55 
http://ircbot.w

Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 07 Mar 2018 (ww58)

[Klozik, MartinX]

Hi Sridhar,

two notes regarding development updates from my side:

1)  CI is still not working - details in INFRA-215 and INFRA-220 (@Trevor - 
could you help us with these issues?)

2)  I've 3 patches at OPNFV gerrit waiting for review. My college Richard 
Elias has prepared a patch to enhance "--test-params" functionality and to 
compare (optional) results of several tests in tabular form. Patch will be send 
for review in next days.

Best Regards,
Martin

From: Rao, Sridhar [mailto:sridhar@spirent.com]
Sent: Tuesday, March 6, 2018 10:37 PM
To: opnfv-tech-discuss@lists.opnfv.org
Cc: 'ALFRED C 'MORTON (AL)'' <acmor...@att.com>; Cooper, Trevor 
<trevor.coo...@intel.com>; 'Mars Toktonaliev (Nokia - US/Irving)' 
<mars.toktonal...@nokia.com>; Ferriter, Cian <cian.ferri...@intel.com>; Klozik, 
MartinX <martinx.klo...@intel.com>; Christian Trautman (ctrau...@redhat.com) 
<ctrau...@redhat.com>; Bill Michalowski (bmich...@redhat.com) 
<bmich...@redhat.com>; Elias, RichardX <richardx.el...@intel.com>; Alec Hothan 
(ahothan) <ahot...@cisco.com>; eddie.arr...@huawei.com; Jose Angel Lausuch 
<jalaus...@suse.com>
Subject: [vsperf] Agenda for VSPERF weekly meeting - 07 Mar 2018 (ww58)

Hi,

Agenda:

  1.  Development Updates .
  2.  Recap of last week's discussion - action review.
  3.  VSPERF results Plotting  - Yardstick-Grafana. (Jose, you can share your 
queries/inputs/requests).
  4.  This week's discussion: VSPERF and Cloud-native NFV (Containerized NFV). 
We need Your inputs !!

Today's meeting would be chaired by Trevor Cooper.

Meeting minutes

  *   WW57 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2018/opnfv-vswitchperf.2018-02-28-15.57.html
  *   WW56 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2018/opnfv-vswitchperf.2018-02-14-15.58.html
  *   WW55 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2018/opnfv-vswitchperf.2018-02-07-15.59.html



Time: Wednesday UTC 16h00, Ireland (UTC) 16h00, PST 8h00 (UTC/GMT -8)

IRC: freenode https://freenode.net/ channel: #opnfv-vswitchperf 
http://webchat.freenode.net/?channels=opnfv-vswitchperf

Audio: https://global.gotomeeting.com/join/391235029
You can also dial in using your phone.  United States: +1 (571) 317-3116  
Access Code: 391-235-029
Phone numbers from other countries are here ... 
https://wiki.opnfv.org/display/meetings


Regards,
Sridhar K. N. Rao (Ph. D)
Architect
+91-9900088064




Spirent Communications e-mail confidentiality.

This e-mail contains confidential and / or privileged information belonging to 
Spirent Communications plc, its affiliates and / or subsidiaries. If you are 
not the intended recipient, you are hereby notified that any disclosure, 
copying, distribution and / or the taking of any action based upon reliance on 
the contents of this transmission is strictly forbidden. If you have received 
this message in error please notify the sender by return e-mail and delete it 
from your system.

Spirent Communications plc
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, 
United Kingdom.

Or if within the US,

Spirent Communications,
27349 Agoura Road, Calabasas, CA, 91301, USA.
Tel No. 1-818-676- 2300
--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 20 Dec 2017 (ww50)

[Klozik, MartinX]

Hi All,

I won't be able to participate on our meeting today. During last week, I've 
performed a few reviews and send a small patch for delayed connection to the 
trafficgen.

Best Regards,
Martin

From: Rao, Sridhar [mailto:sridhar@spirent.com]
Sent: Wednesday, December 20, 2017 7:07 AM
To: opnfv-tech-discuss@lists.opnfv.org
Cc: 'ALFRED C 'MORTON (AL)'' <acmor...@att.com>; Cooper, Trevor 
<trevor.coo...@intel.com>; 'Mars Toktonaliev (Nokia - US/Irving)' 
<mars.toktonal...@nokia.com>; Ferriter, Cian <cian.ferri...@intel.com>; Klozik, 
MartinX <martinx.klo...@intel.com>; Christian Trautman (ctrau...@redhat.com) 
<ctrau...@redhat.com>; Bill Michalowski (bmich...@redhat.com) 
<bmich...@redhat.com>; Elias, RichardX <richardx.el...@intel.com>; Alec Hothan 
(ahothan) <ahot...@cisco.com>
Subject: [vsperf] Agenda for VSPERF weekly meeting - 20 Dec 2017 (ww50)

Hi All,

The agenda for this week:

  1.  Development update.
  2.  TGAAS discussion.
  3.  ???

Meeting minutes

  *   WW49 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-12-13-16.00.html
  *   WW48  
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-11-29-16.14.html
  *   WW47 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-11-22-16.02.html


Time: Wednesday UTC 16h00, Ireland (UTC) 16h00, PST 8h00 (UTC/GMT -8)

IRC: freenode https://freenode.net/ channel: #opnfv-vswitchperf 
http://webchat.freenode.net/?channels=opnfv-vswitchperf

Audio: https://global.gotomeeting.com/join/391235029
You can also dial in using your phone.  United States: +1 (571) 317-3116  
Access Code: 391-235-029
Phone numbers from other countries are here ... 
https://wiki.opnfv.org/display/meetings


Regards,
Sridhar K. N. Rao (Ph. D)
Architect
+91-9900088064




Spirent Communications e-mail confidentiality.

This e-mail contains confidential and / or privileged information belonging to 
Spirent Communications plc, its affiliates and / or subsidiaries. If you are 
not the intended recipient, you are hereby notified that any disclosure, 
copying, distribution and / or the taking of any action based upon reliance on 
the contents of this transmission is strictly forbidden. If you have received 
this message in error please notify the sender by return e-mail and delete it 
from your system.

Spirent Communications plc
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, 
United Kingdom.

Or if within the US,

Spirent Communications,
27349 Agoura Road, Calabasas, CA, 91301, USA.
Tel No. 1-818-676- 2300
--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 13 Dec 2017 (ww49)

[Klozik, MartinX]

Hi All,

I won't be able to join today. During last weeks I was trying to fix our CI 
jobs, which was a bit more challenging than expected. There are two separate 
issues:


1)  VERIFY & MERGE jobs - there are issues with execution of VPP testcases 
at ericcson-build3 machine. Thus some time ago I changed configuration of 
VERIFY & MERGE jobs to be executed at ericsson-build4 machine. For some time it 
worked, but then VPP has failed and it is not working there at all. In order to 
be able to pass gerrit verification of new patches, I had to disable VPP tests 
- it means that if vppctl is not able to connect to running VPP, then VPP tests 
are skipped to avoid verification failure. As I'm not able to connect to this 
server I can't find the root cause. The easiest "solution" is to reboot that 
server. I've asked responsible admins for help some time ago, but I've not 
heard from them for some time now.

So I tried another approach, it means to allow execution of VERIFY & MERGE jobs 
at our intel-pod12. I've changed priorities, so Jenkins would firstly check if 
pod12 is idle with fallback to ericsson-build4 machine. Patch is available at 
gerrit and waiting for review from releng team:

https://gerrit.opnfv.org/gerrit/#/c/47581/

2)  DAILY job execution always failed after POD12 was moved to the new 
location; The reason was crash and reboot of node2 during execution of Ovs 
Vanilla testcases. It took me a while to find a root cause, which is actually a 
kernel crash during removal of "openvswitch.ko" kernel module. Originally I 
though, that it is caused by some resources allocated by OVS, which were not 
cleared properly after OVS shutdown. However it happens also in case, that OVS 
is not started at all. I was able to reproduce it on node2 (CentOS7.3) just by 
calling insmod and rmmod on openvswitch kernel module several times. Sometimes 
machine crashes after a few attempts, other time it takes more than 10 
iterations of insmod/rmmod. I tried 2 different 3.10.0-xxx kernel versions and 
two different OVS versions with the same output. It seems, that it is specific 
to RHT's patched 3.10 kernel. In case that the same OVS version is used with 
4.x kernel, then system is stable (I was able to run several dozens of 
insmod/rmmod iterations without any issue). Thus I've installed kernel-lt from 
elrepo.org to node2, to be able to run our daily job successfully.

With 4.4 kernel, I was able to execute both vswitchperf-daily-master and 
vswitchperf-daily-euphrates several times. Unfortunately it has failed again 
recently, but this time during execution of VPP TCs. One time VPP was not able 
to acquire one NIC. Second time boot of VM was very slow and compilation of 
testpmd took over 30s (it normally takes about 8s). Let's see if these 
incidents will happen more often or not.

Also some performance figures are varying. For example pvp_tput executed 
manually at node2 measures over 11 mil. FPS, but during daily job execution, it 
often measures about 7 or 8. This needs some further investigation to find the 
root cause.


Best Regards,
Martin

From: Rao, Sridhar [mailto:sridhar@spirent.com]
Sent: Wednesday, December 13, 2017 6:22 AM
To: opnfv-tech-discuss@lists.opnfv.org
Cc: 'ALFRED C 'MORTON (AL)'' <acmor...@att.com>; Cooper, Trevor 
<trevor.coo...@intel.com>; 'Mars Toktonaliev (Nokia - US/Irving)' 
<mars.toktonal...@nokia.com>; Ferriter, Cian <cian.ferri...@intel.com>; Klozik, 
MartinX <martinx.klo...@intel.com>; Christian Trautman (ctrau...@redhat.com) 
<ctrau...@redhat.com>; Bill Michalowski (bmich...@redhat.com) 
<bmich...@redhat.com>; Elias, RichardX <richardx.el...@intel.com>
Subject: [vsperf] Agenda for VSPERF weekly meeting - 13 Dec 2017 (ww49)

Hi All,

The agenda for this week:

  1.  Development update - Review of the current status of release plan.
  2.  Plugfest updates.

Meeting minutes

  *   WW48  
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-11-29-16.14.html
  *   WW47 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-11-22-16.02.html
  *   WW46 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-11-15-16.01.html


Time: Wednesday UTC 16h00, Ireland (UTC) 16h00, PST 8h00 (UTC/GMT -8)

IRC: freenode https://freenode.net/ channel: #opnfv-vswitchperf 
http://webchat.freenode.net/?channels=opnfv-vswitchperf

Audio: https://global.gotomeeting.com/join/391235029
You can also dial in using your phone.  United States: +1 (571) 317-3116  
Access Code: 391-235-029
Phone numbers from other countries are here ... 
https://wiki.opnfv.org/display/meetings

Regards,
Sridhar K. N. Rao (Ph. D)
Architect
+91-9900088064




Spirent Communications e-mail confidentiality.
--

Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 15 Nov 2017 (ww46)

[Klozik, MartinX]

Hi Trevor,

you're right, second one was about node4.

Data for node1 follows:
pod12-node1 connections:
eno3 -> ixia port 1
eno4 -> ixia port 2

Installation and configuration of SANDBOX2 is ongoing.

Thank you,
Martin

From: Cooper, Trevor
Sent: Thursday, November 16, 2017 1:34 AM
To: Klozik, MartinX <martinx.klo...@intel.com>; Rao, Sridhar 
<sridhar@spirent.com>; opnfv-tech-discuss@lists.opnfv.org
Cc: ALFRED C 'MORTON (AL)' <acmor...@att.com>; Mars Toktonaliev (Nokia - 
US/Irving) <mars.toktonal...@nokia.com>; Ferriter, Cian 
<cian.ferri...@intel.com>; Christian Trautman (ctrau...@redhat.com) 
<ctrau...@redhat.com>; Ranganath, Sunku <sunku.rangan...@intel.com>; Bill 
Michalowski (bmich...@redhat.com) <bmich...@redhat.com>; Elias, RichardX 
<richardx.el...@intel.com>
Subject: RE: [vsperf] Agenda for VSPERF weekly meeting - 15 Nov 2017 (ww46)

Hi Martin ... thanks I have updated the diagram 
https://wiki.opnfv.org/display/pharos/Intel+POD12

Below I think you mean "node4" on the second one.

/Trevor

From: Klozik, MartinX
Sent: Wednesday, November 15, 2017 3:15 AM
To: Cooper, Trevor <trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>>; 
Rao, Sridhar <sridhar@spirent.com<mailto:sridhar@spirent.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: ALFRED C 'MORTON (AL)' <acmor...@att.com<mailto:acmor...@att.com>>; Mars 
Toktonaliev (Nokia - US/Irving) 
<mars.toktonal...@nokia.com<mailto:mars.toktonal...@nokia.com>>; Ferriter, Cian 
<cian.ferri...@intel.com<mailto:cian.ferri...@intel.com>>; Christian Trautman 
(ctrau...@redhat.com<mailto:ctrau...@redhat.com>) 
<ctrau...@redhat.com<mailto:ctrau...@redhat.com>>; Ranganath, Sunku 
<sunku.rangan...@intel.com<mailto:sunku.rangan...@intel.com>>; Bill Michalowski 
(bmich...@redhat.com<mailto:bmich...@redhat.com>) 
<bmich...@redhat.com<mailto:bmich...@redhat.com>>; Elias, RichardX 
<richardx.el...@intel.com<mailto:richardx.el...@intel.com>>
Subject: RE: [vsperf] Agenda for VSPERF weekly meeting - 15 Nov 2017 (ww46)

Hi Trevor,

thanks, I've retraced ixia connections for node3 (ci) and node4 (1st sandbox). 
I've updated vsperf configuration files at both node3 & node4 accordingly.

Could you, please, update diagrams at appropriate wiki with following details?

pod12-node3 connections:
eno3 -> ixia port 3
eno4 -> ixia port 4

pod12-node3 connections:
eno3 -> ixia port 5
eno4 -> ixia port 6

Best Regards,
Martin
From: Cooper, Trevor
Sent: Tuesday, November 14, 2017 11:59 PM
To: Rao, Sridhar <sridhar@spirent.com<mailto:sridhar@spirent.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: ALFRED C 'MORTON (AL)' <acmor...@att.com<mailto:acmor...@att.com>>; Mars 
Toktonaliev (Nokia - US/Irving) 
<mars.toktonal...@nokia.com<mailto:mars.toktonal...@nokia.com>>; Ferriter, Cian 
<cian.ferri...@intel.com<mailto:cian.ferri...@intel.com>>; Klozik, MartinX 
<martinx.klo...@intel.com<mailto:martinx.klo...@intel.com>>; Christian Trautman 
(ctrau...@redhat.com<mailto:ctrau...@redhat.com>) 
<ctrau...@redhat.com<mailto:ctrau...@redhat.com>>; Ranganath, Sunku 
<sunku.rangan...@intel.com<mailto:sunku.rangan...@intel.com>>; Bill Michalowski 
(bmich...@redhat.com<mailto:bmich...@redhat.com>) 
<bmich...@redhat.com<mailto:bmich...@redhat.com>>; Elias, RichardX 
<richardx.el...@intel.com<mailto:richardx.el...@intel.com>>
Subject: RE: [vsperf] Agenda for VSPERF weekly meeting - 15 Nov 2017 (ww46)

The Ixia is back up ... we discovered that the Win7 date/time was wrong and 
this caused a problem with the license. IxNetwork client VM now connects to the 
chassis using 10.10.50.6 (as before). Please note that the physical Ixia ports 
have been reassigned (VSPERF now uses 1-6).

/Trevor


From: Cooper, Trevor
Sent: Tuesday, November 14, 2017 12:31 PM
To: 'Rao, Sridhar' <sridhar@spirent.com<mailto:sridhar@spirent.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: ALFRED C 'MORTON (AL)' <acmor...@att.com<mailto:acmor...@att.com>>; Mars 
Toktonaliev (Nokia - US/Irving) 
<mars.toktonal...@nokia.com<mailto:mars.toktonal...@nokia.com>>; Ferriter, Cian 
<cian.ferri...@intel.com<mailto:cian.ferri...@intel.com>>; Klozik, MartinX 
<martinx.klo...@intel.com<mailto:martinx.klo...@intel.com>>; Christian Trautman 
(ctrau...@redhat.com<mailto:ctrau...@redhat.com>) 
<ctrau...@redhat.com<mailto:ctrau...@redhat.com>>; Ranganath, Sunku 
<sunku.rangan...@intel.com<mailto:sunku.rangan...@intel.com>>; Bill Michalowski 
(bmich...@redhat.com<mai

Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 15 Nov 2017 (ww46)

[Klozik, MartinX]

Hi Trevor,

thanks, I've retraced ixia connections for node3 (ci) and node4 (1st sandbox). 
I've updated vsperf configuration files at both node3 & node4 accordingly.

Could you, please, update diagrams at appropriate wiki with following details?

pod12-node3 connections:
eno3 -> ixia port 3
eno4 -> ixia port 4

pod12-node3 connections:
eno3 -> ixia port 5
eno4 -> ixia port 6

Best Regards,
Martin
From: Cooper, Trevor
Sent: Tuesday, November 14, 2017 11:59 PM
To: Rao, Sridhar <sridhar@spirent.com>; opnfv-tech-discuss@lists.opnfv.org
Cc: ALFRED C 'MORTON (AL)' <acmor...@att.com>; Mars Toktonaliev (Nokia - 
US/Irving) <mars.toktonal...@nokia.com>; Ferriter, Cian 
<cian.ferri...@intel.com>; Klozik, MartinX <martinx.klo...@intel.com>; 
Christian Trautman (ctrau...@redhat.com) <ctrau...@redhat.com>; Ranganath, 
Sunku <sunku.rangan...@intel.com>; Bill Michalowski (bmich...@redhat.com) 
<bmich...@redhat.com>; Elias, RichardX <richardx.el...@intel.com>
Subject: RE: [vsperf] Agenda for VSPERF weekly meeting - 15 Nov 2017 (ww46)

The Ixia is back up ... we discovered that the Win7 date/time was wrong and 
this caused a problem with the license. IxNetwork client VM now connects to the 
chassis using 10.10.50.6 (as before). Please note that the physical Ixia ports 
have been reassigned (VSPERF now uses 1-6).

/Trevor


From: Cooper, Trevor
Sent: Tuesday, November 14, 2017 12:31 PM
To: 'Rao, Sridhar' <sridhar@spirent.com<mailto:sridhar@spirent.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: ALFRED C 'MORTON (AL)' <acmor...@att.com<mailto:acmor...@att.com>>; Mars 
Toktonaliev (Nokia - US/Irving) 
<mars.toktonal...@nokia.com<mailto:mars.toktonal...@nokia.com>>; Ferriter, Cian 
<cian.ferri...@intel.com<mailto:cian.ferri...@intel.com>>; Klozik, MartinX 
<martinx.klo...@intel.com<mailto:martinx.klo...@intel.com>>; Christian Trautman 
(ctrau...@redhat.com<mailto:ctrau...@redhat.com>) 
<ctrau...@redhat.com<mailto:ctrau...@redhat.com>>; Ranganath, Sunku 
<sunku.rangan...@intel.com<mailto:sunku.rangan...@intel.com>>; Bill Michalowski 
(bmich...@redhat.com<mailto:bmich...@redhat.com>) 
<bmich...@redhat.com<mailto:bmich...@redhat.com>>; Elias, RichardX 
<richardx.el...@intel.com<mailto:richardx.el...@intel.com>>
Subject: RE: [vsperf] Agenda for VSPERF weekly meeting - 15 Nov 2017 (ww46)

Thanks for setting up the VSPERF plugfest Etherpad Sridhar ... I added some 
notes and also about usage of POD 12 for the plugfest. We can add more details 
tomorrow but I think we should focus the meeting on plugfest as the top agenda 
item. https://etherpad.opnfv.org/p/Plugfest-Euphrates-VSPERF

POD 12 VPN access is available and I have updated the POD diagram 
https://wiki.opnfv.org/display/pharos/Intel+POD12

/Trevor

From: Rao, Sridhar [mailto:sridhar@spirent.com]
Sent: Tuesday, November 14, 2017 9:50 AM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: ALFRED C 'MORTON (AL)' <acmor...@att.com<mailto:acmor...@att.com>>; Cooper, 
Trevor <trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>>; Mars 
Toktonaliev (Nokia - US/Irving) 
<mars.toktonal...@nokia.com<mailto:mars.toktonal...@nokia.com>>; Ferriter, Cian 
<cian.ferri...@intel.com<mailto:cian.ferri...@intel.com>>; Klozik, MartinX 
<martinx.klo...@intel.com<mailto:martinx.klo...@intel.com>>; Christian Trautman 
(ctrau...@redhat.com<mailto:ctrau...@redhat.com>) 
<ctrau...@redhat.com<mailto:ctrau...@redhat.com>>; Ranganath, Sunku 
<sunku.rangan...@intel.com<mailto:sunku.rangan...@intel.com>>; Bill Michalowski 
(bmich...@redhat.com<mailto:bmich...@redhat.com>) 
<bmich...@redhat.com<mailto:bmich...@redhat.com>>; Elias, RichardX 
<richardx.el...@intel.com<mailto:richardx.el...@intel.com>>
Subject: [vsperf] Agenda for VSPERF weekly meeting - 15 Nov 2017 (ww46)

Hi All,


Proposed agenda topics:

  1.  Last week's action items.
  2.  Fraser Release plan - Jira Tickets.
 *   Uncaptured developments.
  3.  Development Updates.
  4.  Dashboard Updates
  5.  Testcases for Fraser release: Deadline 11/17
  6.  Plug-fest Discussion - 
https://etherpad.opnfv.org/p/Plugfest-Euphrates-VSPERF



Meeting minutes

  *   WW45 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-11-08-16.01.html
  *   WW44 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-11-01-14.59.html
  *   Ww43 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-10-25-14.57.html



Time: Wednesday UTC 16h00, Ireland (UTC) 16h00, PST 8h00 (

Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 01 Nov 2017 (ww44)

[Klozik, MartinX]

Hi All,

just two optional topics from my side:

a)  status of VSPERF CI jobs - daily, verify & merge

b)  ongoing discussion about CSIT collaboration

Best Regards,
Martin
From: Rao, Sridhar [mailto:sridhar@spirent.com]
Sent: Tuesday, October 31, 2017 5:34 PM
To: 'opnfv-tech-discuss@lists.opnfv.org' <opnfv-tech-discuss@lists.opnfv.org>
Cc: 'MORTON, ALFRED C (AL)' <acmor...@att.com>; Cooper, Trevor 
<trevor.coo...@intel.com>; Klozik, MartinX <martinx.klo...@intel.com>; 'Bill 
Michalowski' <bmich...@redhat.com>; 'Christian Trautman' <ctrau...@redhat.com>; 
'Mars Toktonaliev (Nokia - US/Irving)' <mars.toktonal...@nokia.com>; Ferriter, 
Cian <cian.ferri...@intel.com>
Subject: [vsperf] Agenda for VSPERF weekly meeting - 01 Nov 2017 (ww44)

Hi All,


Proposed agenda topics:

  1.  Quick update on IMIX. I have uploaded slides in VSPERF-READOUTS page in 
wiki (https://wiki.opnfv.org/display/vsperf/Vswitch+Readouts). In last slide, I 
have proposed 3 options A, B and C. Please share your opinion on these 3 
options.
  2.  Discussion on Fraser release. Summary of Fraser release plan MS1 (11/03) 
. https://wiki.opnfv.org/display/SWREL/Summary+of+Release+Plans+for+Fraser
  3.  Plug-fest Discussion.
  4.  Windriver AVS performance benchmarking with VSPERF.



Meeting minutes

  *   Ww43 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-10-25-14.57.html
  *   Ww42 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-10-18-14.59.html
  *   ww41 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-10-11-15.01.html
  *   ww40 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-10-04-14.49.html



Time: Wednesday UTC 15h00, Ireland (UTC) 15h00, PDT 8h00 (UTC/GMT -7) ... 
Currently observing daylight saving

IRC: freenode https://freenode.net/ channel: #opnfv-vswitchperf 
http://webchat.freenode.net/?channels=opnfv-vswitchperf

Audio: https://global.gotomeeting.com/join/391235029
You can also dial in using your phone.  United States: +1 (571) 317-3116  
Access Code: 391-235-029
Phone numbers from other countries are here ... 
https://wiki.opnfv.org/display/meetings



Regards,
Sridhar K. N. Rao (Ph. D)
Architect
+91-9900088064



Spirent Communications e-mail confidentiality.

This e-mail contains confidential and / or privileged information belonging to 
Spirent Communications plc, its affiliates and / or subsidiaries. If you are 
not the intended recipient, you are hereby notified that any disclosure, 
copying, distribution and / or the taking of any action based upon reliance on 
the contents of this transmission is strictly forbidden. If you have received 
this message in error please notify the sender by return e-mail and delete it 
from your system.

Spirent Communications plc
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, 
United Kingdom.

Or if within the US,

Spirent Communications,
27349 Agoura Road, Calabasas, CA, 91301, USA.
Tel No. 1-818-676- 2300
--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [VSPERF] Vote for new VSPERF PTL

[Klozik, MartinX]

+1

From: Cooper, Trevor
Sent: Wednesday, October 11, 2017 1:11 AM
To: opnfv-tech-discuss@lists.opnfv.org
Cc: MORTON, ALFRED C (AL) <acmor...@att.com>; Klozik, MartinX 
<martinx.klo...@intel.com>; 'Bill Michalowski' <bmich...@redhat.com>; 
'Christian Trautman' <ctrau...@redhat.com>; Rao, Sridhar 
<sridhar@spirent.com>; Tahhan, Maryam <maryam.tah...@intel.com>; Cooper, 
Trevor <trevor.coo...@intel.com>
Subject: [VSPERF] Vote for new VSPERF PTL
Importance: High

VSPERF committers ...

There have been no further nominations for the VSPERF PTL position ... 
therefore Sridhar Rao from Spirent is the sole candidate. To provide a record 
of this and acknowledgement from VSPERF committers please respond here 
indicating your approval/disapproval (+1, -1) for Sridhar to take over as PTL 
effective from the Euphrates release.

Thanks!

Trevor




From: Cooper, Trevor
Sent: Monday, October 02, 2017 8:59 PM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
opnfv-...@lists.opnfv.org<mailto:opnfv-...@lists.opnfv.org>
Cc: MORTON, ALFRED C (AL) <acmor...@att.com<mailto:acmor...@att.com>>; Klozik, 
MartinX <martinx.klo...@intel.com<mailto:martinx.klo...@intel.com>>; 'Bill 
Michalowski' <bmich...@redhat.com<mailto:bmich...@redhat.com>>; 'Christian 
Trautman' <ctrau...@redhat.com<mailto:ctrau...@redhat.com>>; 'Mars Toktonaliev 
(Nokia - US/Irving)' 
<mars.toktonal...@nokia.com<mailto:mars.toktonal...@nokia.com>>; Raymond Paik 
<rp...@linuxfoundation.org<mailto:rp...@linuxfoundation.org>>; 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>; 'Rao, 
Sridhar' <sridhar@spirent.com<mailto:sridhar@spirent.com>>
Subject: [VSPERF] New PTL for VSPERF after E release

I will be stepping down as PTL for VSPERF effective from the E release. Thank 
you VSPERF team ... I am very grateful for the opportunity to lead the project 
through Danube and Euphrates. I have learned a lot from all of you and have 
enjoyed your company immensely.

I would like to nominate Sridhar Rao (Spirent) as the next VSPERF PTL. If there 
are any further nominations please notify by 6th October.

/Trevor

--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [VSPERF] E Release DPDK/OVS/VPP/QEMU versions

[Klozik, MartinX]

Hi Christian,

unfortunately I was not able to run CI runs with updated version of vsperf’s 
toolset. The reason is, that all PODs hosted by Intel are not reachable from 
Jenkins running at build.opnfv.org. This situation is caused by update of 
firewall at Intel side and it is not solved yet.

Thus we won’t be able to properly verify possible update of toolset before the 
fork of stable branch. I suggest to update toolset versions in unfrozen master 
branch after the fork and if vsperf proves itself stable enough, we can discuss 
a possibility to merge these changes to the stable/Euphrates branch afterwards.

Broken CI is also preventing us to evaluate an impact of your CI tuning tips, 
because CI is not running since 31st of August. I followed your tips provided 
in Jira to tune CI node (pod12-node3) at Friday 1st of September and manual TC 
execution looked promising. At first I thought, that broken connection between 
node3 and Jenkins was caused by node configuration changes and reboot, but 
finally I’ve found that it is a generic issue. So for proper evaluation of 
results and fine tuning of vpserf configuration, we have to wait until CI will 
be up again.

Let’s hope, that Intel will be able to open accidently forbidden port in 
firewall soon.

Best Regards,
Martin
From: Christian Trautman [mailto:ctrau...@redhat.com]
Sent: Thursday, August 31, 2017 4:49 PM
To: Klozik, MartinX <martinx.klo...@intel.com>
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [VSPERF] E Release DPDK/OVS/VPP/QEMU versions

Hi Martin,

I've tested QEMU 2.9 on some internal tests as well and saw no issues.

I think moving OVS to 2.7 is a good idea. 2.8.0 is still too new.

DPDK 17.05 should work fine. I've used it inside guests for some time now 
without issues. I haven't checked it against OVS 2.7 though.

I think running some tests with the agreed newer versions and giving the green 
light would be a good approach. We should move up a bit for E release if 
possible.

-Christian,



From: "MartinX Klozik" 
<martinx.klo...@intel.com<mailto:martinx.klo...@intel.com>>
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Sent: Thursday, August 31, 2017 7:41:15 AM
Subject: [opnfv-tech-discuss] [VSPERF] E Release DPDK/OVS/VPP/QEMU versions

Hi vsperf community,

as of now, vsperf uses following versions of DPDK/OVS/VPP respectively:

DPDK_TAG ?= v17.02
OVS_TAG ?= cc3a32f3b6891168cee98812e8f5e3d8a5a52c98 (in general compatible with 
DPDK v17.02, so about 6 months old)
VPP_TAG ?= v17.04
QEMU_TAG ?= v2.5.0

Do we want to keep it as it is for E release?

In general vsperf is able to run with:

1)  DPDK v17.05 & compatible OVS (cca 2-3 months old where support for 
17.05 was merged) - which is known to have issues with MULTIQUEUES in the 
GUESTs, so v17.05.1 have to be enforced; However this tag can be installed by 
standard vsperf build scripts, as it is not present in DPDK git repository – in 
a nutshell I would rather avoid this buggy version

2)  DPDK v17.08 & OVS (current master works just fine) – if we would like 
to upgrade – this would be the proper candidate

3)  VPP v17.07

4)  QEMU 2.8.0 (I’ve tested it some time ago) and probably also QEMU 2.9.0 
(can be easily tested)


In case there will be an interest to include newer DPDK/OVS/VPP/DPDK versions 
in E release, I can run a several CI runs with selected versions to verify its 
performance and stability and we can take a decision next week, if newer set of 
tools should be used or not.

Overall, it is just a matter of modification of
src/package-list.mk

In case we will keep current DPDK/OVS/VPP/QEMU versions for E release. Then I 
suggest to switch to recent versions in master branch after the fork of 
Euphrates stable branch.

Please advise,
Martin

--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies.

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

--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distr

[opnfv-tech-discuss] [VSPERF] E Release DPDK/OVS/VPP/QEMU versions

[Klozik, MartinX]

Hi vsperf community,

as of now, vsperf uses following versions of DPDK/OVS/VPP respectively:

DPDK_TAG ?= v17.02
OVS_TAG ?= cc3a32f3b6891168cee98812e8f5e3d8a5a52c98 (in general compatible with 
DPDK v17.02, so about 6 months old)
VPP_TAG ?= v17.04
QEMU_TAG ?= v2.5.0

Do we want to keep it as it is for E release?

In general vsperf is able to run with:

1)  DPDK v17.05 & compatible OVS (cca 2-3 months old where support for 
17.05 was merged) - which is known to have issues with MULTIQUEUES in the 
GUESTs, so v17.05.1 have to be enforced; However this tag can be installed by 
standard vsperf build scripts, as it is not present in DPDK git repository - in 
a nutshell I would rather avoid this buggy version

2)  DPDK v17.08 & OVS (current master works just fine) - if we would like 
to upgrade - this would be the proper candidate

3)  VPP v17.07

4)  QEMU 2.8.0 (I've tested it some time ago) and probably also QEMU 2.9.0 
(can be easily tested)


In case there will be an interest to include newer DPDK/OVS/VPP/DPDK versions 
in E release, I can run a several CI runs with selected versions to verify its 
performance and stability and we can take a decision next week, if newer set of 
tools should be used or not.

Overall, it is just a matter of modification of
src/package-list.mk

In case we will keep current DPDK/OVS/VPP/QEMU versions for E release. Then I 
suggest to switch to recent versions in master branch after the fork of 
Euphrates stable branch.

Please advise,
Martin
--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [VSPERF] [Bottlenecks] VSPERF and StorPerf

[Klozik, MartinX]

Hi Mark,

just to be sure I got correctly your network setup - you want to stress test 
full OpenStack installation by simulation of NIC and storage utilization, am I 
right?

In that case vsperf can be used in "trafficgen mode", where it only controls 
selected traffic generator and collects final results. As of now, vsperf 
doesn't collect any periodic metrics from the traffic generator. It runs 
selected traffic pattern (e.g. RFC2544 Throughput) and records measured values.

However I think that both scenarios would be possible, but first scenario would 
have to be slightly changed:


1)  I start up VSPERF on the NICs that represent the tenant network in an 
OpenStack installation.

MK=> and measure e.g. throughput of setup without the storage network stressing
2)After 10 minutes, start up StorPerf read/write test that should stress 
the OpenStack storage network
3)See if there is a change to the VSPERF throughput.
MK=> i.e. execute vsperf again with the same settings as before and 
compare measured values

 Second scenario can be executed as proposed by you, without any changes.

Best Regards,
Martin


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Beierl, Mark
Sent: Thursday, August 17, 2017 4:39 PM
To: Yuyang (Gabriel) 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [VSPERF] [Bottlenecks] VSPERF and StorPerf

Hello, Gabriel.

The idea behind starting one first is so we can see the delta at the point 
where it started.  We certainly can run both independently as a baseline, and 
then run them together can measure the delta that way...

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

On Aug 17, 2017, at 04:20, Yuyang (Gabriel) 
> wrote:

Hi Mark,

I fully support the idea here. I think it is time testing projects together 
develop some sophisticated stress test cases across components of the system.
Just 1 question, why start VSPERF and STORPERF separately. Why not start both 
tests simultaneously and monitoring/reporting the throughput variation along 
time.

Thanks,
Gabriel


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Beierl, Mark
Sent: Thursday, August 17, 2017 12:17 AM
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [VSPERF] [Bottlenecks] VSPERF and StorPerf

Hello, Trevor and VSPERF team.

I'd like to get a quick overview of VSPERF and how the metrics are captured.  
Sorry if these are dumb questions :)

First, is there a test that simply pushes packets over the network to see what 
the maximum throughput is, like a saturation test?

Does VSPERF capture periodic metrics, or just a summary report at the end?  If 
I change something in the network while the test is running (such as adding 
more traffic outside of VSPERF), is there a way to see the impact of that while 
the test is running?

The reason behind the questions are for the following scenario:

1) I start up VSPERF on the NICs that represent the tenant network in an 
OpenStack installation.
2) After 10 minutes, start up StorPerf read/write test that should stress the 
OpenStack storage network
3) See if there is a change to the VSPERF throughput.

Alternatively, as StorPerf does have minute by minute metrics, we can do this:

1) Start StorPerf read/write
2) After 10 minutes, start VSPERF to stress the tenant network NICs
3) Look at the change in StorPerf throughput at the time that VSPERF starts.

Thoughts?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [VSPERF] Query regarding VSPERF trafficgen module

[Klozik, MartinX]

Hello Kritshekhar,

it seems to me, that you're using an outdated version of vsperf. This issue has 
been fixed on 10th of November 2016. Could you please update your repository 
(git pull) and switch to the recent version of master or stable/danube branch 
and test it again?

In case that your issue will persist, then please sent me following details for 
further debugging:

1)  exact vsperf version, i.e. git commit id

2)  your custom vsperf configuration; In case that you've modified any 
files inside conf/ directory, then please send me all the changes, you have 
performed as a diff against original versions; In case that you've modified 
also vsperf code, then please include also these changes, i.e. the full repo 
diff; e.g. git diff master..HEAD > debug.patch

3)  the full list of  vsperf options used for its execution and full vsperf 
output, e.g. ./vsperf -m trafficgen --trafficgen IxNet | tee debug.log

Thank you,
Martin


From: Cooper, Trevor
Sent: Wednesday, March 22, 2017 7:13 PM
To: Kritshekhar Jha <k...@ixiacom.com>; opnfv-tech-discuss@lists.opnfv.org; 
test...@lists.opnfv.org; Klozik, MartinX <martinx.klo...@intel.com>
Cc: Suvendu Mozumdar <smozum...@ixiacom.com>; Mrinmoy Das 2 <mr...@ixiacom.com>
Subject: RE: Query regarding VSPERF trafficgen module

Hi Kritshekhar

I am heads down with D-release but bringing this to attention of the VSPERF 
team and we will get back shortly.

/Trevor


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Kritshekhar 
Jha
Sent: Wednesday, March 22, 2017 3:27 AM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
test...@lists.opnfv.org<mailto:test...@lists.opnfv.org>
Cc: Suvendu Mozumdar <smozum...@ixiacom.com<mailto:smozum...@ixiacom.com>>; 
Mrinmoy Das 2 <mr...@ixiacom.com<mailto:mr...@ixiacom.com>>
Subject: [opnfv-tech-discuss] Query regarding VSPERF trafficgen module

Hello OPNFV community members,

Thanks to the community for bringing this opportunity into the market.
Before coming to the issues, I would like to state the use case we trying to 
deploy and test.


*   We have a CENTOS7 system as a DUT deployed over a ESXI Hypervisor

*   We have cloned vswitchperf code over this and created the vsperf 
environment with the available script.

*   Currently we are using Ixia as the traffic gen, and we are progressing 
over that.

*   But if we use the 'trafficgen' mode and run it as ./vsperf -m 
trafficgen we are getting an error

AttributeError:  object has no attribute 'TOOLS'


On further debugging we have concluded that somehow TOOLS 
dictionary is not getting populated.

*   On the other hand if I run the test in normal mode TOOLS dictionary are 
getting populated and hence the control succeeded the conditional check where 
the trafficgen mode failed
[cid:image001.jpg@01D2A3A9.E75E1970]

*   Can you please guide what could the possible mistake here .

Thanks and Regards,
Kritshekhar Jha

--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [VSPERF] VOTE on generating VSPERF Stable branch for Danube

[Klozik, MartinX]

+1 to stable branch creation

--Martin

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Cooper, Trevor
Sent: Monday, February 27, 2017 10:31 PM
To: 'opnfv-tech-discuss@lists.opnfv.org' 
Subject: [opnfv-tech-discuss] [VSPERF] VOTE on generating VSPERF Stable branch 
for Danube

VSPERF committers and contributors ...

The deadline for creating the stable branch of VSPERF for Danube is 10th March

There are currently are no outstanding patches waiting for review or commit

PLEASE RESPOND WITH +1, 0, -1 to indicated your agreement/disagreement with 
generating the stable branch. We will check on the consensus at our weekly 
meeting this week (Wednesday) before the final decision to proceed.

Thanks

Trevor (VSPERF PTL)
--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [VSPERF] Yardstick Integration

[Klozik, MartinX]

Hi Sridhar,

I would rather avoid another set of configuration files inside VSPERF repo. We 
would have to keep them up to date and I don't think that it will speed up 
deployment of yardstick/vsperf testing infrastructure.

Whoever wants to execute a traffic via vsperf inside yardstick TC, has to do a 
several nontrivial steps. Especially a preparation of VM image with vsperf 
installation takes some time. Creation of vsperf.conf with selected traffic 
generator is just a minor step if compared to the previous one.

Nevertheless we can consider other steps to  make usage of yardstick/vsperf TCs 
easier, e.g.:
- put configuration examples into vsperf documentation
- prepare a VM image with preinstalled vsperf and a configuration prepared for 
particular trafficgenerator
- enhance yaml options with possibility to setup values for vsperf's args 
"-trafficgen" and "-test-params"

Especially the last option will be very useful, because I'm just working on the 
patch, which will allow to modify through CLI (i.e. through -test-params) any 
configuration option. So yardstick user/tester would be able to put any 
configuration options directly to the yaml file. And thus create TCs specific 
to selected traffic generator.

Similar option could be a definition of vsperf.conf file directly in yaml file 
as a lng string option, which will be stored as vsperf.conf inside VM image.

However we have only a little experience with yardstick/vsperf integration so 
far. Thus it would be hard to identify the real needs of yardstick/vsperf 
user/tester.

Best Regards,
Martin
From: Rao, Sridhar [mailto:sridhar@spirent.com]
Sent: Thursday, October 27, 2016 12:00 PM
To: Klozik, MartinX <martinx.klo...@intel.com>
Subject: RE: VSPERF-Yardstick Integration

"In general, user shall create his own custom configuration file before vsperf 
execution. This file should specify, which traffic generator will be used and 
contain any traffic generator specific configuration, which differs from 
default values. If there are any steps required for correct Spirent Testcenter 
functionality, it would be good to mention them at yardstick specific section 
of configuration. "

You are right. I was referring to the same configuration file. Currently, that 
is not part of the vsperf distribution. However, with Yardstick integration, 
this configuration will still not be part of the distribution, right? Mainly, 
in the .yaml file, for conf-file variable, the value we specify would be 
specific to the user the way he runs.
I was thinking, we need to create such custom configuration files and provide 
it along with the distribution for this integration!
Thanks for the clarification.


Regards,
Sridhar K. N. Rao (Ph. D)
Solutions Architect
+91-9900088064

From: Klozik, MartinX [mailto:martinx.klo...@intel.com]
Sent: Thursday, October 27, 2016 3:03 PM
To: Rao, Sridhar
Subject: RE: VSPERF-Yardstick Integration

Hello Sridhar,

Could you give me an example of configuration, you would like to store at vspef 
repository?

In general, user shall create his own custom configuration file before vsperf 
execution. This file should specify, which traffic generator will be used and 
contain any traffic generator specific configuration, which differs from 
default values. If there are any steps required for correct Spirent Testcenter 
functionality, it would be good to mention them at yardstick specific section 
of configuration.

Best Regards,
Martin

From: Rao, Sridhar [mailto:sridhar@spirent.com]
Sent: Wednesday, October 26, 2016 5:23 PM
To: Klozik, MartinX <martinx.klo...@intel.com<mailto:martinx.klo...@intel.com>>
Subject: VSPERF-Yardstick Integration

Hello Martin,

In order to support other traffic generators for Yardstick-VSPERF integration, 
in my case it is Spirent Testcenter, I suppose we have to create configuration 
files. I was wondering where to place these configuration files?

1.   Vsperf/conf folder?

2.   Vsperf/yardstick/tests folder?

Regards,
Sridhar K. N. Rao (Ph. D)
Solutions Architect
+91-9900088064


Spirent Communications e-mail confidentiality.

This e-mail contains confidential and / or privileged information belonging to 
Spirent Communications plc, its affiliates and / or subsidiaries. If you are 
not the intended recipient, you are hereby notified that any disclosure, 
copying, distribution and / or the taking of any action based upon reliance on 
the contents of this transmission is strictly forbidden. If you have received 
this message in error please notify the sender by return e-mail and delete it 
from your system.

Spirent Communications plc
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN,

Re: [opnfv-tech-discuss] [VSPERF] Stepping down as PTL

[Klozik, MartinX]

Thank you for all the hard work, you did for the project and vsperf community. 
It has been a pleasure to work with you.

--Martin

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Christo Kleu
Sent: Monday, October 24, 2016 5:07 PM
To: Tahhan, Maryam 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [VSPERF] Stepping down as PTL

Thank you Maryam!

- Christo Kleu

On Mon, Oct 24, 2016 at 4:41 PM, MORTON, ALFRED C (AL) 
> wrote:
Thanks a million for your leadership and
your many technical contributions to the
vsperf project, Maryam!

it has been a pleasure,
Al


> -Original Message-
> From: 
> opnfv-tech-discuss-boun...@lists.opnfv.org
>  [mailto:opnfv-tech-
> discuss-boun...@lists.opnfv.org] On 
> Behalf Of Tahhan, Maryam
> Sent: Monday, October 24, 2016 8:50 AM
> To: 
> opnfv-tech-discuss@lists.opnfv.org;
>  TSC OPNFV
> Subject: [opnfv-tech-discuss] [VSPERF] Stepping down as PTL
>
> Hi TSC and fellow VSPERFers
>
> It is with regret I would like to inform you that I am stepping down as
> VSPERF PTL. I will still be working in OPNFV (SFQM) but vsperf no more.
> It has been a pleasure working with you folks.
>
> BR
> Maryam
> ___
> 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

--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [VSPERF] topology description scheme

[Klozik, MartinX]

Hi Maryam,

Thanks for initial proposal. It looks good overall. It seems, we are going to 
define a grammar of a small language. In that case it might be useful to define 
it well for both human and machine processing. Just for case, we would like to 
create a class, which will be able to prepare a setup automatically based on 
the scheme name.

In that case, we should consider:

1)  Possible ambiguity in number meaning; May be, we should consider a 
standalone number as an index and number prefixed with x as multiplication 
factor, e.g. LS1 vs. PVx3P

2)  In your proposal is V a synonym for VM with 2 NICs; We should consider 
a possibility of VMs with different NIC number, i.e. to really use V as a 
Virtual NIC, e.g. PVVP in meaning of phy_nic->virt_nic->virt_nic->phy_nic. 
However I can't figure out an intuitive but still flexible way to describe 
complex scenarios, e.g. 1VM with 4NICs in parallel or even 2 VMs in series, 
where 1st VM has 2NICs, but 2nd 4NICs in parallel...

Best Regards,
Martin

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tahhan, Maryam
Sent: Tuesday, September 06, 2016 11:21 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [VSPERF] topology description scheme


Hi folks
I've been thinking about this and I think I have a possible suggestion



Lettering:

It's case sensitive



L - Local

R - Remote

S - vSwitch

P- Physical NIC

V - Virtual NIC

pp - patch port

O - Overlay port - not sure if we need...



Numbering:
Numeric values can follow any of the last S, V, and P or nothing follows them 
which implies a 1.

For ports it implies the number of ports V2 is two virtual ports connected in 
succession.

For switches it actually acts as an Identifier LS2 is local switch 2.





The scheme is really to describe the flows from port to port through the vswitch



so

Current scheme


Proposed scheme


Phy2phy


LS_P2


PVP


LS_PVP


PVVP


LS_PV2P


Multiple VMs in series


LS_PVxP where X is the number


Multiple VMs in Parallel


LS_PVP_x (where X is a number applies to everything surrounded by underscores)


2 local switches doing phy2phy


LS1_P2_LS2_P2


2 local switches patched together


LS1_Ppp_LS2_P


Overlayed -switches on a local and a remote


LS_PO_RS_OP


Overlayed - local switched


LS1_PO_LS2_OP








Not as simple as I would have hoped, but open to any suggestions



BR
Marayam


--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [VSPERF] support CLI for all configuration parameters

[Klozik, MartinX]

Hi Folks,

Currently VSPERF uses a lot of configuration options spread among several 
configuration files, but only a few of them are configurable "on the fly" by 
CLI option -test-params. During the past, there were several requirements to 
allow a CLI modification of various configuration options. So in these days 
some of them can be modified, but it is hard to find, which one (one have to 
consult documentation related to the specific feature).

What about a change which will allow to modify any option by CLI (and 
"Parameters" option of testcase definition)? It means, that for any 
configuration option (by default UPPER case name) its lower case form can be 
used to redefine the value through -test-params argument.

In a nutshell following patch will do the trick:

diff --git a/conf/__init__.py b/conf/__init__.py
index 4622823..d4332ac 100644
--- a/conf/__init__.py
+++ b/conf/__init__.py
@@ -34,7 +34,11 @@ class Settings(object):
 """Return a settings item value
 """
 if attr in self.__dict__:
-return getattr(self, attr)
+if attr == 'TEST_PARAMS':
+return getattr(self, attr)
+else:
+# Check if parameter value was overridden by CLI option
+return get_test_param(attr.lower(), getattr(self, attr))
 else:
 raise AttributeError("%r object has no attribute %r" %
  (self.__class__, attr))

Let me know what do you think (e.g. reply with +1).

If you'll find it useful, I'll create a ticket for that and prepare a patch. 
The final patch have to take into the account currently supported CLI 
parameters (i.e. code cleanup & type conversion/checking & testing).

Best Regards,
Martin
--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss