Re: [opnfv-tech-discuss] [release] volunteers needed for milestone exception review process

[Tallgren, Tapio (Nokia - FI/Espoo)]

Hi,

I can continue as a reviewer.

-Tapio


From: David McBride <dmcbr...@linuxfoundation.org>
Sent: Monday, May 21, 2018 8:59:54 PM
To: TECH-DISCUSS OPNFV; opnfv-project-leads
Cc: Rossella Sblendido; Tallgren, Tapio (Nokia - FI/Espoo); Julien; Tianhongbo; 
Ulrich Kleber; tim.irn...@ericsson.com; Raymond Paik
Subject: [release] volunteers needed for milestone exception review process

Team,

Our current milestone exception review volunteers have completed two releases, 
as requested. A big thanks to the following volunteers for their help with this 
important task:

  *   Rossella Sblendido
  *   Tapio Tallgren
  *   Hongbo Tian
  *   Julien Zhang
  *   Uli Kleber

So, now it's time to form a new team for the "Gambia" and "H" releases.  The 
time commitment is typically not more than 2 hours per release.

If you would like to volunteer, or if you have questions, please respond to 
this email.  Note that previous volunteers are welcome to volunteer again.  
Thanks.

David

--
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

Re: [opnfv-tech-discuss] [releng] New PTL approved

[Tallgren, Tapio (Nokia - FI/Espoo)]

Congratulations!


From: opnfv-tsc-boun...@lists.opnfv.org  on 
behalf of Fatih Degirmenci 
Sent: Monday, May 14, 2018 11:48:38 AM
To: opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tsc] [releng] New PTL approved

Hi all,

Trevor Bramwell has been elected as the new PTL for OPNFV Releng with the votes 
from majority of the committers.
Please see the change on Gerrit.

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

Congratulations Trevor!

/Fatih


___
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] Wiki pages for 2018 Goals "working groups"

[Tallgren, Tapio (Nokia - FI/Espoo)]

Since Tim is on holiday, I took the liberty to update the CD release model page 
on my own: https://wiki.opnfv.org/display/meetings/Release+Process+Based+on+CD
I found a lot of issues with the current model; see if you agree. I will 
continue by explaining how CI/CD solves *all* those issues.

-Tapio


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
 on behalf of Raymond Paik 

Sent: Friday, April 6, 2018 7:51:55 AM
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] Wiki pages for 2018 Goals "working groups"

All,

As discussed in the TSC call earlier, I created wiki pages for major OPNFV 
activity buckets for 2018.  The main page is here 
https://wiki.opnfv.org/display/meetings/2018+Goals+Working+Groups and you'll 
find the children pages listed for each activity

Thanks,

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

Re: [opnfv-tech-discuss] LDT breakout session summary //Re: ONS Discussion //RE: NFVbench requirements //RE: check xci pike tags //RE: Update on long duration test

[Tallgren, Tapio (Nokia - FI/Espoo)]

Hi,

Our system is using VXLAN, will TRex work with that?

-Tapio


From: Alec Hothan (ahothan) <ahot...@cisco.com>
Sent: Friday, March 30, 2018 7:13:24 PM
To: Tallgren, Tapio (Nokia - FI/Espoo); Yuyang (Gabriel); 'Fatih Degirmenci'; 
'cedric.olliv...@orange.com'; 'Tim Irnich'; 'BLAISONNEAU David IMT/OLN'; 
'sridhar@spirent.com'; 'ross.b.bratt...@intel.com'; 'mark.bei...@emc.com'; 
'Jose Lausuch'; 'Georg Kunz'
Cc: 'trevor.coo...@intel.com'; Kosonen, Juha (Nokia - FI/Espoo); 
'acmor...@att.com'; Wangwulin (Linda); 'rp...@linuxfoundation.org'; 
'opnfv-tech-discuss@lists.opnfv.org'; 'test...@lists.opnfv.org'
Subject: Re: LDT breakout session summary //Re: ONS Discussion //RE: NFVbench 
requirements //RE: check xci pike tags //RE: Update on long duration test


Hi Tapio,

We routinely use Trex with a switch so should not be a problem.
The wiki page mentions that the jump host has 4x10G ports, how many of those 
ports are used?
TRex will need 2 unused ports and the corresponding ports on the switch need to 
be configured in trunk mode and with proper VLAN range (i.e. it has to match 
the VLAN range used by the deployer for the tenant or provider network n- this 
should normally be the same configuration as the ports that connect to all 
compute node provider network).

Thanks

  Alec



From: "Tallgren, Tapio (Nokia - FI/Espoo)" <tapio.tallg...@nokia.com>
Date: Thursday, March 29, 2018 at 10:42 AM
To: "Alec Hothan (ahothan)" <ahot...@cisco.com>, "Yuyang (Gabriel)" 
<gabriel.yuy...@huawei.com>, 'Fatih Degirmenci' 
<fatih.degirme...@ericsson.com>, "'cedric.olliv...@orange.com'" 
<cedric.olliv...@orange.com>, 'Tim Irnich' <tim.irn...@ericsson.com>, 
'BLAISONNEAU David IMT/OLN' <david.blaisonn...@orange.com>, 
"'sridhar@spirent.com'" <sridhar@spirent.com>, 
"'ross.b.bratt...@intel.com'" <ross.b.bratt...@intel.com>, 
"'mark.bei...@emc.com'" <mark.bei...@emc.com>, 'Jose Lausuch' 
<jalaus...@suse.com>, 'Georg Kunz' <georg.k...@ericsson.com>
Cc: "'trevor.coo...@intel.com'" <trevor.coo...@intel.com>, "Kosonen, Juha 
(Nokia - FI/Espoo)" <juha.koso...@nokia.com>, "'acmor...@att.com'" 
<acmor...@att.com>, "Wangwulin (Linda)" <wangwu...@huawei.com>, 
"'rp...@linuxfoundation.org'" <rp...@linuxfoundation.org>, 
"'opnfv-tech-discuss@lists.opnfv.org'" <opnfv-tech-discuss@lists.opnfv.org>, 
"'test...@lists.opnfv.org'" <test...@lists.opnfv.org>
Subject: Re: LDT breakout session summary //Re: ONS Discussion //RE: NFVbench 
requirements //RE: check xci pike tags //RE: Update on long duration test

Hi,

The Nokia lab architecture is on 
https://wiki.opnfv.org/display/pharos/Nokia+Hosting.

You can run TRex on the jump host unless you want to do some custom 
installation. The NICs are standard Intel 82599's aka Niantics, so dpdk should 
just work.

I do not know how TRex works but I have had some difficulties with Moongen with 
the ToR switches. Moongen uses timing packets and these do not go cleanly 
through the ToRs, but everything works with a direct connection. Let me know if 
you need something unusual.

-Tapio

________
From: Alec Hothan (ahothan) <ahot...@cisco.com<mailto:ahot...@cisco.com>>
Sent: Thursday, March 29, 2018 12:25:00 AM
To: Yuyang (Gabriel); 'Fatih Degirmenci'; 
'cedric.olliv...@orange.com<mailto:cedric.olliv...@orange.com>'; Tallgren, 
Tapio (Nokia - FI/Espoo); 'Tim Irnich'; 'BLAISONNEAU David IMT/OLN'; 
'sridhar@spirent.com<mailto:sridhar@spirent.com>'; 
'ross.b.bratt...@intel.com<mailto:ross.b.bratt...@intel.com>'; 
'mark.bei...@emc.com<mailto:mark.bei...@emc.com>'; 'Jose Lausuch'; 'Georg Kunz'
Cc: 'trevor.coo...@intel.com<mailto:trevor.coo...@intel.com>'; Kosonen, Juha 
(Nokia - FI/Espoo); 'acmor...@att.com<mailto:acmor...@att.com>'; Wangwulin 
(Linda); 'rp...@linuxfoundation.org<mailto:rp...@linuxfoundation.org>'; 
'opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>';
 'test...@lists.opnfv.org<mailto:test...@lists.opnfv.org>'
Subject: Re: LDT breakout session summary //Re: ONS Discussion //RE: NFVbench 
requirements //RE: check xci pike tags //RE: Update on long duration test


Just want to add the ETA for getting bare metal installation automated by 
script would have to be before this summer – which is not that far away (3 
months).
To avoid any last minute surprise and further delay, it would be great if Tapio 
could identify which jump host to use to run Trex and whether/when it will have 
the proper NIC by then. Also note that we should be able to verify the proper 
connectivity from TRex to the TOR and back without requiring a bare metal 
openstack installation.

Re: [opnfv-tech-discuss] LDT breakout session summary //Re: ONS Discussion //RE: NFVbench requirements //RE: check xci pike tags //RE: Update on long duration test

[Tallgren, Tapio (Nokia - FI/Espoo)]

Hi,

The Nokia lab architecture is on 
https://wiki.opnfv.org/display/pharos/Nokia+Hosting.

You can run TRex on the jump host unless you want to do some custom 
installation. The NICs are standard Intel 82599's aka Niantics, so dpdk should 
just work.

I do not know how TRex works but I have had some difficulties with Moongen with 
the ToR switches. Moongen uses timing packets and these do not go cleanly 
through the ToRs, but everything works with a direct connection. Let me know if 
you need something unusual.

-Tapio


From: Alec Hothan (ahothan) <ahot...@cisco.com>
Sent: Thursday, March 29, 2018 12:25:00 AM
To: Yuyang (Gabriel); 'Fatih Degirmenci'; 'cedric.olliv...@orange.com'; 
Tallgren, Tapio (Nokia - FI/Espoo); 'Tim Irnich'; 'BLAISONNEAU David IMT/OLN'; 
'sridhar@spirent.com'; 'ross.b.bratt...@intel.com'; 'mark.bei...@emc.com'; 
'Jose Lausuch'; 'Georg Kunz'
Cc: 'trevor.coo...@intel.com'; Kosonen, Juha (Nokia - FI/Espoo); 
'acmor...@att.com'; Wangwulin (Linda); 'rp...@linuxfoundation.org'; 
'opnfv-tech-discuss@lists.opnfv.org'; 'test...@lists.opnfv.org'
Subject: Re: LDT breakout session summary //Re: ONS Discussion //RE: NFVbench 
requirements //RE: check xci pike tags //RE: Update on long duration test


Just want to add the ETA for getting bare metal installation automated by 
script would have to be before this summer – which is not that far away (3 
months).
To avoid any last minute surprise and further delay, it would be great if Tapio 
could identify which jump host to use to run Trex and whether/when it will have 
the proper NIC by then. Also note that we should be able to verify the proper 
connectivity from TRex to the TOR and back without requiring a bare metal 
openstack installation.
Once we get Trex operational, we will be able to run any test that relies on 
Trex.

Thanks

   Alec



From: "Yuyang (Gabriel)" <gabriel.yuy...@huawei.com>
Date: Tuesday, March 27, 2018 at 7:07 PM
To: "Alec Hothan (ahothan)" <ahot...@cisco.com>, 'Fatih Degirmenci' 
<fatih.degirme...@ericsson.com>, "'cedric.olliv...@orange.com'" 
<cedric.olliv...@orange.com>, "'Tallgren, Tapio (Nokia - FI/Espoo)'" 
<tapio.tallg...@nokia.com>, 'Tim Irnich' <tim.irn...@ericsson.com>, 
'BLAISONNEAU David IMT/OLN' <david.blaisonn...@orange.com>, 
"'sridhar@spirent.com'" <sridhar@spirent.com>, 
"'ross.b.bratt...@intel.com'" <ross.b.bratt...@intel.com>, 
"'mark.bei...@emc.com'" <mark.bei...@emc.com>, 'Jose Lausuch' 
<jalaus...@suse.com>, 'Georg Kunz' <georg.k...@ericsson.com>
Cc: "'trevor.coo...@intel.com'" <trevor.coo...@intel.com>, "'Kosonen, Juha 
(Nokia - FI/Espoo)'" <juha.koso...@nokia.com>, "'acmor...@att.com'" 
<acmor...@att.com>, "Wangwulin (Linda)" <wangwu...@huawei.com>, 
"'rp...@linuxfoundation.org'" <rp...@linuxfoundation.org>, 
"'opnfv-tech-discuss@lists.opnfv.org'" <opnfv-tech-discuss@lists.opnfv.org>, 
"'test...@lists.opnfv.org'" <test...@lists.opnfv.org>
Subject: LDT breakout session summary //Re: ONS Discussion //RE: NFVbench 
requirements //RE: check xci pike tags //RE: Update on long duration test

Hi,

It is really nice to have us gather around and to move things forward!
I have made a brief summary of our discussion today. Please find it below and 
comment if there is anything missing or misleading, thanks!

Brief summary LDT breakout discussion

1. SUT deployment

a) We should have a transition solution for SUT deployment, so that 
test projects could adapt their test cases

 i.  Currently, 
deploy xci-virtual first on another POD

   ii.  It could be 
triggered through jenkin

 iii.  Gabriel send the 
name list to Fatih to gain access of the deployment

b)It would best to have a script for deploy xci baremetal, so that we 
can manually do deployment on Nokia POD

2. LDT CI requirements and set-up

a) For transition solution, we only support job triggering

b)For all the Jenkins requirements, Fatih will come with a solution 
later

3. Hardware configurations for Traffic generator

a) NFVbench need bare metal deployment

b)Need to confirm with Tapio about the support for traffic generators

For yesterday’s presentation, please refer to 
https://wiki.opnfv.org/display/testing/Long+Duration+Testing.

Thanks,
Gabriel

发件人: Yuyang (Gabriel)
发送时间: 2018年3月16日 10:07
收件人: Alec Hothan (ahothan) <ahot...@cisco.com>; Fatih Degirmenci 
<fatih.degirme...@ericsson.com>; cedric.olliv...@orange.com; Tallgren, Tapio 
(Nokia - FI/Espoo) <tapio.tallg...@nokia.com

[opnfv-tech-discuss] [releng-xci] XCI documentation for OPNF Docs hackfest?

[Tallgren, Tapio (Nokia - FI/Espoo)]

Hi Fatih, Marcos et al.,

I am planning to participate in the OPNFV Docs Hackfest on Feb 1st and I was 
wondering if I could help with the XCI documentation. The XCI Overview and XCI 
Sandbox seem to be in pretty good shape, the Way of Working I have no idea 
about, and the Developer Guide is mostly missing. Would it make sense for me to 
write down some lessons learned there? Other ideas?

-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] New Adventures

[Tallgren, Tapio (Nokia - FI/Espoo)]

Dan,

Thanks for all the great work you have done in OPNFV and especially for the 
effort you have put into fixing issues with our hardware. It's been great 
working with you!

-Tapio


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
 on behalf of HU, BIN 

Sent: Wednesday, January 17, 2018 11:43:01 PM
To: Dan Radez; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] New Adventures

Dan,

You will be truly missed. I am sure our path will cross again somewhere.

All the best in new adventure.

Bin

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dan Radez
Sent: Wednesday, January 17, 2018 11:56 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] New Adventures

With a new year I have been assigned to a new primary project.

I've enjoyed my time with OPNFV and want to say thank you to the community and 
leadership for the past three years of working together.
It's been a pleasure to work along side of you all.

I'll be around less but not inaccessible. I'll be working to hand off my tasks 
over the next couple weeks so they can be carried forward. Please be in contact 
with me if I'm not already in discussion with you about certain tasks.

Happy New Year!

Dan Radez
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_mailman_listinfo_opnfv-2Dtech-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=z7L52BOPjADgdI6kGIBakeWjVrD0tXk5Db3YhnwPU5I=jOeoBeRD8JLSbjhYBxZoe62CMkl3Z0FT606ZD86FRrY=
___
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] [releng] Committer list per Releng repository

[Tallgren, Tapio (Nokia - FI/Espoo)]

+1


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
 on behalf of Fatih Degirmenci 

Sent: Friday, December 8, 2017 2:01:34 AM
To: Aric Gardner; Tim Rozet; Morgan Richomme; Jose  Lausuch; Ryota; Meimei; 
Trevor Bramwell; Serena Feng; Yolanda Robla Mota; Markos Chandras; Luke Hinds
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [releng] Committer list per Releng repository

Hi Releng Committers,

During OPNFV Plugfest, we had conversations around having committer list per 
Releng repository/Gerrit Project.

The reason behind this is that, Releng project currently has 5 different 
repositories as listed below. [1]


  *   releng
  *   releng-anteater
  *   releng-testresults
  *   releng-utils
  *   releng-xci

The work that is done in these repositories require different competence 
profiles. For example for releng repository, the committers need to have 
knowledge in CI, Jenkins, Jenkins Job Builder and so on.
Apart from the required competence, some developers might not be interested in 
certain parts of Releng but interested in others.

Having single committer list across all Releng owned repositories prevents us 
from recognizing contributors and promoting them as committers for the 
corresponding repositories since they will perhaps never have enough 
contributions across all of them.
Another limitation is that, the current review practices followed by Releng is 
not good and we need to improve this. Having right set of committers per repo 
and getting patches reviewed by them properly will help with the quality of 
work we are doing.

In order to address this limitation and have the ability and the possibility to 
recognize and promote developers who made great contributions to Releng in 
general in the repositories they worked in, I propose to create committer list 
per repo.

Please respond to this mail with +1 and -1 and share questions, comments, 
concerns if you have any.

I plan to bring this topic to TSC on December 12th if the vote passes.

[1] https://gerrit.opnfv.org/gerrit/#/admin/projects/?filter=releng

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

Re: [opnfv-tech-discuss] Request POD for Long Duation Testing

[Tallgren, Tapio (Nokia - FI/Espoo)]

Hi Gabriel,

We could use the Nokia pod 
(https://wiki.opnfv.org/display/pharos/Nokia+Hosting) for this. Let me know 
what needs to be done.

-Tapio

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
 on behalf of Yuyang (Gabriel) 

Sent: Wednesday, October 25, 2017 2:13:30 PM
To: infra...@lists.opnfv.org
Cc: test...@lists.opnfv.org; 'opnfv-tech-discuss@lists.opnfv.org'
Subject: [opnfv-tech-discuss] Request POD for Long Duation Testing

Hi,

Test working group has initiated the long duration test since Danube and plan 
to evolve for Euphrates.
We propose to set an separate CI pipeline for long duration test against 
“stable” releases.
The proposal has been modified and shared for several times which could be 
found in Euphrates Testing 
Needs
 and Testing 
Evolution.

We thought we have Intel-18 for our test and CI pipeline in 
https://jira.opnfv.org/browse/INFRA-154 through community efforts.
However, due to the fact that Intel will not be able to host this activity. 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-10-16-15.01.html
I ask for help here if our lab managers could find available POD to support our 
testing efforts.

Our need is simple. Any POD that could be used for currently OPNFV CI is 
suffice to meet our requirements.
If you have further questions, feel free to ask through email or discuss in the 
next Infra Group Meeting.

Best,
Gabriel


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

Re: [opnfv-tech-discuss] [opnfv-tsc] New meeting time for the TSC call

[Tallgren, Tapio (Nokia - FI/Espoo)]

I was planning to be on vacation on July 4th.

-Tapio

On 21 Jun 2017 8.04, Raymond Paik  wrote:
All,

As discussed on the TSC call today, I'd like to propose changing the TSC 
meeting time to 6am Pacific Time.  This would make it slightly easier for 
community members in Asia to join the weekly call.  Obviously, an earlier start 
will make things a little painful for people in Pacific Timezone (myself 
included).  However, there were no objections from west coasters when I asked 
people a few months ago.

This change won't take effect right away, but we could start in mid-July.  I 
need to thank the Doctor team for agreeing to move their weekly meeting to make 
this possible.   If you have any major concerns/objections about the proposed 
change, please let me know by the end of this week (23rd).

Speaking of July, the first Tuesday in July is the Independence Day holiday in 
the US and many folks here in the US will be on Holiday that week.  Is everyone 
OK with canceling the TSC call in the first week of July?

Thanks,

Ray

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

Re: [opnfv-tech-discuss] [dovetail] Standing down as a committer on DoveTail

[Tallgren, Tapio (Nokia - FI/Espoo)]

Hi,

I put this to the TSC agenda for today. Personally, I agree with Bin about what 
the TSC could and should do about this, so I think we need to call for 
volunteers to help with the Dovetail project.

-Tapio

From: Christopher Price <christopher.pr...@ericsson.com>
Sent: Tuesday, May 2, 2017 3:12:18 PM
To: HU, BIN; Cooper, Trevor; Dave Neary; opnfv-tech-discuss@lists.opnfv.org; 
Tallgren, Tapio (Nokia - FI/Espoo); opnfv-...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [dovetail] Standing down as a committer on 
DoveTail

Hi Bin,

Thanks for sharing your thoughts.
I’d like to further understand the power struggle you clearly see here, I would 
be very interested to understand your views further.

My views are quite clear that dovetail should be established with the best 
competence we have available to judge test cases for application in the CVP, in 
as neutral as manner as possible across as many stakeholders as possible.
I am not the right person in the community to bring that forward so I have 
stood down, I hope the right people step forward to do so without accusations 
that they do so for some form of power.

Cheers,
Chris

On 2017-05-02, 04:37, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
HU, BIN" <opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
bh5...@att.com> wrote:

Guys,

What I see here is power struggle. We all have seen this type of things 
many times before, especially with strong opinion.

Here are my 2 cents:

(1) TSC shouldn't interfere with the internal management of a project. It 
will be a bad precedent for TSC to intervene a project's internal matters here 
unless there is an evidenced misconduct. Otherwise it will open a can of worm 
for future.

(2) One vote per committer cannot be changed at project level. Again, it 
will be a bad precedent to introduce one vote per company within a project. 
Project is contribution driven, and committer promotion is based on merit. 
That's the principle. If one person has made significant contribution, the 
person deserves the promotion no matter what company he works for. If we change 
the principle, basically we lose the credibility as an open source community.

(3) All of those different opinion should be addressed at project level. If 
you are not the majority of opinion, and you lose the vote, sorry you lose. You 
have to accept the result of the voting. Power struggling happens everywhere, 
and I personally experienced it too. You have to negotiate and make compromise, 
even if you have strong opinion. Sorry, you need to learn "compromise". 
Exaggerating power struggle is not a right way to move forward.

(4) If there is an *evidence* that there is a *misconduct* within a 
project, please submit the evidence, and describe the nature of misconduct. TSC 
can discuss the nature of the misconduct based on evidence, further investigate 
it and take disciplinary actions based on the result of investigation of the 
misconduct according to authorized power by TSC Charter.

(5) If there is a concern that a project is driven by a single vendor, TSC 
should take one or more of the following actions:
- Appreciate that company's investment in supporting our open source 
community. Everyone is volunteer here. We should appreciate the investment 
instead of discouraging the investment. We want more company to invest more 
resources in OPNFV.
- Encourage more contributors from other companies to this project. This is 
a hard part we need to know:
   * What is the percentage of code that is contributed by this single 
vendor v.s. others?
   * Are others code contribution intentionally blocked by this single 
vendor? Or just lack of code contribution from others?
- Investigate if there is misconduct
   * Is your code carefully reviewed by others?
   * How many code rejections did you get?
   * Are those rejection reasonable?
   * If you suspect misconduct in code review and your code is rejected 
unreasonably, please submit evidence.
- TSC may make a motion to defer this project's participation in E Release, 
and may suggest to Board to defer CVP, if majority concerns single 
vendor-driven.

So there are many things TSC can do - to appreciate investment, to 
encourage contribution, to investigate misconduct if evidence is provided, and 
to defer its participation in E Release, and to recommend to Board to defer CVP 
until single vendor concern is addressed.

But the last thing we want to do is to interfere with project's internal 
management, change the principle of contribution-driven, and meritocracy-based 
committer election, change the voting model, or discourage investment. Those 
are fundamental to an open source community. We cannot change the cornerstone 
of a house.

My 2 cents.
Thanks
Bin
-Original Message-
From: opnfv-tech

Re: [opnfv-tech-discuss] Danube release community awards

[Tallgren, Tapio (Nokia - FI/Espoo)]

I would like to nominate Mika Rautakumpu and Juha Kosonen for the Integration 
and Testing category for the great work they have done in especially in the 
plugfest. We had a OCP hardware physically present the the Colorado Plogufest 
and will have one in the Danube plugfest also. They have been used for testing 
the installers and also Dovetail. Mika and Juha have installed and debugged the 
machines and the OPNFV software stack with it.

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
 on behalf of Raymond Paik 

Sent: Thursday, April 20, 2017 11:52:12 PM
To: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Danube release community awards

All, a final reminder to send in your nominations for Community Awards by 5pm 
Pacific Time tomorrow (April 21st).

I actually only received 1-2 nominations for Integration and Testing 
categories, and these are supposed to be our bread & butter in OPNFV

Thanks,

Ray

On Mon, Apr 17, 2017 at 4:07 PM, Raymond Paik 
> wrote:
All,

I have not received a lot of nominations for the Community Awards for the 
Danube release.  So far, internship is the only category where I have more 
nominees than awards and I didn't receive any nomination for "Community 
Support/Leadership."

I'm sure my mistake on the nomination due date (I originally wrote May 17th 
when I meant APRIL 17th) didn't help, but I think another issue was the Easter 
holidays.  So I'd like to extend the nomination period to Friday this week 
(April 21st).  Could you send in your nominations by 5pm Pacific Time on April 
21st?

Thanks,

Ray

On Wed, Apr 12, 2017 at 11:15 PM, Raymond Paik 
> wrote:
Thanks Yujun,

Yes, I meant APRIL 17th :-)  (as in ~5 days).  Plan is to start the voting on 
April 19th

Ray

On Wed, Apr 12, 2017 at 10:56 PM, Yujun Zhang (ZTE) 
> wrote:
May 17th is not Monday. Do you mean April 17th?

On Tue, Apr 11, 2017 at 12:08 AM Raymond Paik 
> wrote:
All,

I'm kicking off the nomination period for the Community Awards following the 
Danube release.  As announced in February, we have the following award 
categories (with the number of winners in parentheses).

  *   Code development (3)
  *   Community support/leadership (3)
  *   Integration (3)
  *   Testing (3)
  *   Interns (2)

If you're interested in nominating community members for any of the categories 
above, could you send them to me by 5pm Pacific Time on May 17th (Monday)?

I'll be sending out a SurveyMonkey link for voting to opnfv-tech-discuss on May 
19th.

Thanks,

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



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

Re: [opnfv-tech-discuss] OPNFV Danube 1.0 release

[Tallgren, Tapio (Nokia - FI/Espoo)]

Great news! Thanks to all for your contributions!

On Apr 2, 2017 18:39, David McBride  wrote:
Team,

I'm pleased to report to you that we have completed the Danube 1.0 release.  
Congratulations and thanks to the project teams, test framework teams, 
installer teams, infra team, and docs team for contributing to this release. 
The download page will go live on Tuesday, April 4.

Please be aware that Danube 2.0 is still scheduled for May 4.  Also, if you 
have not yet stated your intent to participate in 
Euphrates,
 please do so ASAP.

Onward to Euphrates!

David

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

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

Re: [opnfv-tech-discuss] Ray Nugent

[Tallgren, Tapio]

Very sorry to hear that! I met Ray a couple of times when he was working 
in Anthony's team, and I got to know him as a very knowledgeable and 
insightful person.


My condolences to the family!

-Tapio



On 03/17/2017 04:05 PM, Ash Young wrote:

For those interested, here's the info for Ray's service:

Fri March 31 12:00noon
Orchard City Banquet Hall in Campbell, at the Community Center

Best,

Ash

On Fri, Mar 17, 2017 at 2:07 AM, Ulrich Kleber 
> wrote:


Hello,

we just have received the sad news that our former colleague Ray
Nugent was killed in an automobile accident on Saturday.

Ray has worked in Huawei’s OPNFV team and I am sure many of you
remember him well, so I wanted to share.

Ray had a very rich experience from many open source projects and
used that to help OPNFV be what it is today.

Best,

Uli


___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org

https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss





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



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

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

[Tallgren, Tapio]

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.


-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 
:~/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:

openstack server create --image cirros-0.3.3 --flavor m1.small --nic 
net-id=net04_ext server_name


(you need to replace the flavor and nic value with your own.

Using the follow command to get all flavors:

openstack flavor list

Using the follow command to get all network:

 openstack network list

)

If you can create a instance, I think maybe there is something wrong 
with yardstick.


If failed to create an instance, maybe there is something wrong with 
the environment.


Regards,

Jack Chan

*From:*opnfv-tech-discuss-boun...@lists.opnfv.org 
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of 
*Marco Varlese

*Sent:* Thursday, March 02, 2017 9:34 PM
*To:* Tapio Tallgren; opnfv-tech-discuss@lists.opnfv.org 


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

On Thu, 2017-03-02 at 14:34 +0200, Tapio Tallgren wrote:

On 03/02/2017 02:15 PM, Marco Varlese wrote:

On Thu, 2017-03-02 at 13:41 +0200, Tapio Tallgren wrote:

On 03/02/2017 10:45 AM, Marco Varlese wrote:

Hi,

In my previous email I did not mention the use of the
docker image, I was trying to install it on the
system following the online Yardstick documentation.

Why do I need to use the docker image necessarily?

I have been using a kvm VM for Yardstick. Docker is
easier to use since you do not need to set up the virtenv
etc.


Also, are there any particular reasons/dependencies why
it has to be Ubuntu 14.04? It's quite "old" and the new
LTS (16.04) has been out for a while.


I just used the Xenial Ubuntu and it worked equally well.
I downloaded and booted the Xenial image, git cloned
Yardstick to it, and then installed Yardstick on it. For
reporting, I used a Docker image.

How did you setup the Openstack environment?

In my case I cloned DevStack (master) and installed it on the
box.

My setup has everything installed onto one single VM:

1) DevStack (with Heat)

2) Yardstick with its virtual-env

And when I try launch the ping.yaml test case I get the error
mentioned in my prev email...

Any thoughts/ideas?


I had a physical deployment. Since you are running everything in
a VM, it is best to use the virtenv and not launch another VM.
Can you use the "openstack server list" command from the
Yardstick virtenv? Do you see cirros-0.3.3 when you do "openstack
image list"? I think there was some confusion about cirros-0.3.3
and cirros-0.3.4, but I cannot find the reference right now.

Yes I can see it... I downloaded the image from 
http://download.cirros-cloud.net/0.3.3/cirros-0.3.3-x86_64-disk.img


and installed it via glance...

Re: [opnfv-tech-discuss] [opnfv-tsc] Continuing the project graduation discussions

[Tallgren, Tapio]

I agree. According to the definitions, most of the projects should be in 
Integration Review by now. If we keep the Graduation Review and 
Termination Review, we could drop Integration Review.


-Tapio


On 03/07/2017 08:39 AM, Ashiq Khan wrote:


+1

Ashiq

*From:*opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of 
*SULLIVAN, BRYAN L

*Sent:* Tuesday, March 07, 2017 4:52 AM
*To:* Raymond Paik; opnfv-tech-discuss@lists.opnfv.org; 
opnfv-...@lists.opnfv.org
*Subject:* Re: [opnfv-tech-discuss] [opnfv-tsc] Continuing the project 
graduation discussions


I added my comments to that page:

I think we need to revisit the 
https://www.opnfv.org/software/technical-project-governance/project-lifecycle expectations 
2.5 years into OPNFV. IMO, in a rapidly evolving industry, projects 
will come and go, morph and merge, both in OPNFV and upstream. In 
fact, if we walk the "working upstream" talk, projects in OPNFV really 
should be quite short-lived (a couple of releases) before they are 
upstreamed fully, leaving behind only perhaps some deployment/test 
scripts as needed for the OPNFV CI/CD system, and some documents which 
describe what the project was about and where further development of 
it lives. Exceptions to this expectation for "succeed and disappear" 
may be the truly integration-focused projects (e.g. OpenStack 
distro-centered installers) and test projects that span upstream projects.


Thanks,

Bryan Sullivan | AT

*From:*opnfv-tsc-boun...@lists.opnfv.org 
 
[mailto:opnfv-tsc-boun...@lists.opnfv.org] *On Behalf Of *Raymond Paik

*Sent:* Monday, March 06, 2017 9:19 AM
*To:* opnfv-tech-discuss@lists.opnfv.org 
; opnfv-...@lists.opnfv.org 


*Subject:* Re: [opnfv-tsc] Continuing the project graduation discussions

All,

Wanted to follow-up via email in order to save sometime during the TSC 
call tomorrow 
(https://wiki.opnfv.org/display/meetings/TSC#TSC-March6,2017).. 
..


Besides a single comment on the wiki page 
(https://wiki.opnfv.org/display/PROJ/Graduation+review+discussions 
), 
I don't believe there were other feedback so here's my recommendation.


Based on past discussions, I believe there's consensus that graduation 
reviews are good ways of recognizing mature projects that can server 
as role models for the rest of the community.  In addition, I don't 
think there's any need to make any modifications to the graduation 
review process in the current OPNFV Project Lifecycle 
(https://www.opnfv.org/software/technical-project-governance/project-lifecycle 
). 
There was a discussion on whether a project team can step forward for 
a graduation review or if there should be a nomination from the 
community, but I think either way will work.


Let me know if you have any other questions/comments.  If not, we 
could probably reach a quick consensus on the call tomorrow.


Thanks,

Ray

On Mon, Feb 20, 2017 at 10:39 PM, Raymond Paik 
> wrote:


All,

I don't think I managed to follow-up after our discussions at the
Plugfest on graduation reviews.  I created a wiki page summarizing
my notes at
https://wiki.opnfv.org/display/PROJ/Graduation+review+discussions


 If you have any questions or comments, please feel free to add
them to the comments section on the wiki page or reply to this email.

I also had a chance to talk to a few OpenDaylight community
members last week and confirmed that projects that passed
graduation/promotion reviews in their community serve as "role
models" for other members of the community.

I can bring this up during the TSC call tomorrow if we have time...

Thanks,


Ray



___
opnfv-tech-discuss mailing list

Re: [opnfv-tech-discuss] [KVM] Test plan for KVM enhancements for NFV

[Tallgren, Tapio (Nokia - FI/Espoo)]

Hi,

I will not commit to having it ready by Danube. It will take me time to learn 
about how to integrate it to Yardstick and there is probably other stuff I 
should do first in Yardstick.

-Tapio

On Oct 26, 2016 2:21 AM, yunhong jiang  wrote:
Hi, Tapio
The KVM4NFV project is discussing what's should be done on D
release.

Considering your role changes, do you still have plan to
push this test, or you will postpone this effort?

Thanks
--jyh

On Thu, 22 Sep 2016 13:57:10 +0300
Tapio Tallgren  wrote:

> On 22.09.2016 00:55, yunhong jiang wrote:
> > On Mon, 20 Jun 2016 12:00:07 +0300
> > Tapio Tallgren  wrote:
> >
> >> Hi,
> >>
> >> I have just put some code to github.com that might be interesting
> >> for your testing: https://github.com/nokia/clocktick_jumps.
> >> It is meant to measure latencies at a very low level, without any
> >> guest operating system involvement.
> >> Ideally, this code would become part of some OPNFV testing project.
> > Hi, Tapio
> >
> >  We have (mostly) integrated the cyclictest into the KVM4NFV
> > project CI. Now it's executed on the patch verification and the
> > daily test. We are also working with yardstick team (
> > https://gerrit.opnfv.org/gerrit/#/c/21255/1) so that the daily test
> > result can be published on the yardstick dashboard
> > (http://testresults.opnfv.org/grafana/dashboard/db/yardstick-main).
> >
> >  Not sure if you have plan to add your clocktick_jumps to the
> > yardstick, and then we can integrate it into the project CI also?
>
> Yes, that is my plan. I need to get more familiar with Yardstick
> first, so it might take a while.
>
> -Tapio


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