Re: [opnfv-tech-discuss] 答复: [functest] [sdnvpn] Proposal for removing installer dependent information in the test tools

[xudan (N)]

Hi Srikanth,

I have one question. Are the paths of all these log files constant for 
different environment (Apex, Fuel and commercial deployments)?
If all paths for different deployments are the same, then using config file to 
login and getting files can work.
If not, there will be some errors even though it can login with the config file.

One more question, what logs do SDNVPN get from all nodes? Are they useful for 
users? If not, can we have an option to disable it?

Thanks
Dan Xu

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of limingjiang
Sent: Thursday, October 12, 2017 9:24 AM
To: Srikanth Vavilapalli
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] 答复: [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

Hi Srikanth,

Yardstick can use a global pod.yaml for test cases.
Since each test case default use the “pod.yaml” located in 
“/etc/yardstick/pod.yaml”. so if you put “pod.yaml” here, it can apply to each 
test case.
The picture you show below is how yardstick test suite customize the input 
parameters, so it also support each test case with different “pod.yaml”
if you give each test case different “pod.yaml”

BR,
Rex

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

发件人: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Srikanth Vavilapalli
发送时间: 2017年10月12日 9:03
收件人: Jose Lausuch; Georg Kunz
抄送: 
opnfv-tech-discuss@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

Thanks everyone for your inputs.

So if Yardstick based approach is the preferred one, then I am thinking of 
extending the existing Deployment Factory class with a new generic INSTALLER 
type (something like “config-file” or so) which will provide the same interface 
as other adapters (ApexAdapter, FuelAdapter…etc), but instead reads from the a 
configured pod.yaml file to provide Node information. Plz let me know if you 
see any issues with this approach.

One quick question on Yardstick: Looks like Yardstick accepts the custom 
pod.yaml file on a per test case basis as shown in the below example. Can it 
also accept a global pod.yaml file that can be applied to all or a group of 
test cases.
-
file_name: opnfv_yardstick_tc043.yaml
   constraint:
  installer: xxx
  pod: xxx-pod1
   task_args:
  xxx-pod1: '{"pod_info": "etc/yardstick/.../pod.yaml",
  "host": "node1.LF","target": "node2.LF"}'

Thanks
Srikanth

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jose Lausuch
Sent: Wednesday, October 11, 2017 10:45 AM
To: Georg Kunz >
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

Hi,

I would vote for having something similar to Yardstick [1] but centralized in 
Releng with an easy python lib that enables functions like SCP things to/from 
the deployed nodes.

For your third point, log collection shouldn’t be done at test case level. It 
should be performed by CI after running the test tools, otherwise you can a 
false negative when running those test on non-OPNFV installers.

Regards,
Jose

[1] 
https://raw.githubusercontent.com/opnfv/yardstick/master/etc/yardstick/nodes/fuel_virtual/pod.yaml


On 11 Oct 2017, at 18:08, Georg Kunz 
> wrote:

Hi,

Just to highlight this, from a Dovetail/CVP perspective, the important aspect 
is that there are no dependencies on OPNFV-specific resources/lib in order to 
be able to run test cases against commercial non-OPNFV deployments.

Having to write an adapter for a particular commercial deployment before you 
can run Dovetail is obviously not really an option. So, for tests which require 
SSH/SCP access, we need to think about...

  *   If the adapter can be parameterized, so that we can make it a 
configuration option, e.g., specifying login credentials, source and target 
directories, etc., similarly to Yardstick.
  *   Reuse what Yardstick is using?
  *   If the test case be parameterized such that it does not attempt to gather 
logs if used for certification? (limited use, of course)
  *   …

Cheers

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: 

[opnfv-tech-discuss] 答复: [functest] [sdnvpn] Proposal for removing installer dependent information in the test tools

[limingjiang]

Hi Srikanth,

Yardstick can use a global pod.yaml for test cases.
Since each test case default use the “pod.yaml” located in 
“/etc/yardstick/pod.yaml”. so if you put “pod.yaml” here, it can apply to each 
test case.
The picture you show below is how yardstick test suite customize the input 
parameters, so it also support each test case with different “pod.yaml”
if you give each test case different “pod.yaml”

BR,
Rex

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

发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Srikanth Vavilapalli
发送时间: 2017年10月12日 9:03
收件人: Jose Lausuch; Georg Kunz
抄送: opnfv-tech-discuss@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

Thanks everyone for your inputs.

So if Yardstick based approach is the preferred one, then I am thinking of 
extending the existing Deployment Factory class with a new generic INSTALLER 
type (something like “config-file” or so) which will provide the same interface 
as other adapters (ApexAdapter, FuelAdapter…etc), but instead reads from the a 
configured pod.yaml file to provide Node information. Plz let me know if you 
see any issues with this approach.

One quick question on Yardstick: Looks like Yardstick accepts the custom 
pod.yaml file on a per test case basis as shown in the below example. Can it 
also accept a global pod.yaml file that can be applied to all or a group of 
test cases.
-
file_name: opnfv_yardstick_tc043.yaml
   constraint:
  installer: xxx
  pod: xxx-pod1
   task_args:
  xxx-pod1: '{"pod_info": "etc/yardstick/.../pod.yaml",
  "host": "node1.LF","target": "node2.LF"}'

Thanks
Srikanth

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jose Lausuch
Sent: Wednesday, October 11, 2017 10:45 AM
To: Georg Kunz >
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

Hi,

I would vote for having something similar to Yardstick [1] but centralized in 
Releng with an easy python lib that enables functions like SCP things to/from 
the deployed nodes.

For your third point, log collection shouldn’t be done at test case level. It 
should be performed by CI after running the test tools, otherwise you can a 
false negative when running those test on non-OPNFV installers.

Regards,
Jose

[1] 
https://raw.githubusercontent.com/opnfv/yardstick/master/etc/yardstick/nodes/fuel_virtual/pod.yaml


On 11 Oct 2017, at 18:08, Georg Kunz 
> wrote:

Hi,

Just to highlight this, from a Dovetail/CVP perspective, the important aspect 
is that there are no dependencies on OPNFV-specific resources/lib in order to 
be able to run test cases against commercial non-OPNFV deployments.

Having to write an adapter for a particular commercial deployment before you 
can run Dovetail is obviously not really an option. So, for tests which require 
SSH/SCP access, we need to think about...

  *   If the adapter can be parameterized, so that we can make it a 
configuration option, e.g., specifying login credentials, source and target 
directories, etc., similarly to Yardstick.
  *   Reuse what Yardstick is using?
  *   If the test case be parameterized such that it does not attempt to gather 
logs if used for certification? (limited use, of course)
  *   …

Cheers
Georg

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jose Lausuch
Sent: Wednesday, October 11, 2017 4:40 PM
To: Beierl, Mark >
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

Hi,

With regards to Functest, you can run it on any OpenStack deployment as long as 
you provide a proper RC file and meet the requirements on the jumphost (docker, 
connectivity to the deployment, …).

However, in some cases, some test cases from feature projects require SSH 
access to the deployment and to make things centralized, the deployment handler 
was created [1]. This is a library that allows users to get the number of nodes 

Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing installer dependent information in the test tools

[Srikanth Vavilapalli]

Thanks everyone for your inputs.

So if Yardstick based approach is the preferred one, then I am thinking of 
extending the existing Deployment Factory class with a new generic INSTALLER 
type (something like “config-file” or so) which will provide the same interface 
as other adapters (ApexAdapter, FuelAdapter…etc), but instead reads from the a 
configured pod.yaml file to provide Node information. Plz let me know if you 
see any issues with this approach.

One quick question on Yardstick: Looks like Yardstick accepts the custom 
pod.yaml file on a per test case basis as shown in the below example. Can it 
also accept a global pod.yaml file that can be applied to all or a group of 
test cases.
-
file_name: opnfv_yardstick_tc043.yaml
   constraint:
  installer: xxx
  pod: xxx-pod1
   task_args:
  xxx-pod1: '{"pod_info": "etc/yardstick/.../pod.yaml",
  "host": "node1.LF","target": "node2.LF"}'

Thanks
Srikanth

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jose Lausuch
Sent: Wednesday, October 11, 2017 10:45 AM
To: Georg Kunz 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

Hi,

I would vote for having something similar to Yardstick [1] but centralized in 
Releng with an easy python lib that enables functions like SCP things to/from 
the deployed nodes.

For your third point, log collection shouldn’t be done at test case level. It 
should be performed by CI after running the test tools, otherwise you can a 
false negative when running those test on non-OPNFV installers.

Regards,
Jose

[1] 
https://raw.githubusercontent.com/opnfv/yardstick/master/etc/yardstick/nodes/fuel_virtual/pod.yaml


On 11 Oct 2017, at 18:08, Georg Kunz 
> wrote:

Hi,

Just to highlight this, from a Dovetail/CVP perspective, the important aspect 
is that there are no dependencies on OPNFV-specific resources/lib in order to 
be able to run test cases against commercial non-OPNFV deployments.

Having to write an adapter for a particular commercial deployment before you 
can run Dovetail is obviously not really an option. So, for tests which require 
SSH/SCP access, we need to think about...

  *   If the adapter can be parameterized, so that we can make it a 
configuration option, e.g., specifying login credentials, source and target 
directories, etc., similarly to Yardstick.
  *   Reuse what Yardstick is using?
  *   If the test case be parameterized such that it does not attempt to gather 
logs if used for certification? (limited use, of course)
  *   …

Cheers
Georg

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jose Lausuch
Sent: Wednesday, October 11, 2017 4:40 PM
To: Beierl, Mark >
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

Hi,

With regards to Functest, you can run it on any OpenStack deployment as long as 
you provide a proper RC file and meet the requirements on the jumphost (docker, 
connectivity to the deployment, …).

However, in some cases, some test cases from feature projects require SSH 
access to the deployment and to make things centralized, the deployment handler 
was created [1]. This is a library that allows users to get the number of nodes 
from the deployment, functions to SCP things from the nodes and some other 
utils. The bad part of it is that it only supports Apex, Fuel and OSA for now…  
unless someones volunteers to write the other adapters for joid, mcp, compass 
osa..  This library might be used to extract the desired logs after 
Functest/Yardstick runs in CI to place them in artifact repo and post-analize.

Regards,
Jose

[1] https://git.opnfv.org/releng/tree/modules/opnfv/deployment




On 11 Oct 2017, at 16:23, Beierl, Mark 
> wrote:

Hello,

StorPerf very much relies on knowledge of the installer to gather information 
about the block storage underlay.  For example, the number of Ceph nodes, or 
even Ceph vs. LVM, is very relevant to the final report.  I also wish there 
were an installer agnostic method of collecting this information as right now I 
keep that code in the ci/daily.sh and other scripts.

With the new releng repository being created, perhaps it is time to start 
moving some of the installer specific code there?  I also see that being of 
benefit when adding XCI support, as technically that would be yet another type 
of installer.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell 

Re: [opnfv-tech-discuss] [opnfv-tsc] [qtip] stepping down as QTIP PTL after E release

[Julien]

Thanks Yujun,

Under your leadership, QTIP project has made a great progress. More and
more integration features have been implemented besides stability, It's
also an model to cooperate with upstream and other projects in the
community.

Yujun Zhang (ZTE) 于2017年10月9日周一 下午4:24写道：

> Hi all,
>
> I have decided to step down as PTL for QTIP after E release.
>
> I took the role since the end of C release. It has been a pleasant journey
> to travel across Danube and Euphrates and now it is time for a new leader
> to navigate the project in Fraser.
>
> I will stay onboard as a committer and continue to explore in OPNFV.
>
> Thanks all.
>
> --
> Yujun Zhang
>
> --
> Yujun Zhang
> ___
> opnfv-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
>
___
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] Releasing OPNFV tools in Euphrates

[Cooper, Trevor]

I think it would be helpful if we can evolve our test ecosystem diagram to show 
a distinction between “developer” type test tools and “user” type test tools … 
something to discuss in the Test Working Group.

/Trevor


From: test-wg-boun...@lists.opnfv.org [mailto:test-wg-boun...@lists.opnfv.org] 
On Behalf Of morgan.richo...@orange.com
Sent: Wednesday, October 11, 2017 2:49 AM
To: Alec Hothan (ahothan) ; Frank Brockners (fbrockne) 
; Sofia Wallin 
Cc: OLLIVIER Cédric IMT/OLN ; 'Brandon Wick' 
; Jose Lausuch ; 
test...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [test-wg] Releasing OPNFV tools in Euphrates

Agree to extend to mailing list :)

just to summarize, we started the discussion on doc for calipso for Euphrates, 
it triggered discussions more general topics including
- a topic on how to include NFVBench in Euphrates (Operation/testing)
- a discussion on OPNFV release / tooling release decorrelation

we can add a slot for this during the next weekly meeting 
https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting 
(maybe a bit late regarding the release date)
I was not able to attend the APAC slot this morning, according to IRC, I was 
not the only one...

/Morgan

On 10/10/2017 21:02, Alec Hothan (ahothan) wrote:

I wish this discussion was brought up on the tech-discuss mailing list ;-)

I had exactly the same questions than Frank at the very bottom and asked 
similar questions to David this morning on the release packaging.
Heather is also right on target to feel like tools should be independent of the 
platform release! This is clearly one of the benefits of having an independent 
versioning for projects vs release which I have been trying to push with the 
release tagging discussion.
For me there is absolutely no question that testing tools developed in OPNFV 
will be used outside of OPNFV release cycle and potentially on NFVi platforms 
that are not even in OPNFV labs and this clearly mandates an independent 
versioning for each tool project.
Trying to version tools in lock step to OPNFV releases was reasonable for the 
early releases but we saw first hand how it became more and more difficult to 
keep this going as we get more tools/projects and more dependencies between 
projects – and now more users of these projects. As a matter of fact, functest 
is the first to break ranks with the way they are planning to manage their 
version tags for euphrates. I feel like functest will not even really use the 
official euphrates image (the one tagged with “5.0.0” or now “opnfv-5.0.0”) 
because it is just too static/slow-paced. Instead functest will use a “stable” 
or “euphrates” tagged image (from discussion with Cedric and Morgan). Functest 
is used outside of OPNFV labs so clearly they need it versioned properly 
outside of the OPNFV release cycle.
I’m in the same situation with NFVbench, which is already used outside of OPNFV 
labs.

Having said that, the sky is not falling on us because these are actually good 
problems to have and shows industry adoption of OPNFV projects. But we need to 
adjust the way projects are versioned, from a best effort ad-hoc basis to a 
more focused/streamlined one.

More inline on NFVbench…



From: "morgan.richo...@orange.com" 

Date: Tuesday, October 10, 2017 at 9:25 AM
To: "Frank Brockners (fbrockne)" 
, Sofia Wallin 

Cc: Fatih Degirmenci 
, Jose 
Lausuch , "Alec Hothan 
(ahothan)" , 'Brandon Wick' 

Subject: Re: Releasing OPNFV tools in Euphrates

design is done by LF design team
they create icons for the projects and create the global image

the testing catalog page provides interactivity on the image to display the 
different test cases
it is based on the cases descriptions created in the test databases
http://testresults.opnfv.org/test/api/v1/projects/yardstick/cases
http://testresults.opnfv.org/test/api/v1/projects/vsperf/cases
changing the image => change the processing for the roll over, onclick, ...

in a first step, regarding the time frame, we could

1) change the figure in the doc (static)
 => need LF update @Brandon possible to get visual for NFVBench and include it 
on the main picture?
as far as I understand it is not connected to CI, Test API, ..so it should be 
somewhere in the Performance Testing box but without connection with Test API 
or Yardstick


[Alec] I did read emails sent by Morgan regarding that testing landing page but 
was not sure how 

[opnfv-tech-discuss] [xci] xci - aio installation failed on a ubuntu 16.04 VM

[Srikanth Vavilapalli]

Hi

I am trying to run XCI inside a ubuntu 16.04 VM and in the mid-way the script 
stopped with the following error (The log is available at 
https://hastebin.com/maqepiwoyi.md). Can any one plz help me to resolve this 
issue? The environment I have is a vagrant VM with ubuntu 16.04 loaded.

TASK [ironic-inspect-node : Sending dnsmasq HUP] ***
skipping: [opnfv]

TASK [ironic-inspect-node : Execute node introspection - noauth_mode] **
fatal: [opnfv]: FAILED! => {"changed": false, "failed": true, "msg": 
"Inspection of node 93494378-56ee-5e22-b6f0-e3be3a9ebdf1 failed, last error: 
timeout reached while inspecting the node"}

NO MORE HOSTS LEFT *
to retry, use: --limit 
@/tmp/.xci-deploy-env/bifrost/playbooks/opnfv-virtual.retry

PLAY RECAP *
127.0.0.1  : ok=127  changed=78   unreachable=0failed=0
opnfv  : ok=6changed=1unreachable=0failed=1
Making logs directory and collecting logs.


Thanks
Srikanth

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

[opnfv-tech-discuss] [dovetail] Weekly meeting agenda 10/13

[Wenjing Chu]

Hi Dovetailers

For this week, we will focus on beta testing:


-Tutorial : hands on process going through CVP testing (Eddie Arrage). 
This will take up most of the time, if not all.

-Jira scrub of open issues, if we have time.

-If time permits, we may start on Plugfest and next release topics.

Anyone participating in Beta testing or interested in learning, please attend 
the tutorial.

Regards
Wenjing

___
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] Intent to Participate in "F" Release

[David McBride]

Reminder...

I'm still waiting to hear from several projects
.
Please send your intent to participate statements to the TSC mailing list.
Thanks.

David

On Mon, Oct 2, 2017 at 8:19 AM, David McBride 
wrote:

> Team,
>
> Today marks the opening of the intent-to-participate window for the "F"
> release (i.e. MS0).  Please find the procedure here
> .
> The window closes as of MS1 on Nov 3.
>
> Also, please remember that if you are planning a new project for the "F"
> release, you have two weeks to submit your proposal to the TSC and still
> have time to be approved and to join the release before the
> intent-to-participate window closes.
>
> Let me know if you have questions.  Thanks.
>
> David
>
> --
> *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
___
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

[David McBride]

Alex - thanks for the update. - D

On Sun, Oct 8, 2017 at 2:59 AM, Alexandru Avadanii <
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] *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> 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: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org

[opnfv-tech-discuss] Cancelled: Weekly Technical Discussion #102 @ Thursday, 12 October 2017

[HU, BIN]

OCT


12









"Weekly Technical Discussion #102" has been cancelled









When

   



Thursday, 12 October 2017
01:00 PM to 02:00 PM 
 (GMT) Greenwich Mean Time - Dublin / Edinburgh / Lisbon / London 









 Where



+1 (312) 757-3126 / Access Code: 819-733-085




   

Message



https://global.gotomeeting.com/join/819733085
+1 (312) 757-3126 / Access Code: 819-733-085

Hello community:

This is our 102nd  weekly technical discussion at 6am PDT / 9am EDT Thursday October 12th, 2017, which is 13:00 UTC.

We will discuss the collected feedback regarding:
-   Hardware Requirements in OPNFV and Sustainable Way to Evolve
-   Improvements on Pharos Specification

All lab owners and Pharos owner(s), please join and participate in the discussion.

You can find your local time here http://www.timeanddate.com/worldclock/fixedtime.html?msg=OPNFV-Technical-Discussion=20171012T13=1.

Please refer to https://wiki.opnfv.org/display/PROJ/Weekly+Technical+Discussion for details of dialing logistics and tentative agenda.

Please let me know if you want to add anything to agenda for discussion in the community.

For your convenience:
-   GoTo Meeting: https://global.gotomeeting.com/join/819733085
-   You can also dial in using your phone:
o   United States (Long distance): +1 (312) 757-3126 / Access Code: 819-733-085
o   More phone numbers: https://global.gotomeeting.com/819733085/numbersdisplay.html

Thanks
Bin







 

   





 This event invitation was sent from   Yahoo Calendar






invite.ics
Description: application/ics
BEGIN:VCALENDAR
PRODID://Yahoo//Calendar//EN
VERSION:2.0
METHOD:CANCEL
BEGIN:VEVENT
SUMMARY:Weekly Technical Discussion #102
DESCRIPTION:https://global.gotomeeting.com/join/819733085\n+1 (312) 757-312
 6 / Access Code: 819-733-085\n\nHello community:\n\nThis is our 102nd  wee
 kly technical discussion at 6am PDT / 9am EDT Thursday October 12th\, 2017
 \, which is 13:00 UTC.\n\nWe will discuss the collected feedback regarding:\n-   Hardware 
 Requirements in OPNFV and Sustainable Way to Evolve\n-   Improvements 
 on Pharos Specification\n\nAll lab owners and Pharos owner(s)\, please joi
 n and participate in the discussion.\n\nYou can find your local time here 
 http://www.timeanddate.com/worldclock/fixedtime.html?msg=OPNFV-Technical-D
 iscussion=20171012T13=1.\n\nPlease refer to https://wiki.opnfv.org/
 display/PROJ/Weekly+Technical+Discussion for details of dialing logistics 
 and tentative agenda.\n\nPlease let me know if you want to add anything to
  agenda for discussion in the community.\n\nFor your convenience:\n-  
  GoTo Meeting: https://global.gotomeeting.com/join/819733085\n-   You 
 can also dial in using your phone:\no   United States (Long distance):
  +1 (312) 757-3126 / Access Code: 819-733-085\no   More phone numbers:
  https://global.gotomeeting.com/819733085/numbersdisplay.html\n\nThanks\nB
 in\n\n\n
CLASS:PUBLIC
DTSTART;TZID=Europe/London:20171012T14
DTEND;TZID=Europe/London:20171012T15
LOCATION: +1 (312) 757-3126 / Access Code: 819-733-085
PRIORITY:0
SEQUENCE:0
STATUS:CONFIRMED
UID:04008200E00074C5B7101A82E0083072A184B741D301000
 01000AB8938198CFD4047A7309D6EBBC51061

[opnfv-tech-discuss] Canceled: Weekly Technical Discussion #102

[HU, BIN]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="HU, BIN":MAILTO:bh5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Maria Toer
 oe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Henry Four
 ie:MAILTO:louis.fou...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Jose Angel
  Lausuch:MAILTO:jalaus...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Georg Kunz
 :MAILTO:georg.k...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
DESCRIPTION;LANGUAGE=en-US:Hello community\,\n\nWe originally planned to di
 scuss the collected feedback at our weekly technical discussion tomorrow regarding:\n-   H
 ardware Requirements in OPNFV and Sustainable Way to Evolve\n-   Impro
 vements on Pharos Specification\n\nHowever\, the key driver of this topic 
 does not feel that there is enough feedback and information collected at t
 his moment. Thus it is suggested to allow more time to collect feedback in
  order to have a more productive discussion in the future.\n\nBecause ther
 e is no other agenda item for tomorrow\, under this situation\, I suggest 
 that we cancel our weekly technical discussion tomorrow.\n\nThanks\nBin\n\
 nhttps://global.gotomeeting.com/join/819733085\n+1 (312) 757-3126 / Access
  Code: 819-733-085\n\nHello community:\n\nThis is our 102nd  weekly techni
 cal discussion at 6am PDT / 9am EDT Thursday October 12th\, 2017\, which i
 s 13:00 UTC.\n\nWe will discuss the collected feedback regarding:\n-   Hardware Requiremen
 ts in OPNFV and Sustainable Way to Evolve\n-   Improvements on Pharos 
 Specification\n\nAll lab owners and Pharos owner(s)\, please join and part
 icipate in the discussion.\n\nYou can find your local time here http://www
 .timeanddate.com/worldclock/fixedtime.html?msg=OPNFV-Technical-Discussion&
 iso=20171012T13=1.\n\nPlease refer to https://wiki.opnfv.org/display/PR
 OJ/Weekly+Technical+Discussion for details of dialing logistics and tentat
 ive agenda.\n\nPlease let me know if you want to add anything to agenda fo
 r discussion in the community.\n\nFor your convenience:\n-   GoTo Meet
 ing: https://global.gotomeeting.com/join/819733085\n-   You can also d
 ial in using your phone:\no   United States (Long distance): +1 (312) 
 757-3126 / Access Code: 819-733-085\no   More phone numbers: https://g
 lobal.gotomeeting.com/819733085/numbersdisplay.html\n\nThanks\nBin\n\n\n
SUMMARY;LANGUAGE=en-US:Canceled: Weekly Technical Discussion #102
DTSTART;TZID=Pacific Standard Time:20171012T06
DTEND;TZID=Pacific Standard Time:20171012T07
UID:04008200E00074C5B7101A82E0083072A184B741D301000
 01000AB8938198CFD4047A7309D6EBBC51061
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20171011T181612Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:1
LOCATION;LANGUAGE=en-US: +1 (312) 757-3126 / Access Code: 819-733-085
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:520792033
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing installer dependent information in the test tools

[Jose Lausuch]

Hi,

I would vote for having something similar to Yardstick [1] but centralized in 
Releng with an easy python lib that enables functions like SCP things to/from 
the deployed nodes.

For your third point, log collection shouldn’t be done at test case level. It 
should be performed by CI after running the test tools, otherwise you can a 
false negative when running those test on non-OPNFV installers.

Regards,
Jose

[1] 
https://raw.githubusercontent.com/opnfv/yardstick/master/etc/yardstick/nodes/fuel_virtual/pod.yaml
 




> On 11 Oct 2017, at 18:08, Georg Kunz  wrote:
> 
> Hi,
>  
> Just to highlight this, from a Dovetail/CVP perspective, the important aspect 
> is that there are no dependencies on OPNFV-specific resources/lib in order to 
> be able to run test cases against commercial non-OPNFV deployments.
>  
> Having to write an adapter for a particular commercial deployment before you 
> can run Dovetail is obviously not really an option. So, for tests which 
> require SSH/SCP access, we need to think about...
> If the adapter can be parameterized, so that we can make it a configuration 
> option, e.g., specifying login credentials, source and target directories, 
> etc., similarly to Yardstick.
> Reuse what Yardstick is using?
> If the test case be parameterized such that it does not attempt to gather 
> logs if used for certification? (limited use, of course)
> …
>  
> Cheers
> Georg
>  
> From: opnfv-tech-discuss-boun...@lists.opnfv.org 
>  
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org 
> ] On Behalf Of Jose Lausuch
> Sent: Wednesday, October 11, 2017 4:40 PM
> To: Beierl, Mark >
> Cc: opnfv-tech-discuss@lists.opnfv.org 
> 
> Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
> installer dependent information in the test tools
>  
> Hi,
>  
> With regards to Functest, you can run it on any OpenStack deployment as long 
> as you provide a proper RC file and meet the requirements on the jumphost 
> (docker, connectivity to the deployment, …).
>  
> However, in some cases, some test cases from feature projects require SSH 
> access to the deployment and to make things centralized, the deployment 
> handler was created [1]. This is a library that allows users to get the 
> number of nodes from the deployment, functions to SCP things from the nodes 
> and some other utils. The bad part of it is that it only supports Apex, Fuel 
> and OSA for now…  unless someones volunteers to write the other adapters for 
> joid, mcp, compass osa..  This library might be used to extract the desired 
> logs after Functest/Yardstick runs in CI to place them in artifact repo and 
> post-analize. 
>  
> Regards,
> Jose
>  
> [1] https://git.opnfv.org/releng/tree/modules/opnfv/deployment 
> 
>  
>  
>  
>  
> On 11 Oct 2017, at 16:23, Beierl, Mark  > wrote:
>  
> Hello,
>  
> StorPerf very much relies on knowledge of the installer to gather information 
> about the block storage underlay.  For example, the number of Ceph nodes, or 
> even Ceph vs. LVM, is very relevant to the final report.  I also wish there 
> were an installer agnostic method of collecting this information as right now 
> I keep that code in the ci/daily.sh and other scripts.
>  
> With the new releng repository being created, perhaps it is time to start 
> moving some of the installer specific code there?  I also see that being of 
> benefit when adding XCI support, as technically that would be yet another 
> type of installer.
>  
> Regards,
> Mark
>  
> Mark Beierl
> SW System Sr Principal Engineer
> Dell EMC | Office of the CTO
> mobile +1 613 314 8106 
> mark.bei...@dell.com 
>  
> On Oct 11, 2017, at 02:25, xudan (N)  > wrote:
>  
> Hi Srikanth,
>  
> As I know, some Yardstick test cases also need to login nodes. Yardstick uses 
> a file providing all the login information.
> You can refer to 
> https://github.com/opnfv/yardstick/tree/master/etc/yardstick/nodes 
>  which 
> gives some examples.
> Hope this will help you.
>  
> BR
> Dan Xu
>  
> From: Srikanth Vavilapalli [mailto:srikanth.vavilapa...@ericsson.com 
> ] 
> Sent: Wednesday, October 11, 2017 12:28 PM
> To: opnfv-tech-discuss@lists.opnfv.org 
> 
> Cc: Tim Irnich; xudan (N)
> Subject: [functest] [sdnvpn] Proposal for removing installer dependent 
> information in the test tools
>  
> Hi
>  
> I am 

[opnfv-tech-discuss] Propose to cancel our weekly technical discussion tomorrow

[HU, BIN]

Hello community,

We originally planned to discuss the collected 
feedback at our weekly 
technical discussion tomorrow regarding:

-  Hardware Requirements in OPNFV and Sustainable Way to Evolve

-  Improvements on Pharos Specification

However, the key driver of this topic does not feel that there is enough 
feedback and information collected at this moment. Thus it is suggested to 
allow more time to collect feedback in order to have a more productive 
discussion in the future.

Because there is no other agenda item for tomorrow, under this situation, I 
suggest that we cancel our weekly technical discussion tomorrow.

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

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

[Tahhan, Maryam]

+ 1 from me too.
Thanks everyone.

From: MORTON, ALFRED C (AL) [mailto:acmor...@att.com]
Sent: Wednesday, October 11, 2017 5:10 PM
To: Foley, Emma L ; Gherghe, Calin 
; Tahhan, Maryam ; Aaron 
Smith 
Cc: Verrall, Timothy ; Power, Damien 
; Mcmahon, Tony B ; 
opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org; Aaron Smith 

Subject: RE: [barometer] Vote for new barometer PTL

+1, thanks for stepping-up, Aaron

Al

From: Foley, Emma L [mailto:emma.l.fo...@intel.com]
Sent: Wednesday, October 11, 2017 11:30 AM
To: Gherghe, Calin; Tahhan, Maryam; MORTON, ALFRED C (AL); Aaron Smith
Cc: Verrall, Timothy; Power, Damien; Mcmahon, Tony B; 
opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; 
Aaron Smith
Subject: RE: [barometer] Vote for new barometer PTL

+1

Sorry for duplicates, I'll keep this to one thread.


From: Gherghe, Calin
Sent: Wednesday, October 11, 2017 4:25 PM
To: Tahhan, Maryam >; 
'MORTON, ALFRED C (AL)' >; Foley, 
Emma L >; Aaron Smith 
>
Cc: Verrall, Timothy 
>; Power, Damien 
>; Mcmahon, Tony B 
>; 
opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; 
Aaron Smith >
Subject: RE: [barometer] Vote for new barometer PTL

+1

From: Tahhan, Maryam
Sent: Wednesday, October 11, 2017 8:21 AM
To: 'MORTON, ALFRED C (AL)' >; Foley, 
Emma L >; Gherghe, Calin 
>; Aaron Smith 
>
Cc: Verrall, Timothy 
>; Power, Damien 
>; Mcmahon, Tony B 
>; Tahhan, Maryam 
>; 
opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; 
Aaron Smith >
Subject: [barometer] Vote for new barometer PTL

Barometer committers ...

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

Thanks!

Maryam


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tahhan, Maryam
Sent: Monday, September 25, 2017 11:30 AM
To: opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; 
Aaron Smith >
Cc: Verrall, Timothy 
>; Power, Damien 
>; Mcmahon, Tony B 
>
Subject: [opnfv-tech-discuss] [barometer] Stepping down as barometer PTL post E 
release.


Hi folks,



After much consideration, I have decided to step down as the PTL for barometer 
after the E release. I have really enjoyed my time as the PTL and the support 
of a great team. I and the team would like to remain involved/stay on as a 
project committers and contributors. But I think it's the right time to give 
someone else the chance to lead a great project. With that, I would like to 
nominate Aaron Smith as the next barometer PTL.



Thank you for the experience and great journey :)

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

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

[MORTON, ALFRED C (AL)]

+1, thanks for stepping-up, Aaron

Al

From: Foley, Emma L [mailto:emma.l.fo...@intel.com]
Sent: Wednesday, October 11, 2017 11:30 AM
To: Gherghe, Calin; Tahhan, Maryam; MORTON, ALFRED C (AL); Aaron Smith
Cc: Verrall, Timothy; Power, Damien; Mcmahon, Tony B; 
opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org; Aaron Smith
Subject: RE: [barometer] Vote for new barometer PTL

+1

Sorry for duplicates, I'll keep this to one thread.


From: Gherghe, Calin
Sent: Wednesday, October 11, 2017 4:25 PM
To: Tahhan, Maryam >; 
'MORTON, ALFRED C (AL)' >; Foley, 
Emma L >; Aaron Smith 
>
Cc: Verrall, Timothy 
>; Power, Damien 
>; Mcmahon, Tony B 
>; 
opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; 
Aaron Smith >
Subject: RE: [barometer] Vote for new barometer PTL

+1

From: Tahhan, Maryam
Sent: Wednesday, October 11, 2017 8:21 AM
To: 'MORTON, ALFRED C (AL)' >; Foley, 
Emma L >; Gherghe, Calin 
>; Aaron Smith 
>
Cc: Verrall, Timothy 
>; Power, Damien 
>; Mcmahon, Tony B 
>; Tahhan, Maryam 
>; 
opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; 
Aaron Smith >
Subject: [barometer] Vote for new barometer PTL

Barometer committers ...

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

Thanks!

Maryam


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tahhan, Maryam
Sent: Monday, September 25, 2017 11:30 AM
To: opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; 
Aaron Smith >
Cc: Verrall, Timothy 
>; Power, Damien 
>; Mcmahon, Tony B 
>
Subject: [opnfv-tech-discuss] [barometer] Stepping down as barometer PTL post E 
release.


Hi folks,



After much consideration, I have decided to step down as the PTL for barometer 
after the E release. I have really enjoyed my time as the PTL and the support 
of a great team. I and the team would like to remain involved/stay on as a 
project committers and contributors. But I think it's the right time to give 
someone else the chance to lead a great project. With that, I would like to 
nominate Aaron Smith as the next barometer PTL.



Thank you for the experience and great journey :)

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

Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing installer dependent information in the test tools

[Georg Kunz]

Hi,

Just to highlight this, from a Dovetail/CVP perspective, the important aspect 
is that there are no dependencies on OPNFV-specific resources/lib in order to 
be able to run test cases against commercial non-OPNFV deployments.

Having to write an adapter for a particular commercial deployment before you 
can run Dovetail is obviously not really an option. So, for tests which require 
SSH/SCP access, we need to think about...

  *   If the adapter can be parameterized, so that we can make it a 
configuration option, e.g., specifying login credentials, source and target 
directories, etc., similarly to Yardstick.
  *   Reuse what Yardstick is using?
  *   If the test case be parameterized such that it does not attempt to gather 
logs if used for certification? (limited use, of course)
  *   …

Cheers
Georg

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jose Lausuch
Sent: Wednesday, October 11, 2017 4:40 PM
To: Beierl, Mark 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

Hi,

With regards to Functest, you can run it on any OpenStack deployment as long as 
you provide a proper RC file and meet the requirements on the jumphost (docker, 
connectivity to the deployment, …).

However, in some cases, some test cases from feature projects require SSH 
access to the deployment and to make things centralized, the deployment handler 
was created [1]. This is a library that allows users to get the number of nodes 
from the deployment, functions to SCP things from the nodes and some other 
utils. The bad part of it is that it only supports Apex, Fuel and OSA for now…  
unless someones volunteers to write the other adapters for joid, mcp, compass 
osa..  This library might be used to extract the desired logs after 
Functest/Yardstick runs in CI to place them in artifact repo and post-analize.

Regards,
Jose

[1] https://git.opnfv.org/releng/tree/modules/opnfv/deployment




On 11 Oct 2017, at 16:23, Beierl, Mark 
> wrote:

Hello,

StorPerf very much relies on knowledge of the installer to gather information 
about the block storage underlay.  For example, the number of Ceph nodes, or 
even Ceph vs. LVM, is very relevant to the final report.  I also wish there 
were an installer agnostic method of collecting this information as right now I 
keep that code in the ci/daily.sh and other scripts.

With the new releng repository being created, perhaps it is time to start 
moving some of the installer specific code there?  I also see that being of 
benefit when adding XCI support, as technically that would be yet another type 
of installer.

Regards,
Mark

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

On Oct 11, 2017, at 02:25, xudan (N) 
> wrote:

Hi Srikanth,

As I know, some Yardstick test cases also need to login nodes. Yardstick uses a 
file providing all the login information.
You can refer to 
https://github.com/opnfv/yardstick/tree/master/etc/yardstick/nodes which gives 
some examples.
Hope this will help you.

BR
Dan Xu

From: Srikanth Vavilapalli [mailto:srikanth.vavilapa...@ericsson.com]
Sent: Wednesday, October 11, 2017 12:28 PM
To: 
opnfv-tech-discuss@lists.opnfv.org
Cc: Tim Irnich; xudan (N)
Subject: [functest] [sdnvpn] Proposal for removing installer dependent 
information in the test tools

Hi

I am looking into Jira ticket 
“SDNVPN-181: Function "gather_logs" 
restricts to Apex and Fuel”, which raises concerns on having installer 
dependent logic in the sdnvpn repo. The issue is, at the end of the sdnvpn test 
execution, we are invoking gather_logs() utility which internally tries to 
gather the information about all the OpenStack nodes based on the configured 
INSTALLER_TYPE in order to run the fetch_logs.sh script on the target OpenStack 
nodes 
(https://gerrit.opnfv.org/gerrit/gitweb?p=sdnvpn.git;a=blob;f=sdnvpn/lib/utils.py;h=ad0714ea9dd40ee8305cd17e42695f0176e88328;hb=HEAD#l215)

So, the jira ticket proposes to accept all the needed information about the 
OpenStack controllers, compute nodes and the associated username, keys…etc. in 
a file format such that these tests can also be run on OPNFV based commercial 
products deployed with their custom deployment tools.

So in general, in the test tools, is there any need to have awareness of what 
installers being used when we all care about the target OpenStack node IPs, 
associated attributes and jumphost IP (in some cases)?

I would like to get the community opinion here. Appreciate your inputs.

Thanks
Srikanth

___

[opnfv-tech-discuss] StorPerf talk at OpenStack Days Canada

[Beierl, Mark]

Hello,

Probably not a lot of folks will be in Ottawa, Canada on the 19, but if you 
are, I have a talk on OPNFV StorPerf at the OpenStack Days Canada conference at 
2:10.

https://www.openstackcanada.com/schedule/

Regards,
Mark

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

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

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

[Gherghe, Calin]

+1

From: Tahhan, Maryam
Sent: Wednesday, October 11, 2017 8:21 AM
To: 'MORTON, ALFRED C (AL)' ; Foley, Emma L 
; Gherghe, Calin ; Aaron Smith 

Cc: Verrall, Timothy ; Power, Damien 
; Mcmahon, Tony B ; Tahhan, 
Maryam ; opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; Aaron Smith 
Subject: [barometer] Vote for new barometer PTL

Barometer committers ...

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

Thanks!

Maryam


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tahhan, Maryam
Sent: Monday, September 25, 2017 11:30 AM
To: opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; 
Aaron Smith >
Cc: Verrall, Timothy 
>; Power, Damien 
>; Mcmahon, Tony B 
>
Subject: [opnfv-tech-discuss] [barometer] Stepping down as barometer PTL post E 
release.


Hi folks,



After much consideration, I have decided to step down as the PTL for barometer 
after the E release. I have really enjoyed my time as the PTL and the support 
of a great team. I and the team would like to remain involved/stay on as a 
project committers and contributors. But I think it's the right time to give 
someone else the chance to lead a great project. With that, I would like to 
nominate Aaron Smith as the next barometer PTL.



Thank you for the experience and great journey :)

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

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

[Foley, Emma L]

+1

Sorry for duplicates, I'll keep this to one thread.


From: Gherghe, Calin
Sent: Wednesday, October 11, 2017 4:25 PM
To: Tahhan, Maryam ; 'MORTON, ALFRED C (AL)' 
; Foley, Emma L ; Aaron Smith 

Cc: Verrall, Timothy ; Power, Damien 
; Mcmahon, Tony B ; 
opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org; Aaron Smith 

Subject: RE: [barometer] Vote for new barometer PTL

+1

From: Tahhan, Maryam
Sent: Wednesday, October 11, 2017 8:21 AM
To: 'MORTON, ALFRED C (AL)' >; Foley, 
Emma L >; Gherghe, Calin 
>; Aaron Smith 
>
Cc: Verrall, Timothy 
>; Power, Damien 
>; Mcmahon, Tony B 
>; Tahhan, Maryam 
>; 
opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; 
Aaron Smith >
Subject: [barometer] Vote for new barometer PTL

Barometer committers ...

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

Thanks!

Maryam


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tahhan, Maryam
Sent: Monday, September 25, 2017 11:30 AM
To: opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org; 
Aaron Smith >
Cc: Verrall, Timothy 
>; Power, Damien 
>; Mcmahon, Tony B 
>
Subject: [opnfv-tech-discuss] [barometer] Stepping down as barometer PTL post E 
release.


Hi folks,



After much consideration, I have decided to step down as the PTL for barometer 
after the E release. I have really enjoyed my time as the PTL and the support 
of a great team. I and the team would like to remain involved/stay on as a 
project committers and contributors. But I think it's the right time to give 
someone else the chance to lead a great project. With that, I would like to 
nominate Aaron Smith as the next barometer PTL.



Thank you for the experience and great journey :)

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

[opnfv-tech-discuss] Canceled: OPNFV Promise meeting

[Kunzmann, Gerald]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Csatari, G
 ergely (Nokia - HU/Budapest)":MAILTO:gergely.csat...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Maria Toer
 oe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Charles Ha
 le:MAILTO:charlie.h...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Prashant S
 unkari:MAILTO:p.sunk...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Juraj Link
 es -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco):MAILTO:jlin...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ahmed Elbo
 rnou (amaged):MAILTO:ama...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Marco Varl
 ese:MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DRUTA, DAN"
 :MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Piyush Sar
 wal:MAILTO:psar...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bharat Bhu
 shan:MAILTO:bharat.bhus...@nxp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Hesham ElB
 akoury:MAILTO:hesham.elbako...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Rabi, Abde
 l":MAILTO:abdel.r...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="MORTON, AL
 FRED C (AL)":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Nagananda 
 Chumbalkar:MAILTO:nchumbal...@lenovo.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Pierre Lyn
 ch:MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Soumya Sha
 nkar Sardar:MAILTO:soumya.shankar.sar...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Frattura, 
 David":MAILTO:david.fratt...@dell.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Aron Wahl:
 MAILTO:a.w...@f5.com
DESCRIPTION;LANGUAGE=en-US:Dear all\,\n\nLet me propose to cancel this week
 ’s meeting as I will be traveling tomorrow.\nIf you have any topics\, pl
 ease start a thread on the mailing list.\n\nBest regards\,\nGerald\n\n
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Promise meeting
DTSTART;TZID=UTC:20171012T11
DTEND;TZID=UTC:20171012T12
UID:04008200E00074C5B7101A82E00810B4E5E6E9A6D201000
 010007CA1B4BED81343459CFC20419236D853
RECURRENCE-ID;TZID=UTC:20171012T11
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20171011T152706Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:10
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:10
X-MICROSOFT-CDO-OWNERAPPTID:-1684326431
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [barometer] Vote for new barometer PTL

[Tahhan, Maryam]

Barometer committers ...

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

Thanks!

Maryam


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tahhan, Maryam
Sent: Monday, September 25, 2017 11:30 AM
To: opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org; Aaron Smith 

Cc: Verrall, Timothy ; Power, Damien 
; Mcmahon, Tony B 
Subject: [opnfv-tech-discuss] [barometer] Stepping down as barometer PTL post E 
release.


Hi folks,



After much consideration, I have decided to step down as the PTL for barometer 
after the E release. I have really enjoyed my time as the PTL and the support 
of a great team. I and the team would like to remain involved/stay on as a 
project committers and contributors. But I think it's the right time to give 
someone else the chance to lead a great project. With that, I would like to 
nominate Aaron Smith as the next barometer PTL.



Thank you for the experience and great journey :)

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

[opnfv-tech-discuss] Swift Support

[Beierl, Mark]

Hello,

I was wondering what installers or use cases we have in OPNFV for Swift object 
storage.  One of the planning activities for StorPerf Fraser would be Swift 
profiling, but I am not sure how useful that is to the community.

Regards,
Mark

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

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

[opnfv-tech-discuss] [StorPerf] Weekly Meeting

[Beierl, Mark]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Beierl, Mark":MAILTO:mark.bei...@emc.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Taseer Ahm
 ed:MAILTO:tasee...@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=s.pisarski
 @cablelabs.com:MAILTO:s.pisar...@cablelabs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:When: Thursday\, October 12\, 2017 11:00 AM-12:0
 0 PM. (UTC-05:00) Eastern Time (US & Canada)\nWhere: https://global.gotome
 eting.com/join/819733085\n\n*~*~*~*~*~*~*~*~*~*\n\nHello\,\n\nThis is a sp
 ecial\, one time change to StorPerf so we can sync up with  Steven Pisarsk
 i of SNAPS-OO and how StorPerf can leverage it.\n\nhttps://global.gotomeet
 ing.com/join/819733085\n\nhttps://wiki.opnfv.org/display/meetings/Storperf
 +Team+Weekly+Meeting\n
SUMMARY;LANGUAGE=en-US:[StorPerf] Weekly Meeting
DTSTART;TZID=Eastern Standard Time:20171012T11
DTEND;TZID=Eastern Standard Time:20171012T12
UID:F813D04F-8EEC-49A9-BAA6-FA12447ABCA3
RECURRENCE-ID;TZID=Eastern Standard Time:20171012T10
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171011T141221Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:2
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/819733085
X-MICROSOFT-CDO-APPT-SEQUENCE:2
X-MICROSOFT-CDO-OWNERAPPTID:2115579989
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT5M
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[Christian Trautman]

+1 

- Original Message -

From: "ALFRED C MORTON (AL)"  
To: "Trevor Cooper" , 
opnfv-tech-discuss@lists.opnfv.org 
Cc: "MartinX Klozik" , "Bill Michalowski" 
, "Christian Trautman" , "Sridhar 
Rao" , "Maryam Tahhan"  
Sent: Wednesday, October 11, 2017 8:48:29 AM 
Subject: RE: [VSPERF] Vote for new VSPERF PTL 



+1, thanks for stepping-up, Sridhar! 

Al 




From: Cooper, Trevor [mailto:trevor.coo...@intel.com] 
Sent: Tuesday, October 10, 2017 7:11 PM 
To: opnfv-tech-discuss@lists.opnfv.org 
Cc: MORTON, ALFRED C (AL); Klozik, MartinX; 'Bill Michalowski'; 'Christian 
Trautman'; Rao, Sridhar; Tahhan, Maryam; Cooper, Trevor 
Subject: [VSPERF] Vote for new VSPERF PTL 
Importance: High 




VSPERF committers … 



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



Thanks! 



Trevor 










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




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



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



/Trevor 



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

Re: [opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 11 Oct 2017

[MORTON, ALFRED C (AL)]

I can chair the meeting today, Trevor.

Beyond the JIRA clean-up, Trevor notes a key action held
over for today: to review the FDIO CSIT tests:
  
https://docs.fd.io/csit/rls1707/report/vpp_performance_tests/index.html#
and then we can make a comparison with our CI results
https://wiki.opnfv.org/display/vsperf/VSPERF+CI+Results

Al

From: Cooper, Trevor [mailto:trevor.coo...@intel.com]
Sent: Tuesday, October 10, 2017 7:54 PM
To: 'opnfv-tech-discuss@lists.opnfv.org'
Cc: MORTON, ALFRED C (AL); 'Sridhar Rao'; Klozik, MartinX; 'Bill Michalowski'; 
'Christian Trautman'; 'Mars Toktonaliev (Nokia - US/Irving)'
Subject: [vsperf] Agenda for VSPERF weekly meeting - 11 Oct 2017


I have a conflict tomorrow and will not be able to attend ... is there a 
volunteer to chair the meeting?



A few notes ...

-  I did notify the TSC of VSPERF's intent to participate in Fraser.

-  I haven't had a chance yet to work on the second sand-box in POD 12

-  Please check all Jira tickets assigned to you for Euphrates ... 
either close them or update fix version to future release



Some proposed agenda topics ...

-  Euphrates Release milestones (The updated release schedule is here 
https://wiki.opnfv.org/display/SWREL/Euphrates?preview=/8689511/12391892/OPNFV%20Release%20%2522Euphrates%2522%20r11.pdf)

o   MS10 (10/19) - JIRA issues closed or deferred

o   MS11 (10/20) - Release Euphrates 5.0

-  Status of 
https://gerrit.opnfv.org/gerrit/#/c/44247/
 Add multistream support to T-Rex

-  Status of tuning CI configuration (Martin)
-  Discuss VPP test cases and results in CSIT report ... try to 
calibrate against VVSPERF CI results 
https://docs.fd.io/csit/rls1707/report/vpp_performance_tests/index.html#



Meeting minutes
-  Ww40 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-10-04-14.49.html
-  ww39 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-09-27-15.01.html

-  ww38 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-09-20-15.05.html

-  ww37 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-09-13-14.53.html



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

IRC: freenode 

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

[MORTON, ALFRED C (AL)]

+1, thanks for stepping-up, Sridhar!
Al

From: Cooper, Trevor [mailto:trevor.coo...@intel.com]
Sent: Tuesday, October 10, 2017 7:11 PM
To: opnfv-tech-discuss@lists.opnfv.org
Cc: MORTON, ALFRED C (AL); Klozik, MartinX; 'Bill Michalowski'; 'Christian 
Trautman'; Rao, Sridhar; Tahhan, Maryam; Cooper, Trevor
Subject: [VSPERF] Vote for new VSPERF PTL
Importance: High

VSPERF committers ...

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

Thanks!

Trevor




From: Cooper, Trevor
Sent: Monday, October 02, 2017 8:59 PM
To: 
opnfv-tech-discuss@lists.opnfv.org; 
opnfv-...@lists.opnfv.org
Cc: MORTON, ALFRED C (AL) >; Klozik, 
MartinX >; 'Bill 
Michalowski' >; 'Christian 
Trautman' >; 'Mars Toktonaliev 
(Nokia - US/Irving)' 
>; Raymond Paik 
>; 
dmcbr...@linuxfoundation.org; 'Rao, 
Sridhar' >
Subject: [VSPERF] New PTL for VSPERF after E release

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

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

/Trevor

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

[opnfv-tech-discuss] [Compass] Minutes for Weekly Call 20171011

[Chigang (Justin)]

Hi,

Agenda:

l  Intern welcome

l  Committer list update

l  K8S introduction and documentation review

Minutes:

l  Lucas Wang make a brief introduction, who is a graduate from Shanghai 
Jiaotong University, focus on OpenDaylight AAA and learn OPNFV from Developer 
Getting Started 
first.

l  Committer list update. remove inactive committer according to Committer 
Removal. Patch 
link. Justin suggest to nominate 
new committer Yifei Xue and HU 
Xinhui, and will get feedback from 
committer who misses the meeting.

l  HU Xinhui make an introduction 
about K8s integration, create a wiki Containerized Compass for K8S 
Integration
 to introduce how to deployment K8s via Compass, explain why to choice Calico 
as a default network plugin.

l  Discuss F release plan but time running out. put it in next meeting.

Actions:
· wutianweihelps to provide 
a new vpn to HU Xinhui to improve his 
GTM audio.

MeetBot Minutes:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-compass4nfv/2017/opnfv-compass4nfv.2017-10-11-08.04.log.html

Regards
Justin

华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]
手　　机：13472817001
电子邮件：chig...@huawei.com

 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e-mail and its attachments contain confidential information from HUAWEI, 
which
is intended only for the person or entity whose address is listed above. Any 
use of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender by
phone or email immediately and delete it!

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

[opnfv-tech-discuss] [releng-xci] My status on CentOS support this week

[Tapio Tallgren]

Hi,

I will be traveling during the weekly XCI IRC meeting, so here is a
short summary of my status wrt supporting CentOS.

TL;DR: Still does not work

I have now all VMs (noha, so opnfv, controller00, compute00, compute01)
up and running and networking is working between them, both the external
and internal. LXC containers are running but I am now working on getting
the container networking working. 

I need to understand openstack-ansible-lxc_hosts better. 

-Tapio


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

Re: [opnfv-tech-discuss] Releasing OPNFV tools in Euphrates

[morgan.richomme]

Agree to extend to mailing list :)

just to summarize, we started the discussion on doc for calipso for 
Euphrates, it triggered discussions more general topics including

- a topic on how to include NFVBench in Euphrates (Operation/testing)
- a discussion on OPNFV release / tooling release decorrelation

we can add a slot for this during the next weekly meeting 
https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting 
(maybe a bit late regarding the release date)
I was not able to attend the APAC slot this morning, according to IRC, I 
was not the only one...


/Morgan

On 10/10/2017 21:02, Alec Hothan (ahothan) wrote:


I wish this discussion was brought up on the tech-discuss mailing list ;-)

I had exactly the same questions than Frank at the very bottom and 
asked similar questions to David this morning on the release packaging.


Heather is also right on target to feel like tools should be 
independent of the platform release! This is clearly one of the 
benefits of having an independent versioning for projects vs release 
which I have been trying to push with the release tagging discussion.


For me there is absolutely no question that testing tools developed in 
OPNFV will be used outside of OPNFV release cycle and potentially on 
NFVi platforms that are not even in OPNFV labs and this clearly 
mandates an independent versioning for each tool project.


Trying to version tools in lock step to OPNFV releases was reasonable 
for the early releases but we saw first hand how it became more and 
more difficult to keep this going as we get more tools/projects and 
more dependencies between projects – and now more users of these 
projects. As a matter of fact, functest is the first to break ranks 
with the way they are planning to manage their version tags for 
euphrates. I feel like functest will not even really use the official 
euphrates image (the one tagged with “5.0.0” or now “opnfv-5.0.0”) 
because it is just too static/slow-paced. Instead functest will use a 
“stable” or “euphrates” tagged image (from discussion with Cedric and 
Morgan). Functest is used outside of OPNFV labs so clearly they need 
it versioned properly outside of the OPNFV release cycle.


I’m in the same situation with NFVbench, which is already used outside 
of OPNFV labs.


Having said that, the sky is not falling on us because these are 
actually good problems to have and shows industry adoption of OPNFV 
projects. But we need to adjust the way projects are versioned, from a 
best effort ad-hoc basis to a more focused/streamlined one.


More inline on NFVbench…

*From: *"morgan.richo...@orange.com" 
*Date: *Tuesday, October 10, 2017 at 9:25 AM
*To: *"Frank Brockners (fbrockne)" , Sofia Wallin 

*Cc: *Fatih Degirmenci , Jose Lausuch 
, "Alec Hothan (ahothan)" , 
'Brandon Wick' 

*Subject: *Re: Releasing OPNFV tools in Euphrates

design is done by LF design team
they create icons for the projects and create the global image

the testing catalog page provides interactivity on the image to 
display the different test cases

it is based on the cases descriptions created in the test databases
http://testresults.opnfv.org/test/api/v1/projects/yardstick/cases
http://testresults.opnfv.org/test/api/v1/projects/vsperf/cases
changing the image => change the processing for the roll over, 
onclick, ...


in a first step, regarding the time frame, we could

1) change the figure in the doc (static)
 => need LF update @Brandon possible to get visual for NFVBench and 
include it on the main picture?
as far as I understand it is not connected to CI, Test API, ..so it 
should be somewhere in the Performance Testing box but without 
connection with Test API or Yardstick


[Alec] I did read emails sent by Morgan regarding that testing landing 
page but was not sure how to position NFVbench.


NFVbench also covers the operational side because it is designed from 
the get go to run in production. Today there is no solution for doing 
data plane performance measurement and monitoring on a production 
cloud because it is just too costly and too complex to do with 
traditional benchmarking methods (HW traffic generators in every cloud 
is just not reasonable). NFVbench fills that gap for practically no 
cost (you just need a NIC card - a tiny fraction of the cost of a pod).


So yes it can be used as a testing tool (to test and measure data 
plane performance) but is also and foremost a tool for production. To 
make it simpler in euphrates we can just put it in the testing group 
for now. To make it even simpler, perhaps we should just add 
“NFVbench” next to vsperf in the diagram since they both tackle the 
data plane performance? No need to add a new logo, we can worry about 
a better arrangement for Fraser



2) reference NFVBench in the testing wiki page 

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

[Gaoliang (kubi)]

Hi Venkat,

Thanks for your question.

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

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

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

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

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







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




Regarding to Question 2



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








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

Hope that would help for you understand yardstick framework.

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

Regards,

Kubi

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

Hi Jack/Kubi/Kristian and yardstick developers,

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

Appreciate your help.

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

Re: [opnfv-tech-discuss] [functest] Alpine for arch

[Cristina Pauna]

Hi Cedric,

Which E are you refering to in this email? The one with deadline on 15th 
December?

Cristina

From: cedric.olliv...@orange.com [mailto:cedric.olliv...@orange.com]
Sent: Wednesday, October 11, 2017 7:24 AM
To: RICHOMME Morgan IMT/OLN ; jalaus...@suse.com; 
Delia Popescu ; Alexandru Avadanii 
; Cristina Pauna ; 
wangwu...@huawei.com
Cc: opnfv-tech-discuss 
Subject: Re: [functest] Alpine for arch

Hello,

I quickly tested to build aarch64 Functest images via Docker automated builds 
what is impossible (several prerequisites are unmet). I precise the first 
published images were built locally.

I'm thinking about an alternative way which will be too much disruptive for E 
release. Again it will be suitable for my own repositories. But releng should 
have been the target to build all Docker images (I bet it won't be ready for 
E). Today's releng can't meet functest prerequisites about Docker.

I will inform as soon as my own repositories are ready.

Cédric

 Cristina Pauna a écrit 
Hi,

There has been a lot of confusion and changes around this topic and I want to 
clear things up going forward, so we do not waste any of our time.
What I understand from all the disparate discussions around this topic is:

1.   We will not do alpine for E0 release on arm, we are targeting E1/E2

2.   For the Functest-core image we will have 1 Dockerfile for x86, and a 
patch for arm that overrides this Dockerfile; from this file we will create one 
Functest-core image and the architecture will be mentioned in its tag

3.   The subsequent images (Functest-healthcheck, Functest-smoke, etc) will 
be based on the previously built Functest-core image. We will do a manifest to 
choose the correct Functest-core image based on its tag. These dependent  
images will also have its arch in the tag.

4.   The problem we are facing now is how to make sure that for 1 build, 
the Functest-core image always get built before the other ones. For x86 that is 
now done with a workaround directly in dockerhub. The target is to do it with 
Jenkins jobs builders, considering image dependencies.

Is this the approach we are all agreeing on?

Thanks,
Cristina

_



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

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

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

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



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

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

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

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

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

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

[vvenkat]

Hi Jack/Kubi/Kristian and yardstick developers,

 

It would be grateful if you could please let me know on details to explore
on the test cases for a specific test case say TC002
(https://github.com/opnfv/yardstick/blob/stable/danube/tests/opnfv/test_case
s/opnfv_yardstick_tc002.yaml)?

I understand the parameters but I would like to understand how yardstick
executes like what are the parameters for two VMs, how many vCPUs, how much
memory ?

In summary, would like to understand the exact execution details/internal
commands of the test case, please point me to the source details in the
yardstick repo.

 

Appreciate your help.

 

Thanks

-Venkat

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

[opnfv-tech-discuss] SFC weekly call cancelled

[Manuel Buil]

Hey,

I have an important meeting today at the same time, so I need to cancel
this week's meeting. I think there is not much to update since all of
us are working on fixing bugs for ODL, OVS or tacker. If there is
something which cannot wait until next week, let's try to discuss it
over the mailing list.

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