[opnfv-tech-discuss] Technical Community Discussion Canceled Tomorrow (8/18)

[HU, BIN]

Hello community,



Sorry for the late notice.



There is no new project proposal in the backlog. And there is not urgent issue 
to discuss either.



So I propose to cancel our technical discussion tomorrow (8/18) so that 
everyone can focus on Colorado release, catch stable branch window, and meet 
documentation milestone.



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] A reminder on Committer-at-large TSC election

[Heather Kirksey]

And as we're closing out on the week, just another reminder  Also, do
please nominate yourself if you're interested. I think it's great that
folks have been showing their love for their fellow community members and
nominating each other, but I don't want that to make folks feel at all
uncomfortable about self-nominations. Don't be shy!

Heather

On Wed, Aug 17, 2016 at 8:21 PM, Raymond Paik 
wrote:

> All, this is a reminder that the nomination period for the
> Committer-at-large TSC election closes this Friday (Aug. 19th) at 5pm
> Pacific Time.
>
> In addition to nominating other committers to mailing lists, you're
> welcome to submit self-nominations at https://wiki.opnfv.org/
> display/DEV/2016+Commiters-at-Large+TSC+Election+Self-Nominations
>
> You can find the current list of accepted nominations at
> https://wiki.opnfv.org/display/DEV/Accepted+Nominations+for+2016+
> Committer-at-Large+TSC+election
>
> Thanks,
>
> Ray
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>


-- 
*Heather Kirksey*
Director, OPNFV
Mobile: +1.512.917.7938
Email/Google Talk: hkirk...@linuxfoundation.org
Skype: HeatherReneeKirksey
IRC: HKirksey

[image: OPNFV_RGB.png]
___
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] How to config the VSPerf and Moongen correctly.

[David XF1 Cui]

Hi Bill,

Yes. I can get MoonGen  running indpendently on a PC without VSPERF enviroment 
referred to the MoonGenSetUp.html. Currently, I set the VSWITCH config to 
'OvsVanilla' to debug the OVS which not using the DPDK.  Could I need to config 
the MoonGen on the another PC. I use the defual config file: opnfv-vsperf.lua?


Thanks & BRs
David

From: Bill Michalowski [mailto:bmich...@redhat.com]
Sent: Wednesday, August 17, 2016 10:33 PM
To: David XF1 Cui
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [VSPERF] How to config the VSPerf and Moongen 
correctly.

Hi David:
Let's break this down and see if you can get MoonGen running outside of the 
VSPERF infrastructure first.  Once that's done, we will try to get the 
phy2phy_tput tests running.
Please refer to the instructions within the MoonGenSetUp.html file on the 
MoonGen side and see if you have any success passing data.
Regards,
Bill
- Original Message -
From: David XF1 Cui mailto:cui...@lenovo.com>>
To: 
opnfv-tech-discuss@lists.opnfv.org
Sent: Mon, 15 Aug 2016 18:39:52 -0400 (EDT)
Subject: Re: [opnfv-tech-discuss] [VSPERF] How to config the VSPerf and Moongen 
correctly.
Sorry, I forget the log files. Attach again.

From: David XF1 Cui
Sent: Tuesday, August 16, 2016 6:34 AM
To: 'opnfv-tech-discuss@lists.opnfv.org'
Subject: [VSPERF] How to config the VSPerf and Moongen correctly.

Hi guys,

Sorry for troubling you. I try to setup a test environment use VSPerf and 
MoonGen to benchmark the performance of OVS.  I use two PCs to setup the 
environment, one for VSPerf and another for MoonGen. I run the phy2phy_tput
test on the VSPerf side.  But I can not get the correct test result. I attached 
the configurations and logs here. Could you help me to check if I config the 
VSperf and Moongen correctly?

Thanks & BRs
David

some logs as below

[INFO ]  2016-08-16 06:20:14,908 : (moongen) - In moongen 
send_rfc2544_throughput method
[INFO ]  2016-08-16 06:20:14,908 : (moongen) - In Moongen traffic_defaults 
method
[DEBUG]  2016-08-16 06:20:14,908 : (root) - traffic['frame_rate'] = 100
[DEBUG]  2016-08-16 06:20:14,908 : (root) - traffic['multistream'] = 0
[DEBUG]  2016-08-16 06:20:14,908 : (root) - traffic['stream_type'] = L2
[DEBUG]  2016-08-16 06:20:14,908 : (root) - traffic['l2']['srcmac'] = 
6c:0b:84:45:4b:53
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l2']['dstmac'] = 
6c:0b:84:dd:ed:07
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l3']['proto'] = udp
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l3']['srcip'] = 
10.100.206.96
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l3']['dstip'] = 
10.100.203.102
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l4']['srcport'] = 3000
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l4']['dstport'] = 3001
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['vlan']['enabled'] = False
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['vlan']['id'] = 0
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['vlan']['priority'] = 0
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['vlan']['cfi'] = 0
[DEBUG]  2016-08-16 06:20:14,909 : (root) - 64
[DEBUG]  2016-08-16 06:20:14,909 : (root) - startRate = 14.880952380952381
opnfv-vsperf-cfg.lua
 
100%  297 0.3KB/s   00:00
2016-08-15T22:20:15Z|00056|poll_loop|INFO|wakeup due to [POLLIN] on fd 37 (FIFO 
pipe:[1366939]) at lib/netdev.c:1918 (78% CPU usage)
moongen_log.txt 
 
100%0 0.0KB/s   00:00
[ERROR]  2016-08-16 06:20:15,296 : (root) - There was a problem parsing Moongen 
REPORT section of Moongen log file
[ERROR]  2016-08-16 06:20:15,296 : (root) - There was a problem parsing Moongen 
PARAMETERS section of Moongen log file
…
2016-08-15T22:20:15Z|00061|poll_loop|INFO|wakeup due to [POLLIN] on fd 37 (FIFO 
pipe:[1366939]) at lib/netdev.c:1918 (78% CPU usage)
2016-08-15T22:20:16Z|00062|poll_loop|INFO|wakeup due to [POLLIN] on fd 37 (FIFO 
pipe:[1366939]) at lib/netdev.c:1918 (78% CPU usage)
2016-08-15T22:20:16Z|00063|poll_loop|INFO|wakeup due to [POLLIN] on fd 37 (FIFO 
pipe:[1366939]) at lib/netdev.c:1918 (78% CPU usage)
2016-08-15T22:20:17Z|00064|poll_loop|INFO|wakeup due to [POLLIN] on fd 37 (FIFO 
pipe:[1366939]) at lib/netdev.c:1918 (78% CPU usage)
[DEBUG]  2016-08-16 06:20:17,316 : (core.vnf_controller) - stop 0 VNF[s] with
[DEBUG]  2016-08-16 06:20:17,316 : (core.vswitch_controller_p2p) - Stop using 

[INFO ]  2016-08-16 06:20:17,316 : (ovs_dpdk_vhost) - Terminating vswitchd...
[INFO ]  2016-08-16 06:20:17,316 : (ovs_dpdk_vhost) - Killing ovs-vswitchd...
[DEBUG]  2016-08-16 06:20:17,317 : (ovs_dpdk_vhost) - cmd : sudo k

[opnfv-tech-discuss] A reminder on Committer-at-large TSC election

[Raymond Paik]

All, this is a reminder that the nomination period for the
Committer-at-large TSC election closes this Friday (Aug. 19th) at 5pm
Pacific Time.

In addition to nominating other committers to mailing lists, you're welcome
to submit self-nominations at
https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Large+TSC+Election+Self-Nominations

You can find the current list of accepted nominations at
https://wiki.opnfv.org/display/DEV/Accepted+Nominations+for+2016+Committer-at-Large+TSC+election

Thanks,

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

[opnfv-tech-discuss] Shout out: Julien Zhang

[Jack Morgan]

OPNFV,

I would like to take a moment to recognize Julien Zhang for his hard
work and dedication during this Colorado release cycle. I really
appreciate his input even though I as the Pharos PTL didn't provide much
direction. Julien worked the JIRA issues in his name and created new
ones when needed. He tirelessly focused on getting things done this
cycle and even harassed me several times to approve his Gerrit hanges. I
hope to be more like him moving forward.

Since Julien is currently a contributor to the Pharos project, I'm going
to recommend he be a committer via Gerrit. Please consider his
nomination and add your +1 in Gerrit.


Thanks,

-- 
Jack Morgan
OPNFV Pharos Intel Lab

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

[opnfv-tech-discuss] [Infra] New INFRA JIRA project

[Jack Morgan]

OPNFV,

I would like to announcea new JIRA project "INFRA". This project will be
used to track user lab requestsinstead of the Pharos JIRA project. This
helps us by reducing the scope of the Pharos JIRA project to just
tracking release related efforts. Then David can track actual JIRA
issues per release and not have them "inflated" by user lab requests.

I've already created the same component fields in the INFRA JIRA project
that are in the Pharos JIRA project. Please use this new JIRA project
for future user lab requests. I'm also providing a link to documentation
on how to submit a user request. This document will improve over time. 

INFRA JIRA project: https://jira.opnfv.org/projects/INFRA/summary
Submitting requests: https://wiki.opnfv.org/display/INF/Jira+and+Confluence


There are still about 20 user lab requests in the Pharos JIRA project.
You can find them via this query:
https://jira.opnfv.org/issues/?filter=11136

Please take a moment to update our status or close them. If you need to
help with do so, let me know. I will automatically migrate any remaining
JIRA issue in that query to the INFRA JIRA project in two weeks. Any new
user lab requests created in the Pharos JIRA project will automatically
get migrated to the INFRA JIRA project moving forward.


Thanks in advance for your help,

-- 
Jack Morgan
OPNFV Pharos Intel Lab

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

[opnfv-tech-discuss] Infra WG meeting minutes Aug. 17th

[Jack Morgan]

  
  

  

Aug 17th
Opens

  Scenarios running on ARM based Pharos POD (Jack)
  Rotating meeting chair going forward

  On a monthly/2-monthly basis for example

  
  Docs team needs help with creating PDF files (Chris)

Discussion

  Review previous weeks task list & discuss status  

Meeting minutes: http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-08-17-15.01.html

  rotating this meeting

  Fatih will take over running this
  meeting from the week after next (Aug. 31st)

  we agree to two month rotations by PTLs
  (Genesis, Octopus, Pharos, Releng) 


  
  docs team needs resources to create pdf
  files somewhere within the OPNFV community

  Chris mentions docs team is looking 3rd
  party company to do this and create hardware resources
  (VM)
  Franks suggest dropping PDF support as
  a 3rd option
  Fatih mentions that html only docs
  doesn't have good version control

  
  senario running on ARM based Pharos POD  

  David gives a summary topic which
  includes that we have an ARM specific hardware  
  so tracking ARM specific senario
  results is what needs to be discussed  
  Chris asks what do we want to track for
  the release?   
  a few mention that we have more then
  two architectures since each lab has different  

  

Actions Items:

  

  Christopher Price to work on long term
plan for html only documentation
  Jack Morgan to create a simple
template for all labs and push to gerrit
  David McBride to make sure this is
included in release milestones as a checkpoint

  


-- 
Jack Morgan
OPNFV Pharos Intel Lab
  

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

Re: [opnfv-tech-discuss] [opnfvdocs] doumentation link patch?

[David McBride]

+Sofia

On Tue, Aug 16, 2016 at 6:50 PM, joehuang  wrote:

> Multisite documentation is ready for configuration guide, installation
> guide and user guide. https://git.opnfv.org/cgit/opnfvdocs/tree/docs
>
> I am confused with the https://wiki.opnfv.org/display/DOC/Userguide,
> https://wiki.opnfv.org/display/DOC/Configurartion+guide,
> https://wiki.opnfv.org/display/DOC/Installation+procedure
>
> Should we submit a pacth in OPNFV doc git repository to include multisite
> documentation? In release B, only need to submit documentation to Multisite
> project folder, and then the documentation is merged automatically in OPNFV
> documentation.
>
> Look forward to your reply. Thanks
>
> Best Regards
> Chaoyi Huang(joehuang)
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>


-- 
*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] [VSPERF] Weekly call August 17th 2016

[Tahhan, Maryam]

Hi Folks

Today's meeting minutes can be found here: 
https://wiki.opnfv.org/display/meetings/Vsperf

*Action items*
  * Maryam to create a wiki where we can start collecting features for OPNFV 
release D --> Done 
https://wiki.opnfv.org/display/vsperf/Vswitch+Work+Items#VswitchWorkItems-RELEASED
 
  Note: I took any leftovers from C and started to populate the table... we 
can prioritize them later.
  * vsperf community to add stories for the august sprint by EOD Fri 19th Aug 
2016 (sprint will be kicked off Monday)
  * vsperf community to add features to this wiki over the next 3 weeks

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

[opnfv-tech-discuss] Security Audit Discussions

[Luke Hinds]

Hi,

As discussed on today's call, and etherpad to start to flesh out what a
security audit would consist of   for each release. This then gets
discussed next week on the TSC.

https://etherpad.opnfv.org/p/sec-audit

Regards,
Luke

-- 
Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44
12 52 36 2483
___
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] How to config the VSPerf and Moongen correctly.

[Bill Michalowski]

Hi David:

Let's break this down and see if you can get MoonGen running outside of the 
VSPERF infrastructure first.  Once that's done, we will try to get the 
phy2phy_tput tests running.

Please refer to the instructions within the MoonGenSetUp.html file on the 
MoonGen side and see if you have any success passing data.

Regards,
Bill


- Original Message -From: David XF1 Cui To: 
opnfv-tech-discuss@lists.opnfv.orgSent: Mon, 15 Aug 2016 18:39:52 -0400 
(EDT)Subject: Re: [opnfv-tech-discuss] [VSPERF] How to config the VSPerf and 
Moongen correctly.


Sorry, I forget the log files. Attach again.
 


From: David XF1 Cui

Sent: Tuesday, August 16, 2016 6:34 AMTo: 
'opnfv-tech-discuss@lists.opnfv.org'Subject: [VSPERF] How to config the VSPerf 
and Moongen correctly.


 
Hi guys, 
 
Sorry for troubling you. I try to setup a test environment use VSPerf and 
MoonGen to benchmark the performance of OVS.  I use two PCs to setup the 
environment, one for VSPerf and another for MoonGen. I run the phy2phy_tput 
test on the VSPerf side.  But I can not get the correct test result. I attached 
the configurations and logs here. Could you help me to check if I config the 
VSperf and Moongen correctly?
 
Thanks & BRs
David
 
some logs as below

[INFO ]  2016-08-16 06:20:14,908 : (moongen) - In moongen 
send_rfc2544_throughput method
[INFO ]  2016-08-16 06:20:14,908 : (moongen) - In Moongen traffic_defaults 
method
[DEBUG]  2016-08-16 06:20:14,908 : (root) - traffic['frame_rate'] = 100
[DEBUG]  2016-08-16 06:20:14,908 : (root) - traffic['multistream'] = 0
[DEBUG]  2016-08-16 06:20:14,908 : (root) - traffic['stream_type'] = L2
[DEBUG]  2016-08-16 06:20:14,908 : (root) - traffic['l2']['srcmac'] = 
6c:0b:84:45:4b:53
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l2']['dstmac'] = 
6c:0b:84:dd:ed:07
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l3']['proto'] = udp
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l3']['srcip'] = 
10.100.206.96
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l3']['dstip'] = 
10.100.203.102
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l4']['srcport'] = 3000
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['l4']['dstport'] = 3001
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['vlan']['enabled'] = False
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['vlan']['id'] = 0
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['vlan']['priority'] = 0
[DEBUG]  2016-08-16 06:20:14,909 : (root) - traffic['vlan']['cfi'] = 0
[DEBUG]  2016-08-16 06:20:14,909 : (root) - 64
[DEBUG]  2016-08-16 06:20:14,909 : (root) - startRate = 14.880952380952381
opnfv-vsperf-cfg.lua
 
100%  297 0.3KB/s   00:00   
2016-08-15T22:20:15Z|00056|poll_loop|INFO|wakeup due to [POLLIN] on fd 37 (FIFO 
pipe:[1366939]) at lib/netdev.c:1918 (78% CPU usage)
moongen_log.txt 
 
100%0 0.0KB/s   00:00   
[ERROR]  2016-08-16 06:20:15,296 : (root) - There was a problem parsing Moongen 
REPORT section of Moongen log file
[ERROR]  2016-08-16 06:20:15,296 : (root) - There was a problem parsing Moongen 
PARAMETERS section of Moongen log file
…
2016-08-15T22:20:15Z|00061|poll_loop|INFO|wakeup due to [POLLIN] on fd 37 (FIFO 
pipe:[1366939]) at lib/netdev.c:1918 (78% CPU usage)
2016-08-15T22:20:16Z|00062|poll_loop|INFO|wakeup due to [POLLIN] on fd 37 (FIFO 
pipe:[1366939]) at lib/netdev.c:1918 (78% CPU usage)
2016-08-15T22:20:16Z|00063|poll_loop|INFO|wakeup due to [POLLIN] on fd 37 (FIFO 
pipe:[1366939]) at lib/netdev.c:1918 (78% CPU usage)
2016-08-15T22:20:17Z|00064|poll_loop|INFO|wakeup due to [POLLIN] on fd 37 (FIFO 
pipe:[1366939]) at lib/netdev.c:1918 (78% CPU usage)
[DEBUG]  2016-08-16 06:20:17,316 : (core.vnf_controller) - stop 0 VNF[s] with
[DEBUG]  2016-08-16 06:20:17,316 : (core.vswitch_controller_p2p) - Stop using 

[INFO ]  2016-08-16 06:20:17,316 : (ovs_dpdk_vhost) - Terminating vswitchd...
[INFO ]  2016-08-16 06:20:17,316 : (ovs_dpdk_vhost) - Killing ovs-vswitchd...
[DEBUG]  2016-08-16 06:20:17,317 : (ovs_dpdk_vhost) - cmd : sudo kill -15 1599
2016-08-15T22[DEBUG]  2016-08-16 06:20:17,321 : (ovs_dpdk_vhost) - Wait for 
process 1599 to terminate after signal -15
:20:17Z|00065|poll_loop|INFO|wakeup due to [POLLIN] on fd 5 (FIFO 
pipe:[1353374]) at lib/fatal-signal.c:224 (78% CPU usage)
2016-08-15T22:20:17Z|1|fatal_signal(revalidator8)|WARN|terminating with 
signal 15 (Terminated)
[INFO ]  2016-08-16 06:20:18,322 : (ovs_dpdk_vhost) - Killing ovsdb with pid: 
1578
[DEBUG]  2016-08-16 06:20:18,322 : (ovs_dpdk_vhost) - cmd : sudo kill -15 1578
2016-08-15T22:20:18Z|2|fatal_signal|WARN|terminating with signal 15 
(Terminated)
[DEBUG]  2016-08-16 06:20:18,3

Re: [opnfv-tech-discuss] [VSPERF] support CLI for all configuration parameters

[Bill Michalowski]

+1

I like it.

- Bill

- Original Message -From: Christian Trautman To: 
MartinX Klozik Cc: 
opnfv-tech-discuss@lists.opnfv.orgSent: Wed, 17 Aug 2016 10:05:01 -0400 
(EDT)Subject: Re: [opnfv-tech-discuss] [VSPERF] support CLI for all 
configuration parameters


+1

This would be extremely helpful for our CI scripts.

-Christian,


From: "MartinX Klozik" To: 
opnfv-tech-discuss@lists.opnfv.orgSent: Monday, August 15, 2016 9:18:07 
AMSubject: [opnfv-tech-discuss] [VSPERF] support CLI for all configuration  
  parameters


Hi Folks,
 
Currently VSPERF uses a lot of configuration options spread among several 
configuration files, but only a few of them are configurable “on the 
fly” by CLI option –test-params. During the past, there were 
several requirements to allow a CLI modification of various configuration 
options. So in these days some of them can be modified, but it is hard to find, 
which one (one have to consult documentation related to the specific feature).
 
What about a change which will allow to modify any option by CLI (and 
“Parameters” option of testcase definition)? It means, that for any 
configuration option (by default UPPER case name) its lower case form can be 
used to redefine the value through –test-params argument.
 

In a nutshell following patch will do the trick:
 

diff --git a/conf/__init__.py b/conf/__init__.py
index 4622823..d4332ac 100644
--- a/conf/__init__.py
+++ b/conf/__init__.py
@@ -34,7 +34,11 @@ class Settings(object):
 """Return a settings item value
 """
 if attr in self.__dict__:
-return getattr(self, attr)
+if attr == 'TEST_PARAMS':
+return getattr(self, attr)
+else:
+# Check if parameter value was overridden by CLI option
+return get_test_param(attr.lower(), getattr(self, attr))
 else:
 raise AttributeError("%r object has no attribute %r" %

  (self.__class__, attr))

 
Let me know what do you think (e.g. reply with +1).
 
If you’ll find it useful, I’ll create a ticket for that and prepare 
a patch. The final patch have to take into the account currently supported CLI 
parameters (i.e. code cleanup & type conversion/checking & testing).
 
Best Regards,
Martin

-- Intel Research 
and Development Ireland Limited Registered in Ireland Registered Office: 
Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263
This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies.

___opnfv-tech-discuss mailing 
listopnfv-tech-discuss@lists.opnfv.orghttps://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] [VSPERF] support CLI for all configuration parameters

[Christian Trautman]

+1 

This would be extremely helpful for our CI scripts. 

-Christian, 

- Original Message -

From: "MartinX Klozik"  
To: opnfv-tech-discuss@lists.opnfv.org 
Sent: Monday, August 15, 2016 9:18:07 AM 
Subject: [opnfv-tech-discuss] [VSPERF] support CLI for all configuration 
parameters 



Hi Folks, 



Currently VSPERF uses a lot of configuration options spread among several 
configuration files, but only a few of them are configurable “on the fly” by 
CLI option –test-params. During the past, there were several requirements to 
allow a CLI modification of various configuration options. So in these days 
some of them can be modified, but it is hard to find, which one (one have to 
consult documentation related to the specific feature). 



What about a change which will allow to modify any option by CLI (and 
“Parameters” option of testcase definition)? It means, that for any 
configuration option (by default UPPER case name) its lower case form can be 
used to redefine the value through –test-params argument. 




In a nutshell following patch will do the trick: 




diff --git a/conf/__init__.py b/conf/__init__.py 

index 4622823..d4332ac 100644 

--- a/conf/__init__.py 

+++ b/conf/__init__.py 

@@ -34,7 +34,11 @@ class Settings(object): 

"""Return a settings item value 

""" 

if attr in self.__dict__: 

- return getattr(self, attr) 

+ if attr == 'TEST_PARAMS': 

+ return getattr(self, attr) 

+ else: 

+ # Check if parameter value was overridden by CLI option 

+ return get_test_param(attr.lower(), getattr(self, attr)) 

else: 

raise AttributeError("%r object has no attribute %r" % 


(self.__class__, attr)) 




Let me know what do you think (e.g. reply with +1). 



If you’ll find it useful, I’ll create a ticket for that and prepare a patch. 
The final patch have to take into the account currently supported CLI 
parameters (i.e. code cleanup & type conversion/checking & testing). 



Best Regards, 

Martin 


-- 
Intel Research and Development Ireland Limited 
Registered in Ireland 
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare 
Registered Number: 308263 

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies. 



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

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

Re: [opnfv-tech-discuss] [SFC] multiple compute nodes with Tacker

[Manuel Buil]

Ok. Great! BTW, do you know when will RC0 be released? It should have been out 
last week.

Regards,
Manuel

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com] 
Sent: Wednesday, August 17, 2016 3:27 PM
To: Manuel Buil
Cc: Yi Y Yang; Sam Hague; Brady Allen Johnson; OPNFV Tech
Subject: Re: [SFC] multiple compute nodes with Tacker

Hey Manuel,
I spoke with Sam a bit yesterday.  It looks like we need a change in the 
classifier code.  The classifier code is comparing the SFF DPL IP to the 
other_config:local_ip of br-int.  Which is 192.0.2.x compared to 11.0.0.x and 
fails, so the classifier thinks the SFF is not on the same node.  Sam should be 
coming up with a new build to try soon.

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Manuel Buil" 
To: "Tim Rozet" 
Cc: "Yi Y Yang" , "Sam Hague" , "Brady 
Allen Johnson" , "OPNFV Tech" 

Sent: Wednesday, August 17, 2016 3:24:47 AM
Subject: RE: [SFC] multiple compute nodes with Tacker

Hi Tim,

You are hitting the bug we informed you guys about.

When the classifier and the first SF are "in the same OVS", the action of the 
classification flow should be resubmit($vxlan_gpe_port,0) instead of 
output:$vxlan_gpe_port. 

I don't have all the details as Brady was looking into this but apparently 
Netvirt compares the IP of the SFF with the IP of the SFF that tacker sees for 
the first SF. If they are the same, Netvirt will instruct the resubmit action 
instead of the output action. However, Tacker and Netvirt are checking the IP 
on different interfaces of the host where the SFF is running, so the result of 
the comparison is always false.

Until that bug is fixed, I am modifying that flow with a script so that the 
OPNFV CI test cases work. This is the script:

https://github.com/manuelbuil/sfc-work/blob/master/configure_first_classifier_ovs25.sh

Regards,
Manuel


-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com]
Sent: Tuesday, August 16, 2016 7:58 PM
To: Manuel Buil
Cc: Yi Y Yang; Sam Hague; Brady Allen Johnson; OPNFV Tech
Subject: Re: [SFC] multiple compute nodes with Tacker

Hi Manuel,
Thanks for hte info.  I enabled the vxlan workaround routes and attempted the 
curl again.  I saw 2 packets hit the vxlan tool on the VNFs, but curl failed 
and the rest of the packets did not make it through.  Updated gist with flows:

https://gist.github.com/trozet/d6547cdc416a27ef7cf5b6c6b91db5cd

ofctl Port mapping:
compute1:
port 4) tap43c21e37 - TestVNF4 (first VNF in chain)
port 6) tape118a- http client

compute0:
port 6) tap867682340-80 - TestVNF5 (second VNF in chain)
port 7) - HTTP server

Main flow here to look at here is the classifier:

cookie=0x1110010001610255, duration=78031.957s, table=11, n_packets=27, 
n_bytes=1998, tcp,reg0=0x1,tp_src=2000,tp_dst=80 
actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_NSH_C2[],push_nsh,load:0x1->NXM_NX_NSH_MDTYPE[],load:0x3->NXM_NX_NSH_NP[],load:0xc20a->NXM_NX_NSH_C1[],load:0xa1->NXM_NX_NSP[0..23],load:0xff->NXM_NX_NSI[],load:0xc203->NXM_NX_TUN_IPV4_DST[],load:0xa1->NXM_NX_TUN_ID[0..31],output:5

It looks like it is skipping the first SFF.  I think that should send to the 
SFF (compute1, same compute, so maybe just resubmit or goto table) and then 
progress into SFC tables.

Sam, can you comment here?

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Manuel Buil" 
To: "Tim Rozet" , "Yi Y Yang" , "Sam 
Hague" 
Cc: "Brady Allen Johnson" , "OPNFV Tech" 

Sent: Tuesday, August 16, 2016 3:40:49 AM
Subject: RE: [SFC] multiple compute nodes with Tacker

Hi Tim,

You still need to do the vxlan workaround. OVS 2.5.90 supports two 
alternatives: eth+nsh or vxlan-gpe+eth+nsh between SF <> SFF. However, ODL 
is currently not capable to render the first one, so we need to do the 
vxlan-gpe+eth+nsh and thus, the workaround. Brady started to implement the 
support for eth+nsh but he did not manage to do it before his vacations. 
Hopefully, we'll get that in September.

Regards,
Manuel

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com]
Sent: Monday, August 15, 2016 11:39 PM
To: Manuel Buil; Yi Y Yang; Sam Hague
Cc: Brady Allen Johnson; OPNFV Tech
Subject: [SFC] multiple compute nodes with Tacker

Expanding to larger audience...

I tested out Apex today with the ODL build Brady provided.  I found there were 
a few updates needed in Tacker and pushed a patch to the colorado branch:
https://github.com/trozet/tacker/commit/d876584242781726d2e4403e69b9d15c08765625

I then created the following nova instances/tacker VNFs:
https://goo.gl/photos/F59h6V31fcQSzVFt6

The chain I created was this:
testVNF4->testVNF5

The curl to the http server failed (typical classifier matching on source port 
2000, dest port 80), and I don't see any packets hitting the vxlan tool on 
either VNF.  However, I do see packets hitting the classifier.  Flow gist:
https://gist.github.com/trozet/3161092c62fdc6582508e7779e445bf1

I did not use the VXLAN workaround (aka

Re: [opnfv-tech-discuss] [SFC] multiple compute nodes with Tacker

[Tim Rozet]

Hey Manuel,
I spoke with Sam a bit yesterday.  It looks like we need a change in the 
classifier code.  The classifier code is comparing the SFF DPL IP to the 
other_config:local_ip of br-int.  Which is 192.0.2.x compared to 11.0.0.x and 
fails, so the classifier thinks the SFF is not on the same node.  Sam should be 
coming up with a new build to try soon.

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Manuel Buil" 
To: "Tim Rozet" 
Cc: "Yi Y Yang" , "Sam Hague" , "Brady 
Allen Johnson" , "OPNFV Tech" 

Sent: Wednesday, August 17, 2016 3:24:47 AM
Subject: RE: [SFC] multiple compute nodes with Tacker

Hi Tim,

You are hitting the bug we informed you guys about.

When the classifier and the first SF are "in the same OVS", the action of the 
classification flow should be resubmit($vxlan_gpe_port,0) instead of 
output:$vxlan_gpe_port. 

I don't have all the details as Brady was looking into this but apparently 
Netvirt compares the IP of the SFF with the IP of the SFF that tacker sees for 
the first SF. If they are the same, Netvirt will instruct the resubmit action 
instead of the output action. However, Tacker and Netvirt are checking the IP 
on different interfaces of the host where the SFF is running, so the result of 
the comparison is always false.

Until that bug is fixed, I am modifying that flow with a script so that the 
OPNFV CI test cases work. This is the script:

https://github.com/manuelbuil/sfc-work/blob/master/configure_first_classifier_ovs25.sh

Regards,
Manuel


-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com] 
Sent: Tuesday, August 16, 2016 7:58 PM
To: Manuel Buil
Cc: Yi Y Yang; Sam Hague; Brady Allen Johnson; OPNFV Tech
Subject: Re: [SFC] multiple compute nodes with Tacker

Hi Manuel,
Thanks for hte info.  I enabled the vxlan workaround routes and attempted the 
curl again.  I saw 2 packets hit the vxlan tool on the VNFs, but curl failed 
and the rest of the packets did not make it through.  Updated gist with flows:

https://gist.github.com/trozet/d6547cdc416a27ef7cf5b6c6b91db5cd

ofctl Port mapping:
compute1:
port 4) tap43c21e37 - TestVNF4 (first VNF in chain)
port 6) tape118a- http client

compute0:
port 6) tap867682340-80 - TestVNF5 (second VNF in chain)
port 7) - HTTP server

Main flow here to look at here is the classifier:

cookie=0x1110010001610255, duration=78031.957s, table=11, n_packets=27, 
n_bytes=1998, tcp,reg0=0x1,tp_src=2000,tp_dst=80 
actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_NSH_C2[],push_nsh,load:0x1->NXM_NX_NSH_MDTYPE[],load:0x3->NXM_NX_NSH_NP[],load:0xc20a->NXM_NX_NSH_C1[],load:0xa1->NXM_NX_NSP[0..23],load:0xff->NXM_NX_NSI[],load:0xc203->NXM_NX_TUN_IPV4_DST[],load:0xa1->NXM_NX_TUN_ID[0..31],output:5

It looks like it is skipping the first SFF.  I think that should send to the 
SFF (compute1, same compute, so maybe just resubmit or goto table) and then 
progress into SFC tables.

Sam, can you comment here?

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Manuel Buil" 
To: "Tim Rozet" , "Yi Y Yang" , "Sam 
Hague" 
Cc: "Brady Allen Johnson" , "OPNFV Tech" 

Sent: Tuesday, August 16, 2016 3:40:49 AM
Subject: RE: [SFC] multiple compute nodes with Tacker

Hi Tim,

You still need to do the vxlan workaround. OVS 2.5.90 supports two 
alternatives: eth+nsh or vxlan-gpe+eth+nsh between SF <> SFF. However, ODL 
is currently not capable to render the first one, so we need to do the 
vxlan-gpe+eth+nsh and thus, the workaround. Brady started to implement the 
support for eth+nsh but he did not manage to do it before his vacations. 
Hopefully, we'll get that in September.

Regards,
Manuel

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com]
Sent: Monday, August 15, 2016 11:39 PM
To: Manuel Buil; Yi Y Yang; Sam Hague
Cc: Brady Allen Johnson; OPNFV Tech
Subject: [SFC] multiple compute nodes with Tacker

Expanding to larger audience...

I tested out Apex today with the ODL build Brady provided.  I found there were 
a few updates needed in Tacker and pushed a patch to the colorado branch:
https://github.com/trozet/tacker/commit/d876584242781726d2e4403e69b9d15c08765625

I then created the following nova instances/tacker VNFs:
https://goo.gl/photos/F59h6V31fcQSzVFt6

The chain I created was this:
testVNF4->testVNF5

The curl to the http server failed (typical classifier matching on source port 
2000, dest port 80), and I don't see any packets hitting the vxlan tool on 
either VNF.  However, I do see packets hitting the classifier.  Flow gist:
https://gist.github.com/trozet/3161092c62fdc6582508e7779e445bf1

I did not use the VXLAN workaround (aka the kernel host route).  I thought this 
was not required anymore with OVS 2.5.90.  Yi can you comment here?

I haven't had a chance to dig into the flows yet, but if anyone sees the root 
cause of the problem, let me know.

Thanks,

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Manuel Buil" 
To: "Tim Rozet" 
Cc: "Brady Allen Jo

Re: [opnfv-tech-discuss] [Infra] Infra WG weekly meeting

[Christopher Price]

“it would be good to have rotation for the meeting chair”

 

+1

 

From:  on behalf of Fatih 
Degirmenci 
Date: Wednesday 17 August 2016 at 15:00
To: Jack Morgan , TECH-DISCUSS OPNFV 

Subject: Re: [opnfv-tech-discuss] [Infra] Infra WG weekly meeting

 

Hi Jack,

 

I can take over the Infra WG meetings, starting from week after next.

 

Apart from this, it would be good to have rotation for the meeting chair so we 
don't always talk about certain areas but have chance to touch upon different 
areas. Added this into the agenda for today's meeting.

 

/Fatih

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
 on behalf of Jack Morgan 

Sent: 16 August 2016 21:06:13
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [Infra] Infra WG weekly meeting 

 

All,

I need to step down from leading this meeting for a while so I can focus
on the Pharos project. Can one of other PTL's lead it? Fatih(Releng)?
Uli(Octopus)? Frank(Genesis)?


thanks,

-- 
Jack Morgan
OPNFV Pharos Intel Lab

___
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] [Infra] Infra WG weekly meeting

[Fatih Degirmenci]

Hi Jack,


I can take over the Infra WG meetings, starting from week after next.


Apart from this, it would be good to have rotation for the meeting chair so we 
don't always talk about certain areas but have chance to touch upon different 
areas. Added this into the agenda for today's meeting.


/Fatih


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
 on behalf of Jack Morgan 

Sent: 16 August 2016 21:06:13
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [Infra] Infra WG weekly meeting

All,

I need to step down from leading this meeting for a while so I can focus
on the Pharos project. Can one of other PTL's lead it? Fatih(Releng)?
Uli(Octopus)? Frank(Genesis)?


thanks,

--
Jack Morgan
OPNFV Pharos Intel Lab

___
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] [Functest] reporting page doc

[morgan.richomme]

Hi,

I created a wiki page to detail the reporting page and explain how
Functest scoring is calculated:
https://wiki.opnfv.org/pages/viewpage.action?pageId=6828617

/Morgan



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

Re: [opnfv-tech-discuss] Meeting Cancelled 8/18

[MORTON, ALFRED C (AL)]

Thanks for letting us know, Daniel,
enjoy your time in the backcountry, un-plugged!


Nikos:  Are you on holiday this week?
If you are available, I would like to use the time
to discuss some measurements with Latte 
(now working for me as of Tuesday this week, with some tweaks).

Al

> -Original Message-
> From: Daniel Farrell [mailto:dfarr...@redhat.com]
> Sent: Wednesday, August 17, 2016 3:41 AM
> To: 'integration-...@lists.opendaylight.org' (integration-
> d...@lists.opendaylight.org) (integration-...@lists.opendaylight.org);
> TECH-DISCUSS OPNFV
> Cc: MORTON, ALFRED C (AL); Luis Gomez; Nikos Anastopoulos; Jamo Luhrsen;
> Marcus Williams
> Subject: [cperf] Meeting Cancelled 8/18
> 
> Hello CPerf,
> 
> I'll be in the backcountry with no networking Wed-Friday.
> 
> You all are welcome to meet without me, but I'm going to assume
> we'll cancel for now. We can cover relevant work in the Integration
> and S3P calls, or via email/IRC.
> 
> Thanks,
> 
> Daniel Farrell
> Software Engineer, Red Hat SDN Team
> https://wiki.opendaylight.org/view/user:dfarrell07

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

[opnfv-tech-discuss] [bottlenecks] bottlenecks weekly meeting 08-18 (1:00-2:00 UTC, Thursday, 9:00-10:00 Beijing Time, Thursday, PDT 18:00-19:00 Wednesday )

[Yuyang (Gabriel)]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Australia Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Yuyang (Gabriel):MAILTO:gabriel.yuy...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Tianhongbo
 :MAILTO:hongbo.tianhon...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lijun (Mat
 thew):MAILTO:matthew.li...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=liangqi (D
 ):MAILTO:liang...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Liyiting:M
 AILTO:liyit...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=mrebellon@
 sandvine.com:MAILTO:mrebel...@sandvine.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wangyaogua
 ng (A):MAILTO:sunshine.w...@huawei.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=zh-CN:Hi\,\n\nThe Bottlenecks weekly meeting will be h
 eld at 1:00-2:00 UTC\, Thursday\, 9:00-10:00 Beijing Time\, Thursday\, PDT
  18:00-19:00 Wednesday.\nWelcome to join our discussion. Details of this m
 eeting are shown below.\n[X]\nAgenda:\n1.  Bottlenecks Colorado Discus
 sion\n2.  Metrics & Tools Discussion for the Proposals\n\nMeeting Reso
 urces\n\nPlease join the meeting from your computer\, tablet or smartphone
 .\nhttps://global.gotomeeting.com/join/882532573\n\nYou can also dial in u
 sing your phone.\nUnited States (Toll-free): 1 877 309 2070\nUnited States
  : +1 (312) 757-3119\n\n\nAccess Code: 882-532-573\n[X]\nBest\,\nYang\n\n\
 n
SUMMARY;LANGUAGE=zh-CN:[bottlenecks] bottlenecks weekly meeting 08-18 (1:00
 -2:00 UTC\, Thursday\, 9:00-10:00 Beijing Time\, Thursday\, PDT 18:00-19:0
 0 Wednesday )
DTSTART;TZID=W. Australia Standard Time:20160818T09
DTEND;TZID=W. Australia Standard Time:20160818T10
UID:04008200E00074C5B7101A82E008F0DFC16FB9F8D101000
 0100034BF3F14652399419CFE34E9F84C2A79
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20160817T110333Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=zh-CN:https://global.gotomeeting.com/join/882532573
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-1091467296
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
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] jenkins postbuildscript plugin

[Fatih Degirmenci]

Hi Dan,


It was a suggestion rather than an endorsement. If the issue can be fixed 
without installing the plugin then I suggest doing that instead.


The general reason for this is that; depending on what certain plugin is used 
for, some things might become tightly coupled to Jenkins, taking away the 
ability to run things outside of (same) Jenkins. This might cause difficulties 
for the users who might want to run stuff since they will not see what is done 
by Jenkins if they don't look at Jenkins and might hit the similar issue.


/Fatih

From: Dan Radez 
Sent: 17 August 2016 03:39:10
To: Fatih Degirmenci
Cc: agard...@linuxfoundation.org; opnfv-tech-discuss@lists.opnfv.org
Subject: jenkins postbuildscript plugin

Fatih was your suggestion to use the postbuildscript plugin an
endorsement to install it too?

Aric wanted to double check that you were on board with it before it was
installed. I could always just to a clean up a the start of the build
instead of at the end of every build.

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

[opnfv-tech-discuss] [multisite]Weekly meeting of Aug.18

[joehuang]

Hello, team,



Now all test cases were executed successfully in CI/Functest. It's time to 
discuss the next step.


Agenda of Aug.18 2016
*   Colorado quality improvement, release preparation
*   Next step for Multisite project, scope, focus, etc


IRC: http://webchat.freenode.net/?channels=opnfv-meeting  7:00-8:00 UTC (During 
summer time, means CET 9:00 AM).

if you would like to discuss other topics in the weekly meeting, please reply 
in this mail.

Best Regards
Chaoyi Huang ( joehuang )
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [cperf] Meeting Cancelled 8/18

[Daniel Farrell]

Hello CPerf,

I'll be in the backcountry with no networking Wed-Friday.

You all are welcome to meet without me, but I'm going to assume
we'll cancel for now. We can cover relevant work in the Integration
and S3P calls, or via email/IRC.

Thanks,

Daniel Farrell
Software Engineer, Red Hat SDN Team
https://wiki.opendaylight.org/view/user:dfarrell07

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

Re: [opnfv-tech-discuss] [SFC] multiple compute nodes with Tacker

[Manuel Buil]

Hi Tim,

You are hitting the bug we informed you guys about.

When the classifier and the first SF are "in the same OVS", the action of the 
classification flow should be resubmit($vxlan_gpe_port,0) instead of 
output:$vxlan_gpe_port. 

I don't have all the details as Brady was looking into this but apparently 
Netvirt compares the IP of the SFF with the IP of the SFF that tacker sees for 
the first SF. If they are the same, Netvirt will instruct the resubmit action 
instead of the output action. However, Tacker and Netvirt are checking the IP 
on different interfaces of the host where the SFF is running, so the result of 
the comparison is always false.

Until that bug is fixed, I am modifying that flow with a script so that the 
OPNFV CI test cases work. This is the script:

https://github.com/manuelbuil/sfc-work/blob/master/configure_first_classifier_ovs25.sh

Regards,
Manuel


-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com] 
Sent: Tuesday, August 16, 2016 7:58 PM
To: Manuel Buil
Cc: Yi Y Yang; Sam Hague; Brady Allen Johnson; OPNFV Tech
Subject: Re: [SFC] multiple compute nodes with Tacker

Hi Manuel,
Thanks for hte info.  I enabled the vxlan workaround routes and attempted the 
curl again.  I saw 2 packets hit the vxlan tool on the VNFs, but curl failed 
and the rest of the packets did not make it through.  Updated gist with flows:

https://gist.github.com/trozet/d6547cdc416a27ef7cf5b6c6b91db5cd

ofctl Port mapping:
compute1:
port 4) tap43c21e37 - TestVNF4 (first VNF in chain)
port 6) tape118a- http client

compute0:
port 6) tap867682340-80 - TestVNF5 (second VNF in chain)
port 7) - HTTP server

Main flow here to look at here is the classifier:

cookie=0x1110010001610255, duration=78031.957s, table=11, n_packets=27, 
n_bytes=1998, tcp,reg0=0x1,tp_src=2000,tp_dst=80 
actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_NSH_C2[],push_nsh,load:0x1->NXM_NX_NSH_MDTYPE[],load:0x3->NXM_NX_NSH_NP[],load:0xc20a->NXM_NX_NSH_C1[],load:0xa1->NXM_NX_NSP[0..23],load:0xff->NXM_NX_NSI[],load:0xc203->NXM_NX_TUN_IPV4_DST[],load:0xa1->NXM_NX_TUN_ID[0..31],output:5

It looks like it is skipping the first SFF.  I think that should send to the 
SFF (compute1, same compute, so maybe just resubmit or goto table) and then 
progress into SFC tables.

Sam, can you comment here?

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Manuel Buil" 
To: "Tim Rozet" , "Yi Y Yang" , "Sam 
Hague" 
Cc: "Brady Allen Johnson" , "OPNFV Tech" 

Sent: Tuesday, August 16, 2016 3:40:49 AM
Subject: RE: [SFC] multiple compute nodes with Tacker

Hi Tim,

You still need to do the vxlan workaround. OVS 2.5.90 supports two 
alternatives: eth+nsh or vxlan-gpe+eth+nsh between SF <> SFF. However, ODL 
is currently not capable to render the first one, so we need to do the 
vxlan-gpe+eth+nsh and thus, the workaround. Brady started to implement the 
support for eth+nsh but he did not manage to do it before his vacations. 
Hopefully, we'll get that in September.

Regards,
Manuel

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com]
Sent: Monday, August 15, 2016 11:39 PM
To: Manuel Buil; Yi Y Yang; Sam Hague
Cc: Brady Allen Johnson; OPNFV Tech
Subject: [SFC] multiple compute nodes with Tacker

Expanding to larger audience...

I tested out Apex today with the ODL build Brady provided.  I found there were 
a few updates needed in Tacker and pushed a patch to the colorado branch:
https://github.com/trozet/tacker/commit/d876584242781726d2e4403e69b9d15c08765625

I then created the following nova instances/tacker VNFs:
https://goo.gl/photos/F59h6V31fcQSzVFt6

The chain I created was this:
testVNF4->testVNF5

The curl to the http server failed (typical classifier matching on source port 
2000, dest port 80), and I don't see any packets hitting the vxlan tool on 
either VNF.  However, I do see packets hitting the classifier.  Flow gist:
https://gist.github.com/trozet/3161092c62fdc6582508e7779e445bf1

I did not use the VXLAN workaround (aka the kernel host route).  I thought this 
was not required anymore with OVS 2.5.90.  Yi can you comment here?

I haven't had a chance to dig into the flows yet, but if anyone sees the root 
cause of the problem, let me know.

Thanks,

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Manuel Buil" 
To: "Tim Rozet" 
Cc: "Brady Allen Johnson" 
Sent: Monday, August 15, 2016 12:27:23 PM
Subject: RE: Creating symmetric chains with tacker

Ok!

I did not have time to try that as we are encountering some bugs in Netvirt and 
I am preparing the demo for Seattle. Please update us if you make it work with 
several compute nodes :).

Regards,
Manuel

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com]
Sent: Monday, August 15, 2016 3:00 PM
To: Manuel Buil
Cc: Brady Allen Johnson
Subject: Re: Creating symmetric chains with tacker

Hi Manuel,
Yeah I don't think I ever accounted for that.  We would need to look at the 
driver call when ODL create

[opnfv-tech-discuss] [dovetail]new topic- script for validating the test cases

[Tianhongbo]

Hi all dovetailers:

The dovetail team are working on the test cases design, requirements from 
C&C(sfc,L3VPN and IPV6).
I would like to arise the new topic: script for validating the test cases.

As required by the C&C, the dovetail needs to prepare the test cases and 
scripts for validate the test cases.
the scripts are related to the codes managements.

Best Regards

hongbo

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