Re: [opnfv-tech-discuss] [Models] Discussion with Guiseppe of OpenBaton and [opnfv-tect-discuss] [MANO WG]

[Prakash Ramchandran]

Hi all,

Good to see Bryan and Giuseppe discussing details of  Models and VES, look 
forward to see how this works out for OPNFV MANO Workgroup which both are 
participating.  I have added summary of Bryan's interactions and ideas to
https://wiki.opnfv.org/display/mano/OPNFV+Upstream+Projects

Also we are looking for OPNFV MANO WG voluntary participation from projects 
that are leveraging the co-ordination. We are looking to organize a 
Semi-monthly Goto Meeting sessions 2nd and 4the week (M/W/ or F) those who are 
interested please send me conformation (prkash.ramchand...@huawei.com)  and I 
will add you to Doodle polling.

Thanks
Prakash

Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@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 Carella, 
Giuseppe
Sent: Thursday, July 21, 2016 12:02 PM
To: SULLIVAN, BRYAN L
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Models] Discussion with Guiseppe of OpenBaton

Hi Bryan, all,

thanks for the introduction. Actually we have been very busy last days in 
preparing our minor release (v2.1.1) which we just announced to our community. 
We spent some effort during this minor release for improving our documentation 
and installation tools. This version of the NFVO provides now multi-tenancy in 
order to separate users into different projects, while the openstack plugin 
fully supports Mitaka. You should be able to bootstrap an open baton 
environment on top of an OpenStack VM in less than 5 minutes executing this 
single procedure [1]:
sh <(curl -s http://get.openbaton.org/bootstraps/bootstrap) release

Looking forward to collaborating with you and the community under these MANO 
related projects and talk to you soon in the upcoming conference calls.

[1] http://openbaton.github.io/documentation/

Cheers,
Giuseppe

Join us at the IEEE 5G Week in November in Berlin (http://www.berlin5gweek.org/)

On 20 Jul 2016, at 22:17, SULLIVAN, BRYAN L 
mailto:bs3...@att.com>> wrote:

Hi Models team,

Here are some notes about a discussion I had with Giuseppe Carella of the 
Frauhofer Fokus organization, about OpenBaton. I’ve mentioned OpenBaton a few 
times as one of the MANO-stack projects that should be in scope per the Models 
project’s goals.

Some links:
http://openbaton.github.io/index.html
http://openbaton.github.io/documentation/
http://sdn.ieee.org/images/files/pdf/FederatedTestbeds/may2016_carella-magedanz_-_the-open-baton-toolkit.pdf

OpenBaton is a Fraunhofer Fokus project that has implemented an ETSI-compliant 
MANO stack for orchestrating NFV workloads.
It interfaces with OpenStack NBI, and provides a modular, message-bus-based 
framework for creation of plugins that operate at the MANO stack layer.
They use Nagios to collect analytics directly from VNFs and process in their 
plugin framework, very similar in concept to what we presented at the OPNFV 
Summit for the VES project. The plugin framework itself is similar in concept 
to AT&T’s ECOMP DCAE and its plugins.
Giuseppe presented about OpenBaton at the OPNFV Summit: 
https://youtu.be/HKQpCjqrrcY
They are interested in getting engaged with the Models project in OPNFV, as 
well as the MANO WG that is forming.
VNFs that they use in testing include iPerf (https://iperf.fr/) and OpenIMSCore 
(http://www.openimscore.org/).
I will be working with Guiseppe to integrate their VNFM capability into OPNFV, 
as part of the Models project test cases. As with the other VNFM projects, a 
goal would be to execute these in CI/CD through the Functest project, once the 
test cases are stable.

Next week at the Models recurring meeting, let’s talk about next steps and 
related topics as noted in the latest agenda at  
https://wiki.opnfv.org/display/models/Models+Meetings

Thanks,
Bryan Sullivan | AT&T

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

[opnfv-tech-discuss] FW: About OPNFV Open-O integration project proposal requesting 7/28/2016 presentaion to weekly Tech meeting

[Prakash Ramchandran]

Bin.

I am forwarding the request to Bin and opnfv tech discuss list requesting third 
presentation for OPEN-O integration project now renamed as
OPNFV-OPEN-O and repo name as Opera.

https://wiki.opnfv.org/display/PROJ/OPNFV-OPEN-O

If we need to also inform TSC list let me know.

Thanks
Prakash

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






From: Yingjun Li
Sent: Thursday, July 21, 2016 5:45 PM
To: Prakash Ramchandran
Subject: RE: About OPNFV Open-O integration project proposal

Prakash

I already updated OPNFV wiki page with latest slides. Emailed updated slides to 
OPNFV TSC board members individually asking for their comments. I guess I am 
ready to present on 7/28. Could you please help to announcing OPNFV Open-O 
Integration project?

Here is the link.

https://wiki.opnfv.org/display/PROJ/OPNFV-OPEN-O

The link to OPNFV-MANO at this page 
https://wiki.opnfv.org/display/PROJ/Project+Proposals is broken. I guess we 
need to rename it as OPNFV Open-O, and link it to project proposal page.

Thanks
Yingjun


From: Prakash Ramchandran
Sent: Thursday, July 21, 2016 10:48 AM
To: Yingjun Li
Subject: RE: About OPNFV Open-O integration project proposal

Let me know when you want the announcement and will do that if and when you are 
ready to present like if you plan for 7/28 I will announce it today..Thanks 
Prakash

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






From: Yingjun Li
Sent: Thursday, July 21, 2016 10:43 AM
To: Prakash Ramchandran
Subject: FW: About OPNFV Open-O integration project proposal

Prakash

The following email thread is from Bin Hu's replay to my email yesterday. We 
don't have to create new project proposal, because we already have wiki page 
for the updated project proposal (Opera) . I will upload latest slides as PDF.

On his third item, announce new project to TSC and tech-discussion mailing 
list, I guess we need re-announce the project as new one?

Please advise.

Thanks
Yingjun

From: HU, BIN [mailto:bh5...@att.com]
Sent: Wednesday, July 20, 2016 7:20 PM
To: Yingjun Li
Cc: Christopher Donley (Chris)
Subject: RE: About OPNFV Open-O integration project proposal

Yingjun,

Thank you for letting me know.

When it is ready, I suggest that:

-  Create a wiki page for this new project proposal

-  Upload the presentation to the wiki page

-  Announce the new project proposal to tsc and tech-discuss mailing 
list

-  In your announcement, you can include the link to the project wiki 
and the presentation.

The clock starts once it is announced publicly. And we can take it next 
Thursday 7/28, and bring it to TSC in 2 weeks after public announcement.

Thank you
Bin

From: Yingjun Li [mailto:yingjun...@huawei.com]
Sent: Wednesday, July 20, 2016 5:58 PM
To: HU, BIN 
Cc: Christopher Donley (Chris) 
Subject: About OPNFV Open-O integration project proposal

Hi, Bin

The OPNFV Open-O integration project proposal review within Open-O is almost 
done. But it is not ready this week to present.

Before presenting at OPNFV TSC,  I'd like to share the presentation slides to 
hear your comments. Any comment is appreciated.

Basically following summarize what has been done to slides based on OPNFV TSC 
meeting and Open-O TSC.


1.   Narrow the project scope to Open-O integration requirement only

2.   Remove dependent projects and add Cross-Project coordination with 
OPNFV MANO WG

3.   Remove proposed committers and contributors, only keep accepted ones.

4.   Add vCPE use case based interfaces diagram as initial requirement.

5.   Re-scope Open-O components in the integration


I will be ready to present next week.

Best regards
Yingjun

[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: yingjun...@huawei.com<mailto:yingjun...@huawei.com>
Work:  +1 (408) 330-4502
Mobile: +1 (408) 390-3266
2330 Central Expy, Santa Clara, CA 95050, USA

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

Re: [opnfv-tech-discuss] About OPNFV Open-O integration project proposal requesting 7/28/2016 presentaion to weekly Tech meeting

[Prakash Ramchandran]

Iben,

Welcome back to hear from you after long.

OPEN-O
In defense of OPEN-O team they wanted the approval of their OPNE-O TSC prior to 
committing on use cases they plan to validate the OPNFV platform.
After first two presentations with the feedback from OPNV  they realized OPNFV 
community wants some alignment between OPNFV Projects and Upstream on Standards 
as well APIs which is evolving plus the Use case approach requires that they be 
specified as part of Projects to be able to drive the acceptance.

OPNFV
The first two presentations in Weekly Technical meeting in June, donned on the 
OPNFV Community to address its way to handle this through MANO WorkGroup  and I 
have initiated the efforts and if you and Sridhar Ramaswamy of Tacker team want 
to join  the OPNFV MANO WG Please follow up on the Poll invite for meetings.

Four O's OpenStack are universal  including  OPNFV  (Open Source, Open Design, 
Open Meetings and Open Community)
Yes these discussions are open and due to intermediate Berlin OPNFV summit we 
had discussions on MANO WG with Open Baton, JuJu and Tacker.
As details for MANO WG are still in incubation stage we waited to see what 
OPEN-O brings to table and how we can go about a minimum common agreed approach 
to the OPNFV moving above VIM in MANO Stack.

We need your constructive support and please feel free to join any meetings 
like you did in Brahmaputra release.

Thanks
Prakash


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






From: HU, BIN [mailto:bh5...@att.com]
Sent: Friday, July 22, 2016 10:12 AM
To: Iben Rodriguez
Cc: Prakash Ramchandran; opnfv-tech-discuss@lists.opnfv.org; 
opnfv-...@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] About OPNFV Open-O integration project 
proposal requesting 7/28/2016 presentaion to weekly Tech meeting

Iben,

No, it was open for discussion in June. I think they keep on changing the name, 
which caused the confusion. That’s why I always have a (wrong) impression that 
this “Opera” is a NEW project. But actually they wanted to continue it as the 
prior one in June.

Anyway, look at Weekly Technical Discussion page, find the agenda and minutes 
in June – the one related to MANO is the prior one.

Thanks
Bin

From: Iben Rodriguez [mailto:iben.rodrig...@gmail.com]
Sent: Friday, July 22, 2016 10:06 AM
To: HU, BIN 
Cc: Prakash Ramchandran 
Subject: Re: [opnfv-tech-discuss] About OPNFV Open-O integration project 
proposal requesting 7/28/2016 presentaion to weekly Tech meeting

When are the opera meetings taking place?  Are the "open" to anyone?

—
iben.rodrig...@gmail.com<mailto:iben.rodrig...@gmail.com>
+14087824726
Skype: ibenrodriguez
Twitter: @iben<http://twitter.com/iben>
Wechat: ibentc

On Jul 22, 2016, at 10:00, HU, BIN mailto:bh5...@att.com>> 
wrote:
Yingjun and Prakash,

I see. So it is the continuation of your prior project proposal that you still 
want to pursue. Sorry that I misunderstood that you wanted to discuss a new 
project. Now I understand that you want to continue to discuss the prior one.

Sure, I am happy to put it on agenda of technical community discussion on 7/28.

Meanwhile, if you wish, you can still ask TSC to review it on next Tuesday 7/26 
because it is allowed by process. This way, you may expedite the approval 
process. So it is your call.

Thank you
Bin

From: Prakash Ramchandran [mailto:prakash.ramchand...@huawei.com]
Sent: Friday, July 22, 2016 9:35 AM
To: HU, BIN mailto:bh5...@att.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: FW: About OPNFV Open-O integration project proposal requesting 
7/28/2016 presentaion to weekly Tech meeting

Bin.

I am forwarding the request to Bin and opnfv tech discuss list requesting third 
presentation for OPEN-O integration project now renamed as
OPNFV-OPEN-O and repo name as Opera.

https://wiki.opnfv.org/display/PROJ/OPNFV-OPEN-O

If we need to also inform TSC list let me know.

Thanks
Prakash

Prakash Ramchandran
 R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@huawei.com>
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






From: Yingjun Li
Sent: Thursday, July 21, 2016 5:45 PM
To: Prakash Ramchandran
Subject: RE: About OPNFV Open-O integration project proposal

Prakash

I already updated OPNFV wiki page with latest slides. Emailed updated slides to 
OPNFV TSC board members individually asking for their comments. I guess I am 
ready to present on 7/28. Could you please help to announcing OPNFV Open-O 
Integration project?

Here is the link.

https://wiki.opnfv.org/display/PROJ/OPNFV-OPEN-O

The link to OPNFV-MANO at this page 
https://wiki.opnfv.org/display/PROJ/Project+Proposals is brok

Re: [opnfv-tech-discuss] Like to create a mano WG page on wiki

[Prakash Ramchandran]

Dave,
We have made progress and continuing our efforts to get participation and 
please check your email for Doodle Poll for MANO WG meeting for incubation of 
the same.

The link to mano wg page is

http://wiki.opnfv.org/display/mano

The link to OPEN-O project proposal is

https://wiki.opnfv.org/display/PROJ/OPNFV-OPEN-O

Thanks
Prakash


Prakash Ramchandran
 R&D 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





-Original Message-
From: Dave Neary [mailto:dne...@redhat.com] 
Sent: Thursday, July 07, 2016 7:57 AM
To: Beierl, Mark; Prakash Ramchandran
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Like to create a mano WG page on wiki

Hi,

Just catching up with this post-Summit + vacation.

On 06/28/2016 09:30 PM, Beierl, Mark wrote:
> The top level under /display is the name of the "space" under which
> content is created.  In the case of /display/security, there is a space
> in the Wiki dedicated to the Security project.
> 
> Therefore if you are looking to create content under a /display/mano
> path, we need to create a mano project space.  Has a project approval
> been done for that yet?  If not, proposals go
> under https://wiki.opnfv.org/display/PROJ/Project+Proposals as well as
> related content until the project has been approved and gets its own
> project space.

Is permission needed to create a wiki page? Or is it the creation of a
space that needs permission?

I just want to be clear on why Prakash would need a project approval to
create a wiki page/hierarchy for MANO topics.

Thanks,
Dave.

>> On Jun 28, 2016, at 6:12 PM, Prakash Ramchandran
>> > <mailto:prakash.ramchand...@huawei.com>> wrote:
>>
>> Mark,
>> I would like to have permission to create new page as
>> https://wiki.opnfv.org/display/mano/
>>  
>> Trying to follow security Group  page
>>  
>> https://wiki.opnfv.org/display/security/
>>  
>> I have attached a first v 1.0 of site if you can create and let me
>> have access to edit with following content as first cut will be helpful.
>> Plus I invite all members of TECH-DISCUSS OPNFV to help build a strong
>> technical team to  help ONNFV succeed in its MANO efforts.
>> Please volunteer to Join as Contributors/Committers by adding your
>> name to Wiki or reply me with your interest to add when Wiki page is
>> ready.
>>  
>> Thanks
>> Prakash
>>  
>> *Prakash Ramchandran*
>> * R&D USA*
>> *FutureWei Technologies, Inc*
>> Email: prakash.ramchand...@huawei.com <mailto:s.c...@huawei.com>
>> Work:  +1 (408) 330-5489
>> Mobile: +1 (408) 406-5810
>> 2330 Central Expy, Santa Clara, CA 95050, USA
>>  
>> / /
>> / /
>>
>>  
>>  
>> 
> 
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> 

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] FW: About OPNFV Open-O integration project proposal requesting 7/28/2016 presentaion to weekly Tech meeting

[Prakash Ramchandran]

Chris,

I will go through along with Yingjun Li (Proposed PTL) if we have met all 
requirements as listed for Project creation and get back to you by Monday if we 
should bring to TSC for approval coming Tuesday or Next.

Thanks
Prakash

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






From: Christopher Price [mailto:chrispric...@gmail.com]
Sent: Friday, July 22, 2016 11:21 AM
To: Prakash Ramchandran; BIN HU
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] FW: About OPNFV Open-O integration project 
proposal requesting 7/28/2016 presentaion to weekly Tech meeting

Hi Prakash,

We try and keep the project creation process as simple as possible, please see 
the checklist and make sure you are following that sequence.
https://wiki.opnfv.org/display/DEV/Project+Proposal+Creation+Review+Checklist

/ Chris

From:  on behalf of Prakash 
Ramchandran 
Date: Friday 22 July 2016 at 18:34
To: BIN HU 
Cc: TECH-DISCUSS OPNFV 
Subject: [opnfv-tech-discuss] FW: About OPNFV Open-O integration project 
proposal requesting 7/28/2016 presentaion to weekly Tech meeting

Bin.

I am forwarding the request to Bin and opnfv tech discuss list requesting third 
presentation for OPEN-O integration project now renamed as
OPNFV-OPEN-O and repo name as Opera.

https://wiki.opnfv.org/display/PROJ/OPNFV-OPEN-O

If we need to also inform TSC list let me know.

Thanks
Prakash

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






From: Yingjun Li
Sent: Thursday, July 21, 2016 5:45 PM
To: Prakash Ramchandran
Subject: RE: About OPNFV Open-O integration project proposal

Prakash

I already updated OPNFV wiki page with latest slides. Emailed updated slides to 
OPNFV TSC board members individually asking for their comments. I guess I am 
ready to present on 7/28. Could you please help to announcing OPNFV Open-O 
Integration project?

Here is the link.

https://wiki.opnfv.org/display/PROJ/OPNFV-OPEN-O

The link to OPNFV-MANO at this page 
https://wiki.opnfv.org/display/PROJ/Project+Proposals is broken. I guess we 
need to rename it as OPNFV Open-O, and link it to project proposal page.

Thanks
Yingjun


From: Prakash Ramchandran
Sent: Thursday, July 21, 2016 10:48 AM
To: Yingjun Li
Subject: RE: About OPNFV Open-O integration project proposal

Let me know when you want the announcement and will do that if and when you are 
ready to present like if you plan for 7/28 I will announce it today..Thanks 
Prakash

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






From: Yingjun Li
Sent: Thursday, July 21, 2016 10:43 AM
To: Prakash Ramchandran
Subject: FW: About OPNFV Open-O integration project proposal

Prakash

The following email thread is from Bin Hu’s replay to my email yesterday. We 
don’t have to create new project proposal, because we already have wiki page 
for the updated project proposal (Opera) . I will upload latest slides as PDF.

On his third item, announce new project to TSC and tech-discussion mailing 
list, I guess we need re-announce the project as new one?

Please advise.

Thanks
Yingjun

From: HU, BIN [mailto:bh5...@att.com]
Sent: Wednesday, July 20, 2016 7:20 PM
To: Yingjun Li
Cc: Christopher Donley (Chris)
Subject: RE: About OPNFV Open-O integration project proposal

Yingjun,

Thank you for letting me know.

When it is ready, I suggest that:

-  Create a wiki page for this new project proposal

-  Upload the presentation to the wiki page

-  Announce the new project proposal to tsc and tech-discuss mailing 
list

-  In your announcement, you can include the link to the project wiki 
and the presentation.

The clock starts once it is announced publicly. And we can take it next 
Thursday 7/28, and bring it to TSC in 2 weeks after public announcement.

Thank you
Bin

From: Yingjun Li [mailto:yingjun...@huawei.com]
Sent: Wednesday, July 20, 2016 5:58 PM
To: HU, BIN 
Cc: Christopher Donley (Chris) 
Subject: About OPNFV Open-O integration project proposal

Hi, Bin

The OPNFV Open-O integration project proposal review within Open-O is almost 
done. But it is not ready this week to present.

Before presenting at OPNFV TSC,  I’d like to share the presentation slides to 
hear your comments. Any comment is appreciated.

Basically following summarize what has been done to slides based on OPNFV TSC 
meeting and Open-O TSC.


1.   Narrow the project scope to Open-O integration requirement only

2.   Remove de

Re: [opnfv-tech-discuss] FW: About OPNFV Open-O integration project proposal requesting 7/28/2016 presentaion to weekly Tech meeting

[Prakash Ramchandran]

Chris,

Note on checklist point 2 says
2. Make a new Project announcement on TSC & Tech-Discuss mailing list
My recollection is  at Least  I  did not make an announcement  in TSC list 
because the OPNFV-OPEN-O wanted first feedback from OPNFV community and go back 
to OPEN-O TSC to get approval. If Bin or Uli did it I do not recollect and will 
like to check with them if they did.

They have come back to present it next week as of today morning and so if I 
send TSC announcement today we should approve it  in next two weeks. So my take 
would be let me send an email requesting TSC for OPNFV-OPEN-O (Opera) project 
now and let this be approved as soon as TSC agrees that good faith efforts have 
been made by Project participants to officially approve it.

Thanks
Prakash


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






From: Christopher Price [mailto:chrispric...@gmail.com]
Sent: Friday, July 22, 2016 11:52 AM
To: Prakash Ramchandran; BIN HU
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] FW: About OPNFV Open-O integration project 
proposal requesting 7/28/2016 presentaion to weekly Tech meeting

Hi Prakash,

Sorry I have been on vacation and have not been tracking e-mail.
At what date did you pass checkpoint #2 on the checklist?

That sets the +2 weeks’ date for when it may be reviewed by the TSC.

/ Chris

From: Prakash Ramchandran 
Date: Friday 22 July 2016 at 20:32
To: Christopher Price , BIN HU 
Cc: TECH-DISCUSS OPNFV 
Subject: RE: [opnfv-tech-discuss] FW: About OPNFV Open-O integration project 
proposal requesting 7/28/2016 presentaion to weekly Tech meeting

Chris,

I will go through along with Yingjun Li (Proposed PTL) if we have met all 
requirements as listed for Project creation and get back to you by Monday if we 
should bring to TSC for approval coming Tuesday or Next.

Thanks
Prakash

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






From: Christopher Price [mailto:chrispric...@gmail.com]
Sent: Friday, July 22, 2016 11:21 AM
To: Prakash Ramchandran; BIN HU
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] FW: About OPNFV Open-O integration project 
proposal requesting 7/28/2016 presentaion to weekly Tech meeting

Hi Prakash,

We try and keep the project creation process as simple as possible, please see 
the checklist and make sure you are following that sequence.
https://wiki.opnfv.org/display/DEV/Project+Proposal+Creation+Review+Checklist

/ Chris

From:  on behalf of Prakash 
Ramchandran 
Date: Friday 22 July 2016 at 18:34
To: BIN HU 
Cc: TECH-DISCUSS OPNFV 
Subject: [opnfv-tech-discuss] FW: About OPNFV Open-O integration project 
proposal requesting 7/28/2016 presentaion to weekly Tech meeting

Bin.

I am forwarding the request to Bin and opnfv tech discuss list requesting third 
presentation for OPEN-O integration project now renamed as
OPNFV-OPEN-O and repo name as Opera.

https://wiki.opnfv.org/display/PROJ/OPNFV-OPEN-O

If we need to also inform TSC list let me know.

Thanks
Prakash

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






From: Yingjun Li
Sent: Thursday, July 21, 2016 5:45 PM
To: Prakash Ramchandran
Subject: RE: About OPNFV Open-O integration project proposal

Prakash

I already updated OPNFV wiki page with latest slides. Emailed updated slides to 
OPNFV TSC board members individually asking for their comments. I guess I am 
ready to present on 7/28. Could you please help to announcing OPNFV Open-O 
Integration project?

Here is the link.

https://wiki.opnfv.org/display/PROJ/OPNFV-OPEN-O

The link to OPNFV-MANO at this page 
https://wiki.opnfv.org/display/PROJ/Project+Proposals is broken. I guess we 
need to rename it as OPNFV Open-O, and link it to project proposal page.

Thanks
Yingjun


From: Prakash Ramchandran
Sent: Thursday, July 21, 2016 10:48 AM
To: Yingjun Li
Subject: RE: About OPNFV Open-O integration project proposal

Let me know when you want the announcement and will do that if and when you are 
ready to present like if you plan for 7/28 I will announce it today..Thanks 
Prakash

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






From: Yingjun Li
Sent: Thursday, July 21, 2016 10:43 AM
To: Prakash Ramchandran
Subject: FW: About OPNFV Open-

[opnfv-tech-discuss] Announcing New OPNFV-OPEN-O (Opera) - OPNFV OPEN-O Requirement for Integration

[Prakash Ramchandran]

Hi all,

OPNFV-OPEN-O Project took  feedback from June OPNFV weekly technical meetings 
(two presentations prior to OPNFV Berlin Summit) and additional  inputs at 
summit and OPEN-O TSC.

Now  OPNFV-OPNE-O Project is ready to steer  vCPE & SFC use cases in phased 
manner through OPEN-O integration with OPNFV

This will be done through generic NFVO and VNFM in upstream like JuJu, Tacker 
etc.

The details are on the Project proposal on link below.

https://wiki.opnfv.org/display/PROJ/OPNFV-OPEN-O

Please join weekly Tech. meeting next Thursday 7/28/2016 for further review to 
help TSC approval.
https://wiki.opnfv.org/display/PROJ/Weekly+Technical+Discussion
OPNFV OPEN-O Requirement for Integration

Thanks
Prakash


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






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

[opnfv-tech-discuss] Continuing on OPNFV MANO WorgGroup formation

[Prakash Ramchandran]

Hi all,

After some  efforts in community we have arrived at a small group of  about 7 
of 10  who are ready to meet mid week Wednesdays 1.30 PM PST.
We have 2 people for EU & China and will need additional or alternate meeting 
time to accommodate them.

In case any project has conflict with GoTo meeting time let me know, I will 
switch to using alternate access.

For now I will schedule
Wednesday Afternoon Pacific Daylight Time 1.30 PM - 2.30 PM
MANO WorkGroup meeting (IRC to use we will plan on the Goto Meeting or use 
#opnfv-mano)
https://global.gotomeetings.com/join/84351705
For this third meeting Agenda is
Begin
1. Welcome to MANO WG formation team (5 min)
2. Agenda bashing and last meetings summary (5 min)
3.  Review the stated goals on Wiki - https://wiki.opnfv.org/display/mano (25 
min)
4.  Inputs for preparation to present at subsequent TSC for providing/seeking 
any approvals and or guidance (15 min)
5. How do we go about upcoming projects relating to MANO (5 min)
End

Thanks
Prakash

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






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

Re: [opnfv-tech-discuss] Like to create a mano WG page on wiki

[Prakash Ramchandran]

Dave,

You asked me for SFC pointers, for now what I got from Yuyang in Yardstick is  
SFC use case 1 details. Use case 2 I will have to find from ODL team before 
Thursday meeting and pass to you.

There are also test cases developed in Yardstick including 1) VM creation; 2) 
SSH traffic; 3) Http traffic, please see following links.

OPNFV_YARDSTICK_TC029_SFC: VM Creation  
https://jira.opnfv.org/browse/YARDSTICK-189

OPNFV_YARDSTICK_TC030_SFC: Block HTTP   
https://jira.opnfv.org/browse/YARDSTICK-190

OPNFV_YARDSTICK_TC031_SFC: Block SSH
https://jira.opnfv.org/browse/YARDSTICK-191


The scripts are listed in 
https://git.opnfv.org/cgit/yardstick/commit/yardstick/benchmark?id=9a4ed05300b2aed28e8d2ec213049d5475655577

If you have any comments let me know from Centos or Apex point of view is this 
usable for you to test SFC?

Thanks
Prakash

Prakash Ramchandran
 R&D 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





-Original Message-
From: Prakash Ramchandran 
Sent: Friday, July 22, 2016 11:22 AM
To: 'Dave Neary'; Beierl, Mark
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] Like to create a mano WG page on wiki

Dave,
We have made progress and continuing our efforts to get participation and 
please check your email for Doodle Poll for MANO WG meeting for incubation of 
the same.

The link to mano wg page is

http://wiki.opnfv.org/display/mano

The link to OPEN-O project proposal is

https://wiki.opnfv.org/display/PROJ/OPNFV-OPEN-O

Thanks
Prakash


Prakash Ramchandran
 R&D 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





-Original Message-
From: Dave Neary [mailto:dne...@redhat.com] 
Sent: Thursday, July 07, 2016 7:57 AM
To: Beierl, Mark; Prakash Ramchandran
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Like to create a mano WG page on wiki

Hi,

Just catching up with this post-Summit + vacation.

On 06/28/2016 09:30 PM, Beierl, Mark wrote:
> The top level under /display is the name of the "space" under which
> content is created.  In the case of /display/security, there is a space
> in the Wiki dedicated to the Security project.
> 
> Therefore if you are looking to create content under a /display/mano
> path, we need to create a mano project space.  Has a project approval
> been done for that yet?  If not, proposals go
> under https://wiki.opnfv.org/display/PROJ/Project+Proposals as well as
> related content until the project has been approved and gets its own
> project space.

Is permission needed to create a wiki page? Or is it the creation of a
space that needs permission?

I just want to be clear on why Prakash would need a project approval to
create a wiki page/hierarchy for MANO topics.

Thanks,
Dave.

>> On Jun 28, 2016, at 6:12 PM, Prakash Ramchandran
>> > <mailto:prakash.ramchand...@huawei.com>> wrote:
>>
>> Mark,
>> I would like to have permission to create new page as
>> https://wiki.opnfv.org/display/mano/
>>  
>> Trying to follow security Group  page
>>  
>> https://wiki.opnfv.org/display/security/
>>  
>> I have attached a first v 1.0 of site if you can create and let me
>> have access to edit with following content as first cut will be helpful.
>> Plus I invite all members of TECH-DISCUSS OPNFV to help build a strong
>> technical team to  help ONNFV succeed in its MANO efforts.
>> Please volunteer to Join as Contributors/Committers by adding your
>> name to Wiki or reply me with your interest to add when Wiki page is
>> ready.
>>  
>> Thanks
>> Prakash
>>  
>> *Prakash Ramchandran*
>> * R&D USA*
>> *FutureWei Technologies, Inc*
>> Email: prakash.ramchand...@huawei.com <mailto:s.c...@huawei.com>
>> Work:  +1 (408) 330-5489
>> Mobile: +1 (408) 406-5810
>> 2330 Central Expy, Santa Clara, CA 95050, USA
>>  
>> / /
>> / /
>>
>>  
>>  
>> 
> 
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> 

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Kicking off nominations for Q2'2016 OPNFV Quarterly Awards

[Prakash Ramchandran]

I would like to nominate following OPNFV participants fro Q2 awards - Thanks
Code Development: Ulas Kozat
Collaboration: Bryan Sullivan
Documentation and  User Support: Mike Beierl
Integration:  Dan Radez
Testing:  Morgan Richomme

Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@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 Raymond Paik
Sent: Thursday, July 21, 2016 6:32 AM
To: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Kicking off nominations for Q2'2016 OPNFV 
Quarterly Awards

All,

A quick reminder to send your Q2 awards nominations if you haven't already.

Thanks,

Ray

On Mon, Jul 18, 2016 at 3:10 PM, Raymond Paik 
mailto:rp...@linuxfoundation.org>> wrote:
All,

It's again time to kick things off for the Q2 Awards.  As a reminder, this is 
to recognize contributions from OPNFV community members in the following 
categories.
·  Code development
·  Collaboration (e.g. across different OPNFV projects or with other upstream 
communities)
·  Documentation & User support
·  Integration
·  Testing
You'll notice that the "documentation" category has been expanded to include 
user support (e.g. via AskBot/opnfv-users mailing list) based on feedback from 
Jonas and others in the community. In order to give new people opportunities 
for recognition, the award winners from the previous quarter will not be 
eligible to win the same category 2 quarters in a row. As a reminder, below are 
the winners from Q1'2015.
·  Code development: Fatih Degirmenci
·  Collaboration: Tomi Juvonnen
·  Documentation: Chris Price
·  Integration: David Blaisonneau
·  Testing: Jose Lausuch
(So for example, Jose will not be eligible to win the Testing category again in 
Q2. However, he can be a winner for other categories)

If you'd like to nominate someone for any of the 5 areas above, please send me 
the following information by 5pm Pacific Time on July 27th (Wednesday).
·  Name/Company
·  Award category
·  Brief description of her/his contribution
Once nomination statements are collected, voting will be done by TSC members 
(e.g. on SurveyMonkey). Thanks and let me know if you have any questions.

Ray

___
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 platform API inventory and CI test coverage

[Prakash Ramchandran]

Bryan,

Catalog are still in MANO space and all VNFM have been assuming that is 
external to it with (VNFM has local catalog) and (NFVO  Global Catalog) and 
corresponding Interfaces we have are
So-Ca -> Service Catalog
Ca-Ma -> VNF & Infrastructure Catalog  listed in proposal for OMNFV MANO WG am 
pointing you to here.
refer
https://wiki.opnfv.org/display/mano/MANO+Group+Home?preview=/6825097/6826020/User%20Stories%20Zoom_v2-04.png


Issue here is one can use OpenStack (Admin or Tenant=Project)
Admin->Images (Glace Index of images)
Admin->Instance (Nova Instance VM details with host plus flavor plus active 
status etc)
or
Project->Images (Glace Index of images)
Project->Instance (Nova Instance VM details with host plus flavor plus active 
status etc)

But these apply only for image based representation of VNFs artifacts.

For Descriptors (TOSCA/YANG) the projects have been importing them from URI or 
some path listed in the projects.

If you look to OpenStack there is an application Catalogue plug-in to horizon
https://wiki.openstack.org/wiki/App-Catalog#Horizon_plugin_for_Native_Access
you can view the Project (tenant) Catalog by adding this as shown in link above.
Download this as part of any OPNFV Project with adding requirements for Catalog 
 and use it if you like as experiment.
https://git.openstack.org/cgit/openstack/app-catalog-ui which gives users the 
ability to search and retrieve App Catalog Contents directly from the Horizon.
Details are on

If any of the OPNFV projects have used any other methods please reply and would 
like to make user we have some common minimum agreement across projects for 
Catalog through MANO WG efforts.

Thanks
Prakash


Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@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: Wednesday, July 27, 2016 11:04 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] OPNFV platform API inventory and CI test coverage

Hi all,

I was wondering if there is any activity or capability in OPNFV yet to:

-  Build a living catalog (i.e. automatically maintained) of APIs 
exposed by the OPNFV platform components

-  Target CI tests to those APIs (I assume for OpenStack, Tempest tests 
cover some of this)

-  Track the test coverage of APIs per the catalog

Any info/pointers are appreciated.

Thanks,
Bryan Sullivan | AT&T

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

Re: [opnfv-tech-discuss] Continuing on OPNFV MANO WorgGroup formation

[Prakash Ramchandran]

Hi all,
The link and MANO WG Wiki pages were out of synch and due the incorrect  
meeting ID we waited for 10-15 minutes going over the wiki and fixed the links 
and now meeting page shows the  link corrected as follows

https://global.gotomeeting.com/join/843517045

Access Code: 843-517-045
Meeting ID: 843-517-045

Please note I will recheck the Doodle pole tomorrow by evening and announce the 
options we have to include all participants in one or two meetings and 
accordingly update the  wiki meeting page. If anyone need invite please send 
email to me soon.

For  Cross project co-ordinations, VNF On boarding and now Catalogue Interface 
as broughout by Bryan, and other aspects we will need to continue our sharing 
information across projects and agreeing to some common minimum so that we can 
build Marketplace for OPNFV like OpenStack does today using the Catalog 
plug-in. May be Bryan has an idea here for new project of building OPNF 
Catalogue for all Projects use with their GUI efforts and if it's done through 
different GUI like ODL, ONOS, Lab-as-a-service, OPNFV(OpenStack Horizon) etc, 
there could be something that may help all OPNFV Projects.

Thanks

Prakash









Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@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 Prakash 
Ramchandran
Sent: Friday, July 22, 2016 2:09 PM
To: opnfv-tech-discuss@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Continuing on OPNFV MANO WorgGroup formation

Hi all,

After some  efforts in community we have arrived at a small group of  about 7 
of 10  who are ready to meet mid week Wednesdays 1.30 PM PST.
We have 2 people for EU & China and will need additional or alternate meeting 
time to accommodate them.

In case any project has conflict with GoTo meeting time let me know, I will 
switch to using alternate access.

For now I will schedule
Wednesday Afternoon Pacific Daylight Time 1.30 PM - 2.30 PM
MANO WorkGroup meeting (IRC to use we will plan on the Goto Meeting or use 
#opnfv-mano)
https://global.gotomeetings.com/join/84351705
For this third meeting Agenda is
Begin
1. Welcome to MANO WG formation team (5 min)
2. Agenda bashing and last meetings summary (5 min)
3.  Review the stated goals on Wiki - https://wiki.opnfv.org/display/mano (25 
min)
4.  Inputs for preparation to present at subsequent TSC for providing/seeking 
any approvals and or guidance (15 min)
5. How do we go about upcoming projects relating to MANO (5 min)
End

Thanks
Prakash

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






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

[opnfv-tech-discuss] meetobot installtion for irc's like Dovtail, Domino...

[Prakash Ramchandran]

Hi all,

Most  old projects have the irc channels and meetbots installed along for 
recording meeting minutes in OPNFV.
The links below  not tell what we need to do on our irc channels to enable this.

The link https://wiki.opnfv.org/display/meetings/Meetbot
the link leads to another link https://wiki.debian.org/MeetBot/
and the manual is in http://meetbot.debian.net/Manual.html

All I can gather is we need some meetbot config file to be imported through 
python over possibly  the irc channel.

Can someone point to  procedure to install meebot on irc like
#opnfv-domino,
#opnfv-dovetail,
#opnfv-mano

So that I can ask MeiMei or some in infra team to help us simplify our irc 
channels for taking meeting note?
Also please update the local config file with appropriate entries to record the 
meeting logs on pages, formats etc.

Thanks
Prakash


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






#!/usr/bin/env python
#meetingLocalConfig.py

import 
class Config(object):
# These two are **required**:
logFileDir = '/home/richard/meetbot/'
logUrlPrefix = 'http://rkd.zgib.net/meetbot/'
filenamePattern = '%(channel)s/%%Y/%(channel)s.%%F-%%H.%%M'
MeetBotInfoURL = 'http://some_other_side.tld'
 ___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] OPNFV [Dovetall] Meeting Summary

[Prakash Ramchandran]

Hi all,

Since Tianhongbo could not make to the Got meeting or IRC, the meeting was IRC 
only on #opnfv-meeting

Since the time ran past 8.00 due to late start besides wanted to summarize what 
can we retain from last 2-3 meetings besides today to consolidate Actionable 
Items and responsibilities...

meetbot to make sure we take proper minutes during meeting on irc..Thanks 
Prakash
 [08:06] <@collabot> Minutes:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-29-14.25.html
[08:06] <@collabot> Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-29-14.25.txt
[08:06] <@collabot> Log:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-29-14.25.log.html
[08:06]  #info ChrisPriceAB proposes that we start a wiki page to 
define test case requirements, structure, and the procedure for considering new 
tests.
[08:06]  I guess that didn't get minuted...
[08:06]  Thanks everyone, feels like we made progress

Please if you want it delegated to someone else please respond back

Maybe we can spin up a wiki page under dovetail to walk through our test case 
requiremenents. Happy to start that. 
(ChrisPriceAB<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-29-14.25.log.html#l-100>,
 14:46:54)
Action 1: Chris Price to spin wiki page for dovetail test case requirements and 
others can help to update it based on some structure which Chris can propose
Action 2: Prakash will update the C&C guidance as listed below as request to 
Dovetail from C&C and we can debate it next week to
Action 3: Dave Neary to review and point any deviations we have here from the 
agreed scope of Dovetail and any concerns he has on SDNC, Installers etc. for 
use case testing or suggestions to help spirit of OPNFV to keep it Open to all
Action 4: Mathew Li - summarize IPv6  overlay (underlay out of scope for now) 
test efforts  that are taken up in different projects and consolidation of same 
for Dovetail once Chris Price spins the wiki with some structure to present

Here are my note from last  two meeting Action 2
Note C&C inputs to Dovetail  : Prakash has  summary of  C&C request as proposed 
by Chris Donley

* Chris Donley specified  directions to Dovetail stating that time is 
essence and we need to fit into plans to get Dovetail moving as the value for 
OPNFV by working with Compliance Verification Program (CVP) guidance.

* There was discussions on API vs. Use case (Blackbox) Approach.

* Since API from OPNFV projects are yet to be compiled and gap assessed 
with respect to ETSI TST APIs for many projects that have MANO implications, 
the baseline currently appears to be OPENSTACK + SDNC  and NB APIs are going to 
take time to settle.

* A black box approach with use cases in Release C that were taken up 
as part of roadmap and that will be addressed between SP & C&C while Dovetail 
should focus on use cases that were taken up in Release C under different 
projects.

* While OPNFV MANO Working group can address cross-project 
co-ordination , the testing can be based on Use cases with low bar to qualify 
at start and discussions moved to Dovetail framework and use cases to consider.

Dovetail framework  and use case discussions we had earlier can for now be 
expunged and revisit it after wiki is spun by Chris Price at next weekly 
meeting.

Thanks
Prakash




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






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

Re: [opnfv-tech-discuss] [Orchestra] new project proposal and MANO WG support for projects

[Prakash Ramchandran]

Dave,
We have started addressing few of your well founded concerns.

Trying to get MANO WG (workgroup) formed tying to identify MANO Stack issues 
for both NB /SB users wrt OPNFV VIM

1. cross-project relations (existing OPNFV Models, Parser, VES, Copper, Domino)
2. upstream NVFVO (Generic)  integration common minimum like Interface/APIs/Use 
cases to test and verify - OPEN-O, Open Baton, OSM etc.
3. Relation between VNFM (generic) - like Tacker, Juju etc.
4. Cross layer commonality for generic modules for compliance
5. Catalog bindings for  Local and Global serving of VNFs (and VSFs as some 
call) their on-boarding etc.
6. Your question on Templates which are both TOSA, YANG, Hybrid and standards 
as they evolve will also be subject of MANO WG.

I am planning to demonstrate next week MANO meeting some  Catalog and 
On-boarding possibilities to help arrive at some integration aspects that need 
to be fleshed out for OPNFV Eco system to provide Vendors the opportunity to 
build on top of generic capabilities.

Thus I believe the concerns will not run away soon, until Markets prefer what 
we do in OPNFV, we should be open to all upstream as well to internal projects 
that can build & deploy  missing pieces in the eco system.

Monday morning 8 AM PDT (15 UTC MANO WG) 
Monday morning 9 AM PDT ( 16 UTC) Models)- Cross Project co-ordination with 
Model

Wednesday afternoon 1.30 PM PDT (8.30 UTC) 
Wednesday evening  5 PM PDT ( 0 UTC Thursday) for cross project co-ordination 
other than Mode

Thanks
Prakash


Prakash Ramchandran
 R&D 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






-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dave Neary
Sent: Wednesday, August 03, 2016 1:44 PM
To: Liu Yuan; Carella, Giuseppe; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Orchestra] new project proposal

Hi Yuan,

Hasn't OPNFV-OPEN-O changed its name to Opera in its proposal? I'm not
ure why there needs to be a link to a specific project name.

I do have other feedback, though - I would love to know what
relationship, if any, Orchestra intends to have with MANO related
projects which are already in existence: Models, Parser, VES, Copper,
Domino. I have the same questions/concerns about Opera, for that matter.
I see a lot of words present in both architecture diagrams (Message
queue, NS engine/policy engine, analytics engine, generic VNFM) and some
common requirements that are not states (the need for an NSD, VNFFGD,
VNFD) which suggest to me that there is room for creating common
building blocks for these.

Thanks,
Dave.

On 08/02/2016 05:44 AM, Liu Yuan wrote:
> Hi Giuseppe,
> 
> I am confused about the name of the project. Your main objective is to
> integrate between Open Baton and OPNFV. There are many MANO /
> Orcheatrator open source projects, and there is a MANO group in the
> OPNFV. I don't think you could use the "Orchestra" to only appoint to
> the Open Baton, maybe named Open Baton or OPNFV-Open Baton are more better. 
> 
> Regards,
> Yuan
> 
> Liu Yuan
> liuyuan_c...@hotmail.com
> 
>  
> *From:* Carella, Giuseppe <mailto:giuseppe.care...@fokus.fraunhofer.de>
> *Date:* 2016-08-02 05:08
> *To:* opnfv-tech-discuss@lists.opnfv.org
> <mailto:opnfv-tech-discuss@lists.opnfv.org>
> *CC:* Michael Pauls <mailto:michael.pa...@tu-berlin.de>
> *Subject:* [opnfv-tech-discuss] [Orchestra] new project proposal
> Hi all, 
> 
> please find on the wiki [1] a new project proposal, named Orchestra,
> having as main objective the integration between Open Baton and
> OPNFV. We'll be available to present it during the next TSC call. 
> 
> Get in touch if you are interested in getting involved. 
> 
> [1] https://wiki.opnfv.org/display/PROJ/Orchestra
> 
> Cheers,
> Giuseppe
> 
> Join us at the IEEE 5G Week in November in
> Berlin (http://www.berlin5gweek.org/)
> 
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> 

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338
___
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] Yardstick-CI Docker image

[Prakash Ramchandran]

Hi all,

Recollect the discussions  we had earlier at OPNFV summit last year in Santa 
Clara where should we place Test functions VM or Containers?

1. Jump Server - Was easiest and acceptable to CI team
2. OPNFV Controller - This was optional however FUEL team uses it for example 
ODL installer  (Feature or  later Scenario)  as per my recollection
3. External server other than Jump Server - This was difficult as Pharos team 
did not want its configuration of 5 or less servers for PODs being violated.

May be we need to bring this  back to Infrastructure team on their ongoing Lab 
upgrades and  best practices they recommend and if there is a link to it please 
point out for all Projects and Test teams to review and plan.

Thanks
Prakash

Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@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 Lijun (Matthew)
Sent: Wednesday, August 03, 2016 11:49 PM
To: David XF1 Cui
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] 答复: Yardstick-CI Docker image

Hi

It’s a good question.

From my experience, it depends. It depends on if this docker will influence the 
already existing docker network. Compass now is OK. Even if you want to run on 
jumpserver, if it conflicts with the already existing docker network(if it has 
one), it will cause problems.
I think the original idea to isolate different test project codes by using 
docker, and jumperserver is usually a place to put from  view of architecture. 
In other words, it also will be OK if you put on some host/VM as long as 
correctly configured with the installer interface, just as what rally do, a 3rd 
party test tool.

By now, I think it’s OK for you to put it on control node. Since its test case 
grows, not sure if it will always OK depends on the test case design/running 
method.

MatthewLi

发件人: David XF1 Cui [mailto:cui...@lenovo.com]
发送时间: 2016年8月4日 13:53
收件人: Lijun (Matthew)
主题: RE: Yardstick-CI Docker image

Hi Matthew,

Thanks for your reply. It is very useful for me. But, I have another question 
about yardstick. Could I run yardstick on control node? Because the docker 
bring up from our jump host node could not access the public network 
temporarily.

Thanks

From: Lijun (Matthew) [mailto:matthew.li...@huawei.com]
Sent: Tuesday, August 02, 2016 11:45 AM
To: David XF1 Cui; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: 答复: Yardstick-CI Docker image

Hi

The link is https://hub.docker.com/u/opnfv/

For more info, u can refer 
https://git.opnfv.org/cgit/yardstick/tree/docs/userguide/03-installation.rst#n121

If u are interested with the CI docker job, u can see 
https://git.opnfv.org/cgit/releng/tree/jjb/opnfv/opnfv-docker.yml#n73


/MatthewLi

发件人: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 David XF1 Cui
发送时间: 2016年8月2日 11:12
收件人: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
主题: [opnfv-tech-discuss] Yardstick-CI Docker image

Hi guys,

I want to install YardStick using Docker in OPNFV PoC enviorment. I try to pull 
yardstick-ci docker from hub, but I can not get the right answer. I run docker 
search yardstiack and can not find the yardstick-ci docker also.
So, where is the yardstick-ci docker? Or other docker to try the run-benchmarks?

Thanks & BRs
David


David Cui (崔先锋)
Lenovo Research CTL
Lenovo China
6 Shangdi West Road, Haidian, BJ


cui...@lenovo.com<mailto:cui...@lenovo.com>
Ph: +86 010 58869420
Mobile: +86 18910869420

[cid:699D5EF3-0109-4F3E-B406-AF4689634910]

http://www.lenovo.com<http://www.lenovo.com/>
Forums<http://forums.lenovo.com/> | Blogs<http://lenovoblogs.com/> | 
Twitter<http://twitter.com/lenovo> | Facebook<http://www.facebook.com/lenovo> | 
Flickr<http://www.flickr.com/photos/lenovophotolibrary>




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

[opnfv-tech-discuss] [Dovetail] Aug 5 Dovetail meeting notes

[Prakash Ramchandran]

Here is today's OPNFV Dovetail meeting notes based on Gotomeeting and  
#opnfv-dovetail channels ...
Agenda:
1)start point(L3VPN, SFC and IPV6)
2)test cases structures
3) additional basic testcases( for SDN controller and NFVI...)
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827269
4)other issues

For more details, please refer to: 
https://wiki.opnfv.org/display/dovetail/Dovetail+Home

Summary Notes of discussions:

Chris defines what should be content of Dovetail
should focus on requirements and not project and release anagement
info test will be on SUT that includes OPNFV VIM + NFVi as shown in link
The details to follow the test plan
Bin says we should first verify Functest and Yardstick before we start on 
Dovetail
Dave & Chris say they should be standlone and as a subset may be needed
Purpose of the Dovetail here is to show what is needed for OPNF view of NFV 
compliance
Bin sees a potential issue here that Dovtail testing and OPNFV tests are 
different
CORD example may be able to be claim OPNFV compatibility through Dovetail but 
not from OPNFV Platform testing in Projects and Releases
Bin says Bryan wants CORD to run over OPNFV platform and Chris says its  
different as Release testing is diffrent from Dovetail testing
Same holds for OPEN-O and OpenBaton
Hongbo and Chris want to start form IPv6 overlay testing and Bin suggested we 
reuse most of what we have from Service VM IPv6 testing
Mathew stated he has started on it and can help
Testsuya Nakamura chimed he can help in adding some specifc IPv6 related to it 
for test case structure
Tetsuya says we need a clear definition for SUT IPv6, SFC or L3VPN before we 
start test plans for IPv6
What we are starting with can be IPv6 to establish test plan, test design and 
test case documentaion templates
Prioritizing the test cases can be taken at next meeting and define a link to 
the same
#action Hongbo to establish a link and bring use cases to bring to table for 
disucssing priority
further discussions over use case can be over email

07:51]  Minutes:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-dovetail/2016/opnfv-dovetail.2016-08-05-14.05.html
[07:51]  Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-dovetail/2016/opnfv-dovetail.2016-08-05-14.05.txt
[07:51]  Log:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-dovetail/2016/opnfv-dovetail.2016-08-05-14.05.log.html



Note People who attended the Gotomeeting are not listed here in link, please 
add them when Hongbo posts the summary to Dovetail wiki.
The include
Chris Price
Dave Neary
Bi Hu
Tetsuya Nakmura



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






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

[opnfv-tech-discuss] Here are some suggestion for use cases to look at for Dovetail

[Prakash Ramchandran]

Hi all,

I  though over the CVP program as was described by Chris and trying to build 
some uses case documents to submit for next week discussions based on our 
Dovetail meeting today.

If I am off the mark please correct me but this is what I understand from 
various interactions within community.

We can go over this at Models meeting Monday organized  by Bryan Sullivan and 
see how this pans out as lot of cross project co-ordination will be required to 
get to "OPNFV Inside" thinking.

Please use rst file and update it for getting it ready for approved to Dovetail 
repo.

Thanks

 Prakash


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








certification_usecase.pdf
Description: certification_usecase.pdf


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

Re: [opnfv-tech-discuss] Yardstick-CI Docker image

[Prakash Ramchandran]

David/Mathew,

Since was looking for similar test integration issues from Dovetail to 
Yardstick, saw some reference in Yardstick that may give you some clue of state 
of the art used in OPNFV projects...Since Mathew and Kubi are dealing with this 
they can give David better insight on this.

https://wiki.opnfv.org/display/yardstick/How+to+install+a+plug-in+into+Yardstick


Thanks
Prakash

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






From: Prakash Ramchandran
Sent: Thursday, August 04, 2016 11:03 AM
To: 'Lijun (Matthew)'; 'David XF1 Cui'
Cc: 'opnfv-tech-discuss@lists.opnfv.org'
Subject: RE: Yardstick-CI Docker image

Hi all,

Recollect the discussions  we had earlier at OPNFV summit last year in Santa 
Clara where should we place Test functions VM or Containers?

1. Jump Server - Was easiest and acceptable to CI team
2. OPNFV Controller - This was optional however FUEL team uses it for example 
ODL installer  (Feature or  later Scenario)  as per my recollection
3. External server other than Jump Server - This was difficult as Pharos team 
did not want its configuration of 5 or less servers for PODs being violated.

May be we need to bring this  back to Infrastructure team on their ongoing Lab 
upgrades and  best practices they recommend and if there is a link to it please 
point out for all Projects and Test teams to review and plan.

Thanks
Prakash

Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@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 Lijun (Matthew)
Sent: Wednesday, August 03, 2016 11:49 PM
To: David XF1 Cui
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] 答复: Yardstick-CI Docker image

Hi

It’s a good question.

From my experience, it depends. It depends on if this docker will influence the 
already existing docker network. Compass now is OK. Even if you want to run on 
jumpserver, if it conflicts with the already existing docker network(if it has 
one), it will cause problems.
I think the original idea to isolate different test project codes by using 
docker, and jumperserver is usually a place to put from  view of architecture. 
In other words, it also will be OK if you put on some host/VM as long as 
correctly configured with the installer interface, just as what rally do, a 3rd 
party test tool.

By now, I think it’s OK for you to put it on control node. Since its test case 
grows, not sure if it will always OK depends on the test case design/running 
method.

MatthewLi

发件人: David XF1 Cui [mailto:cui...@lenovo.com]
发送时间: 2016年8月4日 13:53
收件人: Lijun (Matthew)
主题: RE: Yardstick-CI Docker image

Hi Matthew,

Thanks for your reply. It is very useful for me. But, I have another question 
about yardstick. Could I run yardstick on control node? Because the docker 
bring up from our jump host node could not access the public network 
temporarily.

Thanks

From: Lijun (Matthew) [mailto:matthew.li...@huawei.com]
Sent: Tuesday, August 02, 2016 11:45 AM
To: David XF1 Cui; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: 答复: Yardstick-CI Docker image

Hi

The link is https://hub.docker.com/u/opnfv/

For more info, u can refer 
https://git.opnfv.org/cgit/yardstick/tree/docs/userguide/03-installation.rst#n121

If u are interested with the CI docker job, u can see 
https://git.opnfv.org/cgit/releng/tree/jjb/opnfv/opnfv-docker.yml#n73


/MatthewLi

发件人: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 David XF1 Cui
发送时间: 2016年8月2日 11:12
收件人: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
主题: [opnfv-tech-discuss] Yardstick-CI Docker image

Hi guys,

I want to install YardStick using Docker in OPNFV PoC enviorment. I try to pull 
yardstick-ci docker from hub, but I can not get the right answer. I run docker 
search yardstiack and can not find the yardstick-ci docker also.
So, where is the yardstick-ci docker? Or other docker to try the run-benchmarks?

Thanks & BRs
David


David Cui (崔先锋)
Lenovo Research CTL
Lenovo China
6 Shangdi West Road, Haidian, BJ


cui...@lenovo.com<mailto:cui...@lenovo.com>
Ph: +86 010 58869420
Mobile: +86 18910869420

[cid:699D5EF3-0109-4F3E-B406-AF4689634910]

http://www.lenovo.com<http://www.lenovo.com/>
Forums<http://forums.lenovo.com/> | Blogs<http://lenovoblogs.com/> | 
Twitter<http://twitter.com/lenovo>

Re: [opnfv-tech-discuss] [Dovetail] Dovetail/CC committee sync meeting in Toronto?

[Prakash Ramchandran]

Dave,

I have listed organizing the same in Tuesday slot.
https://etherpad.opnfv.org/p/collabrationofdovetail

We will assess as who are attending and you, me , Chris Price seem to be 
attending and lets see as we get more confirmation what can we accomplish there.




Those who need to still review the agenda please refer to link below and 
register for Hackfest. 
I am requesting Chris Donelay (christopher.don...@huawei.com) to help me manage 
the C&C requirements through his slides, if he is not able to make it and same 
with Tianhongbo as we await is confirmation.

https://www.regonline.com/OPNFVTorontoHackfest




Please feel free to update the ether pad link above to ensure if we need more 
time we can allocate Tuesday/Wednesday as per convenience of participating 
team/workgroup  members.

Thanks
Prakash

Prakash Ramchandran
 R&D 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





-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dave Neary
Sent: Monday, August 08, 2016 9:58 AM
To: opnfv-tech-discuss@lists.opnfv.org; opnfv-cc-commit...@lists.opnfv.org
Subject: [opnfv-tech-discuss] [Dovetail] Dovetail/CC committee sync meeting in 
Toronto?

Hi all,

A few weeks ago there was a discussion of whether the Dovetail and C&C 
Committee should sync in Toronto to collaborate on what we will deliver for 
Colorado.

Who will be there? Do we have critical mass? What would the agenda be 
("Collaboration on Colorado deliverables" seems like a good start to me). I 
would like to get something on the books this week if we do, since I will be on 
vacation next week.

Thanks,
Dave.
--
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338 
___
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] [Dovetail] Dovetail/CC committee sync meeting in Toronto?

[Prakash Ramchandran]

FYI: Looks like I missed the Hackfest Agenda link see below
https://wiki.opnfv.org/display/EVNT/Q3%272016+Hackfest

Parakash

-Original Message-
From: Prakash Ramchandran 
Sent: Monday, August 08, 2016 11:13 AM
To: 'Dave Neary'; opnfv-tech-discuss@lists.opnfv.org; 
opnfv-cc-commit...@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [Dovetail] Dovetail/CC committee sync meeting 
in Toronto?

Dave,

I have listed organizing the same in Tuesday slot.
https://etherpad.opnfv.org/p/collabrationofdovetail

We will assess as who are attending and you, me , Chris Price seem to be 
attending and lets see as we get more confirmation what can we accomplish there.




Those who need to still review the agenda please refer to link below and 
register for Hackfest. 
I am requesting Chris Donelay (christopher.don...@huawei.com) to help me manage 
the C&C requirements through his slides, if he is not able to make it and same 
with Tianhongbo as we await is confirmation.

https://www.regonline.com/OPNFVTorontoHackfest




Please feel free to update the ether pad link above to ensure if we need more 
time we can allocate Tuesday/Wednesday as per convenience of participating 
team/workgroup  members.

Thanks
Prakash

Prakash Ramchandran
 R&D 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





-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dave Neary
Sent: Monday, August 08, 2016 9:58 AM
To: opnfv-tech-discuss@lists.opnfv.org; opnfv-cc-commit...@lists.opnfv.org
Subject: [opnfv-tech-discuss] [Dovetail] Dovetail/CC committee sync meeting in 
Toronto?

Hi all,

A few weeks ago there was a discussion of whether the Dovetail and C&C 
Committee should sync in Toronto to collaborate on what we will deliver for 
Colorado.

Who will be there? Do we have critical mass? What would the agenda be 
("Collaboration on Colorado deliverables" seems like a good start to me). I 
would like to get something on the books this week if we do, since I will be on 
vacation next week.

Thanks,
Dave.
--
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338 
___
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] [OPNFV] [Mano WG] Support for OPNFV MANO releated projects - Meeting today 20.30 UTC (1.30 PM PDT)

[Prakash Ramchandran]

Hi all
Please join us in discussing MANO WG and review the Catalog Interface Demo today
irc: #opnfv-mano
GTM Link : https://global.gotomeeting.com/join/843517045
Meeting Wednesday(2nd and 4th weeks in month) 20.30 UTC (1.30 PM PDT)


Agenda (Continuing from last meeting and Monday meetings)

MANO WG discussions at Hackfest in Toronto - Establish Etherpad
https://wiki.opnfv.org/display/EVNT/Q3%272016+Hackfest

MANO WG items to discuss and Demo today...Catalog Interfaces

1. cross-project relations (existing OPNFV Models, Parser, VES, Copper, 
Domino), VNF on-boarding   - Will be in OPNFV Models meetings

2. Upstream NVFVO (Generic)  integration common minimum like Interface/APIs/Use 
cases to test and verify - OPEN-O, Open Baton, OSM etc.
Projects are getting approved - Refer Blog 
https://wiki.opnfv.org/pages/viewrecentblogposts.action?key=mano

3. Relation between VNFM (generic) - like Tacker, Juju etc. - We need inputs 
from Tacker and Juju teams in OPNFV as well upstream

4. Cross layer commonality for generic modules for compliance - This will be 
inputs from C&C / Dovetail team

5. Catalog bindings for  Local and Global serving of VNFs (and VSFs as some 
call) their on-boarding etc. (this we plan to address today)
OPNFV Eco system to provide Vendors the opportunity to build on top of generic 
capabilities
demonstrate next week MANO meeting some  Catalog and On-boarding possibilities

6. Templates which are both TOSA, YANG, Hybrid and standards as they  evolve 
will also be subject of MANO WG.

7. Installer issues for MNAO Project - Need co-ordination with Genesis and 
Installers  & Infra team in OPNFV(Fuel, Apex, Compass, JOID etc.)



Thanks
Prakash

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






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

Re: [opnfv-tech-discuss] [testperf][qtip] maximum line length

[Prakash Ramchandran]

Please use 80 or less and 79 is better. Maximum Line Length. Limit all lines to 
a maximum of 79 characters. -Thanks Prakash

Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@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 Yujun Zhang
Sent: Saturday, August 20, 2016 5:12 PM
To: TECH-DISCUSS OPNFV
Subject: [opnfv-tech-discuss] [testperf][qtip] maximum line length

Dear test project leaders,

What is the maximum line length do you apply in the PEP8 check in your projects?

Is there a opnfv coding rules for this?

The default value is 80 and recommended value is 80 to 100 according to
https://www.python.org/dev/peps/pep-0008/#maximum-line-lengtha

--
Yujun

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

[opnfv-tech-discuss] OPNFV-TECHNICAL] [MANO WG] Meeting Wednesday changed time from (Toronto) Hackfest 13.30 EST/ 17.30 UTC

[Prakash Ramchandran]

Hi all,

Please join us in discussing MANO WG meeting from  Hackfest tomorrow at  17.30 
UTC / 13.30 EST./ 10.30 AM PDT
You can also join on irc: #opnfv-mano

GTM Link : https://global.gotomeeting.com/join/843517045
Meeting Wednesday(2nd and 4th weeks in month)

The agenda for meeting is listed on link
https://wiki.opnfv.org/pages/editpage.action?pageId=6827111
or as of now the items to discuss  are

1. Welcome to MANO WG - Goals (Guide and Support for standards to adopt. for 
MANO Stack) and Roles (to ensure Service Providers and Vendors convergence on 
gaps to cover), any other list?

2. Agenda bashing and last meetings summary

3. MANO projects: Currently participating (OPNFV+Upsream)...OPEN-O 
(Opera),OpenBaton(Orchestra), Models, VES, Domino, JuJu, Tacker

4. What is the incentive for other MANO related (Projects+Upstream) : Doctor, 
OSM,ECOMP,...

5. Cross-project Co-ordination (goes with Models Meeting Monday even weeks 
monthly mornings/evenings) -Summary

6. VNF On-boarding (goes with Models Meeting Monday even weeks monthly 
mornings/evenings) -Summary

7. Catalog Interfaces - Demo

8. MANO Wiki Page updates based on inputs from participants.

Thanks
Prakash

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






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

Re: [opnfv-tech-discuss] [qtip] nominating Zhifeng Jiang as committer

[Prakash Ramchandran]

+1

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






From: Yujun Zhang [mailto:zhangyujun+...@gmail.com]
Sent: Sunday, August 28, 2016 7:25 PM
To: prabu.kuppusw...@spirent.com; Prakash Ramchandran; Cooper, Trevor; 
iben.rodrig...@vmsec.com
Cc: TECH-DISCUSS OPNFV
Subject: Re: [qtip] nominating Zhifeng Jiang as committer

A reminder for committers who haven't vote yet.

Please either reply to this thread or vote on gerrit [1]

Thank you for your supporting to qtip project.

[1] https://gerrit.opnfv.org/gerrit/#/c/19703/

On Mon, Aug 22, 2016 at 11:47 AM Yujun Zhang 
mailto:zhangyujun%2b...@gmail.com>> wrote:
Dear Qtip committers,

I'd like to nominate Zhifeng Jiang 
mailto:jiang.zhif...@zte.com.cn>> as new committer 
for QTIP project.

Zhifeng has been contributed a majority of code to QTIP since last season[1]. I 
believe she will help QTIP project to make a success in next release.

Please vote +2 in https://gerrit.opnfv.org/gerrit/#/c/19141/ if you agree.

[1] http://stackalytics.com/?project_type=opnfv-group&metric=commits&module=qtip

[Screen Shot 2016-08-22 at 11.45.15 AM.png]

--
Yujun
___
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

[Prakash Ramchandran]

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&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@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&T


-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

[opnfv-tech-discuss] [Parser][Domino] Cross-Project meeting 2016-Aug-29

[Prakash Ramchandran]

 Hi all,

Here is Summary of Parser meeting today

>From Domino meeting today following Gaps were identified for discussion in 
>Parser meeting
Gaps in tosca parser
  1.  Processing of substitution mapping statements to load VNF definitions
Gaps in heat translator
 2.  Heat Translator does not recognize node type VNF
Placement policy base type is translated into an affinity policy rule

Parser Meeting
@shangxdy to Everyone:  08:15 PM : I am working on substitution in tosca parser 
and it's almost finished.
Placement policy about affinity and anti affinity are already ok in parser, but 
it only support affinity in openstack community

.
@Shiva is working on Release C and will cherry pick or help Howard to Cherry 
pick  and submit the code by  Friday for Release C stable.
https://gerrit.opnfv.org/gerrit/#/c/16693/


@Prakash from Domino indicated that the gaps that are needed to be covered in 
translation are TOSCA to HOT.
Thus there needs to be discussion between Domino and Parser on what is relevant 
of the work @shangxdy has done to date.
If @shangxdy can point to code Domino team can review and see if this will 
suffice or needs additional work for release D for translations. It also plans 
to review the progress of Aria-ng and evaluate if the other options is an 
alternate, to conserve forking anything as long as the resource required is 
minimum.

Note: The Parser in OPNFV is focused on mapping YANG to  TOSCA.

@Howard indicated that Parser plans to peruse semantic validation as new 
feature  in Release D.
The other possibilities are gRPDC calls support as the Parser service can be 
used with REST or gRPC with multiple language binding support.
Domino will prefer gRPC binding as that helps batch processing. Although 
RESTful API is also an option.


>From shangxdy to Everyone here are the links for review:
substitution mappings patch in openstack:
https://review.openstack.org/#/c/345492/
placement policy patch in parser:
https://gerrit.opnfv.org/gerrit/#/c/16335/
https://gerrit.opnfv.org/gerrit/#/c/12699/

Please continue the debate through email and see how the Independent Domino 
Template Distribution and Template Parsing can  co-ordinate in Release D.

Thanks

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






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

[opnfv-tech-discuss] [MANO_WG] update reequest for VNF On-boarding

[Prakash Ramchandran]

Hi all,

Please find the updates to VNF On-boarding page for your inputs
https://wiki.opnfv.org/display/mano/VNF+Onboarding

Thanks

Prakash

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






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

[opnfv-tech-discuss] [opnfv-mano-wg] JIRA ticket tagiing for mano work

[Prakash Ramchandran]

Hi all,

Here is the summary of discussions at OPNFV Hackfest  at Toronto on MANO issues.

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111
refer to Agenda & Summary of meeting 8/24/2016 in the link above.

Would like to get feedback from PTLs  on MNAO activities being tagged in JIRA 
by respective projects to be able to track in  as labeled 'mano-' with tasks 
like vnf-onboarding etc.

If we could agree to use this tag, it will be helpful indicating participation 
and can be independent of release tags and help tracking mano work being done 
in projects

Tanks
Prakash

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






___
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

[Prakash Ramchandran]

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&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@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&T

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&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@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>
 [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&T


-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] FW: [Dovetail] Need concept of Capability and Bundles

[Prakash Ramchandran]

Chris,

Good to hear from you.
Sure use case based testing  looks good for Release C. But needs further review 
for a Multi-Release efforts. See my comments in-line.
Thanks
Prakash
Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@huawei.com>
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






From: Christopher Price [mailto:chrispric...@gmail.com]
Sent: Friday, September 02, 2016 11:09 AM
To: Prakash Ramchandran; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] FW: [Dovetail] Need concept of Capability and 
Bundles

Hi Prakash,

Apologies for not being able to attend the entire meeting today.
I’d like to raise concerns at this, some of the things below I find confusing.

Are you proposing that:

-  We use the term ”capability” instead of use case?  Why?
For Release C use case may suffice for Dovetail testing ... But Use Case refers 
to one capability based on a given Scenario we use to configure build and test. 
However a platform may need to support both IPv6 and L3 VPN or say SFC 
capability. Thus we may have to run three test  harness or suite (which I term 
bundle) to verify and validate all capability for a give release with that 
combination Platform and test suits.


-  We use the term “bundle” instead of test harness or test tool?  Why? 
Sure we can use test harness or suite. Tool is separate like test runner using 
those test harness for the said release testing for compliance etc.
This seems to increase confusion without a purpose I am able to fathom.  Why 
would we not use regular terms for these things?  I would strongly urge that we 
use normal testing terminology in DoveTail, maybe we can discuss it again next 
week as I am a little confused as to the motivation for this deviation.
Well we had similar confusion on Scenario and these are evolving and we need to 
think through, I am not claiming this is final, let's go through workflow and 
also review as how self test, third-party tests will be enabled based on 
dependencies and what would be better terms to use. It's an open discussion, 
the motivation is simple how do we help Dovetail test planning, along with 
tying efforts to provide test plan and results in a consistent way across 
releases and use cases for different builds and Deployment configurations.

I suggest we revisit the other test suite terminology discussion also.  The 
areas listed do not align with any of the agreements/proposals we made at the 
hackfest, or in the week since. We have yet to identify the use cases we want 
to address and we are otherwise busy creating names like “defrel” and “rcup” 
for suites and tools that do not exist and areas as of yet undefined.

Test suite terminology is open for debate and not closed yet. I did present  
the proposal and was interrupted and agreement/alignment  can be made after 
everyone evaluates and have sent this to opnfv-tech-list earlier and due to 
Release C work most of committers/contributors are still trying to close, so 
lets work through one more pass next week.

Maybe we could also spend a little time updating the IPv6 spec that has been 
untouched since August 12th pending some promised input.
I did that and send the updates by email on Aug 25th (refer my email to you and 
Dave Neary) as I could not update the files in gerrit.  The specs work sure 
will address, the  diagram and write up is on 
https://etherpad.opnfv.org/pipv6.(use Fontype Monospace to review the diagram)

Regards,
Chris

From:  on behalf of Prakash 
Ramchandran 
Date: Friday 2 September 2016 at 17:29
To: TECH-DISCUSS OPNFV 
Subject: [opnfv-tech-discuss] FW: [Dovetail] Need concept of Capability and 
Bundles


Hi all,

Here is the details of Dovetail tools building. Please review and we discuss 
this next week.
We need to add
1. Capability - Defines a specific use case to test based on one or more 
scenarios/APIs/Features eg. IPv6, L3VPN, SFC etc.
2. Bundle - We refer to test harness that needs to test  the Capability defined 
by one or more use cases as part of Capability

Now the Pass fail criterions can be defined by Dovetail and report sent to C&C 
based on its requirements for Compliances under Compliance Verification Program 
(CVP)
But the scoring by Capability and Matrix plus reporting  must be defined by C&C 
for Dovetail to implement as that is out of scope for Dovetail team.

Openstack

By Module(s)

OPNFV

By Use Case(s)

DefCore

Eg. Keystone, Glance, Nova, Neutron, Cinder, Swift

DefRel

Eg. say IPv6, L3VPN, SFC in Colorado

RefStack

HP, Rackspace CI/CD nodes (800-1000 nodes)

RefRel

LF, Community and Third party labs like NH

Tempest

Non-Admin API based by Modules

Dovetail



TCUP

Docker with micro-kernel versioned copy of tempest to run the RefStack software 
package locally on test clouds for certification

RCUP

Docker with mi

[opnfv-tech-discuss] [opnfv-mano-wg] Need Subscription list plus discussions for Sept 14 VNF onbaoarding & Mapping TOSCA service to NFV{VNFD+NSD}

[Prakash Ramchandran]

Hi all,
There  was a request from Margret that she cannot  get this as without joining 
opnfv-tech-list and that she and many in Polestar/S&P would prefer that we have 
a separate opnnfv-mano-wg subscription. My understanding is that this will be 
addressed by LF helpdesk. Until then I am copying the listed participants of 
MANO WG on wiki page and this is for September 14th meeting. We still have a 
week's time to get things moving.

If so can I request LF helpdesk to enable the opnfv-mano-wg subscription list.
 We do have #opnfv-mano channel that we use besides the scheduled


As part of MANO WG tasks would like to initiate debate on following items:

Like to verify with Models & Domino/parser if they would create a opnfv-mano-wg 
tags and create a Jira tickets for the  same?

1. VNF On boarding as listed by Polestar / S&P team by Bryan
? VNF Packaging - Compare and contrast  in how JuJu and Tacker  use OpenStack 
Glance or SDN-C (ODL/ONOS/OC}  {how do they align with IFA011?}

2. Mapping between TOSCA and NFV for using VNFD from oasis for VNFM to use 
(http://docs.oasis-open.org/tosca/tosca-nfv/v1.0/csd03/tosca-nfv-v1.0-csd03.pdf 
)
? Review how Service Descriptors from TOSCA match with NFV and if mapped 
correctly can  Template Distribution and Parsing manage this to deliver to 
orchestrators   like Heat or any controller that can support Pub/Sub via OPNFV 
project like Domino/Parser?

3. Would like to see OPEN-O(Opera) / OpenBaton (Orchestra) to add any Jira 
tickets that will help them on IFA007, use case or API aspects that would like 
to bring to opnfv-mano-wg

Once we know JIRA tickets are established will let Bryan lead us on 1 and will 
try bring some proposal for 2 working with Domino/Parser projects and PTLS of 
Opera and Orchestra as what they will need guidance from MANO WG to support 
them.

Thanks
Prakash


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






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

Re: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

[Prakash Ramchandran]

Ashish,

I hear your approach from Neutron managing this, so this assumes some topology 
for multisite. Based on Release notes of OpenStack  Mitaka... I see

Deprecate security_group_api configuration option. The current values are nova 
and neutron. In future the correct security_group_api option will be chosen 
based on the value of use_neutron which provides a more coherent user 
experience.

I heard that JuJu uses its own secgroup which is different from Neutron and 
thus JOID installer had no issues based on changes to secgroup in Mitaka

So prescribing some flow you have mentioned  for security group is interesting 
and  like to know what topology of multisite you are referring to,  to be able 
to absorb, what actually is being proposed here for tech team to understand. 
Suggest you refer this to security working group or may be bring to weekly tech 
discussions as what exactly is current state of security group in OPNFV 
multisite project and what you would like to change to make it better.

If this is out of context please ignore it.

Thanks
Prakash


Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@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 Ashish singh
Sent: Thursday, September 08, 2016 8:58 AM
To: opnfv-tech-discuss; caizhiyuan (A); Meimei; Sama, Malla Reddy; Zhipeng 
Huang; Ashish singh; Dimitri Mazmanov; joehuang; Ashish Singh7
Subject: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hi All,

I have drafted a basic approach for security group synching in release D and it 
is as follows.

- Get list of secgroups  with rules for a tenant from all the regions which do 
not have remote group references(currently, we ignore remote secgroup 
references as there can be lot nested dependencies).
- Traverse each region and do the following
- Get the list of secgroup which are present in all the regions except 
the current region, These are the secgroups which we need to sync in current 
region: say it GRP_TO_BE_SYNCED
- There can be case where the secgroup from GRP_TO_BE_SYNCED may have 
the same rules as the secgroup in current region(If not initially but which 
will obviously happen after a sync job).
- Traverse through the GRP_TO_BE_SYNCED and check if there are such 
secgroups(rules overlapping groups), if there, ignore it. After this filtering, 
the remaining secgroup will be the final list of secgroup which should be 
created for the current region.
- Create the secgroup with the final list of secgroups in the region.
- Repeat the process for all the tenant in batches.
The default security group is not syned, as I feel region specific default 
secgroup has to there in each region.

We must use neutron to perform all our operations as with neutron we have total 
control over it.


For creating a security group we need the following information

  --tenant-id TENANT_ID
The owner tenant ID.
  --description DESCRIPTION
Description of security group rule.
  --direction {ingress,egress}
Direction of traffic: ingress/egress.
  --ethertype ETHERTYPE
IPv4/IPv6
  --protocol PROTOCOL   Protocol of packet. Allowed values are [icmp, icmpv6,
tcp, udp] and integer representations [0-255]
  --port-range-min PORT_RANGE_MIN
Starting port range. For ICMP it is type.
  --port-range-max PORT_RANGE_MAX  Ending port range. For ICMP it is code.
  --remote-ip-prefix REMOTE_IP_PREFIX
CIDR to match on.
We have all these details with us available.


Let us take this forward, Please review/comment.

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

[opnfv-tech-discuss] Does any one have updates for OPNFV VNFs avilable for on-boarding and testing

[Prakash Ramchandran]

Hi all,

We in   OPNFV Dovetail  as well opnfv-mano-wg ,would like to revisit and see 
what VNFs are available mainly  through Open Source and may be  through 
Licensing by OPNFV members.

This will help compliance use case testing and   newer projects Opera, 
Orchestra, Domino as well multi-release Parser, Copper and Model to build their 
use case to test around what is available.

Please update with what you have or know to enable us helping define what 
descriptors / image formats are available for us to help zero on what we can 
use or leverage in Release D and later.

https://wiki.opnfv.org/display/functest/List+Of+VNFs


Thanks
Prakash



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






___
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-tsc] Does any one have updates for OPNFV VNFs avilable for on-boarding and testing

[Prakash Ramchandran]

Hi all,

About presentation by Giuseppe include me, will try join.

We did a demo on VNF Catalog using OpenStack Muarano  module at Hackfest and if 
needed can do that for test team to see how useful it can be next week on 
Tuesday  at Release Meeting  8AM PDT or we can work out some later 
Thursday/Friday slots. We used Devstack but any installer can add this to 
Horizon-plug-in  to see catalog in Mitaka release on-wards.


Thanks
Prakash

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






From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com]
Sent: Friday, September 09, 2016 8:55 AM
To: Carella, Giuseppe
Cc: Prakash Ramchandran; opnfv-tech-discuss; opnfv-...@lists.opnfv.org; Rohit 
Gupta; Souville, Bertrand; Christian Esteve Rothenberg
Subject: Re: [opnfv-tsc] Does any one have updates for OPNFV VNFs avilable for 
on-boarding and testing

Hi Guiseppe

do you know if it would be possible to make a 20 minutes presentation of this 
initiative during a future weekly test meeting?

The scope of the internship proposal published on OPNFV page is not as wide as 
the IEEE SDN initiative.
We just want to collect the Open Souce VNF candidates for onboarding/testing in 
Functest as we want to increase the vnf category for D release.

But I am pretty sure it make sense to contribute and cross our references to 
get a view as consistant as possible
We know that wiki lists are difficult to maintain, I am pretty sure there is 
place for synergies here...

/Morgan

NB for D release we still have in mind a possible integration of a case with 
OpenBaton/vWhatever/Test ...


Le 09/09/2016 à 15:49, Carella, Giuseppe a écrit :
Hi Morgan, all,

regarding VNF catalogues, I saw that you also placed on the wiki a link to the 
google spreadsheet [1] which was circulated by Christian on other lists. On 
this spreadsheet we are collecting all open source toolkits which could be used 
for SDN/NFV experimentation. This content will be soon migrated into a 
dedicated Wiki hosted by the IEEE SDN initiative. This is an activity currently 
led by us (Fraunhofer FOKUS/TU Berlin) and University of Campinas and supported 
by a large number of other entities. More info here [2].

Please let us know if you (or anybody else in this list) would like to actively 
contribute.

[1] 
https://docs.google.com/spreadsheets/d/1NHI4MZZWVDpxF_Rs7OOSTUa_aHL2ACUVA_Ov-YQs1DA/edit#gid=0
[2] http://www.sdn-os-toolkits.org/

Cheers,
Giuseppe

Join us at the IEEE 5G Week in November in Berlin (http://www.berlin5gweek.org/)

On 09 Sep 2016, at 08:34, 
morgan.richo...@orange.com<mailto:morgan.richo...@orange.com> wrote:

Hi,

it is a task identified in Functest for D
I created an internship proposal (see Title: Open Source VNF catalog 
inhttps://wiki.opnfv.org/display/functest/Functextnexttaks ) on this topic
Bertand got the green light to be a co-mentor so we will publish it soon (this 
morning)

One of of our goal for D is to have more VNFs following the rules we setup when 
we integrated cloudify/vIMS clearwater/Signaling test suite as shared during 
the summit.
We will try to learn VNF onboarding and MANO by doing
Yesterday during the Test working group meeting there was a presentation of 
Open Air Interface (see presentation here: 
https://wiki.opnfv.org/display/meetings/TestPerf), we hope we could integrate 
their vEPC in Functest for D (using Juju as VNFM as they already did the 
integration).

/Morgan


Le 09/09/2016 à 01:16, Prakash Ramchandran a écrit :
Hi all,

We in   OPNFV Dovetail  as well opnfv-mano-wg ,would like to revisit and see 
what VNFs are available mainly  through Open Source and may be  through 
Licensing by OPNFV members.

This will help compliance use case testing and   newer projects Opera, 
Orchestra, Domino as well multi-release Parser, Copper and Model to build their 
use case to test around what is available.

Please update with what you have or know to enable us helping define what 
descriptors / image formats are available for us to help zero on what we can 
use or leverage in Release D and later.

https://wiki.opnfv.org/display/functest/List+Of+VNFs


Thanks
Prakash



Prakash Ramchandran
 R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@huawei.com>
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA










___

opnfv-tsc mailing list

opnfv-...@lists.opnfv.org<mailto:opnfv-...@lists.opnfv.org>

https://lists.opnfv.org/mailman/listinfo/opnfv-tsc




--

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

[opnfv-tech-discuss] [opnfv-mano-wg] Agenda for Meeting Wednesday

[Prakash Ramchandran]

Please refer to link for meeting  Agenda on 14th this Wednesday

 https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111


Meeting Times: Every 2nd and 4th  Wednesday at 20:30pm UTC (1:30pm PDT)
IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

Thanks
Prakash

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






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

[opnfv-tech-discuss] [mnao-wg] subscription list available and Wednesday UTC 20.30 (PDT 13.30/EST 16.30) / Thursday BJT 4.30 AM

[Prakash Ramchandran]

Hi all,

Glad to inform you all the subscription link for opnfv  mano-wg is available at 
https://lists.opnfv.org/mailman/listinfo/

For this week's Pre-ODL summit meeting is to give inputs from mano-wg to 
co-ordinate with Polestar and also get project PTL inputs that has been 
requested by participating teams.

Please refer to  Meetings Agenda & 
Summary<https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111> on link 
https://wiki.opnfv.org/display/mano/OPNFV+MANO+Work+Group+Meetings.

You can either join the call on irc #opnfv-mano and/or the gotomeeting id in 
link above or send your feedback to PowerPoint slide on the man-wg-plan-v1.0.


Thanks
Prakash






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






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

[opnfv-tech-discuss] [opnfv-mano]: Reminder Wedneday 5th October meeting

[Prakash Ramchandran]

When: Occurs every 2 weeks on Wednesday effective 10/5/2016 until 10/19/2016

Meeting Times: October 1st and 3rd  Wednesday at 20:30pm UTC or Ad-hoc meeting 
as per Project requests (1:30pm PDT)


IRC#opnfv-mano

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

Meeting Agenda & 
Summary<https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111>

Agenda bashing

Follow up briefing for ODL summit

architecture for catalog integration

action follow ups.


Thanks

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






___
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-tsc] Announcing the 2016 TSC Chair election result

[Prakash Ramchandran]

Congratulations  Tapio and welcome to new role - Cheers Prakash

Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@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 HU, BIN
Sent: Monday, October 10, 2016 6:32 AM
To: Raymond Paik; opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [opnfv-tsc] Announcing the 2016 TSC Chair 
election result

Congratulations, Tapio.

Bin
From: opnfv-tsc-boun...@lists.opnfv.org 
[mailto:opnfv-tsc-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Sunday, October 09, 2016 11:06 PM
To: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
Subject: [opnfv-tsc] Announcing the 2016 TSC Chair election result

All,

I'm happy to officially announce that Tapio Tallgren (Nokia) has been elected 
as the new TSC Chair for OPNFV.  Tapio will run the TSC meeting starting on 
October 11th.  Congratulations, Tapio!

Thanks,

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

Re: [opnfv-tech-discuss] [mano-wg] [MANO] Discussion of how to include MANO stack components into scenarios

[Prakash Ramchandran]

Bryan,

Each Project is taking different approach and we will discuss this in next 
mano-wg meeting, about the Goals and their relevance.
The OPERA team PTL Yingjun Li had discussions on  the same last week and Jira 
tickets in OPERA reflect that.

So as part of mano-wg I will add this to discussions for best practices for us 
to work out.


The Jira tickets are created for the same as
https://jira.opnfv.org/browse/OPERA-1
https://jira.opnfv.org/browse/OPERA-2 - Specific to Compass

[cid:image001.png@01D2249A.7676B3E0]


Thanks
Prakash

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






From: mano-wg-boun...@lists.opnfv.org [mailto:mano-wg-boun...@lists.opnfv.org] 
On Behalf Of SULLIVAN, BRYAN L
Sent: Wednesday, October 12, 2016 9:20 AM
To: opnfv-tech-discuss@lists.opnfv.org; mano...@lists.opnfv.org
Subject: [mano-wg] [MANO] Discussion of how to include MANO stack components 
into scenarios

Hi all,

Cross-posting as not all may be on the MANO-WG list yet. Subscribe here: 
https://lists.opnfv.org/mailman/listinfo/mano-wg

As noted today on the IRC for the Infra call:
bryan_att> Bryan Sullivan 
#info<https://www.irccloud.com/#%21/ircs://irc.freenode.net:6697/%23info> We 
should have a discussion on the MANO WG re the need for scenarios for MANO 
testing. IMO as noted we should have no direct dependency upon any scenario. 
MANO components can be installed and uninstalled, replaced, etc dynamically as 
part of test scripts or post-install scripts.
 Bryan Sullivan 
#info<https://www.irccloud.com/#%21/ircs://irc.freenode.net:6697/%23info> As 
noted in the Models project we will be doing this for a variety of MANO stack 
components, both to install them (a reusable capability) and then to test them 
for specific features e.g. TOSCA blueprint compatibility, from onboarding, 
deployment, lifecycle management, etc.
8:49 AM 
#info<https://www.irccloud.com/#%21/ircs://irc.freenode.net:6697/%23info> So 
far we have developed support for Tacker and Cloudify, and OpenBaton, 
ARIA+JuJu, OSM, etc all can be addressed if we have time resources. These 
should all run on any scenario.
 
#info<https://www.irccloud.com/#%21/ircs://irc.freenode.net:6697/%23info> How 
to handle MANO can be discussed within MANO WG and MANO WG can come up with a 
common way of handling these
8:50 AM
 Bryan Sullivan 
#info<https://www.irccloud.com/#%21/ircs://irc.freenode.net:6697/%23info> and 
of course, very soon (I hope) OpenECOMP!

* I started a MANO WG wiki page for the discussion at Integrating MANO 
Components in 
OPNFV<https://wiki.opnfv.org/display/mano/Integrating+MANO+Components+in+OPNFV>.
 Some initial thoughts are shown there in a table that we can co-edit:
Goal

Assumption/Rationale/Exceptions

Comments

MANO stack component integration does not require new scenarios

VIM NBI provide a clean interface allowing MANO stack components to be added 
post-deploy, e.g. as we do today with vIMS, or as the Models project is doing 
for various VNFM/NFVO components. Exceptions might include MANO projects that 
depend (for some unclear/poor reason!) on a specific version/fork of a VIM.



Multiple MANO stack components can coexist in a single OPNFV deploy

MANO components, even those that offer the same/overlapping functions, can 
coexist as NBI consumers on OPNFV. Good use cases for this include interim 
phases toward a truly converged future, in which a SP may need to use various 
VNFMs that work with a particular VNF/service modeling toolset. In that case 
multiple MANO component deployment will be expected to work.



*
Thanks,
Bryan Sullivan | AT&T

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

[opnfv-tech-discuss] [mano-wg] [MANO] Meeting #9 this Wendnesday Oct 19, 20.30 UTC (13.30 PDT)

[Prakash Ramchandran]

FYI: OPNFV MANO WG Meeting Details

Meeting Times: Every 1st and 3rd  Wednesday at 20:30pm UTC or Ad-hoc meeting as 
per Project requests (1:30pm PDT)
IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

Agenda of meeting October 24, 2016  20.30 UTC /13.30 PDT Meeting #9
1.1. Inputs to TSC for Board "State of MANO architecture (Bimodal)"
a. a. Predictable - VNF 
Onboarding<https://wiki.opnfv.org/display/mano/VNF+Onboarding> (wiki) - 
Discussions
b.b. Exploratory - Integrating MANO components in 
OPNFV<https://wiki.opnfv.org/display/mano/Integrating+MANO+Components+in+OPNFV> 
and Hello world  Blue Prints efforts for VNF LCM.(Bryan)
c. c. Evolving Architecture - Top Down vs. Bottom 
up<https://wiki.opnfv.org/display/mano/MANO+Group+Home> -( Prakash)
d.d. MANO Project 
Guidance<https://wiki.opnfv.org/display/mano/MANO+Project+Guidance> (wiki)
2.2. Review Internal Process
a. a. Need change of time (with Daylight Saving 
changes and to help EU/China participation)
b.b. Need web page updates and review.
c. c. Stick to one irc channel allocated : 
#opnfv-mano and help needed for taking notes
Thanks
Prakash

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






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

Re: [opnfv-tech-discuss] [mano-wg] [MANO] Meeting #9 this Wendnesday Oct 19, 20.30 UTC (13.30 PDT)

[Prakash Ramchandran]

Hi mano wg team,

Appreciate the participation from every one today and will summarize the State 
of the MANO for TSC working with Bryan.
Here is the updated link with summary of today's deliberations.

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

One thing I could not cover was changing the time slot accommodate for 
participation from EU & Asia. Will be consulting everyone attending OpenStack 
and OPNFV meet at Barcelona and if needed send a pole to lock the timings 
starting new daylight time changes in November.

Thanks
Prakash

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






From: Prakash Ramchandran
Sent: Monday, October 17, 2016 12:45 AM
To: 'opnfv-m...@lists.opnfv.org'
Cc: opnfv-tech-discuss
Subject: [mano-wg] [MANO] Meeting #9 this Wendnesday Oct 19, 20.30 UTC (13.30 
PDT)

FYI: OPNFV MANO WG Meeting Details

Meeting Times: Every 1st and 3rd  Wednesday at 20:30pm UTC or Ad-hoc meeting as 
per Project requests (1:30pm PDT)
IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

Agenda of meeting October 24, 2016  20.30 UTC /13.30 PDT Meeting #9
1.1. Inputs to TSC for Board "State of MANO architecture (Bimodal)"
a. a. Predictable - VNF 
Onboarding<https://wiki.opnfv.org/display/mano/VNF+Onboarding> (wiki) - 
Discussions
b.b. Exploratory - Integrating MANO components in 
OPNFV<https://wiki.opnfv.org/display/mano/Integrating+MANO+Components+in+OPNFV> 
and Hello world  Blue Prints efforts for VNF LCM.(Bryan)
c. c. Evolving Architecture - Top Down vs. Bottom 
up<https://wiki.opnfv.org/display/mano/MANO+Group+Home> -( Prakash)
d.d. MANO Project 
Guidance<https://wiki.opnfv.org/display/mano/MANO+Project+Guidance> (wiki)
2.2. Review Internal Process
a. a. Need change of time (with Daylight Saving 
changes and to help EU/China participation)
b.b. Need web page updates and review.
c. c. Stick to one irc channel allocated : 
#opnfv-mano and help needed for taking notes
Thanks
Prakash

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






___
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 test vIMS using FUNCTEST-332

[Prakash Ramchandran]

Hi all,

We have Dovetail certification team offering some place for us to gather at 
OpenStack Barcelona on
Tuesday October 25, 1:00 - up to 3:00 PM Local time (We will figure that out 
before 1 PM on Tuesday at Barcelona)
The details of following email have added there under MANO Info at the bottom.

https://etherpad.opnfv.org/p/collabrationofdovetail

Those of who are attending please join us f2f to get some idea on testing MANO.
We can possibly spend 2 hours to update on this FUNCTEST-332

Please review MANO Info on the etherpad above.

Thanks
Prakash


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






From: Prakash Ramchandran
Sent: Friday, October 21, 2016 2:35 PM
To: jose.laus...@ericsson.com
Cc: Yingjun Li; 'giuseppe.care...@fokus.fraunhofer.de'; bs3...@att.com; 
dmcbr...@linuxfoundation.org
Subject: How to test vIMS using FUNCTEST-332

Jose,

First congratulations for having taken over the mantel of FUNCTEST. We like to 
help each other to improve our testing efficiency.

I would like to arrange a meeting in MANO working Group if you can throw some 
light on FUNCTEST-332. This appears an exciting way to on-board MANO projects 
both Opera and Orchestra.
The next meeting is scheduled for November 9, timing is either 7AM PST or 7PM 
PST will confirm after openstack summit. If you can go through the following 
and give both Yingjun Li and Giuseppe on how to bring on MANO stack over OPNFV 
using the Feature template, you have two possible candidates to make this 
happen.

For now I am going with OPERA and once have ORCHESTRA  review will like to 
bring them in too.


Assuming  Project Opera in OPNFV  wants to test vIMS with changes from Cloudify 
 Orchestrator to OPEN-O NFVO (from Opera Project), what would be the correct 
procedure to adapt?

Here is the old blueprint for Clearwater (CW)  vIMS

https://github.com/Orange-OpenSource/opnfv-cloudify-clearwater/blob/master/openstack-blueprint.yaml

Functest codes for vIMS using Cloudify Orchestrator

https://git.opnfv.org/cgit/functest/tree/testcases/vnf/vIMS

Can Opera team gitclone the above for Opera (nfvo orchestrator) and submit in 
Opera Repo or should it be in Functest Repo for test codes listed in the link?

How to test  vIMS
Opera needs a Scenario as  feature project for the Release D

Requires creation of specific file, tune configuration (as per 
https://jira.opnfv.org/browse/FUNCTEST-332)
 it would be interesting to consider a template allowing
§  declaration of the test (including constraints in the yaml + DB)
Do you have or can you prepare a template for vIMS  testing and give us so that 
we can fill  it for Opera nfvo based  CW vIMS testing?.
§  Our interest here is to specifically test all NFVO to VIM calls before 
November end  C3.0 and and NFVO to  VNFM (Juju) by Jan 15.
§
§  run test through Scenario.
§
§  collect result as per functest  docker runs from Jumpserver.
§
§  integrate results to Kibana dashboard - Sure will be cool if we can do by 
Release D deadlines
§
§
§  integrate into automatic reporting -  One more cool stuff
Feature projects shall inherit an abstract project class  - Do you have 
abstract class to use while we complete test plans say in 2-3 weeks?

Thanks
Prakash


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






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

Re: [opnfv-tech-discuss] RE : How to test vIMS using FUNCTEST-332 - Meet 1 PM Barceloan (local time) at D15 OPNFV Booth

[Prakash Ramchandran]

Hi all,

This to inform you all in MNAO WG , technical community as well Functest team.
We are meeting Face-to-face at OPNFV Booth D15 at  1 PM to go over the general 
way to test a VNF like vIMS using standard template.
https://jira.opnfv.org/browse/FUNCTEST-332

We will pull Bryan too if we can get him but looks most of us are in Market 
Place and find some tables to swarm together and get some simple basics works 
out, which we can expand as we approach implementation.


In case Dovetail folks have meeting place issue they too can barge into OPNFV 
booth and we can co-ordinate finding some seats in Marketplace for them.


Thanks
Prakash


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






From: Prakash Ramchandran
Sent: Monday, October 24, 2016 10:52 AM
To: 'morgan.richo...@orange.com'; Jose Lausuch
Cc: valentin boucher
Subject: RE: RE : How to test vIMS using FUNCTEST-332

Morgan,
Yes that will help and will try get all your inputs on FUNCTEST-332 for MANO 
integration we are looking for...Thanks Prakash

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






From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com]
Sent: Monday, October 24, 2016 4:18 AM
To: Jose Lausuch
Cc: Prakash Ramchandran; valentin boucher
Subject: RE : How to test vIMS using FUNCTEST-332

I could attend the beginning
But I planned to attend EUAG meeting planned at 2 PM

Morgan




Envoyé de mon Galaxy Note 4 d'Orange


 Message d'origine 
De : Jose Lausuch 
Date : 24/10/2016 10:05 (GMT+01:00)
À : RICHOMME Morgan IMT/OLN 
Objet : FW: How to test vIMS using FUNCTEST-332
Will you be able to attend this? I will be still on my way to Barcelona ☺


From: Prakash Ramchandran [mailto:prakash.ramchand...@huawei.com]
Sent: Saturday, October 22, 2016 1:06 AM
To: Prakash Ramchandran; Jose Lausuch
Cc: Yingjun Li; giuseppe.care...@fokus.fraunhofer.de; bs3...@att.com; 
dmcbr...@linuxfoundation.org; opnfv-tech-discuss@lists.opnfv.org; 
mano...@lists.opnfv.org
Subject: RE: How to test vIMS using FUNCTEST-332

Hi all,

We have Dovetail certification team offering some place for us to gather at 
OpenStack Barcelona on
Tuesday October 25, 1:00 - up to 3:00 PM Local time (We will figure that out 
before 1 PM on Tuesday at Barcelona)
The details of following email have added there under MANO Info at the bottom.

https://etherpad.opnfv.org/p/collabrationofdovetail

Those of who are attending please join us f2f to get some idea on testing MANO.
We can possibly spend 2 hours to update on this FUNCTEST-332

Please review MANO Info on the etherpad above.

Thanks
Prakash


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






From: Prakash Ramchandran
Sent: Friday, October 21, 2016 2:35 PM
To: jose.laus...@ericsson.com<mailto:jose.laus...@ericsson.com>
Cc: Yingjun Li; 'giuseppe.care...@fokus.fraunhofer.de'; 
bs3...@att.com<mailto:bs3...@att.com>; 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>
Subject: How to test vIMS using FUNCTEST-332

Jose,

First congratulations for having taken over the mantel of FUNCTEST. We like to 
help each other to improve our testing efficiency.

I would like to arrange a meeting in MANO working Group if you can throw some 
light on FUNCTEST-332. This appears an exciting way to on-board MANO projects 
both Opera and Orchestra.
The next meeting is scheduled for November 9, timing is either 7AM PST or 7PM 
PST will confirm after openstack summit. If you can go through the following 
and give both Yingjun Li and Giuseppe on how to bring on MANO stack over OPNFV 
using the Feature template, you have two possible candidates to make this 
happen.

For now I am going with OPERA and once have ORCHESTRA  review will like to 
bring them in too.


Assuming  Project Opera in OPNFV  wants to test vIMS with changes from Cloudify 
 Orchestrator to OPEN-O NFVO (from Opera Project), what would be the correct 
procedure to adapt?

Here is the old blueprint for Clearwater (CW)  vIMS

https://github.com/Orange-OpenSource/opnfv-cloudify-clearwater/blob/master/openstack-blueprint.yaml

Functest codes for vIMS using Cloudify Orchestrator

https://git.opnfv.org/cgit/functest/tree/testcases/vnf/vIMS

Can Opera team gitclone the above for Opera (nfvo orchestrator) and submit in 
Opera Repo or should it be in Functest Repo for test codes listed in the link?

How to test  vIMS
Opera needs a

Re: [opnfv-tech-discuss] Nonimation of the bottlenecks committer

[Prakash Ramchandran]

+1 (if it counts)  I had attended few of Bottleneck meetings and like the open 
approach of Yu Yang - Thanks Prakash

Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@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 Tianhongbo
Sent: Wednesday, October 12, 2016 7:07 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Nonimation of the bottlenecks committer

Hi:

I would like to nominate Yang Yu as committer to Bottlenecks.
He has been one of the most active Bottlenecks contributors during Colorado 
development phase. Apart from being the top contributor to Bottlenecks during 
September, he did lots of contributions to add a new Test suite(POSCA), 
organize the Bottlenecks weekly meeting ,help maintain WIKI and also improve 
Bottlenecks documentations and Flake8 scanning.


please reply to this mail with your vote (-1, 0, +1).


Achievements/Conbributions include:
https://gerrit.opnfv.org/gerrit/#/q/owner:Gabriel.yuyang%2540huawei.com+project:bottlenecks

1. Adding POSCA test suite in Bottlenecks

a) POSCA testing framework

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-92

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/20837/

b) Adding Factor Test case System_Bandwidth

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-94

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/21351/

c) Adding Factor Test case CPU_Burden

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-95

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/21355/

d) Adding Factor Test case TX PKT Size

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-99

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/21563/

e) Adding Factor Test case RX_PKT_Size

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-97

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/21401/

f)  Adding Factor Test case TX_Cache_Size

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-98

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/21561/

g) Adding Factor Test case RX_Cache_Size

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-96

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/21379/

2. Refactoring Bottlenecks documentations

a) Correcting table format error in userguide docs

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-88

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/19043/

b) Adding framework illustration in Bottlenecks docs

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-88

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/19131/

c) Adding Release Notes Doc Framework

 i.  
https://jira.opnfv.org/browse/BOTTLENECK-88

   ii.  
https://gerrit.opnfv.org/gerrit/#/c/22309/

3. Flake8 fix for Bottlenecks project

a) https://jira.opnfv.org/browse/BOTTLENECK-101

b) https://gerrit.opnfv.org/gerrit/#/c/22593/

4. Organizing the Bottlenecks weekly meeting and maintaining WIKI

a) Meeting minutes and meterial

 i.  
https://wiki.opnfv.org/pages/viewpage.action?pageId=6828202

   ii.  
https://wiki.opnfv.org/download/attachments/2926187/Proposals%20in%20Bottlenecks.pdf?version=7&modificationDate=1472176386000&api=v2

b) Release Planning WIKI pages

5. Design and sharing the POSCA test suite

a) POSCA test suite in Bottlenecks D release

 i.  
https://wiki.opnfv.org/download/attachments/2926187/POSCA%20in%20Bottlenecks%20D%20Release.pptx?version=1&modificationDate=1475983276813&api=v2

b) Sharing POSCA in Bottlenecks weekly meeting

 i.  
https://wiki.opnfv.org/download/attachments/2926187/2016-09-22%20Sharing%20POSCA%20in%20Bottlenecks.mp4?version=1&modificationDate=1475993554550&api=v2

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

[opnfv-tech-discuss] [mano-wg] [MANO] Meeting #10 this Wendnesday Nov 2, 15.00 UTC (7.00 PDT)

[Prakash Ramchandran]

FYI: OPNFV MANO WG Meeting Details

Meeting Times: Weekly 7 AM PDT (15:00 UTC) this week and 7 AM PST (14:00 UTC) 
after daylight changes next week

 IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

Agenda of meeting November 2, 2016  14.00 UTC /7.00 PDT Meeting #10

1, Briefing on "State of MANO architecture" and feedback listed below.

MANO TSC-Board report and feedback
State of MANO in 
OPNFV-tsc-borad-october-28-2016.pdf<https://wiki.opnfv.org/download/attachments/6827111/State%20of%20MANO%20in%20OPNFV-tsc-borad-october-28-2016.pdf?version=1&modificationDate=1478009353911&api=v2>

2. Cross-Project Co-ordination for Danube and Assess the participation of MANO  
activities for UNHV Plugfest Dec 5-8

3. Functest through common test plans for MANO VNFM and NFVO  (Opera, 
Orchestra, and participating Projects)

4. Any topics of interests to upstream and Projects in OPNFV.
Thanks
Prakash


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






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

Re: [opnfv-tech-discuss] [netready] Gluon integration in OPNFV

[Prakash Ramchandran]

George,

Your points are relevant. My only question is can we not reuse any of the 
existing Apex scenarios for the Danube listed under APEX in the following?
https://wiki.opnfv.org/display/SWREL/Danube+Scenario+Status

If there is any one that fits closest can we not adapt them like?
os-odl_l2-sfc-ha Apex @Brady Johnson
os-odl_l3-ovs-noha Apex @Thomas F Herbert

check with Brady Johnson if they really have an HA for SFC and Thomas what it 
means to be noha?
Since  Gluon uses odl we can use ether one, with ha and noha as well l2/l3 
options.


Once we know what is difference between the two options and what changes we 
need to make to work with both l2 and l3 we can plan for if required for new 
scenario os-odl-gluon-noha


Meanwhile we work with the two scenarios identified for seeing what it takes to 
adapt them, you go ahead and add the scenario os-odl-gluon-noha Apex@Georg Kunz
to wiki page https://wiki.opnfv.org/display/SWREL/Danube+Scenario+Status

Hope this helps David McBride and CI/CD and Infrastructure team to see how they 
can help us.

Have a good weekend as we may be in for shock nextweek of  AmeXit (following 
BreXit)!!!

Thanks
Prakash 


Prakash Ramchandran
 R&D 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





-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Georg Kunz
Sent: Friday, November 04, 2016 7:24 AM
To: HU, BIN (bh5...@att.com); Nikolas Hermanns; Tim Irnich; 
gergely.csat...@nokia.com; thomas.hamble...@nokia.com; kamal.huss...@nokia.com; 
iawe...@cisco.com; Jeff Collins II
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [netready] Gluon integration in OPNFV

Hi guys,

As I mentioned during the last meeting, I am working towards installer support 
for Gluon in OPNFV. I believe it is highly beneficial for Gluon if we can make 
use of the CI and testing framework that OPNFV provides - in addition to the 
community building, of course. In this context, I have been in contact with 
Feng Pan from the Apex team.

The first step towards an OPNFV integration is to define a new deployment 
scenario for Gluon. This involves a couple of aspects I'd like to get your 
input on:

* SDN controller: There are currently two major SDN controllers in OPNFV: ODL 
and ONOS. Based on our experience and competence, I propose to start with ODL.
* Network Service: This one is simple as we only have the L3VPN service at the 
moment.
* Layer: The current scenarios distinguish between l2 and l3. For Gluon, I'd 
like to refrain from prematurely restricting the deployed network service. 
Hence, I propose to leave out any reference to l2 or l3.
* Installer: As I mentioned, the Apex team voiced interest in supporting this 
activity.
* High-availability: We have not looked into high-availability aspects of Gluon 
yet. Hence, I propose to define a noha scenario first.

In summary, given the OPNFV scenario naming conventions, a first Gluon scenario 
would be called os-odl-gluon-noha.

Let know what you think.

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 mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [mano-wg] [MANO] Meeting #11 this Wendnesday Nov 9, 14.00 UTC (7.00 PST)

[Prakash Ramchandran]

FYI: OPNFV MANO WG Meeting Details

Meeting Times: Weekly Wednesday 7 AM PST (14:00 UTC)

 IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045
Want to get some some formal word  document so that we can use it for Release D 
with content defined herein
Agenda of meeting November 9, 2016  14.00 UTC /7.00 PDT Meeting #11

  1.  What should we document for MANO best practice for OPEN-O and OpenBaton 
integration through Opera and Orchestra.
 *   What use case to start with - - Should vIMS be the first use case?
 *   VNF On-Boarding - TOSCA Node Template  NFV (VNFD, VLD, 
VNNFGD, PNFD)
 *   Service Invocation and Deletion - TOSCA Service  template = NFV NSD, 
How do we handle SO & RO for this?
 *   API versioning - which API?
  2.  At what point should upstream integration project  consider OPNFV Models 
topology design and templates to choose  and use.
  3.  What should be test strategy (refer  item 3 Nov 2 meeting)
  4.  Where is the test plan and how will the projects share the testing codes?
  5.  How would the results of collaboration through MANO WG reflect in 
D-release of OPNFV.
  6.  What is reasonable deliverable expected from UNH Plug-fest for 
cross-project co-ordination?

Edit if you want you want to add agenda items to

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111


Thanks
Prakash


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






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

[opnfv-tech-discuss] [mano-wg] [MANO] Meeting #11 agenda plus summary updates

[Prakash Ramchandran]

Here is the summary of MANO meeting today Nov 9 and some common approach 
between Opera and Orchestra for on boarding, service invocation and  API 
versions / testing  - as summarized below.

I will be updating links etc provided by Giuseppe and Yingjun Li for same.
Any suggestions for next week call besides the ones agreed today, please feel 
free reply back for me or Bryan to include in next mano-wg or Models calls.

Subscribe for mano-wg if you want to keep upto date on mano-wg summary : 
https://lists.opnfv.org/mailman/listinfo/

Agenda of meeting November 9, 2016  14.00 UTC /7.00 PDT Meeting #11 and summary 
updates

  1.  What should we document for MANO best practice for OPEN-O and OpenBaton 
integration through Opera and Orchestra.
 *   What use case to start with - - Should vIMS be the first use case?
vIMS is agreed use case to document as first one for MANO integration
Besides Clearwater vIMS Blueprint in OPNFV,  Arthur from Canonical suggested 
using OpenIMS and JuJu can handle both.
 *   VNF On-Boarding - TOSCA Node Template  NFV (VNFD, VLD, 
VNNFGD, PNFD) - Onboarding
OpenBaton / Orchestra indicated that they like to see VNF Package to include 
VNFD along with image name and script to instantiate the VNF. So did Yingjun Li 
PTL Opera chimed and thus there is agreement on this from both projects. The 
issue of formats to use include CSAR & JSON and run times both Python and Java 
are being considered. Thus there will be attempt by both teams to define them 
along with VNFM's they plan to use like JujU and Tacker.

The VNF package, and data model / representations for NSD and VNFD, and how/why 
those vary across MANO projects

b1.   OpenBaton: JSON for 
VNFD, 
NSD; TOSCA for 
NSD
b2.   Open-O: ...Needs input from Opera team
 (OPNE-O : 
https://wiki.open-o.org/view/OPEN-O_Sun_Release_Notes#Release_Overview )

 *   Service Invocation and Deletion - TOSCA Service  template = NFV NSD, 
How do we handle SO & RO for this?
This will follow NFVO flow to VNFM asking to allocate resource and if it does 
not that capability then NFVO will reroute the request to VIM. On success of 
Resource reservation (Quota) etc. the NFVO will ask VNFM to instantiate the 
service for the deployment completion as first target. Life cycle management 
will follow that based on agreed hooks to be defined as common between the 
Opera , Orchestra, Juju and Tacker teams. A proposal will be reviewed next week.
 *   API versioning - which API?
The API versioning is of abstractions or wrappers that is being proposed by 
OpenBaton and will be reviewed by other MANO participants to agree on a common 
wrapper approach for IFA 5, 6,7 and OPNFV VIM and VNFM drivers from NFVO.
  1.  At what point should upstream integration project  consider OPNFV Models 
topology design and templates to choose  and use. - This will be discussed at 
next Models call with Bryan Sullivan.
  2.  What should be test strategy (refer  item 3 Nov 2 meeting) - Await 
FUNCTEST-237 response from Morgan and Action for MANO teams to create new 
FUNCTEST JIRA ticket based on vIMS use case.
  3.  Where is the test plan and how will the projects share the testing codes? 
- Proposal to be discussed next week with inputs for Giuseppe of Orchestra 
(OpenBaton team).
  4.  How would the results of collaboration through MANO WG reflect in 
D-release of OPNFV. - A template to be reviewed to see what should the best 
practices to include in the D-release based on MANO WG participation by Opera, 
Orchestra and associated VNFM.
  5.  What is reasonable deliverable expected from UNH Plug-fest for 
cross-project co-ordination? - The Open-O team from China Mobile plans to demo 
OPEN-O and OpenBaton team indicated that they may not be bale to make it to UNH 
Plug-fest but plan to Demo their efforts in ETSI Plugtest in February.
Attendees: irc+GTM
aimeeu,B_Smith,bryan_att,ChrisPriceAB,collabot`,dmcbride,ljlamers, rprakash, 
yingjun Li, Arthur Tyloc, Narinder Gupta
Thanks
Prakash

[logo_huawei] R&D 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






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

[opnfv-tech-discuss] [mano-wg] [MANO] Meeting #12 agenda - Nov 16th Wednesday 14 UTC

[Prakash Ramchandran]

FYI: OPNFV MANO WG Meeting Details

Meeting Times: November 16th, Regular Weekly Wednesday 7 AM PST (14:00 UTC)

 IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join mano-wg  meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111 (see for updates to 
following)
Agenda of meeting November 16, 2016  14.00 UTC /7.00 PDT Meeting #12

  1.  Summary of last meeting and Agenda bashing
  2.  Compare Clearwater vIMS vs. OpenIMS- (Artur Tyloc - details on OpenIMS 
and JuJu orchestration for the same)
  3.  Review  or propose TOSCA template for vIMS and OpenIMS for On-Boarding 
and compare with ( NFV (VNFD, VLD, VNNFGD, PNFD) - (Yingjun Li)
  4.  What VNF  package should  contain besides TOSCA descriptor ( for CW vIMS 
/ OpenIMS) - OPEN-O & OpenBaton for their NFVO & VNFM choice they make 
(Opera/Orchestra teams)
  5.  Service Invocation and Termination API versioning and flows for VNF 
(vIMS/OpenIMS) use case.(General Discussions)
  6.  Inputs from OpenBaton for IFA5,6,7 Interface functional calls. (Giuseppe)
  7.  Progress on Models  based on Peter Lees inputs using Django & YANG. How 
will that apply to vIMS/OpenMANO? (Bryan)
  8.  Need FUNCTEST-237 replaced by one that Opera/Orchestra will commonly use 
- YingjunLi/Giuseppe)
  9.  Where is the test plan and how will the projects share the testing codes? 
- Proposal to be discussed next week with inputs for Giuseppe of Orchestra 
(OpenBaton team).
  10. How would the results of collaboration through MANO WG reflect in 
D-release of OPNFV. - A template to be reviewed to see what should the best 
practices to include in the D-release based on MANO WG participation by Opera, 
Orchestra and associated VNFM.
  11. UNH Plug-fest for cross-project co-ordination? - Update from OPEN-O/Opera 
team
  12. Discussions on what would be inputs from MANO_WG to OPNFV D & E Release. 
Wiki Page to update after discussions in WG.

Subscribe for mano-wg if you want to keep up to date on mano-wg summary : 
https://lists.opnfv.org/mailman/listinfo/

Thanks
Prakash


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






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

[opnfv-tech-discuss] [mano-wg] [MANO] Meeting #13 todays Summary and next Meeting #14 - Nov 30th Wednesday 15 UTC

[Prakash Ramchandran]

s)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111 (see for updates to 
meeting  agenda)
Thanks
Prakash



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






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

Re: [opnfv-tech-discuss] [mano-wg] [MANO] Meeting #13 todays Summary and next Meeting #14 - Nov 30th Wednesday 15 UTC

[Prakash Ramchandran]

Hi all

Please review the following suggestion for VNFM, NFVO registration to Keystone 
with Glance Image Catalog displaying artifacts and an OSS Monitor abstraction 
to verify  that the instances of these two MNO components are available to take 
 functionla calls to manage VNF life cycle.

5 Use case of vIMS

We can assume the Clearwater vIMS as an example to use here.

5.1Use cases with focus on management of OPNFV-MANO functions

   This clause should be used for use cases whose 
focus is more on the NFV-MANO functions.

5.1.1   On boarding of OPNFV-MANO entity(NFVO/VNFM) artefact
5.1.1.1Introduction and goal
As any network function entity in a real network deployment, needs to be 
recognized by other  collaborating components. In the OPNFV MANO being built 
ground up, the Keystone module in OPNFV VIM requires that NFVO/VNFM are 
registered as endpoints providing respective services. Before the service can 
be registered the artefacts or NFVO or VNFM package must be on boarded to 
Glance catalog.
5.1.1.2Actors and roles
Table 5.1.1.2-1 describes the use case actors and roles.

Table 5.1.1.2-1: On-boarding & Registering of OPNFV-MANO function entity actors 
and roles

#


Role


Description


1


OPNFV-MANO function entity.


The entity that is being on-boarded to Glance or Registered with Keystone as a 
service.


2


MANO entity VM or Container.




The entity that is on-boarded and Registered.



Editor's Note: The "MANO entity VM or Container" is used for the purpose to 
describe the use case and help understand the functionality that is described 
herein. The use case does not make any assumption what entity can play such a 
role, and if any is FFS(**).


**FFSFreedom for Some


5.1.1.3Pre-conditions
Table 5.1.1.3-1 describes the use case pre-conditions.

Table 5.1.1.3-1: On-boarding  & Registration of OPNFV-MANO function entity O&R 
pre-conditions

#


Pre-condition


Additional description


1


The OPNFV-MANO function entity is onboarded.


Enabled (False)


2


The OPNFV-MANO function entity is running


Running (False)


5.1.1.4Post-conditions
Table 5.1.1.4-1 describes the use case post-conditions.

Table 5.1.1.4-1: On-boarding & Registration of OPNFV-MANO function  O&R entity 
post-conditions

#


Post-condition


Additional description


1


The OPNFV-MANO function entity is onboarded.


Enabled (True)


2


The OPNFV-MANO function entity is running


Running (True)



5.1.1.5Flow description
Table 5.1.1.5-1 describes the use case flow.

Table 5.1.1.5-1: On-boarding and Registration of OPNFV-MANO function entity 
description

#


Actor/Role


Action/Description


Begins when


MANO entity is on-boarded or registered


The MANO Glance Catalogue/ Keystone Endpoint  determines that a specific 
OPNFV-MANO function entity needs to be on-boarded or registered. The source of 
the determination can be an automatic action based on a specific configuration 
or call from an explicit request, e.g., from the network operator.


Step 1


MANO Oboard -> OPNFV-NFVO or

OPNFV-VNFM functionentity


The OPNFV-MANO requests the NFVO or VNFM function entity to set-up the entry in 
Catalogue to notify about availability of the entity itself (see note).


Step 2


MANO registered ->

OPNFV-NFVO or

OPNFV-VNFM functionentity


The NFV-MANO function entity informs about the successful setup of the entity 
in Keystone as an endpoint (see note).


Step 3


OSS Monitor (external to OPNFV like OPEN-O/OpenBaton)


The OSS Monitor may query OPNFV-MANO function entity as a monitored entity. The 
OSS Monitor also starts monitoring the OPNFV-MANO function entity (e.g., by 
sending health check requests at regular intervals).


Step 4


NFV-MANO functionentity -> OSS Monitor

or

OSS Monitor


Whenever a failure occurs and is detected by the OSS Monitor the OPNFV-MANO  
function entity failure (see note), or

Whenever the OSS Monitor detects the OPNFV-MANO function entity is 
unresponsive, the OSS Monitor determines itself that the OPNFV-MANO function 
entity to be faulty.


Ends when


OSS Monitor


The OSS Monitor requests the OPNFV-MANO function entity to stop the failure 
monitoring mechanism (see note),

The OSS Monitor stops monitoring the NFV-MANO function entity.


NOTE:   This behaviour applies only to the case of enabling the 
notification of failures detected by the OPNFV-MANO function entity itself.


To be conti



Thanks
Prakash

Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@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: Wednesday, November 30, 2016 9:06 AM
To: Prakash Ramchandran; mano...@lists.opnfv.org
Cc: opnfv-tech-discuss@lis

Re: [opnfv-tech-discuss] [OPNFV] [FUNCTEST] [Danube] VNF OnBoarding

[Prakash Ramchandran]

Morgan,

Went through the code for VNF On boarding still trying to understand the logic.
Point 1 that you are on boarding  the VNF with or without Orchestrator (why not 
call it nfvo and being opera or orchestra) similarly why juju_vnf and not vnfm 
as Juju or Tacker or OpenBaton vnfm, looks to abstractions are needed rather 
than specifics which should be included as internal names.

Nevertheless let me better understand before I add any comments to code, so I 
did not put a+1 yet to it.

We have 7 AM PST TSC and 8 AM PST Release planning meeting.
The Functest meeting appears to be mid night for me but will follow up tomorrow 
based on the minutes of the meeting and bring that to MANO WG call on Wednesday 
7 AM PST to collect all the inputs to respond back for both D-Release priority 
plus the code review to close the VNF On-boarding and testing.

Another question, Is there any relation between this and OAI ?  May be you can 
help me on that.

Thanks
Prakash


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






From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com]
Sent: Monday, January 09, 2017 8:54 AM
To: Carella, Giuseppe
Cc: Yingjun Li; zhao.huab...@zte.com.cn; meng.zhaoxi...@zte.com.cn; 
by...@etri.re.kr; Narinder Gupta; Yunxia Chen; Olga Havel; Tomasini, Lorenzo; 
Pauls, Michael; rohit.gu...@eurecom.fr; navid.nika...@eurecom.fr; 
wlu...@bupt.edu.cn; cs15mtech01...@iith.ac.in; cs15mtech01...@iith.ac.in; 
Prakash Ramchandran; SULLIVAN, BRYAN L; Jose Lausuch; David McBride; 
opnfv-tech-discuss@lists.opnfv.org; valentin boucher
Subject: Re: [OPNFV] [FUNCTEST] [Danube] VNF OnBoarding

Hi Guiseppe

I think I got your point
As you mentioned we should differentiate 2 things
- VNF onboarding: testing the capability to deploy a VNF with or without an 
orchestrator and test the VNF
- Mano stack validation see as a feature available in scenario(s)

the proposal was related to the first topic only
the idea of the abstraction is to try to harmonize the way we deploy the VNFs, 
it is also a guide for VNF and/or MANO providers for the intergation
and it shall encourage VNF providers to integrate the test suite as part as the 
VNF to ease an integration in OPNFV scenario(s)
for Danube we can see that we should have several orchestrators deploying the 
vIMS

for the second point, I agree with you, it could be considered as a "feature" 
assuming that a scenario includes an orchestrator
then we can define a specific constraint and run any test suites to the MANO 
stacks related to the scenario as any feature
as a feature, functest can triggers the test then the MANO stack testing will 
be automatically integrated in the reporting page and used to calculate the 
Functest scenario scoring 
(http://testresults.opnfv.org/reporting/functest/release/master/index-status-fuel.html)

Let's continue discussing it tomorrow

/Morgan

Le 09/01/2017 à 12:23, Carella, Giuseppe a écrit :
Hi Morgan,

during the last days we have done a review (not fully complete yet) about the 
approach you proposed for integrating our test scenario with functest, and we 
internally agreed that this approach should be enough for us to test the vIMS 
scenario running on Orchestra. We already have some code which we plan to 
commit during this week, however it would be good to discuss with you all about 
some doubts we are having during tomorrow’s call.

In the wiki page you sent it is mentioned also that "Functest does not test any 
MANO stack”. In general, in Orchestra we would be interested in having some 
integration scenarios which could be useful for covering test cases for MANO 
frameworks. We have already an upstream project [1] doing something similar, 
and our initial plan was to integrate this project within OPNFV functest, as 
already mentioned earlier to Jose. With the approach taken in your abstraction 
I see that this integration won’t be really easily doable. Main reason is that 
our integration-test framework already splits the test cases in different 
steps, while you cover at the moment mainly two steps (deploy VNF and test VNF)
* registration of a VIM instance
* on boarding a NSD
* deployment a NSR using the on boarded NSD from previous step
* testing that the NS is really deployed (optional in case of negative testing)
* deletion of the NSR
* deletion of the NSD
* unregistration of the VIM

With our framework, it is possible to define a scenario (and the steps which 
needs to be executed) directly using a configuration file. An example of a 
scenario can be found here [2], deploying an iperf server and client network 
service and testing that the client connected effectively with the server 
(therefore testing that dependencies were correctly configured between VNFs).

Although I see that your approach can 

[opnfv-tech-discuss] [mano-wg] [MANO] Meeting #16 Recap 2015+ D-Release Priority including Scenario , Installers Features and Tetsing vIMS

[Prakash Ramchandran]

Please join us tomorrow for MANO WG setting D-Release Proirities for 
Integration with OPNFV VIM and test vIMS as priority.

Agenda:

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111



Meeting Times: Every Even Wednesday at 15.00 UTC (7.00 am PST)  as per Project 
requests

 IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

Thanks


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

___
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] VNF on boarding: Q&A Functest versus orchestrator projects

[Prakash Ramchandran]

Morgan,
tried on orange bridge via US number and asks pin code that does not work. May 
be we reschedule the meeting for tomorrow after Tech meeting of Bin Hu? - 
Thanks Prakash

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






From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com]
Sent: Wednesday, January 11, 2017 9:07 AM
To: Margaret Chiosi; Rautakumpu, Mika (Nokia - FI/Espoo)
Cc: SULLIVAN, BRYAN L; Yunxia Chen; Yang Xu (Yang, Fixed Network); 
zhao.huab...@zte.com.cn; meng.zhaoxi...@zte.com.cn; by...@etri.re.kr; 
navid.nika...@eurecom.fr; wlu...@bupt.edu.cn; cs15mtech01...@iith.ac.in; 
cs15mtech01...@iith.ac.in; opnfv-tech-discuss@lists.opnfv.org; Prakash 
Ramchandran; giuseppe.care...@fokus.fraunhofer.de; 
narinder.gu...@canonical.com; bouch...@live.fr; Olga Havel; 
dmcbr...@linuxfoundation.org; jose.laus...@ericsson.com; 
michael.pa...@tu-berlin.de; lorenzo.tomas...@fokus.fraunhofer.de; 
huang.leib...@zte.com.cn; Thajudheen Rajak
Subject: Re: [opnfv-tech-discuss] [OPNFV] VNF on boarding: Q&A Functest versus 
orchestrator projects

I do appologize for the mess
basically the GTM bridge were already booked
and I misbooked the bridge (bad date)
sorry again

/Morgan


Le 11/01/2017 à 17:44, Margaret Chiosi a écrit :
ok that worked

On Wed, Jan 11, 2017 at 11:25 AM, Rautakumpu, Mika (Nokia - FI/Espoo) 
mailto:mika.rautaku...@nokia.com>> wrote:
here is link which is working

https://coopnet.multimedia-conference.orange-business.com/?c=DBmKQ4dqDf



From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>]
 On Behalf Of SULLIVAN, BRYAN L
Sent: Wednesday, January 11, 2017 6:23 PM
To: Yunxia Chen mailto:helen.c...@huawei.com>>; Yang Xu 
(Yang, Fixed Network) mailto:yang@huawei.com>>; 
RICHOMME Morgan IMT/OLN 
mailto:morgan.richo...@orange.com>>; 
zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>; 
meng.zhaoxi...@zte.com.cn<mailto:meng.zhaoxi...@zte.com.cn>; 
by...@etri.re.kr<mailto:by...@etri.re.kr>; 
navid.nika...@eurecom.fr<mailto:navid.nika...@eurecom.fr>; 
wlu...@bupt.edu.cn<mailto:wlu...@bupt.edu.cn>; 
cs15mtech01...@iith.ac.in<mailto:cs15mtech01...@iith.ac.in>; 
cs15mtech01...@iith.ac.in<mailto:cs15mtech01...@iith.ac.in>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
Prakash Ramchandran 
mailto:prakash.ramchand...@huawei.com>>; 
giuseppe.care...@fokus.fraunhofer.de<mailto:giuseppe.care...@fokus.fraunhofer.de>;
 narinder.gu...@canonical.com<mailto:narinder.gu...@canonical.com>; 
bouch...@live.fr<mailto:bouch...@live.fr>; Olga Havel 
mailto:olga.ha...@huawei.com>>; 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>; 
jose.laus...@ericsson.com<mailto:jose.laus...@ericsson.com>; 
michael.pa...@tu-berlin.de<mailto:michael.pa...@tu-berlin.de>; 
lorenzo.tomas...@fokus.fraunhofer.de<mailto:lorenzo.tomas...@fokus.fraunhofer.de>;
 huang.leib...@zte.com.cn<mailto:huang.leib...@zte.com.cn>; Thajudheen Rajak 
mailto:thajudheen.ra...@huawei.com>>
Subject: Re: [opnfv-tech-discuss] [OPNFV] VNF on boarding: Q&A Functest versus 
orchestrator projects

Same. Here.
Is this meeting happening? Can’t we use an OPNFV GTM bridge?

Thanks,
Bryan Sullivan | AT&T

From: Yunxia Chen [mailto:helen.c...@huawei.com]
Sent: Wednesday, January 11, 2017 8:17 AM
To: Yang Xu (Yang, Fixed Network) 
mailto:yang@huawei.com>>; RICHOMME Morgan IMT/OLN 
mailto:morgan.richo...@orange.com>>; 
zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>; 
meng.zhaoxi...@zte.com.cn<mailto:meng.zhaoxi...@zte.com.cn>; 
by...@etri.re.kr<mailto:by...@etri.re.kr>; 
navid.nika...@eurecom.fr<mailto:navid.nika...@eurecom.fr>; 
wlu...@bupt.edu.cn<mailto:wlu...@bupt.edu.cn>; 
cs15mtech01...@iith.ac.in<mailto:cs15mtech01...@iith.ac.in>; 
cs15mtech01...@iith.ac.in<mailto:cs15mtech01...@iith.ac.in>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
Prakash Ramchandran 
mailto:prakash.ramchand...@huawei.com>>; 
giuseppe.care...@fokus.fraunhofer.de<mailto:giuseppe.care...@fokus.fraunhofer.de>;
 narinder.gu...@canonical.com<mailto:narinder.gu...@canonical.com>; 
bouch...@live.fr<mailto:bouch...@live.fr>; Olga Havel 
mailto:olga.ha...@huawei.com>>; 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>; SULLIVAN, 
BRYAN L mailto:bs3...@att.com>>; 
jose.laus...@ericsson.com<mailto:jose.laus...@ericsson.com>; 
michael.pa...@tu-berlin.de<mailto:mi

Re: [opnfv-tech-discuss] [OPNFV] VNF on boarding: Q&A Functest versus orchestrator projects

[Prakash Ramchandran]

this worked for me now
Thanks! This link works. US bridge is 929-322-2258 with 158991303#


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






From: Prakash Ramchandran
Sent: Wednesday, January 11, 2017 9:11 AM
To: 'morgan.richo...@orange.com'; Margaret Chiosi; Rautakumpu, Mika (Nokia - 
FI/Espoo)
Cc: SULLIVAN, BRYAN L; Yunxia Chen; Yang Xu (Yang, Fixed Network); 
zhao.huab...@zte.com.cn; meng.zhaoxi...@zte.com.cn; by...@etri.re.kr; 
navid.nika...@eurecom.fr; wlu...@bupt.edu.cn; cs15mtech01...@iith.ac.in; 
cs15mtech01...@iith.ac.in; opnfv-tech-discuss@lists.opnfv.org; 
giuseppe.care...@fokus.fraunhofer.de; narinder.gu...@canonical.com; 
bouch...@live.fr; Olga Havel; dmcbr...@linuxfoundation.org; 
jose.laus...@ericsson.com; michael.pa...@tu-berlin.de; 
lorenzo.tomas...@fokus.fraunhofer.de; huang.leib...@zte.com.cn; Thajudheen Rajak
Subject: RE: [opnfv-tech-discuss] [OPNFV] VNF on boarding: Q&A Functest versus 
orchestrator projects

Morgan,
tried on orange bridge via US number and asks pin code that does not work. May 
be we reschedule the meeting for tomorrow after Tech meeting of Bin Hu? - 
Thanks Prakash

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






From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com]
Sent: Wednesday, January 11, 2017 9:07 AM
To: Margaret Chiosi; Rautakumpu, Mika (Nokia - FI/Espoo)
Cc: SULLIVAN, BRYAN L; Yunxia Chen; Yang Xu (Yang, Fixed Network); 
zhao.huab...@zte.com.cn; meng.zhaoxi...@zte.com.cn; by...@etri.re.kr; 
navid.nika...@eurecom.fr; wlu...@bupt.edu.cn; cs15mtech01...@iith.ac.in; 
cs15mtech01...@iith.ac.in; opnfv-tech-discuss@lists.opnfv.org; Prakash 
Ramchandran; giuseppe.care...@fokus.fraunhofer.de; 
narinder.gu...@canonical.com; bouch...@live.fr; Olga Havel; 
dmcbr...@linuxfoundation.org; jose.laus...@ericsson.com; 
michael.pa...@tu-berlin.de; lorenzo.tomas...@fokus.fraunhofer.de; 
huang.leib...@zte.com.cn; Thajudheen Rajak
Subject: Re: [opnfv-tech-discuss] [OPNFV] VNF on boarding: Q&A Functest versus 
orchestrator projects

I do appologize for the mess
basically the GTM bridge were already booked
and I misbooked the bridge (bad date)
sorry again

/Morgan


Le 11/01/2017 à 17:44, Margaret Chiosi a écrit :
ok that worked

On Wed, Jan 11, 2017 at 11:25 AM, Rautakumpu, Mika (Nokia - FI/Espoo) 
mailto:mika.rautaku...@nokia.com>> wrote:
here is link which is working

https://coopnet.multimedia-conference.orange-business.com/?c=DBmKQ4dqDf



From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>]
 On Behalf Of SULLIVAN, BRYAN L
Sent: Wednesday, January 11, 2017 6:23 PM
To: Yunxia Chen mailto:helen.c...@huawei.com>>; Yang Xu 
(Yang, Fixed Network) mailto:yang@huawei.com>>; 
RICHOMME Morgan IMT/OLN 
mailto:morgan.richo...@orange.com>>; 
zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>; 
meng.zhaoxi...@zte.com.cn<mailto:meng.zhaoxi...@zte.com.cn>; 
by...@etri.re.kr<mailto:by...@etri.re.kr>; 
navid.nika...@eurecom.fr<mailto:navid.nika...@eurecom.fr>; 
wlu...@bupt.edu.cn<mailto:wlu...@bupt.edu.cn>; 
cs15mtech01...@iith.ac.in<mailto:cs15mtech01...@iith.ac.in>; 
cs15mtech01...@iith.ac.in<mailto:cs15mtech01...@iith.ac.in>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
Prakash Ramchandran 
mailto:prakash.ramchand...@huawei.com>>; 
giuseppe.care...@fokus.fraunhofer.de<mailto:giuseppe.care...@fokus.fraunhofer.de>;
 narinder.gu...@canonical.com<mailto:narinder.gu...@canonical.com>; 
bouch...@live.fr<mailto:bouch...@live.fr>; Olga Havel 
mailto:olga.ha...@huawei.com>>; 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>; 
jose.laus...@ericsson.com<mailto:jose.laus...@ericsson.com>; 
michael.pa...@tu-berlin.de<mailto:michael.pa...@tu-berlin.de>; 
lorenzo.tomas...@fokus.fraunhofer.de<mailto:lorenzo.tomas...@fokus.fraunhofer.de>;
 huang.leib...@zte.com.cn<mailto:huang.leib...@zte.com.cn>; Thajudheen Rajak 
mailto:thajudheen.ra...@huawei.com>>
Subject: Re: [opnfv-tech-discuss] [OPNFV] VNF on boarding: Q&A Functest versus 
orchestrator projects

Same. Here.
Is this meeting happening? Can’t we use an OPNFV GTM bridge?

Thanks,
Bryan Sullivan | AT&T

From: Yunxia Chen [mailto:helen.c...@huawei.com]
Sent: Wednesday, January 11, 2017 8:17 AM
To: Yang Xu (Yang, Fixed Network) 
mailto:yang@huawei.com>>

Re: [opnfv-tech-discuss] [mano-wg] [MANO] Meeting #16 Recap 2015+ D-Release Priority including Scenario , Installers Features and Tetsing vIMS

[Prakash Ramchandran]

Hi all,

We had a good first meeting of MANO WG for 2017(Meeting#16) and some of the 
action items taken  or completed today were

1. Priority for D release from MNAO working group added to  
http://wiki.opnfv.org/display/SWREL/Danube+priorities
Serge (Sprint) had questions on Interoperability and Bryan(AT&T) indicated 
Consistency across MANO stacks and End use Portability of VNFs a key.

2. The VNF On-Boarding  codes of functest were reviewed by Giuseppe(OpenBaton) 
who felt that it does not go far enough but will accept it for Release-D and 
would like to see more considerations as listed by him in email as well on MANO 
wiki Meeting 15.

3. The VNF On-boarding testing may be different as per Yingjun Li (Opera) and 
will assign a OPEN-O coder to review. There is difference between Compass  and 
Juju due to AAA using Keystone 2.0 vs 3.0 and MANO WG prefers Keystone 3.0 as 
moving from Newton to Ocata that will become a requirement as  Keystone 2.0 API 
will not be supported officially by OpenStack. Narinder mentioned that JOID can 
support client side 3.0 but for Platform  JuJu Chram  can use either Keystone 
2.0 or .3.0 and not both. Dvaid McBride  provided a link  -Keystone API Usage 
per Installer in Danube

4. The functest details was deferred to Morgan's functest  meeting later today 
and Narinder will fill in details for Juju there

5. Artur from Canonical provided brief description on OAI and EuroCom 
initiative by Juju for OPNFV.

6.ABOT BDD was requested for Debashis C(Rebaca Tech.) to  be moved to Weekly 
Tech Meeting as it involved more than MNAO and covers broader aspect of OPNFV 
using BDD framework and hence we request  Bin Hu to include that as part of his 
Thursday meetings when possible.

7 Discussions on other items on agenda deferred to next meeting 17 on Jan 25th.

For more details refer to wiki link
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

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






From: Prakash Ramchandran
Sent: Tuesday, January 10, 2017 12:25 PM
To: mano...@lists.opnfv.org
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [mano-wg] [MANO] Meeting #16 Recap 2015+ D-Release Priority including 
Scenario , Installers Features and Tetsing vIMS


Please join us tomorrow for MANO WG setting D-Release Proirities for 
Integration with OPNFV VIM and test vIMS as priority.

Agenda:

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111



Meeting Times: Every Even Wednesday at 15.00 UTC (7.00 am PST)  as per Project 
requests

 IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

Thanks


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

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

[opnfv-tech-discuss] Adding Multi-Calendar to Project or WG wiki pages

[Prakash Ramchandran]

Hi all,

Is there  a procedure to follow to add this to Project or WG wiki pages?
This link was presented today at TSC,
https://wiki.opnfv.org/display/ds/Multi+Calendar+Example
Can someone point where is the details for this to implement?

Thanks
Prakash

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






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

[opnfv-tech-discuss] Regards to MNAO priorities in D and consistancy in E or later releases

[Prakash Ramchandran]

Hi all,

There was asking for simplifying the MANO write-up for  Release D  at TSC today 
as the table for MANO Integration had too many points listed.
Danube 
priorities<https://wiki.opnfv.org/display/SWREL/Danube+priorities?src=mail&src.mail.timestamp=1484639012819&src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&src.mail.recipient=2c9e48d553af6aa90153b027b72c0007&src.mail.action=view>

Suggest the following simplification to message
MANO  Integration Pilot

Integration Pilot

MANO stack Integration pilot in Danube requires identifying ways and means to 
enable MANO modules to integrate with OPNFV VIM.

An effort is made in Danube to add nfvo and vnf artifacts through upstream 
OPEN-O and OpenBaton and Juju over OPNFV VIM  and test sample vnf(vIMS) through 
functest  This can be cleaned for  consistency across different stacks in 
future releases


Actual details of consistency of MANO stack integration we differ to later 
release as Bryan Sullivan has listed for release E.
e.g. of consistency could be Service Catalog addition for On-boarding,  using  
Registration, Health check and using Keystone v3 (AAA), Hierarchical Catalog 
etc.

If any of the MANO community  participants want to reword it  to reflect the 
view point please feel free to respond.

Thanks
Prakash

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






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

[opnfv-tech-discuss] [MANO] Meeting #17 Jan 25 UTC 15.00 / PST 7.00

[Prakash Ramchandran]

Please join us tomorrow for MANO WG Meeting 17

Agenda:

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

Jan  25, Wednesday : 15.00 UTC /7.00 PST  Meeting 17

Meeting Times: Every Even Wednesday at 15.00 UTC (7.00 am PST)  as per Project 
requests

 IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045
1.Agenda:
2.1.Agenda bashing
3.2.Review of last meeting (#15) and actions
a. a.Priority for D<https://wiki.opnfv.org/display/SWREL/Danube+priorities> 
- completed
b.b. Review of VNF 
on-boarding<https://wiki.opnfv.org/pages/viewpage.action?pageId=8687767> - Is 
anyone Interested in monitoring Intern for VNF 
On-boarding<https://wiki.opnfv.org/display/DEV/Intern+Project%3A+Open+Source+VNF+catalog>
c. c. Code review for VNF 
testing<https://gerrit.opnfv.org/gerrit/#/c/26769/> - Completed  common testing 
for vIMS (Orchestra to use Orchestration and Opera to use Compass Installer for 
testing vIMS as VNF use case)
d.d. Scenario conclusion - Orchestra - (???) , 
Opera(os-onos-nofetaure-ha?), Domino (os-...), Model (None), , Parser(?), - Do 
we have a path to no scenario? Whats input from Installers on Scenario for MANO?
e.e.  Release E (Move left out D to E +??? for consistency?)
f. f. ABOT framewrok for BDD has impact beyond MANO and hence moved the 
discussions to Tech Meeting - Completed Transfer to Weekly Tech for Thursday.
4.3.Architecture 
comparison<https://wiki.opnfv.org/display/mano/Architecture> and LCM.
5.4.OSM & ETSI NFV updates - Refer [ RP ] in Meeting 15 -2016
6.5.Report from upstream (OpenBaton, Open-O, openECOMP, JuJu, Tacker, 
OSM/Plug-test) and its impact on MANO WG
7.6.MANO related tests for Dovetail beyond C for D based on what we have 
and who will volunteer to get this moving?
8.7.Continuing on Reviewing Best Practices for VNF On-boarding & LCM based 
on current community project status?
9.8.Actionable Items and Agreement summary recording



2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

Thanks


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

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

[opnfv-tech-discuss] [MANO] Meeting #18 Feb 8 UTC 15.00 / PST 7.00 - Agenda planning for meeting 18

[Prakash Ramchandran]

Hi all,
Here is report for MANO WG for month of JAN 2017 (Some background to  Dec 2016 
for reference only)

Please review Agenda for  MANO WG Meeting 18th for next Wednesday  Feb 8th

Agenda:  (please plan and suggest anything we have missed herein)

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111
Feb 8, Wednesday : 15.00 UTC /7.00 PST  Meeting 18


  1.   Agenda bashing
  2.  Plugtest 
<http://www.etsi.org/index.php/news-events/events/1104-1st-nfv-plugtests> and 
inputs for MANO from 
Participants<https://wiki.opnfv.org/download/attachments/6827111/Plugtest-inputs-for-MANO-WG.odt?version=1&modificationDate=1486004423479&api=v2>.
  3.  Follow-up on Action Items and  from last month and finalizing E-Release 
Goals and agreements
a.Goals for E should be to release test tools for integration and testing MANO 
stack -Bryan
b.Release E discussions: using keystone Auth v3 in Release 
E<http://docs.openstack.org/developer/keystoneauth/using-sessions.html> - Moved 
from D to E
c.Review and Guidance for MANO based on newly specified OPNFV Archiecture - 
OPNFV Architecture for Danube 
release<https://wiki.opnfv.org/display/DOC/OPNFV+Architecture+for+Danube+release>
 - New from TSC call 1/31/2016
d.Report from upstream (OpenBaton, Open-O, openECOMP, JuJu, Tacker, 
OSM/Plug-test) and its impact on MANO WG - Need inputs for E from all MANO 
Projects

  1.  Review of VNF 
on-boarding<https://wiki.opnfv.org/pages/viewpage.action?pageId=8687767> - 
Action taken Prakash is monitoring Intern for VNF 
On-boarding<https://wiki.opnfv.org/display/DEV/Intern+Project%3A+Open+Source+VNF+catalog>
 for MANO Projects.In D we took vIMS should we look at 
vEPC<https://wiki.opnfv.org/display/TBM/Epc+Network+Function%2C+Mme+Or+Pgw> ?.
  2.  Code review for VNF testing<https://gerrit.opnfv.org/gerrit/#/c/26769/> - 
Completed  common testing for vIMS (Orchestra to use Orchestration and Opera to 
use Compass Installer for testing vIMS as VNF use case)
  3.  How to arrive at best practices for NS and VNF Package Formats and run 
time, Generation refer link  Models 
VNF-Packaging<https://wiki.opnfv.org/display/models/Testing> and 
Riftt.io<http://rift.io/>
  4.  What will be selection of use case and test areas/tests which we can 
drive MANO inputs for D release
  5.  Continuing on Reviewing Best Practices for VNF On-boarding & LCM
  6.  OSM & ETSI NFV updates - Refer [ RP ] in Meeting 15 -2016.

Thanks

Prakash

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








opnfv-mano-wg-report-jan-2017.pdf
Description: opnfv-mano-wg-report-jan-2017.pdf
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [MANO] Meeting #18 Feb 8 UTC 15.00 / PST 7.00 - Agenda

[Prakash Ramchandran]

Hi all,

To avoid too many topics for 1 meeting I have prioritized and pushed few to 
next meeting and here is the new agenda for


Feb 8, Wednesday : 15.00 UTC /7.00 PST  Meeting 18

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111


IRC#opnfv-mano

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045


  1.   Agenda bashing
  2.  Follow-up on Action Items and  from last month and finalizing E-Release 
Goals and agreements
 *   Goals for E should be to release test tools for integration and 
testing MANO stack -Bryan
 *   Release E discussions: using keystone Auth v3 in Release 
E<http://docs.openstack.org/developer/keystoneauth/using-sessions.html> - Moved 
from D to E -D2E
 *   Review and Guidance for MANO based on newly specified OPNFV 
Archiecture - OPNFV Architecture for Danube 
release<https://wiki.opnfv.org/display/DOC/OPNFV+Architecture+for+Danube+release>
 - New from TSC call 1/31/2016
 *   Report from upstream (OpenBaton, Open-O, openECOMP, JuJu, Tacker, 
OSM/Plug-test) and its impact on MANO WG - Need inputs for E from all MANO 
Projects
  3.  How to arrive at best practices for NS and Cloud Native VNF Package 
Formats and run time,
 *Generating YAML(TOSCA/YANG)  refer link  Models 
VNF-Packaging<https://wiki.opnfv.org/display/models/Testing> and 
Riftt.io<http://rift.io/> , TOSCA file inside CSAR zip 
file<http://tinyurl.com/tosca-yaml-csar>
 *Linux Package-Management 
formats<https://www.digitalocean.com/community/tutorials/package-management-basics-apt-yum-dnf-pkg>
 , OpenSUSE Package Manager<https://en.opensuse.org/Package_management>
  4.  Follow-up on Action Items and  from last month and finalizing E-Release 
Goals and agreements (must be before March 27 as per EUAG)

 *   NS/VNF Package Standards adapted ( TOSCA/ CSAR (OPen-O)?, TOSCA / 
rift.io Juju YAML (OpenBaon?), TOSCA/Rift.io (OSM), ECOMP ? - AI who?
 *   VNF Onboarding Process across MANO stacks (to be consistent? how?) - 
AI (who?)
 *   Keystone v3 - (Installers JOID/Junju in E?)
 *   Use case continue with simple Hello world + vIMS or add one more in E?
  5.   Plugtest 
<http://www.etsi.org/index.php/news-events/events/1104-1st-nfv-plugtests> and 
inputs for MANO from 
Participants<https://wiki.opnfv.org/download/attachments/6827111/Plugtest-inputs-for-MANO-WG.odt?version=1&modificationDate=1486004423000&api=v2>.
Thanks
Prakash


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






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

[opnfv-tech-discuss] [MANO] Meeting #18 Feb 8 UTC 15.00 / PST 7.00 - Agenda

[Prakash Ramchandran]

Hi all,

To avoid too many topics for 1 meeting I have prioritized and pushed few to 
next meeting and here is the new agenda for


Feb 8, Wednesday : 15.00 UTC /7.00 PST  Meeting 18

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

IRC#opnfv-mano

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045


  1.   Agenda bashing
  2.  Follow-up on Action Items and  from last month and finalizing E-Release 
Goals and agreements
 *   Goals for E should be to release test tools for integration and 
testing MANO stack -Bryan
 *   Release E discussions: using keystone Auth v3 in Release 
E<http://docs.openstack.org/developer/keystoneauth/using-sessions.html> - Moved 
from D to E -D2E
 *   Review and Guidance for MANO based on newly specified OPNFV 
Archiecture - OPNFV Architecture for Danube 
release<https://wiki.opnfv.org/display/DOC/OPNFV+Architecture+for+Danube+release>
 - New from TSC call 1/31/2016
 *   Report from upstream (OpenBaton, Open-O, openECOMP, JuJu, Tacker, 
OSM/Plug-test) and its impact on MANO WG - Need inputs for E from all MANO 
Projects
  3.  How to arrive at best practices for NS and Cloud Native VNF Package 
Formats and run time,
 *Generating YAML(TOSCA/YANG)  refer link  Models 
VNF-Packaging<https://wiki.opnfv.org/display/models/Testing> and 
Riftt.io<http://rift.io/> , TOSCA file inside CSAR zip 
file<http://tinyurl.com/tosca-yaml-csar>
 *Linux Package-Management 
formats<https://www.digitalocean.com/community/tutorials/package-management-basics-apt-yum-dnf-pkg>
 , OpenSUSE Package Manager<https://en.opensuse.org/Package_management>
  4.  Follow-up on Action Items and  from last month and finalizing E-Release 
Goals and agreements (must be before March 27 as per EUAG)
 *   NS/VNF Package Standards adapted ( TOSCA/ CSAR (OPen-O)?, TOSCA / 
rift.io Juju YAML (OpenBaon?), TOSCA/Rift.io (OSM), ECOMP ? - AI who?
 *   VNF Onboarding Process across MANO stacks (to be consistent? how?) - 
AI (who?)
 *   Keystone v3 - (Installers JOID/Junju in E?)
 *   Use case continue with simple Hello world + vIMS or add one more in E?
  5.   Plugtest 
<http://www.etsi.org/index.php/news-events/events/1104-1st-nfv-plugtests> and 
inputs for MANO from 
Participants<https://wiki.opnfv.org/download/attachments/6827111/Plugtest-inputs-for-MANO-WG.odt?version=1&modificationDate=1486004423000&api=v2>.
Thanks
Prakash


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






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

[opnfv-tech-discuss] MANO WG Meeting#18 and Summary plus Next Meeting#19 for Feb22

[Prakash Ramchandran]

ANO from 
Participants<https://wiki.opnfv.org/download/attachments/6827111/Plugtest-inputs-for-MANO-WG.odt?version=1&modificationDate=1486004423000&api=v2>.
 - Deferred to next meeting
Thanks
Prakash

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






___
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] Projects > SNAPS-OO

[Prakash Ramchandran]

Kevin,

Few question on SNAP-OO team  as I could not ask them at Technical presentation 
earlier

1) pytest , is MIT license usable instead of recommended  Apache License for 
use in SNAP-OO?
2) Is there a need to wrap around the current FUNCTEST Swagger APIs to support 
it using SNAP-OO?
3) You mentioned that there is no support for SDN (OD/ONOS/OC) , how will it 
the support several scenarios  if it just focuses on OpenStack alone?
4) What will be relation between this project and other Test Project,  as 
Dependencies or ply stated as py library, but how do we then leverage 
duplication of work in different test projects? (Is it like some based on py 
2.7 and others based on py3.3 etc  or we stop working on FUNCTEST and move all 
their resources to SNAP-OO?
5) Are we going to keep the focus here on virtual env only for development and 
let other Test Projects focus on Deployment testing?


Hope this questions makes sense to address before we get to  TSC for Project 
Creation.

Thanks
Prakash


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






From: Kevin Kershaw (OPNFV Confluence) [mailto:conflue...@opnfv.org]
Sent: Tuesday, January 24, 2017 12:13 PM
To: Prakash Ramchandran
Subject: [OPNFV confluence] Projects > SNAPS-OO

[cid:image003.jpg@01D28337.D178A3B0]<https://wiki.opnfv.org/display/~kjkershaw?src=mail&src.mail.timestamp=1485288802330&src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&src.mail.recipient=2c9e48d553af6aa90153b027b72c0007>

Kevin Kershaw edited a page




[page 
icon]<https://wiki.opnfv.org/display/PROJ/SNAPS-OO?src=mail&src.mail.timestamp=1485288802330&src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&src.mail.recipient=2c9e48d553af6aa90153b027b72c0007&src.mail.action=view>


SNAPS-OO<https://wiki.opnfv.org/display/PROJ/SNAPS-OO?src=mail&src.mail.timestamp=1485288802330&src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&src.mail.recipient=2c9e48d553af6aa90153b027b72c0007&src.mail.action=view>



...

The OpenStack Python APIs are very useful but can be rather cumbersome to use. 
As they have been written for procedural use, managing newly minted objects 
(networks, routers, images, instances, etc.) becomes more daunting the larger 
the virtual environment becomes. As certain OpenStack objects contain others, 
the creator classes encapsulate not only the first-class object (network, 
router, keypair, image, user, project, VM instance, security group), but also 
any other underlying OpenStack objects (i.e. ports, subnets) that are not 
shared across objects, and all of the individual API calls required during 
creation.

...


[View page 
Icon]<https://wiki.opnfv.org/display/PROJ/SNAPS-OO?src=mail&src.mail.timestamp=1485288802330&src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&src.mail.recipient=2c9e48d553af6aa90153b027b72c0007&src.mail.action=view>

View 
page<https://wiki.opnfv.org/display/PROJ/SNAPS-OO?src=mail&src.mail.timestamp=1485288802330&src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&src.mail.recipient=2c9e48d553af6aa90153b027b72c0007&src.mail.action=view>

•


[Add comment 
Icon]<https://wiki.opnfv.org/display/PROJ/SNAPS-OO?showComments=true&showCommentArea=true&src=mail&src.mail.timestamp=1485288802330&src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&src.mail.recipient=2c9e48d553af6aa90153b027b72c0007&src.mail.action=comment#addcomment>

Add 
comment<https://wiki.opnfv.org/display/PROJ/SNAPS-OO?showComments=true&showCommentArea=true&src=mail&src.mail.timestamp=1485288802330&src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&src.mail.recipient=2c9e48d553af6aa90153b027b72c0007&src.mail.action=comment#addcomment>

•

[Like 
Icon]<https://wiki.opnfv.org/plugins/likes/like.action?contentId=8688013&src=mail&src.mail.timestamp=1485288802330&src.mail.notification=com.atlassian.confluence.plugins.confluence-content-notifications-plugin%3Apage-edited-notification&src.mail.recipient=2c9e48d553af6aa90153b027b72c0007&src.mail.action=like&jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ4c3JmOjJjOWU0OGQ1NTNhZjZhYTkwMTUzYjAyN2I3MmMwMDA3IiwicXNoIjoiNjIxNzk3YjQ5YmNjNmVkMTIwYzAyNDhiYjFlNGRiZjNhZDVlMWVmMT

[opnfv-tech-discuss] [mano-wg] Regards to MNAO priorities in E and Architeture inputs #meeting 18 (Continuation)

[Prakash Ramchandran]

Hi all,
Few  participating MANO WG projects could not complete their inputs for 
Release-E and Architectural, plan to continue discussions of Meeting#18 on 
those two issues

Please join us Wednesday Feb 15th  Regards to MNAO priorities in E and 
Architecture inputs #meeting 18 (Continuation).

Agenda:

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

Agenda includes E-Release and OPNFV Architecture inputs.

Meeting Times: Every Even Wednesday at 15.00 UTC (7.00 am PST)  as per Project 
requests

 IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

Thanks

Prakash

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






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

[opnfv-tech-discuss] [mano-wg] support Keystone Api V2 and V3 in OPNFV Release D and E

[Prakash Ramchandran]

Hi all,

We have some indication from Compass as they need to downgrade their efforts to 
support Keystone V2.0  for Opera in D , where as JOID needs to upgrade its 
support for Keystone v3.0 API for E.

Please comment if my understanding is correct by installers and we can discuss 
this in tomorrow's MANO WG meeting  for E-Release minimum baselines suggested 
by  David  McBride Release manager OPNFV as OpenStack Ocata and Keystone API 
v3.0.

Thanks
Prakash

[cid:jira-generated-image-avatar-b775a13f-c1b8-459a-a31f-4cc6ffefbeb8]

Harry Huang 
commented on [Improvement] 
COMPASS-524




Re: Support Keystone Api V2 



Compass now has a open-o scenario (os-nosdn-openo-noha) has this Api issue 
which mainly because open-o sun release and juju2.0 are using keystone Api v2 
while compass creates keystone Api v3 as default. This is the only scenario 
which may fail because of Api v3 in compass. However you can still be 
authorized with api v2 openrc file to access almost full openstack service 
except some identity function. So far compass manage to install open-o and 
juju-controller using api v2 rc file to authorize with v3. Considering open-o 
mercury is scheduled to release in this April, we may not be talking this issue 
two months later.


[Add Comment]

Add Comment






This message was sent by Atlassian JIRA (v7.0.4#70113-sha1:3aced62)

[Atlassian logo]




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

[opnfv-tech-discuss] [mano-wg] MNAO priorities in E and Architeture inputs #meeting 18 (Continuation) 15 UTC/7 PST -Reminder

[Prakash Ramchandran]

Hi all,
Few  participating MANO WG projects could not complete their inputs for 
Release-E and Architectural, plan to continue discussions of Meeting#18 on 
those two issues

Please join us Wednesday Feb 15th  Regards to MNAO priorities in E and 
Architecture inputs #meeting 18 (Continuation).

Agenda:

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

Agenda includes E-Release and OPNFV Architecture inputs.

Meeting Times: Every Even Wednesday at 15.00 UTC (7.00 am PST)  as per Project 
requests

 IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

Thanks

Prakash


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






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

[opnfv-tech-discuss] [mano-wg] Best Practices and Wiki updates for Release-E preparation

[Prakash Ramchandran]

Hi all,

Based on our last 2-3 meetings and actions before we consolidate by next week 
please update and make all your links current for the following

Best Practices<https://wiki.opnfv.org/display/mano/Best+Practices> page is 
created as per action Item 1 Meeting#18

Release-E planning updates for MANO WG Wiki pages

Please update your  MANO participation and project collaboration topics for 
Release-E
https://wiki.opnfv.org/display/mano/MANO+Project+Guidance
(Carry over from Release D as well what you plan to add from MANO in Release E)

Since Upstream MANO Projects too have evolved this is time for MANO WG upstream 
participants to update their
Design/Deployment,  Tools ,SDK / Library, APIs, Supports for different VNFM, 
VIMS, Use cases and any Introduction Videos etc.

I have tried to re-org by trying to put in alpha order and please feel free to 
correct if there is any mistakes or broken links.

Also will follow up with mano-wg plans for next week plans after I can 
summarize the logs and reports for this week.

 I  would like to seek help on using mano-wg irc #mano-wg to take notes on irc 
from next week to get better notes than we do now on Wiki page directly.

Also please let me know do we need Jira to track the MANO WG activity on Best 
Practices once we put down the tasks on the page created.
Any guidance on this will be helpful consolidating Documents we can add the 
current or Future release.

Thanks
Prakash



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






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

[opnfv-tech-discuss] [mano-wg] Best Practices and Wiki updates for Release-E Inputs sought from MANO WG particpants

[Prakash Ramchandran]

Hi all,

Have updated the MANOWG Meeting#18 (last two weeks) summary
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

Please feel free to edit and update MANO pages to reflect  what MANO WG must do 
to co-ordinate with other work groups and Projects:
Refer
Cross Work Group/Project Co-ordination has brought few topics we need to 
address for defining  the Best Practices  for MANO in Release E/F:
There will be discussions at Weekly Tech Meeting on this net week Thursday 
morning  BJT  UTC 14 / 6 AM PST

For MANO WG contributions please refer
For web access refer link:  
https://wiki.opnfv.org/display/mano/MANO+OPNFV+cross-project?src=contextnavpagetreemode
And for your suggestions: Edit and add to   Cross Project/WG  Co-ordinations 
through MANO WG

Here are some suggestions to locate and update the site tables with latest info 
from other WG's ot upstream.
1.  Infra WG: Scenario definition for MANO
  Jira Tciket / gerrit

2. Tetsing WG: VNF testing using vIMS
--Jira Ticket /gerrit

3.The Compliance Verification Program and Dovetail projects have listed on Jira 
"Kanban board", seeking inputs for MANO for two specific Test Areas listed 
below.

https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=147&view=detail&selectedIssue=DOVETAIL-345

Priority:1
2017-2 (E): MANO stack interop with VIMs
Priority:2
2018-1 (F): MANO-stack interop for VNFs (VNF portability)


Also we are working on Best practices for Top 10 items and all MANO stacks can 
contribute within the framework to state what they do and how? We can bring 
this commonality or differences to arrive at Best Practices.
https://wiki.opnfv.org/display/mano/Best+Practices

Please feel free to update and we will go over them at next meeting on Feb 22 
refer link for meeting
https://wiki.opnfv.org/display/mano/OPNFV+MANO+Work+Group+Meetings

Thanks
Prakash


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






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

[opnfv-tech-discuss] [test-wg] A survey regarding Open Source VNF Catalogue

[Prakash Ramchandran]

Bryan and Kumar,

I could not locate the email you pointed in my emails so will use directly 
point  link here in
https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-February/014950.html


Concretely, My 5 main criteria to deploy a VNF on top of OPNFV are:

#1:VNF should establish its name and context as an Application or Component 
with a path to Application/Component Catalog(Cat.3/Repo). This assumes that 
hierarchy of Catalogues/Repos is Cat.5/Repo5 (Marketplace), Cat.4/Repo4 
-Service Provider Service Catalog (This is where you onboard NS/NSD), 
Cat.3/Repo3 - Application/Component Catalog (This is where you onboard your 
VNF/VNFD/Packages etc), (Cat2./Repo2) -SDN Controller Catalog, (Cat1/Repo1) 
Image Catalog [Glance for Openstack], Cat.0/Repo0 - Instance Catalog [like HEAT 
catalog in OpenStack, or] Any Catalogue in OPNFV that shows running Instances', 
their id, state etc.


Note: Cat5 / Marketplace Catalog is external to Service Provider and is part of 
hosting and can be found in all Markets including OpenStack, OPEN-O, OpenBaton, 
OSM, openECOM etc.
[cid:image004.jpg@01D28C4F.4AEAE9E0]


#2:VNF Should have a list of metadata described either in its package along 
with Catalogue architecture for identifying explicitly a.Cat.3/repo3  path with 
list of components/topology/relations  in Cat3. and any Scenario for OPNFV VIM 
Configuration and reference to SDN-C Cat2 if used, Any underlay topology in 
Cat2/Repo2, And any system images to use in Cat.1/Repo1,and specify default 
Orchestrator Instance Catalog to use if any or optional ones.
#3:The preference would be to use CSAR. tgz or an Orchestrator acceptable 
formats to avoid conversion at launch . Thus this means we want to ensure that 
there is a run time specified and will be native to OPNFV MANO Stack
#4:The VNF Packages' are signed and have a signature file associated to verify 
that these are from valid repos and that meet security criterions of OPNFV 
Security WG and or Badge certifications
#5:The LCM of VNF will follow standard configure, init metadata, run, start, 
pause , snapshot, restart, restore,[optional for now Scale-up, Scale-down, 
Scale-out, Scale-in], stop, delete metadata, de-configure etc.

We will discuss this in MANO WG this tomorrow and will confirm priorities.

Bryan too has stated his 5 and would like to get an agreement for Release-E as 
we are too far into to D to add any of this now.

Thanks
Prakash





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






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

[opnfv-tech-discuss] [mano-wg] Release-E Priority aggreements and OPNFV Architecture inputs

[Prakash Ramchandran]

Hi all,



Please join us Wednesday Feb 22nd  Regards to MNAO priorities in E and 
Architecture inputs #meeting 19

Agenda:

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

Agenda includes E-Release and OPNFV Architecture inputs.

Meeting Times: Every Even Wednesday at 15.00 UTC (7.00 am PST)  as per Project 
requests

 IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

Thanks

Prakash


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






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

[opnfv-tech-discuss] [mano-wg] Meeting#19 Summary of E-Release Priority & Architecture Discussions (Cont.)

[Prakash Ramchandran]

Hi all,
Here is quick summary from IRC will update Wiki after we have E-Release 
discussions through emails by end of week.
Thanks
Prakash
Meeting summary

  1.
 *   rprakash 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-5>,
 15:00:53)
Agenda Bashing

  1.  Best Practices 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-8>,
 15:09:55)
 *   https://wiki.opnfv.org/display/mano/Best+Practices 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-9>,
 15:10:03)
 *   OpenBaton offers Packages for VNFM for gVNFM as well Juju 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-11>,
 15:16:09)
 *   Docker based packaging is also being connsidered 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-12>,
 15:16:38)
 *   bootsrap for NFVO+VNFM will be from OpenBaton and Integration with 
OPNFV VIM will be using JOID Installer + Scenario? 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-13>,
 15:18:30)
 *   Scnario for OPEN-O os-openo-nofaeture-ha with compass & JOID 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-14>,
 15:19:53)
 *   AGREED: Priority 1 is Integrating MANO Stack Compaonents over OPNFV 
VIM 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-15>,
 15:23:40)
 *   Catalog and Priority for integrating VNF over the MANO Integration 
platform 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-16>,
 15:35:20)
 *   
https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-February/014950.html 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-17>,
 15:35:32)
 *   VNF should establish its name and context as an Application or 
Component with a path to Application/Component Catalog(Cat.3/Repo). This 
assumes that hierarchy of Catalogues/Repos is Cat.5/Repo5 (Marketplace), 
Cat.4/Repo4 -Service Provider Service Catalog (This is where you onboard 
NS/NSD), Cat.3/Repo3 - Application/Component Catalog (This is where you onboard 
your VNF/VNFD/Packages etc), (Cat2./Repo2) -SDN Controller Catalo 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-18>,
 15:36:04)
 *   MANO SB APIs Or-Vi is most mature at this time to consider 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-19>,
 15:43:23)
 *   Close loop monitoring is a possible candidate for OPEN-O with Doctor 
Project' 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-20>,
 15:45:45)
 *   VNFD use of Simaple TOSCA YAML file is norm for most MANO projects 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-21>,
 15:47:13)
 *   Define first the metadata and content like using Blueprint etc before 
a fomrat can be made or agreed 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-22>,
 15:50:02)
 *   How you create package is through SDK which is being proposed by both 
OpenBaton and Open-O 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-23>,
 15:51:55)


  1.  Architecture from MANO side 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-24>,
 15:56:45)
 *   
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111&preview=/6827111/10289542/MANO%20WG%20Priority-Directions-D2Eand%20Architetcure-v1.21.pptx
 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-25>,
 16:02:02)
 *   reviewe both E-Relase Priority and Architecture inputs to Tapio/TSC 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-26>,
 16:02:29)
 *   ACTION: to follow up E-Release Priority by email 
(rprakash<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html#l-27>,
 16:02:56)


Meeting ended at 16:03:03 UTC (full 
logs<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-02-22-15.00.log.html>).
Action items

  1.  to follow up E-Release Priority by email


Prakash Ramcha

Re: [opnfv-tech-discuss] [netready] OPNFV Hackfest Paris

[Prakash Ramchandran]

George,

Following your drive to add vSwitch HA and other use cases encouraged to find 
if  Gluon L3VPN use case is addressed before I can look at Edge Cloud.

If I missed any review on L3VPN point to me and will follow up.

 If not yet, this  time we can move 
NETREADY-7<https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=99&projectKey=NETREADY&view=planning&selectedIssue=NETREADY-7>
  that to Release-E as potential candidate which points to 
https://en.wikipedia.org/wiki/Cloudlet

Thanks
Prakash


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






From: Georg Kunz [mailto:georg.k...@ericsson.com]
Sent: Wednesday, February 22, 2017 8:45 AM
To: HU, BIN (bh5...@att.com); Tim Irnich; Nikolas Hermanns; 
gergely.csat...@nokia.com; Prakash Ramchandran; jlin...@cisco.com; Ahmed 
Elbornou (amaged) (ama...@cisco.com); opnfv-tech-discuss@lists.opnfv.org; 
thomas.hamble...@nokia.com
Subject: [opnfv-tech-discuss][netready] OPNFV Hackfest Paris

Hi all,

As promised in the last NetReady meeting, I would like to start a discussion 
about potential topics for the upcoming plugfest and hackfest and bounce them 
with the team.

The plugfest / hackfest will take place in Paris (France) April 24 - 28.

Potential hackfest agenda items for the NetReady team:

· Evolution of the Gluon integration

o   Creation and integration of other protons (APIs)

§  SFC

§  layer-2 networking

§  "exotic networking use case" showcasing Gluon's flexibility

o   Maintenance of existing scenario

o   Extension of Gluon scenario to other installers

· Potential new use cases

o   Container networking

o   Edge cloud networking

o   Information centric networking

o   ...

This is just a starting point. Your feedback is very welcome. Let's try to 
jointly build a good agenda.

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] [mano-wg] OPNFV Release-E agreements and Priority and impact of ONAP on MANO Projects- Meeting#20

[Prakash Ramchandran]

Hi all,

I am adding the agreements we have to date for Release-E -Content for MANO 
Projects at high level. below. Also I have prioritized based on discussions and 
debates in MANO WG over last 5 meetings.
Tentatively can  update Release-E link for 
MANO<https://wiki.opnfv.org/pages/viewpage.action?pageId=8688472> but final 
agreements we should arrive  by February 28  to make it official , unless there 
is a request for additional time due to ONAP  which we will discuss on March1st 
meeting.

Please reply emails and  address  any concerns you may have . Plus like to hear 
if we need a JIRA account for MANO WG to document this with more details or 
just update the Release-E 
link<https://wiki.opnfv.org/pages/viewpage.action?pageId=8688472> and let 
projects add the JIRA tickets for their work with respect to four priorities 
listed.


Please join us Wednesday March 1st  Regards to OPNFV Release-E agreements and 
Priority and impact of ONAP on MANO Projects - Meeting#20

Agenda:

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

Agenda includes E-Release agreements and ONAP inputs.

Meeting Times: Every Even Wednesday at 15.00 UTC (7.00 am PST)  as per Project 
requests

 IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

March 1st, Wednesday : 15.00 UTC /7.00 PST  Meeting #20

  1.  Agenda Bashing
  2.  Need JIRA for consolidating E-Rlease Priority for MANO WG / Alternate to 
refer to JIRA per MANO Projects?
  3.  ONAP 
<https://www.yahoo.com/tech/linux-foundation-announces-merger-open-source-ecomp-open-14052.html>
 and its impact on MNAO WG for OPERA (OPEN-O/ECOMP)
  4.  Final Agreements for Release E by both Orchestra , Opera and other 
participating projects + Upstream
Agreements Approval by MANO WG team
Consolidated E-Release inputs from MANO WG
MANO Projects in E release will focus on test tools for integration and testing 
MANO stack  from Meeting #18
 Agreed consistency across MANO stacks we mean "Consistency of end users 
experience" from Meeting #18
Priority 1 is Integrating MANO Stack Components over OPNFV VIM from Meeting #19 
2017
Priority 2  is considerations for agreement on VNF On-boarding from Meeting #19 
2017
Priority 3 is Continuing on Reviewing Best Practices for VNF On-boarding & LCM 
from Meeting #19 2017 plus EUAG 
reference<https://wiki.opnfv.org/display/mano/VNF+Onboarding>
Priority 4 Use inputs from OSM for VNFD and NSD challenges. from Meeting #15 
-2016


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






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

[opnfv-tech-discuss] [mano-wg] OPNFV Release-E agreements and Priority and impact of ONAP on MANO Wed March 1, PST 7/UTC 15

[Prakash Ramchandran]

Hi all,


Please join us Wednesday March 1st  Regards to OPNFV Release-E agreements and 
Priority and impact of ONAP on MANO Projects - Meeting#20
Based on the recent LinuxFoundation "ONAP" project announcement  (aligning 
efforts from  ECOPM and OPEN-O) like to review its impact on E-Release Priority 
and work items listed below. Please feel free to join and understand the 
ongoing efforts in OPNFV and upstream to meet  the challenges in MANO space.



Agenda:

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

Agenda includes E-Release agreements and ONAP inputs.

Meeting Times: Every Even Wednesday at 15.00 UTC (7.00 am PST)  as per Project 
requests

 IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045


March 1st, Wednesday : 15.00 UTC /7.00 PST  Meeting #20

  1.  Agenda Bashing
  2.   JIRA for consolidating E-Release Priority : option 1 - Have separate one 
for MANO WG option 2- Use the ones by respective Projects to refer to
  3.  ONAP 
<https://www.yahoo.com/tech/linux-foundation-announces-merger-open-source-ecomp-open-14052.html?soc_src=mail&soc_trk=ma>
 and its impact on MNAO WG for OPERA (OPEN-O/ECOMP) - ONAP slide 
1.0<https://wiki.opnfv.org/download/attachments/6827111/OPNFV-MANO-with-ONAP-v1.0.ppt?version=2&modificationDate=1488329913104&api=v2>
  4.  Final Agreements for Release E by both Orchestra , Opera and other 
participating projects + Upstream
5. Agreements Approval by MANO WG team
Consolidated E-Release Work Items from MANO WG
MANO Projects in E release will focus on test tools for integration and testing 
MANO stack  from Meeting #18
 Agreed consistency across MANO stacks we mean "Consistency of end users 
experience" from Meeting #18
Proposed wok Items based on Priorities arrived earlier meetings to follow up 
with Actions and Assignments

Look forward to participation from  OPNFV and Upstream.

Thanks
Prakash

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






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

[opnfv-tech-discuss] [mano-wg] WG and asociated projects priority Meeting #21

[Prakash Ramchandran]

Hi all,

Please join for MANO WG Meeting#21 this Wednesday
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111


Meeting Times: Every Even Wednesday (7.00 am PST)  at 15.00 UTC, Other  Ad-hoc 
meeting as per Project requests

 IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045



Agenda:

March 8th, Wednesday : 15.00 UTC /7.00 PST  Meeting #21

1.Agenda Bashing

2.MANO WG Survey (TBD) / MANO WG Feb 
report<https://wiki.opnfv.org/download/attachments/6827111/opnfv_%20%20%20opnfv-mano-wg-report-feb-2017.pdf?version=1&modificationDate=1488848003498&api=v2>

3. Models/VNF Graph additions from Models/Domino call from this week for use 
cases through Models and possible SampleVNFs

4. New timings going back to 14.00 UTC ( 7 AM PDT, 9 PM EU, Asia India  IST 
7.30 PM / China CST 11 PM)

5. Discussions on work items identified for Q1 not able to cover from last week.


Thanks
Prakash

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






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

[opnfv-tech-discuss] [mano-wg] Minutes of todays mano-wg meeting fro IRC

[Prakash Ramchandran]

Hi all,

Summary of MANO Meeting#21
Minutes:
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-03-08-14.58.html

Please review and next meeting Wednesday 3/15/2017  onwards  time will be 14 
UTC /7 AM PDT

I will update the meeting link and I do not see any conflict as we are just 
moving back to our Day Light saving time used before.

But if any conflicts are there please let us know.

Thanks
Prakash

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






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

[opnfv-tech-discuss] [mano-wg] Moving from D to E and asociated projects priority Meeting #22

[Prakash Ramchandran]

Hi all,

Please join for MANO WG Meeting#22 this Wednesday
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111


Meeting Times: Every Wednesday (7.00 am PDT)  at 14.00 UTC, (Note Daylight 
changes here 14 UTC instead of 15)

 IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045



Agenda:


March 15th, Wednesday : 14.00 UTC /7.00 PDT  Meeting #22

1.Agenda Bashing

 Refer log of Tech meeting last week  MANO WG update - 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-09-14.01.html

2. Review action items from last meeting and progress on

 AI101/102/103 - Scenario, MANO Components , External vs. Internal Build  - 
PTL Opera/Orchestra

 AI201/202 - VNF On-boarding Flow + Use case descriptors (vEPC/vIMS) - PTL 
Models/Domino  + Prakash

3. New timings for Models+Domino for inputs to MANO?

4. Review MANO WG event planning Plugfest + ONF +  plans for OpenStack 
Boston<https://etherpad.openstack.org/p/mano> +   +MANO WG Survey Questions?

6. Discussions on work items identified for Q1 not able to cover from last 2 
meetings  if time permits


Thanks
Prakash

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






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

[opnfv-tech-discuss] [mano-wg] Updates and discussions on Platform Build and VNF use case issues

[Prakash Ramchandran]

Hi all,

It was heartening to see debate on different view points for MANO project 
integration over OPNFV VIM by  PTLs and urgency felt by team to review 
priorities for their projects before the Intent and the Scenario and Contents 
are published for E-release.

Here is the link to summary page of meeting#22:
 https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

For MANO meeting #23 next Wednesday, if you want any topics not listed for your 
project please advice.

Thanks
Prakash


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






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

[opnfv-tech-discuss] [mano-wg] Reviewing OPNFV Release E MANO Build and Test options and usecases Meeting#23

[Prakash Ramchandran]

Hi all,

Please join for MANO WG Meeting#23 this Wednesday 3/21/2017
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111


Meeting Times: Every Wednesday (7.00 am PDT)  at 14.00 UTC

IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045



Agenda:

1.Agenda Bashing

2. Discussions & Actions on  MANO Build Options in 
Release-E<https://wiki.opnfv.org/download/attachments/6827111/MANO-Build-Options-v1.2-Release-E.pdf?version=1&modificationDate=1490143043978&api=v2>
 - Giuseppe , Yingjun , Arturt, Ulas

3. Streamlining VNF Onboarding & LCM 
Release-E<https://wiki.opnfv.org/download/attachments/6827111/MANO-Build-Options-v1.2-Release-E.pdf?version=1&modificationDate=1490143043978&api=v2>
  and Action plans - Giuseppe , Yingjun , Narinder, Sameer

4. Time permitting Use case discussions -   from Models 
Test<https://wiki.opnfv.org/display/models/Testing> and 
Samplevnf,<https://wiki.opnfv.org/display/PROJ/Technical+Briefs+of+VNFs> vOLTE 
(Opera request) - deferred for Open-O and Models co-ordination.(Pakash, Yingjun 
Li, Bryan)

5. Follow up's on items from last week.


Thanks
Prakash

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






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

[opnfv-tech-discuss] [mano-wg] OPNFV Release E Process for MANO Build and Test Meeting #24

[Prakash Ramchandran]

Hi all,

Please join for MANO WG Meeting#24 this Wednesday 3/29/2017
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111


Meeting Times: Every Wednesday (7.00 am PDT)  at 14.00 UTC

IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045



Agenda:

1. Agenda Bashing

2. Discussions and Actions on Process  aspects and API for VNF Build / Test  in 
FUNCTEST and value for Release E

refer some OPENO APIs usage / discussions
https://wiki.open-o.org/display/REL/OPEN-O+Sun+Release+Notes#OPEN-OSunReleaseNotes-APIDocumentation

3. Time permitting use case vOLTE

4. Any other items to follow up

https://wiki.opnfv.org/display/mano/OPNFV+MANO+Work+Group+Meetings

Thanks
Prakash

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






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

[opnfv-tech-discuss] Summary of todays MANO Meeting#24

[Prakash Ramchandran]

Here is the summary

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-03-29-13.57.html

Thanks

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






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

[opnfv-tech-discuss] [mano-wg] OPNFV D 1.0 MANO review and D/E TOSCA for Scenario, API + usecase discussions Meeting #25

[Prakash Ramchandran]

Hi all,

Please join MANO WG Meeting#25 this Wednesday April 5
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111


Meeting Times: Every Wednesday (7.00 am PDT)  at 14.00 UTC

IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045



Agenda:

1.Agenda Bashing

2. Q1 MANO WG 
report<https://opnfv.slack.com/files/pramchan/F4V87422K/opnfv-mano-wg-march-report>
 - Prakash

3. TOSCA for MANO scenario descriptor file from last week discussions - Bryan/ 
Narinder/ Uli

4. testing vIMS feedback from test WG - Bryan/Prakash on review in Test WG, 
Orchestra (Giuseppe), Yingjun Li(Opera),

5. Considerations for lower complexity  SBC use case based on 3-node vHello 
Tacker in Models Project (Bryan/Aimee)

6. Anything new from ONS summit at Santa Clara (April 3-6) - OPNFV Release D1.0 
news and anything on ONAP?

7. Any follow-up  from MANO WG teams like WSO2 API and  for 
Events<https://wiki.opnfv.org/display/EVNT>  Plugfest (Paris),  OpenStack 
Boston + OPNFV Beijing Summit.

Thanks
Prakash


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






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

[opnfv-tech-discuss] [mano-wg] OPNFV D 1.0 VNF testing code review and E-Release API + usecase discussions Meeting #26

[Prakash Ramchandran]

Hi all,

Please join MANO WG Meeting#25 this Wednesday April 12
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111


Meeting Times: Every Wednesday (7.00 am PDT)  at 14.00 UTC

IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045



Agenda:

1.Agenda Bashing

2. Code 
Review<https://wiki.opnfv.org/download/attachments/6827111/VNF-vIMS-testing-v1.1.xlsx?version=1&modificationDate=1491962886384&api=v2>
 report of vIMS testing in D1.0 using 
FUNCTEST<https://wiki.opnfv.org/download/attachments/6827111/Dovetail-vIMMS-VNF-test-case-information-Danube1.0.docx?version=1&modificationDate=1491962850911&api=v2>
 - Orchetsra (openbaton as Orchestrator instantiating and testing   openims) - 
Moderated by Prakash , Giuseppe & Arturt to validate..

Validate against: 
https://wiki.opnfv.org/display/dovetail/Dovetail+Test+Case+Requirements

3. TOSCA for MANO scenario descriptor file from last week discussions - Bryan/ 
Narinder/ Uli - Await inputs

4. mano - testing use cases for various vnf types - Arturt - (What will be new 
adds besides SBC?, vOLTE?, vEPC?)

5. Considerations for lower complexity  SBC<https://github.com/RestComm/sbc> 
use case based (define the use case first) on 3-node vHello Tacker in Modles 
Project (Bryan/Aimee/Prakash) - First Code Review of 3Node v Hello Tacker - 
BP<https://wiki.opnfv.org/download/attachments/6827111/blueprint.yaml?version=1&modificationDate=1491953471356&api=v2>
 + 
Start<https://wiki.opnfv.org/download/attachments/6827111/start.sh.txt?version=1&modificationDate=1491953509041&api=v2>

6. Anything new from ONS summit at Santa Clara (April 3-6) on ONAP? - Inputs 
from Attendees any?

7. Any followup  from MANO WG teams like WSO2 API  - Chintana (Updates for new 
LF API Tool<https://wiki.opnfv.org/display/INF/API+Tool> ?)

8. Events<https://wiki.opnfv.org/display/EVNT>  Plugfest (Paris),  OpenStack 
Boston + OPNFV Beijing Summit - Any updates?

9. Should MANO WG wiki be updated for ETSI 
updates<https://wiki.opnfv.org/display/PROJ/tc+minutes+20170406> -Release 2 
presented by (Pierre Lynch<https://wiki.opnfv.org/display/~dafuse>)


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






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

[opnfv-tech-discuss] [mano-wg] Meeting #27 Summary and next week plans

[Prakash Ramchandran]

Hi all,

We had our mano-wg meeting#26 today and summary is
D-Release
-  went over vIMS VNF FUNCTEST approach for qualification for Dovetail and 
concluded it not mature to proceed on that in D-release.
E-Release
- Follow up MANO TOSCA descriptor is pending inputs
- Follow up on SBC with 3-node sample vHello/ VES is in progress
- Follows ups on  Infra API Tool Port will be taken up next week
- ETSI inputs 2.0 and wiki updates deferred to next week

Other details are on link for next week Meeting#27 to follow are at
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

Thanks
Prakash

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






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

[opnfv-tech-discuss] Looking for OpenSource SBC with flexible license (Apache/BSD etc)

[Prakash Ramchandran]

Hi all,

MANO WG is looking for an Open Source SBC like https://github.com/RestComm/sbc 
but prefer a better license like Apache, BSD and may be you can suggest that is 
more flexible for SBC simple session NAT traversal across external to tenant 
and reverse SIP call control/media SDP flows.

Thanks

Prakash

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






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

[opnfv-tech-discuss] [mano-wg] E-Release discussions Meeting #27 summary and plans for next meeting

[Prakash Ramchandran]

Hi all,
Please in case we run into last minute Goto Meeting issue please try  connect 
to #opnfv-mano irc to get the alternate link used for call.
We used link   https://global.gotomeeting.com/join/391235029 instead of link  
https://global.gotomeeting.com/join/843517045.
Hope this will be fixed soon for other OPNFV meetings.

Summary of Meeting #27 discussions and  actions planned:

1.  Based on earlier E-Release plans :
a. Focus will continue to be on  VNF On-boarding and Deployment focus in OPNFV. 
(Bryan, David, Prakash)
 b. ONAP will need some time to setup and install  as part of rationalization 
process.
 c. Opera will need realignment based on the inputs from upstream ONAP 
(wiki.onap.org) for  integration efforts. - Action for Opera team to  
consolidate OPNFV  CI build and deploy aspect changes to include ONAP as NFVO.
d. Orchestra team will also use  inputs from FUCTEST VNF vIMS  On-boarding from 
 D release to see how it can expose the same to OPNFV CI Build and deploy 
aspect on the CI Dashboard.
e.  Although current ONAP is setup for  Heat  Templates and Mitaka OpenStack 
that will require change to TOSCA and Newton or later Openstack   versions as 
rationalization continues to evolve. Thus there will be more MANO build and 
test focus in Release -E.

2. ONAP Installation review (Aimee)
resource sizing:
Refer the wiki link  for vanila ONAP install - 
https://wiki.onap.org/display/DW/Resources+and+Sizing+on+vanilla+Openstack
for current Rackspace configuration refer: 
https://wiki.onap.org/display/DW/Resources+and+Sizing+on+Rackspace?src=contextnavpagetreemode
This will take few weeks to verify and test and expect some Demo at OPNFV 
Summit in China June 11-15.


Next Meeting#28 on  4/26/2017

1. Agenda Bashing
2. Inputs from  Models/Domino meeting the details on SBC using  3-node Tacker 
Hello template (Models Team/Prakash)
3. Prepare inputs  for test qualifications for selected use case  from Models. 
(Model team/Prakash)
4. Considerations in OPNFV for  ONAP API (WSO2)
5. Follow up on Action Items for Opera and Orchestra (Yingjun Li / Giuseppe 
Carella)

If you have any other inputs please provide by reply to  be included in next 
Meeting#28 on  4/26/2017 while I update the wiki page.

Thanks
Prakash



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






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

[opnfv-tech-discuss] Congratulations to Narinder Gupta as new PTL for OPNFV JOID

[Prakash Ramchandran]

Hi all,

Arthur has stepped down as  JOID PTL due to re-org in Canonical.

JOID team proposed Narinder Gupta as PTL and voted as per  OPNFV policy. and 
the record of voting are in log.
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-joid/2017/opnfv-joid.2017-04-19-16.09.log.html

Aric can you please ensure that Narinder is provided PTL access to JOID and any 
other changes we need can work out with Artur as  he wants please do needful.

 OPNFV  recognizes the excellent work done by Artur in the four releases 
starting A when idea of JOID installer was conceived by him and with help of 
Narinder he established  the diversity sought by OPNFV and wish him the best 
and please do volunteer for  OPNFV r in whatever capacity as  volunteer to the 
community.

Meanwhile I will wait for your response if on behalf of JOID team we need to 
send anything to TSC?


Plus can we fix issues with GTM dashboard both MNAO WG and JOID meeting faced 
today.

Thanks
Prakash


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






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

[opnfv-tech-discuss] [mano-wg] E-Release discussions Meeting #28 this wednesday

[Prakash Ramchandran]

Hi all,
Please join MANO WG Meeting#28 this Wednesday April 26

Meeting Times: Every Wednesday (7.00 am PDT)  at 14.00 UTC

IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

April 26th, Wednesday : 14.00 UTC /7.00 PDT  Meeting #28

1.Agenda Bashing
2. Release E  followups on MANO projects / PTLs

  *   Project PTLs inputs to E-Release content (VNF Onboarding & Deployment 
focus )
  *   Models Team SBC/vEPC usecase (MS1)- (Aimee Ukasick/Prakash) 
Models-48/49<https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=93&projectKey=MODELS&view=planning&selectedIssue=MODELS-48>
  *   Domino Team (MS1) - (Ulas/Prkash) -  Extending Publish 
RPC<https://jira.opnfv.org/browse/DOMINO-27> , HA support in 
Domino<https://jira.opnfv.org/browse/DOMINO-28> , Evaluating Support for 
kubernetes based template distribution<https://jira.opnfv.org/browse/DOMINO-29>
  *   Opera - Follow up on Action MS0+MS1  (Yingjun Li )
  *   Orchestra -  Follow up on Action MS1  (Giuseppe Carella)
  *TOSCA for MANO scenario descriptor file from past discussions - Bryan/ 
Narinder/ Uli - Await inputs
  *   Ensure add your project 
participation<https://wiki.opnfv.org/display/SWREL/Projects+Intending+to+Participate+in+the+Euphrates+Release>
  to OPNFV Euphrates (E-Release)  (MS0) with Content 
<https://wiki.opnfv.org/display/SWREL/Summary+of+Release+Plans+for+Euphrates> 
(MS1)
3. Updates for new LF API Tool<https://wiki.opnfv.org/display/INF/API+Tool> - 
Chintana (WSO2)
4. Prepare inputs  for Dovetail test 
qualifications<https://wiki.opnfv.org/pages/viewpage.action?pageId=10291560> 
for selected use case  from Models. (Model team/Prakash/)
5. Should MANO WG wiki be updated for ETSI 
updates<https://wiki.opnfv.org/display/PROJ/tc+minutes+20170406> -Release 2 
presented by (Pierre Lynch<https://wiki.opnfv.org/display/~dafuse>)
6. Events<https://wiki.opnfv.org/display/EVNT> and planning MANO issues for 
Openstack (Boston) & OPNFV(Beijing)


Thanks
Prakash

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






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

[opnfv-tech-discuss] [mano-wg] E-rlease content confirmation and mano over opnfv rationlaization planning

[Prakash Ramchandran]

Meeting Details
Meeting Times: Every Even Wednesday (7.00 am PST)  at 15.00 UTC, Other  Ad-hoc 
meeting as per Project requests
For IRC can use can use http://webchat.freenode.net/
IRC#opnfv-mano (meetbot is set for meeting minutes )

GOTOMEETING:
1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045 (in case of GTM fails join IRC 
using webchat link above and get the new GTM link)

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.
United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070
Access Code: 843-517-045
Audio PIN: Shown after joining the meeting
Meeting ID: 843-517-045

<https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111>
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

Agenda:

May 3rd, Wednesday : 14.00 UTC /7.00 PDT  Meeting #29

1.Agenda Bashing
2. Release E  followups on MANO projects plans and inputs from PTLs
  a.ONAP /Opera Readiness : Not participating in E-Release (Updates from 
Yingjun Li on what are the issues)
  b.Orchestra has committed for  Build Deploy for E-Release and two JIRA 
tickets are opened (updates from Giuseppe)
1.  
Orchestra-1<https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=163&projectKey=ORCHESTRA&view=detail&selectedIssue=ORCHESTRA-1>
2. 
Orchestra-2<https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=163&projectKey=ORCHESTRA&view=detail&selectedIssue=ORCHESTRA-2>
  c. Write a Juju charm for installing Open Baton / Test Juju charm - (other 
inputs from Narinder)
  JOID plans to support OpenStack Ocata with noSDN scenario for OpenBaton in 
release-E to start with. If ODL support for charm is added later it may 
consider that for OpenBaton at that time.
  d. Review of other projects in MANO WG that have indicated intent to 
participate in E-Release include Domino, Parser, Models and Copper
3. Discussions on Open Source SBC use case from MANO for Design and Deployment  
for Dovetail
4. Events<https://wiki.opnfv.org/display/EVNT> and planning MANO issues
Openstack 
(Boston)<https://wiki.opnfv.org/display/EVNT/OPNFV+at+OpenStack+Summit+-+Boston>
 & OPNFV(Beijing)<http://beijing%20design%20summit%20schedule/> and OPNFV 
Meetup (WSO2)<https://www.meetup.com/OPNFV-Bay-Area-User-Group/> and APIs 
(ONOS/ONAP)<https://wiki.onap.org/display/DW/APIs>
5. Continuing discussions on VNF On-boarding, Packaging  best practices (MANO 
rationalization over OPNFV)




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






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

[opnfv-tech-discuss] [mano-wg] Release E priorities and MANO Project contents addressing EUAG pain points

[Prakash Ramchandran]

Hi all,

Please Join MANO WG meeting .

Meeting Times: Every Wednesday (7.00 am PST)  at 15.00 UTC, Other  Ad-hoc 
meeting as per Project requests

For IRC can use can use http://webchat.freenode.net/

IRC#opnfv-mano (meetbot is set for meeting minutes )

OPNFV MNAO WG Meeting

GOTOMEETING

1. Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/229632485
(in case of GTM fails join IRC using webchat link above and get the new GTM 
link/ meeting number)

2. Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States (Toll Free): 1 877 309 2073
United States: +1 (312) 757-3136

Access Code: 229-632-485

Agenda:

https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111


May 10th, Wednesday : 14.00 UTC /7.00 PDT  Meeting #30

1.Agenda Bashing

2. Release E  follow-ups on MANO projects plans and inputs from PTLs

  a. ONAP/OPEN-O Harmonization plans /Opera Readiness :  E-Release (Updates 
from Yingjun Li on what are the issues for deferrals)

  b. Orchestra has committed for  Build Deploy for E-Release and two JIRA 
tickets are opened (updates from Giuseppe)

  1.  
Orchestra-1<https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=163&projectKey=ORCHESTRA&view=detail&selectedIssue=ORCHESTRA-1>
  2.  
Orchestra-2<https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=163&projectKey=ORCHESTRA&view=detail&selectedIssue=ORCHESTRA-2>

  c. Write a Juju charm for installing Open Baton / Test Juju charm - (other 
inputs from Narinder)

  d. Are projects in MANO WG  addressing EUAG Pain 
Points<https://wiki.opnfv.org/display/EUAG/Pain+Points>? Discuss Compile by 
projects what each project is doing for the same for weekly Tech meetings.

  JOID plans to support OpenStack Ocata with noSDN scenario for OpenBaton in 
release-E to start with. If ODL support for charm is added later it may 
consider that for OpenBaton at that time.

  d. Review of other projects in MANO WG that have indicated intent to 
participate in E-Release include Domino, Parser, Models and Copper

3. Discussions on Open Source SBC use case from MANO for Design and Deployment  
for Dovetail

4. Events<https://wiki.opnfv.org/display/EVNT> and planning MANO issues

Openstack 
(Boston)<https://wiki.opnfv.org/display/EVNT/OPNFV+at+OpenStack+Summit+-+Boston>
 - Reports & OPNFV(Beijing)<http://Beijing%20Design%20Summit%20Schedule> -plans 
and OPNFV Meetup (WSO2)<https://www.meetup.com/OPNFV-Bay-Area-User-Group/> and 
APIs (ONOS/ONAP)<https://wiki.onap.org/display/DW/APIs>

5. Continuing discussions on VNF On-boarding, Packaging  best practices for 
MANO rationalization over OPNFV
Thanks
Prakash


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






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

[opnfv-tech-discuss] [mano-wg] Weekly Wednesday : 14.00 UTC /7.00 PDT Meeting #31

[Prakash Ramchandran]

Hi all,
you are invited for MANO WG weekly Wednesday meeting.

Meeting Times: Every Even Wednesday (7.00 am PST)  at 15.00 UTC, Other  Ad-hoc 
meeting as per Project requests

For IRC can use can use http://webchat.freenode.net/

IRC#opnfv-mano (meetbot is set for meeting minutes )

OPNFV MNAO WG Meeting

GOTOMEETING

1. Please join my meeting from your computer, tablet or Smartphone.
https://global.gotomeeting.com/join/229632485
(in case of GTM fails join IRC using webchat link above and get the new GTM 
link/ meeting number)

2. Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States (Toll Free): 1 877 309 2073
United States: +1 (312) 757-3136

Access Code: 229-632-485

Meeting Agenda: https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111

1.Agenda Bashing

2. Release E  follow-ups on MANO projects plans and inputs from PTLs

3. Discussions on Open Source SBC use case from MANO for Design and Deployment  
for Dovetail

4. Events<https://wiki.opnfv.org/display/EVNT> and planning MANO items and 
feedbacks

Openstack 
(Boston)<https://wiki.opnfv.org/display/EVNT/OPNFV+at+OpenStack+Summit+-+Boston>
 - Reports & OPNFV(Beijing)<http://beijing%20design%20summit%20schedule/> 
-plans and OPNFV Meetup 
(WSO2)<https://www.meetup.com/OPNFV-Bay-Area-User-Group/> and APIs 
(ONOS/ONAP)<https://wiki.onap.org/display/DW/APIs>

5. Continuing discussions on VNF On-boarding, Packaging  best practices for 
MANO rationalization over OPNFV

Thanks
Prakash

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






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

Re: [opnfv-tech-discuss] [mano-wg] Weekly Wednesday : 14.00 UTC /7.00 PDT Meeting #31

[Prakash Ramchandran]

Dave,

Sure the SBC use case is more to do with future releases both for MANO and 
Dovetail. 
Trying to juggle between IRC a GTM is an art & a Craft!!! and some times we do 
mistakes.

They are not in scope as you pointed yet. May be some copy past has carried 
forward and will fix it on site.

FYI: SBC we were pursuing to simplify design over VoLTE and was to be in Models 
but since Models is not participating in E, we discuss this up in MANO as part 
of use cases and E-Release priority plus some Demo is in pipeline by Canonical 
limited to SIP call flow using VoLTE/vIMS.
 
Appreciate your Open source SBC referral and keep you updated on the NAT 
Traversal as part of SBC use case.
https://www.opensips.org/ with tools to use like RTPProxy and MediaProxy.

1. Nat Traversal using(RTPProxy) / NAT traversal capability for media streams 
from SIP user agents located behind NAT(MediaProxy)   
2. buddy lists and policy for subscriptions to presence using OpenXCAP

We have no discussions on that yet and when we bring that will keep you all 
updated.

Thanks
Prakash





Prakash Ramchandran
 R&D 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






-Original Message-
From: Dave Neary [mailto:dne...@redhat.com] 
Sent: Wednesday, May 17, 2017 9:44 AM
To: Prakash Ramchandran; mano...@lists.opnfv.org
Cc: 'TECH-DISCUSS OPNFV'
Subject: Re: [opnfv-tech-discuss] [mano-wg] Weekly Wednesday : 14.00 UTC /7.00 
PDT Meeting #31

Hi Prakash,

On 05/16/2017 02:06 PM, Prakash Ramchandran wrote:
> Meeting Agenda: https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111
> 
> 1.Agenda Bashing
> 
> 2. Release E  follow-ups on MANO projects plans and inputs from PTLs
> 
> 3. Discussions on Open Source SBC use case from MANO for Design and
> Deployment  for Dovetail

I'm curious what the overlap between an SBC use-case for MANO and
Dovetail. I believe at least today, MANO and VNFs are out of scope for
Dovetail. What is the objective of this discussion point?

Thanks,
Dave.

> 4. Events <https://wiki.opnfv.org/display/EVNT> and planning MANO items
> and feedbacks
> 
> Openstack (Boston)
> <https://wiki.opnfv.org/display/EVNT/OPNFV+at+OpenStack+Summit+-+Boston>
> - Reports & OPNFV(Beijing)
> <http://beijing%20design%20summit%20schedule/> -plans and OPNFV Meetup
> (WSO2) <https://www.meetup.com/OPNFV-Bay-Area-User-Group/> and APIs
> (ONOS/ONAP) <https://wiki.onap.org/display/DW/APIs>
> 
> 5. Continuing discussions on VNF On-boarding, Packaging  best practices
> for MANO rationalization over OPNFV
> 
>  
> 
> Thanks
> 
> Prakash
> 
>  
> 
> *Prakash Ramchandran*
> 
> logo_huawei* R&D USA*
> 
> *FutureWei Technologies, Inc*
> 
> Email:prakash.ramchand...@huawei.com <mailto:s.c...@huawei.com>
> 
> Work:  +1 (408) 330-5489
> 
> Mobile:+1 (408) 406-5810
> 
> 2330 Central Expy, Santa Clara, CA 95050, USA
> 
>   
> 
> / /
> 
> / /
> 
>  
> 
>  
> 
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> 

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Can we add IPv6 Danube testing proposal for this Weekly Thursday : 13.00 UTC /6.00 PDT

[Prakash Ramchandran]

Bin,

Can we add the IPv6 test proposal review on link for Danube Dovetail  testing 
at this week's Tech meeting on Thursday?
https://wiki.opnfv.org/display/ipv6/Release+D+Tests+for+%28CVP%29+Danube+-+Proposal

If there is any submits to make to Git/Gerrit or already made please point out 
for the test suit included on the wiki link above.


Thanks
Prakash

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






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

Re: [opnfv-tech-discuss] Can we add IPv6 Danube testing proposal for this Weekly Thursday : 13.00 UTC /6.00 PDT

[Prakash Ramchandran]

Hi all,

Just noticed the link in Dovetail  meeting note on 5/19 on the IPv6 test area 
patch in Dovetail

 https://gerrit.opnfv.org/gerrit#/c/34577/

and this has the updated patch with API, you can drop my request.

Thanks
Prakash

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






From: Prakash Ramchandran
Sent: Monday, May 22, 2017 11:33 AM
To: 'TECH-DISCUSS OPNFV'
Subject: [opnfv-tech-discuss] Can we add IPv6 Danube testing proposal for this 
Weekly Thursday : 13.00 UTC /6.00 PDT

Bin,

Can we add the IPv6 test proposal review on link for Danube Dovetail  testing 
at this week's Tech meeting on Thursday?
https://wiki.opnfv.org/display/ipv6/Release+D+Tests+for+%28CVP%29+Danube+-+Proposal

If there is any submits to make to Git/Gerrit or already made please point out 
for the test suit included on the wiki link above.


Thanks
Prakash

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






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

Re: [opnfv-tech-discuss] Can we add IPv6 Danube testing proposal for this Weekly Thursday : 13.00 UTC /6.00 PDT

[Prakash Ramchandran]

Hi all,

Based on inputs obtained  from patch set submitted and IPv6 co-ordinations 
efforts, the Downloadable test file modified as v1.1 and a suggested CVP report 
is updated to link under Downloads.

https://wiki.opnfv.org/display/ipv6/Release+D+Tests+for+%28CVP%29+Danube+-+Proposal

Thanks
Prakash

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






From: HU, BIN [mailto:bh5...@att.com]
Sent: Monday, May 22, 2017 2:53 PM
To: Prakash Ramchandran; 'TECH-DISCUSS OPNFV'
Subject: RE: [opnfv-tech-discuss] Can we add IPv6 Danube testing proposal for 
this Weekly Thursday : 13.00 UTC /6.00 PDT

Thank you Prakash for your great work, and keeping us updated.

So there is no need to discuss it on Thursday.

Thank you again
Bin

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Prakash 
Ramchandran
Sent: Monday, May 22, 2017 2:39 PM
To: Prakash Ramchandran ; 'TECH-DISCUSS OPNFV' 

Subject: Re: [opnfv-tech-discuss] Can we add IPv6 Danube testing proposal for 
this Weekly Thursday : 13.00 UTC /6.00 PDT

Hi all,

Just noticed the link in Dovetail  meeting note on 5/19 on the IPv6 test area 
patch in Dovetail

 https://gerrit.opnfv.org/gerrit#/c/34577/

and this has the updated patch with API, you can drop my request.

Thanks
Prakash

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






From: Prakash Ramchandran
Sent: Monday, May 22, 2017 11:33 AM
To: 'TECH-DISCUSS OPNFV'
Subject: [opnfv-tech-discuss] Can we add IPv6 Danube testing proposal for this 
Weekly Thursday : 13.00 UTC /6.00 PDT

Bin,

Can we add the IPv6 test proposal review on link for Danube Dovetail  testing 
at this week's Tech meeting on Thursday?
https://wiki.opnfv.org/display/ipv6/Release+D+Tests+for+%28CVP%29+Danube+-+Proposal

If there is any submits to make to Git/Gerrit or already made please point out 
for the test suit included on the wiki link above.


Thanks
Prakash

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






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

[opnfv-tech-discuss] [mano-wg] Weekly Wednesday : 14.00 UTC /7.00 PDT Meeting #32

[Prakash Ramchandran]

Meeting Times: Every  Wednesday (7.00 am PST)  at 15.00 UTC, Other  Ad-hoc 
meeting as per Project requests

For IRC can use can use http://webchat.freenode.net/

IRC#opnfv-mano (meetbot is set for meeting minutes )

OPNFV MNAO WG Meeting

GOTOMEETING

1. Please join my meeting from your computer, tablet or Smartphone.
https://global.gotomeeting.com/join/229632485
(in case of GTM fails join IRC using webchat link above and get the new GTM 
link/ meeting number)

2. Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States (Toll Free): 1 877 309 2073
United States: +1 (312) 757-3136

Access Code: 229-632-485



Meeting Agenda: https://wiki.opnfv.org/pages/viewpage.action?pageId=6827111


1.Agenda Bashing (Action Item review from last week)
2. Release E  follow-ups on MANO projects plans and inputs from PTLs
Containers for Build and Deploy in Orchestra/Opera
3. MNAO WG -considering on focus areas to in facilitating Delivering E release 
priority & plan for F
4. Events and other feedbacks on Action Items closed or to close.
Details on Agenda link above.

Thanks
Prakash



Thanks

Prakash


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






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

[opnfv-tech-discuss] [mano-wg] meeting#32 irc summary and plan for meeting#33

[Prakash Ramchandran]

Hi all,
Here is minutes of mano-wg meeting#32

We have closure on several action items and propose to keep foucs to Orchestra, 
Domino, Parser, Installers  for Build nfvo/vnfm using containers 
/formats/packaging and VNF oboarding best practices needed for release E and 
rest for release F.

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-mano/2017/opnfv-mano.2017-05-24-13.58.html

Next week if you have topics in scope of mano-wg  send across and if we need to 
move to irc only or alternate GTM will update by next Monday.
refer link: https://wiki.opnfv.org/display/mano/OPNFV+MANO+Work+Group+Meetings

plan for...

May 31st, Wednesday : 14.00 UTC /7.00 PDT  Meeting #33

1.Agenda Bashing

2. Containers Packaging and On-boarding considerations for nfvo and vnfm + 
common practices checklist to consider

3. MNAO WG - focus areas to  facilitate Delivering E release priority & plan 
for F

4. China Summit preparation by  MANO projects and any presentation/ feedback 
for speakers.

Thanks
Prakash

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






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

[opnfv-tech-discuss] [mano-wg] irc only meeting and plan for meeting#33 on Wednesday 31st at 14 UTC

[Prakash Ramchandran]

IRC only meeting #opnfv-mano


May 31st, Wednesday : 14.00 UTC /7.00 PDT  Meeting #33

1.Agenda Bashing

2. VNF Packaging and On-boarding considerations for nfvo and vnfm + common 
practices checklist to consider

3. MNAO WG - focus areas to  facilitate Delivering E release priority & plan 
for F

4. China Summit preparation by  MANO projects and any presentation/ feedback 
for speakers


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






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