Dhananjay
Good use cases but Hope you are thinking only at the functional interaction . You are not thinking about -- Performance and Capacity view . As I see the use case driving the Release Content and goal of ONAP . I had couple of question . Do we have any concrete definition w.r.t to a VNF . VNF to VF Relationship .( is it 1:n or m:n ) and VF to Controller Mapping .for example (SDNC and APPC/VNF-C) Why I am asking is For example for the demo use case of - vFW/vDNS - I am still not able to connect dots in terms of why some ONAP component interaction is needed when everything looks to be preloaded /preconfigured as per the Demo Flow . Thanks in advance to clarify . with best regards gaurav ________________________________ From: [email protected] <[email protected]> on behalf of Alla Goldner <[email protected]> Sent: 21 July 2017 22:55 To: Dhananjay Pavgi; [email protected] Cc: [email protected]; onap-tsc Subject: Re: [onap-tsc] R2 use cases Hi Dhananjay, Thanks for your inputs! Please provide your suggested use cases under https://wiki.onap.org/display/DW/Release+2+Use+Cases<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Release-2B2-2BUse-2BCases&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=ATTgafIHYzOQf6JXLijsPu7rLnfRLJjkxWEUIpbraA4&s=I8WwmYUld5cA0UcFBfdgvVbpiMt2tZg5uEsW0aXHgr8&e=> For Enterprise vCPE use case extensions, I would suggest to work directly with Long (China Telecom) who provided the initial Enterprise vCPE use case proposal. Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:[email protected]] From: Dhananjay Pavgi [mailto:[email protected]] Sent: Friday, July 21, 2017 8:09 PM To: Alla Goldner <[email protected]>; [email protected] Cc: onap-tsc <[email protected]>; [email protected] Subject: RE: R2 use cases Thanks, Alla. Suggest that we consider following use cases : 1. Enterprise vCPE with integration with upstream BSS/Ordering system. [Note : we need to showcase as to how ONAP works with TMF Open APIs and also would be good to showcase Microservice Bus to accommodate existing BSS/OSS eco-system] 2. Consider one umbrella MPLS-VPN connectivity for Enterprise customer (something like BIS) as a Product and show how ONAP provides modularity and reusability at product component level. i. E.g. L2VPN : ELAN Port Based, ELAN VLAN Based, ELINE Port Based, ELINE VLAN Based. ii. L3VPN iii. Priority L2VPN (with QoS) iv. Priority L3VPN (with QoS) 3. Let us realize any of the use case in the list in below email (a thr’ e) by having 2 or more VNFs residing across hybrid Telco Cloud e.g. one VNF on Mirantis Openstack and others on vanilla Opensack/VMWare etc. [Note : This will help us elucidate Multi-VIM support] thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:[email protected]] [ONAP_logo_Sig] www.techmahindra.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=ATTgafIHYzOQf6JXLijsPu7rLnfRLJjkxWEUIpbraA4&s=LVqDH8VSUH_7FBtaSauwOXAsp4e7u8UKuBYPHej-Twc&e=> Platinum Member. Visit : http://www.onap.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.onap.org_&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=ATTgafIHYzOQf6JXLijsPu7rLnfRLJjkxWEUIpbraA4&s=ngJL1XqHJe-CDfuxdYcth-3LHjMGViNPjYNoZx4AT0o&e=> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Alla Goldner Sent: Friday, July 21, 2017 9:07 PM To: [email protected]<mailto:[email protected]> Cc: onap-tsc <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: [onap-tsc] R2 use cases HI all, Our major objective right now is to keep on track and finalize R1 use cases definitions. Having said that, I strongly believe we should work in parallel on R2 use cases. If you look on the flow below, ideally we should target completion of step 6 when Release starts, in order for project teams to deliver their functionality on time. That means we should be able to come up with our R2 use cases initial proposal by September f2f meeting – this would leave sufficient time to iterate with projects and, hopefully, enough time for architecture subcommittee for their related work. Please start including your R2 use cases proposals under https://wiki.onap.org/display/DW/Release+2+Use+Cases<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Release-2B2-2BUse-2BCases&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=ATTgafIHYzOQf6JXLijsPu7rLnfRLJjkxWEUIpbraA4&s=I8WwmYUld5cA0UcFBfdgvVbpiMt2tZg5uEsW0aXHgr8&e=> - we may have an opportunity to review them next week during our Virtual meeting. Right now, the list of potential proposals includes: * Network Function Change Management (agreed to reword as use case and move under R2) * Enterprise vCPE (agreed to move under R2, revision was presented during the last use case subcommittee meeting) * SD-WAN ? * SD-LAN ? * 5G ? i. RAN deployment ii. E2E Network Slicing iii. Mobile Edge Computing And proposal for usage of EPA technology across a different R2 use cases. Use case subcommittee flow: 1. Use case subcommittee discuses new use cases 2. Use case subcommittee produces use case flow diagrams, provides its view on the foreseen modules introductions/modifications and suggests potential PNFs / VNFs 3. Use case subcommittee gets feedback from the potentially effected projects including integration team on feasibility 4. Iterate back to 2 5. TSC approves the use case 6. In case a new modules or a new functionality to existing modules or a new APIs introduction is foreseen, architecture subcommittee defines the new/modified ONAP flows and the interfaces principles, based on the approved use cases (1) 7. Projects define their extended functionality and their external APIs, following those principles. 8. Detailed per-component flows are defined by the projects and projects write their user stories / implement them; Integration team continuously works with Use case subcommittee to accompany the use case development, review epics/user stories, answer questions, etc. Use case subcommittee behaves as system engineers for the use case through test start date 9. Integration team defines the gating use case based on step 8 and finalizes the PNFs / VNFs selection, with the help of use case subcommittee, architecture subcommittee, PTLs of a different ONAP projects 10. TSC approves the gating use case 11. Integration project leads (coordinates) effort to get the gating use case tested, repaired, and verified, and the results are documented. (1) The defined functional extensions should be as generic as possible to allow re-use of it by additional use cases. Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:[email protected]] 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=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=ATTgafIHYzOQf6JXLijsPu7rLnfRLJjkxWEUIpbraA4&s=vevXFlywXD-ZBbd3Ijn6AWh4jfbC1uA_v7q4G6vg6uE&e=> ============================================================================================================================ 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=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=ATTgafIHYzOQf6JXLijsPu7rLnfRLJjkxWEUIpbraA4&s=ZgAI6o93rT1bwqj_R-CbBhoRnmpjXgIKMLN_71qpEeM&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=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=ATTgafIHYzOQf6JXLijsPu7rLnfRLJjkxWEUIpbraA4&s=qur-7DXVzCPkE_TkV9-Q1BFPuWw7JuddNO_TIvJx7-k&e=> internally within TechMahindra. ============================================================================================================================ 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=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=ATTgafIHYzOQf6JXLijsPu7rLnfRLJjkxWEUIpbraA4&s=vevXFlywXD-ZBbd3Ijn6AWh4jfbC1uA_v7q4G6vg6uE&e=>
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
