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 work, or find someone (possibly the projects actual contributors) to do that work. This is analogous to a vendor who agrees to support their vnf in the use cases we use them for.
Thanks, Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: [email protected] [mailto:[email protected]] On Behalf Of SULLIVAN, BRYAN L Sent: Thursday, June 01, 2017 10:31 AM To: SPATSCHECK, OLIVER <[email protected]>; Zhou, Danny <[email protected]> Cc: onap-discuss <[email protected]>; [email protected] Subject: Re: [onap-discuss] [onap-tsc] Call for vCPE VNFs proposals ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Having support info in the table of open source VNFs, as well as notes on functional limitations / fitness for a particular purpose, and some consensus assessment [limited, viable] or status [experimental, lab-ready, deployed] that can change over time, would be useful. There are various types/levels of purpose here, and for the community’s need, functionally complete / production-ready open source VNFs while clearly a desired goal, are a would-be-nice. Viability would include the level of community support for maintaining or further developing the VNF. But some VNFs may be still be viable for particular purposes (e.g. in tests for performance or lifecycle automation) even if they are incomplete or there is no active community. Thanks, Bryan Sullivan | AT&T From: SPATSCHECK, OLIVER Sent: Thursday, June 01, 2017 6:07 AM To: Zhou, Danny <[email protected]<mailto:[email protected]>> Cc: SULLIVAN, BRYAN L <[email protected]<mailto:[email protected]>>; KLUGER, YOAV <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; onap-discuss <[email protected]<mailto:[email protected]>> Subject: 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 commercial VNFs this support will be provided by the vendor. However, for open source VNFs we need volunteers to take on that role. I would track those on the Wiki or identify them as gaps. If we can’t find that support we can’t use that VNF. Thx Oliver On May 31, 2017, at 11:36 PM, Zhou, Danny <[email protected]<mailto:[email protected]>> wrote: The wiki page<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Use-2BCase-253A-2BResidential-2BBroadband-2BvCPE&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2-FskNSRL5sc9nQutgafCDIk3JbYrtcUwMwT5Zs1Tnk&m=Y6oSqusd5waa24F38QbqX5Q7z4FxBvAQy3WAxeNdz2E&s=QPIvHP7_JFzDMiX8sdebViT7Y8GADNDb_lq2G0otif0&e=> already lists preferred and usable open source VNFs like below, but the ONOS vBNG as open source vBNG and OpenWRT as open source vHGW does not make sense to me. Specifically, the ONOS vBNG is essentially a L3 NAT without the capabilities to address requirement such as session management, traffic aggregation and routing, etc., and in addition to OpenWRT acting as vHGW, VPP based high performance Home Gateway<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.fd.io_view_VPP_VPP-5FHome-5FGateway&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4&m=S8WnofRTLquCoooSWMs6VppfiPsKgSASeuqb2NassTM&s=nZY_T4pjVyyFucKeg0ijm68LJm5NaaF46RQY48VPSQM&e=> as well asvRouter<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.fd.io_view_VPP-5FSandbox_router&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4&m=S8WnofRTLquCoooSWMs6VppfiPsKgSASeuqb2NassTM&s=MPD8ZLXRaBDF8Nx2xexNTaR8uFKEDBJqPAABHk4TcAU&e=> should be better. * vDHCP: ISC DHCP * vDNS: ISC Bind * vAAA: FreeRADIUS -Danny Zhou Intel From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of SULLIVAN, BRYAN L Sent: Thursday, June 1, 2017 3:36 AM To: KLUGER, YOAV <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; onap-discuss <[email protected]<mailto:[email protected]>> Subject: Re: [onap-tsc] Call for vCPE VNFs proposals I recommend that any available open source implementations of these VNFs also be included. I am aware of several potential VNFs as used in the R-CORD project, and as being collected through the similar ODL VCO (Virtualized Central Office) project. These are being collected and assessed for deployment on OPNFV reference platforms as part of the proposed “Edge” project: https://wiki.opnfv.org/display/PROJ/Multi-Access+Edge<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_display_PROJ_Multi-2DAccess-2BEdge&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4&m=S8WnofRTLquCoooSWMs6VppfiPsKgSASeuqb2NassTM&s=pMPlFX7WiLZPIsWgpgL_uX8D9TNoYhXk3zlKzR_Wbsw&e=> intended to expand reference VNF options for edge-focused service deployments such as residential broadband. As a part of this project we will also be building reference blueprints (TOSCA based) for these VNFs and orchestrating them using ONAP components as well as other projects we are currently using for this in OPNFV (Cloudify, and OpenStack Tacker). OPNFV is acquiring the necessary hardware (e.g. OLT devices) to have a fully-functional edge-focused lab environment in which to complete this integration. I’ll add the related info to the ONAP wiki as the usability of the open source VNFs becomes clear. Thanks, Bryan Sullivan | AT&T From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of KLUGER, YOAV Sent: Wednesday, May 31, 2017 12:23 PM To: [email protected]<mailto:[email protected]>; onap-discuss <[email protected]<mailto:[email protected]>> Subject: [onap-discuss] Call for vCPE VNFs proposals Dear ONAP community, As we all know, the Residential Broadband vCPE use case is one of our two targeted use cases for R1. Its wiki page<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Use-2BCase-253A-2BResidential-2BBroadband-2BvCPE&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2-FskNSRL5sc9nQutgafCDIk3JbYrtcUwMwT5Zs1Tnk&m=Y6oSqusd5waa24F38QbqX5Q7z4FxBvAQy3WAxeNdz2E&s=QPIvHP7_JFzDMiX8sdebViT7Y8GADNDb_lq2G0otif0&e=> has been significantly enriched recently, and more details are added on a daily basis. A general residential broadband solution can be much more complex than what would be reasonably achievable by R1. We have narrowed down the description of the use case for R1, to something that should be both achievable and usable. For the use case to work the following VNFs will be needed: * vBNG * vHGW * vDHCP * vDNS * vAAA In addition a simple hardware box with 802.1ad capabilities will be needed. This is a call for vendors of such VNFs and/or such a box to join the activity. Would be great if by Beijing time the wiki will have at least one vendor name alongside every VNF, and also at least one vendor for the box. Thanks, Yoav Kluger Amdocs Technology +1(201)912-7294 +972-54-4850278 <image001.jpg> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2-FskNSRL5sc9nQutgafCDIk3JbYrtcUwMwT5Zs1Tnk&m=Y6oSqusd5waa24F38QbqX5Q7z4FxBvAQy3WAxeNdz2E&s=4DsjLuum5-WDdGQllWAreUo_BzbuxLSg0nGK7t4a7Ls&e=> _______________________________________________ ONAP-TSC mailing list [email protected]<mailto:[email protected]> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4&m=S8WnofRTLquCoooSWMs6VppfiPsKgSASeuqb2NassTM&s=7r4GcoAS9niUJg2CajGClIJqPwvGUi_suVhbtA_U_hA&e=
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
