Re: [opnfv-tech-discuss] [SDNVPN] Standing down as SDNVPN PTL

[Nikolas Hermanns]

+1

From: Prem sankar G
Sent: Friday, January 26, 2018 4:58 PM
To: Tim Irnich <tim.irn...@ericsson.com>; Periyasamy Palanisamy 
<periyasamy.palanis...@ericsson.com>; Thomas Sounapoglou 
<s...@intracom-telecom.com>; MORIN Thomas IMT/OLN (thomas.mo...@orange.com) 
<thomas.mo...@orange.com>; Nikolas Hermanns <nikolas.herma...@ericsson.com>; 
Jose Lausuch <jalaus...@suse.com>
Cc: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
Subject: RE: [SDNVPN] Standing down as SDNVPN PTL

+1

From: Tim Irnich
Sent: Friday, January 26, 2018 1:14 AM
To: Periyasamy Palanisamy 
<periyasamy.palanis...@ericsson.com<mailto:periyasamy.palanis...@ericsson.com>>;
 Thomas Sounapoglou 
<s...@intracom-telecom.com<mailto:s...@intracom-telecom.com>>; Prem sankar G 
<prem.sanka...@ericsson.com<mailto:prem.sanka...@ericsson.com>>; MORIN Thomas 
IMT/OLN (thomas.mo...@orange.com<mailto:thomas.mo...@orange.com>) 
<thomas.mo...@orange.com<mailto:thomas.mo...@orange.com>>; Nikolas Hermanns 
<nikolas.herma...@ericsson.com<mailto:nikolas.herma...@ericsson.com>>; Jose 
Lausuch <jalaus...@suse.com<mailto:jalaus...@suse.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
opnfv-...@lists.opnfv.org<mailto:opnfv-...@lists.opnfv.org>
Subject: RE: [SDNVPN] Standing down as SDNVPN PTL

Hi all,

Looks like Peri is the only interested candidate. SDNVPN Committers, can you 
please respond in this thread with +1, 0, -1 to indicate your opinion on having 
Peri take over the PTL role for the SDNVPN project?

Thanks and kind regards, Tim

From: Tim Irnich
Sent: Wednesday, January 17, 2018 16:13
To: Periyasamy Palanisamy 
<periyasamy.palanis...@ericsson.com<mailto:periyasamy.palanis...@ericsson.com>>;
 Thomas Sounapoglou 
<s...@intracom-telecom.com<mailto:s...@intracom-telecom.com>>; Prem sankar G 
<prem.sanka...@ericsson.com<mailto:prem.sanka...@ericsson.com>>; MORIN Thomas 
IMT/OLN (thomas.mo...@orange.com<mailto:thomas.mo...@orange.com>) 
<thomas.mo...@orange.com<mailto:thomas.mo...@orange.com>>; Nikolas Hermanns 
<nikolas.herma...@ericsson.com<mailto:nikolas.herma...@ericsson.com>>; Jose 
Lausuch <jalaus...@suse.com<mailto:jalaus...@suse.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
opnfv-...@lists.opnfv.org<mailto:opnfv-...@lists.opnfv.org>
Subject: [SDNVPN] Standing down as SDNVPN PTL

SDNVPN Committers,

I would like to announce that I am standing down as SDNVPN PTL. I feel that I'm 
no longer able to fill this role the way it deserves given my other obligations 
and would like to make room for someone that can dedicate more time.

I understand that Peri, who has been making significant contributions to the 
project during Euphrates and Fraser, is interested to take the helm. If you are 
interested as well, please let us know by Wed next week. If Peri remains the 
only candidate, we will use a simple +-1 vote by the committers to approve.

Regards, Tim
___
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][danube] MS6 compliance assessment

[Nikolas Hermanns]

Hey David,

Here are the requested info for SDNVPN:
Enabling testing did happen already in earlier releases but we have added some 
more test cases this release. It is not completely applicable for us since we 
enable the test cases in the sdnvpn repo which will be run by functest.
Enabling testing for your project in the Functest repo:

-  Enable floating IP and router assoc test: 
https://gerrit.opnfv.org/gerrit/#/c/28903/

-  Re-enable the tests for bgpvpn scenario wich use floating ips: 
https://gerrit.opnfv.org/gerrit/#/c/28841/1
Test case implementation in your project repo:

-  This is not yet merged but will be merged soon: 
https://gerrit.opnfv.org/gerrit/#/c/29287/1

-  Implement testcase 3: Quagga-ODL integration: 
https://gerrit.opnfv.org/gerrit/#/c/28835/16
Please indicate whether the scenarios with which your project is integrated are 
visible on the Functest dashboard:
Yes it is visible.
Preliminary Documentation Requirement
https://gerrit.opnfv.org/gerrit/#/c/29295/

BR Nikolas

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of David McBride
Sent: Wednesday, February 22, 2017 9:30 PM
To: opnfv-project-le...@lists.opnfv.org; TECH-DISCUSS OPNFV
Subject: [opnfv-tech-discuss] [release][danube] MS6 compliance assessment

Team,

I'd like to request that the PTLs for projects participating in Danube respond 
to the following questions, designed to assess compliance with MS6.
Feature Projects
1.Please provide a list of commits for the following:
a. Enabling testing for your project in the Functest repo (or other test 
framework repo if you are not using functest)
b.Test case implementation in your project repo.
2.Please indicate whether the scenarios with which your project is 
integrated are visible on the Functest dashboard.  If not, why?
Test Framework Projects
1.Please provide a list of commits for your self-validation tests.
Preliminary Documentation Requirement
1.Please provide a link to the preliminary documentation for your project.


Let me know if you have any questions.

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [APEX] error while deploying dependency clash

[Nikolas Hermanns]

Hey,

I do have the following error when running apex deployment:
--> Finished Dependency Resolution
Error: Package: python2-pandas-0.19.1-2.el7.1.x86_64 (delorean-newton-testing)
   Requires: python2-numexpr
Error: Package: python2-pandas-0.19.1-2.el7.1.x86_64 (delorean-newton-testing)
   Requires: python2-pytz
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

I see that the pipeline has similar issues but some deps issues are fixed 
already:
https://build.opnfv.org/ci/job/apex-deploy-baremetal-os-odl_l3-nofeature-ha-master/91/console

--> Finished Dependency Resolution
Error: Package: python2-pandas-0.19.1-2.el7.x86_64 (delorean-newton-testing)
   Requires: python2-tables
Error: Package: python2-pandas-0.19.1-2.el7.x86_64 (delorean-newton-testing)
   Requires: python2-numexpr
Error: Package: python2-pandas-0.19.1-2.el7.x86_64 (delorean-newton-testing)
   Requires: python2-pytz
Error: Package: python2-pandas-0.19.1-2.el7.x86_64 (delorean-newton-testing)
   Requires: python2-Bottleneck
Error: Package: python2-pandas-0.19.1-2.el7.x86_64 (delorean-newton-testing)
   Requires: python2-dateutil
 You could try using --skip-broken to work around the problem

Is someone working on that/has a solution already?

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

[opnfv-tech-discuss] [3rd-party-odl-netvirt-ci] API abetween jenkins and script set

[Nikolas Hermanns]

Hey Fatih,

I have updated the wikipage with the info of how to start the 
odl-3rd-party-pipeline.

https://wiki.opnfv.org/display/INF/ODL+3rd+Party+CI

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

[opnfv-tech-discuss] [SDNVPN test Case fail criteria

[Nikolas Hermanns]

1.   We need to change the 75% test criteria for all test. That just makes 
thing more complicated. Can we copy the tests we have an rewrite them so that 
we don't need the criteria? Then we disable the first test and run them when 
the bug is fixed upstream.

2.   I think we should add a small check in the meta data of the VM is it 
got a ip. Greping for it or something similar. Or checking if it has at least a 
route to send the ping on. If it doesn't then we fail in any case. For a /24 ip 
to ping it would be something like:

a.   [[ $(route -n|awk '{print $1}') == *"192.168.122.0"* ]];
BR Nikolas

From: Skiadas Romanos [mailto:r...@intracom-telecom.com]
Sent: Friday, December 02, 2016 4:04 PM
To: BV Guravareddy
Cc: Nikolas Hermanns
Subject: RE: test Case fail criteria

The problem is that a VM not getting IP is not our issue per se. It causes us 
problems, but what we test is VPN connectivity.
We could have an assertion before each test that all the VMs must get an IP and 
then fail all of them, but then we fail to check if the VMs that got IPs had 
the correct VPN connectivity.

We could fail all the tests the specific VM participates in.
Eg. Vm1 doesn't get an IP, we should fail:
- Vm1 can ping vm2
- Vm1 cannot ping vm2
But not vm2 can ping vm2.

I think the first would be the easiest thing to implement but I don't know 
which is the saner thing to do. I've cc'd Niko so he can have a say in this.

In most tests we have 75% success criteria because isolation doesn't work. So 
one flipped fail and one flipped pass would still give the same success %, 
causing the overall tests to pass.

BR,
Romanos
From: BV Guravareddy [mailto:bv.guravare...@ericsson.com]
Sent: Friday, December 02, 2016 1:43 PM
To: Skiadas Romanos
Subject: test Case fail criteria

Hi Rom,

I have seen that some test cases are not having proper check for pass/fail 
Criteria. Please see the examples below.


1.   DHCP is not working, so instances will not get an IP address.

2.   Ping of VM-1 to VM-2  will not be success.

3.   But scenario like VM-1 should not be ping-able from VM-2 will PASS. 
Without even having  an IP address.  My suggestion is to Fail ALL test cases if 
VM is not having an IP address.

I am sure, we have success criteria of 100%. So it should not be an issue. 
Please feel free to  suggest.

Thanks & Regards,
Venkata Guravareddy.

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

Re: [opnfv-tech-discuss] [SDNVPN] Call for work item proposals and contributions for Danube release

[Nikolas Hermanns]

Hey,

Attached you will find the slide deck I talked about. Basically the quagga VM 
is just a forwarder and we do simulate an external datacenter GW.

Br Nikolas

From: Tim Irnich
Sent: Thursday, October 06, 2016 10:25 AM
To: opnfv-tech-discuss@lists.opnfv.org
Cc: Nikolas Hermanns; Prem sankar G; MORIN Thomas IMT/OLN 
(thomas.mo...@orange.com); HU, BIN (bh5...@att.com); r...@intracom-telecom.com; 
Jose Lausuch; geo...@intracom-telecom.com
Subject: [SDNVPN] Call for work item proposals and contributions for Danube 
release

Dear all,

The SDNVPN project is currently planning the work to be done in the Danube 
release. If you are interested in using/shaping the SDNVPN feature of OPNFV, 
please let us know your use case for consideration. If you are interested in 
making a contribution to the project, please let us know too.

Please respond on this thread or come to our weekly project meeting (Mondays, 
16:00 UTC). Visit our Wiki for more information 
https://wiki.opnfv.org/display/sdnvpn/Sdnvpn

The background of this request is that we are planning to change our way of 
working from Danube onwards. So far, we were driven by the use cases and 
features supported by our main upstream communities and focused on pulling a 
working system together, stabilizing auto-deployment and putting basic testing 
in place. Now that this is basically done, we think it's the right time to 
start identifying and prioritizing use cases from OPNFV community perspective 
and take that as the primary input to our prioritization.

Along with the use case we also plan to take an inventory of desired stack 
configuration options, so in case you have input on that please let us know too.

Best regards,

Tim (SDNVPN PTL)



new-ideas-sdnvpn-D-release.pptx
Description: new-ideas-sdnvpn-D-release.pptx
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss