Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources collection

[Chenjiankun (JackChan)]

Hi David,

Thanks for your response. ☺

About the build_id, it is same as Jenkins macro, but I have checked the 
environment variable, I don’t see any variable can be used. Maybe I have 
missing something? @Julien, can you give some clarification?

For the health check and fuel@x86@aarm64 issue, I think it is not had to 
implement. I will add them in another patches. We can improve this page step by 
step.

BRs,
Jack Chan

发件人: David McBride [mailto:dmcbr...@linuxfoundation.org]
发送时间: 2018年4月26日 11:53
收件人: Chenjiankun (JackChan)
抄送: TECH-DISCUSS OPNFV; tro...@redhat.com; Brattain, Ross B; Rao, Sridhar; 
OLLIVIER Cédric IMT/OLN; mark.bei...@dell.com; Yuyang (Gabriel); ALFRED C 
'MORTON ' (acmor...@att.com); emma.l.fo...@intel.com; Liyin (Ace); Wangwulin 
(Linda); georg.k...@ericsson.com; Serena Feng; Julien
主题: Re: [opnfv-tech-discuss][test-wg]Requirements for test resources collection

Hi Jack,

Sorry for the slow response.  I've been busy with the Fraser release.

Comments

  1.  I didn't understand point 1 about the build_id.  I thought that was the 
purpose of the Jenkins macro that Julien developed.  What am I missing?
  2.  I'd like to see Health Check broken out as a separate column from 
Functest.
  3.  The installer drop-down just lists "Fuel".  We need to include both 
Fuel@x86 and Fuel@aarm64.
Thanks for your effort in pushing this forward.

David


On Sun, Apr 22, 2018 at 8:49 PM, Chenjiankun (JackChan) 
<chenjiank...@huawei.com<mailto:chenjiank...@huawei.com>> wrote:
Hi David,

As discussed in the previous Email, I have create a first version of  scenario 
results table(we can call it gating reporting ☺), see:
 http://116.66.187.136:9998/index.html
Patch see:
 https://gerrit.opnfv.org/gerrit/#/c/56179/

For now, I have added four filters:

1.   Scenario

2.   Version

3.   Installer

4.   Iteration(we will query the last 10 days data, the default iteration 
is 10, if all record is more than 10, it will only 10 record)

For now, we still have some problems to solve:

1. build_id(Jenkins id), we don’t have a unified ID to mark the whole 
Jenkins jobs(deployment + functest + yardstick), for now, I use the 
build_tag(e.g. jenkins-functest-fuel-baremetal-daily-master-131, the 
project:functest and installer:fuel are in build_tag) to index, so we can only 
show the functest result.

2.   Jenkins job results, depend on build_id, we can’t show all 
results(deployment + functest + yardstick, only functest for now). And each 
projects need to upload their results(UNTRIGGERED, PASS, FAIL).

3.   Deployment results, for now, only daisy upload its deployment result, 
we need ask each installer to upload deployment results, only build_id ready, 
we can show all results.

4.   Statistic results, depend on projects upload their results

It is the first version, we will add more functions step by step after the 
above issue solved.
@All, if you have any suggestions, please let me know.

BRs,
Jack Chan

发件人: chenjiankun
发送时间: 2018年1月22日 17:02
收件人: 'David McBride'
抄送: TECH-DISCUSS OPNFV; tro...@redhat.com<mailto:tro...@redhat.com>; Brattain, 
Ross B; Rao, Sridhar; OLLIVIER Cédric IMT/OLN; 
mark.bei...@dell.com<mailto:mark.bei...@dell.com>; Yuyang (Gabriel); ALFRED C 
'MORTON ' (acmor...@att.com<mailto:acmor...@att.com>); 
emma.l.fo...@intel.com<mailto:emma.l.fo...@intel.com>; Liyin (Ace); Wangwulin 
(Linda); georg.k...@ericsson.com<mailto:georg.k...@ericsson.com>; Serena Feng; 
Julien
主题: RE: [opnfv-tech-discuss][test-wg]Requirements for test resources collection

Thanks, David.

According your descriptions, I have created a demo table as below(wish I do not 
misunderstanding your meaning):

scenario

date

Jenkins

Version

Installer

Deployment

Functest

yardstick

os-nosdn-nofeature-ha

2018-01-21

Jenkins id

euphrates

compass

pass

pass

pass


2018-01-21

Jenkins id

euphrates

compass

fail

not trigger

not trigger


statistic

8/9/10
(pass:8,triggered:9, total:10)

6/7/8

6/7/8



This last line in table body is the statistics information, and lines above are 
the detailed information(and it can be folded).
The score 8/9/10 is pass/triggered/total. Total means should run, triggered 
means actually run.
Also we can add three filters:

If you select installer as compass, then will show all data related to compass.
Iterations means last x data points to be displayed.

Does this table satisfied your requirements?

BRs,
Jack Chan
发件人: David McBride [mailto:dmcbr...@linuxfoundation.org]
发送时间: 2018年1月20日 3:07
收件人: chenjiankun
抄送: TECH-DISCUSS OPNFV; tro...@redhat.com<mailto:tro...@redhat.com>; Brattain, 
Ross B; Rao, Sridhar; OLLIVIER Cédric IMT/OLN; 
mark.bei...@dell.com<mailto:mark.bei...@dell.com>; Yuyang (Gabriel); ALFRED C 
'MORTON ' (acmor...@att.com<mailto:acmor...@att.com>); 
emma.l.fo...@intel.com<mailto:emma.l.fo...@intel.com>; Liyin (Ace); Wangwulin 
(Linda); georg.k.

Re: [opnfv-tech-discuss] [yardstick] : failed to "yardstick task start samples/ping.yaml"

[Chenjiankun (JackChan)]

Hi Ameed,

Can you try to add OS_PROJECT_DOMAIN_NAME in your openrc?
In my environment, OS_PROJECT_DOMAIN_NAME=Default works for me.

BRs,
Jack Chan

发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Ameed Ashour
发送时间: 2018年5月2日 15:25
收件人: opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] [yardstick] : failed to "yardstick task start 
samples/ping.yaml"


Hi



I'm now facing issue in running yardstick test case.



When I run a sample test, 'yardstick task start samples/ping.yaml',

following error is occurring continuously.



BadRequest: Expecting to find domain in project. The server could not comply 
with the request since it is either malformed or otherwise incorrect. The 
client is assumed to be in error. (HTTP 400) (Request-ID: 
req-6ac7c240-f8a0-46bc-826e-df274ca4d63c)



I'm using Ubuntu 16.04 and used openstack and yardstick installed directly.



Is this error already  known issue?



I would very appreciate if somebody help me..



PS: I was run test on older version of openstack , it's work!

Best Regards,

Ameed

___
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]Requirements for test resources collection

[Chenjiankun (JackChan)]

Hi David,

As discussed in the previous Email, I have create a first version of  scenario 
results table(we can call it gating reporting ☺), see:
 http://116.66.187.136:9998/index.html
Patch see:
 https://gerrit.opnfv.org/gerrit/#/c/56179/

For now, I have added four filters:

1.   Scenario

2.   Version

3.   Installer

4.   Iteration(we will query the last 10 days data, the default iteration 
is 10, if all record is more than 10, it will only 10 record)

For now, we still have some problems to solve:

1. build_id(Jenkins id), we don’t have a unified ID to mark the whole 
Jenkins jobs(deployment + functest + yardstick), for now, I use the 
build_tag(e.g. jenkins-functest-fuel-baremetal-daily-master-131, the 
project:functest and installer:fuel are in build_tag) to index, so we can only 
show the functest result.

2.   Jenkins job results, depend on build_id, we can’t show all 
results(deployment + functest + yardstick, only functest for now). And each 
projects need to upload their results(UNTRIGGERED, PASS, FAIL).

3.   Deployment results, for now, only daisy upload its deployment result, 
we need ask each installer to upload deployment results, only build_id ready, 
we can show all results.

4.   Statistic results, depend on projects upload their results

It is the first version, we will add more functions step by step after the 
above issue solved.
@All, if you have any suggestions, please let me know.

BRs,
Jack Chan

发件人: chenjiankun
发送时间: 2018年1月22日 17:02
收件人: 'David McBride'
抄送: TECH-DISCUSS OPNFV; tro...@redhat.com; Brattain, Ross B; Rao, Sridhar; 
OLLIVIER Cédric IMT/OLN; mark.bei...@dell.com; Yuyang (Gabriel); ALFRED C 
'MORTON ' (acmor...@att.com); emma.l.fo...@intel.com; Liyin (Ace); Wangwulin 
(Linda); georg.k...@ericsson.com; Serena Feng; Julien
主题: RE: [opnfv-tech-discuss][test-wg]Requirements for test resources collection

Thanks, David.

According your descriptions, I have created a demo table as below(wish I do not 
misunderstanding your meaning):

scenario

date

Jenkins

Version

Installer

Deployment

Functest

yardstick

os-nosdn-nofeature-ha

2018-01-21

Jenkins id

euphrates

compass

pass

pass

pass


2018-01-21

Jenkins id

euphrates

compass

fail

not trigger

not trigger


statistic

8/9/10
(pass:8,triggered:9, total:10)

6/7/8

6/7/8



This last line in table body is the statistics information, and lines above are 
the detailed information(and it can be folded).
The score 8/9/10 is pass/triggered/total. Total means should run, triggered 
means actually run.
Also we can add three filters:

If you select installer as compass, then will show all data related to compass.
Iterations means last x data points to be displayed.

Does this table satisfied your requirements?

BRs,
Jack Chan
发件人: David McBride [mailto:dmcbr...@linuxfoundation.org]
发送时间: 2018年1月20日 3:07
收件人: chenjiankun
抄送: TECH-DISCUSS OPNFV; tro...@redhat.com<mailto:tro...@redhat.com>; Brattain, 
Ross B; Rao, Sridhar; OLLIVIER Cédric IMT/OLN; 
mark.bei...@dell.com<mailto:mark.bei...@dell.com>; Yuyang (Gabriel); ALFRED C 
'MORTON ' (acmor...@att.com<mailto:acmor...@att.com>); 
emma.l.fo...@intel.com<mailto:emma.l.fo...@intel.com>; Liyin (Ace); Wangwulin 
(Linda); georg.k...@ericsson.com<mailto:georg.k...@ericsson.com>; Serena Feng; 
Julien
主题: Re: [opnfv-tech-discuss][test-wg]Requirements for test resources collection

+Serena, Julien

Thanks, Jack.

  1.  Data reported per scenario (i.e., jenkins job, deployment, functest, 
yardstick, etc. displayed together for each scenario) instead of separate test 
silos.
  2.  Include deployment results
  3.  Include all Jenkins job results (failure to start, failure to complete, 
etc.)
  4.  Clear date/time stamps for every data point
  5.  Display the data above for the last x data points (e.g., 4, 5, 10 ?)
  6.  Use an easy-to-understand, unified scoring method for all test frameworks.
As I mentioned, yesterday, Julien and Serena have been working on this, as 
well.  Julien has developed a macro<https://gerrit.opnfv.org/gerrit/#/c/48515/> 
to enable consolidation of all results per scenario. He is intending to use the 
Daisy installer as a platform to verify the macro, which then can be adapted to 
other installers.

In addition, Serena has agreed to help manage an intern who can assist with the 
project.  I have an action to create an intern proposal for that purpose.

David

On Fri, Jan 19, 2018 at 1:23 AM, chenjiankun 
<chenjiank...@huawei.com<mailto:chenjiank...@huawei.com>> wrote:
Hi,

As we discussed last test working group weekly meeting, we want to do test 
resources aggregation.
We plan to offer a new friendly web portal which contain all existing test 
resource and more functions.

I have a broad classification as bellow:

1.   Data analysis

a) Reporting(existing, For release)

b) Bitergia(existing)

c) Grafana(existing, For detailed test r

Re: [opnfv-tech-discuss] yardstick

[Chenjiankun (JackChan)]

Hi,

It seems you install yardstick without docker, right? (Install yardstick using 
docker will have this issue. )
If you install yardstick only once, you can:
 vim yardstick/common/constants.py
 change API_PORT to another port.
 uwsgi –I /etc/yardstick/yardstick.ini (restart API service)

Or I can summit a patch to make it configurable.

BRs,
Jack Chan

发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Rawzan Masood
发送时间: 2018年4月4日 15:04
收件人: opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] yardstick

We are trying to install StorPerf plugin to the yardstick environment  for 
storage testing , the storperf swagger uses port 5000  which is the default for 
storperf plugin . In the same time we are using Yardstick REST APIs which use 
the same port too (5000)
We tried to install storPerf plugin as docker on another port , but it didn't 
work
so , how we can install it on a specific port without facing conflicts which 
the REST APIs.
___
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] Reporting Fraser Release Adaption

[Chenjiankun (JackChan)]

Hi,

 I have updated the reporting page for Fraser on the server. See:
   http://testresults.opnfv.org/reporting/index.html
 (Functest, Yardstick, Qtip is ready now, Storperf and Vsperf seems not 
follow the OPNFV Release)
 (Also the Fraser Icon need to be updated)

 I also have upload a patch, see:
   https://gerrit.opnfv.org/gerrit/#/c/54881/

 For now, there is no data in the database, so the pages are still 
empty page. Once we upload test results, each pages will show the result.


BRs,
Jack Chan
___
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]

[Chenjiankun (JackChan)]

Hi

If you install without docker, the port should be 5000.

BRs,
Jack Chan

发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Ameed Ashour
发送时间: 2018年3月12日 20:28
收件人: opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] [yardstick]

Hi

I have a question regarding yardstick rest API. as you see in this example the 
port of yardstick is  since its a docker, but when we try to install it 
without docker, we can't send any request to it.

http://localhost:/yardstick/testcases

so, should I install yardstick on docker?
if no, how can I change the listening port?

Best Regards
Ameed
___
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]

[Chenjiankun (JackChan)]

Hi Ameed,

I am sorry I don’t get your requirement clearly. What the “protect that with 
credentials” mean?
Can you give a example to illustrate your requirement in detail?

BRs,
Jack Chan
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Ameed Ashour
发送时间: 2018年2月28日 20:30
收件人: opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] [yardstick]

Hi

I have a question about Yardstick REST API,

if I call YardStick functionality through API, how can I protect that with 
credentials?

in case I put yardstick on a public server.

Best Regards
Ameed

___
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]Requirements for test resources collection

[chenjiankun]

Hi Julien,

Sorry for missing the email you have cc to me and the meeting.

Can you update the relevant information here then?

Thanks in advance. ☺

BRs,
Jack Chan

发件人: Julien [mailto:julien...@gmail.com]
发送时间: 2018年1月27日 23:42
收件人: David McBride
抄送: chenjiankun; SerenaFeng(zte); Serena Feng; TECH-DISCUSS OPNFV
主题: Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources collection

Hi Jack,

I have finished the macro, but it failed for a Jenkins plugin is missing. I cc 
the issue email to you, which will be discussed in the infra meeting.

BR/Julien

David McBride 
<dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>>于2018年1月27日周六
 上午12:13写道：
+Julien

Jack,

I like the table format and the filtering options that you proposed.  Also +1 
to Serena's suggestion to break out the health check data.

I think that Julien is working on a Jenkins macro to enable the test API to 
retrieve the "jenkins id".  Julien - please confirm.

David

On Tue, Jan 23, 2018 at 10:53 PM, chenjiankun 
<chenjiank...@huawei.com<mailto:chenjiank...@huawei.com>> wrote:
Hi Serena,

Thanks for your information updating.
I am so glad to see TestAPI is ready to collecting deployment results, and it 
would be much more convenient.
One question: does all installer will push result to DB, or just Daisy for now?

For the Jenkins id, it means a combination of deployment + functest + yardstick 
job. I am not sure if there are a ‘jenkins_id’ for now. This field is for 
identify the combination jobs.
For the second comment, maybe there are some misunderstanding, as David’s 
requirements, we will show data last x iterations(not days), so I think there 
will be no such problems.
For the healthcheck column, I totally agree with you. But maybe it will depend 
on functest to upload test result independently.

What’s your opinions? @David, @Serena

BRs,
Jack Chan

发件人: SerenaFeng(zte) 
[mailto:serena.feng.711+...@gmail.com<mailto:serena.feng.711%2b...@gmail.com>]
发送时间: 2018年1月22日 18:08
收件人: chenjiankun
抄送: David McBride; Serena Feng; TECH-DISCUSS OPNFV
主题: Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources collection

Hi David & Jack,

Thanks for mentioning the task, an interface for collecting deployment results 
has been ready in TestAPI[1],
the Macro for pushing deployment result is also ready by Jelien[2], I believe 
it will facilitate all the installers' work,
currently, Julien is working on pushing daisy results to TestAPI leveraging 
that Macro, I think it will be finished soon.

And regarding how to show all the information in a table, I suggest we can take 
a look at Jack's proposal first.

@Jack, a few comments:
1. what's the opinion of jenkins id?
2. for a scenario-installer combination, some will not run once in a 
day(trigger multiple times or run in multiple pods),
in this case, a simple pass/fail will be too vague, and to facilitate the 
support of data iteration, I would suggest
leveraging 8/9/10(8 passed, 9 triggered, 10total), delete the final 
statistic line
3. how about adding a healthcheck column(functest-healthcheck test cases), to 
see if the installer meets the milestone 3.0


[1]: https://gerrit.opnfv.org/gerrit/#/c/49895/
[2]: https://gerrit.opnfv.org/gerrit/#/c/48515/

BRs
Serena

On Mon, Jan 22, 2018 at 5:02 PM chenjiankun 
<chenjiank...@huawei.com<mailto:chenjiank...@huawei.com>> wrote:
Thanks, David.

According your descriptions, I have created a demo table as below(wish I do not 
misunderstanding your meaning):

scenario

date

Jenkins

Version

Installer

Deployment

Functest

yardstick

os-nosdn-nofeature-ha

2018-01-21

Jenkins id

euphrates

compass

pass

pass

pass


2018-01-21

Jenkins id

euphrates

compass

fail

not trigger

not trigger


statistic

8/9/10
(pass:8,triggered:9, total:10)

6/7/8

6/7/8



This last line in table body is the statistics information, and lines above are 
the detailed information(and it can be folded).
The score 8/9/10 is pass/triggered/total. Total means should run, triggered 
means actually run.
Also we can add three filters:

If you select installer as compass, then will show all data related to compass.
Iterations means last x data points to be displayed.

Does this table satisfied your requirements?

BRs,
Jack Chan
发件人: David McBride 
[mailto:dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>]
发送时间: 2018年1月20日 3:07
收件人: chenjiankun
抄送: TECH-DISCUSS OPNFV; tro...@redhat.com<mailto:tro...@redhat.com>; Brattain, 
Ross B; Rao, Sridhar; OLLIVIER Cédric IMT/OLN; 
mark.bei...@dell.com<mailto:mark.bei...@dell.com>; Yuyang (Gabriel); ALFRED C 
'MORTON ' (acmor...@att.com<mailto:acmor...@att.com>); 
emma.l.fo...@intel.com<mailto:emma.l.fo...@intel.com>; Liyin (Ace); Wangwulin 
(Linda); georg.k...@ericsson.com<mailto:georg.k...@ericsson.com>; Serena Feng; 
Julien
主题: Re: [opnfv-tech-discuss][test-wg]Requirements for test resources col

Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources collection

[chenjiankun]

Hi Serena,

For the Jenkins id, as Fatih and Trevor clarification, we can’t use build_id to 
implement. So maybe we can discuss with them in detail and try to add a new 
variable in Jenkins. As for the name, Fatih and Trevor maybe are  familiar with 
the Jenkins, so maybe they can offer a more accuracy name after we clarify our 
requirements.
As for the status, both are OK to me. Since I get this requirements from David, 
in the previous email he said “Display the data above for the last x data 
points (e.g., 4, 5, 10 ?) “, and I add a statistic line to show more 
information. So for this issue, maybe it’s better to leave it to David to 
clarify what information he want to display here.
@David, can you give us some clarification about what information you want to 
see here?
For the health check, Linda told me that maybe later Functest will upload 
health check status independently. If so, it would be easy to get health result 
then. For now we can combine the connection_check/api_check/_snaps_health_check 
result to get a total status.

BRs,
Jack Chan

发件人: SerenaFeng(zte) [mailto:serena.feng.711+...@gmail.com]
发送时间: 2018年1月29日 14:40
收件人: Julien
抄送: David McBride; chenjiankun; Serena Feng; TECH-DISCUSS OPNFV
主题: Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources collection

Hi Jack

Eventually, we hope all the installers push their deployment results to 
TestAPI, in the current stage, we just leverage Daisy to have a try and find a 
common framework to achieve that, we will promote it to other installers soon 
after it works.

In terms of Jenkins id, almost all the installers leverage muti-job to manage 
deployment and drive test projects. there is an entry job to control all the 
jobs, such as 
daisy-os-nosdn-nofeature-ha-baremetal-daily-master<https://build.opnfv.org/ci/job/daisy-os-nosdn-nofeature-ha-baremetal-daily-master/>,
 maybe we can leverage the combination of the Jenkins job and build_id 
daisy-os-nosdn-nofeature-ha-baremetal-daily-master_185<https://build.opnfv.org/ci/job/daisy-os-nosdn-nofeature-ha-baremetal-daily-master/185/>(or
 jest the Jenkins job) to link to the Jenkins. As for naming, instead of 
'Jenkins' I would recommend using 'Job_name', because, in zuulv3, Jenkins will 
be discarded, but the job idea will be left(maybe in some other way)

For the status show, if only show the last and latest one iteration, simple 
pass/fail is fine, or else multi-results will be included, I don't recommend 
that. Personally, my suggestion is either integrate last one iteration into 
last x iterations, all use statistics to show the results, or separate into two 
pages: the current status(simple pass/fail) and the history statistic 
status(8/9/10).

For Functest health check, Sure, Functest reports per execution result per test 
case separately, we can get them from TestAPI, there's no problem with that. 
But for health check actually includes 3 test 
cases(connection_check/api_check/snaps_health_check), we need to cope with that 
carefully.


BRs
Serena

On Sat, Jan 27, 2018 at 11:42 PM Julien 
<julien...@gmail.com<mailto:julien...@gmail.com>> wrote:
Hi Jack,

I have finished the macro, but it failed for a Jenkins plugin is missing. I cc 
the issue email to you, which will be discussed in the infra meeting.

BR/Julien

David McBride 
<dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>>于2018年1月27日周六
 上午12:13写道：
+Julien

Jack,

I like the table format and the filtering options that you proposed.  Also +1 
to Serena's suggestion to break out the health check data.

I think that Julien is working on a Jenkins macro to enable the test API to 
retrieve the "jenkins id".  Julien - please confirm.

David

On Tue, Jan 23, 2018 at 10:53 PM, chenjiankun 
<chenjiank...@huawei.com<mailto:chenjiank...@huawei.com>> wrote:
Hi Serena,

Thanks for your information updating.
I am so glad to see TestAPI is ready to collecting deployment results, and it 
would be much more convenient.
One question: does all installer will push result to DB, or just Daisy for now?

For the Jenkins id, it means a combination of deployment + functest + yardstick 
job. I am not sure if there are a ‘jenkins_id’ for now. This field is for 
identify the combination jobs.
For the second comment, maybe there are some misunderstanding, as David’s 
requirements, we will show data last x iterations(not days), so I think there 
will be no such problems.
For the healthcheck column, I totally agree with you. But maybe it will depend 
on functest to upload test result independently.

What’s your opinions? @David, @Serena

BRs,
Jack Chan

发件人: SerenaFeng(zte) 
[mailto:serena.feng.711+...@gmail.com<mailto:serena.feng.711%2b...@gmail.com>]
发送时间: 2018年1月22日 18:08
收件人: chenjiankun
抄送: David McBride; Serena Feng; TECH-DISCUSS OPNFV
主题: Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources collection

Hi David & Jack,

Thanks for mentioning the 

Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources collection

[chenjiankun]

Hi Serena,

Thanks for your information updating.
I am so glad to see TestAPI is ready to collecting deployment results, and it 
would be much more convenient.
One question: does all installer will push result to DB, or just Daisy for now?

For the Jenkins id, it means a combination of deployment + functest + yardstick 
job. I am not sure if there are a ‘jenkins_id’ for now. This field is for 
identify the combination jobs.
For the second comment, maybe there are some misunderstanding, as David’s 
requirements, we will show data last x iterations(not days), so I think there 
will be no such problems.
For the healthcheck column, I totally agree with you. But maybe it will depend 
on functest to upload test result independently.

What’s your opinions? @David, @Serena

BRs,
Jack Chan

发件人: SerenaFeng(zte) [mailto:serena.feng.711+...@gmail.com]
发送时间: 2018年1月22日 18:08
收件人: chenjiankun
抄送: David McBride; Serena Feng; TECH-DISCUSS OPNFV
主题: Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources collection

Hi David & Jack,

Thanks for mentioning the task, an interface for collecting deployment results 
has been ready in TestAPI[1],
the Macro for pushing deployment result is also ready by Jelien[2], I believe 
it will facilitate all the installers' work,
currently, Julien is working on pushing daisy results to TestAPI leveraging 
that Macro, I think it will be finished soon.

And regarding how to show all the information in a table, I suggest we can take 
a look at Jack's proposal first.

@Jack, a few comments:
1. what's the opinion of jenkins id?
2. for a scenario-installer combination, some will not run once in a 
day(trigger multiple times or run in multiple pods),
in this case, a simple pass/fail will be too vague, and to facilitate the 
support of data iteration, I would suggest
leveraging 8/9/10(8 passed, 9 triggered, 10total), delete the final 
statistic line
3. how about adding a healthcheck column(functest-healthcheck test cases), to 
see if the installer meets the milestone 3.0


[1]: https://gerrit.opnfv.org/gerrit/#/c/49895/
[2]: https://gerrit.opnfv.org/gerrit/#/c/48515/

BRs
Serena

On Mon, Jan 22, 2018 at 5:02 PM chenjiankun 
<chenjiank...@huawei.com<mailto:chenjiank...@huawei.com>> wrote:
Thanks, David.

According your descriptions, I have created a demo table as below(wish I do not 
misunderstanding your meaning):

scenario

date

Jenkins

Version

Installer

Deployment

Functest

yardstick

os-nosdn-nofeature-ha

2018-01-21

Jenkins id

euphrates

compass

pass

pass

pass


2018-01-21

Jenkins id

euphrates

compass

fail

not trigger

not trigger


statistic

8/9/10
(pass:8,triggered:9, total:10)

6/7/8

6/7/8



This last line in table body is the statistics information, and lines above are 
the detailed information(and it can be folded).
The score 8/9/10 is pass/triggered/total. Total means should run, triggered 
means actually run.
Also we can add three filters:
 [cid:image003.png@01D393A2.AC65E3E0]
If you select installer as compass, then will show all data related to compass.
Iterations means last x data points to be displayed.

Does this table satisfied your requirements?

BRs,
Jack Chan
发件人: David McBride 
[mailto:dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>]
发送时间: 2018年1月20日 3:07
收件人: chenjiankun
抄送: TECH-DISCUSS OPNFV; tro...@redhat.com<mailto:tro...@redhat.com>; Brattain, 
Ross B; Rao, Sridhar; OLLIVIER Cédric IMT/OLN; 
mark.bei...@dell.com<mailto:mark.bei...@dell.com>; Yuyang (Gabriel); ALFRED C 
'MORTON ' (acmor...@att.com<mailto:acmor...@att.com>); 
emma.l.fo...@intel.com<mailto:emma.l.fo...@intel.com>; Liyin (Ace); Wangwulin 
(Linda); georg.k...@ericsson.com<mailto:georg.k...@ericsson.com>; Serena Feng; 
Julien
主题: Re: [opnfv-tech-discuss][test-wg]Requirements for test resources collection

+Serena, Julien

Thanks, Jack.

  1.  Data reported per scenario (i.e., jenkins job, deployment, functest, 
yardstick, etc. displayed together for each scenario) instead of separate test 
silos.
  2.  Include deployment results
  3.  Include all Jenkins job results (failure to start, failure to complete, 
etc.)
  4.  Clear date/time stamps for every data point
  5.  Display the data above for the last x data points (e.g., 4, 5, 10 ?)
  6.  Use an easy-to-understand, unified scoring method for all test frameworks.
As I mentioned, yesterday, Julien and Serena have been working on this, as 
well.  Julien has developed a macro<https://gerrit.opnfv.org/gerrit/#/c/48515/> 
to enable consolidation of all results per scenario. He is intending to use the 
Daisy installer as a platform to verify the macro, which then can be adapted to 
other installers.

In addition, Serena has agreed to help manage an intern who can assist with the 
project.  I have an action to create an intern proposal for that purpose.

David

On Fri, Jan 19, 2018 at 1:23 AM, chenjiankun 
<chenjiank...@huawei.com<mailto

Re: [opnfv-tech-discuss] [test-wg]Requirements for test resources collection

[chenjiankun]

Thanks, David.

According your descriptions, I have created a demo table as below(wish I do not 
misunderstanding your meaning):

scenario

date

Jenkins

Version

Installer

Deployment

Functest

yardstick

os-nosdn-nofeature-ha

2018-01-21

Jenkins id

euphrates

compass

pass

pass

pass


2018-01-21

Jenkins id

euphrates

compass

fail

not trigger

not trigger


statistic

8/9/10
(pass:8,triggered:9, total:10)

6/7/8

6/7/8



This last line in table body is the statistics information, and lines above are 
the detailed information(and it can be folded).
The score 8/9/10 is pass/triggered/total. Total means should run, triggered 
means actually run.
Also we can add three filters:
 [cid:image003.png@01D393A2.AC65E3E0]
If you select installer as compass, then will show all data related to compass.
Iterations means last x data points to be displayed.

Does this table satisfied your requirements?

BRs,
Jack Chan
发件人: David McBride [mailto:dmcbr...@linuxfoundation.org]
发送时间: 2018年1月20日 3:07
收件人: chenjiankun
抄送: TECH-DISCUSS OPNFV; tro...@redhat.com; Brattain, Ross B; Rao, Sridhar; 
OLLIVIER Cédric IMT/OLN; mark.bei...@dell.com; Yuyang (Gabriel); ALFRED C 
'MORTON ' (acmor...@att.com); emma.l.fo...@intel.com; Liyin (Ace); Wangwulin 
(Linda); georg.k...@ericsson.com; Serena Feng; Julien
主题: Re: [opnfv-tech-discuss][test-wg]Requirements for test resources collection

+Serena, Julien

Thanks, Jack.

  1.  Data reported per scenario (i.e., jenkins job, deployment, functest, 
yardstick, etc. displayed together for each scenario) instead of separate test 
silos.
  2.  Include deployment results
  3.  Include all Jenkins job results (failure to start, failure to complete, 
etc.)
  4.  Clear date/time stamps for every data point
  5.  Display the data above for the last x data points (e.g., 4, 5, 10 ?)
  6.  Use an easy-to-understand, unified scoring method for all test frameworks.
As I mentioned, yesterday, Julien and Serena have been working on this, as 
well.  Julien has developed a macro<https://gerrit.opnfv.org/gerrit/#/c/48515/> 
to enable consolidation of all results per scenario. He is intending to use the 
Daisy installer as a platform to verify the macro, which then can be adapted to 
other installers.

In addition, Serena has agreed to help manage an intern who can assist with the 
project.  I have an action to create an intern proposal for that purpose.

David

On Fri, Jan 19, 2018 at 1:23 AM, chenjiankun 
<chenjiank...@huawei.com<mailto:chenjiank...@huawei.com>> wrote:
Hi,

As we discussed last test working group weekly meeting, we want to do test 
resources aggregation.
We plan to offer a new friendly web portal which contain all existing test 
resource and more functions.

I have a broad classification as bellow:

1.   Data analysis

a) Reporting(existing, For release)

b) Bitergia(existing)

c) Grafana(existing, For detailed test results)

d) ……(maybe we can develop more tools to show our detailed test results)

2.   Test working group information(What information you want to see from 
test working group? Test working group event? Event of each project?)

3.   Tools of each project(Need each project member to complete)

4.   ……(waiting for you to improve)


This email is aim at collecting requirements for test resources, so if you have 
any idea about classification, existing tools(such as reporting), new functions 
you want, please do not hesitate to comment here.
As Gabriel said, he will create a new wiki page for test resources collection, 
so you can also comment there.

@David, @Tim, can you repeat your advice about reporting here? I will try my 
best to implement it.
@All, all requirements, advice, comment are welcome~☺

BRs,
Jack Chan



--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018<tel:%2B1.805.276.8018>
Email/Google Talk: 
dmcbr...@linuxfoundation.org<mailto: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

[opnfv-tech-discuss] [test-wg]Requirements for test resources collection

[chenjiankun]

Hi,

As we discussed last test working group weekly meeting, we want to do test 
resources aggregation.
We plan to offer a new friendly web portal which contain all existing test 
resource and more functions.

I have a broad classification as bellow:

1.   Data analysis

a) Reporting(existing, For release)

b) Bitergia(existing)

c) Grafana(existing, For detailed test results)

d) ..(maybe we can develop more tools to show our detailed test 
results)

2.   Test working group information(What information you want to see from 
test working group? Test working group event? Event of each project?)

3.   Tools of each project(Need each project member to complete)

4.   ..(waiting for you to improve)


This email is aim at collecting requirements for test resources, so if you have 
any idea about classification, existing tools(such as reporting), new functions 
you want, please do not hesitate to comment here.
As Gabriel said, he will create a new wiki page for test resources collection, 
so you can also comment there.

@David, @Tim, can you repeat your advice about reporting here? I will try my 
best to implement it.
@All, all requirements, advice, comment are welcome~:)

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

Re: [opnfv-tech-discuss] VSPERF Results Dashboard Issue.

[chenjiankun]

Hi All,

I have upload a patch for Vsperf new reporting page.
See:
 https://gerrit.opnfv.org/gerrit/#/c/47221/
I also have updated it in testresults.opnfv.org, see:
 http://testresults.opnfv.org/reporting/euphrates/vsperf/reporting.html

@David, do you have any comment on it?
@All, if you have any suggestions, do not hesitate to comment(Patch or Email, 
both OK☺)

BR,
Jack Chan

发件人: Rao, Sridhar [mailto:sridhar@spirent.com]
发送时间: 2017年11月10日 14:43
收件人: chenjiankun
抄送: Cooper, Trevor <trevor.coo...@intel.com> (trevor.coo...@intel.com); Mars 
Toktonaliev (Nokia - US/Irving); Martin Klozik (martinx.klo...@intel.com); 
ALFRED C 'MORTON ' (acmor...@att.com)
主题: RE: VSPERF Results Dashboard Issue.

Hello All,

Summarizing the discussion, we had today (Thanks to Martin and Jack).


  1.  The primary key will be the case_name field in the VSPERF result. For the 
sake of completeness, I have attached pictures highlighting what ‘primary-key’ 
is and sample vsperf result.
  2.  Build-tag has the version information and it was agreed that it results 
can be obtained and categorized using this field.
  3.  Jack will check the ‘source code’ to decide on Installer-wise display. 
He’ll propose one of the following options (a) Display same results for all 
installer (b) Display only ‘fuel’ as installer option and show the results (b) 
Add baremetal as one of the options in installer and show results under that.
  4.  It would be ideal – consider the low-frequency of testruns for VSPERF – 
to display last 10-results instead of last-10days’ results. Jack will consider 
this, going ahead – though it is not a high priority.

Thanks again,

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

From: chenjiankun [mailto:chenjiank...@huawei.com]
Sent: Thursday, November 09, 2017 7:14 AM
To: Rao, Sridhar <sridhar@spirent.com<mailto:sridhar@spirent.com>>
Cc: Cooper, Trevor <trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>> 
(trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>) 
<trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>>; Mars Toktonaliev 
(Nokia - US/Irving) 
<mars.toktonal...@nokia.com<mailto:mars.toktonal...@nokia.com>>; Martin Klozik 
(martinx.klo...@intel.com<mailto:martinx.klo...@intel.com>) 
<martinx.klo...@intel.com<mailto:martinx.klo...@intel.com>>; ALFRED C 'MORTON ' 
(acmor...@att.com<mailto:acmor...@att.com>) 
<acmor...@att.com<mailto:acmor...@att.com>>
Subject: RE: VSPERF Results Dashboard Issue.

Hi  Sridhar,

From my perspective, it’s easy to fix. But the question is what information we 
want to show.
Or in another way of saying this, which field we want to choose as the primary 
key.

In functest or yardstick, we choose scenario as primary key, but since Vsperf 
do not have OPNFV scenario/version, so we can’t follow it.
I have checked the Vsperf data in DB, maybe we can choose case_name as primary 
key.

BTW, since when we open this page, we first choose version, then installer, but 
for Vsperf, we do not follow the OPNFV version, installer.
So we must find a way to follow the workflow.

BR,
Jack Chan

发件人: Rao, Sridhar [mailto:sridhar@spirent.com]
发送时间: 2017年11月8日 16:24
收件人: chenjiankun
抄送: Cooper, Trevor <trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>> 
(trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>); Mars Toktonaliev 
(Nokia - US/Irving); Martin Klozik 
(martinx.klo...@intel.com<mailto:martinx.klo...@intel.com>); ALFRED C 'MORTON ' 
(acmor...@att.com<mailto:acmor...@att.com>)
主题: VSPERF Results Dashboard Issue.

Hello Jack Chan,
As discussed during today’s Testperf call, this link still throws 404 error.
http://testresults.opnfv.org/reporting/danube/vsperf/status-apex.html

However, VSPERF is publishing the results. This link returns last 10 results 
(last being on 22nd October).
http://testresults.opnfv.org/test/api/v1/results?project=vsperf=10

Can you suggest how do we fix this issue? VSPERF team will definitely help in 
any possibly way to get this fixed.

If you prefer a discussion on this, maybe, I can setup one – I guess VSPERF 
weekly call may not be the Ideal time for you.

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


Spirent Communications e-mail confidentiality.

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

Spirent Communications plc
Northwood Park, Gatwick Road, Crawley

[opnfv-tech-discuss] [test-wg]Reporting requirements

[chenjiankun]

Hi David,

As discussed last night, we all agree that adding timestamps in reporting page.
So in order to clarify your need better, can you repeat your demand?
Once we come to a conclusion, I will try to do it ASAP.

BTW, since you are a very important user to reporting page, your suggestion 
means a lot to us.
If you have any confusion/suggestion about it, please do not hesitate to tell 
us.


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

Re: [opnfv-tech-discuss] [release][euphrates] Euphrates status

[chenjiankun]

Hi, Alex,

Sorry for causing trouble, since the criteria field in DB has been changed 
yesterday , so the result is not accurate.
And I have done a quick fix in testresults.opnfv.org, see:
 
http://testresults.opnfv.org/reporting/euphrates/yardstick/status-f...@x86.html

For the history data, we still need more days to see the trend.

BR,
Jack Chan

发件人: Alexandru Avadanii [mailto:alexandru.avada...@enea.com]
发送时间: 2017年10月13日 3:42
收件人: David McBride; chenjiankun
抄送: opnfv-project-leads; TSC OPNFV; TECH-DISCUSS OPNFV; Michail Polenchuk
主题: RE: [opnfv-tech-discuss] [release][euphrates] Euphrates status

Hi, David,
Michael is currently on vacation.
The results were looking good yesterday, but meanwhile the history seems to 
have been cleared, probably by a recent change in the script.
I will try to identify the rootcause and ping the proper audience.

BR,
Alex


From: David McBride [mailto:dmcbr...@linuxfoundation.org]
Sent: Thursday, October 12, 2017 7:01 PM
To: chenjiankun
Cc: opnfv-project-leads; TSC OPNFV; TECH-DISCUSS OPNFV; Alexandru Avadanii; 
Michail Polenchuk
Subject: Re: [opnfv-tech-discuss] [release][euphrates] Euphrates status

+Michail

Thanks, Jack.

I see the test results pages, but no results.  When do you think that we'll see 
results populating the pages?

Also, the deploy results for fuel@x86 do not look very good:

os-nosdn-nofeature-noha

Fuel/MCP

Michael Polenchuk

link<https://url10.mailanyone.net/v1/?m=1e2fw2-0002hR-47=57e1b682=qoM4u3Nklz6CopZyL4WNlD0atBXabbInclTGDbhnGpTolUJCO45XEhuFgb0tIpEiFd4tfX6rHC0f4GZ5d2TAQfZAfYWppyV6c6UPpMOELctJOG6YsSxzWx5a-Rf2N5V5N2HRvTBOJfTb2AOXPr3Huq_uzjmKvXLyZzxLAAgKozGhkhYm0C0cB9xYnM5Rtf4DhV_tlrn2pAdt3_f-M0xBC2jb3VHhf7_8oxPNUEjI5dx5EdAWPUNSvshhauRddLf0P4ajoGVHX2WWk9FZRQWB2Hq6qNTT1G25RT6a62p50RMDC3mbpV0jVhteeYCOkrcT>

not running

os-nosdn-nofeature-ha

Fuel/MCP

Michael Polenchuk

link<https://url10.mailanyone.net/v1/?m=1e2fw2-0002hR-47=57e1b682=_pHw3RCs9YJCmuMBdmSY6AxAxj82FK1p-5kWohZASMKXjKBpk5AqKXZ5ggxFQnB0czm5ref7xnWs8ziuHTM9p3wxGT0LYzE-4Wy7EOE6OiX-pRCIPAUX_cGSDJfvb_HsbcWJmJrmCAzAjsWSkkWQmrNRsfnOFLtP4O5_HdaEMNFHbf6XU0Ava8fuSktRgXnsqHxxgjC7-Zo_1pP9221PBDzGNu0Q9DZ_wbv13BirIPTbIZnd83zdgLJJmtVMU3gUO5KXlg2mB4Y7TsseTSXDlpnlobMAjUbUu_WH93r4aQ0>

fail

os-nosdn-ovs-noha

Fuel/MCP

Michael Polenchuk

link<https://url10.mailanyone.net/v1/?m=1e2fw2-0002hR-47=57e1b682=0ppagEQFQ3-X1YTGUEkQgwc1CtFBEKjlNjZBu_mXCAj8sbp30rhmS6dqCa8RxJgg-GTnvpDdD59HoKz3d8mJl_9qzPB6gp5XOeufRACdvDNfXfJHuTSwS6koNKR-KeYF2TpksAElbVsBJdKTYQMUGvjCJPwEYciKQRinqNeIi6ixm9U3w-RUnJ40f2W4kqgA280khD-js5gQPXDS9XyI1hFJzLhjF-KnSX8eUmtNHgTYtaIbvRhwzZ7Fhqh7uRIDXAuMVUBo7jCrQsBDZ26hO0ldpvivhAuSQ9OmHRTP22Y>

not running

os-nosdn-ovs-ha

Fuel/MCP

Michael Polenchuk

link<https://url10.mailanyone.net/v1/?m=1e2fw2-0002hR-47=57e1b682=Nvdjoh_7CuVh_ClB1vgASPngOTcaMWUnyQVtiJOF9HSJnezKzAiD2WRGhaSvmcHj3W-rS_Qbz4O6boPnxbEbK4c-SsqVOSY9A6SyFx0mLCCHSVNvUka0B18xYIuDiQWqehkpEMAkDSLKiBthkFb-opjZA4aDWHbKYGx1VjEreMfbP7mMw4nBjBiTwfHPdDcEOvD6yEEJa-aj61qDJU7Uou54QkFW6lOdmS4MvI73bCwLS52CAKPesHzRU1x5juHsJqgD38vH-6W6aDlOpDHGTr5RjbpG_8extACn2jsR9H0>

pass

os-odl-nofeature-noha

Fuel/MCP

Michael Polenchuk

link<https://url10.mailanyone.net/v1/?m=1e2fw2-0002hR-47=57e1b682=XyPdH4_8po7LVJGdjI7LCLXlq7XSp1RoGh9niFKXdzkKDcRP9ZBX6nFuPlDlfqRGY4mAZYRqSk-jbOhIh0Xkz3YF56A_8Rkh9PrfPNUT6tcMEI4YjhxJIeEqhPNMt--ZS9jAIJXfsxL7KSohbT5M4DL-_wi40EkqFwUoa6ui_-24lYZzWL2Aa8MIS23VUrOAaO8xUC4LlQC_yOQIwnUKr6gvDWvZfjP_wMJMc6407oIP8EoicQzkeBoM02lF3joOqQRkkqiPf3lemj61Ft9TdNuJ5x789YcS-i8TEuqRKqE>

not running

os-odl-nofeature-ha

Fuel/MCP

Michael Polenchuk

link<https://url10.mailanyone.net/v1/?m=1e2fw2-0002hR-47=57e1b682=eaGvkmvcE3DruK_CYIbQiWq9xrQcTPNxWJ2thOUn8sVwD9wSLzvYEBx4qqd9_jsATQwYnXNkbMAPIjR_bPMmTw6FXcEINdYsxef9t7PisKbEjCDWRvpBEm74K86SLdj0e4oHvxt19GDg1Xw7i8V1mru5PAAW2iqEoEy9KiVewRcL-AJY7rWWWcveEdUY9E-717NbRL6xjACmelkFZFPFfQpdNFw7qvwKhCSOmPTPZKBhVvZW7Ir7Z0voCVwJjTd37vfF93UIxusTs7D7ovc-5Xd8isoUJxh2qImD4zJ-h-k>

pass


On Wed, Oct 11, 2017 at 6:32 PM, chenjiankun 
<chenjiank...@huawei.com<mailto:chenjiank...@huawei.com>> wrote:
Hi David,

Fuel x86 and Fuel arrch64 page are available now.

See:

1.   
http://testresults.opnfv.org/reporting/euphrates/yardstick/status-f...@x86.html<https://url10.mailanyone.net/v1/?m=1e2fw2-0002hR-47=57e1b682=cyOCbT5lyHS-_MxGtuWwc075qKkNuh8kJEkQW2_dzQmAej6ZxFNDegF4ZL9y8XlIliakrDuJNDggS1Qaca3h5b9QgHUtkmX6OJ7C_ZPKfyHxU76iB65Q4rW6nWQamZbLt5BkM6BJralwELoHlnd-WtSpcmXr8YLGdM0GGp5k2Nn4LsrYvXujdeSS63QjkKGZlnWFeSKMYJTWPrJ2PUwqhX21d49T6wjwnTBL-GIRtxI4HQLHX8PfZ6U5FLku749B4km9BvG1jv3YqI9VTanqf6-cC7ODkoVXAwdrUTcJ9N0>

2.   
http://testresults.opnfv.org/reporting/euphrates/yardstick/status-f...@aarch64.html<https://url10.mailanyone.net/v1/?m=1e2fw2-0002hR-47=57e1b682=K03oVT4HbPtuETAftZiBQjQx2rHpUwJrlat8XnGr5J-uQULSkunzuE6lMvb70pj082jsZMcHAKO3lNrDkuQ7fUSeEqMyGgqNrp3jo0DgSGi-a-UQtIb6XHWtxWbyIkz4UhwcNyIWftNxUy5ti2IslNp4_4bM9-NSCzzqTT4ujic4h8GcYFl-9sUwnY

Re: [opnfv-tech-discuss] [release][euphrates] Euphrates status

[chenjiankun]

Since we split fuel with fuel@x86 and fuel@aarch64, so the history data are not 
available any more.
So if we want to see the trend, still need several days.

BTW, we change the criteria from ‘SUCCESS’ to ‘PASS’ as Morgan suggested, so 
the results you see maybe not accurate yesterday, I have change the field in DB.
So now it should show the right result.

BR,
Jack Chan

发件人: David McBride [mailto:dmcbr...@linuxfoundation.org]
发送时间: 2017年10月13日 0:01
收件人: chenjiankun
抄送: opnfv-project-leads; TSC OPNFV; TECH-DISCUSS OPNFV; Alexandru Avadanii; 
Michail Polenchuk
主题: Re: [opnfv-tech-discuss] [release][euphrates] Euphrates status

+Michail

Thanks, Jack.

I see the test results pages, but no results.  When do you think that we'll see 
results populating the pages?

Also, the deploy results for fuel@x86 do not look very good:

os-nosdn-nofeature-noha

Fuel/MCP

Michael Polenchuk

link<https://build.opnfv.org/ci/job/fuel-os-nosdn-nofeature-noha-baremetal-daily-euphrates/>

not running

os-nosdn-nofeature-ha

Fuel/MCP

Michael Polenchuk

link<https://build.opnfv.org/ci/job/fuel-os-nosdn-nofeature-ha-baremetal-daily-euphrates/>

fail

os-nosdn-ovs-noha

Fuel/MCP

Michael Polenchuk

link<https://build.opnfv.org/ci/job/fuel-os-nosdn-ovs-noha-baremetal-daily-euphrates/>

not running

os-nosdn-ovs-ha

Fuel/MCP

Michael Polenchuk

link<https://build.opnfv.org/ci/job/fuel-os-nosdn-ovs-ha-baremetal-daily-euphrates/>

pass

os-odl-nofeature-noha

Fuel/MCP

Michael Polenchuk

link<https://build.opnfv.org/ci/job/fuel-os-odl-nofeature-noha-baremetal-daily-euphrates/>

not running

os-odl-nofeature-ha

Fuel/MCP

Michael Polenchuk

link<https://build.opnfv.org/ci/job/fuel-os-odl-nofeature-ha-baremetal-daily-euphrates/>

pass


On Wed, Oct 11, 2017 at 6:32 PM, chenjiankun 
<chenjiank...@huawei.com<mailto:chenjiank...@huawei.com>> wrote:
Hi David,

Fuel x86 and Fuel arrch64 page are available now.

See:

1.   
http://testresults.opnfv.org/reporting/euphrates/yardstick/status-f...@x86.html

2.   
http://testresults.opnfv.org/reporting/euphrates/yardstick/status-f...@aarch64.html

BR,
Jack Chan

发件人: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>]
 代表 David McBride
发送时间: 2017年10月12日 2:59
收件人: Alexandru Avadanii
抄送: opnfv-project-leads; TSC OPNFV; TECH-DISCUSS OPNFV
主题: Re: [opnfv-tech-discuss] [release][euphrates] Euphrates status

Alex - thanks for the update. - D

On Sun, Oct 8, 2017 at 2:59 AM, Alexandru Avadanii 
<alexandru.avada...@enea.com<mailto:alexandru.avada...@enea.com>> wrote:
Hi, David,
Fuel now pushes Yardstick results too [1]. The results are not filtered by arch 
yet.

BR,
Alex

[1] http://testresults.opnfv.org/reporting/euphrates/yardstick/status-fuel.html


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto: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 David McBride
Sent: Tuesday, October 03, 2017 3:33 AM
To: TSC OPNFV
Cc: opnfv-project-leads; TECH-DISCUSS OPNFV
Subject: Re: [opnfv-tech-discuss] [release][euphrates] Euphrates status

Updated installer and scenario data after the weekend:

Installer Summary (changes in red)



DEPLOY ON EUPHRATES

FUNCTEST DASHBOARD ON EUPHRATES

YARDSTICK DASHBOARD ON EUPHRATES

APEX

yes

yes

yes

COMPASS

yes

yes

yes

DAISY

yes

yes

n/a

FUEL (X86)

yes

yes

no

FUEL (AARCH64)

yes

yes

no

JOID

yes

yes

yes

Scenario Summary

Total (listed on scenario status page and found in Jenkins)

45

Pass Deploy

58%

Fail Deploy

36%

Not Running

9%


Functest results

58%

YardStick results

42%



On Fri, Sep 29, 2017 at 7:50 PM, David McBride 
<dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>> wrote:
TSC Members,

As you know, the Euphrates release is scheduled for Oct 6.  In advance of the 
next TSC meeting, here is the status of the release. Let me know if you have 
questions or comments.

Installer Summary



deploy on euphrates

Functest dashboard on euphrates

yardstick dashboard on euphrates

Apex

yes

yes

yes

Compass

yes

no

no

daisy

yes

yes

n/a

fuel (x86)

yes

yes

no

fuel (aarch64)

yes

no

no

Joid

yes

yes

yes



Scenario Summary

Total (listed on scenario status page and found in Jenkins)

45

Pass Deploy

47%

Fail Deploy

42%

Not Running

11%


Functest results

49%

YardStick results

38%


Major Issues

  1.  Chinese National Holiday.  There is a Chinese holiday from Oct 1 - 8.  
During this period, there will be power maintenance in the building where the 
Huawei lab is located and the pods will be offline.  
(https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-September/018333.html<https://url10.mailanyone.net/v1

Re: [opnfv-tech-discuss] [release][euphrates] Euphrates status

[chenjiankun]

Hi David,

Fuel x86 and Fuel arrch64 page are available now.

See:

1.   
http://testresults.opnfv.org/reporting/euphrates/yardstick/status-f...@x86.html

2.   
http://testresults.opnfv.org/reporting/euphrates/yardstick/status-f...@aarch64.html

BR,
Jack Chan

发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 David McBride
发送时间: 2017年10月12日 2:59
收件人: Alexandru Avadanii
抄送: opnfv-project-leads; TSC OPNFV; TECH-DISCUSS OPNFV
主题: Re: [opnfv-tech-discuss] [release][euphrates] Euphrates status

Alex - thanks for the update. - D

On Sun, Oct 8, 2017 at 2:59 AM, Alexandru Avadanii 
> wrote:
Hi, David,
Fuel now pushes Yardstick results too [1]. The results are not filtered by arch 
yet.

BR,
Alex

[1] http://testresults.opnfv.org/reporting/euphrates/yardstick/status-fuel.html


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org]
 On Behalf Of David McBride
Sent: Tuesday, October 03, 2017 3:33 AM
To: TSC OPNFV
Cc: opnfv-project-leads; TECH-DISCUSS OPNFV
Subject: Re: [opnfv-tech-discuss] [release][euphrates] Euphrates status

Updated installer and scenario data after the weekend:

Installer Summary (changes in red)



DEPLOY ON EUPHRATES

FUNCTEST DASHBOARD ON EUPHRATES

YARDSTICK DASHBOARD ON EUPHRATES

APEX

yes

yes

yes

COMPASS

yes

yes

yes

DAISY

yes

yes

n/a

FUEL (X86)

yes

yes

no

FUEL (AARCH64)

yes

yes

no

JOID

yes

yes

yes

Scenario Summary

Total (listed on scenario status page and found in Jenkins)

45

Pass Deploy

58%

Fail Deploy

36%

Not Running

9%


Functest results

58%

YardStick results

42%



On Fri, Sep 29, 2017 at 7:50 PM, David McBride 
> wrote:
TSC Members,

As you know, the Euphrates release is scheduled for Oct 6.  In advance of the 
next TSC meeting, here is the status of the release. Let me know if you have 
questions or comments.

Installer Summary



deploy on euphrates

Functest dashboard on euphrates

yardstick dashboard on euphrates

Apex

yes

yes

yes

Compass

yes

no

no

daisy

yes

yes

n/a

fuel (x86)

yes

yes

no

fuel (aarch64)

yes

no

no

Joid

yes

yes

yes



Scenario Summary

Total (listed on scenario status page and found in Jenkins)

45

Pass Deploy

47%

Fail Deploy

42%

Not Running

11%


Functest results

49%

YardStick results

38%


Major Issues

  1.  Chinese National Holiday.  There is a Chinese holiday from Oct 1 - 8.  
During this period, there will be power maintenance in the building where the 
Huawei lab is located and the pods will be offline.  
(https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-September/018333.html)
 This will impact the Compass and JOID installers, as well as all of the 
projects that depend on those installers. The Yardstick project will also be 
impacted by the Huawei lab outage.
  2.  Intel lab firewall reconfiguration.  The status remains unchanged.  In 
the mean time, the LF release engineering team has identified a workaround 
which could be in place by Monday or Tuesday.  The main impact has been that 
the Apex, Compass, and JOID installers have had to shift builds to an alternate 
POD, thereby reducing capacity.  In addition, the VSPerf and KVM4NFV projects 
are without CI support.
  3.  Docker builds.  See 
RELENG-315.
  With the increase of the number of docker jobs in Euphrates, there have been 
a lot of failures due to timeouts.  This has been partially resolved with 
additional capacity and improvements to the script, but remains an open issue.  
This affects any project that requires docker builds, such as StorPerf.

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride



--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride



--
David McBride
Release Manager, OPNFV
Mobile: 

Re: [opnfv-tech-discuss] [OPNFV] [testing group] landing page: score and trust indicator

[chenjiankun]

@Morgan, thank you for your clearly illustration.

I am trying to write a demo to update the status and trust_indicator now.

But the definition of status and trust_indicator still to be discuss.
So if you have any suggestions, please do not hesitate to comment here.
Once we come to a conclusion, I will write a python demo script or an API for 
you to implement it.
And then our landing page will finally  works.

Any ideas are all welcome~ ☺

Regards,
Jack Chan

发件人: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com]
发送时间: 2017年9月15日 22:35
收件人: Brattain, Ross B; Gaoliang (kubi); mark.bei...@emc.com; Cooper, Trevor; 
MORTON, ALFRED C (AL); Yuyang (Gabriel); jalaus...@suse.com; chenjiankun; 
test...@lists.opnfv.org
抄送: opnfv-tech-discuss@lists.opnfv.org
主题: [OPNFV] [testing group] landing page: score and trust indicator

Hi

we initiated the landing page some time ago: 
http://testresults.opnfv.org/testing/#!/landingpage/table

front and back end are now ready
Jack started doing an update for Yardstick
It is now possible to call the Test API to set a score and see/modify trust 
indicator after a CI run.

during the plugfest we saw that we were not fully aligned on what we want to 
show on such landing page
the recent discussion on the reporting pages show also some differences on the 
way we report our results

I think we need to agree on a minimum common view during a Testing working 
meeting to have a consistent page

Concretely we have 2 scenario parameters for this landing page:
- Scenario score
- Scenario Trust Indicator

Scenario score
***
Today there are 2 main views

VSPERF, Yardstick and Bottleneck => report Jenkins status assuming that
- SLA/threshold neither defined (VSPERF) nor taken into account (Yardstick) to 
set test suite criteria to PASS or FAIL
- if test suite deals with lots of tests => only 1 aggregated result 
corresponding to the test suite "runnability" in CI

In Functest we do a calculation based on the sum of all the individual cases 
(https://wiki.opnfv.org/pages/viewpage.action?pageId=6828617) that is why in 
reporting page we have score like 14/27, 18/18, 1/9 
The first figure represent the success (18/18 = max score; 1/9 = very poor 
results)
the max score represent the richness of the test suite, i.e. /9 = 3 test cases 
in the suite; / 27 = 9 test cases.
We have a x3 factor due to the criteria of 4 consecutive runs. In the evolution 
I had in mind to report only the scenario status
In Storperf Mark defined and takes into the threshold to set the test to PASS 
or FAIL

So we may have 2 approaches for the landing page
- The Jenkins status (nb run OK / nb attempted over the last N days)
- The testing status (tests are run and results are according to project 
success criteria e.g. for functest we expect the max score, 15/18 will be 
considered as FAIL)

What is your view?
What kind of score would you give to the CI runs currently running?
shall we be all consistent or is it up to each project to define what it wants 
to show in such page?

Trust Indicator
**
this parameter allows to consider the scenario evolution versus time
in previous discussions we considered 3 states:
- Silver (init)
- Gold
- Platinium

this indicator is related to the scenario on which a test project is running 
the test suite

A simple proposal for scenario promotion

[cid:image001.png@01D33181.8CE0EED0]

/Morgan

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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

Re: [opnfv-tech-discuss] [yardstick] yardstick env prepare - chroot error

[chenjiankun]

Hi

Is there yardstick-image in /home/opnfv/images?

Anyway, if you are compiling for arm pod, yardstick-image should be rebuild.
Since I am not familiar with arm, maybe you can check with Alexandru Avadanii.

Regards,
Jack Chan

发件人: vven...@codeaurora.org [mailto:vven...@codeaurora.org]
发送时间: 2017年8月24日 16:48
收件人: chenjiankun; opnfv-tech-discuss@lists.opnfv.org
主题: RE: [opnfv-tech-discuss] [yardstick] yardstick env prepare - chroot error

Hi Jack,
Thanks for the reply. I see below images in /home/opnfv/images directory. I am 
compiling for arm pod. Please suggest.

root@57db44f0c4b5:/home/opnfv/images# ls
cirros-0.3.5-x86_64-disk.img  xenial-server-cloudimg-amd64-disk1.img
root@57db44f0c4b5:/home/opnfv/images#

But I followed the steps you suggested, still I see the same issue…’Image build 
failed with 126’ because of chroot error

Thanks
-Venkat


From: chenjiankun [mailto:chenjiank...@huawei.com]
Sent: Thursday, August 24, 2017 12:04 PM
To: vven...@codeaurora.org<mailto:vven...@codeaurora.org>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] [yardstick] yardstick env prepare - chroot 
error

Hi,

It seems there are something wrong when you build yardstick-image.
Maybe you can download yardstick-image directly:
 cd /home/opnfv/images
 wget http://artifacts.opnfv.org/yardstick/images/yardstick-image.img

Then execute yardstick env prepare again.
Hope that would work for you.

Regards,
Jack Chan

发件人: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 
vven...@codeaurora.org<mailto:vven...@codeaurora.org>
发送时间: 2017年8月24日 13:26
收件人: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
主题: [opnfv-tech-discuss] [yardstick] yardstick env prepare - chroot error


Hi,

I am setting up yardstick using docker on Danube 3.0 and followed the 
instructions as per 
http://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/04-installation.html
Setup the env variables in /etc/yardstick/openstack.creds inside docker with 
the below mentioned parameters.
Next when I setup “yardstick env prepare” though it says [Finished] without 
prompting any error, I see the error as below in /var/log/yardstick/uwsgi.log 
(Also attached ). Request someone to help on this.

+ chroot /mnt/yardstick /ubuntu-server-cloudimg-modify.sh 10.222.196.22
chroot: failed to run command '/ubuntu-server-cloudimg-modify.sh': Exec format 
error
+ error_trap
+ local rc=126



#!/bin/sh
export OS_NO_CACHE='true'
export OS_TENANT_NAME='admin'
export OS_PROJECT_NAME='admin'
export OS_USERNAME='admin'
export OS_PASSWORD='admin'
export OS_AUTH_URL='http://192.168.0.2:5000/v3'
export OS_IDENTITY_API_VERSION=3
export OS_DEFAULT_DOMAIN='default'
export OS_USER_DOMAIN_NAME='Default'
export OS_PROJECT_DOMAIN_NAME='Default'
export OS_AUTH_STRATEGY='keystone'
export OS_REGION_NAME='RegionOne'
export CINDER_ENDPOINT_TYPE='internalURL'
export GLANCE_ENDPOINT_TYPE='internalURL'
export KEYSTONE_ENDPOINT_TYPE='internalURL'
export NOVA_ENDPOINT_TYPE='internalURL'
export NEUTRON_ENDPOINT_TYPE='internalURL'
export OS_ENDPOINT_TYPE='internalURL'
export MURANO_REPO_URL='http://storage.apps.openstack.org/'
export MURANO_PACKAGES_SERVICE='glance'
export EXTERNAL_NETWORK=’admin_floating_net’

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] [yardstick] yardstick env prepare - chroot error

[chenjiankun]

Hi,

It seems there are something wrong when you build yardstick-image.
Maybe you can download yardstick-image directly:
 cd /home/opnfv/images
 wget http://artifacts.opnfv.org/yardstick/images/yardstick-image.img

Then execute yardstick env prepare again.
Hope that would work for you.

Regards,
Jack Chan

发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 vven...@codeaurora.org
发送时间: 2017年8月24日 13:26
收件人: opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] [yardstick] yardstick env prepare - chroot error


Hi,

I am setting up yardstick using docker on Danube 3.0 and followed the 
instructions as per 
http://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/04-installation.html
Setup the env variables in /etc/yardstick/openstack.creds inside docker with 
the below mentioned parameters.
Next when I setup “yardstick env prepare” though it says [Finished] without 
prompting any error, I see the error as below in /var/log/yardstick/uwsgi.log 
(Also attached ). Request someone to help on this.

+ chroot /mnt/yardstick /ubuntu-server-cloudimg-modify.sh 10.222.196.22
chroot: failed to run command '/ubuntu-server-cloudimg-modify.sh': Exec format 
error
+ error_trap
+ local rc=126



#!/bin/sh
export OS_NO_CACHE='true'
export OS_TENANT_NAME='admin'
export OS_PROJECT_NAME='admin'
export OS_USERNAME='admin'
export OS_PASSWORD='admin'
export OS_AUTH_URL='http://192.168.0.2:5000/v3'
export OS_IDENTITY_API_VERSION=3
export OS_DEFAULT_DOMAIN='default'
export OS_USER_DOMAIN_NAME='Default'
export OS_PROJECT_DOMAIN_NAME='Default'
export OS_AUTH_STRATEGY='keystone'
export OS_REGION_NAME='RegionOne'
export CINDER_ENDPOINT_TYPE='internalURL'
export GLANCE_ENDPOINT_TYPE='internalURL'
export KEYSTONE_ENDPOINT_TYPE='internalURL'
export NOVA_ENDPOINT_TYPE='internalURL'
export NEUTRON_ENDPOINT_TYPE='internalURL'
export OS_ENDPOINT_TYPE='internalURL'
export MURANO_REPO_URL='http://storage.apps.openstack.org/'
export MURANO_PACKAGES_SERVICE='glance'
export EXTERNAL_NETWORK=’admin_floating_net’

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] timeout error during env prepare

[chenjiankun]

Hi,

We wait for a certain times when prepare env. It is the reason why you got a 
timeout error.
Since there is asynchronous thread run in backend, so even it is timeout, the 
task start run.
So you can use the follow command to check if yardstick-image, cirros-0.3.5 
exists:
 openstack image list

If these images still didn’t exists, maybe we should check the log:
 /var/log/yardstick/uwsgi.log

BTW, which version of yardstick you are using now?

Regards,
Jack Chan

发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Kalaivani R
发送时间: 2017年7月18日 15:30
收件人: opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] timeout error during env prepare


Hi,



Getting timeout error during

yardstick env prepare.


can any one tel what might be the issue.


Regards,

Kalaivani.R

Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at http://www.techmahindra.com/Disclaimer.html externally 
http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra.

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

Re: [opnfv-tech-discuss] [OpenRetriever][Yardstick] Yardstick first kubernetes test case

[chenjiankun]

Hi jiaxuan,

We assuming that there is a CI POD(as SUT), so that we can run this test case 
the way as CI do. And then upload the test result to the database.

Regards,
Jack Chan

发件人: 贾玄 [mailto:jiax...@chinamobile.com]
发送时间: 2017年7月18日 15:18
收件人: chenjiankun; dmcbr...@linuxfoundation.org
抄送: test...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org; 
jason.jiax...@gmail.com; ruijing@intel.com; 'Ross Brattain'; Gaoliang (kubi)
主题: 答复: [opnfv-tech-discuss] [OpenRetriever][Yardstick] Yardstick first 
kubernetes test case

To Jiankun:
Thanks for your great help. That is a big step for OpenRetriever.

For the POD, what do you mean we do not have the pod to test it currently ? 
Does it mean there is no POD available for us ? or there is no POD satisfy our 
requirement ?

For E release, I submit our resource requirement in this page.
https://wiki.opnfv.org/display/SWREL/Project+CI+Resource+Requirements+for+Euphrates

Hi, Dave, Do you know how can openretriever team get the resource ?  What need 
we  do ?

Thanks

Xuan Jia
Project Manager
Big Data & IT Technology Research Center China Mobile Research Institute
32 Xuanwumen West Street, Xicheng Distirct, Beijing 100032, China
Mobile: (+86) 13811000575
E-mail: jiax...@chinamobile.com<mailto:jiax...@chinamobile.com>

发件人: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 chenjiankun
发送时间: 2017年7月18日 14:15
收件人: jason.jiax...@gmail.com<mailto:jason.jiax...@gmail.com>; 
ruijing@intel.com<mailto:ruijing@intel.com>; Ross Brattain 
<ross.b.bratt...@intel.com<mailto:ross.b.bratt...@intel.com>>; Gaoliang (kubi) 
<jean.gaoli...@huawei.com<mailto:jean.gaoli...@huawei.com>>
抄送: test...@lists.opnfv.org<mailto:test...@lists.opnfv.org>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
主题: [opnfv-tech-discuss] [OpenRetriever][Yardstick] Yardstick first kubernetes 
test case

Hi All,

After this patch(https://gerrit.opnfv.org/gerrit/#/c/36537/) merged, we are 
very glad to have the first test case in yardstick for kubernetes: ping_k8s.
With the help of @Ruijing(thanks Ruijing:) as well as OpenRetriever team), now 
we have a basic kubernetes context, we have the basic ability to use kubernetes 
context
to orchestrate containers(as SUT) and then do test on it.

It should be our first step, I will strengthen kubernetes context step by step 
in the future.

But we also have a problem: Ideally this test case should run in CI so that we 
can do continuous testing, but unfortunately we do not have the pod to test it 
currently.
Also we need a way to trigger test case and then report the test result to our 
database. What’s your opinion? please do not hesitate to comment.

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

[opnfv-tech-discuss] [OpenRetriever][Yardstick] Yardstick first kubernetes test case

[chenjiankun]

Hi All,

After this patch(https://gerrit.opnfv.org/gerrit/#/c/36537/) merged, we are 
very glad to have the first test case in yardstick for kubernetes: ping_k8s.
With the help of @Ruijing(thanks Ruijing:) as well as OpenRetriever team), now 
we have a basic kubernetes context, we have the basic ability to use kubernetes 
context
to orchestrate containers(as SUT) and then do test on it.

It should be our first step, I will strengthen kubernetes context step by step 
in the future.

But we also have a problem: Ideally this test case should run in CI so that we 
can do continuous testing, but unfortunately we do not have the pod to test it 
currently.
Also we need a way to trigger test case and then report the test result to our 
database. What's your opinion? please do not hesitate to comment.

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

[opnfv-tech-discuss] 答复: [yardstick] Yardstick run-time issue

[chenjiankun]

Hi,

for the yardstick-plot, now it is deprecated now.
If you want to parse data to the GUI, you can use the InfluxDB and Grafana.
But unfortunately, now our documentation only support using docker to install. 
The link is as bellow:
https://wiki.opnfv.org/display/yardstick/How+to+deploy+InfluxDB+and+Grafana+locally

Maybe you can use the documentation of influxDB and Grafana to install them.
And then config yardstick  as the documentation in the link.

That would be great if you plan to submit a patch to yardstick.
If you need any help, please do not hesitate to contact me.

Regards,
Jack Chan


发件人: Marco Varlese [mailto:marco.varl...@suse.com]
发送时间: 2017年3月14日 19:20
收件人: chenjiankun; Tallgren, Tapio; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
主题: Re: [opnfv-tech-discuss] [yardstick] Yardstick run-time issue

On Tue, 2017-03-14 at 10:46 +, chenjiankun wrote:

Hi,

See the comment.

Regards,
Jack Chan
From: Marco Varlese [mailto:marco.varl...@suse.com]
Sent: Tuesday, March 14, 2017 5:14 PM
To: chenjiankun; Tallgren, Tapio; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [yardstick] Yardstick run-time issue

On Tue, 2017-03-14 at 09:08 +, chenjiankun wrote:
Hi Marco,

We made some change in Danube(including split requirements.txt from setup.py 
and using pip to install), I will upgrade the documentation soon.
Now you can use pip to install(pip install -r requirements.txt and pip install 
.).
Ok, but as far as I can tell, there are missing entries in the requirements.txt 
file which I had to manually install later (pip install ...) when yardstick was 
failing to launch and the .py script
was notifying me of missing modules... so I would say that there's still 
something missing beside splitting things in different files?
Do you mean there are some dependencies not including in the requirements.txt? 
Can you tell me what they are?

Will do. I have to collect everything I've done over the past week. Will keep 
you posted.

BTW, something appears to be broken with yardstick-plot too...
I'm passing to the script the output file generated by Yardstick and it breaks.
I tried multiple test-cases and all of them can't be parsed by yardstick-plot, 
generating always the same error message.

(yardstick_venv) stack@wingenfelder<mailto:stack@wingenfelder>:~/yardstick> 
yardstick-plot -i /tmp/yardstick.out -o /tmp/yardstick/
Parsing input file
Traceback (most recent call last):
  File "/home/stack/yardstick_venv/bin/yardstick-plot", line 11, in 
load_entry_point('yardstick==0.1.dev0', 'console_scripts', 
'yardstick-plot')()
  File 
"/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/plot/plotter.py",
 line 315, in main
parser.parse_input_file()
  File 
"/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/plot/plotter.py",
 line 97, in parse_input_file
self._add_record(record)
  File 
"/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/plot/plotter.py",
 line 73, in _add_record
runner_object = self.scenarios[record["runner_id"]]
KeyError: 'runner_id'


Actually you can run ./install.sh in yardstick root path.


As for creating a guest-image, you need not to add ssh-key-pair to the image. 
Yardstick will inject the key when creating the instance automatically.
I suppose you use cloud-init in the VM image for accomplishing this, correct?
We use heat to add the key. There is an option for it.


We generate the key dynamically for security reason. If you want to login the 
instance, you can use yardstick generated key to login.
The key gets deleted once the tests finish and - as you know - a new one is 
created at the next iteration...
You can use --keep-deploy option, it do not delete the vm. For example,
yardstick -d task start sample/ping.yaml --keep-deploy


The key file path is 
/usr/local/lib/python2.7/dist-packages/yardstick/resources/files/.
Sure, I know about this path but as mentioned above, the keys are deleted once 
the tests finish...



Regards,
Jack Chan
Cheers,
Marco



From: Marco Varlese [mailto:marco.varl...@suse.com]
Sent: Monday, March 13, 2017 7:34 PM
To: chenjiankun; Tallgren, Tapio; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [yardstick] Yardstick run-time issue

Hi,

I solved all the issues, etc.
I spotted some descrepancies in documentation and/or points opened to 
interpretation. I plan to submit a patch soon to address those.
Also, on my environment, lots of python dependencies were not installed 
"automatically" by the yardstick script and I had to proceed
by manually install them via "pip install ..."

Having said all this, if I want to create a guest-image myself... do you have 
an

Re: [opnfv-tech-discuss] [yardstick] Yardstick run-time issue

[chenjiankun]

Hi Marco,

We made some change in Danube(including split requirements.txt from setup.py 
and using pip to install), I will upgrade the documentation soon.
Now you can use pip to install(pip install -r requirements.txt and pip install 
.).

As for creating a guest-image, you need not to add ssh-key-pair to the image. 
Yardstick will inject the key when creating the instance automatically.
We generate the key dynamically for security reason. If you want to login the 
instance, you can use yardstick generated key to login.
The key file path is 
/usr/local/lib/python2.7/dist-packages/yardstick/resources/files/.

Regards,
Jack Chan

From: Marco Varlese [mailto:marco.varl...@suse.com]
Sent: Monday, March 13, 2017 7:34 PM
To: chenjiankun; Tallgren, Tapio; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [yardstick] Yardstick run-time issue

Hi,

I solved all the issues, etc.
I spotted some descrepancies in documentation and/or points opened to 
interpretation. I plan to submit a patch soon to address those.
Also, on my environment, lots of python dependencies were not installed 
"automatically" by the yardstick script and I had to proceed
by manually install them via "pip install ..."

Having said all this, if I want to create a guest-image myself... do you have 
any documentation or can you suggest me how to make the
guest image "working" with the ssh-key-pair which Yardstick uses? My 
understanding is that yardstick generates a new key everytime it runs
so I am not clear how the endpoints can communicate.

Any help on the above would be much appreciated.


Thanks,
Marco


On Fri, 2017-03-10 at 01:53 +, chenjiankun wrote:
Hi,

SSHTimeout may be caused by lots of reasons.
Maybe there is something wrong with network, router, security group, so it is 
hard to locate the problem for user.
You can ping and ssh the ip when the yardstick ssh client try to ssh the 
instance. And see the return message of it.

Does this problem reproduce  every time?

Or maybe there is something wrong with the environment.
( Since every time after redeploying the environment, the problem is different, 
so there is a little possibility for the environment)
So maybe you can try to redeploying the environment to see if it reproduce.

Can you tell me the version of the devstack and what openstack version you’re 
deploying. I would deploy one locally and then try to figure it out.

Regards,
Jack Chan
From: Marco Varlese [mailto:marco.varl...@suse.com]
Sent: Thursday, March 09, 2017 6:29 PM
To: Tallgren, Tapio; chenjiankun; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [yardstick] Yardstick run-time issue

Hi,

So after redeploying my devstack environment, it looks like yardstick managed 
to deploy the two VMs but the ping test fails

Context 'demo-2a3523ca' deployed
Starting runner of type 'Duration'
2017-03-09 11:14:56,003 yardstick.benchmark.runners.duration duration.py:43 
INFO worker START, duration 60 sec, class 
2017-03-09 11:14:56,004 yardstick.benchmark.scenarios.networking.ping 
ping.py:56 INFO Log in via key, user:cirros, host:10.0.0.70, 
key_filename:/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/resources/files/yardstick_key-0e70545c

Process Process-2:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/multiprocessing/process.py", line 258, in 
_bootstrap
self.run()
  File "/usr/lib64/python2.7/multiprocessing/process.py", line 114, in run
self._target(*self._args, **self._kwargs)
  File 
"/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/benchmark/runners/duration.py",
 line 47, in _worker_process
benchmark = cls(scenario_cfg, context_cfg)
  File 
"/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/benchmark/scenarios/networking/ping.py",
 line 60, in __init__
self.connection.wait(timeout=600)
  File 
"/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/ssh.py",
 line 301, in wait
raise SSHTimeout("Timeout waiting for '%s'", self.host)
SSHTimeout: ("Timeout waiting for '%s'", u'10.0.0.70')
Runner failed
Undeploying all contexts
Undeploying context 'demo-2a3523ca'


Do I need to configure anything (still) for yardstick?


Thanks,
Marco


On Wed, 2017-03-08 at 14:36 +0100, Marco Varlese wrote:
On Wed, 2017-03-08 at 15:31 +0200, Tallgren, Tapio wrote:
Does the nova scheduler log tell anything useful about why there are not enough 
hosts available?

Since you are running in a VM, it could be that you really do not have enough 
hosts.

I moved everything to a physical host since last time it was suggested that VM 
could be problematic.
So, eveything is running on physical machine right now.


-Tapio




On 03/08/2017 12:54 PM

Re: [opnfv-tech-discuss] [yardstick] Yardstick run-time issue

[chenjiankun]

Hi,

SSHTimeout may be caused by lots of reasons.
Maybe there is something wrong with network, router, security group, so it is 
hard to locate the problem for user.
You can ping and ssh the ip when the yardstick ssh client try to ssh the 
instance. And see the return message of it.

Does this problem reproduce  every time?

Or maybe there is something wrong with the environment.
( Since every time after redeploying the environment, the problem is different, 
so there is a little possibility for the environment)
So maybe you can try to redeploying the environment to see if it reproduce.

Can you tell me the version of the devstack and what openstack version you’re 
deploying. I would deploy one locally and then try to figure it out.

Regards,
Jack Chan
From: Marco Varlese [mailto:marco.varl...@suse.com]
Sent: Thursday, March 09, 2017 6:29 PM
To: Tallgren, Tapio; chenjiankun; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [yardstick] Yardstick run-time issue

Hi,

So after redeploying my devstack environment, it looks like yardstick managed 
to deploy the two VMs but the ping test fails

Context 'demo-2a3523ca' deployed
Starting runner of type 'Duration'
2017-03-09 11:14:56,003 yardstick.benchmark.runners.duration duration.py:43 
INFO worker START, duration 60 sec, class 
2017-03-09 11:14:56,004 yardstick.benchmark.scenarios.networking.ping 
ping.py:56 INFO Log in via key, user:cirros, host:10.0.0.70, 
key_filename:/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/resources/files/yardstick_key-0e70545c

Process Process-2:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/multiprocessing/process.py", line 258, in 
_bootstrap
self.run()
  File "/usr/lib64/python2.7/multiprocessing/process.py", line 114, in run
self._target(*self._args, **self._kwargs)
  File 
"/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/benchmark/runners/duration.py",
 line 47, in _worker_process
benchmark = cls(scenario_cfg, context_cfg)
  File 
"/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/benchmark/scenarios/networking/ping.py",
 line 60, in __init__
self.connection.wait(timeout=600)
  File 
"/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/ssh.py",
 line 301, in wait
raise SSHTimeout("Timeout waiting for '%s'", self.host)
SSHTimeout: ("Timeout waiting for '%s'", u'10.0.0.70')
Runner failed
Undeploying all contexts
Undeploying context 'demo-2a3523ca'


Do I need to configure anything (still) for yardstick?


Thanks,
Marco


On Wed, 2017-03-08 at 14:36 +0100, Marco Varlese wrote:
On Wed, 2017-03-08 at 15:31 +0200, Tallgren, Tapio wrote:
Does the nova scheduler log tell anything useful about why there are not enough 
hosts available?

Since you are running in a VM, it could be that you really do not have enough 
hosts.

I moved everything to a physical host since last time it was suggested that VM 
could be problematic.
So, eveything is running on physical machine right now.


-Tapio




On 03/08/2017 12:54 PM, Marco Varlese wrote:
Hi,

I can create manually an instance with the "openstack server create".

However, when yardstick does its magic I get the following error:

Writing 
/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/resources/files/yardstick_key-e9b9c7c2
 ...
Deploying context 'demo-86b44547'
2017-03-08 11:33:12,907 yardstick.orchestrator.heat heat.py:450 INFO Creating 
stack 'demo-86b44547'
error: failed to deploy stack: 'Resource CREATE failed: ResourceInError: 
resources.athena.demo-86b44547: Went to status ERROR due to "Message: No valid 
host was found. There are not enough hosts available., Code: 500"'
Undeploying all contexts


And then - if I check the status:

(yardstick_venv) stack@wingenfelder<mailto:stack@wingenfelder>:~/yardstick> 
openstack server list
+--+--++--+--+
| ID   | Name | Status | 
Networks | Image Name   |
+--+--++--+--+
| c91fba90-500b-4c8e-86c3-f08b67a4f5e0 | athena.demo-86b44547 | ERROR  |
  | cirros-0.3.3 |
| 14a415e9-adaa-4d8a-b465-e9ccff85cbd8 | ares.demo-86b44547   | ACTIVE | 
demo-86b44547-test=10.0.1.11 | cirros-0.3.3 |
+--+--++------+--+


Thanks,
Marco

On Wed, 2017-03-08 at 06:11 +, chenjiankun wrote:
Hi,

Can you create an instance using openstack command manually?

Using the follow command:
open

Re: [opnfv-tech-discuss] [yardstick] Yardstick run-time issue

[chenjiankun]

Hi Marco,

What's the latest status of this issue?
Does my solution be OK for you?

I'm looking forward to your reply.

Regards,
Jack Chan

From: chenjiankun
Sent: Thursday, February 23, 2017 5:25 PM
To: 'Marco Varlese'
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [yardstick] Yardstick run-time issue


Hi Marco,



I am Jack from yardstick team.



I haven't experienced this issue before. But it seems there are some errors 
with the cirros image.

I think you can try to run ping test case in the follow steps:



1.   docker run -itd --privileged --name yardstick opnfv/yardstick:latest

2.   docker exec -it yardstick bash

3.   config and source the openstack openrc file(include EXTERNAL_NETWORK)

4.   load images: you can execute the follow command in this directory:

cd /home/opnfv/repos/yardstick

 bash tests/ci/load_image.sh

5.   run test case

 yardstick -d task start sample/ping.yaml



BTW, can you tell me:

1.   what's your Openstack version in your SUT?

2.   Which yardstick docker are you using?



If you have any other questions, please feel free to let me know. Thanks.



Best Regards,

Jack Chan





-Original Message-
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 Marco Varlese
Sent: Tuesday, February 21, 2017 7:37 PM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: [opnfv-tech-discuss] Yardstick run-time issue



Hi,

I'm trying to setup an environment to deploy Yardstick; to start with I'm doing 
everything in one single Virtual machine.



The Virtual Machine basically represent both the Jumphost and the SUT. I 
understand this is not the best to measure performance but my real lab setup is 
being currently worked on and I'd like to get ahead of the game with learning.



I have an Openstack environment installed via Devstack (master branch) 
including Heat.



When I try and launch the ping.yaml test case I get the following error:



2017-02-21 12:18:29,515 yardstick.orchestrator.heat heat.py:440 INFO Creating 
stack 'demo-054b1f93'

error: failed to deploy stack: 'ERROR: Property error: : resources.ares.demo-

054b1f93.properties.image: : "cirros-0.3.3" does not validate glance.image 
(constraint not found)'



Has anybody experienced this issue before?



Any help or input would be much appreciated.





Thanks,

Marco



___

opnfv-tech-discuss mailing list

opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>

https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
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 run-time issue

[chenjiankun]

Hi Marco,



I am Jack from yardstick team.



I haven't experienced this issue before. But it seems there are some errors 
with the cirros image.

I think you can try to run ping test case in the follow steps:



1.   docker run -itd --privileged --name yardstick opnfv/yardstick:latest

2.   docker exec -it yardstick bash

3.   config and source the openstack openrc file(include EXTERNAL_NETWORK)

4.   load images: you can execute the follow command in this directory:

cd /home/opnfv/repos/yardstick

 bash tests/ci/load_image.sh

5.   run test case

 yardstick -d task start sample/ping.yaml



BTW, can you tell me:

1.   what's your Openstack version in your SUT?

2.   Which yardstick docker are you using?



If you have any other questions, please feel free to let me know. Thanks.



Best Regards,

Jack Chan





-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Marco Varlese
Sent: Tuesday, February 21, 2017 7:37 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Yardstick run-time issue



Hi,

I'm trying to setup an environment to deploy Yardstick; to start with I'm doing 
everything in one single Virtual machine.



The Virtual Machine basically represent both the Jumphost and the SUT. I 
understand this is not the best to measure performance but my real lab setup is 
being currently worked on and I'd like to get ahead of the game with learning.



I have an Openstack environment installed via Devstack (master branch) 
including Heat.



When I try and launch the ping.yaml test case I get the following error:



2017-02-21 12:18:29,515 yardstick.orchestrator.heat heat.py:440 INFO Creating 
stack 'demo-054b1f93'

error: failed to deploy stack: 'ERROR: Property error: : resources.ares.demo-

054b1f93.properties.image: : "cirros-0.3.3" does not validate glance.image 
(constraint not found)'



Has anybody experienced this issue before?



Any help or input would be much appreciated.





Thanks,

Marco



___

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] testing meeting APAC slot

[chenjiankun]

Hi Morgan,

I am Jack from yardstick. How is it going?

I have attended the last APAC Testing meeting. I really appreciate your work in 
Testing view and Case Selection.

In the meeting you replied to me that the Testing user’s case configuration 
will be stored in the public mongoDB.
So I think maybe we need a register/login mechanism to manage this user’s 
configuration. What’s your point?
Or can we store it in local DB?

I have been in charge of yardstick reporting and yardstick API and have 
experience with web.
I really enjoy working in web. So I am wondering if there is anything I can do 
in Testing view and Case Selection.

I am looking forward to your reply.

Regards,
Jack Chan

发件人: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com]
发送时间: 2016年11月8日 17:15
收件人: Gaoliang (kubi); Lijun (Matthew); tian.hon...@huawei.com; Yujun Zhang; 
Cooper, Trevor; Jose Lausuch; rexlee8...@gmail.com; chenjiankun
抄送: opnfv-tech-discuss@lists.opnfv.org
主题: [OPNFV] testing meeting APAC slot


Hi

the next weekly meeting APAC slot is not clear. We indicate 2 dates in the 
wiki: https://wiki.opnfv.org/display/meetings/TestPerf

According to the calendar it is on the 9th but the agenda is declared for the 
10th...

I assume it is the 9 8UTC => I modified the wiki

if so for the moment we do not have chair/minutes and the agenda is limited to 
the discussion on priority for Danube (I assume I will introduce the topic 
during the TSC meeting today see attached "Building a TSC vision for Danube" 
deck )

I also created some slides to illustrate what we have discussed in Barcelona on 
the some aggregation actions to provide a consistent Testing reporting view as 
well as web pages to allow scenario owner/user to select their list of cases 
among all the test cases...

I can present it but I have a constraints at 8h25 so I may not be able to 
attend all the meeting

Suggested agenda (do not hesitate to amend it on the wiki...)

  *   Testing community Danube release landing page + scenario selection 
proposals(15')
  *   Test community common goals (20') 
https://etherpad.opnfv.org/p/TestCommunityGoals
  *   QTIP presentation (15')
  *   AoB (5')

/Morgan

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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