Alla – Thanks for bringing it up for discussion.
Before making decisions on the use case content of R2, I believe we should have
a better definition of the purpose of the use cases, and their selection
criteria. I believe that once we have that nailed down, it will be easy to
decide what goes into R2, R3…
So, here is my suggestion for goals and criteria:
* Use case goals
* Showcase ONAP features capabilities
* Provide a common set of test cases for ONAP releases
* Serve as a reference for other use cases that may be deployed using
ONAP
* What use cases are not
* A strict definition of what is in or out of scope for an ONAP release
(e.g. it is perfectly OK to have functionality in ONAP that is not necessarily
being consumed by any use case
* A strict definition of what functionality is “supported” or
“unsupported” (e.g. it should be possible to use a feature in a way that is not
used by any of the use cases)
* Examining a new use case should consider the following criteria
* Does it showcase new functionality that other use cases did not?
* Are all the relevant VNFs available as open source or trial license?
* What will be the cost (in terms of complexity, test duration, etc.) of
adding the use case to the set of release tests?
I am sure the community can suggest more goals and criteria, but IMHO we should
agree on them soon.
Regards,
Ranny.
From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org]
On Behalf Of Jason Hunt
Sent: Thursday, August 17, 2017 12:16 PM
To: Alla Goldner <alla.gold...@amdocs.com>
Cc: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] R2 use cases planning
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: djh...@us.ibm.com<mailto:djh...@us.ibm.com>
Twitter: @DJHunt
From: Alla Goldner
<alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>>
To: "onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>"
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
Date: 08/17/2017 01:48 PM
Subject: [onap-tsc] R2 use cases planning
Sent by:
onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>
________________________________
Hi again,
And in order to start the actual discussion… ☺
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
[cid:image001.png@01D31753.5A8079D0]
From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Thursday, August 17, 2017 9:39 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
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
[cid:image001.png@01D31753.5A8079D0]
From:
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>[mailto:onap-discuss-boun...@lists.onap.org]
On Behalf Of Alla Goldner
Sent: Thursday, August 10, 2017 8:21 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>;
'onap-disc...@lists.onap.org'
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>
Cc: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
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
[cid:image001.png@01D31753.5A8079D0]
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
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-tsc
_______________________________________________
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc
