Re: [opnfv-tech-discuss] [test-wg] [yardstick] Yardstick PTL Election

[Cooper, Trevor]

Hi Kubi

Thanks for everything that you have done over the past 2 releases ... you have 
done an exceptional job to keep Yardstick progressing as a key part of the 
OPNFV test toolchain.

I would like to nominate Ross Brattain for the position of PTL. Ross has been 
an active committer for about 4 months.

Trevor


From: test-wg-boun...@lists.opnfv.org [mailto:test-wg-boun...@lists.opnfv.org] 
On Behalf Of Gaoliang (kubi)
Sent: Friday, May 05, 2017 5:44 AM
To: opnfv-tech-discuss@lists.opnfv.org
Cc: test-wg 
Subject: [test-wg] [opnfv-tech-discuss][yardstick] Yardstick PTL Election

Hi All ,

To keep the team diversity, bring new ideas and energy, we have finalized the 
Yardstick PTL election process[1] with team(similar with Functest's process).

We will start the Yardstick PTL election Process today, As the process 
described, "Calls for nomination will be open for a 2 weeks process",  so we 
will end the nomination at May 19th

Election would be open to any Yardstick committer[2] (+2/-2) , Then we will 
have one week to vote with http://civs.cs.cornell.edu/

As I have been yardstick PTL for 2 release(C, D), I will step down once new PTL 
has been elected.  All nomination are warmly welcome, let's make yardstick 
better and better

So Please feel free to nominate yourself and other committers before May 19th 
with this email thread.  Thanks :)


[1] https://wiki.opnfv.org/display/yardstick/Yardstick+PTL+Election
[2] https://wiki.opnfv.org/display/yardstick/People


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

[opnfv-tech-discuss] [tech-discuss][armband] IRC only this morning

[Bob Monkman]

Greetings Armbanders,
I have a new OS on my laptop and seem to have lost my saved passed for GTM.

We will have to proceed on IRC today.

IRC Channel is set up @ https://webchat.freenode.net/
#opnfv-armband
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. 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] [SFC]:Use case on Colorado release with Fuel installer

[Manuel Buil]

HI Roberto,

It is strange that one works and the other one does not. The use case
you are testing is being tested everyday in the CI and it works, so I
wonder what might be wrong. Are you using the Colorado release? How
many compute and controllers you are using? Can you please send us a
dump of your flows please using hatebin or pastebin?

Thanks,
Manuel

On Fri, 2017-05-05 at 12:38 +, Congiu Roberto wrote:
> 
> 
> Hi folk!
>  
> > I am playing a little bit with the chains and there something I would
like to share.
>  
> I am trying to create two chains: 
>  
> 
> > tacker sfc-create chain1 –chain firewall1tacker sfc-create chain2
–chain firewall2
>  
> > The two firewalls are of course two vnfs created with tacker (with
sfc-danube.qcow2, taken from the community).
> > Afterwards I create two different sfc-classifiers (block traffic 80
in one chain and block traffic 22 on the other one).
>  
> > What happens is that the traffic is routed correctly only on the
first chain created; the second one does not seem working.
>  
> > > So, basically, the http traffic is blocked correctly because goes to
the first SF on the first chain, but the ssh traffic does not pass
the second chain and goes lost somewhere.
> > The dump-flows seem correct; both the flows terminate on the same
port 18 (vxgpe of the br-int)
>  
> Any hint? Is it a use case that should work?
>  
>  
> Thank you very much
>  
> --
> 
> Telecom Italia
>  | TIM
> 
> Roberto Congiu
> 
> Network Function Virtualization 
> Via G.Reiss Romoli 274, 10148 Torino
> 
> Office: +39 011 228 6469
> Mobile: +39 335 7532462
> 
>  
> 
> 
> 
>   
>   
>   
> > > > > > > > Questo messaggio e i suoi 
> > > > > > > > allegati sono
indirizzati esclusivamente alle persone indicate. La diffusione,
copia o qualsiasi altra azione derivante dalla conoscenza di queste
informazioni sono rigorosamente vietate. Qualora abbiate ricevuto
questo documento per errore siete cortesemente pregati di darne
immediata comunicazione al mittente e di provvedere alla sua
distruzione, Grazie.
>   
> 
> 
>   
> > > > > > >   This e-mail and any attachments
is confidential and may  contain privileged information intended for
the addressee(s) only. Dissemination, copying, printing or use by
anybody else is unauthorised. If you are not the intended recipient,
please delete this message and any attachments and advise the sender
by return  e-mail, Thanks.
>   
>   
> 
> 
> > >   Rispetta l'ambiente. Non stampare
questa mail se non è necessario.
>   
>   
>   
> 
> 
> 
> ___
> 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] [SFC]:Use case on Colorado release with Fuel installer

[Congiu Roberto]

Hi folk!

I am playing a little bit with the chains and there something I would like to 
share.

I am trying to create two chains:


  *   tacker sfc-create chain1 -chain firewall1
  *   tacker sfc-create chain2 -chain firewall2

The two firewalls are of course two vnfs created with tacker (with 
sfc-danube.qcow2, taken from the community).
Afterwards I create two different sfc-classifiers (block traffic 80 in one 
chain and block traffic 22 on the other one).

What happens is that the traffic is routed correctly only on the first chain 
created; the second one does not seem working.

So, basically, the http traffic is blocked correctly because goes to the first 
SF on the first chain, but the ssh traffic does not pass the second chain and 
goes lost somewhere.
The dump-flows seem correct; both the flows terminate on the same port 18 
(vxgpe of the br-int)

Any hint? Is it a use case that should work?


Thank you very much

--
Telecom Italia | TIM
Roberto Congiu
Network Function Virtualization
Via G.Reiss Romoli 274, 10148 Torino
Office: +39 011 228 6469
Mobile: +39 335 7532462


Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone 
indicate. La diffusione, copia o qualsiasi altra azione derivante dalla 
conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate 
ricevuto questo documento per errore siete cortesemente pregati di darne 
immediata comunicazione al mittente e di provvedere alla sua distruzione, 
Grazie.

This e-mail and any attachments is confidential and may contain privileged 
information intended for the addressee(s) only. Dissemination, copying, 
printing or use by anybody else is unauthorised. If you are not the intended 
recipient, please delete this message and any attachments and advise the sender 
by return e-mail, Thanks.

Rispetta l'ambiente. Non stampare questa mail se non è necessario.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [test-wg][yardstick] Yardstick PTL Election

[Gaoliang (kubi)]

Hi All ,

To keep the team diversity, bring new ideas and energy, we have finalized the 
Yardstick PTL election process[1] with team(similar with Functest's process).

We will start the Yardstick PTL election Process today, As the process 
described, "Calls for nomination will be open for a 2 weeks process",  so we 
will end the nomination at May 19th

Election would be open to any Yardstick committer[2] (+2/-2) , Then we will 
have one week to vote with http://civs.cs.cornell.edu/

As I have been yardstick PTL for 2 release(C, D), I will step down once new PTL 
has been elected.  All nomination are warmly welcome, let's make yardstick 
better and better

So Please feel free to nominate yourself and other committers before May 19th 
with this email thread.  Thanks :)


[1] https://wiki.opnfv.org/display/yardstick/Yardstick+PTL+Election
[2] https://wiki.opnfv.org/display/yardstick/People

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

[opnfv-tech-discuss] [qtip] Agenda of weekly meeting 2017-05-05

[Yujun Zhang (ZTE)]

*# QTIP project weekly meeting on 2017-05-05*


   - time: UTC0730


   - irc://#opnfv-qtip@freenode


   - index: https://etherpad.opnfv.org/p/qtip-meetings


*## Action followup*


   - 


*## Topics*


   - Weekly updates


   - OPNFV plugfest retrospective


   - OPNFV summit sessions


   - Euphrates release plan

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

[opnfv-tech-discuss] [daisy4nfv] Meeting minutes for IRC meeting 0800UTC May 5 2017

[hu.zhijiang]

Minutes:
http://eavesdrop.openstack.org/meetings/daisycloud/2017/daisycloud.2017-05-05-07.59.html
 




Minutes (text): 
http://eavesdrop.openstack.org/meetings/daisycloud/2017/daisycloud.2017-05-05-07.59.txt
 




Log:
http://eavesdrop.openstack.org/meetings/daisycloud/2017/daisycloud.2017-05-05-07.59.log.html
 











B. R.,

Zhijiang___
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] Split of releng repo?

[Fatih Degirmenci]

Hi,

This is still the plan. The reason why this hasn't happened yet is Danube.

I'll share the analysis soon and then we can do this once Danube.3.0 is out.

/Fatih

On 5 May 2017, at 10:54, "morgan.richo...@orange.com" 
 wrote:

Hi

I think we already initiated this discussion some times ago
but would it make sense to split releng repo into releng-jjb and
releng-utils
as there are at least 2 very different areas (jenkins and Xproject
tooling/lib)

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



smime.p7s
Description: S/MIME cryptographic signature
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [OPNFV] Split of releng repo?

[morgan.richomme]

Hi

I think we already initiated this discussion some times ago
but would it make sense to split releng repo into releng-jjb and
releng-utils
as there are at least 2 very different areas (jenkins and Xproject
tooling/lib)

/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] On Stress Test Demo//RE: [test-wg] Notes from OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"

[Yuyang (Gabriel)]

Hi Alec,

Please see my answers inline!

Thanks!
Gabriel

From: Alec Hothan (ahothan) [mailto:ahot...@cisco.com]
Sent: Friday, May 05, 2017 11:11 AM
To: Yuyang (Gabriel); morgan.richo...@orange.com; Cooper, Trevor; 
opnfv-tech-discuss@lists.opnfv.org; test...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] On Stress Test Demo//RE: [test-wg] Notes from 
OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"

Hi Gabriel,

Regarding TC1, do you have the results and original chart available somewhere 
(the chart in the picture and in the slides is kind of small).
Gabriel: We do not have the original results and chart now since this is one 
time result that we have when we do local test. We have discussed the results 
plotting within Testperf.
The test results will be shown in the community ELK maintained by bitergia in 
Q2.
Some results could be found in the community CI, e.g., 
https://build.opnfv.org/ci/view/bottlenecks/job/bottlenecks-compass-posca_stress_traffic-baremetal-daily-danube/5/console

Do you also have a detailed description of the test:
Gabriel: I assume you ask detailed about TC3 here, since we only run TC1 on 
vPOD or bare mental POD.

· what kind of packet gen you are running in the first VM and what kind 
of forwarder you are running in the second VM
Gabriel: For TC3, we use netperf to send packet and retransmit it in the second 
VM.

· what flavor
Gabriel: Bottlenecks calls yardstick to do each test, the flavor is specified 
in Yardstick, i.e., yardstick-flavor: nova flavor-create yardstick-flavor 100 
512 3 1.

· what vswitch was used
Gabriel: OVS is used. If you have any recommendation, please also inform us :)

· how are the VMs placed (wrt compute node, numa node)
Gabriel: VMs are created by using heat client without specifying how and where 
to place them

· I assume the test will ramp up the number of VM pairs, if so how do 
you synchronize your VM starts/measurements (VMs don’t tend to all start the 
test at the same time due to the latency for bringing up individual VMs)
Gabriel: Yes, the VMs will not start to ping simultaneously. We can 
only simultaneously sent the request to create all the VMs, waiting for the 
creation and then to the ping operation.

· How do you track drop rate and latency across VM pairs
Gabriel: I assume you mean the packet drop rate and latency here. For these 
metrics, we use netperf to do the monitoring

Gabriel: you could also do the test locally. For more information, please refer 
to the link below.
Bottlenecks Testing Guide: 
http://docs.opnfv.org/en/stable-danube/submodules/bottlenecks/docs/testing/developer/devguide/posca_guide.html



Thanks!

  Alec





From: 
>
 on behalf of "Yuyang (Gabriel)" 
>
Date: Thursday, May 4, 2017 at 7:48 PM
To: "morgan.richo...@orange.com" 
>, "Cooper, 
Trevor" >, 
"opnfv-tech-discuss@lists.opnfv.org" 
>,
 "test...@lists.opnfv.org" 
>
Subject: [opnfv-tech-discuss] On Stress Test Demo//RE: [test-wg] Notes from 
OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"

Hi,

For the stress test demo, we have added more details.
Youtube link is provided below.
https://youtu.be/TPd4NZr__HI
Slides deck is uploaded in the WIKI page: 
https://wiki.opnfv.org/display/bottlenecks/Sress+Testing+over+OPNFV+Platform

The demo contents and results are briefly summarized below.

  Testing Contents
 Executing Stress Test and Provide comparison results for different 
installers (Installer A and Installer B)
Up to 100 stacks for Installer A (Completes the test)
Up to 40 stacks for Installer B (System fails to complete the 
test)
 Testing Steps
Enter the Bottlenecks Repo: cd /home/opnfv/bottlenecks
Prepare virtual environment: . pre_virt_env.sh
Executing ping test case: bottlenecks testcase run 
posca_factor_ping
Clean the virtual environment: . rm_virt_env.sh
  Testing Results
 Testing for Installer A
Up to 100 stacks in configuration file for Installer B
 1 stack SSH error when number of stack raised to 50
When stack number up to 100, most of the errors are heat response 
time out
 100 stacks are established successfully in the end
 Testing for Installer B
Up to 40 stacks in configuration file for Installer B
 When stack number up to 30, the system fails to create all the stacks
21 stacks are either created failure or keeping in creation
To