Hi Pam, Will you have a meeting next week?
Best regards, Alla -------- Original Message -------- Subject: Re: [Onap-usecasesub] Outcomes of Usecase subcommittee meeting today From: "DRAGOSH, PAMELA L (PAM)" <pdrag...@research.att.com> Date: Dec 14, 2017, 14:18 To: Alla Goldner <alla.gold...@amdocs.com>,onap-usecase...@lists.onap.org Alla and Use Case Owners, Would it possible to consolidate some parts of this by having Use Case Owners present Control Loop requirements (If Applicable) in the Control Loop Sub Committee meetings? The committee would like to collect and manage all the requirements for Beijing for all the PTL’s, most of which are attending the CL sub committee meeting. Regards, Pam Dragosh From: <onap-usecasesub-boun...@lists.onap.org> on behalf of Alla Goldner <alla.gold...@amdocs.com> Date: Wednesday, December 13, 2017 at 4:54 PM To: "onap-usecase...@lists.onap.org" <onap-usecase...@lists.onap.org> Cc: "onap-tsc@lists.onap.org" <onap-tsc@lists.onap.org> Subject: [Onap-usecasesub] Outcomes of Usecase subcommittee meeting today Hi all, Thanks a lot to those attending our meeting today, both f2f and in remote mode!!! Here is the summary/list of action items: 1. Needed to have contact person details per each requirement – Alla to provide (in the attached) 2. Scaling out requirement is merged with auto/manual scaling requirement, assuming both VFC and APPC support 3. Enhancements for service onboarding requirement merges with PNF support requirement 4. 5G task force ned to discuss VFC support with VFC team, as currently this is missing from the table of affected entities 5. The next level of details for discussions with PTLs must be provided by the requirements authors and this should include, at least: a. Sequence diagrams b. VNFs c. Full list of involved companies (in terms of number of developers each company is willing to put on the specific development) d. Model information e. Description of how the requirement will be tested f. APIs (existing and new) – nice to have, if information is available 6. It is up to requirements’ authors to have discussions with PTLs during the next week (as the following one is Christmas Holidays). PTLs must get all information related to specific functional requirements (as per described above) and discuss it with the teams by the end of the next week, so, when they come back from Christmas vacation (January 2nd), they can analyze and discuss it with their teams, and come up with their estimations by January 8th. By January 18 (during the following 10 days) they will need to build harmonized view on all functional requirements plus S3P, and define what they can implement. Those requirements which will not be discussed with PTLs next week will be defined as a stretch goal. Monday’s Usecase subcommittee meeting will be dedicated to review the additional information available by Monday. We can also use some of the meeting time for discussions with the PTLs, if requirements team makes sure PTL attends our call. Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image001.png@01D374E5.FE2D97D0] 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=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=QwBKbiMYBb845bOp5BxY7nSe4K5mtIEFYMqbK8XIIEE&s=WViKuDT2HrC37F6Tg_MHi184JiracfeT7iko1_Z9f28&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://www.amdocs.com/about/email-disclaimer>
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
