Hi Alla, IMHO, the use case helps us drive focus on a set of capabilities that we want to highlight in a release (be they features, architecture, models, interfaces, demos, etc.). I think it's helpful to identify that set up front and select a use case that can expose it. Ideally, the use case should be achievable and stretch our capabilities a little, while allowing us to address technical debt. We should also be capable of demoing the use case at relevant events after the release, so we should have confidence we can support it in the lab (e.g., people are willing to provide VNFs/PNFs and we have sufficient expertise and interest in the lab teams).
I haven't been actively engaged in the use case discussions, and don't want to second-guess the team. Generally, I agree with your suggestion below. My personal view is that the use case should address: 1. Capabilities - better integration between VF-C/APP-C flows, underlay networks, possibly orchestration federation/hierarchy 2. Time to clean up technical debt 3. Achievable in the lab With those lenses, I think use cases such as the enterprise vCPE/SD-WAN proposals offer a good balance of adding some new (demo-able) functionality, while also allowing us to address technical debt and improve the quality of the release. Chris From: [email protected] [mailto:[email protected]] On Behalf Of Alla Goldner Sent: Thursday, August 17, 2017 11:48 AM To: [email protected] Subject: [onap-tsc] R2 use cases planning 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 [cid:[email protected]] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Alla Goldner Sent: Thursday, August 17, 2017 9:39 PM To: [email protected]<mailto:[email protected]> 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 [cid:[email protected]] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Alla Goldner Sent: Thursday, August 10, 2017 8:21 PM To: [email protected]<mailto:[email protected]>; '[email protected]' <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> 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 . 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 [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 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 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
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
