Hi all, Some update on the AI from the list below:
1. Yang has included tool requirements for validating CSAR file as R2 non-functional requirements proposal https://wiki.onap.org/display/DW/R2+proposals+for+Non-functional+requirements 2. As agreed with Chris, we will have a joint discussion with architecture subc. , modeling subc. and all involved projects on external Controller during the next week's Architecture call. As indicated by Ramesh, he will provide more requirements details before that meeting. Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:[email protected]] From: [email protected] [mailto:[email protected]] On Behalf Of Alla Goldner Sent: Monday, October 09, 2017 6:35 PM To: [email protected] Cc: GILBERT, MAZIN E (MAZIN E) <[email protected]>; Phil Robb <[email protected]>; [email protected] Subject: [Onap-usecasesub] Usecase subcommittee 09/10/2017, the meeting summary Hi all, Thanks to all meeting's attendants! Here is the meeting's summary: 1. We reviewed the status and needs of R1 vVoLTE and R-vCPE use cases. It was reported by Yang (vVoLTE team) that vendor's validation tools are lacking and this delays progress. AI (Alla, Yang) - to check what tools implementation proposals are missing from R2 non-functional requirements proposals and include those 2. We reviewed 5G requirements status, presented by Vimal and members of 5G task force a. RAN deployment and Optimization - some requirements for a specific projects will be extracted from the list, and discussed as a proposals with a relevant projects, while the full use cases implementation will not be targeted by Beijing release b. Network slicing - team will bring the next level of details i.e. proposal what should be done per each one of the potentially affected projects in 2 weeks from now. Next week we will get an update. We will target discussion with a different projects/architecture/modelling subcommittees in a 2 weeks from now. AI(Vimal - to progress work, Alla - to arrange meeting, once indication on the list of affected projects is in place) 3. We discussed Ramesh's proposal on External Controller implementation. AI (Ramesh - generalize description to apply to any external controller, Alla - schedule meeting with involved projects for the next week) 4. Bharath presented resiliency requirements. AI (Bharath will work with Jason on mapping those requirements to the list of "Enterprise-grade" levels we build currently). I re-attach the list of prioritized functional requirements that we have as an output from f2f meeting (also available on wiki) and encourage you to extend your favorite requirements definition, as we are getting close to the Beijing Release scope's approval, while we need more extended description of the requirements to be able to proceed :) Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:[email protected]] From: Alla Goldner Sent: Friday, October 06, 2017 12:13 PM To: '[email protected]' <[email protected]<mailto:[email protected]>> Cc: 'Kenny Paul' <[email protected]<mailto:[email protected]>>; Phil Robb <[email protected]<mailto:[email protected]>>; GILBERT, MAZIN E (MAZIN E) <[email protected]<mailto:[email protected]>>; '[email protected]' <[email protected]<mailto:[email protected]>> Subject: Usecase subcommittee: agenda for 09/10/2017 Hi all, Here is agenda for the upcoming Usecase subcommittee meeting: 1. Short overview of R1 vVoLTE and R-vCPE status and needs (10 min) 2. Network slicing discussion: whether there is a need in a new dedicated network slicing requirements related to ONAP (e.g. slice controller). Please bring inputs for this discussion, as we must move towards conclusion here (20 min) 3. Other prioritized functional requirements: the next level of details. For your reference, the outcomes of f2f meting are attached. (15 min) 4. Non-functional requirements - common resiliency (Bharath) (15 min) 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 <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
