Hi Mazin, Thanks for the replay. All the points and requirements in your replay below make a lot of sense, and should address the use of commercial VNFs in R1, but what about the use of commercial infrastructure (NFVI+VIM) as part of R1? The VNFs need to run on an infrastructure?
I see that the same rules should be applied to the usage of commercial infrastructure. What is the TSC thinking about this? Best regards, Gil Hellmann From: "GILBERT, MAZIN E (MAZIN E)" <ma...@research.att.com> Date: Friday, June 2, 2017 at 7:50 AM To: Dhananjay Pavgi <dp00476...@techmahindra.com>, "onap-tsc@lists.onap.org" <onap-tsc@lists.onap.org> Cc: Rajesh Gadiyar <rajesh.gadi...@intel.com>, Gil Hellmann <gil.hellm...@windriver.com> Subject: Re: [onap-tsc] Usage of commercial VNF and NFVI+VIM solutions for ONAP R1 use cases, and open lab Gil, Thanks for the kind words regarding the ONAP community. Let me make sure I respond to your question and put this subject to rest as it was discussed numerous times by the TSC. 1. Our first integrated release (ONAP seeded by ECOMP and Open-O) will be the first week of Nov. This is our goal and the TSC community is committed to this. 2. Two broad sets of services have been identified for vetting the integrated release; vEPC/VoLTE and vCPE 3. Each broad use case will have options of open source VNFs and several commercial VNFs. 4. It is our desire to use commercial VNFs if we can make our release date; otherwise we will revert to Open Source. This means a. licenses are available in time that is aligned with our release planning, b. VNFs can be stood up in the ONAP OpenLabs in time that align with our release. c. Developers get complete support during testing, dev and certification d. VNF vendors are willing to further extend their VNFs to meet our ONAP VNF requirements for R1. I encourage VNF vendors who are interested in meeting those guidelines to sign up on our wiki asap. The TSC is excited about the first release and look forward to working with the entire community to make this a huge success. Thanks mazin On Jun 2, 2017, at 12:27 AM, Dhananjay Pavgi <dp00476...@techmahindra.com<mailto:dp00476...@techmahindra.com>> wrote: +1. For lab having commercial ecosystem of VNFs; we may consider Tech Mahindra’s VNFXchange lab. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 <image007.png> <image008.jpg> www.techmahindra.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=JJfoYB5IShRfFveCly_uZ8d7ons9K9DaPdtaeHiM7AE&s=3kwlLzHQQZr3XBY9-Sjyu249Z17L5q0sl52GUontqac&e=> Platinum Member. Visit : http://www.onap.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.onap.org_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=JJfoYB5IShRfFveCly_uZ8d7ons9K9DaPdtaeHiM7AE&s=KHvnBPypJNu4lcmdaBMwnSj0fNf__O-rH5PgJ2tk3oE&e=> From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Gadiyar, Rajesh Sent: Friday, June 02, 2017 2:48 AM To: Hellmann, Gil (Wind River) <gil.hellm...@windriver.com<mailto:gil.hellm...@windriver.com>>; onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> Subject: 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: <onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>> on behalf of Gil Hellmann <gil.hellm...@windriver.com<mailto:gil.hellm...@windriver.com>> Date: Thursday, June 1, 2017 at 2:08 PM To: "onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> Subject: [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 open lab / integration in release 1 or should it be strictly limited to use only open source. I would suggest that the TSC will consider the following before making a decision: As it was agreed by both the TSC and the wider ONAP community, using real life use case like the proposed VoLTE and vCPE use cases for release 1 is very important to ensure that ONAP is built from day 1 in a way that will provide close implementation to a real-life use case which can provide proper foundation to use ONAP in commercial deployment, and implementation of real life use case can have a great contribution to the success of this project. ONAP as orchestration / MANO project require NFVI+VIMs (clouds) to run on, and VNFs to run to create the services. The use of commercial NFVI+VIMs and VNFs for the use case implementation and open lab / integration can have a big positive impact on our ability to be as close as possible to a real-life usage scenario. Limiting the usage *to only open source* solutions will limit dramatically the ability to get there. Not saying we should not use open source VNFs and NFVI+VIMs, but I hope we wouldn’t limit ourselves to only open source VNFs & NFVI+VIM in the open lab / integration lab and for the release 1 use cases, same like we would not limit yourself to only use open source hardware. I hope this can be considered, and thanks for your consideration. Regards, Gil Hellmann, VP - Solutions Readiness direct 289.553.5815 mobile 905.409.6878 skype ID gil.hellmann <image009.png><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.windriver.com_email_sigs_blog-2Dnetwork.html&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=JJfoYB5IShRfFveCly_uZ8d7ons9K9DaPdtaeHiM7AE&s=4iCw0y9xR7JnRZiplXeiSIRaMh4HL0mhYJw1Pp0EuHs&e=> <image010.png><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_company_wind-2Driver&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=JJfoYB5IShRfFveCly_uZ8d7ons9K9DaPdtaeHiM7AE&s=m2qx_D5EsveCAP3c5Wfrocaw_38nnsNIX8NuM9BiPqU&e=> <image011.png><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.windriver.com_email_sigs_facebook.html&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=JJfoYB5IShRfFveCly_uZ8d7ons9K9DaPdtaeHiM7AE&s=i9_yZN12s15jROwYjyW2cD7yql5FoUjZP39neC3cLqU&e=> <image012.png><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.windriver.com_email_sigs_twitter.html&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=JJfoYB5IShRfFveCly_uZ8d7ons9K9DaPdtaeHiM7AE&s=N4z2kmnRDcVrogadA4l8pli_4MLo29Ph9ZgchgxShK0&e=> <image013.png><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.windriver.com_email_sigs_youtube.html&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=JJfoYB5IShRfFveCly_uZ8d7ons9K9DaPdtaeHiM7AE&s=ApZzaLKXwn5QVoy9wY8AZ7UkihHBc9hae3lTXVRrhVM&e=> <image014.gif><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.windriver.com_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=JJfoYB5IShRfFveCly_uZ8d7ons9K9DaPdtaeHiM7AE&s=5UJqs7d94NytP3QcMWI3m-U4vQfTYJgJk0AEfJ6d84A&e=> “If you will it, it is no dream.” Theodor Herzl “If you want to go fast, go alone. If you want to go far, go together.” An old African proverb “The only way to avoid making mistakes is not to do anything. And that.. will be the ultimate mistake” Goh Keng Swee ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_Disclaimer.html&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=JJfoYB5IShRfFveCly_uZ8d7ons9K9DaPdtaeHiM7AE&s=bzRIwYIjNGWjdiLA9seJtTh3GF_Mtp-JqAlaP4chTDs&e=> externally http://tim.techmahindra.com/tim/disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__tim.techmahindra.com_tim_disclaimer.html&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=JJfoYB5IShRfFveCly_uZ8d7ons9K9DaPdtaeHiM7AE&s=j50zxKCl2AmkcZW_XvrrqJnp_wYy8Oiu-J9Mm3ikgwY&e=> internally within TechMahindra. ============================================================================================================================ _______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=JJfoYB5IShRfFveCly_uZ8d7ons9K9DaPdtaeHiM7AE&s=uQFarZjdTImPulsbGfq4M1mk-Vv7bCAMTHSjz-Bwgog&e=
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
