Alla,

Thank you for your leadership here and for the work of the use case 
committee on this topic.

ONAP should be able to run any VNF or network service, even ones that 
aren't known today.  And, just as importantly, ONAP needs to manage those 
VNFs and network services well, in a number of various carrier 
environments.  As you've outlined, the question is how we balance those 
two items.

I agree with all of your points below  -- that R2 should be focused on 
improving the ONAP platform capabilities & only supporting new use cases 
where they are built on existing ONAP functionality.

If the community agrees with this approach, I think we want to be cautious 
about how we present the release's goal externally.  This may require some 
help from the marketing committee, so that R2 isn't viewed as simply 
reducing technical debt.  In my view, R2 would be about strengthening the 
non-functional aspects of the platform (usability, maintainability, 
scalability, reliability, etc.) to provide an unrivaled, hardened platform 
that can be leveraged in any carrier's environment.


Regards,
Jason Hunt 
Executive Software Architect, IBM 

Phone: 314-749-7422
Email: [email protected]
Twitter: @DJHunt
 



From:   Alla Goldner <[email protected]>
To:     "[email protected]" <[email protected]>
Date:   08/17/2017 01:48 PM
Subject:        [onap-tsc] R2 use cases planning
Sent by:        [email protected]



Hi again, 
 
And in order to start the actual discussion… J
 
My own view is:
 
1.       We should concentrate on missing ONAP Platform capabilities
2.       New functional use cases can only be considered if
a.       They have big level of similarity/harmonization with R1 use case
b.      They are about extending ONAP Platform capabilities (no 
introduction of new functionality, new PNFs/VNFs, etc.)
3.       We should follow the high level milestones plan presented on the 
last slide
 
 
 
Best regards, 
 
Alla Goldner
 
Open Network Division 
Amdocs Technology
 
 

 
From: [email protected] [
mailto:[email protected]] On Behalf Of Alla Goldner
Sent: Thursday, August 17, 2017 9:39 PM
To: [email protected]
Subject: [onap-tsc] R2 use cases planning
 
Hi, TSC,
 
I forward the material I’ve presented today on Usecase subcommittee 
discussions and ask for your feedback. 
 
We need to get guidelines on what to concentrate on for R2. 
 
 
 
Best regards, 
 
Alla Goldner
 
Open Network Division 
Amdocs Technology
 
 

 
From: [email protected] [
mailto:[email protected]] On Behalf Of Alla Goldner
Sent: Thursday, August 10, 2017 8:21 PM
To: [email protected]; '[email protected]' <
[email protected]>
Cc: [email protected]
Subject: [onap-discuss] R2 use cases planning
 
Hi all,
 
Unfortunately, we didn’t have time during the TSC meeting to cover R2 use 
cases topic.
 
I would like to ask you to review the attached presentation, covering 
status of Usecase subcommittee discussions and asking TSC for guidelines 
on directions we should take going forward (Extending ONAP Platform 
capabilities or introducing new functional use cases). 
Also, some initial proposal for R2 timelines is part of this input 
material, with emphasize given to pre-R2 milestones related to use cases 
approval.
 
It is part of the next meeting agenda, 
https://wiki.onap.org/display/DW/2017-08-17+Meeting+Agenda .
It would be great if we can start the related discussion by emails and get 
your feedback prior to TSC meeting next week.
 
Best regards, 
 
Alla Goldner
 
Open Network Division 
Amdocs Technology
 
 

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




_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc

Reply via email to