Hi Yuan,

Thanks a lot for your comments!
The intention is to gather all these comments, start discussing them by emails 
now, present those requirements during our ONS/ONAP meeting next week and 
follow-up with f2f detailed discussions next week as well.

As to the process, our intention is to develop functional requirements, not use 
cases in their full form, in the same way as we did in Beijing.
For reference, here is the link to our process:
https://wiki.onap.org/display/DW/Use+Case+Evaluation+Process
Those functional requirements then may be leveraged by several demanded use 
cases, depending on the need.
We can also discuss it next week during our meeting.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:[email protected]]

From: [email protected] [mailto:[email protected]]
Sent: Tuesday, March 20, 2018 10:28 AM
To: Alla Goldner <[email protected]>
Cc: [email protected]; [email protected]
Subject: Re:[onap-tsc] Usecase subcommittee meeting 0f 19/03/2018 - the summary


Several comments:



1.    Scale out use case:  It looks like a functional requirement instead of a 
use case. A requirement could be general but use case should be specific so 
that the test team could write test case and prepare some specific VNFs for 
integration and testing based on the use case. I'd like to propose that a use 
case should describe: in which scenario who use and how to use what function 
for what purpose.

2.    Change management: To me, it is a quite clear requirement of "live 
upgrading", change management is too general to be understood. Most of teleco 
legacy equipments have thier own live upgrading capability and correspondent 
approach based on thier own software and hardware architecture. From my own 
developing experience, live upgrading is the most complicated part in teleco 
software. Different data storage policy and synchronization mechanism need 
different preparation during live upgrading. I believe virtualized 
infrastructure might provide some possibility to reduce the complicity of live 
upgrading but it is still complex when we think about data of the software 
which is deeply coupled with VNF internal approach.

3.    OSAM: Edge Cloud is still a cloud inlude virtualized infrastracture and 
PNF. I did not see any specific difference. Please clarify why this proposal 
intent to introduce a new kind of resource and management  mechanism.





袁越 yuanyue

资深战略规划师   Senior Strategy Planner

技术规划部/技术规划部/系统产品 Technology Planning Dept./Technology Planning Dept./System 
Product


[cid:[email protected]]

[cid:[email protected]]
南京市雨花区软件大道50号中兴通讯3号楼
1/F,Building 3, ZTE Nanjing R&D Center II, No.50, Software Avenue,YuHua 
District,Nanjing,P.R.China 210012

T: +025 88013478
M: +86 13851446442
E: [email protected]<mailto:[email protected]>
www.zte.com.cn<http://www.zte.com.cn/>

Original Mail
Sender: AllaGoldner <[email protected]<mailto:[email protected]>>
To: [email protected]<mailto:[email protected]> 
<[email protected]<mailto:[email protected]>>
CC: [email protected]<mailto:[email protected]> 
<[email protected]<mailto:[email protected]>>
Date: 2018/03/20 02:57
Subject: [onap-tsc] Usecase subcommittee meeting 0f 19/03/2018 - the summary
_______________________________________________
ONAP-TSC mailing list
[email protected]<mailto:[email protected]>
https://lists.onap.org/mailman/listinfo/onap-tsc


Hi all,

Thanks a lot to all meeting’s participants!

The following requirements were presented and will also be presented next week 
during our session at ONS (our session is on Monday, 1 pm – 2:30 pm)
1.            Manual Scaling in, Auto scaling in/out
2.            OSAM
3.            Change Management

Additionally,


1.       5G task force (Network Slicing, Optimization/OOF, PNF support 
leftovers)

2.       Parviz Yegani ((Real Time Data Event Streaming & Processing ( RESP))

3.       Any more?

Please send your presentations till this Thursday, the latest.

We also discussed the need to have f2f discussions for all related task forces 
during ONS, as there are many technical questions for the proposals, task force 
leads will send out emails inviting for such a discussions.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:[email protected]]

From: Alla Goldner
Sent: Sunday, March 18, 2018 4:54 PM
To: 'Vladimir Yanover (vyanover)' 
<[email protected]<mailto:[email protected]>>; 
[email protected]<mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>
Subject: RE: [onap-tsc] Agenda for the next Usecase subcommittee meeting 
(19/3/2018)

Hi Vladimir,

Fully agree,
I only received materials from Scott. Attached.

Others – please also try to distribute your materials in advance 9and upload to 
wiki).

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:[email protected]]

From: Vladimir Yanover (vyanover) [mailto:[email protected]]
Sent: Sunday, March 18, 2018 4:52 PM
To: Alla Goldner <[email protected]<mailto:[email protected]>>; 
[email protected]<mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>
Subject: RE: [onap-tsc] Agenda for the next Usecase subcommittee meeting 
(19/3/2018)

Hello, Alla
Are there any materials? We will use the meetings time more efficiently if the 
presentations are available in advance.
Thanks
Vladimir

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Alla Goldner
Sent: Friday, March 16, 2018 8:14 PM
To: [email protected]<mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>
Subject: [onap-tsc] Agenda for the next Usecase subcommittee meeting (19/3/2018)

Hi all,

The next meeting will be dedicated to review of your proposals for Casablanca, 
as a candidates to be presented during ONS/ONAP meeting.
The proposals will include leftovers from Beijing (those sub-features of 
scaling, Change management, HPA, PNF support which eventually will not be 
supported in Beijing) plus same requirements extensions for Casablanca plus new 
Casablanca  proposals.

Those planning to bring proposals – please let me know so I can plan the time 
accordingly.

So far, I’ve received the following:


1.       Scott Blandford (Manual Scaling in, Auto scaling in/out)

2.       Sumithra Bhojan (OSAM)

3.       Parviz Yegani (Real Time Data Event Streaming & Processing ( RESP)

4.       Ajay Mahimkar (Change Management)

Additionally, 5G task force have expressed their intention to present on 
Network Slicing and on Optimization/OOF, as well as on PNF support leftovers.

Please correct me if I forgot to include some and if there will be additional 
proposals.

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 
<https://www.amdocs.com/about/email-disclaimer>
_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc

Reply via email to