Alla, Team Agree with the discussion below that the goal of R1 has been on integration of Open-O with Open ECOMP. One of the key goals for R2 should be maturing the platform to an “enterprise” grade, specifically the non-functional aspects. We should have measures and frameworks that evaluate those measures so we track progress.
Another key goal of R2 should be to create additional platform capabilities that can promote self-service of the platform. I.e., we may not develop many new applications for R2, but with R2, the user community should be able to develop a number of new applications that require new VNF instantiation, micro services on-boarding and closed loop automation with no development. Very exciting discussion topic. Let’s organize and plan to reach a conclusion at the F2F meeting in Sep. Mazin On Aug 18, 2017, at 7:27 AM, Alla Goldner <alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>> wrote: Hi Vladimir, all, Thanks for all replies received so far! Vladimir, this is not about meeting time resources, I believe. Meeting time can be extended, if necessary. The limitation and the need to reduce the scope comes from the fact that different projects will have to support related functionality, Integration team will have to do all integration work around approved use cases etc. R1 major goal, as Mazin mentioned yesterday, is about merging Openecomp and Open-O code and we decided that the best way to achieve this goes though implementing R1 use cases. However, we compromised on ONAP Platform functionalities – some of them appear on the dedicated wiki page already, some more will be included by the community members. And, as also appears in my presentation yesterday “- Issue of the technical debt we are acquiring in R1 and how to pay that off • If we load R2 at 100% capacity with new features this may never get cleaned up and ONAP may eventually collapse under its own complexity.” When we develop a use case it typically consists of 2 different aspects: 1. New ONAP platform capabilities 2. New functionality related to specific use case, including connectivity support, support of new VNFs etc. For example, if we were guided to concentrate on ONAP Platform capabilities only, we then would support R2 with R1 only use cases by implementing ONAP Platform capabilities missing in R1, and by also aligning this with R2 target architecture view. As clearly, (2) above requires additional effort. This, I guess, goes back to the question asked by Jason on R2 goal – and, also in my view, as Jason put it, “R2 would be about strengthening the non-functional aspects of the platform (usability, maintainability, scalability, reliability, etc.) to provide an unrivaled, hardened platform that can be leveraged in any carrier's environment.” And, yet another example, if we agree to decide on case-by-case basis, as proposed by Vladimir and by Rajesh, we need criteria on how we select to support use cases/missing Platform capabilities. And Ranny provided a great list of initial criteria to be used for this goal, if we decide to go in this direction. We are looking for more inputs on this, as this will eventually determine the direction R2 takes. Best regards, Alla Goldner Open Network Division Amdocs Technology <image001.png> From: Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com] Sent: Friday, August 18, 2017 12:43 PM To: Jason Hunt <djh...@us.ibm.com<mailto:djh...@us.ibm.com>>; Alla Goldner <alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>> Cc: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> Subject: RE: [onap-tsc] R2 use cases planning Jason, Alla and All Just to understand the topic, what is this resource that should be managed here; is it e.g. meeting time? Speaking of the #1 below, I understand it as that some ONAP platform capabilities are missing so that the agreed R1 use cases cannot be supported. If this is the case, the gap certainly should be closed, but it’s R1 work item, isn’t it? One therefore can expect that there will be R1 related activities (“R1 work items”) and R2 related activities (“R2 work items”) with some resource partitioning between them. Speaking of R2 related activities, we certainly need some selection of use cases, but I think it should go on case by case basis: importance, complexity of new platform capabilities needed (if any), timeline etc. Thanks Vladimir From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Jason Hunt Sent: Thursday, August 17, 2017 10:16 PM To: Alla Goldner <alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>> Cc: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> Subject: Re: [onap-tsc] R2 use cases planning Alla, Thank you for your leadership here and for the work of the use case committee on this topic. ONAP should be able to run any VNF or network service, even ones that aren't known today. And, just as importantly, ONAP needs to manage those VNFs and network services well, in a number of various carrier environments. As you've outlined, the question is how we balance those two items. I agree with all of your points below -- that R2 should be focused on improving the ONAP platform capabilities & only supporting new use cases where they are built on existing ONAP functionality. If the community agrees with this approach, I think we want to be cautious about how we present the release's goal externally. This may require some help from the marketing committee, so that R2 isn't viewed as simply reducing technical debt. In my view, R2 would be about strengthening the non-functional aspects of the platform (usability, maintainability, scalability, reliability, etc.) to provide an unrivaled, hardened platform that can be leveraged in any carrier's environment. Regards, Jason Hunt Executive Software Architect, IBM Phone: 314-749-7422 Email: djh...@us.ibm.com<mailto:djh...@us.ibm.com> Twitter: @DJHunt From: Alla Goldner <alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>> To: "onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> Date: 08/17/2017 01:48 PM Subject: [onap-tsc] R2 use cases planning Sent by: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> ________________________________ Hi again, And in order to start the actual discussion… ☺ My own view is: 1. We should concentrate on missing ONAP Platform capabilities 2. New functional use cases can only be considered if a. They have big level of similarity/harmonization with R1 use case b. They are about extending ONAP Platform capabilities (no introduction of new functionality, new PNFs/VNFs, etc.) 3. We should follow the high level milestones plan presented on the last slide Best regards, Alla Goldner Open Network Division Amdocs Technology <image001.png> From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner Sent: Thursday, August 17, 2017 9:39 PM To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> Subject: [onap-tsc] R2 use cases planning Hi, TSC, I forward the material I’ve presented today on Usecase subcommittee discussions and ask for your feedback. We need to get guidelines on what to concentrate on for R2. Best regards, Alla Goldner Open Network Division Amdocs Technology <image001.png> From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alla Goldner Sent: Thursday, August 10, 2017 8:21 PM To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 'onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>' <onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>> Cc: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org> Subject: [onap-discuss] R2 use cases planning Hi all, Unfortunately, we didn’t have time during the TSC meeting to cover R2 use cases topic. I would like to ask you to review the attached presentation, covering status of Usecase subcommittee discussions and asking TSC for guidelines on directions we should take going forward (Extending ONAP Platform capabilities or introducing new functional use cases). Also, some initial proposal for R2 timelines is part of this input material, with emphasize given to pre-R2 milestones related to use cases approval. It is part of the next meeting agenda, https://wiki.onap.org/display/DW/2017-08-17+Meeting+Agenda<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_2017-2D08-2D17-2BMeeting-2BAgenda&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=etBN_zMmGjcGLhVqLfRzXeRE3OrheO1r5gpaJS481HA&s=QVIvLKg2we5jaMbrnNT3--ErpTEyHSc8H8OZCw2d7ew&e=>. It would be great if we can start the related discussion by emails and get your feedback prior to TSC meeting next week. Best regards, Alla Goldner Open Network Division Amdocs Technology <image001.png> 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=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=etBN_zMmGjcGLhVqLfRzXeRE3OrheO1r5gpaJS481HA&s=rxtJ_H81Xzp_fuHATyUefizPV0SvA6fJxsBl3gasJRY&e=> 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=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=etBN_zMmGjcGLhVqLfRzXeRE3OrheO1r5gpaJS481HA&s=rxtJ_H81Xzp_fuHATyUefizPV0SvA6fJxsBl3gasJRY&e=> 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=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=etBN_zMmGjcGLhVqLfRzXeRE3OrheO1r5gpaJS481HA&s=rxtJ_H81Xzp_fuHATyUefizPV0SvA6fJxsBl3gasJRY&e=>_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-tsc<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=etBN_zMmGjcGLhVqLfRzXeRE3OrheO1r5gpaJS481HA&s=0W25cv5W17kUFzCVqlPPimecZ0JBlgmeOEA2OorvrVw&e=> 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=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=etBN_zMmGjcGLhVqLfRzXeRE3OrheO1r5gpaJS481HA&s=rxtJ_H81Xzp_fuHATyUefizPV0SvA6fJxsBl3gasJRY&e=> _______________________________________________ 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=etBN_zMmGjcGLhVqLfRzXeRE3OrheO1r5gpaJS481HA&s=0W25cv5W17kUFzCVqlPPimecZ0JBlgmeOEA2OorvrVw&e=
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
