I think we should capture the feedbacks from various collaborative projects
using ONAP.
As an illustration, MEF is working on a project involving ONAP
https://mef.net/News/MEF-In-The-News
MEF members currently are working on three 3 reference implementation projects
on MEFnet: ... (2) an ONAP-t
support.
Thanks,
Alex Vul
Intel Corporation
From: Alla Goldner [mailto:alla.gold...@amdocs.com]
Sent: Wednesday, August 23, 2017 9:31 AM
To: Vul, Alex ; onap-usecasesub
Cc: onap-tsc@lists.onap.org P
Subject: RE: [onap-tsc] R2 use cases planning
Hi Alex,
Of course, we can do it, I agree
@intel.com]
Sent: Wednesday, August 23, 2017 7:26 PM
To: Alla Goldner ; onap-usecasesub
Cc: onap-tsc@lists.onap.org P
Subject: RE: [onap-tsc] R2 use cases planning
Alla,
I would suggest that we continue working on 5G use cases in their entirety,
even though we may only be able offer a subset of 5G
cents,
Alex Vul
Intel Corporation
From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org]
On Behalf Of Alla Goldner
Sent: Wednesday, August 23, 2017 9:16 AM
To: onap-usecasesub
Cc: onap-tsc@lists.onap.org P
Subject: Re: [onap-tsc] R2 use cases planning
Hi all,
Let me try
]
From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Monday, August 21, 2017 2:53 PM
To: Alla Goldner
Cc: Vladimir Yanover (vyanover) ; Jason Hunt
; onap-tsc@lists.onap.org P
Subject: Re: [onap-tsc] R2 use cases planning
Alla, Team
Agree with the discussion below that the goal of
-tsc@lists.onap.org
Subject: Re: [onap-tsc] R2 use cases planning
Just to be clear it’s development resources – people writing actual code.
Let me also try to separate resources a bit:
1. There are core development resources. People which write, integrate and
test code which is part of the
dimir Yanover
(vyanover)"
Date: Friday, August 18, 2017 at 5:42 AM
To: Jason Hunt , Alla Goldner
Cc: "onap-tsc@lists.onap.org"
Subject: Re: [onap-tsc] R2 use cases planning
what is this resource that should be managed
___
ONAP-TSC m
Hello
I also believe that we should be cautious about introducing new use-cases for
R2.
We should focus on missing topics that will be delivered for R1:
- High available ONAP platform (with HA components, ONAP release
management, ONAP components monitoring)
- DNS configuration
-
Technology
From: Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Sent: Friday, August 18, 2017 12:43 PM
To: Jason Hunt mailto:djh...@us.ibm.com>>; Alla Goldner
mailto:alla.gold...@amdocs.com>>
Cc: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: RE: [on
@lists.onap.org
Subject: Re: [onap-tsc] R2 use cases planning
Hi Vladimir, all,
Thanks for all replies received so far!
Vladimir, this is not about meeting time resources, I believe. Meeting time can
be extended, if necessary.
The limitation and the need to reduce the scope comes from the fact that
1.png@01D31829.1B8EB760]
From: Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Sent: Friday, August 18, 2017 12:43 PM
To: Jason Hunt ; Alla Goldner
Cc: onap-tsc@lists.onap.org
Subject: RE: [onap-tsc] R2 use cases planning
Jason, Alla and All
Just to understand the topic, what is this res
, August 17, 2017 10:16 PM
To: Alla Goldner
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
[mailto:onap-tsc-boun...@lists.onap.org]
On Behalf Of Jason Hunt
Sent: Thursday, August 17, 2017 12:16 PM
To: Alla Goldner
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
;
Subject: [onap-tsc] R2 use cases planning
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/har
AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] R2 use cases planning
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 leve
7422
Email: djh...@us.ibm.com
Twitter: @DJHunt
From: Alla Goldner
To: "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
Hi again,
And in order to start the actual discus
@01D317A2.561A6EB0]
From: 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
Subject: [onap-tsc] R2 use cases planning
Hi, TSC,
I forward the material I've presented today on Us
, 2017 8:21 PM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@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-tsc] R2 use cases planning
Hi all,
Un
ap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org]
On Behalf Of Alla Goldner
Sent: Thursday, August 10, 2017 8:21 PM
To: onap-tsc@lists.onap.org; 'onap-disc...@lists.onap.org'
Cc: onap-usecase...@lists.onap.org
Subject: [onap-tsc] R2 use cases planning
Hi all,
Unfortu
19 matches
Mail list logo
