[opnfv-tech-discuss] [dovetail]weekly dovetail meeting

[Tianhongbo]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:China 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=Tianhongbo:MAILTO:hongbo.tianhon...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='TECH-DISC
 USS OPNFV':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Christoph
 er Price':MAILTO:christopher.pr...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Dave Near
 y':MAILTO:dne...@redhat.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='marko.a.k
 ui...@nokia.com':MAILTO:marko.a.kui...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Rautakump
 u, Mika (Nokia - FI/Espoo)'":MAILTO:mika.rautaku...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='sheng-ann
 .y...@ericsson.com':MAILTO:sheng-ann...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='yangjiany
 j...@chinamobile.com':MAILTO:yangjian...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='zhang.jun
 3...@zte.com.cn':MAILTO:zhang.ju...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'HU, BIN'":
 MAILTO:bh5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='lma@biigr
 oup.cn':MAILTO:l...@biigroup.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tetsuya N
 akamura':MAILTO:t.nakam...@cablelabs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Wenjing Ch
 u:MAILTO:wenjing@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Christophe
 r Donley (Chris):MAILTO:christopher.don...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Jose Laus
 uch':MAILTO:jose.laus...@ericsson.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='Shobhan A
 yyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Canio Cil
 lis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Marco Var
 lese':MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Kedalagud
 de, Meghashree Dattatri'":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Lawrence 
 Lamers':MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Georg Kun
 z':MAILTO:georg.k...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Maria Toe
 roe':MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Rathnakum
 ar Kayyar':MAILTO:rkay...@lcnpl.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Gabor Hal
 ász':MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Pierre Ly
 nch':MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='rgrigar@l
 inuxfoundation.org':MAILTO:rgri...@linuxfoundation.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ganesh Ra
 jan':MAILTO:gan...@pensanetworks.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ahmed Elb
 ornou (amaged)':MAILTO:ama...@cisco.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Csatari, 
 Gergely (Nokia - HU/Budapest)'":MAILTO:gergely.csat...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'GUPTA, AL
 OK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=xudan (N):
 MAILTO:xuda...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'DRUTA, DA
 N'":MAILTO:dd5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Hesham ElB
 akoury:MAILTO:hesham.elbako...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Tallgren,
  Tapio (Nokia - FI/Espoo)'":MAILTO:tapio.tallg...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vul, Alex
 '":MAILTO:alex@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Reid Chen
 g (xincheng)':MAILTO:xinch...@cisco.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Tomasini,
  Lorenzo'":MAILTO:lorenzo.tomas...@fokus.fraunhofer.de
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Bernier, 

Re: [opnfv-tech-discuss] [yardstick] user-data parameter?

[Ross Brattain]

There are two modes for Heat context,  user-defined templates or generated 
templates.

With user-defined templates, you can add any Heat option you like.  Example for 
user_data 
https://git.opnfv.org/yardstick/tree/yardstick/vTC/apexlake/heat_templates/vTC.yaml#n79.
  If you are doing fancy stuff then you probably want your own heat templates.

For the generated templates, it looks like we have some code in the template 
generator, but it is not fully connected.

I made a quick patch, untested:  https://gerrit.opnfv.org/gerrit/#/c/30623/

--
Ross


On 03/15/2017 07:04 AM, Marco Varlese wrote:
> Hi,
> 
> Is there a way in yardstick to pass the user-data information to the VM 
> instance
> creation?
> 
> I'm thinking something inline with what I can do via "nova boot --user-data
> user_data.file"
> 
> Is there a way to pass either a file or instructions to Yardstick so that it 
> can
> execute or configure something via the cloud-init?
> 
> 
> Thanks,
> Marco
> ___
> 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] VNF to demonstrate VNF high availability across VIM

[joehuang]

Hello,

In multisite, we have one use cases ever discussed:

a VNF (telecom application) should, be able to realize high availability 
deployment across OpenStack instances.
For more detail of such an use cases, you can refer to 
https://git.opnfv.org/multisite/tree/docs/requirements/VNF_high_availability_across_VIM.rst

Now, it's time to bring it into reality.

After Tricircle provides cross OpenStack L2/L3 networking automation capability 
based on VxLAN, we'd like to have a demo in OPNFV Beijing summit to show how a 
VNF can run in 2 OpenStack instances and achieve high availability regardless 
how much nine, planned or unplanned downtime of an OpenStack cloud would be.

The VNF will work in cluster, active/active or active/standby mode, and it was 
deployed into two OpenStack instances, overlay VxLAN network will provide 
network plane for session/or other data replication between VNF parts, and also 
provide the VIP for VNF to provide service, if the VNF is running in 
active/standby, the standby VNF can take over the VIP and continue to provide 
service after the master or the openstack cloud is failed.

If you are interested in such an use case, please join us, help would be 
appreciated:

1. Provide or integrate sample VNF which is able to be deployed into multiple 
OpenStack instances to reach cloud level redundancy/failure escape.
2. Joint demo in Beijing OPNFV summit.
3. Build multi-site general infrastructure in E-release for CI/Functest/3rd 
party service, to provide general multi-region environment for services like 
Tricircle/Kingbird/Domino/Tacker which deal with multi-region functionalities.


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] [dovetail] Dovetail weekly meeting agenda

[HU, BIN]

IPv6 has been following the convention and rule. So we have been using, and 
will continue to use the *even* hour bridge, which is 
tech-projec...@opnfv.org.

Thanks
Bin

From: Tianhongbo [mailto:hongbo.tianhon...@huawei.com]
Sent: Wednesday, March 15, 2017 5:59 PM
To: HU, BIN ; Wenjing Chu ; Christopher 
Price ; Jose Lausuch 
; Gaoliang (kubi) ; 
morgan.richo...@orange.com; Tomofumi Hayashi ; Ulrich 
Kleber ; SULLIVAN, BRYAN L ; Dave 
Neary ; Lijun (Matthew) ; 
'TECH-DISCUSS OPNFV' 
Subject: 答复: [opnfv-tech-discuss] [dovetail] Dovetail weekly meeting agenda

Hi:
Thanks for your suggestion.

There are two accounts for the gotomeeting. That means it can support two 
meeting simultaneously .
For 7am. ARM are using the 
tech-proje...@opnfv.org, dovetail are using the 
tech-projec...@opnfv.org. there are two 
different account users.

To Bin: how about your IPv6? If IPv6 are using 
tech-proje...@opnfv.org, it will be ok for the 
dovetail. There is no conflict between dovetail and IPV6.

Is that ok?

Best regards

hongbo

发件人: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 HU, BIN
发送时间: 2017年3月16日 8:50
收件人: Wenjing Chu; Christopher Price; Jose Lausuch; Gaoliang (kubi); 
morgan.richo...@orange.com; Tomofumi 
Hayashi; Ulrich Kleber; SULLIVAN, BRYAN L; Dave Neary; Lijun (Matthew); 
'TECH-DISCUSS OPNFV'
主题: Re: [opnfv-tech-discuss] [dovetail] Dovetail weekly meeting agenda

I suggest that you keep the 6am PDT, which is now UTC 13:00 / 21:00 in China.

Otherwise, you will conflict with ARM Band (7am PDT) or IPv6 (8am PDT) no 
matter you use *odd* hour bridge or *even* hour bridge.

Thanks
Bin

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Wenjing Chu
Sent: Wednesday, March 15, 2017 5:33 PM
To: Christopher Price 
>; Jose 
Lausuch >; Gaoliang 
(kubi) >; 
morgan.richo...@orange.com; Tomofumi Hayashi 
>; Ulrich Kleber 
>; SULLIVAN, BRYAN L 
>; Dave Neary 
>; Lijun (Matthew) 
>; 'TECH-DISCUSS 
OPNFV' 
>
Subject: [opnfv-tech-discuss] [dovetail] Dovetail weekly meeting agenda


Here is a list of topics I propose we try to cover this Friday:


1)  Test case requirement update (Dave Neary) – 20 min

2)  Danube plan review – agreement on TSC report on 3/21 (Wenjing) – 20 min

3)  Functest/yardstick/testWG dependencies update: result DB, refstack, 
interface, http/https – (Mathew/Jose/Chris P…) – 15 min

4)  Dovetail test/qa/CI requirements (Uli/Leo) – 15 min

5)  How to get started on test area/test case review (Bryan/Wenjing) – 15 
min

6)  AOB – 5 min

This is based on a 1.5 hour long meeting as we discussed last week. If you are 
to lead a topic, please come prepared so we can make max use of the meeting 
time. Thanks.

I also saw Hongbo’s meeting invite that reverts back to our original 7AM PDT 
spot (while rest of the world stays the same hour). I’m not sure if that slot 
is free from GTM bridge conflict for 7:00 – 8:30 period, or if something needs 
to be changed. Hongbo, can you help sort the bridge problem out? I’m unable to 
login to verify one way or the other. It says I have no permission.

Also, Does anyone in US have problem with the new time?

Regards
Wenjing

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

[opnfv-tech-discuss] 答复: [dovetail] Dovetail weekly meeting agenda

[Tianhongbo]

Hi:
Thanks for your suggestion.

There are two accounts for the gotomeeting. That means it can support two 
meeting simultaneously .
For 7am. ARM are using the 
tech-proje...@opnfv.org, dovetail are using the 
tech-projec...@opnfv.org. there are two 
different account users.

To Bin: how about your IPv6? If IPv6 are using 
tech-proje...@opnfv.org, it will be ok for the 
dovetail. There is no conflict between dovetail and IPV6.

Is that ok?

Best regards

hongbo

发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 HU, BIN
发送时间: 2017年3月16日 8:50
收件人: Wenjing Chu; Christopher Price; Jose Lausuch; Gaoliang (kubi); 
morgan.richo...@orange.com; Tomofumi Hayashi; Ulrich Kleber; SULLIVAN, BRYAN L; 
Dave Neary; Lijun (Matthew); 'TECH-DISCUSS OPNFV'
主题: Re: [opnfv-tech-discuss] [dovetail] Dovetail weekly meeting agenda

I suggest that you keep the 6am PDT, which is now UTC 13:00 / 21:00 in China.

Otherwise, you will conflict with ARM Band (7am PDT) or IPv6 (8am PDT) no 
matter you use *odd* hour bridge or *even* hour bridge.

Thanks
Bin

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Wenjing Chu
Sent: Wednesday, March 15, 2017 5:33 PM
To: Christopher Price 
>; Jose 
Lausuch >; Gaoliang 
(kubi) >; 
morgan.richo...@orange.com; Tomofumi Hayashi 
>; Ulrich Kleber 
>; SULLIVAN, BRYAN L 
>; Dave Neary 
>; Lijun (Matthew) 
>; 'TECH-DISCUSS 
OPNFV' 
>
Subject: [opnfv-tech-discuss] [dovetail] Dovetail weekly meeting agenda


Here is a list of topics I propose we try to cover this Friday:


1)  Test case requirement update (Dave Neary) – 20 min

2)  Danube plan review – agreement on TSC report on 3/21 (Wenjing) – 20 min

3)  Functest/yardstick/testWG dependencies update: result DB, refstack, 
interface, http/https – (Mathew/Jose/Chris P…) – 15 min

4)  Dovetail test/qa/CI requirements (Uli/Leo) – 15 min

5)  How to get started on test area/test case review (Bryan/Wenjing) – 15 
min

6)  AOB – 5 min

This is based on a 1.5 hour long meeting as we discussed last week. If you are 
to lead a topic, please come prepared so we can make max use of the meeting 
time. Thanks.

I also saw Hongbo’s meeting invite that reverts back to our original 7AM PDT 
spot (while rest of the world stays the same hour). I’m not sure if that slot 
is free from GTM bridge conflict for 7:00 – 8:30 period, or if something needs 
to be changed. Hongbo, can you help sort the bridge problem out? I’m unable to 
login to verify one way or the other. It says I have no permission.

Also, Does anyone in US have problem with the new time?

Regards
Wenjing

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

[opnfv-tech-discuss] [dovetail] Dovetail weekly meeting agenda

[Wenjing Chu]

Here is a list of topics I propose we try to cover this Friday:


1)  Test case requirement update (Dave Neary) – 20 min

2)  Danube plan review – agreement on TSC report on 3/21 (Wenjing) – 20 min

3)  Functest/yardstick/testWG dependencies update: result DB, refstack, 
interface, http/https – (Mathew/Jose/Chris P…) – 15 min

4)  Dovetail test/qa/CI requirements (Uli/Leo) – 15 min

5)  How to get started on test area/test case review (Bryan/Wenjing) – 15 
min

6)  AOB – 5 min

This is based on a 1.5 hour long meeting as we discussed last week. If you are 
to lead a topic, please come prepared so we can make max use of the meeting 
time. Thanks.

I also saw Hongbo’s meeting invite that reverts back to our original 7AM PDT 
spot (while rest of the world stays the same hour). I’m not sure if that slot 
is free from GTM bridge conflict for 7:00 – 8:30 period, or if something needs 
to be changed. Hongbo, can you help sort the bridge problem out? I’m unable to 
login to verify one way or the other. It says I have no permission.

Also, Does anyone in US have problem with the new time?

Regards
Wenjing

___
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] Colorado 3.0 doc issue for vswitchperf

[Cooper, Trevor]

Looks like it worked
http://artifacts.opnfv.org/opnfvdocs/colorado/3.0/docs/documentation/index.html



From: Cooper, Trevor
Sent: Wednesday, March 15, 2017 11:48 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [VSPERF] Colorado 3.0 doc issue for vswitchperf

I added the Colorado 3.0 label to stable head of Colorado branch ... 
https://gerrit.opnfv.org/gerrit/gitweb?p=vswitchperf.git;a=shortlog;h=refs/heads/stable/colorado

I am not sure if the Colorado docs will be automatically rebuilt ... is there 
still an active job for that?

http://artifacts.opnfv.org/vswitchperf/colorado/3.0/docs/index.html

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

[opnfv-tech-discuss] [VSPERF] Colorado 3.0 doc issue for vswitchperf

[Cooper, Trevor]

I added the Colorado 3.0 label to stable head of Colorado branch ... 
https://gerrit.opnfv.org/gerrit/gitweb?p=vswitchperf.git;a=shortlog;h=refs/heads/stable/colorado

I am not sure if the Colorado docs will be automatically rebuilt ... is there 
still an active job for that?

http://artifacts.opnfv.org/vswitchperf/colorado/3.0/docs/index.html

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

[opnfv-tech-discuss] [ovn4nfv] 2017 OPNFV Summit CFP Now Open

[Vikram Dham]

Hi All,

Deadline for OPNFV Summit CFP is March 27th. Please try to submit your 
proposals before that. If required we can discuss on IRC channel - 
#opnfv-ovn4nfv

Thanks,

Vikram

> Begin forwarded message:
> 
> From: Brandon Wick 
> Subject: [opnfv-tech-discuss] 2017 OPNFV Summit CFP Now Open
> Date: February 16, 2017 at 11:49:47 AM PST
> To: "opnfv-tech-dis." 
> 
> OPNFV Technical Community:
> 
> The Call for Proposals (CFP) for the 2017 OPNFV Summit in Beijing is now 
> open! Listed below is the link and the important dates. More information 
> about the Summit can be found on the OPNFV Summit Website here 
> .
> 
> CFP Link: 
> http://events.linuxfoundation.org/events/opnfv-summit/program/cfp-details 
> 
> 
> Dates To Remember:
> CFP Open: Thursday, February 16, 2017
> CFP Close: Monday, March 27, 2017, 11:59 PST
> CFP Notifications: Week of April 20, 2017
> Schedule Announced: Week of April 27, 2017
> Event Dates: June 12-15, 2017
> Question on submitting a proposal? Contact us at speak...@opnfv.org 
> .
> 
> We look forward to your submissions!
> 
> Best,
> 
> Brandon Wick
> OPNFV Head of Marketing, The Linux Foundation
> Mobile: +1.917.282.0960  Skype: wick.brandon
> Email / Google Talk: bw...@linuxfoundation.org 
> 
> 
> New Report! OPNFV Plugfest at UNH-IOL 
> 
> ___
> 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] Weekly meeting minutes, March 15

[Brady Allen Johnson]

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.2017-03-15-15.04.html

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

[opnfv-tech-discuss] [SFC] Weekly meeting agenda

[Brady Allen Johnson]

Let's discuss the following in today's meeting:



  *   ODL cleanup after deletion
  *   Classifier location
  *   Status of Tacker pull request
  *   AOB

Regards,

Brady

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

[opnfv-tech-discuss] [netready] Meeting agenda March 15

[Georg Kunz]

Hi all,

This is the agenda for today's meeting:


* Gluon integration

* Gluon lab setup

* Requirements document update

* AOB

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

[opnfv-tech-discuss] [Compass4NFV] weekly meeting of Mar.16

[Justin chi]

Hi team,

*Agenda of Mar.16 2017*

   - Danube release Status
  - Open-O scenario status
  - ONOS scenario status
   - OPNFV Summit Demo Discuss
   - E release
  - Requirements
  - K8s CI verification
   - Aob



   Weekly on Thursday at 0900 UTC
   IRC channel: #opnfv-compass4nfv


https://wiki.opnfv.org/display/meetings/Compass4nfv

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

Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for SFs/SFFs/Classifiers creation

[Manuel Buil]

Hello Babu,

Yes, that is the right place. Some sub-tests are still failing though. 
The deadline to have them working in next Friday 24th of March. However, 
try to launch them because everything should be working (except you will 
get a message that some sub-tests fail).


Regards,
Manuel

On 03/15/2017 01:09 PM, Babu Kothandaraman wrote:


Brady,


Thanks for your prompt reply, Sorry about that, we did 
actually deploy "os-odl_l2-sfc-noha" scenario. We were trying the func 
test in 
https://wiki.opnfv.org/display/sfc/Functest+SFC-ODL+-+Test+1 to test 
the deployment. But we are not sure if this is the right one to follow 
according to the discussion above. Is this the right guide to follow 
for testing the deployment?





Best Regards,

Babu


*From:* Brady Allen Johnson 
*Sent:* Wednesday, March 15, 2017 12:56:26 PM
*To:* Babu Kothandaraman; Michail Polenchuk; mb...@suse.com; 
achiv...@mera.ru

*Cc:* opnfv-tech-discuss@lists.opnfv.org
*Subject:* Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation



Babu,

I think it would be better to instead deploy OPNFV Colorado with the 
"os-odl_l2-sfc-noha" scenario. This document should help guide you 
through the installation:


http://artifacts.opnfv.org/sfc/colorado/2.0/docs/installationprocedure/index.html

Regards,

Brady

-Original Message-
*From*: Babu Kothandaraman >
*To*: Brady Allen Johnson >, 
Michail Polenchuk >, 
mb...@suse.com >, 
achiv...@mera.ru >
*Cc*: opnfv-tech-discuss@lists.opnfv.org 
>
*Subject*: Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation

*Date*: Wed, 15 Mar 2017 11:46:37 +

Hi Brady,


I'm Babu from Packetfront software, we have installed OPNFV colorado 
for os-odl_l2-nofeature-noha scenario in virtual environment. We want 
to test SFC usecase using tacker as VNF manager like you mentioned in 
the mail above, could you please guide us to some documentation 
relating to this?


Thanks in advance.



Best Regards,

Babu


*From:* opnfv-tech-discuss-boun...@lists.opnfv.org 
 on behalf of Brady Allen 
Johnson 

*Sent:* Wednesday, March 15, 2017 12:10:06 PM
*To:* Michail Polenchuk; mb...@suse.com; achiv...@mera.ru
*Cc:* opnfv-tech-discuss@lists.opnfv.org
*Subject:* Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation


Anton,

I should have been a bit more explicit in my previous email.

The SFC103/104 demos are intended for a stand-alone, Non-OpenStack 
(hence no OPNFV needed) setup. Basically, they use vagrant to setup 
the necessary VMs. These demos do */not/* use Tacker.


In an OPNFV deployment, there needs to be an entity that spins-up and 
manages VMs for the SFC SFs, and ODL wont (and shouldnt) do that. This 
functionality is called a VNF Manager. Tacker is a VNF Manager (and 
some orchestration) as it does VNF management and orchestrates the SF 
VM info to ODL SFC. If you dont use Tacker, and dont have another VNF 
Manager, then you'll need to handle the VMs by hand, which is 
possible, but can be very tedious.


Regards,

Brady

-Original Message-
*From*: "Chivkunov, Anton" >
*To*: Brady Allen Johnson >, 
Michail Polenchuk >, 
mb...@suse.com >
*Cc*: opnfv-tech-discuss@lists.opnfv.org 
>
*Subject*: RE: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation

*Date*: Wed, 15 Mar 2017 09:35:45 +

Hi Brady.

Thank you for your feedback! Yes, I saw demos 103/104 as well and the 
reason why I interested in 101/102 instead is because they don’t use 
Tacker, but 103/104 use it.


Our current installation based on instruction 

[opnfv-tech-discuss] [yardstick] user-data parameter?

[Marco Varlese]

Hi,

Is there a way in yardstick to pass the user-data information to the VM instance
creation?

I'm thinking something inline with what I can do via "nova boot --user-data
user_data.file"

Is there a way to pass either a file or instructions to Yardstick so that it can
execute or configure something via the cloud-init?


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

[opnfv-tech-discuss] Pharos Bi-Weekly Meeting

[Morgan, Jack]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Morgan, Jack":MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-discuss (opnfv-tech-discuss@lists.opnfv.org):MAILTO:opnfv-tech-discuss@l
 ists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Pharos Bi-Weekly Meeting Details\n\n   Weekly on
  Monday at 6:00 PST or 14:00 UTC\n   GTM Link https://global.gotomeeting.c
 om/join/819733085\n   Meeting Agenda at Pharos Meetings in Pharos wiki page\n   Minutes at Ph
 aros Meetings wiki page\n 
   IRC #opnfv-pharos on freenode.net\n   You can also dial in using your ph
 one with Access Code: 819-733-085\n United States +1 (312) 757-312
 6\n Australia +61 2 8355 1040\n Austria +43 7 2088 0034\n 
 Belgium +32 (0) 28 93 7018\n Canada +1 (647) 497-9350\n   
   Denmark +45 69 91 88 64\n Finland +358 (0) 923 17 0568\n
  France +33 (0) 170 950 592\n Germany +49 (0) 692 5736 7211\n 
 Ireland +353 (0) 15 360 728\n Italy +39 0 247 92 13 01\n  
Netherlands +31 (0) 208 080 219\n New Zealand +64 9 280 630
 2\n Norway +47 75 80 32 07\n Spain +34 911 82 9906\n  
Sweden +46 (0) 853 527 836\n Switzerland +41 (0) 435 0167 13\n 
 United Kingdom +44 (0) 330 221 0086\n\n\n
RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=MO;WKST=SU
SUMMARY;LANGUAGE=en-US:Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20170327T06
DTEND;TZID=Pacific Standard Time:20170327T07
UID:04008200E00074C5B7101A82E00830577C22599DD201000
 01000BFA3830B40D42946991DA2947304ACED
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170315T140224Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:GTM and #opnfv-pharos
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:214906849
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:TRUE
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] [opnfv-project-leads] [release][danube] Intent-to-Release for Danube scenarios

[Sofia Wallin]

And please don’t forget that scenarios intended for release need to be 
documented.

Templates can be found under 
opnfvdocs/docs/templates/release/scenarios/scenario.name/

Scenario descriptions for Colorado can be found 
here
If I’m not mistaken six out of these will be included in Danube and probably 
need to be updated and new scenarios need to be added.
I will update the composite document with the scenario status page as base.

Regards,
Sofia

From: opnfv-project-leads-boun...@lists.opnfv.org 
[mailto:opnfv-project-leads-boun...@lists.opnfv.org] On Behalf Of David McBride
Sent: den 14 mars 2017 20:55
To: TECH-DISCUSS OPNFV ; 
opnfv-project-leads ; Tapio Tallgren 
; Raymond Paik ; Aric 
Gardner 
Subject: [opnfv-project-leads] [release][danube] Intent-to-Release for Danube 
scenarios

Scenario Owners,

I need to get an idea of which scenarios will be releasing with Danube 1.0, 
2.0, and 3.0, respectively.  I've modified the scenario status 
page to add 
columns for intent-to-release.  Please update the table to indicate your plans. 
 In addition, I've also generated a scenario status table for Euphrates.  So, 
if you believe that you will not be able to release your scenario with Danube, 
you may move your scenario to the Euphrates scenario status 
page.

IMPORTANT NOTE!  PLEASE READ CAREFULLY!

  1.  Please be aware that you must support your scenario for each release 
subsequent to when you first plan to release.

 *   For example, if you release in Danube 1.0, then you MUST also support 
a release in 2.0 and 3.0.
 *   Similarly, if you first release your scenario in 2.0, then you must 
support a release in 3.0.
 *   Why does this matter?  If your scenario becomes broken after your 
initial release, you will need to fix it for each subsequent release.  Make 
sure that you are planning for this possibility.
 *   We only support the most recent minor release of any major release.  
This means that 2.0 replaces 1.0 and 3.0 replaces 2.0.
 *   Therefore, if you release your scenario in 1.0, and it is broken as we 
approach 2.0, and you don't fix it, your work is effectively gone because 1.0 
will no longer be available.

  1.  Installers MUST support ALL three releases, regardless of what your 
dependent scenarios are doing.
Let me know if you have any questions.

David

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

Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for SFs/SFFs/Classifiers creation

[Chivkunov, Anton]

Hi Brady.

Thank you for clarifications! Yes, I think I mixed up SFC 103 (which use 
vagrant) with 
https://github.com/trozet/sfc-random/blob/master/tacker_sfc_apex_walkthrough.txt,
 (which actually use Tacker).
*During last several weeks I’ve studied a lot of different documents to find 
out instruction, which will explain all details regarding SFC deployments and 
looks like I mixed up these two.

Ok, then I think 
https://github.com/trozet/sfc-random/blob/master/tacker_sfc_apex_walkthrough.txt
 is most suitable instruction for our OPNFV environment.

Thank you very much for your help!

BR/Anton.


From: Brady Allen Johnson [mailto:brady.allen.john...@ericsson.com]
Sent: Wednesday, March 15, 2017 2:10 PM
To: Michail Polenchuk; mb...@suse.com; Chivkunov, Anton
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation


Anton,

I should have been a bit more explicit in my previous email.

The SFC103/104 demos are intended for a stand-alone, Non-OpenStack (hence no 
OPNFV needed) setup. Basically, they use vagrant to setup the necessary VMs. 
These demos do not use Tacker.

In an OPNFV deployment, there needs to be an entity that spins-up and manages 
VMs for the SFC SFs, and ODL wont (and shouldnt) do that. This functionality is 
called a VNF Manager. Tacker is a VNF Manager (and some orchestration) as it 
does VNF management and orchestrates the SF VM info to ODL SFC. If you dont use 
Tacker, and dont have another VNF Manager, then you'll need to handle the VMs 
by hand, which is possible, but can be very tedious.

Regards,

Brady

-Original Message-
From: "Chivkunov, Anton" 
>
To: Brady Allen Johnson 
>,
 Michail Polenchuk 
>,
 mb...@suse.com 
>
Cc: 
opnfv-tech-discuss@lists.opnfv.org 
>
Subject: RE: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation
Date: Wed, 15 Mar 2017 09:35:45 +

Hi Brady.

Thank you for your feedback! Yes, I saw demos 103/104 as well and the reason 
why I interested in 101/102 instead is because they don’t use Tacker, but 
103/104 use it.
Our current installation based on instruction 
http://artifacts.opnfv.org/sfc/review/20587/installationprocedure-single/index.html
 (5.2.4. Feature configuration on existing Fuel), and this instruction didn’t 
contain installation of Tacker plugin. Only next two are mentioned there:
fuel plugins --install fuel-plugin-ovs-*.noarch.rpm
fuel plugins --install opendaylight-*.noarch.rpm

Therefore we have no Tacker installed currently. It is not big problem (sure we 
can install Tacker), but this is the reason why we looked for the way how to 
run SFC without Tacker.
Meanwhile, we have setup with 3 Controller and 2 compute nodes. I’m wondering 
if there are some significant difference in compare with VM setup (we have no 
virtualbox & vagrant, which were used in SFC103)?

BR/Anton.

From: Brady Allen Johnson [mailto:brady.allen.john...@ericsson.com]
Sent: Wednesday, March 15, 2017 12:22 PM
To: Michail Polenchuk; mb...@suse.com; Chivkunov, Anton
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation


Anton,

The SFC101 and 102 demos are outdated and no longer supported. Its best to look 
at either the SFC103 or 104 demos. The sfc-agent is still used in SFC103, but 
we will soon stop supporting it.

The SFC103 demo is a great way to run and execute SFC in a single VM. If you 
want to create SFs, SFFs, and classifiers in an OPNFV context, the best would 
be to use Tacker.

Regards,

Brady


-Original Message-
From: Michael Polenchuk 
>
To: "Chivkunov, Anton" 
>, 
Manuel Buil >
Cc: 
opnfv-tech-discuss@lists.opnfv.org 
>
Subject: Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation
Date: Wed, 15 Mar 2017 11:45:46 +0400

Hi Anton,

+ Manuel
I believe Manuel has more experience with SFC than me.

On Wed, Mar 15, 2017 at 10:09 AM, Chivkunov, 

Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for SFs/SFFs/Classifiers creation

[Chivkunov, Anton]

Hi Brady.

Thank you for your feedback! Yes, I saw demos 103/104 as well and the reason 
why I interested in 101/102 instead is because they don’t use Tacker, but 
103/104 use it.
Our current installation based on instruction 
http://artifacts.opnfv.org/sfc/review/20587/installationprocedure-single/index.html
 (5.2.4. Feature configuration on existing Fuel), and this instruction didn’t 
contain installation of Tacker plugin. Only next two are mentioned there:
fuel plugins --install fuel-plugin-ovs-*.noarch.rpm
fuel plugins --install opendaylight-*.noarch.rpm

Therefore we have no Tacker installed currently. It is not big problem (sure we 
can install Tacker), but this is the reason why we looked for the way how to 
run SFC without Tacker.
Meanwhile, we have setup with 3 Controller and 2 compute nodes. I’m wondering 
if there are some significant difference in compare with VM setup (we have no 
virtualbox & vagrant, which were used in SFC103)?

BR/Anton.

From: Brady Allen Johnson [mailto:brady.allen.john...@ericsson.com]
Sent: Wednesday, March 15, 2017 12:22 PM
To: Michail Polenchuk; mb...@suse.com; Chivkunov, Anton
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation


Anton,

The SFC101 and 102 demos are outdated and no longer supported. Its best to look 
at either the SFC103 or 104 demos. The sfc-agent is still used in SFC103, but 
we will soon stop supporting it.

The SFC103 demo is a great way to run and execute SFC in a single VM. If you 
want to create SFs, SFFs, and classifiers in an OPNFV context, the best would 
be to use Tacker.

Regards,

Brady


-Original Message-
From: Michael Polenchuk 
>
To: "Chivkunov, Anton" 
>, 
Manuel Buil >
Cc: 
opnfv-tech-discuss@lists.opnfv.org 
>
Subject: Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation
Date: Wed, 15 Mar 2017 11:45:46 +0400

Hi Anton,

+ Manuel
I believe Manuel has more experience with SFC than me.

On Wed, Mar 15, 2017 at 10:09 AM, Chivkunov, Anton 
> wrote:

Hi Michael.

If I didn’t cross the limit yet, I want to ask one more question about PlugIn ☺
On SFC main page 
(https://wiki.opendaylight.org/view/Service_Function_Chaining:Main) there are 
several Demos available. Demos 101&102 describe procedure of 
SFs/SFFs/Classifiers creation 
(https://drive.google.com/file/d/0BzS_qWNqsnQbUnEzU3BqVzdueTQ/view).
There mentioned that SFC agent have to be started on corresponding node for 
this purpose. To start SFC agent there is special script “start_agent.sh”. But 
in our installation, with ODL/SFC as Plugin, we have no this script available. 
I’m wondering if we need just to load this script from SFC repo and use it, or 
there is another method for SFs/SFFs/Classifiers creation provided in 
environments, deployed by Fuel, and we should use some other way to create 
SFs/SFFs/Classifiers?

*Not 100% sure that this question is really related to plugin. If it is not, 
then please sorry for this.

BR/Anton.

From: Chivkunov, Anton
Sent: Friday, March 03, 2017 11:20 AM
To: 'Michael Polenchuk'
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [fuel][plugins][odl] HW requirements for ODL 
Controller with SFC.

Hi Michael.

Thank you for advice!
Currently we are trying to use our most powerful node (16Gb of RAM and 4-cores 
CPU) for Openstack + ODL Controller. Also we requested additional RAM for all 5 
nodes, to have 16-32Gb on each.
If it will not help we also will try with dedicated node for ODL controller as 
you suggested.

BR/Anton.

From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Friday, March 03, 2017 11:10 AM
To: Chivkunov, Anton
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [fuel][plugins][odl] HW requirements for ODL 
Controller with SFC.

Hi Anton,
Definitely the timeout and low performance caused by RAM capacity. I guess you 
have a lot of processes in swap.
I would recommend to dedicate one node to opendaylight controller since 8Gb is 
actually ain't enough for openstack+odl.
Also for the openstack controllers itself the minimum/required RAM is ~10-11Gb.

On Thu, Mar 2, 2017 at 2:33 PM, Chivkunov, Anton 
> wrote:
Hi all.

Sorry to bother you again, but we want to consult regarding HW requirements for 
Controller node, which act as ODL controller as well.
As it was described in initial mail, we have an 

Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for SFs/SFFs/Classifiers creation

[Babu Kothandaraman]

Brady,


Thanks for your prompt reply, Sorry about that, we did actually deploy 
"os-odl_l2-sfc-noha" scenario. We were trying the func test in 
https://wiki.opnfv.org/display/sfc/Functest+SFC-ODL+-+Test+1 to test the 
deployment. But we are not sure if this is the right one to follow according to 
the discussion above. Is this the right guide to follow for testing the 
deployment?




Best Regards,

Babu


From: Brady Allen Johnson 
Sent: Wednesday, March 15, 2017 12:56:26 PM
To: Babu Kothandaraman; Michail Polenchuk; mb...@suse.com; achiv...@mera.ru
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation



Babu,

I think it would be better to instead deploy OPNFV Colorado with the 
"os-odl_l2-sfc-noha" scenario. This document should help guide you through the 
installation:

http://artifacts.opnfv.org/sfc/colorado/2.0/docs/installationprocedure/index.html

Regards,

Brady

-Original Message-
From: Babu Kothandaraman 
>
To: Brady Allen Johnson 
>,
 Michail Polenchuk 
>,
 mb...@suse.com 
>, 
achiv...@mera.ru 
>
Cc: opnfv-tech-discuss@lists.opnfv.org 
>
Subject: Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation
Date: Wed, 15 Mar 2017 11:46:37 +


Hi Brady,


I'm Babu from Packetfront software, we have installed OPNFV colorado for 
os-odl_l2-nofeature-noha scenario in virtual environment. We want to test SFC 
usecase using tacker as VNF manager like you mentioned in the mail above, could 
you please guide us to some documentation relating to this?

Thanks in advance.



Best Regards,

Babu


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
 on behalf of Brady Allen Johnson 

Sent: Wednesday, March 15, 2017 12:10:06 PM
To: Michail Polenchuk; mb...@suse.com; achiv...@mera.ru
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation


Anton,

I should have been a bit more explicit in my previous email.

The SFC103/104 demos are intended for a stand-alone, Non-OpenStack (hence no 
OPNFV needed) setup. Basically, they use vagrant to setup the necessary VMs. 
These demos do not use Tacker.

In an OPNFV deployment, there needs to be an entity that spins-up and manages 
VMs for the SFC SFs, and ODL wont (and shouldnt) do that. This functionality is 
called a VNF Manager. Tacker is a VNF Manager (and some orchestration) as it 
does VNF management and orchestrates the SF VM info to ODL SFC. If you dont use 
Tacker, and dont have another VNF Manager, then you'll need to handle the VMs 
by hand, which is possible, but can be very tedious.

Regards,

Brady

-Original Message-
From: "Chivkunov, Anton" 
>
To: Brady Allen Johnson 
>,
 Michail Polenchuk 
>,
 mb...@suse.com 
>
Cc: opnfv-tech-discuss@lists.opnfv.org 
>
Subject: RE: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation
Date: Wed, 15 Mar 2017 09:35:45 +

Hi Brady.

Thank you for your feedback! Yes, I saw demos 103/104 as well and the reason 
why I interested in 101/102 instead is because they don’t use Tacker, but 
103/104 use it.
Our current installation based on instruction 
http://artifacts.opnfv.org/sfc/review/20587/installationprocedure-single/index.html
 (5.2.4. Feature configuration on existing Fuel), and this instruction didn’t 
contain installation of Tacker plugin. Only next two are mentioned there:
fuel plugins --install fuel-plugin-ovs-*.noarch.rpm
fuel plugins --install opendaylight-*.noarch.rpm

Therefore we have no Tacker installed currently. It is not big problem (sure we 
can install Tacker), but this is the reason why we looked for the way how to 
run SFC without Tacker.
Meanwhile, we have setup with 3 Controller and 2 

[opnfv-tech-discuss] [dovetail]weekly dovetail meeting

[Tianhongbo]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:China 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=Tianhongbo:MAILTO:hongbo.tianhon...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='TECH-DISC
 USS OPNFV':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Christoph
 er Price':MAILTO:christopher.pr...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Dave Near
 y':MAILTO:dne...@redhat.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='marko.a.k
 ui...@nokia.com':MAILTO:marko.a.kui...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Rautakump
 u, Mika (Nokia - FI/Espoo)'":MAILTO:mika.rautaku...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='sheng-ann
 .y...@ericsson.com':MAILTO:sheng-ann...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='yangjiany
 j...@chinamobile.com':MAILTO:yangjian...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='zhang.jun
 3...@zte.com.cn':MAILTO:zhang.ju...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'HU, BIN'":
 MAILTO:bh5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='lma@biigr
 oup.cn':MAILTO:l...@biigroup.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tetsuya N
 akamura':MAILTO:t.nakam...@cablelabs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Wenjing Ch
 u:MAILTO:wenjing@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Christophe
 r Donley (Chris):MAILTO:christopher.don...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Jose Laus
 uch':MAILTO:jose.laus...@ericsson.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='Shobhan A
 yyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Canio Cil
 lis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Marco Var
 lese':MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Kedalagud
 de, Meghashree Dattatri'":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Lawrence 
 Lamers':MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Georg Kun
 z':MAILTO:georg.k...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Maria Toe
 roe':MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Rathnakum
 ar Kayyar':MAILTO:rkay...@lcnpl.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Gabor Hal
 ász':MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Pierre Ly
 nch':MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='rgrigar@l
 inuxfoundation.org':MAILTO:rgri...@linuxfoundation.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ganesh Ra
 jan':MAILTO:gan...@pensanetworks.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ahmed Elb
 ornou (amaged)':MAILTO:ama...@cisco.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Csatari, 
 Gergely (Nokia - HU/Budapest)'":MAILTO:gergely.csat...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'GUPTA, AL
 OK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=xudan (N):
 MAILTO:xuda...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'DRUTA, DA
 N'":MAILTO:dd5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Hesham ElB
 akoury:MAILTO:hesham.elbako...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Tallgren,
  Tapio (Nokia - FI/Espoo)'":MAILTO:tapio.tallg...@nokia.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vul, Alex
 '":MAILTO:alex@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Reid Chen
 g (xincheng)':MAILTO:xinch...@cisco.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Tomasini,
  Lorenzo'":MAILTO:lorenzo.tomas...@fokus.fraunhofer.de
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Bernier, 

Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for SFs/SFFs/Classifiers creation

[Babu Kothandaraman]

Hi Brady,


I'm Babu from Packetfront software, we have installed OPNFV colorado for 
os-odl_l2-nofeature-noha scenario in virtual environment. We want to test SFC 
usecase using tacker as VNF manager like you mentioned in the mail above, could 
you please guide us to some documentation relating to this?

Thanks in advance.



Best Regards,

Babu


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
 on behalf of Brady Allen Johnson 

Sent: Wednesday, March 15, 2017 12:10:06 PM
To: Michail Polenchuk; mb...@suse.com; achiv...@mera.ru
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation


Anton,

I should have been a bit more explicit in my previous email.

The SFC103/104 demos are intended for a stand-alone, Non-OpenStack (hence no 
OPNFV needed) setup. Basically, they use vagrant to setup the necessary VMs. 
These demos do not use Tacker.

In an OPNFV deployment, there needs to be an entity that spins-up and manages 
VMs for the SFC SFs, and ODL wont (and shouldnt) do that. This functionality is 
called a VNF Manager. Tacker is a VNF Manager (and some orchestration) as it 
does VNF management and orchestrates the SF VM info to ODL SFC. If you dont use 
Tacker, and dont have another VNF Manager, then you'll need to handle the VMs 
by hand, which is possible, but can be very tedious.

Regards,

Brady

-Original Message-
From: "Chivkunov, Anton" 
>
To: Brady Allen Johnson 
>,
 Michail Polenchuk 
>,
 mb...@suse.com 
>
Cc: opnfv-tech-discuss@lists.opnfv.org 
>
Subject: RE: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation
Date: Wed, 15 Mar 2017 09:35:45 +

Hi Brady.

Thank you for your feedback! Yes, I saw demos 103/104 as well and the reason 
why I interested in 101/102 instead is because they don’t use Tacker, but 
103/104 use it.
Our current installation based on instruction 
http://artifacts.opnfv.org/sfc/review/20587/installationprocedure-single/index.html
 (5.2.4. Feature configuration on existing Fuel), and this instruction didn’t 
contain installation of Tacker plugin. Only next two are mentioned there:
fuel plugins --install fuel-plugin-ovs-*.noarch.rpm
fuel plugins --install opendaylight-*.noarch.rpm

Therefore we have no Tacker installed currently. It is not big problem (sure we 
can install Tacker), but this is the reason why we looked for the way how to 
run SFC without Tacker.
Meanwhile, we have setup with 3 Controller and 2 compute nodes. I’m wondering 
if there are some significant difference in compare with VM setup (we have no 
virtualbox & vagrant, which were used in SFC103)?

BR/Anton.

From: Brady Allen Johnson [mailto:brady.allen.john...@ericsson.com]
Sent: Wednesday, March 15, 2017 12:22 PM
To: Michail Polenchuk; mb...@suse.com; Chivkunov, Anton
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation


Anton,

The SFC101 and 102 demos are outdated and no longer supported. Its best to look 
at either the SFC103 or 104 demos. The sfc-agent is still used in SFC103, but 
we will soon stop supporting it.

The SFC103 demo is a great way to run and execute SFC in a single VM. If you 
want to create SFs, SFFs, and classifiers in an OPNFV context, the best would 
be to use Tacker.

Regards,

Brady


-Original Message-
From: Michael Polenchuk 
>
To: "Chivkunov, Anton" 
>, 
Manuel Buil >
Cc: 
opnfv-tech-discuss@lists.opnfv.org 
>
Subject: Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for 
SFs/SFFs/Classifiers creation
Date: Wed, 15 Mar 2017 11:45:46 +0400

Hi Anton,

+ Manuel
I believe Manuel has more experience with SFC than me.

On Wed, Mar 15, 2017 at 10:09 AM, Chivkunov, Anton 
> wrote:

Hi Michael.

If I didn’t cross the limit yet, I want to ask one more question about PlugIn :)
On SFC main page 
(https://wiki.opendaylight.org/view/Service_Function_Chaining:Main) there are 
several 

[opnfv-tech-discuss] [multisite]weekly meeting of Mar.16

[joehuang]

Hello, team,

Mar.16 2017 Agenda:

* Functest issue.

* E-Release discussion

* OPNFV Beijing summit prepration

* Open discussion

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

Other topics are also welcome 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] [fuel][plugins][odl] SFC agent for SFs/SFFs/Classifiers creation

[Michael Polenchuk]

Hi Anton,

+ Manuel
I believe Manuel has more experience with SFC than me.

On Wed, Mar 15, 2017 at 10:09 AM, Chivkunov, Anton  wrote:

> Hi Michael.
>
>
>
> If I didn’t cross the limit yet, I want to ask one more question about
> PlugIn J
>
> On SFC main page (https://wiki.opendaylight.org
> /view/Service_Function_Chaining:Main) there are several Demos available.
> Demos 101&102 describe procedure of SFs/SFFs/Classifiers creation (
> https://drive.google.com/file/d/0BzS_qWNqsnQbUnEzU3BqVzdueTQ/view).
>
> There mentioned that SFC agent have to be started on corresponding node
> for this purpose. To start SFC agent there is special script
> “start_agent.sh”. But in our installation, with ODL/SFC as Plugin, we have
> no this script available. I’m wondering if we need just to load this script
> from SFC repo and use it, or there is another method for
> SFs/SFFs/Classifiers creation provided in environments, deployed by Fuel,
> and we should use some other way to create SFs/SFFs/Classifiers?
>
>
>
> *Not 100% sure that this question is really related to plugin. If it is
> not, then please sorry for this.
>
>
>
> BR/Anton.
>
>
>
> *From:* Chivkunov, Anton
> *Sent:* Friday, March 03, 2017 11:20 AM
> *To:* 'Michael Polenchuk'
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* RE: [opnfv-tech-discuss] [fuel][plugins][odl] HW requirements
> for ODL Controller with SFC.
>
>
>
> Hi Michael.
>
>
>
> Thank you for advice!
>
> Currently we are trying to use our most powerful node (16Gb of RAM and
> 4-cores CPU) for Openstack + ODL Controller. Also we requested additional
> RAM for all 5 nodes, to have 16-32Gb on each.
>
> If it will not help we also will try with dedicated node for ODL
> controller as you suggested.
>
>
>
> BR/Anton.
>
>
>
> *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com
> ]
> *Sent:* Friday, March 03, 2017 11:10 AM
> *To:* Chivkunov, Anton
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* Re: [opnfv-tech-discuss] [fuel][plugins][odl] HW requirements
> for ODL Controller with SFC.
>
>
>
> Hi Anton,
>
> Definitely the timeout and low performance caused by RAM capacity. I guess
> you have a lot of processes in swap.
>
> I would recommend to dedicate one node to opendaylight controller since
> 8Gb is actually ain't enough for openstack+odl.
>
> Also for the openstack controllers itself the minimum/required RAM is
> ~10-11Gb.
>
>
>
> On Thu, Mar 2, 2017 at 2:33 PM, Chivkunov, Anton  wrote:
>
> Hi all.
>
>
>
> Sorry to bother you again, but we want to consult regarding HW
> requirements for Controller node, which act as ODL controller as well.
>
> As it was described in initial mail, we have an environment, which consist
> of Fuel master node, 3 Controller and 2 compute nodes.
>
> Controller nodes have 2-core Intel(R) Core(TM) i3-2100 CPUs. Two out of 3
> controllers have 8Gb of RAM, and one – 6 (not 16)Gb. ODL controller is one
> of 8Gb nodes.
>
>
>
> Compute nodes have 16Gb RAM and next CPUs:
>
> Intel(R) Core(TM) i5-4460  CPU
>
> Intel(R) Core(TM) i3 CPU
>
>
>
> First of all, quite often during deployments in this configuration one or
> few nodes can go away and back online:
> Node 'Controller1 n103262' is back online
>
> Node 'Controller1 n103262' has gone away
>
>
>
> After such attempts part of functions are not operational and many tests
> fails.
>
> When we are lucky and nodes were not away during deploy, most part of
> tests works, only few of them may fail due to timeouts and work only after
> several re-runs.
>
> At this step we are able to create/ping instances and so on, but as soon
> as we install SFC UI and try do to something there everything breaks:
>
> -  Existing instances are not pingable
>
> -  New instances can’t be created due to error from
> nova-scheduler (no hosts found)
>
> -  CPU load on  ODL controller becomes extremely high (up to
> 100%) and even Controller restart doesn’t help
>
> -  ODL controller goes away and back online in fuel time to time
>
> -  SFC UI very-very slow
>
>
>
> I’m wondering if all these problems are due to low performance of our
> node? In presentation from Luis Gomez I fount next table with requirements
> and we are above minimum values:
>
>
>
> But I guess it might be for configurations without OpenStack and when ODL
> work as PlugIn for Fuel/Openstack requirements should be higher?
>
> For example on http://artifacts.opnfv.org/pharos/docs/pharos-spec.html I
> see that 32Gb and Intel Xeon E5-2600v2 Series (Ivy Bridge and newer, or
> similar) are mentioned.
>
>
>
> Could you please confirm if our problems are really due to too low
> performance of HW and if so, then which characteristics are recommended?
>
>
>
> Thank you in advance!
>
> BR/Anton.
>
>
>
> *From:* Chivkunov, Anton
> *Sent:* Monday, February 20, 2017 11:28 AM
> *To:* 'Michael Polenchuk'
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* RE: [opnfv-tech-discuss]