答复: [onap-tsc] Frankfurt Release Requirements - Target: Oct 15th, EOD !!!
Thank you Hui, for the quick clarification. Is it safe to say, that one could be focused on the first modeling track, if he/she is interested in enabling slicing support. Thanks, Lingli 发件人: denghui (L) [mailto:denghu...@huawei.com] 发送时间: 2019年10月15日 13:59 收件人: Lingli Deng; onap-tsc@lists.onap.org 抄送: 'MAYER, ANDREW J' 主题: RE: [onap-tsc] Frankfurt Release Requirements - Target: Oct 15th, EOD !!! Hi Lingli and Eric, For modeling part, 1) Slicing modeling, it is more specific topic with the committed implementation. 2) 5G/ORAN & 3GPP standards harmonization, https://jira.onap.org/browse/REQ-38, It is more ORAN related ORAN RIC, SDN-R/CDS, 3) For 5G / 5G Service Modeling: Modeling (exploratory) work for creating a 5G Service, it has been moved to lower priority according to https://wiki.onap.org/display/DW/ONAP+R6+Modeling+High+Level+Requirements So I don’t see any confliction here. Thanks a lot for your checking again Best regards, DENG Hui From: Lingli Deng [mailto:denglin...@chinamobile.com] Sent: Tuesday, October 15, 2019 6:37 AM To: onap-tsc@lists.onap.org Cc: 'MAYER, ANDREW J' ; denghui (L) Subject: 答复: [onap-tsc] Frankfurt Release Requirements - Target: Oct 15th, EOD !!! Hi Eric, Thanks for pointing out the issues. I also believe we need to consolidate and differentiate usecase and modeling/functional requirements. And I have some good progress to report. >From the usecase perspective, according to the discussion we had in Anterwep >hosted by Alla, we are merging the following two into a single one E2E network >slicing usecase, and getting prepared for an architectural review next week 4) Vertical Industry Oriented On-demand 5G Slice Service 5) Network Slicing >From the modeling requirement perspective, I am afraid that it seems to me >that there are internal dependencies between some of them, so high recommend >to sort out the relation, do some consolidation and properly prioritize >related modeling threads. 6) Modeling: Enhanced Nested and Shared Service Information Model - 5G / E2E Network Slicing modeling 7) Modeling: 5G / ORAN & 3GPP Standards Harmonization 8) 5G / 5G Service Modeling: Modeling (exploratory) work for creating a 5G Service But I am not a modeling expert, so perhaps we need to do something similar as we did with usecase and asking the SubC co-chairs to help us out. Lingli 发件人: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] 代表 Eric Debeau via Lists.Onap.Org 发送时间: 2019年10月14日 20:30 收件人: onap-tsc@lists.onap.org 主题: Re: [onap-tsc] Frankfurt Release Requirements - Target: Oct 15th, EOD !!! Hello There is still a lot of requirements. How do we intend to prioritize all the requirements ? In addition, I believe that some requirements are overlapping: Eg for network slicing, I can find the following requirements and it is difficult to commit for such requirements 9) Modeling: Enhanced Nested and Shared Service Information Model - 5G / E2E Network Slicing modeling 10) Modeling: 5G / ORAN & 3GPP Standards Harmonization 11) 5G / 5G Service Modeling: Modeling (exploratory) work for creating a 5G Service 12) Vertical Industry Oriented On-demand 5G Slice Service 13) Network Slicing We also have various levels of description: -Some requirements are very atomic -Some requirements are more global (eg Network Slicing) I also noticed that some requirements and use-cases are not listed in the right table ·End to End Layer 1 Service Management. Modeling the Optical Service should be a use –case ·Service Resolver should be a feature and not a use-case If the requirements only impact one project (and Integration), it should be managed at the project level (eg Portal, DCAE/Acumos integration, … Best Regards Eric De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de Catherine LEFEVRE Envoyé : vendredi 11 octobre 2019 20:58 À : onap-tsc@lists.onap.org Objet : [onap-tsc] Frankfurt Release Requirements - Target: Oct 15th, EOD !!! Importance : Haute Dear Frankfurt « Owners », Thank you for submitting your use cases and your requirements for the Frankfurt release. We are really excited to kick-off our Frankfurt as soon as possible https://wiki.onap.org/display/DW/Frankfurt+Release+Requirements The TSC is currently performing some prioritizations based on your inputs and EUAG inputs. It is essential that we collect your additional inputs not later than Oct 15th, 2019 end of your day If we do not get them on time then we will postpone your use case/requirements to the Guilin Release. ·Use Case / requirements should be reviewed by the Architecture Team ASAP ·As you know, we are currently under capacity concerning our Testing activities Therefore a new column
答复: [onap-tsc] Frankfurt Release Requirements - Target: Oct 15th, EOD !!!
Hi Eric, Thanks for pointing out the issues. I also believe we need to consolidate and differentiate usecase and modeling/functional requirements. And I have some good progress to report. >From the usecase perspective, according to the discussion we had in Anterwep >hosted by Alla, we are merging the following two into a single one E2E network >slicing usecase, and getting prepared for an architectural review next week · Vertical Industry Oriented On-demand 5G Slice Service · Network Slicing >From the modeling requirement perspective, I am afraid that it seems to me >that there are internal dependencies between some of them, so high recommend >to sort out the relation, do some consolidation and properly prioritize >related modeling threads. · Modeling: Enhanced Nested and Shared Service Information Model - 5G / E2E Network Slicing modeling · Modeling: 5G / ORAN & 3GPP Standards Harmonization · 5G / 5G Service Modeling: Modeling (exploratory) work for creating a 5G Service But I am not a modeling expert, so perhaps we need to do something similar as we did with usecase and asking the SubC co-chairs to help us out. Lingli 发件人: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] 代表 Eric Debeau via Lists.Onap.Org 发送时间: 2019年10月14日 20:30 收件人: onap-tsc@lists.onap.org 主题: Re: [onap-tsc] Frankfurt Release Requirements - Target: Oct 15th, EOD !!! Hello There is still a lot of requirements. How do we intend to prioritize all the requirements ? In addition, I believe that some requirements are overlapping: Eg for network slicing, I can find the following requirements and it is difficult to commit for such requirements · Modeling: Enhanced Nested and Shared Service Information Model - 5G / E2E Network Slicing modeling · Modeling: 5G / ORAN & 3GPP Standards Harmonization · 5G / 5G Service Modeling: Modeling (exploratory) work for creating a 5G Service · Vertical Industry Oriented On-demand 5G Slice Service · Network Slicing We also have various levels of description: - Some requirements are very atomic - Some requirements are more global (eg Network Slicing) I also noticed that some requirements and use-cases are not listed in the right table · End to End Layer 1 Service Management. Modeling the Optical Service should be a use –case · Service Resolver should be a feature and not a use-case If the requirements only impact one project (and Integration), it should be managed at the project level (eg Portal, DCAE/Acumos integration, … Best Regards Eric De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de Catherine LEFEVRE Envoyé : vendredi 11 octobre 2019 20:58 À : onap-tsc@lists.onap.org Objet : [onap-tsc] Frankfurt Release Requirements - Target: Oct 15th, EOD !!! Importance : Haute Dear Frankfurt « Owners », Thank you for submitting your use cases and your requirements for the Frankfurt release. We are really excited to kick-off our Frankfurt as soon as possible https://wiki.onap.org/display/DW/Frankfurt+Release+Requirements The TSC is currently performing some prioritizations based on your inputs and EUAG inputs. It is essential that we collect your additional inputs not later than Oct 15th, 2019 end of your day If we do not get them on time then we will postpone your use case/requirements to the Guilin Release. ·Use Case / requirements should be reviewed by the Architecture Team ASAP ·As you know, we are currently under capacity concerning our Testing activities Therefore a new column has been added “Integration Lead” to identify per use case, per requirement. The Integration Lead will have the following responsibilities: o Identify the testers o Define the Integration Test Plan for the use case or requirement o Develop with his/her testers the automated tests o Provide Test Results to the Integration Team ·Provide project’s impact for your use case/requirement. Example: SDC (C); SO (C) , AAI(TO) C= Code Change, TO= Test Only ·Provide the list of Dev committed to impacted PTL per use case, per requirement a.k.a these columns should be filled up Examples SDC committed by Ericsson SO partially committed by Nokia SO will only support REQ-xxx ·Provide T-Shirt Size – is it a multiple release requirement or not? ·Provide Company Engagement If you look at the TSC minutes (Oct. 10th), you will find the list of missing items per use case, per requirement. https://wiki.onap.org/display/DW/TSC+2019-10-10 If your use case/requirement is not listed in the table then the architecture did not approve it or have not yet finalized the review. Please let us know if you have any question concerning our
