Re: [opnfv-tech-discuss] [yardstick] New PTL elected

[Gaoliang (kubi)]

Hi 

Firstly , Thanks Ross for leading Yardstick through two releases,   I was 
deeply impressed by your great leadership and excellent technical skills.  I 
think we wouldn't have the Yardstick today without you. 

Secondly, Congratulation to Rex,  Many Key feature of yardstick are delivered 
by you during the last two years.  I believe you will lead this project keeping 
moving.

Regards,
Kubi

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ross Brattain
Sent: Tuesday, May 29, 2018 8:14 AM
To: opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [yardstick] New PTL elected

Hi OPNFV,


Mingjiang Li (Rex Lee) has been elected as the new PTL for the Yardstick 
project by Condorcet vote.

CIVS poll results here:
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_b99c79421ce70058=c39fb1d5405efc15


Congratulations Rex!


--
Ross
___
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] [OSN-meetup]Open Source Networking User Group Shanghai Meetup on 04/14/2018 Saturday

[Gaoliang (kubi)]

Hi Community,
Our 2018 first meetup (4th Meetup) of OSN User group Shanghai is less than a 
week away:

--  1:30pm-5:30pm on Saturday 04/14 co-hosted by Shanghai Openstack Meetup 
(Shane Wang, Intel) and OSN User group Shanghai at INNOSPACE , Yang Pu, 
Shanghai, China.
Topic:  Edge computing
 Agenda:
13:30 - 14:30 《Building the Infrastructure network for MEC and IoT based on 
Fd.io 》, Hui Wang( ZTE)
14:30- 15:30  《High Performance In Edge Cloud》, Ruijing Guo (Intel)
15:30- 16:30 《Cloud Computing Encounters Edge Computing》, Jiangtao Wu (China 
Mobile )
16:30- 17:30 《Building IoT Smart Home Platform Based on K8s and Harbor》, Justin 
Chi (Huawei) , Xinhui Hu (Haier)
If you are in Shanghai at that time, please join us. We will be delighted to 
see as many of you as possible.
For more details of the event, and driving direction and maps, please go to 
https://www.meetup.com/Shanghai-OPNFV-Meetup/
and register there.
FREE DRINK AND TEA, and plus Gift for OPNFVer.
See you there.

Kubi
Organizer of Open Source Networking User Group Shanghai (OPNFV Shanghai Meetup)
OPNFV Ambassador

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

Re: [opnfv-tech-discuss] LFN Developer Forum planning wiki

[Gaoliang (kubi)]

Hi Ray,

When I click the link  
https://confluence.linuxfoundation.org/display/LN/LFN+Developer+Forum+Session+Proposals
 and login with my LF account, I found that I don’t have the right to edit the 
page

However, when I go with the LFN wiki page and 
jump to developer session proposals page, it works. So I would like to confirm 
that if the below link is the right link for us and in case other guys meet the 
same problem.  Thanks

https://wiki.lfnetworking.org/display/LN/LFN+Developer+Forum+Session+Proposals

Regards,
Kubi
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Wednesday, January 31, 2018 12:54 AM
To: opnfv-tech-discuss 
Subject: Re: [opnfv-tech-discuss] LFN Developer Forum planning wiki

All,

A quick update on this.  This took a while, but we now have an LFN 
wiki so I moved the developer forum session 
proposals page to 
https://confluence.linuxfoundation.org/display/LN/LFN+Developer+Forum+Session+Proposals.
  No one from OPNFV community proposed any topics yet, so I encourage everyone 
to add plenary topics that would be of interest across different LFN projects 
(e.g. LaaS, integrated testing, etc.).

In addition to plenary sessions across all communities, we will also have rooms 
for project specific breakouts on Monday & Tuesday.  These are just some 
examples, but we may want to have a session on OPNFV releases, OPNFV Verified 
release 2, XCI update, etc. in the OPNFV Breakout room.  I created a separate 
page in OPNFV wiki at 
https://wiki.opnfv.org/display/EVNT/OPNFV+Unconference+topics+at+LFN+Developer+Forum
 so you can add topics here.

Thanks,

Ray

On Mon, Jan 22, 2018 at 9:30 AM, Raymond Paik 
> wrote:
All,

As discussed during last week's TSC, we're trying to create an LFN wiki page(s) 
to start planning for LFN Developer Forum on March 26 (all day) & 27th (morning 
only).  Unfortunately, we're dealing with some technical challenges (e.g. 
giving edit access to everyone that have access to OPNFV, ODL, ONAP, 
fd.io wiki's) and the LFN wiki isn't sorted out yet.

In the mean time, I wanted the OPNFV community to start our planning so I 
created a couple of wiki pages in OPNFV.  One 
(https://wiki.opnfv.org/display/EVNT/LFN+Developer+Forum) lists possible tracks 
that we discussed last week plus a few additions.  The other 
(https://wiki.opnfv.org/display/EVNT/LFN+Developer+Forum+Session+Proposals) is 
a child page where you can start posting session proposals.

I'm in the process of finalizing rooms for the unconference portion of the 
event, and once that's confirmed I'll create a separate page for unconference 
planning.

When the LFN wiki is up and running, I'll send out a separate announcement and 
move the Developer Forum planning activities there (I'll copy over any 
comments/edits on the OPNFV wiki pages.)

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] Stepping down as Yardstick committer

[Gaoliang (kubi)]

Hi Vince,

It's my pleasure to work with you in yardstick, especially some work in 
Brahmaputra.

many thanks to your contribution.

I wish you the best on your new project.

Regards,
Kubi
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Riccobene, 
Vincenzo M
Sent: Thursday, January 18, 2018 6:35 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Stepping down as Yardstick committer

Hello,
I am currently a committer for the OPNFV Yardstick project, but as I see 
unfortunately in the last months I have been absent from the project since 
other commitments took higher priorities and all my time, resulting in no major 
contributions to Yardstick, and I consequently decided to step down from the 
positon of committer.

It has been a great pleasure to contribute to the community and I hope I will 
be able to contribute again in the future.
Thank you very much all!

Best Regards.
Vince


--
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] [yardstick]k8s HA test

[Gaoliang (kubi)]

Hi Louie，

Thanks for pointing this out.

According to Yardstick Fraser planning, we are trying to implement more test 
cases for container testing, especially for K8S.

In Euphrates, Yardstick already supports HA test cases for LXC scenarios which 
are deployed by OSA and ping test case for K8S.

Now, it is the time to talk about HA test cases for K8S.

From my perspective , Killing container and Killing progress are different 
fault injection type.  One is progress fault, the other is container fault. 
although I believe It make sense to test K8S with Killing container, there are 
still some topics to be discussed,  including  “how to kill the container”,” 
which containers we should kill” and “what metrics we should monitor”  .

Based on our previous experience of LXC testing, I’m not sure if it make sense 
to kill the container instead of progress. In some containers, there are more 
than one openstack progress (such as cinder, it includes cinder-api and 
cinder-scheduler), you would extend the fault range with the killing container.

I would like to invite HA team and Container4NFV team to join the thread.  I 
guess they could give some valuable comments from their perspectives.

Just my two cents.

Regards,
Kubi

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 龙雨
Sent: Thursday, December 14, 2017 4:16 PM
To: opnfv-tech-discuss 
Subject: [opnfv-tech-discuss] [yardstick]k8s HA test


 Hi，all，

 This is louie from BII-CFIEC，CFIEC is a third party neutral SDN/NFV technology 
evaluation and innovation center. Recently I have participate in OPNFV CVP test，
as we know CVP certification use dovatil program and dovetail integrate other 
OPNFV test programs like yardstick，functest, etc.

 When we do CVP test for our custom we meet a problem in HA test, the current 
CVP test tool doesn't support k8s, but our custom use k8s to realize HA.
Yardstick use ssh to login the controller node and kill such as nova-api 
progress to test HA, but due to the k8s feature the nova service exist in one 
container
behind the k8s ， and yardstick tes tool cann't login the container directly, 
this lead to the HA testcase failed.

 I have feedback this problem to dovetail and CVP，according to the HA testcase 
I put forward one method to solve this problem，use kill container to instead of
kill nova-api progress，as for haproxy， due to the k8s use nginx to realize LB 
we can use kill nginx to instead. Meanwhile, I ask dovetail whether they can 
offer
a patch in dovetail to match k8s HA test, the reply me this patch is all for 
yardstick and may do  many changes, so they suggest me go to yardstick progrom 
seek for
help. I know yardstick maybe support k8s in F version，but it seems to long for 
my current condition.

 By the way, in my test SUT every controller nodes have a container run 
opensatck service, such as nova-api, glance-api. We can access one controller 
node to kill
the container by specify name id or use k8s command to kill the container, When 
kill the container k8s will auto recovey the container on this node, and the 
recovery time is decided by k8s configuration.

This email first I want to know whether this kill container methond feasible； 
second，whether yardstick could offer such a patch for k8s HA test.

Thanks,

 louie

--
龙雨  Louie Long
邮箱:yl...@biigroup.cnE-mail: 
yl...@biigroup.cn
手机：+86 13261979365  Mobile: +86 13261979365
传真: 86-10-5638-1682-162Fax: 86-10-5867-8466
邮编：10 Postcode：10
地址：北京市经济技术开发区经海五路58号院数字工场5号楼2层
Add: 2nd Floor, Building 5, No.58 Jinghai Road, BDA, Beijing, China
天地互连信息技术有限公司  下一代互联网国家工程中心
Website: www.biigroup.com  
www.cfiec.net
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [test-wg] Monitoring dashboard for long duration test

[Gaoliang (kubi)]

Hi Rutuja,

The dashboard looks pretty good ☺

Only few questions about the dashboard.

What kind of  SUT you can monitor?  A single host or 5 hosts (OPNFV physical HA 
deployment)?  It seems that It can be filtered by Node IP. Do we have a whole 
view for a physical deployment POD?

What does the “Load” mean? CPU Load?  Why “CPU usage” can go to 400%?  Does the 
“Network Traffic” monitor one port or all of the ports of host?

Regards,

Kubi




From: test-wg-boun...@lists.opnfv.org [mailto:test-wg-boun...@lists.opnfv.org] 
On Behalf Of Rutuja Surve
Sent: Tuesday, November 21, 2017 4:42 PM
To: opnfv-tech-discuss@lists.opnfv.org; test...@lists.opnfv.org
Subject: [test-wg] Monitoring dashboard for long duration test

Hi,

I am currently working on Bottlenecks intern project focusing on 
monitoring/dashboarding for long duration test.
We have been closing to a protoype. We need your opinions/comments on how to 
organize the dashboard, what metrics/plugins should be included, etc.
The screenshots/details for the pre-protoype dashboard are provided below. 
Please comment on that.
Currently, we do not have a public access to the dashboard. If you'd like to 
know more details/operations, please refer to the gerrit patch:
https://gerrit.opnfv.org/gerrit/#/c/47567/
and give your review there or attend the Bottlenecks meeting tomorrow 
(Wednesday) at 8.30 am IST where I will provide regular reports for the 
progress and show customization of the dashboard.

Also find the screenshot-pdf of the dashboard attached with this e-mail. We are 
using Prometheus for querying and as datasource, Cadvisor and Collectd plugins 
for collecting system metrics and Grafana for displaying the dashboard.

Thanks,
Rutuja

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

Re: [opnfv-tech-discuss] 答复: [availability]High Availability Project meeting on Oct. 18

[Gaoliang (kubi)]

Hi All,

I would like to update the those new HA test cases into Test DB within today.

I will let you check it once I finished the update work.

Regards,

Kubi

From: Fu Qiao [mailto:fuq...@chinamobile.com]
Sent: Wednesday, November 15, 2017 9:11 AM
To: 'Georg Kunz' <georg.k...@ericsson.com>; 'Srikanth Vavilapalli' 
<srikanth.vavilapa...@ericsson.com>; Gaoliang (kubi) <jean.gaoli...@huawei.com>
Cc: 'wucaifu' <wuca...@chinamobile.com>; 'likaiyjy' <likai...@chinamobile.com>; 
'wangxuyjy' <wangxu...@chinamobile.com>; 'juan_qiu' <juan_...@tongji.edu.cn>; 
'lansizhong' <lansizh...@chinamobile.com>; 'opnfv-tech-discuss' 
<opnfv-tech-discuss@lists.opnfv.org>; 'Tony Yin' <14_...@tongji.edu.cn>; 'Yue 
Yuan' <yuan@zte.com.cn>
Subject: 答复: [opnfv-tech-discuss] 答复: [availability]High Availability Project 
meeting on Oct. 18

Hi, all. I go through the vote and concluded 5 TCs with scores higher than 4 as 
the suggested TCs for F release.
The HA test cases is going with the Yardstick testcases as before, so I guess 
Kubi or Kanglin will work on the test API database. Right?
Thanks!

发件人: Georg Kunz [mailto:georg.k...@ericsson.com]
发送时间: 2017年11月15日 2:59
收件人: Fu Qiao <fuq...@chinamobile.com<mailto:fuq...@chinamobile.com>>; Srikanth 
Vavilapalli 
<srikanth.vavilapa...@ericsson.com<mailto:srikanth.vavilapa...@ericsson.com>>; 
'Gaoliang (kubi)' <jean.gaoli...@huawei.com<mailto:jean.gaoli...@huawei.com>>
抄送: 'wucaifu' <wuca...@chinamobile.com<mailto:wuca...@chinamobile.com>>; 
'likaiyjy' <likai...@chinamobile.com<mailto:likai...@chinamobile.com>>; 
'wangxuyjy' <wangxu...@chinamobile.com<mailto:wangxu...@chinamobile.com>>; 
'juan_qiu' <juan_...@tongji.edu.cn<mailto:juan_...@tongji.edu.cn>>; 
'lansizhong' <lansizh...@chinamobile.com<mailto:lansizh...@chinamobile.com>>; 
'opnfv-tech-discuss' 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>;
 'Tony Yin' <14_...@tongji.edu.cn<mailto:14_...@tongji.edu.cn>>; 'Yue Yuan' 
<yuan@zte.com.cn<mailto:yuan@zte.com.cn>>
主题: RE: [opnfv-tech-discuss] 答复: [availability]High Availability Project 
meeting on Oct. 18

Hi all,

I added some comments and voted on the test cases. One remark: milestone 2 is 
on Friday and requires all new test cases to be registered in the test API 
database. Has this process already started for the newly considered HA test 
cases?

Best regards
Georg

From: Fu Qiao [mailto:fuq...@chinamobile.com]
Sent: Thursday, November 02, 2017 8:15 AM
To: Georg Kunz <georg.k...@ericsson.com<mailto:georg.k...@ericsson.com>>; 
Srikanth Vavilapalli 
<srikanth.vavilapa...@ericsson.com<mailto:srikanth.vavilapa...@ericsson.com>>; 
'Gaoliang (kubi)' <jean.gaoli...@huawei.com<mailto:jean.gaoli...@huawei.com>>
Cc: 'wucaifu' <wuca...@chinamobile.com<mailto:wuca...@chinamobile.com>>; 
'likaiyjy' <likai...@chinamobile.com<mailto:likai...@chinamobile.com>>; 
'wangxuyjy' <wangxu...@chinamobile.com<mailto:wangxu...@chinamobile.com>>; 
'juan_qiu' <juan_...@tongji.edu.cn<mailto:juan_...@tongji.edu.cn>>; 
'lansizhong' <lansizh...@chinamobile.com<mailto:lansizh...@chinamobile.com>>; 
'opnfv-tech-discuss' 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>;
 'Tony Yin' <14_...@tongji.edu.cn<mailto:14_...@tongji.edu.cn>>; 'Yue Yuan' 
<yuan@zte.com.cn<mailto:yuan@zte.com.cn>>
Subject: 答复: [opnfv-tech-discuss] 答复: [availability]High Availability Project 
meeting on Oct. 18

Hi, all. According to the discussion yesterday, I reorganize the etherpad page 
and conclude the proposed test cases into 12 TC.
Please check the following link and propose your comments.
Meanwhile, please put +1 on test cases you suggest to work on first for F 
release. We will make the decision for F release plan based on this.
Please provide any comments and your suggestion onto the page before the end of 
next week. I will work on JIRA tast allocation after that.
Thank you!

https://etherpad.opnfv.org/p/HA_Testcases_F_Release



发件人: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Fu Qiao
发送时间: 2017年11月2日 14:33
收件人: 'Georg Kunz' <georg.k...@ericsson.com<mailto:georg.k...@ericsson.com>>; 
'Srikanth Vavilapalli' 
<srikanth.vavilapa...@ericsson.com<mailto:srikanth.vavilapa...@ericsson.com>>; 
'Gaoliang (kubi)' <jean.gaoli...@huawei.com<mailto:jean.gaoli...@huawei.com>>
抄送: 'wucaifu' <wuca...@chinamobile.com<mailto:wuca...@chinamobile.com>>; 
'likaiyjy' <likai...@chinamobile.com<mailto:likai...@chinamobile.com>>; 
'wangxuyjy' <wangxu...@chinamobile.co

Re: [opnfv-tech-discuss] [yardstick] Opnfv Grafana results need upgrading.

[Gaoliang (kubi)]

Hi Charalampos and Rex,

A quick fix for the  os-nosdn-nofeature-ha overview page[1] for grafana.  
Please have a look.

Although we can use the $VERSION to filter the data, there is still need to 
select the time range for each release.

We can do more improvement in Fraser, Maybe we can separate the page into each 
release.

Adding Yardstick Release Planning link, please feel free to add your comments 
about Grafana upgrading

https://wiki.opnfv.org/display/yardstick/Release+Fraser

https://etherpad.opnfv.org/p/yardstick_release_f


[1] http://testresults.opnfv.org/grafana/dashboard/db/os-nosdn-nofeature-ha

Regards,

Kubi

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of limingjiang
Sent: Friday, November 03, 2017 12:25 PM
To: Charalampos Kominos 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [yardstick] Opnfv Grafana results need 
upgrading.

Hi Charalampos，

For releases mix, I think this can be done by using a template variable 
$RELEASE so you can switch to each release’s data.
This will be done in Fraser release, and current Grafana version is a bit 
obsolete, so it is planned to update to a newer stable version in Fraser.

For scenario naming changes, I think I can renew the scenarios template and 
show it in the SCENARIO list.

As for the Euphrates user guide, you can find it here:
http://docs.opnfv.org/en/stable-euphrates/submodules/yardstick/docs/testing/user/userguide/index.html

BRs
Rex

+---+
[cid:image001.png@01D0A50A.DD5A8F20]
+ Mingjiang Li (Rex) Mobile: +86 13761275017
+ Shanghai Institute, Huawei
+ No. , Xinjinqiao Road, Pudong, Shanghai, 201206, P.R.China
+---+

发件人: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Charalampos Kominos
发送时间: 2017年11月2日 19:44
收件人: 
opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] [yardstick] Opnfv Grafana results need upgrading.


Greetings to all

There is some confusion regarding the grafana results in 
http://testresults.opnfv.org/grafana/dashboard/

I see that in the dashboards there are results for B,C,D releases mixed in with 
E release
Is there a plan to change this?
Furthermore due to the scenario naming changes some results are pushed to the 
wrong place.
For example opnfv-armband (E release Fuel installer) pushes results in a dash 
named os-odl-nofeature-ha. instead of the TC cases.
This is very confusing in my opinion.

Also I believe the manual 
http://artifacts.opnfv.org/yardstick/docs/userguide/index.html#document-07-installation
 here is for C release so in some places it is obsolete.
Are there any plans to update it?

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

Re: [opnfv-tech-discuss] [availability]High Availability Project meeting on Oct. 18

[Gaoliang (kubi)]

Hi Srikanth,

Thanks for your email

I went through the etherpad page of HA test case Fraser Planning,  It looks 
good.  Yardstick Fraser planning[3] is also on going. We already plan to sync 
the requirement from HA Team.  I would like to join the next HA meeting to 
discuss more detail about further HA test cases.

What I did is to following the action point of Test WG weekly meeting[1], I 
briefly summarized the existing HA test cases in Yardstick repo and make a 
slide[2] to  introduce HA testing to Openstack QA team, because they also would 
like to do some “ destructive testing” in Openstack community.  I guess Georg 
is the key person to connected with Openstack QA team.

[1] 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-testperf/2017/opnfv-testperf.2017-09-28-15.00.html
[2] 
https://wiki.opnfv.org/pages/viewpage.action?pageId=5734608=/5734608/13206674/HA%20testing%20in%20Yardstick%20v0.6.pdf
[3] https://etherpad.opnfv.org/p/yardstick_release_f

Regards,
Kubi
发件人: Srikanth Vavilapalli [mailto:srikanth.vavilapa...@ericsson.com]
发送时间: 2017年10月27日 2:49
收件人: Georg Kunz <georg.k...@ericsson.com>; Fu Qiao <fuq...@chinamobile.com>; 
'Fan Yamei' <fanya...@chinamobile.com>; 'Tony Yin' <14_...@tongji.edu.cn>; 
'lansizhong' <lansizh...@chinamobile.com>; 'wucaifu' <wuca...@chinamobile.com>; 
'likaiyjy' <likai...@chinamobile.com>; 'wangxuyjy' <wangxu...@chinamobile.com>; 
Gaoliang (kubi) <jean.gaoli...@huawei.com>
抄送: 'juan_qiu' <juan_...@tongji.edu.cn>; 'Yue Yuan' <yuan@zte.com.cn>; 
'opnfv-tech-discuss' <opnfv-tech-discuss@lists.opnfv.org>
主题: RE: 答复: [opnfv-tech-discuss] [availability]High Availability Project 
meeting on Oct. 18

+kubi

Hi Kubi

I am referring to this e-mail thread in today’s test-wg call and here is the 
link to etherpad: https://etherpad.opnfv.org/p/HA_Testcases_F_Release where we 
are collating the High Availability test scenarios that we wanted to target for 
F release. As I understood from today’s call that you are also doing the 
similar exercise (by collecting inputs from OpenStack QA project and other 
sources) and it would be good if we can combine all these findings into the 
above etherpad.

Thanks
Srikanth

From: Georg Kunz
Sent: Wednesday, October 25, 2017 2:40 AM
To: Fu Qiao <fuq...@chinamobile.com<mailto:fuq...@chinamobile.com>>; 'Fan 
Yamei' <fanya...@chinamobile.com<mailto:fanya...@chinamobile.com>>; 'Tony Yin' 
<14_...@tongji.edu.cn<mailto:14_...@tongji.edu.cn>>; 'lansizhong' 
<lansizh...@chinamobile.com<mailto:lansizh...@chinamobile.com>>; 'wucaifu' 
<wuca...@chinamobile.com<mailto:wuca...@chinamobile.com>>; 'likaiyjy' 
<likai...@chinamobile.com<mailto:likai...@chinamobile.com>>; 'wangxuyjy' 
<wangxu...@chinamobile.com<mailto:wangxu...@chinamobile.com>>; Srikanth 
Vavilapalli 
<srikanth.vavilapa...@ericsson.com<mailto:srikanth.vavilapa...@ericsson.com>>
Cc: 'juan_qiu' <juan_...@tongji.edu.cn<mailto:juan_...@tongji.edu.cn>>; 'Yue 
Yuan' <yuan@zte.com.cn<mailto:yuan@zte.com.cn>>; 'opnfv-tech-discuss' 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: RE: 答复: [opnfv-tech-discuss] [availability]High Availability Project 
meeting on Oct. 18

Hi,

Ok, this gives us a bit more time for polishing the input on the the etherpad. 
Please note, that Nov 1st is a public holiday in Germany and that I most likely 
will not make it to the meeting. Srikanth will certainly (hopefully?) cover for 
me.

Best regards
Georg

From: Fu Qiao [mailto:fuq...@chinamobile.com]
Sent: Wednesday, October 25, 2017 4:34 AM
To: Georg Kunz <georg.k...@ericsson.com<mailto:georg.k...@ericsson.com>>; 'Fan 
Yamei' <fanya...@chinamobile.com<mailto:fanya...@chinamobile.com>>; 'Tony Yin' 
<14_...@tongji.edu.cn<mailto:14_...@tongji.edu.cn>>; 'lansizhong' 
<lansizh...@chinamobile.com<mailto:lansizh...@chinamobile.com>>; 'wucaifu' 
<wuca...@chinamobile.com<mailto:wuca...@chinamobile.com>>; 'likaiyjy' 
<likai...@chinamobile.com<mailto:likai...@chinamobile.com>>; 'wangxuyjy' 
<wangxu...@chinamobile.com<mailto:wangxu...@chinamobile.com>>; Srikanth 
Vavilapalli 
<srikanth.vavilapa...@ericsson.com<mailto:srikanth.vavilapa...@ericsson.com>>
Cc: 'juan_qiu' <juan_...@tongji.edu.cn<mailto:juan_...@tongji.edu.cn>>; 'Yue 
Yuan' <yuan@zte.com.cn<mailto:yuan@zte.com.cn>>; 'opnfv-tech-discuss' 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: 答复: 答复: [opnfv-tech-discuss] [availability]High Availability Project 
meeting on Oct. 18

Hi, Georg. No HA meeting plan for today. I will go through the etherpad page 
about the test cases. I suggest we have another project meeting next week at 
same time to 

Re: [opnfv-tech-discuss] 答复: hello. can i ask something?

[Gaoliang (kubi)]

Another channel for user supporting is the website http://ask.opnfv.org .  
There are already some Q & A about OPNFV installation. You can post your own 
questions if that can’t cover your need.


Regards,
Kubi
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Chigang (Justin)
发送时间: 2017年10月25日 11:32
收件人: 김경현 ; opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] 答复: hello. can i ask something?

Hi,

Here[1] is the wiki page for developer get start,  you can get how to 
participate a project or sign up opnfv mail list from it.
You just need to send mail to opnfv mail list[2], the everyone who signed in 
the mailing list will receive your mail.
If you want to try to install opnfv , the latest release “Euphrates” can be get 
from [3]. You can follow the installation guide to deploy.

Regards
Justin

[1]: https://wiki.opnfv.org/display/DEV/Developer+Getting+Started
[2]: https://www.opnfv.org/software/developer-tools/mailing-lists
[3]: https://www.opnfv.org/software/downloads

发件人: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 ???
发送时间: 2017年10月25日 10:36
收件人: 
opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] hello. can i ask something?

i want to ask something about opnfv like this 
page(https://lists.linux-foundation.org/pipermail/opnfv-tech-discuss/2017-October/thread.html)'s
 person.

do i just send email to 
opnfv-tech-discuss@lists.opnfv.org ? 
or any other steps in there?

i have less knowledge, so i hope you help me.

i want to ask installation about opnfv, compute node, control node.

thank you, have a good day!

-kyunghyun-



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

Re: [opnfv-tech-discuss] 答复: Stepping down

[Gaoliang (kubi)]

Uli ,

Thanks for your great effort to improve OPNFV Infra. 

It is a great honor to work with you in OPNFV. It seems that ETSI will have a 
new super star :)

Best Regards,
Kubi


-邮件原件-
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Chigang (Justin)
发送时间: 2017年10月24日 14:36
收件人: Ulrich Kleber 
抄送: TSC OPNFV ; TECH-DISCUSS OPNFV 

主题: [opnfv-tech-discuss] 答复: Stepping down

Uli,

Thanks for your great contribution in OPNFV infrastructure group and CI team. 
Wish you all the best in new position.

Regards
Justin

-邮件原件-
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Tapio Tallgren
发送时间: 2017年10月24日 13:31
收件人: Cooper, Trevor
抄送: TSC OPNFV; TECH-DISCUSS OPNFV
主题: Re: [opnfv-tech-discuss] Stepping down

Thanks Uli, especially for starting the scenario description and cleanup work!

-Tapio


On Mon, Oct 23, 2017 at 07:30:45PM +, Cooper, Trevor wrote:
> Yes agreed … thanks Uli for all your work and dedication to improve 
> the community. It’s been a pleasure to work with you.
> 
>  
> 
> /Trevor
> 
>  
> 
> From: opnfv-tech-discuss-boun...@lists.opnfv.org
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 
> Wenjing Chu
> Sent: Monday, October 23, 2017 10:28 AM
> To: Ulrich Kleber ; TSC OPNFV 
> ; TECH-DISCUSS OPNFV 
> 
> Subject: Re: [opnfv-tech-discuss] Stepping down
> 
>  
> 
> Thank you Uli for your long and distinguished contribution to OPNFV. 
> Look forward to seeing your work in ETSI!
> 
>  
> 
> Wenjing
> 
>  
> 
> From: opnfv-tsc-boun...@lists.opnfv.org [ 
> mailto:opnfv-tsc-boun...@lists.opnfv.org] On Behalf Of Ulrich Kleber
> Sent: Monday, October 23, 2017 6:12 AM
> To: TSC OPNFV ; TECH-DISCUSS OPNFV < 
> opnfv-tech-discuss@lists.opnfv.org>
> Subject: [opnfv-tsc] Stepping down
> 
>  
> 
> Hello community,
> 
> my company has assigned new work to me, so my time for OPNFV will be 
> very limited from now on.
> 
> Therefore I have to step down from Octopus PTL and from my committer 
> roles in Doctor and Escalator project.
> 
> Special thanks to Fatih and Jack in the Infra group; sorry I cannot 
> run the meetings with you anymore.
> 
>  
> 
> Octopus in recent months mainly did the scenario work which can be 
> followed up by the Infra group and
> 
> Xci. Therefore, if there is nobody else to step up as new octopus PTL, 
> I suggest to terminate the project.
> 
>  
> 
> I will be around but mainly listening, since my new work is still 
> related to NFV – mainly in ETSI.
> 
>  
> 
> Cheers,
> 
> Uli
> 

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

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

Re: [opnfv-tech-discuss] [yardstick] Yardstick test case details

[Gaoliang (kubi)]

Hi Venkat,

Thanks for your question.

In TC002 Yaml file, you can easily find it consists of two sections.

One is “Scenarios”,  the other is “Context”.

“Contexts” section is the description of pre-condition of testing. As 
TC002.yaml shown, you can configure the image, flavor , name ,affinity and 
network of Test VM(servers),  with this section, you will get a pre-condition 
env for Testing.  Yardstick will automatic setup the stack which are described 
in this section. In fact, yardstick use convert this section to heat template 
and setup the VMs by heat-client (Meanwhile, yardstick can support to convert 
this section to Kubernetes template to setup containers).

Go back to your question1, Two VMs are configured by keyword “servers”.  And 
“flavor ” will determine how many vCPU, how much memory for test VMs . As 
“yardstick-flavor” is a basic flavor which will be automatically created when 
you run command “yardstick env prepare”. “yardstick-flavor” is “ 1 vCPU 1G 
RAM,3G Disk”,

[cid:image001.png@01D342AA.D08D6FC0]







Moreover, you can configure your specific flavor as below, yardstick will setup 
the stack for you.
[cid:image002.png@01D342AC.E5A302B0]




Regarding to Question 2



“Scenarios” section is the description of  testing step, you can orchestrate 
the complex testing step through orchestrate scenarios.
Each scenario will do one testing step,  In one scenario , you can configure 
the type of scenario(operation) , runner type and SLA of the scenario..
 For TC002, We only have one step , that is Ping from host VM to target VM. In 
this step, we also have some detail operation implement ( such as ssh to VM, 
ping from VM1 to VM2. Get the latency, verify the SLA, report the result.)
If you want to get this detail implement , you can check with the scenario.py 
file. For Ping scenario, you can find it[1] in yardstick repo ( yardstick / 
yardstick / benchmark / scenarios / networking / ping.py)








Additional. Some basic concept of yardstick framework. You can find it in user 
guide chapter 3.2.2 [2], And we will to improve the developer guide for 
developers soon. Thanks for your question again.

Hope that would help for you understand yardstick framework.

[1] 
https://github.com/opnfv/yardstick/blob/stable/danube/yardstick/benchmark/scenarios/networking/ping.py
[2] 
https://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/03-architecture.html#concept

Regards,

Kubi

发件人: vven...@codeaurora.org [mailto:vven...@codeaurora.org]
发送时间: 2017年10月11日 15:37
收件人: chenjiankun <chenjiank...@huawei.com>; Gaoliang (kubi) 
<jean.gaoli...@huawei.com>; kristian.h...@gmail.com; 
opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] [yardstick] Yardstick test case details

Hi Jack/Kubi/Kristian and yardstick developers,

It would be grateful if you could please let me know on details to explore on 
the test cases for a specific test case say TC002 
(https://github.com/opnfv/yardstick/blob/stable/danube/tests/opnfv/test_cases/opnfv_yardstick_tc002.yaml)?
I understand the parameters but I would like to understand how yardstick 
executes like what are the parameters for two VMs, how many vCPUs, how much 
memory ?
In summary, would like to understand the exact execution details/internal 
commands of the test case, please point me to the source details in the 
yardstick repo.

Appreciate your help.

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

Re: [opnfv-tech-discuss] Fuel/Armband ODL scenario rename in Functest test results dashboard

[Gaoliang (kubi)]

Hi Ross,

Venkat's email reminder me that there are still some work for ODL scenario 
rename.

I saw you have upload a patch which is "add 
opnfv_os-odl-nofeature-noha_daily.yaml [1] for odl_l3 to odl rename" 

And It seems that we also need to add opnfv_os-odl-nofeature-ha_daily.yaml to 
Yardstick repo for odl_l3 to odl rename .

[1] https://gerrit.opnfv.org/gerrit/#/c/40895/

Regards,

Kubi

-邮件原件-
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 vven...@codeaurora.org
发送时间: 2017年9月13日 13:52
收件人: 'Alexandru Avadanii' ; 'RICHOMME Morgan 
IMT/OLN' 
抄送: opnfv-tech-discuss@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] Fuel/Armband ODL scenario rename in Functest test 
results dashboard

Hi Alex,
While your question is answered,
Request you to clarify :  This is also exported to Yardstick, Functest 
accordingly. I should feed there as os-odl-nofeature-ha say as an example or 
still os-odl_l3-nofeature-ha ??

Thanks
-Venkat

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alexandru 
Avadanii
Sent: Wednesday, September 13, 2017 4:50 AM
To: RICHOMME Morgan IMT/OLN 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Fuel/Armband ODL scenario rename in Functest test 
results dashboard

Hi,
Fuel and Armband projects renamed the ODL-L3 scenario to simply ODL, and 
dropped the ODL-L2 scenarios, as described in [1].
I noticed that the Functest results dashboard pages [2, 3] still use the old 
naming scheme, although the new scenario is also listed.
Would it be possible to cleanup obsolete scenarios?

Thank you,
Alex

[1] https://jira.opnfv.org/browse/FUEL-279
[2]
http://testresults.opnfv.org/reporting/master/functest/status-f...@x86.html
[3]
http://testresults.opnfv.org/reporting/master/functest/status-fuel@aarch64.h
tml

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

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

Re: [opnfv-tech-discuss] [yardstick] Yardstick results showing Null or Error

[Gaoliang (kubi)]

HI Venkat,

Sorry for the delay in responding.

Some comments in line.

Regards,
Kubi
发件人: vven...@codeaurora.org [mailto:vven...@codeaurora.org]
发送时间: 2017年9月12日 21:26
收件人: Gaoliang (kubi) <jean.gaoli...@huawei.com>; 
opnfv-tech-discuss@lists.opnfv.org; opnfv-us...@lists.opnfv.org; 'Alexandru 
Avadanii' <alexandru.avada...@enea.com>
主题: RE: [opnfv-tech-discuss] [yardstick] Yardstick results showing Null or Error

Hi Kubi, Alex(ARMBand)

Any inputs/clarifications on the below mail please ?

Thanks for your help.
-Venkat

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 
Venkateshwarlu Vangala
Sent: Saturday, September 9, 2017 4:12 PM
To: Gaoliang (kubi) 
<jean.gaoli...@huawei.com<mailto:jean.gaoli...@huawei.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
opnfv-us...@lists.opnfv.org<mailto:opnfv-us...@lists.opnfv.org>
Subject: [opnfv-tech-discuss] [yardstick] Yardstick results showing Null or 
Error


Hi Kubi and Yardstick team,

Thanks for your information on the yardstick earlier.
I just collected the old results from Grafana by going through each of the 
tests for a specific date range as suggested. Below is the table. Intel C 
release below points based on the Yardstick report.
Request you to please clarify the below questions and Sorry for many questions 
as this may be useful for others as wel.


  1.  Why some of the results of the test cases are showing either error or 
null if I query them as shown below as NA/error ?
[Kubi] I believe there should be some test date in influxdb during the time 
range. I will  give you the root cause after I check with the influxdb and 
grafana config. It should be related to the “Mean”  of Grafana function.

  1.  Is SLA to be defined for some cases ?
[Kubi] we have give some reference SLA for some test case. But that is not a 
standard. Just give by yardstick developer based on some testing experience. As 
I said, we will try to analyze the result by the Tool, then give some more 
reasonable SLA in future release.

  1.  For a particular test, the test runs for multiple iterations say on a 
specific day. How is the single number achieved ? Is it average of those 
multiple iterations on a specific day and how is Grafana picking the average of 
those multiple iterations ?
[Kubi] yes, It is average of those multiple iterations on a specific day, 
Grafana provide the Mean function for the data. It need admin root to config 
that with each graph.


  1.  How about other test cases as default only these test cases run say for 
os-nosdn-nofeature-noha ? Is it based on the scenarios ?
[Kubi]   we have different test suites for each scenario. Please check the 
below link
https://git.opnfv.org/yardstick/tree/tests/opnfv/test_suites
As the maximum time for each CI job is 3 hours,  we didn’t put all test cases 
into one scenario.  Only find some typical test cases to make them with CI jobs.

Please help in answering the questions.

Thanks
-Venkat






May 2,2017 to Aug 30,2017 tests conducted
















arm-pod1


Linux Foundation-pod2

/huawei-pod (Intel)


SLA


Intel

C-Release


Units


OPNFV_YARDSTICK_TC002_NETWORK LATENCY


1.26


1.08


10


0.55


ms


OPNFV_YARDSTICK_TC005_STORAGE PERFORMANCE


217.2


137.29


400


200


MB/s


OPNFV_YARDSTICK_TC010_MEMORY LATENCY


NA


1.61


30


1.2


ns


OPNFV_YARDSTICK_TC011_PACKET DELAY VARIATION BETWEEN VMs


0.1193


0.0133


 NA


0.0067


ms


OPNFV_YARDSTICK_TC012_MEMORY BANDWIDTH


3.7


19.8


15


17.6


GB/s


OPNFV_YARDSTICK_TC014_PROCESSING SPEED


610


3827


 NA


3150


score


OPNFV_YARDSTICK_TC037_LATENCY


NA(error)


NA(error)


 NA


15


ms


OPNFV_YARDSTICK_TC037_CPU LOAD


NA(error)


NA(error)


 NA


2


%


OPNFV_YARDSTICK_TC037_THROUGHPUT


NA(error)


NA(error)


 NA


433000


pps


OPNFV_YARDSTICK_TC037_PACKET LOSS


NA(error)


NA(error)


 NA


550


packets


OPNFV_YARDSTICK_TC069_Memory Bandwidth


13


29.4


6


20.45


GB/s


OPNFV_YARDSTICK_TC070_Memory Utilization


NA


NA


 NA


235


MB


OPNFV_YARDSTICK_TC071_Cache Utilization


NA


NA


 NA


208


MB


OPNFV_YARDSTICK_TC072_Network Utilization


NA


NA


 NA


200


KPPS


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

Re: [opnfv-tech-discuss] [opnfv-tsc] [announce] Opening nominations for Committers-at-Large TSC & Committer Board elections

[Gaoliang (kubi)]

Thank you Wenjing for nomination.

Thank you Ray. Yes, I humbly accept the nomination.

Regards,

Kubi

发件人: opnfv-tsc-boun...@lists.opnfv.org 
[mailto:opnfv-tsc-boun...@lists.opnfv.org] 代表 Raymond Paik
发送时间: 2017年9月7日 5:26
收件人: Wenjing Chu 
抄送: opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
主题: Re: [opnfv-tsc] [opnfv-tech-discuss] [announce] Opening nominations for 
Committers-at-Large TSC & Committer Board elections

Thanks Wenjing...

Kubi, do you accept the nomination?

Ray

On Wed, Sep 6, 2017 at 1:18 PM, Wenjing Chu 
> wrote:
I would like to nominate Kubi / Gaoliang (huawei) for commiter-at-large TSC 
member.
Kubi has been a long time project lead at Yardstick until recently and 
instrumental in bringing Yardstick to where it is today as a pillar of the 
performance testing projects. He’s also a very active community builder, 
organized both the first Shanghai and  first Beijing OPNFV meetups and workshop 
during OPNFV Summit. His experience and perspective will be a big plus for the 
TSC.

Regards
Wenjing

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org]
 On Behalf Of Raymond Paik
Sent: Tuesday, September 05, 2017 10:32 PM
To: 
opnfv-tech-discuss@lists.opnfv.org; 
opnfv-...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [announce] Opening nominations for 
Committers-at-Large TSC & Committer Board elections

All,

I don't believe I saw any nomination for either Committers-at-Large TSC or 
Committer Board elections  Yesterday was a holiday in the US, but this is still 
somewhat surprising...

Could someone to get things started please?  :-)

Thanks,

Ray

On Mon, Sep 4, 2017 at 9:31 PM, Raymond Paik 
> wrote:
Re-sending with the eligible committers link (the first link below) fixed...

Thanks,

Ray


On Sun, Sep 3, 2017 at 10:42 AM, Raymond Paik 
> wrote:
All,

I'm kicking off the nomination process for Committers-at-Large TSC (electing 5 
members) plus the Committer Board (electing 1) elections.

The list of eligible committers who can run for & vote in both elections are 
posted 
here, and 
I want to encourage all eligible committers to nominate community members who 
can represent the OPNFV technical community in both the TSC and the Board.  
Self nominations are also welcome.   As I mentioned earlier in the week, I hope 
to see a diverse group of community members represented--in terms of geography, 
gender, projects,  service providers/vendors, etc.--in the nominations.

Nominations should be posted to opnfv-tech-discuss & opnfv-tsc mailing lists by 
5pm Pacific Time on September 8th (Friday).  You are welcome to reply to this 
email or if you're sending out a separate note, please include phrases like 
"Committer Board nomination" or "Committer-at-Large TSC nomination" in email 
subjects.  In nomination statements, please list the following information:

  *   Which election (TSC vs. Board) the nomination is for
  *   Name of the nominee
  *   Organization
  *   A brief description of nominee's qualifications
As nominations are accepted, I will add them to this 
page.  There 
will be separate Condorcet ballot for these two elections, and they will be 
sent out by September 11th.

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] [yardstick] Yardstick Testresult Report???

[Gaoliang (kubi)]

Thanks Morgan .

I’m clear about that now.

Regards,

Kubi


发件人: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com]
发送时间: 2017年8月28日 15:47
收件人: Gaoliang (kubi) <jean.gaoli...@huawei.com>
抄送: vven...@codeaurora.org; Lvjing (Jing Lu) <lvji...@huawei.com>; 
opnfv-tech-discuss@lists.opnfv.org; opnfv-us...@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] [yardstick] Yardstick Testresult Report???

the trend line can cover a long period, it is based on the local file storing 
all the results
but a trend line is associated with a scenario and the list of scenarios is 
built based on the results over the last 10 days
that is why if there is no run since 10 days, we have an empty page

In deed we have fortunately results for all the installers

[morgan@gce-opnfv-sandbox-fbrockners danube]$ cat scenario_history.txt |grep 
compass |wc -L
57
[morgan@gce-opnfv-sandbox-fbrockners danube]$ cat scenario_history.txt |grep 
fuel |wc -L
63
[morgan@gce-opnfv-sandbox-fbrockners danube]$ cat scenario_history.txt |grep 
apex |wc -L
53
[morgan@gce-opnfv-sandbox-fbrockners danube]$ cat scenario_history.txt |grep 
joid |wc -L
54

but
last run on
- compass: 28/8
- fuel: 11/8
- apex: 20/5
- joid: 3/8

The reporting page really reflects the CI activity, we could amend the 
reporting to consider all the scenarios stored in the local file rather than 
considering the scneario over the last 10 days...but empty pages mean something 
(no CI activity)

In Euphrates we introduced the scenario in the test API. It is not used yet but 
it should replace the local file

/Morgan

On 28/08/2017 09:33, Gaoliang (kubi) wrote:

"In functest we save the status after each release (Danube 1.0, Danube2.0, 
Danube 3.0) in our repo"



That's a best practice for reporting.  We should followed that at E release :)



By the way, Is it possible to show the Trend picture even if there is  no data 
in last 10 days.  we may don't need to see the score and status which are 
calculated by last 10 day's result but a trend from one or two month result  
for each scenario.



Such as compass page, we can see the trend from April to August

http://testresults.opnfv.org/reporting/yardstick/release/danube/index-status-compass.html



Regards,



Kubi





-邮件原件-

发件人: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 
morgan.richo...@orange.com<mailto:morgan.richo...@orange.com>

发送时间: 2017年8月28日 14:47

收件人: vven...@codeaurora.org<mailto:vven...@codeaurora.org>; Lvjing (Jing Lu) 
<lvji...@huawei.com><mailto:lvji...@huawei.com>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
opnfv-us...@lists.opnfv.org<mailto:opnfv-us...@lists.opnfv.org>

主题: Re: [opnfv-tech-discuss] [yardstick] Yardstick Testresult Report???



regarding the reporting link, it always deals with a sliding windows processing 
the results from the last 10 days if no results since 10 days for the given 
version => no results so currently no Danube results, some runs on master => 
http://testresults.opnfv.org/reporting/yardstick/release/master/index-status-fuel.html



In functest we save the status after each release (Danube 1.0, Danube2.0, 
Danube 3.0) in our repo



it is possible to rebuild the status assuming that we save the scores in a 
local files but it will be just a "release status" and it will not be as 
detailed as the first link you mentioned.



/Morgan



On 26/08/2017 09:46, vven...@codeaurora.org<mailto:vven...@codeaurora.org> 
wrote:

And on the other hand, If I go to the below link it is showing empty,

How can I get the result of each Yardstick result performnace numbers

. Please help

http://testresults.opnfv.org/reporting/yardstick/release/danube/index-

status-fuel.html



_



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

Re: [opnfv-tech-discuss] [yardstick] Yardstick Testresult Report???

[Gaoliang (kubi)]

"In functest we save the status after each release (Danube 1.0, Danube2.0, 
Danube 3.0) in our repo"

That's a best practice for reporting.  We should followed that at E release :)

By the way, Is it possible to show the Trend picture even if there is  no data 
in last 10 days.  we may don't need to see the score and status which are 
calculated by last 10 day's result but a trend from one or two month result  
for each scenario.

Such as compass page, we can see the trend from April to August
http://testresults.opnfv.org/reporting/yardstick/release/danube/index-status-compass.html

Regards,

Kubi


-邮件原件-
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 
morgan.richo...@orange.com
发送时间: 2017年8月28日 14:47
收件人: vven...@codeaurora.org; Lvjing (Jing Lu) ; 
opnfv-tech-discuss@lists.opnfv.org; opnfv-us...@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] [yardstick] Yardstick Testresult Report???

regarding the reporting link, it always deals with a sliding windows processing 
the results from the last 10 days if no results since 10 days for the given 
version => no results so currently no Danube results, some runs on master => 
http://testresults.opnfv.org/reporting/yardstick/release/master/index-status-fuel.html

In functest we save the status after each release (Danube 1.0, Danube2.0, 
Danube 3.0) in our repo

it is possible to rebuild the status assuming that we save the scores in a 
local files but it will be just a "release status" and it will not be as 
detailed as the first link you mentioned.

/Morgan

On 26/08/2017 09:46, vven...@codeaurora.org wrote:
> And on the other hand, If I go to the below link it is showing empty, 
> How can I get the result of each Yardstick result performnace numbers 
> . Please help 
> http://testresults.opnfv.org/reporting/yardstick/release/danube/index-
> status-fuel.html

_

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 mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [yardstick] Yardstick Testresult Report???

[Gaoliang (kubi)]

Hi Venkat,

The result of each Yardstick result performnace numbers are located at InfluxDB 
of community,
You can view the data with the Grafana page.

https://testresults.opnfv.org/grafana/dashboard/db/yardstick-tc005   
(user/password: opnfv/opnfv)

Tips:
You can select the time range with the grafana page,  June 18th to July 18th 
would be a good choice for Danube 3.0
[cid:image001.png@01D31FF5.03725730] [cid:image002.png@01D31FF5.72153F40]

Meanwhile, you can select each test case with the grafana.
[cid:image003.png@01D31FF6.3208CDD0]

Regards,
Kubi


发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 vven...@codeaurora.org
发送时间: 2017年8月26日 15:47
收件人: Lvjing (Jing Lu) ; opnfv-tech-discuss@lists.opnfv.org; 
opnfv-us...@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] [yardstick] Yardstick Testresult Report???

Hi Jing Lu,

Thanks for the reply. I was specifically looking for the detailed analysis of 
the test result done and the summary written like this.
http://artifacts.opnfv.org/yardstick/colorado/docs/results/index.html#test-results-for-os-nosdn-nofeature-ha


And on the other hand, If I go to the below link it is showing empty, How can I 
get the result of each Yardstick result performnace numbers . Please help 
http://testresults.opnfv.org/reporting/yardstick/release/danube/index-status-fuel.html


Venkat


From: Lvjing (Jing Lu) [mailto:lvji...@huawei.com]
Sent: Saturday, August 26, 2017 12:57 PM
To: vven...@codeaurora.org; 
opnfv-tech-discuss@lists.opnfv.org; 
opnfv-us...@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [yardstick] Yardstick Testresult Report???

Hi,

You can find it at:
  
http://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/release/release-notes/release-notes.html#scenario-matrix

regards,
Jing Lu
From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 
vven...@codeaurora.org
Sent: Saturday, August 26, 2017 3:05 PM
To: 
opnfv-tech-discuss@lists.opnfv.org; 
opnfv-us...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [yardstick] Yardstick Testresult Report???

Request you to please let me know.

From: vven...@codeaurora.org 
[mailto:vven...@codeaurora.org]
Sent: Thursday, August 24, 2017 11:52 AM
To: 'opnfv-tech-discuss@lists.opnfv.org' 
>
Subject: [opnfv-tech-discuss] [yardstick] Yardstick Testresult Report???

Hi,

Request you to please point me to the report similar to below for Danube 3.0 on 
both x86 and arm pods?

http://artifacts.opnfv.org/yardstick/colorado/docs/results/index.html

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

[opnfv-tech-discuss] Reminder : [opnfv-users] [opnfv-meetup] OPNFV Beijing Meetup During the Design Summit

[Gaoliang (kubi)]

Welcome to Beijing Meetup at tomorrow afternoon.

发件人: opnfv-users-boun...@lists.opnfv.org 
[mailto:opnfv-users-boun...@lists.opnfv.org] 代表 Gaoliang (kubi)
发送时间: 2017年6月8日 19:02
收件人: opnfv-tech-discuss@lists.opnfv.org; opnfv-us...@lists.opnfv.org
主题: [opnfv-users] [opnfv-meetup] OPNFV Beijing Meetup During the Design Summit

Hi Community,

As most of us will come to the Beijing summit, It would be great chance to hold 
an OPNFV meetup that could gather people from China and other countries.

Qiao Fu and me are trying to hold this OPNFV meetup during the design summit. 
Like what we have done in Beijing and shanghai meetup, we could have face to 
face discussions and exchange our opinions pleasantly

The current consideration of the topic is the challenges and practice in NFV 
integration and testing Area.

You can also find the details of the meetup as follows
.
Topic

Challenges and Practice in NFV Integration and Testing Area

Time

14:00 �C 16:00, June 13th, 2017. ( Day2 for Design Summit )

Venue

Room Red Tea at B1 floor of the Ritz Carlton.
Please proceed to the lower level and follow the short hallway that connects 
the two hotels if you staying at JW.Marriott
http://www.ritzcarlton.com/en/hotels/china/beijing/meetings/meeting-room-details/red-tea#fndtn-Floorplan

Agenda


Time

Topic

14:00-15:00

Challenges and Practice in NFV Integration and Testing Area for Operators

15:00-15:20

Practice in NFV Integration and Testing Area for Vendors

15:20-16:00

How OPNFV Projects Help Solving Pain Points and Challenges for the Industry




We are very excited to see you joining the meetup.


Regards,

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

[opnfv-tech-discuss] [opnfv-meetup] OPNFV Beijing Meetup During the Design Summit

[Gaoliang (kubi)]

Hi Community,

As most of us will come to the Beijing summit, It would be great chance to hold 
an OPNFV meetup that could gather people from China and other countries.

Qiao Fu and me are trying to hold this OPNFV meetup during the design summit. 
Like what we have done in Beijing and shanghai meetup, we could have face to 
face discussions and exchange our opinions pleasantly

The current consideration of the topic is the challenges and practice in NFV 
integration and testing Area.

You can also find the details of the meetup as follows
.
Topic

Challenges and Practice in NFV Integration and Testing Area

Time

14:00 - 16:00, June 13th, 2017. ( Day2 for Design Summit )

Venue

Room Red Tea at B1 floor of the Ritz Carlton.
Please proceed to the lower level and follow the short hallway that connects 
the two hotels if you staying at JW.Marriott
http://www.ritzcarlton.com/en/hotels/china/beijing/meetings/meeting-room-details/red-tea#fndtn-Floorplan

Agenda


Time

Topic

14:00-15:00

Challenges and Practice in NFV Integration and Testing Area for Operators

15:00-15:20

Practice in NFV Integration and Testing Area for Vendors

15:20-16:00

How OPNFV Projects Help Solving Pain Points and Challenges for the Industry




We are very excited to see you joining the meetup.


Regards,

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

[opnfv-tech-discuss] [opnfv-tsc][test-wg][yardstick] Yardstick New PTL Election Done

[Gaoliang (kubi)]

Hi TSC and community,

According to Yardstick PTL Election Process[1], we started the Yardstick PTL 
election at three weeks ago, we spend two weeks to nomination and one week to 
vote[2].  (All committers +2 ) .

Now, we have the new PTL of Yardstick! He is Ross Brattain 
(ross.b.bratt...@intel.com)
 . Congratulation to Ross !

Ross who is the most active committer in last four months made yardstick 
support python3 and introduced the NSB into Yardstick with Deepak.
As a excellent committer, He brings lots of valuable comments for code review 
and new energy to Yardstick team. [3]
I do believe that Ross will lead the Yardstick and the team better and better.

I will step down as PTL and still keep active in testing working group as a 
yardstick committer. I would like to extend our sincere thanks to yardstick 
team and community for your kindly support and help.
@ helpdesk, please help to deal with the admin rights for new PTL. Thanks


[1] https://wiki.opnfv.org/display/yardstick/Yardstick+PTL+Election
[2] https://gerrit.opnfv.org/gerrit/#/c/35141/
[3] https://gerrit.opnfv.org/gerrit/#/q/owner:ross.b.brattain%2540intel.com

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

[opnfv-tech-discuss] [test-wg] [yardstick]Reminder: Yardstick PTL Election

[Gaoliang (kubi)]

Hi All,

This is a reminder: The nomination of Yardstick PTL will be end at 24 hours 
later.

For now, Ross Brattain who is the most active committer of yardstick has been 
nominated, other nominations are still welcome within the deadline.

Regards,
Kubi
发件人: Cooper, Trevor [mailto:trevor.coo...@intel.com]
发送时间: 2017年5月6日 2:53
收件人: Gaoliang (kubi) 
<jean.gaoli...@huawei.com<mailto:jean.gaoli...@huawei.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
抄送: test-wg <test...@lists.opnfv.org<mailto:test...@lists.opnfv.org>>; 
Brattain, Ross B <ross.b.bratt...@intel.com<mailto:ross.b.bratt...@intel.com>>
主题: RE: [test-wg] [opnfv-tech-discuss][yardstick] Yardstick PTL Election

Hi Kubi

Thanks for everything that you have done over the past 2 releases … you have 
done an exceptional job to keep Yardstick progressing as a key part of the 
OPNFV test toolchain.

I would like to nominate Ross Brattain for the position of PTL. Ross has been 
an active committer for about 4 months.

Trevor


From: test-wg-boun...@lists.opnfv.org<mailto:test-wg-boun...@lists.opnfv.org> 
[mailto:test-wg-boun...@lists.opnfv.org] On Behalf Of Gaoliang (kubi)
Sent: Friday, May 05, 2017 5:44 AM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: test-wg <test...@lists.opnfv.org<mailto:test...@lists.opnfv.org>>
Subject: [test-wg] [opnfv-tech-discuss][yardstick] Yardstick PTL Election

Hi All ,

To keep the team diversity, bring new ideas and energy, we have finalized the 
Yardstick PTL election process[1] with team(similar with Functest’s process).

We will start the Yardstick PTL election Process today, As the process 
described, “Calls for nomination will be open for a 2 weeks process”,  so we 
will end the nomination at May 19th

Election would be open to any Yardstick committer[2] (+2/-2) , Then we will 
have one week to vote with http://civs.cs.cornell.edu/

As I have been yardstick PTL for 2 release(C, D), I will step down once new PTL 
has been elected.  All nomination are warmly welcome, let’s make yardstick 
better and better

So Please feel free to nominate yourself and other committers before May 19th 
with this email thread.  Thanks :)


[1] https://wiki.opnfv.org/display/yardstick/Yardstick+PTL+Election
[2] https://wiki.opnfv.org/display/yardstick/People


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

[opnfv-tech-discuss] [test-wg][yardstick] Yardstick PTL Election

[Gaoliang (kubi)]

Hi All ,

To keep the team diversity, bring new ideas and energy, we have finalized the 
Yardstick PTL election process[1] with team(similar with Functest's process).

We will start the Yardstick PTL election Process today, As the process 
described, "Calls for nomination will be open for a 2 weeks process",  so we 
will end the nomination at May 19th

Election would be open to any Yardstick committer[2] (+2/-2) , Then we will 
have one week to vote with http://civs.cs.cornell.edu/

As I have been yardstick PTL for 2 release(C, D), I will step down once new PTL 
has been elected.  All nomination are warmly welcome, let's make yardstick 
better and better

So Please feel free to nominate yourself and other committers before May 19th 
with this email thread.  Thanks :)


[1] https://wiki.opnfv.org/display/yardstick/Yardstick+PTL+Election
[2] https://wiki.opnfv.org/display/yardstick/People

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

Re: [opnfv-tech-discuss] [Functest] Tagging and docker build completed for Danube.1.0

[Gaoliang (kubi)]

It should be "1.0".  I tried with "danube1.0",  the result was 
"danube.danube.1.0"

regards
kubi

Sent from HUAWEI AnyOffice
发件人：Yujun Zhang
收件人：Jose Lausuch,Soni, Anand Kumar via opnfv-tech-discuss,
时间：2017-04-01 08:55:09
主题:Re: [opnfv-tech-discuss] [Functest] Tagging and docker build completed for 
Danube.1.0

Hi, Jose

Thanks for the hint. Should RELEASE_VERSION be `1.0` or `danube.1.0`. It seems 
the release name is automatically prefixed in jjb.


# Get tag version
echo "Current branch: $BRANCH"

if [[ "$BRANCH" == "master" ]]; then
DOCKER_TAG="latest"
else
if [[ -n "${RELEASE_VERSION-}" ]]; then
release=${BRANCH##*/}
DOCKER_TAG=${release}.${RELEASE_VERSION}
# e.g. colorado.1.0, colorado.2.0, colorado.3.0
else
DOCKER_TAG="stable"
fi
fi

On Sat, Apr 1, 2017 at 1:52 AM Jose Lausuch 
> wrote:

Hi,



I did it manually from the latest built “stable” image when I tagged the repo. 
The Jenkins job we have allows you to do that automatically specifying the tag 
in the RELEASE_VERSION field (see below).



You might need rights in Jenkins to run this job. If you have problems let me 
know and I can trigger the build for you.





[cid:image001.png@01D2AA58.4D0DA6F0]





From: Yujun Zhang (ZTE) 
[mailto:zhangyujun+...@gmail.com]
Sent: Friday, March 31, 2017 17:22 PM
To: Jose Lausuch; TECH-DISCUSS OPNFV
Subject: Re: [opnfv-tech-discuss] [Functest] Tagging and docker build completed 
for Danube.1.0



Hi, Jose,



When will the docker build with tag be triggered?



Besides tagging in git, is there anything else  required to make it happen?



On Fri, Mar 31, 2017 at 10:44 PM Jose Lausuch 
> wrote:

Hi,



Functest repo ready with tags:

danube.1.0 : 
https://gerrit.opnfv.org/gerrit/gitweb?p=functest.git;a=tag;h=refs/tags/danube.1.0

danube.1.RC1: 
https://gerrit.opnfv.org/gerrit/gitweb?p=functest.git;a=tag;h=refs/tags/danube.1.RC1



Docker image built with tag “danube.1.0”

https://hub.docker.com/r/opnfv/functest/tags/





Thanks,

Jose

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

--

Yujun Zhang

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

Re: [opnfv-tech-discuss] Request to contribute to yardstick

[Gaoliang (kubi)]

Hi Jing,

Warmly welcome to Yardstick team:)
I’m very glad to know your team have used Yardstick to benchmark your Software 
and extend the framework. That would be a very good news for yardstick.
So I added you into Yardstick Contributors List[1], I will send the your 
attachment to Yardstick team to review.
Welcome to Join the Yardstick Weekly Meeting[2] to discuss:)

[1]  https://wiki.opnfv.org/display/yardstick/People
[2] https://wiki.opnfv.org/display/yardstick/Meetings

Regards,
Kubi
发件人: Zhang, Jing C. (Nokia - CA/Ottawa) [mailto:jing.c.zh...@nokia.com]
发送时间: 2017年3月28日 2:30
收件人: Gaoliang (kubi) <jean.gaoli...@huawei.com>
抄送: opnfv-tech-discuss@lists.opnfv.org
主题: Request to contribute to yardstick

Dear Yardstick,

We, Nokia Cloudband, have been using Yardstick to benchmark our Cloudband 
Intrastructure Software (CBIS) since Colorado is released last October, mainly 
in areas of throughput and latency.

We are big fans of the framework and have done a list of extenstions, our 
benchmarking results are well received by our partners and cusstomers.

I have attached a high level review of contents we propose to contribute, 
please review and let me know of your decisions. After this, we plan to move to 
the new Danube release when it becomes available.

Thank you and Best Regards

Jing


Jing Zhang
System Architect,
Cloudband, Nokia
External: +1-613-784-1839
OnNet: 2-825-1839



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

[opnfv-tech-discuss] 答复: [functest][dovetail] OpenStack HTTPS transport support in functest/dovetail

[Gaoliang (kubi)]

Hi  Wenjing,

Yardstick team has fixed the https issue with Jack Chan‘s help .

The patch had been merged with stable branch.
https://gerrit.opnfv.org/gerrit/#/c/30319/

@morgan and Jose, I think we should add some verification for  HTTPS  in daily 
jobs with a specific pod.
Otherwise, we may make that failed again.

Regards,
Kubi

发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Wenjing Chu
发送时间: 2017年3月11日 2:27
收件人: Julien ; yaohelan ; Tomofumi 
Hayashi ; trevor.coo...@intel.com; 
opnfv-tech-discuss@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] [functest][dovetail] OpenStack HTTPS transport 
support in functest/dovetail

+1

Does yardstick have the same issue? If it does, can we have a fix too in 
Danube. Thanks.

Wenjing

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Julien
Sent: Thursday, March 09, 2017 7:27 PM
To: yaohelan >; Tomofumi 
Hayashi >; 
trevor.coo...@intel.com; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [functest][dovetail] OpenStack HTTPS 
transport support in functest/dovetail

Hi all,

Maybe this will be a good guideline for all OPNFV projects when they consume or 
provide APIs.

Regards,
Julien



yaohelan >于2017年3月10日周五 
上午11:15写道：
Hi Tomofumi,

I am a committer of Functest. I will try to enable HTTPS for Functest.

There is a JIRA item tracking the status.
https://jira.opnfv.org/browse/FUNCTEST-757


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org]
 On Behalf Of Tomofumi Hayashi
Sent: Thursday, March 02, 2017 9:14 PM

To: trevor.coo...@intel.com; 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [functest][dovetail] OpenStack HTTPS transport 
support in functest/dovetail

Hi folks,

Let me clarify HTTPS support status and plan of functest/yardstick/dovetail.

I tried to run functest/dovetail against TripleO deployment and find that 
functest script, leveraged by dovetail, only works with HTTP (!= HTTPS) for 
OpenStack API (see verify_connectivity(): functest/ci/check_os.py). In 
addition, more modification is required certificate (such as self-signed one).

At that time, OPNFV testing project is mainly consumed by OPNFV platforms (e.g. 
Apex). But in the future, at least dovetail should be used for C (compliance 
and certification) in various OpenStack platform and some of them does not 
support HTTP transport for OpenStack API (mostly due to security reason). So I 
suppose we should support HTTPS OpenStack API in dovetail and functest.

What do you think about it?

Regards,
Tomofumi
___
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

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][danube] MS6 compliance assessment

[Gaoliang (kubi)]

Hi David,

This is the reply for yardstick about MS6 compliance assessment
Test Framework Projects
1.Please provide a list of commits for your self-validation tests.

-   Yardstick has unit-test coverage gate included in the ci verify job, 
you can find most of the patches in the link below:

-   https://gerrit.opnfv.org/gerrit/#/q/project:yardstick+test+case

Preliminary Documentation Requirement
1.Please provide a link to the preliminary documentation for your project.

-   Below is the newest documentation for yardstick:

-   http://artifacts.opnfv.org/yardstick/docs/userguide/index.html
Best Regards,
kubi


发件人: opnfv-project-leads-boun...@lists.opnfv.org 
[mailto:opnfv-project-leads-boun...@lists.opnfv.org] 代表 David McBride
发送时间: 2017年2月23日 4:30
收件人: opnfv-project-le...@lists.opnfv.org; TECH-DISCUSS OPNFV 

主题: [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] [qtip][yardstick] Q on integration

[Gaoliang (kubi)]

Hi Yujun，

Sure, I added the topic into this week meeting agenda[1](US time slot with 
GTM), hope we will have a great discussion at the meeting.

[1] https://wiki.opnfv.org/display/yardstick/Meetings

Regards,
Kubi
From: Yujun Zhang [mailto:zhangyujun+...@gmail.com]
Sent: Sunday, February 05, 2017 10:06 AM
To: TECH-DISCUSS OPNFV; Gaoliang (kubi)
Subject: Re: [qtip][yardstick] Q on integration

Dear yardsticker,

As suggested in last yardstick meeting[1], I've updated the QTIP architecture 
to introduce an even more simpler plugin mode[2]. We may discuss it in next 
Yardstick meeting.

Do you think it will be OK? @Kubi

The discussion has been lasting for months IIRC. We really need to make 
decision ASAP otherwise we are unlikely to catch up with Danube release.

[1]: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-yardstick/2017/opnfv-yardstick.2017-01-24-00.30.log.html
[2]: 
https://wiki.opnfv.org/display/qtip/Architecture#Architecture-PluginMode(Melody)

On Tue, Jan 24, 2017 at 11:47 AM Yujun Zhang 
<zhangyujun+...@gmail.com<mailto:zhangyujun%2b...@gmail.com>> wrote:
Dear all

I reviewed the meeting log[1] and it seems we have several questions to 
clarify. Feel free to comment.

1. how to integrate

option 1: as a server like original proposal[2]
option 2: as a module

Both are OK to me, if it is YardStick's team to decide to integrate as a 
module, we need to revise the proposal and QTIP will provide full support on it 
as well.

2. testing vs benchmarking

For sure benchmarking requires testing data. Benchmarking is one method/purpose 
of performance testing. Besides that, we may also use testing data for 
verification or validation. You may also use benchmarking result for 
verification or validation.

3. benchmarking in YardStick or testing in QTIP

This is not a battle between two projects. We chase different targets and have 
common methodology.

QTIP may consume testing data from YardStick but not all of them and not only 
from YardStick.

YardStick may use QTIP as benchmarking module or implement its own module. It's 
up to YardStick team's decision and I'm fine with either way.

[1]: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-yardstick/2017/opnfv-yardstick.2017-01-24-00.30.log.html
[2]: https://wiki.opnfv.org/display/yardstick/Yardstick-Qtip+integration
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [test-wg] [all] TestPerf EcoSystem diagram now editable

[Gaoliang (kubi)]

Hi Yunjun,

Thanks for your work to make the TestPerf Ecosystem image editable. But I ‘m a 
little confused with the rule of the TestPerf EcoSystem Diagram modification.
It seems that you have modified the  TestPerf Ecosystem structure.  I ‘m not 
sure if it is a good way to modify the Ecosystem Diagram without agreement of 
whole testing community.
All the performance test projects are involved in Benchmark area. I guess what 
Qtip want to do is to calculate the score from the Yardstick test result. So I 
guess we still need to have a discussion with test projects about the structure 
and the key words of each area. Thanks.

Regards,
Kubi

发件人: test-wg-boun...@lists.opnfv.org [mailto:test-wg-boun...@lists.opnfv.org] 
代表 Yujun Zhang
发送时间: 2016年12月15日 21:05
收件人: test-wg
抄送: TECH-DISCUSS OPNFV
主题: [test-wg] [all] TestPerf EcoSystem diagram now editable

Hi testers,

I have replaced the previous image of TestPerf EcoSystem with an editable 
diagram in the overview section of testperf wiki page[1]. Please review and 
amend if something is missing.

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

Re: [opnfv-tech-discuss] [yardstick] Nomination of Mingjiang, Zhihui, Kanglin and Jing as committer to Yardstick

[Gaoliang (kubi)]

Hi TSC,

I would like to inform the TSC that Zhihui Wu (ZTE),  Kanglin (Tongji 
University),  Mingjiang and Jing(Huawei) have been added as committers to the 
Yardstick.
All patches have been approved unanimously. .
https://gerrit.opnfv.org/gerrit/#/c/22911/ Zhihui Wu
https://gerrit.opnfv.org/gerrit/#/c/22913/ Kanglin Yin
https://gerrit.opnfv.org/gerrit/#/c/22909/ Mingjiang Li
https://gerrit.opnfv.org/gerrit/#/c/22915/ Jing Lu

Meanwhile, Jingwen Hou（Huawei）, Qi Liang（Huawei） and Wenjing Chu（Huawei） have 
resigned as committers to Yardstick, I have added the their original retirement 
e-mails into the attachment.
https://gerrit.opnfv.org/gerrit/#/c/23817/

Regards,

Kubi


发件人: Gaoliang (kubi)
发送时间: 2016年10月10日 19:24
收件人: 'jorgen.w.karls...@ericsson.com'; Houjingwen; Wenjing Chu; liangqi (D); 
Gaoliang (kubi); 'vincenzo.m.riccob...@intel.com'
抄送: limingjiang; 'wu.zhih...@zte.com.cn'; '14_...@tongji.edu.cn'; Lvjing 
(Network Platform Development Mgmt Dept); 'opnfv-tech-discuss@lists.opnfv.org'
主题: [opnfv-tech-discuss] [yardstick] Nomination of Mingjiang, Zhihui, Kanglin 
and Jing as committer to Yardstick

Hi Yardstick Committers.

I would like to nominate Mingjiang Li as committer to Yardstick.
 He has been one of the most active Yardstick contributors during Colorado 
development phase. He did lots of contributions to generic test cases (net 
latency between nodes, throughput between nodes, IPV6 test case), Framework 
(test case show CLI, Reporting, test suite evolution ) and 
documentation(Userguide). Meanwhile, he also gave two presentations at Testing 
Weekly Meeting and Yardstick Weekly Meeting.
https://gerrit.opnfv.org/gerrit/#/q/owner:limingjiang%2540huawei.com+project:yardstick
 Please cast your vote on Gerrit: https://gerrit.opnfv.org/gerrit/#/c/22909/

I would like to nominate Zhihui Wu as committer to Yardstick.
She has been one of the most active Yardstick contributors during Colorado 
development phase. She did lots of contributions to DPDK testing (latency), 
include DPDK test cases and DPDK images, ZTE Pod maintain with Yardstick CI 
job, Grafana Update.
https://gerrit.opnfv.org/gerrit/#/q/owner:wu.zhihui1%2540zte.com.cn+project:yardstick
 Please cast your vote on Gerrit: https://gerrit.opnfv.org/gerrit/#/c/22911/

I would like to nominate Kanglin Yin as committer to Yardstick.
He has been one of the most active Yardstick contributors during Colorado 
development phase. He did lots of contributions to reliability testing, include 
enhanced HA testing framework and 10 HA test cases, Also gave a presentation 
about HA testing at Shanghai OPNFV Meetup.
https://gerrit.opnfv.org/gerrit/#/q/owner:14_ykl%2540tongji.edu.cn+status:merged
Please cast your vote on Gerrit: https://gerrit.opnfv.org/gerrit/#/c/22913/

I would like to nominate Jing Lu as committer to Yardstick.
He has been one of the most active Yardstick contributors during Colorado 
development phase. He did lots of contributions to generic test cases(RAMspeed, 
MemoryLoad, CacheStat, ComputeCapacity, NetUtilization), framework(multiple 
target VMs support, Yardstick plugin, StorPerf and VSperf Integration) and 
documentation(Release Note). Also he gave two presentations about yardstick at 
Berlin Summits.
https://gerrit.opnfv.org/gerrit/#/q/owner:lvjing5%2540huawei.com+status:merged
Please cast your vote on Gerrit: https://gerrit.opnfv.org/gerrit/#/c/22915/



Regards,
Kubi

--- Begin Message ---
Thanks. Yes, I'd like to resign and please remove me as committer in yardstick.

Regards
Wenjing

From: Gaoliang (kubi)
Sent: Wednesday, October 19, 2016 3:33 AM
To: Wenjing Chu <wenjing@huawei.com>
Subject: [Yardstick] Committers list update confirmation

Hi Wenjing,

I hope you're well. I noticed that you have been inactive for quite a while. I 
sincerely appreciate your remarkable contribution for the Yardstick Project. As 
you know, it is important for OPNFV projects to maintain their list of 
committers, so we can keep the project active and diversified. Hence I'd like 
to confirm whether you are willing to continue as a committer to Yardstick. If 
not, I would like to remove you from the committer list.

On behalf of the team, thank you for your contributions over the past year.

Regards,

Kubi


--- End Message ---
--- Begin Message ---
Please update the committers list .

Thanks

发件人: Gaoliang (kubi)
发送时间: 2016年10月19日 18:31
收件人: Houjingwen
主题: [Yardstick] Committers list update confirmation

Hi Jingwen,

I hope you're well. I noticed that you have been inactive for quite a while. I 
sincerely appreciate your remarkable contribution for the Yardstick Project. As 
you know, it is important for OPNFV projects to maintain their list of 
committers, so we can keep the project active and diversified. Hence I’d like 
to confirm whether you are willing to continue as a committer to Yardstick. If 
not, I would like to remove you from the committer list.

On behalf of the team, thank you for your contributions over the past year.

R

Re: [opnfv-tech-discuss] CI evolution on impact on test projects

[Gaoliang (kubi)]

Hi ,

Thanks for the great slides, CI evolution is definitely an importing thing in 
Danube release.

for yardstick in CI, the status is as below:

definition of smoke test / weekly scope / test slicing
 ->Yardstick have drafted the proposal of test slicing in Colorado release, but 
the framework do not support it in c, we're planning to support it in Danube

Automatic selection of tests according to scenarios
->Yardstick already support executing a scenario via a test-suite yaml in 
Colorado.
Selection is not automatic, it need to be defined in a scenario test-suite yaml.

Test used for installer gating -> no

scenario scoring -> yes, but yardstick only calculate the score by the scenario 
fail/pass status, after Slicing of Yardstick Test cases, Yardstick will include 
Tier score in Danube.

I agree with Jose about a layer between CI (Jenkins) and the test project. That 
would be helpful for all test projects. Let 's discuss details in OpenStack 
Summit.

Regards,

Kubi

-邮件原件-
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Jose Lausuch
发送时间: 2016年10月18日 16:01
收件人: morgan.richo...@orange.com; test...@lists.opnfv.org
抄送: yaohelan; serena feng; opnfv-tech-discuss@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] CI evolution on impact on test projects

Hi,

Although it took a while to go through all your slides and understand them all 
(the 2 big example slides helped a lot), I agree in general with what you 
explain. There are some confusing assumptions like   "if a case(weekly) fails 
=> still weekly loop but daily status" ... but the concept behind sounds like a 
good approach to follow.
We should definitively move to different keywords to latest/daily/weekly. 
Silver/Gold/Platinum sounds good enough, and congratulations for those 
scenarios that get the Platinum badge from Functest because it comprises a lot 
of long tests..

The promotions are performed in a logical way and everything is calculated and 
stored in the central DB. Just some concerns come to my mind:

   - if a couple scenarios (say 3 or 4) are promoted to "Gold", it means that 
they will be running all the tests (weekly loop) in CI (unless there is a 
regression on a daily test if I understand correctly)  ==> each Funtest weekly 
run might take 3-5 hours (say 8 hours for Deploy+Functest+Yardstick) ==> CI 
needs more time to complete an entire installer loop going through all the 
scenarios. Today, in some cases, a scenario takes ~2 days to run again in CI 
(with only daily Functest tests) and some scenarios could be considered 
nowadays as "Gold".. Are we prepared to run weekly tests on so many scenarios? 
Will we be able to do this the weeks before a release?

   - This new logic is very CI-oriented. We also need to bypass it for the case 
that an end user just wants to run all the tests the same way we do now (i.e. 
functest testcase run all). So, the logic has to be implemented in another 
layer on top, not in the test project framework as such. I can imagine a layer 
between CI (Jenkins) and the test project. This layer just tells Functest what 
to execute according to the info in the DB.

Regards,
Jose


-Original Message-
From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com] 
Sent: Thursday, October 13, 2016 17:12 PM
To: test...@lists.opnfv.org
Cc: Fatih Degirmenci; opnfv-tech-discuss@lists.opnfv.org; serena feng; 
yaohelan; Jose Lausuch
Subject: CI evolution on impact on test projects

Hi,

I took the action point to describe the possible consequences of CI evolution 
on test projects.

Please find attached a pdf detailing what I tried to explain yesterday :)

I will be off next Thursday and will not be able to detail it before Barcelona 
but if you have comments/remarks

I have also the odp and yed files if you want to edit anything

@Kubi could you check Yardstick status info?

If you prefer I can put that on the wiki, but as there are many things to agree 
first (to be sure we are sharing the same view), I prefer to initiate first 
exchanges by mail to converge to a first level of stability.

/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 

Re: [opnfv-tech-discuss] Interpretation of yardstick test results

[Gaoliang (kubi)]

Hi,

Thanks all for great questions and suggestions and sorry for the delay in 
responding. Since I was in National Day vacation.

The yardstick.out file stores raw data of each test case you ran. The raw data 
consists of test details and raw test output. All result data are stored under 
“data” section.
It is not easy to understand the results in yardstick.out directly but it is 
much easier to use grafana to visualize these data to help you understand the 
results.

All CI jobs data can be found at Yardstick’s community dashboard.
If you want to analyze your local test data, you will need to build a local 
influx DB and grafana. 
https://wiki.opnfv.org/display/yardstick/How+to+deploy+InfluxDB+and+Grafana+locally
In Danube release, we plan to support automatic influx DB and grafana local 
deployment.

For details of metrics measured and relevant specifications, currently we only 
have the test case description in user guide.
In C-release, we have done some test result analysis for the passed scenarios, 
this can be find at 
http://artifacts.opnfv.org/yardstick/colorado/docs/results/index.html

For test results criteria, it is probably complex to define thresholds. A good 
news is Yardstick grafana do support threshold. If the thresholds are defined, 
it would be useful.
Once the threshold is defined, You can use it to evaluate the test results. For 
example:

Here we set two threshold levels for ping test.
[cid:image001.png@01D2217E.5356F790]

If the round trip time is smaller than 1.5ms, it may be considered as “good”. 
If the RTT is between 1.5ms to 3ms, it may be considered as “good enough”.
One thing needs to mention is although Yardstick grafana can set the threshold 
for each test case , it is up to standardization side and the whole test 
community to define these thresholds.
[cid:image002.png@01D2217E.5356F790]


For comparative tests, so far, you can compare different scenarios on the same 
pod.
We have a dedicated graph for each pod.
[cid:image003.png@01D22183.E8A7D030]

To compare test results of same scenario on different pods, you will need to 
choose the scenario and pod from the pull-down menu. Like below:
[cid:image004.png@01D22184.53F524A0]
And we are planning to improve this in Danube. One basic idea is to support 
compare different pod per scenario.

Regards.

Kubi

发件人: MORTON, ALFRED C (AL) [mailto:acmor...@att.com]
发送时间: 2016年10月8日 1:03
收件人: Cooper, Trevor; morgan.richo...@orange.com; Frank Brockners (fbrockne); 
Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco); Gaoliang (kubi); 
limingjiang
抄送: Andrej Vanko -X (avanko - PANTHEON TECHNOLOGIES at Cisco); 
opnfv-tech-discuss@lists.opnfv.org
主题: RE: [opnfv-tech-discuss] Interpretation of yardstick test results

Hi Morgan,

you wrote:
We got an update on grafana last week but it was more on the capabilities of 
the tools than on the interpretation of the results.
I think we should clearly have a discussion on this topic.
It is probably complex to define thresholds = f(pod, hardware, network 
config,..) but it would be helpful.
Is there any activity on standardization side on this area?
I think there is agreement (in some stds bodies) that the benchmarking results
we collect for NFVI and VNFs should support operator engineering and capacity 
planning
in a better way than we have done in the past (for physical NF).
In other words, truly fundamental metrics should lead to additive system models,
and VNF workload expressed in the same units could be matched with system 
capabilities.
I think Trevor’s list below is kind-of a pre-requisite for this...

It’s different from (more useful than?) setting thresholds for specific tests
that can be mapped to different platforms, and a related process in my mind.
If you can perform comparative tests (A vs B), then the relative test results
should be useful without thresholds.

One side topic that has come up recently: I don’t know if there are
“standard” definitions for processor utilization and interface metrics
(packet and byte counts) that can be expressed at various levels of physical
and virtualization, but it would certainly help the have these (std) metrics
available to support operations (and avoid calculation differences per system).

Al


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 Cooper, Trevor
Sent: Friday, October 07, 2016 10:57 AM
To: morgan.richo...@orange.com<mailto:morgan.richo...@orange.com>; Frank 
Brockners (fbrockne); Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at 
Cisco); Gaoliang (kubi); limingjiang
Cc: Andrej Vanko -X (avanko - PANTHEON TECHNOLOGIES at Cisco); 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] Interpretation of yardstick test results

I don’t think Yardstick tests are being interpreted much today, at least not as 
performance metrics. To reach a

Re: [opnfv-tech-discuss] [Yardstick] Patch to Yardstick master

[Gaoliang (kubi)]

Hi Tapio,

Thanks for your great patch. 

I already added you into Yardstick Contributors list. But I guess this is not 
the key point for this issue.

I guess you need to send email to help-desk( or Aric) to apply right  
opnfv-helpd...@rt.linuxfoundation.org

Regards,
Kubi

-邮件原件-
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Tapio Tallgren
发送时间: 2016年9月29日 21:15
收件人: opnfv technical mailing list
主题: [opnfv-tech-discuss] [Yardstick] Patch to Yardstick master

Hi all,

I seem not to have rights to send anything to the Yardstick gerrit (probably 
because I am not a contributor?),

but here is a patch to the yardstick-img-modify script. I wasted some time 
because of this, so hopefully this will help the next guy.


-Tapio



commit cc6e6f9f04b7ee6b39b091c5fee6d7d212d9c9a1
Author: Tapio Tallgren 
Date:   Thu Sep 29 15:51:45 2016 +0300

 Add default value amd64 to YARD_IMG_ARCH

 Signed-off-by: Tapio Tallgren 

diff --git a/tools/yardstick-img-modify b/tools/yardstick-img-modify
index 07f10b3..2913fc3 100755
--- a/tools/yardstick-img-modify
+++ b/tools/yardstick-img-modify
@@ -41,6 +41,8 @@ mountdir="/mnt/yardstick"
  workspace=${WORKSPACE:-"/tmp/workspace/yardstick"}
  host=${HOST:-"cloud-images.ubuntu.com"}
  release=${RELEASE:-"trusty"}
+# Set default value amd64 for YARD_IMG_ARCH
+if [ -z $YARD_IMG_ARCH ]; then YARD_IMG_ARCH="amd64"; fi
  
image_path="${release}/current/${release}-server-cloudimg-${YARD_IMG_ARCH}-disk1.img"
  image_url=${IMAGE_URL:-"https://${host}/${image_path}"}
  md5sums_path="${release}/current/MD5SUMS"

___
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

Re: [opnfv-tech-discuss] [testperf] weekly meeting APAC slot

[Gaoliang (kubi)]

hi Yujun,

Thanks for your email

this survey would help us to improve APAC slot.

Firstly, sorry for missing last APAC meeting.
I noticed that you had send email to remind us before the meeting , that 's 
great. I appreciate it.
That would be better if we can send a outlook invitaion to calendar before the 
meeting. As you said, we are not used to new meeting. I really forgot the 
meeting at that moment although I realized the APAC meeting would coming at the 
last tuesday.

My two cents

Regards
Kubi

Sent from HUAWEI AnyOffice
发件人：Yujun Zhang
收件人：test...@lists.opnfv.org,Soni, Anand Kumar via opnfv-tech-discuss,
抄送：高亮,morgan.richo...@orange.com,Beierl, Mark,Tahhan, Maryam,Daniel Farrell,田红波,
时间：2016-09-22 09:27:50
主题:[testperf] weekly meeting APAC slot

Dear Testers and PTLs,

Few people have attended the weekly testperf meeting last Wednesday[1]. Perhaps 
we are not used to the new APAC timeslot yet.

I'm not sure if people have any concerns about it. Please share your opinion so 
we can make improvement.

[1] 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-testperf/2016/opnfv-testperf.2016-09-14-08.03.log.html

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