Re: [onap-tsc] Proposed replies to 3GPP Liaison Statements addressed to ONAP

Good Morning Catherine, What was the result of the vote? Sorry for being pushy but we are on a very tight time schedule. I need to provide the reply to 3GPP ASAP to hit their Rel-16 freeze date. Thanks, Magnus From: onap-tsc@lists.onap.org On Behalf Of Catherine LEFEVRE via lists.onap.org Sen

Re: [Onap-arc] [onap-tsc] ArchCom: Planning and Preparations for the Guilin-R7 Release Architecture Reviews

Dear Chaker, Got it! Thank you very much for your kind consideration. Best, Lin --- 发件人: 代表 Chaker Al-Hakim 日期: 2020年5月11日 星期一 20:56 收件人: LinMeng , "onap-...@lists.onap.org" 抄送: "swaminathan.seethara...@wipro.com" , "onap-tsc@lists.onap.org" 主题: Re: [O

Re: [onap-tsc] ACTION REQUIRED / Changes to Release Use Case / Requirements Tracking #jira #guilin

Team, I've setup the new Guilin requirements tracking page . Please take a look. I split out the tables by: Use Cases; Requirements; Non-Functional Requirements; and PoC. Let me know if you have any questions or concerns. David On Fri, May 8, 2020 at 12:24 PM D

Re: [onap-tsc] [Onap-usecasesub] Guilin Release is Now Kicked-Off - CALL FOR ACTION - Ends May 27th, 5 PM Pacific

Hi Scott, I'd like to try to avoid a proliferation of fields and options, if I can help it. I think that if you make it clear in the description that it is a control loop requirement, then that should be sufficient. Let me know if you disagree. Thanks. David On Mon, May 11, 2020 at 12:44 PM BL

Re: [onap-tsc] [Onap-usecasesub] Guilin Release is Now Kicked-Off - CALL FOR ACTION - Ends May 27th, 5 PM Pacific

Hi Andy, This appears to be a release requirement proposal (let me know if I'm wrong). If so, I suggest that you replace DOC-608 with a REQ epic, and attach the stories to the REQ epic. Instructions may be found here . On

Re: [onap-tsc] [Onap-usecasesub] Guilin Release is Now Kicked-Off - CALL FOR ACTION - Ends May 27th, 5 PM Pacific

David, Should we also add an option to that field for Control Loop Requirement? The Requirement Subcommittee is not tracking those requirements, and it might be good to know where the requirements are originating. Scott Blandford From: onap-usecase...@lists.onap.org On Behalf Of David McBrid

Re: [onap-tsc] [Onap-usecasesub] Guilin Release is Now Kicked-Off - CALL FOR ACTION - Ends May 27th, 5 PM Pacific

There was already a field called "Req or Use Case", that included the options "Requirement" and "Use Case". I just added a third choice "Non-Functional Requirement". The field still defaults to "Requirement". David On Mon, May 11, 2020 at 10:31 AM David McBride wrote: > Ok - I will add it to

Re: [onap-tsc] Please Read: Possible Date Change for the June Developer and Testing Forum

Hi all! [OFFICIALLY ANNOUNCED] We are now officially moving the date to June 22-25. Thank you to everyone who provided us feedback on the date change. Registration for the event is now open: https://events.linuxfoundation.org/lfn-dev-test-forum/ Because we've pushed back the date of the event, w

Re: [onap-tsc] [Onap-usecasesub] Guilin Release is Now Kicked-Off - CALL FOR ACTION - Ends May 27th, 5 PM Pacific

Alla, I created these JIRAs under the Documentation project for the API Documentation non-functional requirements. Epic: https://jira.onap.org/browse/DOC-608 User Story: https://jira.onap.org/browse/DOC-609 User Story: https://jira.onap.org/browse/DOC-610 User Story: https://jira.onap.org/browse/

Re: [onap-tsc] [Onap-usecasesub] Guilin Release is Now Kicked-Off - CALL FOR ACTION - Ends May 27th, 5 PM Pacific

Ok - I will add it to the template. - D On Mon, May 11, 2020 at 10:25 AM Alla Goldner wrote: > I would say so. > > > Sent from Nine > -- > *From:* David McBride > *Sent:* Monday, 11 May 2020 20:20 > *To:* Alla Goldner > *Cc:* catherine.lefe...@intl.att.com; onap-tsc@

Re: [onap-tsc] [Onap-usecasesub] Guilin Release is Now Kicked-Off - CALL FOR ACTION - Ends May 27th, 5 PM Pacific

I would say so. Sent from Nine From: David McBride Sent: Monday, 11 May 2020 20:20 To: Alla Goldner Cc: catherine.lefe...@intl.att.com; onap-tsc@lists.onap.org; onap-usecase...@lists.onap.org Subject: Re: [Onap-usecasesub] Guilin Release is Now Kicked-Off - CALL

Re: [onap-tsc] [Onap-usecasesub] Guilin Release is Now Kicked-Off - CALL FOR ACTION - Ends May 27th, 5 PM Pacific

Alla and Catherine, Do we need another field in the Requirements JIRA template to distinguish “non functional” requirements from other requirements? Please advise. David On Mon, May 11, 2020 at 8:41 AM Alla Goldner wrote: > Hi Catherine, all, > > > > In general, all non-functional requirement

[onap-tsc] 2020 April LFN Event Blog and More ...

Dear ONAP Community, The Linux Foundation gave me a great opportunity to create a blog about our 2020 April LFN Event. Have a look at it - https://www.lfnetworking.org/blog/2020/05/11/the-lfn-technical-meetings-go-virtual/ As previously stated, I was impressed by the high attendance numbers, th

[onap-tsc] Hi all, Requirements subcommittee meeting minutes can be found under

https://wiki.onap.org/display/DW/May+11%2C+2020 Please pay attention to the deadlines and process described in the minutes! Best Regards, Alla This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at

Re: [onap-tsc] Guilin Release is Now Kicked-Off - CALL FOR ACTION - Ends May 27th, 5 PM Pacific

Hi Catherine, all, In general, all non-functional requirements supposed to be documented here: https://wiki.onap.org/display/DW/Guilin+release+-+non-functional+requirements+proposed+list We reviewed and endorsed those on the wiki page and Security ones (Pawel will document them on the same page)

[onap-tsc] ESR Subproject status

Dear ONAP TSC, There has been an ongoing search for resources to support the ESR subproject, and the lack of an updated and working ESR component in the Frankfurt Release needs attention. Background: The original code was part of Open-O and was originally proposed as a standalone project, but

Re: [E] [onap-tsc] a reminder - today's Requirements subcommittee meeting starts at 2 PM UTC

Hi Alla, I can't find the requirements meeting on the groups.io calendar. Can you provide the zoom meeting link? BR, Fred On Mon, May 11, 2020 at 6:31 AM Alla Goldner wrote: > We will continue discussing Guilin Release requirements proposals > > *This email and the information contained herein

Re: [onap-tsc] Recommend GO on Frankfurt RC1 #frankfurt

Just realized that I used the wrong link for AAF-1127. Here's the correct link: https://jira.onap.org/browse/AAF-1127 David On Fri, May 8, 2020 at 3:28 PM David McBride wrote: > TSC members, > > Morgan provided a summary of integration status >

[onap-tsc] Upcoming Event: #ptl Weekly (UTC) - Mon, 05/11/2020 1:00pm-3:00pm #cal-reminder

*Reminder:* #ptl Weekly (UTC) *When:* Monday, 11 May 2020, 1:00pm to 3:00pm, (GMT+00:00) UTC *Where:* https://zoom.us/j/283628617 View Event ( https://lists.onap.org/g/onap-tsc/viewevent?eventid=774161 ) *Organizer:* David McBride dmcbr...@linuxfoundation.org ( dmcbr...@linuxfoundation.org?sub

Re: [onap-tsc] [Onap-usecasesub] a reminder - today's Requirements subcommittee meeting starts at 2 PM UTC

Hi Alla，we have a requirement CCVPN- Transport Slicing to report. We would like to request 10mins on today’s call. Hope this is ok.We will post the business driver on the wiki before the call.Best,Lin

[onap-tsc] a reminder - today's Requirements subcommittee meeting starts at 2 PM UTC

We will continue discussing Guilin Release requirements proposals This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service

Re: [onap-tsc] ArchCom: Planning and Preparations for the Guilin-R7 Release Architecture Reviews

Dear Chaker, I have created a wiki page following the template you provided: https://wiki.onap.org/display/DW/R7+Guilin%28AR-0011-R7-052020%29E2E+Network+Slicing+Architecture+Review-functional+requirements Content will be completed before our report to the Archom. We would like to request a

Re: [onap-tsc] Testing automation requirements apply for the Guilin-R7 release architecture review

Dear Chaker, Sorry, due to some time conflict, can we re-apply and change the requirement architecture report time to next week? Our requirements include: AR-0027-R7-052020: Support for Test Topology Auto Design （NFV Testing Automatic Platform） AR-0028-R7-052020: Support for Test Env