Re: [opnfv-tech-discuss] welcome Alex Yang to Multisite project

[Zhipeng Huang]

Welcome ! :)

On Thu, Sep 1, 2016 at 11:16 AM, joehuang  wrote:

> Hello, team,
>
> Welcome Alex Yang to Multisite project, Alex is from ZTE. Please attend
> today's weekly meeting, thanks.
>
> Best Regards
> Chaoyi Huang(joehuang)
>
> yangya...@zte.com.cn
> To:
>  joehuang‎; opnfv-helpd...@rt.linuxfoundation.org
>
> 01 September 2016 0:07
> Hi,
> I work for ZTE Corporation, and plan to participate in opnfv multisite
> project.
> Please let me be a contributor of this project, and set-up rights for me.
>
> Thanks.
> Alex Yang
> --
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [
> opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang [
> joehu...@huawei.com]
> *Sent:* 31 August 2016 17:32
> *To:* Dimitri Mazmanov; ashishsingh...@gmail.com; zhipengh...@gmail.com;
> Sama, Malla Reddy; Meimei; caizhiyuan (A); opnfv-tech-discuss@lists.
> opnfv.org
> *Subject:* [opnfv-tech-discuss] [multisite]Weekly meeting of Sept.1
>
> Hello, team,
>
>
>
> Thanks to all of us, the functest in CI job can work successfully now.
> Congratulation!
>
>
> Agenda of Aug.31 2016
>
> §   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 )
>
>


-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Prooduct Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
___
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 D-release naming

[Raymond Paik]

Any other suggestions?  A reminder that "nominations" for the D-release
naming closes at 5pm Pacific Time on Friday (September 2nd).

Thanks,

Ray

On Mon, Aug 29, 2016 at 9:34 AM,  wrote:

> Don is a good and tricky idea!
> Danube is good as well even if it will be our 4th release and we have 5
> continents (same issue with Don)
>
> congratulations to Dave for Dordogne! There are lot of French rivers
> starting with D but Dordogne is the best place for food.. :)
>
> I am a bit disapointed by the Australian rivers, they seem all
> pronounceable this time
>
> Let's vote...
>
> /Morgan
>
>
>
> Le 29/08/2016 à 09:26, Ash a écrit :
>
> I'd like to propose "Don", a Russian river and in tribute to the father of
> NFV, Mr. Don Clarke.
>
> On Sun, Aug 28, 2016 at 10:03 PM, Raymond Paik 
> wrote:
>
>> All,
>>
>> As discussed on the last TSC call, I'd like to get the process started
>> for the D-release naming.
>>
>> A quick reminder that we have a river theme for OPNFV releases and our
>> first 3 release names are Arno (Europe), Brahmaputra (Asia), and
>> Colorado (Americas).  I'd like to continue the tradition of going to
>> different continents/geographies, so we could venture into Africa or return
>> to Europe...
>>
>> Can you send me your top 2-3 nominations (at most) in the following
>> format by 5pm Pacific Time on September 2nd?  After I collect all the
>> nominations, I'll send out a SurveyMonkey poll so the community can pick
>> the winner
>>
>> Format: River name (locations)
>> For example,
>>
>>- Danube (Austria, Germany, Hungary, etc.)
>>- Draa (Algeria, Morocco)
>>- etc.
>>
>>
>> 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 mailing 
> listopnfv-tech-discuss@lists.opnfv.orghttps://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>
>
> --
> Morgan Richomme
> Orange/ IMT/ OLN/ CNC/ NCA/ SINA
>
> Network architect for innovative services
> Future of the Network community member
> Open source Orange community manager
>
>
> tel. +33 (0) 296 072 106
> mob. +33 (0) 637 753 326morgan.richo...@orange.com
>
> _
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [KVM] Weekly meeting for KVM enhancements for NFV - Agenda 9/1/2016

[Reddy, Raghuveer]

Meeting logistics - https://wiki.opnfv.org/nfv-kvm

Agenda:

1)  C-Release

-Scenario Testing Status

-Jira tickets

2)  Opens

Regards,
-Raghu
Ph: 408 765 4620
___
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.org is not resolving

[Raymond Paik]

All,

Thanks for your patience on this.  Obviously not a pleasant thing to deal
with a less than a month to go for the Colorado release.

The outages were caused by two instances of human error when installing a
new gear at LF's co-location facility.  The LF IT team is working with the
facilities manager to ensure that this does not happen again and are
exploring options to increase redundancy.

Apologies for the inconvenience and let me know if you have any questions.

Ray

On Wed, Aug 31, 2016 at 6:04 PM, Daniel Smith 
wrote:

> Hey there.
>
> thanks – Trevor reported the resolution a bit ago so we are good -seems LF
> (OPNFv/ODL) all went down for a moment.
>
>
> D
>
>
>
> *From:* 张军10013968 [mailto:zhang.ju...@zte.com.cn]
> *Sent:* Wednesday, August 31, 2016 8:51 PM
> *To:* Daniel Smith ;
> agard...@linuxfoundation.org 
> *Cc:* Kunzmann, Gerald ; SULLIVAN, BRYAN L <
> bs3...@att.com>; opnfv-tech-discuss@lists.opnfv.org <
> opnfv-tech-discuss@lists.opnfv.org>
>
> *Subject:* Re: [opnfv-tech-discuss] opnfv.org is not resolving
>
>
>
> Hi Daniel,
>
>
>
> I can access all the websites correctly. In China, I get the same domain(
> dev.opnfv.org) and ip address from 8.8.8.8 and 114.114.114.114.
>
> I think there may be a united nginix server for wiki, gerrit and other
> websites from opnfv.
>
> To Aric, do you know something about this?
>
>
>
> $ nslookup wiki.opnfv.org 8.8.8.8
>
> Server: 8.8.8.8
>
> Address: 8.8.8.8#53
>
>
>
> Non-authoritative answer:
>
> wiki.opnfv.org canonical name = dev.opnfv.org.
>
> Name: dev.opnfv.org
>
> Address: 198.145.29.81
>
>
>
> $ nslookup wiki.opnfv.org 114.114.114.114
>
> Server: 114.114.114.114
>
> Address: 114.114.114.114#53
>
>
>
> Non-authoritative answer:
>
> wiki.opnfv.org canonical name = dev.opnfv.org.
>
> Name: dev.opnfv.org
>
> Address: 198.145.29.81
>
>
>
> BR,
>
> Julien
>
>
>
> NFV Architect
> Controller System Design Dept./Wireless Product R＆D Institute/Wireless
> Product Operation
>
>
> D206(D2028), R Building, ZTE Plaza, #889, Bibo RD,
> Pudong District, Shang Hai, P.R.China, 201203
> T: +86 21 68897791   M: +86 21 15317680806
> E: zhang.ju...@zte.com.cn
> www.zte.com.cn
>
>
>
>  Send by zMail PC  
>
> Original Mail
>
> *From: *DanielSmith
>
> *To: *Kunzmann, Gerald ＜kunzm...@docomolab-euro.com＞SULLIVAN, BRYAN L ＜
> bs3...@att.com＞ ＜opnfv-tech-discuss@lists.opnfv.org＞
>
> *Subject: Re: [opnfv-tech-discuss] opnfv.org  is not
> resolving*
>
> *Date: *2016/09/01 06:54
>
>
>
> Hello.
>
>
>
> I am having this issue.
>
>
> DNS for North America seems to be funky – reporting a no answer for
> OPNFV.org
>
>
> Cached DNS responses are working for DNS servers in Sweden and China that
> I tried, but their TTL will expire shortly.
>
>
>
> I have tested with the following
>
>
>
> Nslookup wiki.opnfv.org  - using GOOGLE 8.8.8.8 DNS – no authoritative
> answer
>
> Isitdown.org shows the Site is not responding.
>
>
>
> D
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [
> mailto:opnfv-tech-discuss-boun...@lists.opnfv.org
> ] *On Behalf Of *Kunzmann,
> Gerald
> *Sent:* Wednesday, August 31, 2016 4:39 PM
> *To:* SULLIVAN, BRYAN L ＜bs3...@att.com＞; opnfv-tech-discuss@lists.
> opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] opnfv.org is not resolving
>
>
>
> Hi Bryan,
>
>
>
> Have checked www, wiki and jira. Seems to be fine on my side.
>
>
>
> Best regards,
>
> Gerald
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [
> mailto:opnfv-tech-discuss-boun...@lists.opnfv.org
> ] *On Behalf Of *SULLIVAN,
> BRYAN L
> *Sent:* Mittwoch, 31. August 2016 19:46
> *To:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* [opnfv-tech-discuss] opnfv.org is not resolving
>
>
>
> Anyone else seeing this issue? Just started happening. Opnfv.org and all
> subdomains.
>
>
>
> Thanks,
>
> Bryan Sullivan | AT
>
>
>
>
>
>
>
> ___
> 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] welcome Alex Yang to Multisite project

[joehuang]

Hello, team,

Welcome Alex Yang to Multisite project, Alex is from ZTE. Please attend today's 
weekly meeting, thanks.

Best Regards
Chaoyi Huang(joehuang)

[X][X]
yangya...@zte.com.cn
[X][X][X]
[X]
To:
 joehuang‎; opnfv-helpd...@rt.linuxfoundation.org

01 September 2016 0:07
Hi,
I work for ZTE Corporation, and plan to participate in opnfv multisite project.
Please let me be a contributor of this project, and set-up rights for me.

Thanks.
Alex Yang

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang 
[joehu...@huawei.com]
Sent: 31 August 2016 17:32
To: Dimitri Mazmanov; ashishsingh...@gmail.com; zhipengh...@gmail.com; Sama, 
Malla Reddy; Meimei; caizhiyuan (A); opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [multisite]Weekly meeting of Sept.1

Hello, team,



Thanks to all of us, the functest in CI job can work successfully now. 
Congratulation!

Agenda of Aug.31 2016
•   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

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

[Pierre Lynch]

Just resending this while removing any links with a semblance to Al Morton's 
filters to see if it works for him.




Thanks,

Pierre


 Original message 
From: "Yang, Yi Y" 
Date: 8/31/16 7:57 PM (GMT-05:00)
To: Tim Rozet 
Cc: vlingadaha...@mvista.com, pkanau...@mvista.com, OPNFV Tech 

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

Tim, thank for your information. Yes, ovs 2.5.90 has supported Eth+NSH, but 
classifier and sfc need to do necessary changes to support it.

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com]
Sent: Wednesday, August 31, 2016 10:27 AM
To: Yang, Yi Y 
Cc: Manuel Buil ; Sam Hague ; 
Brady Allen Johnson ; OPNFV Tech 
; vlingadaha...@mvista.com; 
pkanau...@mvista.com; Andre Fredette ; Victor Mehmeri 
; Ricardo Noriega De Soto 
Subject: Re: [SFC] multiple compute nodes with Tacker

Hi Yi.  Yes still using the vxlan workaround.  The reason it never worked 
before were due to known bugs in Tacker and ODL.  Fixing those plus 
accomodating new changes in Tacker/ODL to support OVS 2.5.90 took a while to 
get it all working.  Hopefully now we can move to doing Eth+NSH to SFs.  That 
is possible with OVS 2.5.90 right?  Then we can get rid of the workaround?

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Yi Y Yang" 
To: "Tim Rozet" 
Cc: "Manuel Buil" , "Sam Hague" , 
"Brady Allen Johnson" , "OPNFV Tech" 
, vlingadaha...@mvista.com, 
pkanau...@mvista.com, "Andre Fredette" , "Victor Mehmeri" 
, "Ricardo Noriega De Soto" 
Sent: Tuesday, August 30, 2016 9:26:17 PM
Subject: RE: [SFC] multiple compute nodes with Tacker

Tim, great job, I guess this demo is still using vxlan workaround, right? My 
question is why you couldn't successfully create multiple compute nodes with 
Tacker before but you can now.

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com]
Sent: Saturday, August 27, 2016 2:38 AM
To: Yang, Yi Y 
Cc: Manuel Buil ; Sam Hague ; 
Brady Allen Johnson ; OPNFV Tech 
; vlingadaha...@mvista.com; 
pkanau...@mvista.com; Andre Fredette ; Victor Mehmeri 
; Ricardo Noriega De Soto 
Subject: Re: [SFC] multiple compute nodes with Tacker

Hi All,
Happy to announce that with the lastest fixes into ODL Boron, multiple compute 
nodes/VNFs in a chain works with Tacker and OVS 2.5.90!  The outputs and flows 
can be seen here:
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgist.github.com%2ftrozet%2ff24e2b81ed0be504c3904f3a7a2ab27d=01%7c01%7cplynch%40ixiacom.com%7c73fa48ca72bc409bc66b08d3d1fa9628%7c069fd614e3f843728e18cd06724a9b23%7c0=CrrS29FrT1YXSWdnW3j3cvs%2bQThJsSHji6T1cBSIIbo%3d

The one caveat here is there is no way to tell ODL SFC which VNF to use in the 
chain.  When SFC goes to create the chain, it will pick VNFs based on type.  
Therefore in Tacker when you create your VNFs, you need to create them with 
different types (by modifying the service_type in the VNFD, and invoking that 
VNFD on VNF create).  The accepted values right now in ODL SFC are:
-firewall
-dpi
-napt44
-qos
-ids
-http-header-enrichment
-tcp-proxy
-Cisco-vASA
-Cisco-vNBAR

Next I'm going to start looking into some of the other bugs.  Particularly 
issues with creating more than 1 chain/classifier.

Many thanks to all the people that helped get this working: Manuel, Brady, 
Victor, Sam, Ricky, Yi

Tim Rozet
Red Hat SDN Team

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

Sent: Sunday, August 21, 2016 9:44:31 PM
Subject: RE: [SFC] multiple compute nodes with Tacker

Current SFC can't yet support Eth+NSH, so VxLAN workaround is necessary, Brady 
and other guys from Ericsson  have a plan to support Eth+NSH in SFC.

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com]
Sent: Tuesday, August 16, 2016 5:39 AM
To: Manuel Buil ; Yang, Yi Y ; 
Sam Hague 
Cc: Brady Allen Johnson ; OPNFV Tech 

Subject: [SFC] multiple compute nodes with Tacker

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

[MORTON, ALFRED C (AL)]

Sending this appeal again - Just received another notice of
a filtered message because of the goo gl URL...

> -Original Message-
> From: MORTON, ALFRED C (AL)
> Sent: Wednesday, August 31, 2016 10:18 AM
> To: opnfv-tech-discuss@lists.opnfv.org
> Subject: Re: [opnfv-tech-discuss] [SFC] multiple compute nodes with
> Tacker
> 
> This subject thread has a URL (goo gl) that triggers a
> proofpoint filter at AT, and we don't see the
> message. I've been following this interesting thread
> in the archive. The message was sent back on Aug 16.
> 
> If the next sender would please delete the offending
> URL in the next message on the thread, then I won't
> have to keep chasing the thread down in the archive :-)
> 
> thanks much!
> Al
> 
___
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.org is not resolving

[Daniel Smith]

Hello.

I am having this issue.

DNS for North America seems to be funky - reporting a no answer for OPNFV.org

Cached DNS responses are working for DNS servers in Sweden and China that I 
tried, but their TTL will expire shortly.

I have tested with the following

Nslookup wiki.opnfv.org  - using GOOGLE 8.8.8.8 DNS - no authoritative answer
Isitdown.org shows the Site is not responding.

D

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Kunzmann, 
Gerald
Sent: Wednesday, August 31, 2016 4:39 PM
To: SULLIVAN, BRYAN L ; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] opnfv.org is not resolving

Hi Bryan,

Have checked www, wiki and jira. Seems to be fine on my side.

Best regards,
Gerald

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Mittwoch, 31. August 2016 19:46
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] opnfv.org is not resolving

Anyone else seeing this issue? Just started happening. Opnfv.org and all 
subdomains.

Thanks,
Bryan Sullivan | AT

___
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.org is not resolving

[Daniel Smith]

Hey there.

I think there is probably someone doing some work on the back side of LF - 
since looking at DNS records for the last bit I can see the the result is 
flipping back and forth between resolving opnfv.org to 'dev.opnfv.org"  (alias 
for wiki) and a authoritative answer (wiki).

This smacks of DNS record editing and batch update to me :)  anyway y- its back 
now.
D

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Wednesday, August 31, 2016 1:46 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] opnfv.org is not resolving

Anyone else seeing this issue? Just started happening. Opnfv.org and all 
subdomains.

Thanks,
Bryan Sullivan | AT

___
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.org is not resolving

[Kunzmann, Gerald]

Hi Bryan,

Have checked www, wiki and jira. Seems to be fine on my side.

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Mittwoch, 31. August 2016 19:46
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] opnfv.org is not resolving

Anyone else seeing this issue? Just started happening. Opnfv.org and all 
subdomains.

Thanks,
Bryan Sullivan | AT

___
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.org is not resolving

[MORTON, ALFRED C (AL)]

I saw it for a while about an hour ago,
but it's ok now...

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Wednesday, August 31, 2016 1:46 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] opnfv.org is not resolving

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Anyone else seeing this issue? Just started happening. Opnfv.org and all 
subdomains.

Thanks,
Bryan Sullivan | AT

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

[opnfv-tech-discuss] opnfv.org is not resolving

[SULLIVAN, BRYAN L]

Anyone else seeing this issue? Just started happening. Opnfv.org and all 
subdomains.

Thanks,
Bryan Sullivan | AT

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

Re: [opnfv-tech-discuss] Models Weekly Meeting A

[SULLIVAN, BRYAN L]

Yes, the work to create reference VNF blueprints and test them with various 
VNFMs, can be referenced as a piece of the MANO WG scope. I've started with 
Cloudify, and am working on expanding to Tacker and JuJu. Giuseppe was planning 
to do the same with OpenBaton. As we wrap up Colorado, and that I was more or 
less out for 3 weeks, time has been short but it's progressing again now. I've 
got open threads going with the Cloudify and Tacker team members to resolve 
issues with setting up those VNFMs.

Thanks,
Bryan Sullivan | AT

From: Prakash Ramchandran [mailto:prakash.ramchand...@huawei.com]
Sent: Tuesday, August 30, 2016 1:22 PM
To: SULLIVAN, BRYAN L ; 'opnfv-tech-discuss@lists.opnfv.org' 

Subject: RE: Models Weekly Meeting A

Bryan,

Was the VNF On boarding  with Cloudify  "hello world sample" was a Model 
project that can be linked or tagged as MANO participation task?

I thought we had another one from Giuseppe for MANO API testing with 
Yardstick/Functets that was part of "Orchestra".


Another one was VES for metadata standardization for VNF Event streaming for 
Collector, await Aloks return from Leave on that.

All I am is trying to gather that can bring value to MANO Working Groups 
efforts to share best practices across different projects including upstream to 
help minimize gaps between OPNFV reference architecture and its deployments.

I did miss Model as I was on road and will try attend with some inputs on  
Sept. 12th and if possible next week Sept. 5th too.

Thanks
Prakash



Prakash Ramchandran
[logo_huawei] R USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: Tuesday, August 30, 2016 1:07 PM
To: Prakash Ramchandran; 'opnfv-tech-discuss@lists.opnfv.org'
Subject: RE: Models Weekly Meeting A

No, there was no meeting as no one showed up :(...
I also don't know of any discussions around onboarding yet. That's a to-do for 
the MANO WG I think.

Thanks,
Bryan Sullivan | AT

From: Prakash Ramchandran [mailto:prakash.ramchand...@huawei.com]
Sent: Monday, August 29, 2016 12:03 PM
To: SULLIVAN, BRYAN L >; 
'opnfv-tech-discuss@lists.opnfv.org' 
>
Subject: RE: Models Weekly Meeting A

Bryan,

If there was any discussions on VNF On-boarding in terms of the VNFD , 
TOSCA/YANG templates and workflow with respect to Cloudify please do point to 
summary.

I missed today's Models meeting at 9 AM. Will catch up as just returned from 
Hackfest and trying to get back to normal working.

Thanks
Prakash

Prakash Ramchandran
[logo_huawei] R USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Monday, August 22, 2016 7:40 AM
To: 'opnfv-tech-discuss@lists.opnfv.org'
Subject: Re: [opnfv-tech-discuss] Models Weekly Meeting A

Hi all,

I'm on vacation this week. I'm not sure if Prakash intends to hold the MANO WG 
today, but there will be no Models project meeting today.

Thanks,
Bryan Sullivan | AT


-Original Appointment-
From: SULLIVAN, BRYAN L
Sent: Monday, July 18, 2016 12:12 PM
To: SULLIVAN, BRYAN L; 'opnfv-tech-discuss@lists.opnfv.org'
Cc: MORTON JR., AL; 'Andrew Veitch'; 'David Suarez Fuentes'; GUPTA, ALOK; Henry 
Fourie; Ulas Kozat; Mario Torrecillas Rodriguez; Sen, Prodip; Dan Westerberg; 
Tal Barenboim; Kuppuswamy, Prabu; Gabor Halász; Lawrence Lamers; Ola Liljedahl; 
Vul, Alex
Subject: Models Weekly Meeting A
When: Monday, August 22, 2016 9:00 AM-10:00 AM (UTC-08:00) Pacific Time (US & 
Canada).
Where: https://global.gotomeeting.com/join/865421325


Sending out a calendar reminder since this makes it easier to remember!

https://wiki.opnfv.org/display/models/Models+Meetings
IRC: #opnfv-models, e.g.  
https://www.irccloud.com/#!/ircs://irc.freenode.net:6697/%23opnfv-models


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

Re: [opnfv-tech-discuss] How are Documentation/Reference Projects Published in C release

[Christopher Price]

Hi Folks,

 

We may have a definition issue here as I think we are all doing the right 
things as far as we have defined them.

 

Not part of the release:

Documents describing requirements are not tracked, nor required to pass 
specific milestones for a release.  The only milestone that is important is 
docs freeze and what is available is up to the project writing the docs and is 
not coordinated by the release project.

 

Delivered with Colorado:

Requirement or descriptive docs can be included in the document publication of 
release artifacts by including them on the release page as we did in 
Brahmaputra.

This is OK as long as we are able to differentiate documentation of delivered 
platform capability and documentation of planned or projected capability.  
(Future requirements should not be in the same document as the release 
description)

Talk to your friendly docs team about these types of docs you would like to 
have included in the “Colorado library”.

 

Hope this helps clear things up.

 

As we discussed after Brahmaputra, but not acted upon yet.  It would be great 
for our projects doing “requirements documentation” to collaborate on some form 
of structure, standard and template with the docs team to make this more 
consistent and automated.

 

/ Chris 

 

From:  on behalf of David McBride 

Date: Wednesday 31 August 2016 at 16:58
To: "Kunzmann, Gerald" 
Cc: TECH-DISCUSS OPNFV 
Subject: Re: [opnfv-tech-discuss] How are Documentation/Reference Projects 
Published in C release

 

Hi Gerald,

 

I'm certainly aware that many project do most, or even all, of their work 
upstream.  When I say "deliver code", that includes making changes in upstream 
projects.  

 

Also, to be clear, I'm NOT saying that requirements projects should not be part 
of OPNFV, I'm just saying that I do not see the benefit of a project joining a 
release if their only activity is writing a requirements document.  Join the 
OPNFV project, write a requirements document, then join a release.  

 

Perhaps I'm missing something, though.  What benefit do you see in the release 
process for projects that are only writing requirements?  Why could that not be 
done as part of the OPNFV project, but outside of the release process?

 

David

 

 

 

On Wed, Aug 31, 2016 at 12:51 AM, Kunzmann, Gerald 
 wrote:

Hi David, all,

 

My 2 cent on your question:

 

The question is: does it make sense for requirements projects to participate in 
releases until they're ready to deliver code?

 

Requirement projects are an essential part of OPNFV and some may even do all 
development in upstream, i.e. there might even be no code within OPNFV except 
test cases. Thus, I support having the requirement documents as part of the 
release documentation.

 

Best regards,

Gerald

 

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Georg Kunz
Sent: Mittwoch, 31. August 2016 09:42
To: Daniel Smith ; David McBride 



Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] How are Documentation/Reference Projects 
Published in C release

 

Hi Daniel, hi all,

 

Thank you Daniel for stating the advantages for the requirements projects and 
for OPNFV. From my point of view it is important for projects which are 
currently in the “requirements phase” to be represented in an OPNFV release:

 

-  We are in the process of reaching out to the OpenStack community 
based on our document. Making the requirements document an official part of an 
OPNFV release helps us in doing that by having an “official backing” of OPNFV 
(we are an OPNFV project after all)

-  It shows to the outside world that projects are active in all phases 
(requirements phase), supporting the overall perception of OPNFV

-  It gives the project members the feeling of contributing to OPNFV

 

I had some discussions with Chris and Sofia on this during the OPNFV summit. 
Back then the proposal was to include our requirements document in the 
“document library” under a section such as “requirements projects”. This could 
be a simple link – just as we have it right now on our project wiki.

 

As David pointed out, there is some overhead involved for the project, but I 
believe the benefits outweigh the overhead. 

 

Looking forward to discussing with you in today’s docs meeting.

 

Best regards

Georg

 

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Daniel Smith
Sent: Tuesday, August 30, 2016 11:44 PM
To: David McBride
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] How are Documentation/Reference Projects 
Published in C release

 

Hey All.

 

I 

Re: [opnfv-tech-discuss] How are Documentation/Reference Projects Published in C release

[David McBride]

Hi Gerald,

I'm certainly aware that many project do most, or even all, of their work
upstream.  When I say "deliver code", that includes making changes in
upstream projects.

Also, to be clear, I'm NOT saying that requirements projects should not be
part of OPNFV, I'm just saying that I do not see the benefit of a project
joining a release if their only activity is writing a requirements
document.  Join the OPNFV project, write a requirements document, then join
a release.

Perhaps I'm missing something, though.  What benefit do you see in the
release process for projects that are only writing requirements?  Why could
that not be done as part of the OPNFV project, but outside of the release
process?

David



On Wed, Aug 31, 2016 at 12:51 AM, Kunzmann, Gerald <
kunzm...@docomolab-euro.com> wrote:

> Hi David, all,
>
>
>
> My 2 cent on your question:
>
>
>
> The question is: does it make sense for requirements projects to
> participate in releases until they're ready to deliver code?
>
>
>
> Requirement projects are an essential part of OPNFV and some may even do
> all development in upstream, i.e. there might even be no code within OPNFV
> except test cases. Thus, I support having the requirement documents as part
> of the release documentation.
>
>
>
> Best regards,
>
> Gerald
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Georg Kunz
> *Sent:* Mittwoch, 31. August 2016 09:42
> *To:* Daniel Smith ; David McBride <
> dmcbr...@linuxfoundation.org>
>
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] How are Documentation/Reference
> Projects Published in C release
>
>
>
> Hi Daniel, hi all,
>
>
>
> Thank you Daniel for stating the advantages for the requirements projects
> and for OPNFV. From my point of view it is important for projects which are
> currently in the “requirements phase” to be represented in an OPNFV release:
>
>
>
> -  We are in the process of reaching out to the OpenStack
> community based on our document. Making the requirements document an
> official part of an OPNFV release helps us in doing that by having an
> “official backing” of OPNFV (we are an OPNFV project after all)
>
> -  It shows to the outside world that projects are active in all
> phases (requirements phase), supporting the overall perception of OPNFV
>
> -  It gives the project members the feeling of contributing to
> OPNFV
>
>
>
> I had some discussions with Chris and Sofia on this during the OPNFV
> summit. Back then the proposal was to include our requirements document in
> the “document library” under a section such as “requirements projects”.
> This could be a simple link – just as we have it right now on our project
> wiki.
>
>
>
> As David pointed out, there is some overhead involved for the project, but
> I believe the benefits outweigh the overhead.
>
>
>
> Looking forward to discussing with you in today’s docs meeting.
>
>
>
> Best regards
>
> Georg
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Daniel Smith
> *Sent:* Tuesday, August 30, 2016 11:44 PM
> *To:* David McBride
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] How are Documentation/Reference
> Projects Published in C release
>
>
>
> Hey All.
>
>
>
> I spoke with Sofia as well about this and presented our NetReady
> situation. We have a document that covers what we wanted to cover for Phase
> 1 (targeting C release) of the NetReady Requirements Project.   We now want
> to stop internally editing it and release it for comment – and the thinking
> is that, since we have built the document in gerrit and based on DOCS
> formatting guidelines, was the vehicle to provide the following in terms of
> the work that the team did:
>
>
>
> -Allow for the completion and publishing of the Project Goals
> Phase 1 targets (in line with agreed principles when the project  was
> approved/started) – Phase2,3,4 as outlined are targeted for subsequent
> releases as documented
>
> -Allow for the distribution of the finished product to external
> (non commiter/contributer groups) -  is it realistic to think that someone
> from Openstack (whom the requirements are destined for) will look at the
> RST line format in our gerrit repository to find our documentation? (rather
> than in the released docs page/artifact)?   Or perhaps a different way of
> looking at it would be to ask, how do we move the finished requirements
> document for C release to a platform to be viewed and commented (i.e JIRA
> for D release for review or in gerrit) going forward
>
> -Allows us to tag and timestamp the work (and thus the evolution)
> of the work the team is doing.  Provides start and stop points to
> coordinate work for the team (goal/endpoints).
>
> -Allows all projects to feel that they 

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

[MORTON, ALFRED C (AL)]

This subject thread has a URL (goo gl) that triggers a
proofpoint filter at AT, and we don't see the 
message. I've been following this interesting thread
in the archive. The message was sent back on Aug 16.

If the next sender would please delete the offending
URL in the next message on the thread, then I won't 
have to keep chasing the thread down in the archive :-)

thanks much!
Al
 
___
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] Sept 2016 Sprint

[MORTON, ALFRED C (AL)]

Works now, thanks a bunch!
Al

> -Original Message-
> From: Tahhan, Maryam [mailto:maryam.tah...@intel.com]
> Sent: Wednesday, August 31, 2016 9:13 AM
> To: MORTON, ALFRED C (AL); opnfv-tech-discuss@lists.opnfv.org
> Subject: RE: [VSPERF] Sept 2016 Sprint
> 
> Hi Al
> I've added all the committers and any active contributors to the
> developers list now. You should be able to pull in issues.
> If you have any issues please let me know
> 
> BR
> Maryam
> 
> -Original Message-
> From: MORTON, ALFRED C (AL) [mailto:acmor...@att.com]
> Sent: Wednesday, August 31, 2016 2:03 PM
> To: Tahhan, Maryam ; opnfv-tech-
> disc...@lists.opnfv.org
> Subject: RE: [VSPERF] Sept 2016 Sprint
> 
> Hi Maryam and all Committers,
> 
> Can anyone (besides Maryam) drag and drop a JIRA ticket from Backlog to
> the September Sprint list?
> 
> I can't, JIRA says I don't have schedule permission.
> 
> Maryam - I think we've been here before (for real, not déjà vu), and
> Aric was unable to resolve it...
> 
> regards,
> Al
> 
> > -Original Message-
> > From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-
> > discuss-boun...@lists.opnfv.org] On Behalf Of Tahhan, Maryam
> > Sent: Wednesday, August 31, 2016 8:49 AM
> > To: opnfv-tech-discuss@lists.opnfv.org
> > Subject: [opnfv-tech-discuss] [VSPERF] Sept 2016 Sprint
> >
> > Hi folks
> > I am a bit late to this so for that I apologise. To continue with the
> > monthly sprint trend, I've ended the current sprint and started a new
> > sprint backlog for sept
> > (https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=43
> > =V
> > SPERF=planning.nodetail=VSPERF-332 )
> >
> > [ACTION] VSPERF community: can you please log into Jira and
> > create/pull any issues that you plan on working on in Sept into the
> > backlog before COB Fri 2nd of Sept 2016
> >
> > If you have any issues, please give me a shout.
> >
> > BR
> > Maryam
> > ___
> > 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] [VSPERF] Sept 2016 Sprint

[Tahhan, Maryam]

Hi Al
I've added all the committers and any active contributors to the developers 
list now. You should be able to pull in issues.
If you have any issues please let me know

BR
Maryam

-Original Message-
From: MORTON, ALFRED C (AL) [mailto:acmor...@att.com] 
Sent: Wednesday, August 31, 2016 2:03 PM
To: Tahhan, Maryam ; opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [VSPERF] Sept 2016 Sprint

Hi Maryam and all Committers,

Can anyone (besides Maryam) drag and drop a JIRA ticket from Backlog to the 
September Sprint list?

I can't, JIRA says I don't have schedule permission.

Maryam - I think we've been here before (for real, not déjà vu), and Aric was 
unable to resolve it... 

regards,
Al

> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech- 
> discuss-boun...@lists.opnfv.org] On Behalf Of Tahhan, Maryam
> Sent: Wednesday, August 31, 2016 8:49 AM
> To: opnfv-tech-discuss@lists.opnfv.org
> Subject: [opnfv-tech-discuss] [VSPERF] Sept 2016 Sprint
> 
> Hi folks
> I am a bit late to this so for that I apologise. To continue with the 
> monthly sprint trend, I've ended the current sprint and started a new 
> sprint backlog for sept 
> (https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=43
> =V
> SPERF=planning.nodetail=VSPERF-332 )
> 
> [ACTION] VSPERF community: can you please log into Jira and 
> create/pull any issues that you plan on working on in Sept into the 
> backlog before COB Fri 2nd of Sept 2016
> 
> If you have any issues, please give me a shout.
> 
> BR
> Maryam
> ___
> 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] [VSPERF] Sept 2016 Sprint

[MORTON, ALFRED C (AL)]

Hi Maryam and all Committers,

Can anyone (besides Maryam) drag and drop a JIRA ticket
from Backlog to the September Sprint list?

I can't, JIRA says I don't have schedule permission.

Maryam - I think we've been here before (for real, not déjà vu),
and Aric was unable to resolve it... 

regards,
Al

> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-
> discuss-boun...@lists.opnfv.org] On Behalf Of Tahhan, Maryam
> Sent: Wednesday, August 31, 2016 8:49 AM
> To: opnfv-tech-discuss@lists.opnfv.org
> Subject: [opnfv-tech-discuss] [VSPERF] Sept 2016 Sprint
> 
> Hi folks
> I am a bit late to this so for that I apologise. To continue with the
> monthly sprint trend, I've ended the current sprint and started a new
> sprint backlog for sept
> (https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=43=V
> SPERF=planning.nodetail=VSPERF-332 )
> 
> [ACTION] VSPERF community: can you please log into Jira and create/pull
> any issues that you plan on working on in Sept into the backlog before
> COB Fri 2nd of Sept 2016
> 
> If you have any issues, please give me a shout.
> 
> BR
> Maryam
> ___
> 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] [VSPERF] Sept 2016 Sprint

[Tahhan, Maryam]

Hi folks
I am a bit late to this so for that I apologise. To continue with the monthly 
sprint trend, I've ended the current sprint and started a new sprint backlog 
for sept 
(https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=43=VSPERF=planning.nodetail=VSPERF-332
 )

[ACTION] VSPERF community: can you please log into Jira and create/pull any 
issues that you plan on working on in Sept into the backlog before COB Fri 2nd 
of Sept 2016

If you have any issues, please give me a shout.

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

Re: [opnfv-tech-discuss] How to enable latency test?

[MORTON, ALFRED C (AL)]

Hi Binghan,

Please see section 6 of [0] for HW requirements and
limitations of latency measurement in MoonGen (typically
only a sub-set of packets can be measured for latency).
IMO, this is a small compromise when considering an
opensource solution for the test device.

regards,
Al

[0] 
https://www.researchgate.net/publication/266913386_MoonGen_A_Scriptable_High-Speed_Packet_Generator


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Bill 
Michalowski
Sent: Wednesday, August 31, 2016 8:34 AM
To: Christian Trautman
Cc: Binghan; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [VSPERF] How to enable latency test?

Thanks Christian!  I just assigned this to myself and will integrate the 
feature into VSPERF in the near future.
- Bill
- Original Message -
From: Christian Trautman >
To: Binghan >
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Sent: Tue, 30 Aug 2016 22:19:49 -0400 (EDT)
Subject: Re: [opnfv-tech-discuss] [VSPERF] How to enable latency test?
Hi Binghan,
Moongen does support collection of latency stats so it just needs to be added 
to VSPerf. We will add this as a JIRA ticket and advise you when its available.
Thanks.
-Christian,

From: "Christian Trautman" >
To: "Binghan" >
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Sent: Tuesday, August 30, 2016 9:14:40 PM
Subject: Re: [opnfv-tech-discuss] [VSPERF] How to enable latency test?
Hi Binghan,
Moongen in VSPerf does not currently collect latency stats. I will inquire with 
the developers if this is planned in the near future and get back to you.
-Christian,

From: "Binghan" >
To: "MartinX Klozik" >
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Sent: Tuesday, August 30, 2016 11:04:15 AM
Subject: Re: [opnfv-tech-discuss] [VSPERF] How to enable latency test?
Hi Martin,
I am using Moongen, I cannot find latency result from Moongen log, I consider 
that VSperf parse Moongen log to get the test result.
And about the configuration, I did not use the custom.conf, everything is by 
default. Sure, traffic generator part has been reconfigured, but nothing else.
I attached pvp test log file and test report.
Thanks a lot.

BRs,
Binghan

On Tue, Aug 30, 2016 at 4:19 PM, Klozik, MartinX 
> wrote:
Hi Binghan,

Could you please sent us following info?
* what traffic generator you use
* your vsperf configuration
* full test output

In general these values are reported by traffic generator and the level of 
implementation might be different among supported traffic
generators. It would be good to check if these latencies are visible in traffic 
generator itself.

Thank you,
Martin

From:opnfv-tech-discuss-boun...@lists.opnfv.org
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org]
On Behalf Of Binghan
Sent: Tuesday, August 30, 2016 3:02 PM
To:opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [VSPERF] How to enable latency test?

Hi VSPERF experts,

I am trying to use VSPERF to benchmark OVS performance.

I use default configuration, but no matter I run PVP test or P2P test, the 
latency result is always 0. Do I need to configure anything special to enable 
latency test?

BRs,
Binghan

[INFO ]  2016-08-26 22:00:15,727 : (root) -  Key: throughput_rx_fps, 
Value: 19123026.00
[INFO ]  2016-08-26 22:00:15,727 : (root) -  Key: throughput_rx_mbps, 
Value: 9950.989
[INFO ]  2016-08-26 22:00:15,727 : (root) -  Key: 
throughput_rx_percent, Value: 64.253
[INFO ]  2016-08-26 22:00:15,727 : (root) -  Key: tx_rate_fps, Value: 
19123026.00
[INFO ]  2016-08-26 22:00:15,727 : (root) -  Key: tx_rate_mbps, Value: 
12850.673
[INFO ]  2016-08-26 22:00:15,728 : (root) -  Key: tx_rate_percent, 
Value: 64.253
[INFO ]  2016-08-26 22:00:15,728 : (root) -  Key: min_latency_ns, 
Value: 0.000
[INFO ]  2016-08-26 22:00:15,728 : (root) -  Key: max_latency_ns, 
Value: 0.000
[INFO ]  2016-08-26 22:00:15,728 : (root) -  Key: avg_latency_ns, 
Value: 0.000
[INFO ]  2016-08-26 22:00:15,728 : (root) -  Key: type, Value: rfc2544
[INFO ]  2016-08-26 22:00:15,728 : (root) -  Key: packet_size, Value: 64

--

Intel Research and Development Ireland Limited

Registered in Ireland

Re: [opnfv-tech-discuss] [ovsnfv] Success virtual deployment (Fuel) + Report troubleshooting

[O Mahony, Billy]

Hi Chunghan,

Cc’ing Jonas.

Comments below.

From: Lee, Chunghan [mailto:lee.chung...@jp.fujitsu.com]
Sent: Tuesday, August 30, 2016 5:32 AM
To: O Mahony, Billy ; 
opnfv-tech-discuss@lists.opnfv.org
Cc: therb...@redhat.com; Gray, Mark D 
Subject: RE: [ovsnfv] Success virtual deployment (Fuel) + Report troubleshooting

Hi Billy,

> Chunghan will check for relevant section in fuel documentation

I checked fuel repo.( 
https://gerrit.opnfv.org/gerrit/gitweb?p=fuel.git;a=tree;f=docs;hb=HEAD) to add 
the troubleshooting to the fuel documentation.
However, I cannot find the suitable location at the documents.

>[fuel.git]/docs/installationprocedure/installation.instruction.rst
The above location looks like the suitable location, but there is no mention 
about the virtual deployment.
(It looks like the deployment procedure for bare-metal…)
[[BO'M]]
[[BO'M]] You could check with Fuel team - Jonas Bjurel perhaps if they plan on 
adding documentation for a virtual deployment. If so then the CentOS specific 
instructions would go well there. Michal yesterday mentioned the ONFV 
“playground” which sounds like it may be the best method for doing virtual 
deployments.

We’d like to ask the location to Michal Skalski ?
(In my memory, he mentioned the fuel documentation at the yesterday's meeting.)
# If I was wrong, sorry.

Alternatively, our project has the document for the virtual deployment of old 
version.
https://wiki.opnfv.org/display/ovsnfv/Deploy+OPNFV+with+Fuel+in+a+virtual+environment

I think that it is a possible way to add the troubleshooting to the above link 
(wiki).
Could you give me your opinion ?
[[BO'M]] That document is from Arno, so realistically it would need to be 
updated before you could add CentOS instructions.
Regards,
Chunghan Lee

--
Chunghan Lee
Cloud Network Project. Fujitsu Laboratories Ltd.
4-1-1 Kamikodanaka, Nakahara-ku,
Kawasaki-shi, Kanagawa 211-8588, Japan
E-mail： lee.chung...@jp.fujitsu.com
--

From: O Mahony, Billy [mailto:billy.o.mah...@intel.com]
Sent: Monday, August 29, 2016 6:14 PM
To: Lee, Chunghan/李 忠翰; 
opnfv-tech-discuss@lists.opnfv.org
Cc: therb...@redhat.com; Gray, Mark D
Subject: RE: [ovsnfv] Success virtual deployment (Fuel) + Report troubleshooting

Hi Chunghan,

That’s great work - good to know of some fixes required for using CentOS.

A few other comments inline below.

Thanks,
Billy.

From: Lee, Chunghan [mailto:lee.chung...@jp.fujitsu.com]
Sent: Friday, August 26, 2016 10:58 AM
To: O Mahony, Billy 
>; 
opnfv-tech-discuss@lists.opnfv.org
Cc: therb...@redhat.com; Gray, Mark D 
>; Lee, Chunghan 
>
Subject: [ovsnfv] Success virtual deployment (Fuel) + Report troubleshooting

Hi Billy,

I can deploy the OPNFV testbed (Colorado) using Fuel on my local environment.
Thank you so much!

The local environment (one server) is as follow.
---
OS : CentOS 7.2 (Default kernel : 3.10)
CPU : Intel(R) Xeon(R) CPU  E5640  @ 2.67GHz
Memory : 48GB
DISK : 1TB
Fuel IMAGE : opnfv-2016-08-24_22-58-32.iso
http://artifacts.opnfv.org/fuel.html
# I tried to do the indicated image (opnfv-2016-08-03_23-58-37.iso) from Billy,
# but it was already deleted.
---

I’d like to report some problems to install the testbed and empirical approach 
to solve them.


1. If the OS language (LANG) is not English, the installation will be 
stopped.
Fuel did not know the other languages, such as Korean or Japanese.
In the local environment, LANG was ja_JP.UTF-8 unfortunately.

In my case, LANG is changed from ja_JP.UTF-8 to C, and I can solve this problem.


2. If the OS is CentOS7, the location of kvm is different from Ubuntu.
In Fuel, the kvm location is based on Ubuntu.

I created the follow symbolic link myself.
> ln -s /usr/libexec/qemu-kvm /usr/bin/kvm


3. New version of python packages are required for the installation.
If the scp python package is installed by yum (epel),
this version (python-scp-0.7.1-3.el7.noarch.) is old and
there is no data type (sanitize) at the old version.
As a result, the installation will be stopped due to no sanitize.

The scp package (0.10.2) is installed by pip.

4. The following message is time-consuming.
> Trying to SSH into Fuel VM 10.20.0.2 ... sleeping 10 seconds
# The patience is required for this procedure.
[[BO'M]] This is the deployment scripts way of figuring out when the 
installation of the fuel master has completed - it just keeps trying to ssh to 
the fuel master. After that it can track progress by invoking the fuel cli over 
ssh.

5. 

[opnfv-tech-discuss] [opnfvdocs] Requirements Projects in C Release - continued

[Daniel Smith]

Hey there.

To continue the discussion on Requirements Projects and how they are released.  
 I will try to listen in, however I am triple booked at this time slot this 
morning at 9am local.

I think the idea of the page is fine.  I don't think it should be called 
"Future Projects" since these are projects that were approved and have started 
as per the OPNFV Project Approval process - thus these are "real" articles 
within OPNFV and have a namespace already  - and thus should be given their own 
space (IMHO).

I would like to understand more what we mean  by "link to projects 
documentation"   - since this would again link back to a gerrit repo.   So 
again, for inclusion of the work that teams have done for contribution to C 
release, following the document structure, etc - why can the items in the repo, 
which are in RST format, not be branched and artifcats generated just like 
anything else (for example FUEL, APEX, ETc) - these are all projects.

My questions would be simple( wearing a contributor hat):

-   If a release project (A, B C) can simply change what is in and out in 
terms of documentation / approach between releases - how as a member / 
contributor does the OPNFV release program ensure requirements projects work is 
actually published and sent upstream for review (THE OPNFV GOAL).
o   David/Chris - can you please outline how a requirements project is 
actually reviewed and sent upstream from OPNFV (tagged to a release or not)?  
Since its not clear how the work we are doing (in or out of a release) would be 
served upstream.  Code can be tagged bugs, however for Openstack the blueprints 
are needed by certain dates.
*   Are the release dates tied in such a way to accommodate when blueprints 
and other requirments projects must deliver to Openstack ?
*   How does the mechanism from OPNFV requirements projects to upstream and 
then back (review) work in a release?  In OPNFV as a whole
-   Some explanation as to the "advantages" that releasing only projects 
that have code (and thus tagged with "C-release") have over releasing all the 
work that all the teams have done towards the release.

Good discussion, many thanks for the input - sorry if Im asking too many 
questions.

Cheers,
D



-Original Appointment-
From: Sofia Wallin [mailto:sofia.wal...@ericsson.com]
Sent: Tuesday, April 19, 2016 9:54 AM
To: Sofia Wallin; Christopher Price; Ryota Mibu (r-m...@cq.jp.nec.com); Fatih 
Degirmenci; TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org)
Cc: Ari Pietikäinen; Tim Irnich; 'Coppola, Simona'; 'Beierl, Mark'; 'Tim 
Dalton'; 'Ahmed Elbornou (amaged)'; 'SULLIVAN, BRYAN L'; 'Henry Fourie'; 
'Seiler, Glenn'; 'Mario Torrecillas Rodriguez'; 'Skip Booth (ebooth)'; Gabor 
Halász; Alan McNamee; Paul-Andre Raymond; Canio Cillis; Agarwal, Anshu
Subject: [opnfv-tech-discuss] [opnfvdocs] opnfvdocs bi-weekly team meeting
When: Wednesday, August 31, 2016 3:00 PM-3:45 PM (UTC+01:00) Amsterdam, Berlin, 
Bern, Rome, Stockholm, Vienna.
Where: https://global.gotomeeting.com/join/984191797


Invitation updated to bi-weekly.

Welcome to join this bi-weekly opnfvdocs meeting.

Intention is to cover:
Project backlog and progress
Questions and issues

Hoping to see opnfvdocs committers participate as regularly as possible.

//Sofia

Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/984191797

You can also dial in using your phone.
United States : +1 (669) 224-3318

Access Code: 984-191-797

More phone numbers
Australia : +61 2 8355 1039
Austria : +43 7 2088 1049
Belgium : +32 (0) 42 68 0180
Canada : +1 (647) 497-9379
Denmark : +45 69 91 89 30
Finland : +358 (0) 942 41 5793
France : +33 (0) 170 950 589
Germany : +49 (0) 692 5736 7301
Ireland : +353 (0) 15 360 757
Italy : +39 0 230 57 81 80
Netherlands : +31 (0) 208 080 221
New Zealand : +64 9 280 6304
Norway : +47 21 04 30 54
Spain : +34 911 82 9908
Sweden : +46 (0) 852 500 516
Switzerland : +41 (0) 435 0167 69
United Kingdom : +44 (0) 330 221 0099

  << File: ATT1.txt >>

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

Re: [opnfv-tech-discuss] How are Documentation/Reference Projects Published in C release

[Sofia Wallin]

Hi everyone,
I haven’t been involved in the discussion whether we want the requirement 
projects to be a part of our releases or not.
But when it comes to documentation it is obvious that people see a need to 
include this kind of work as well.
I agree with Chris, “to publish a “future work” section of our release library 
that describes more where our community is heading”.

I talked to Daniel yesterday and we think that it would be fine to handle this 
in the same way as the release documentation. We create an introduction 
document explaining what this is about and link to the projects documentation.


But let’s discuss this (and hopefully agree),
I will add this as topic for the docs meeting this afternoon, so people 
concerned are welcome to call in.

BR,
Sofia

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Kunzmann, 
Gerald
Sent: den 31 augusti 2016 09:51
To: Georg Kunz; Daniel Smith; David McBride
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] How are Documentation/Reference Projects 
Published in C release

Hi David, all,

My 2 cent on your question:

The question is: does it make sense for requirements projects to participate in 
releases until they're ready to deliver code?

Requirement projects are an essential part of OPNFV and some may even do all 
development in upstream, i.e. there might even be no code within OPNFV except 
test cases. Thus, I support having the requirement documents as part of the 
release documentation.

Best regards,
Gerald

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Georg Kunz
Sent: Mittwoch, 31. August 2016 09:42
To: Daniel Smith >; 
David McBride 
>
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] How are Documentation/Reference Projects 
Published in C release

Hi Daniel, hi all,

Thank you Daniel for stating the advantages for the requirements projects and 
for OPNFV. From my point of view it is important for projects which are 
currently in the “requirements phase” to be represented in an OPNFV release:


-  We are in the process of reaching out to the OpenStack community 
based on our document. Making the requirements document an official part of an 
OPNFV release helps us in doing that by having an “official backing” of OPNFV 
(we are an OPNFV project after all)

-  It shows to the outside world that projects are active in all phases 
(requirements phase), supporting the overall perception of OPNFV

-  It gives the project members the feeling of contributing to OPNFV


I had some discussions with Chris and Sofia on this during the OPNFV summit. 
Back then the proposal was to include our requirements document in the 
“document library” under a section such as “requirements projects”. This could 
be a simple link – just as we have it right now on our project wiki.

As David pointed out, there is some overhead involved for the project, but I 
believe the benefits outweigh the overhead.

Looking forward to discussing with you in today’s docs meeting.

Best regards
Georg

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Daniel Smith
Sent: Tuesday, August 30, 2016 11:44 PM
To: David McBride
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] How are Documentation/Reference Projects 
Published in C release

Hey All.

I spoke with Sofia as well about this and presented our NetReady situation. We 
have a document that covers what we wanted to cover for Phase 1 (targeting C 
release) of the NetReady Requirements Project.   We now want to stop internally 
editing it and release it for comment – and the thinking is that, since we have 
built the document in gerrit and based on DOCS formatting guidelines, was the 
vehicle to provide the following in terms of the work that the team did:


-Allow for the completion and publishing of the Project Goals Phase 1 
targets (in line with agreed principles when the project  was approved/started) 
– Phase2,3,4 as outlined are targeted for subsequent releases as documented

-Allow for the distribution of the finished product to external (non 
commiter/contributer groups) -  is it realistic to think that someone from 
Openstack (whom the requirements are destined for) will look at the RST line 
format in our gerrit repository to find our documentation? (rather than in the 
released docs page/artifact)?   Or perhaps a different way of looking at it 
would be to ask, how do we move the finished requirements document 

[opnfv-tech-discuss] [multisite]Weekly meeting of Sept.1

[joehuang]

Hello, team,



Thanks to all of us, the functest in CI job can work successfully now. 
Congratulation!

Agenda of Aug.31 2016
*   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 )



From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang 
[joehu...@huawei.com]
Sent: 24 August 2016 16:37
To: Dimitri Mazmanov; ashishsingh...@gmail.com; zhipengh...@gmail.com; Sama, 
Malla Reddy; Meimei; caizhiyuan (A); opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [multisite]Weekly meeting of Aug.25


Hello, team,


Agenda of Aug.25 2016
*   Unstable CI job running
*   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] [Bottlenecks] Cancel the Bottlenecks Weekly Meeting on September 1st

[Yuyang (Gabriel)]

Hi,

Due to the confliction with Huawei Connect on September 1st, the Bottlenecks 
weekly meeting is canceled.
Welcome to our meeting in next week!

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