Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP R1 use cases, and open lab

+1. For lab having commercial ecosystem of VNFs; we may consider Tech Mahindra’s VNFXchange lab. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com

Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions forONAP R1 use cases, and open lab

Dear Mazin, I understand that "VNF Requirements" project is meant for the same. I propose that we make a Generic Requirements (GR) document covering all aspects and interfaces including FCAPS. The document shall be version controlled and will mature alongside ONAP. While on boarding test/demo

[onap-tsc] Use case subcommittee

Hi all, Yesterday we approved creation of Use case subcommittee. I propose to have bi-weekly conference calls, starting after next week’s f2f meeting. I will ask Linux Foundation to send out invitation and create wiki page for this subcommittee. Best regards, Alla Goldner Open Network

Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions forONAP R1 use cases, and open lab

Team, I will put together a set of expectations for ONAP to consider commercial VNFs in R1 or future releases. We can then discuss and have them vetted by the TSC. Having access to the VNF in a testing lab with continuous support is necessary but not sufficient. We need to ensure that VNFs

Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP R1 use cases, and open lab

For an open source community, the use of proprietary software in the production of the platform (including tools, NFVI platforms, or VNFs used as use cases for developing the platform in open labs), or as part of the released platform, takes the project into a tricky space. It will complicate

Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP R1 use cases, and open lab

+1 I was taking this as a given. We need a robust vendor/commercial ecosystem of VNFs and NFVI software, in addition to open source. I see that the vCPE and vVoLTE use case documents on the wiki already incorporate this; which I am supportive. From: on behalf

[onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP R1 use cases, and open lab

Dear TSC members, It is very exciting to see the great momentum and grow in the ONAP community, I hear that there is different opinion / debate with regard to whether release 1 of ONAP should be using commercial VNFs & NFVI+VIM’s solutions for the implementation of the proposed use cases and

[onap-tsc] Community Meetings

The ONAP Community now has 8 Zoom licences available. If you are hosting a community meeting, please allow me to migrate the meeting to these community accounts. If you can, please forward me the Meeting Time and recurrence schedule (if there is one), Meeting Title, and a list of participants OR

Re: [onap-tsc] Call for vCPE VNFs proposals

Viability to even be included is certainly an important point. But I think oliver’s point is there is always some work to get a vnf to be onap ready, and then some more work to configure it to work in our use case. Someone in the ONAP project has to take ownership and agree to either do that

[onap-tsc] tsc merting

dear all, i will not be able to attend the tsc today. But jamil will attend for me, with eric and vincent. Roberto _ Ce message et ses pieces jointes peuvent contenir des

Re: [onap-tsc] Call for vCPE VNFs proposals

Could we also start listing who is supporting the open source VNFs? E.g. even the simple open source based VNFs we are using for the current ONAP demo based on the seed code took a couple of people 2 months or so to get to work properly in the integration environment. I would assume that for

[onap-tsc] Common Frameworks - Project Proposal

Hello Committee Members, I would like to submit the following project proposal: https://wiki.onap.org/display/DW/Common+Frameworks?src=contextnavpagetreemode This project is a consolidation of several other common projects that were already introduced to this committee Thanx, Liron This