Re: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

2018-05-16 Thread Alla Goldner 
Vladimir,

if I understood Steve's comment correctly, it is not about any particular name, 
but more about recognition of yet additional standalone controller, while we 
don't have it as a part of our architecture.
This is why the proposal is to contain it under SDN-C (as, also according to 
our architecture, this is SDN-C's sub-module/sub-project), but explain 
explicitly what this module's functionality is.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EDBE.84CB1FF0]

From: Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Sent: Thursday, May 17, 2018 8:53 AM
To: Alla Goldner ; Dhananjay Pavgi 
; SHANKARANARAYANAN, N K (N K) 
; onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
Subject: RE: [Onap-usecasesub] [onap-tsc] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

SDN-R is ONF project based on the Microwave Information Model TR-532, which is 
quite distant from what is needed for cellular RAN.
So what we knew as SDN-R in fact never was SDN Radio controller :)
Therefore we are free to keep the name SDN-R or find another good looking name. 
After all, it's just trademark.
I propose SADRAN= SoftwAre Defined RAN.
Thanks
Vladimir




From: 
onap-usecasesub-boun...@lists.onap.org
 
mailto:onap-usecasesub-boun...@lists.onap.org>>
 On Behalf Of Alla Goldner
Sent: Wednesday, May 16, 2018 10:28 PM
To: Dhananjay Pavgi 
mailto:dp00476...@techmahindra.com>>; 
SHANKARANARAYANAN, N K (N K) 
mailto:shan...@research.att.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: Re: [Onap-usecasesub] [onap-tsc] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Guys,

All proponents of SDN-R terminology - when I asked during the meeting are there 
any concerns regarding the compromise proposal of saying "SDN-C" and then 
explicitly describing the functionality of this sub-module, there were no 
concerns about it.

One additional sub-compromise :) - can we agree on calling it "SDN-R (SDN-C 
sub-module)"?

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EDBE.84CB1FF0]

From: Dhananjay Pavgi [mailto:dp00476...@techmahindra.com]
Sent: Thursday, May 17, 2018 7:07 AM
To: SHANKARANARAYANAN, N K (N K) 
mailto:shan...@research.att.com>>; Alla Goldner 
mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: RE: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Concur with views below from Shankar. Why confuse by changing it to SDN-C when 
we know it's functionality quite "Radio" and wireless domain specific.

thanks & regards,
Dhananjay Pavgi
+91 98220 22264

From: onap-tsc-boun...@lists.onap.org 
mailto:onap-tsc-boun...@lists.onap.org>> On 
Behalf Of SHANKARANARAYANAN, N K (N K)
Sent: Thursday, May 17, 2018 8:39 AM
To: Alla Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Alla,

I don't understand the decision to change the SDN-R term after the several 
discussions in the 5G and SDN-R groups
using this term to describe the single ONAP OA&M controller persona (derived 
from CC-SDK) for mobility and wireless PNF/VNFs.
The reasons were articulated in the discussions. There has been momentum in 
using the SDN-R term, and changing it to SDN-C now causes confusion.

Regards,

Shankar


From: 
onap-usecasesub-boun...@lists.onap.org
 [onap-usecasesub-boun...@lists.onap.org] on behalf of Alla Goldner 
[alla.gold...@amdocs.com]
Sent: Tuesday, May 15, 2018 4:21 AM
To: onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc
Subject: [Onap-usecasesub] The summary of Usecase subcommittee meeting 
14/05/2017 - Casablanca use cases/functional requirements endorsement
Hi all,

Here is the summary of our yesterday's meeting.
Thanks to all meeting participants!


1.   We have fully endorsed the following use cases/functional requirements:

a.   OSAM

b.  Auto Scaling out

c.   Consistent representation a

Re: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

2018-05-16 Thread Vladimir Yanover (vyanover) 
SDN-R is ONF project based on the Microwave Information Model TR-532, which is 
quite distant from what is needed for cellular RAN.
So what we knew as SDN-R in fact never was SDN Radio controller :)
Therefore we are free to keep the name SDN-R or find another good looking name. 
After all, it's just trademark.
I propose SADRAN= SoftwAre Defined RAN.
Thanks
Vladimir



From: onap-usecasesub-boun...@lists.onap.org 
 On Behalf Of Alla Goldner
Sent: Wednesday, May 16, 2018 10:28 PM
To: Dhananjay Pavgi ; SHANKARANARAYANAN, N K (N K) 
; onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
Subject: Re: [Onap-usecasesub] [onap-tsc] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Guys,

All proponents of SDN-R terminology - when I asked during the meeting are there 
any concerns regarding the compromise proposal of saying "SDN-C" and then 
explicitly describing the functionality of this sub-module, there were no 
concerns about it.

One additional sub-compromise :) - can we agree on calling it "SDN-R (SDN-C 
sub-module)"?

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3ED66.740666A0]

From: Dhananjay Pavgi [mailto:dp00476...@techmahindra.com]
Sent: Thursday, May 17, 2018 7:07 AM
To: SHANKARANARAYANAN, N K (N K) 
mailto:shan...@research.att.com>>; Alla Goldner 
mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: RE: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Concur with views below from Shankar. Why confuse by changing it to SDN-C when 
we know it's functionality quite "Radio" and wireless domain specific.

thanks & regards,
Dhananjay Pavgi
+91 98220 22264

From: onap-tsc-boun...@lists.onap.org 
mailto:onap-tsc-boun...@lists.onap.org>> On 
Behalf Of SHANKARANARAYANAN, N K (N K)
Sent: Thursday, May 17, 2018 8:39 AM
To: Alla Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Alla,

I don't understand the decision to change the SDN-R term after the several 
discussions in the 5G and SDN-R groups
using this term to describe the single ONAP OA&M controller persona (derived 
from CC-SDK) for mobility and wireless PNF/VNFs.
The reasons were articulated in the discussions. There has been momentum in 
using the SDN-R term, and changing it to SDN-C now causes confusion.

Regards,

Shankar


From: 
onap-usecasesub-boun...@lists.onap.org
 [onap-usecasesub-boun...@lists.onap.org] on behalf of Alla Goldner 
[alla.gold...@amdocs.com]
Sent: Tuesday, May 15, 2018 4:21 AM
To: onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc
Subject: [Onap-usecasesub] The summary of Usecase subcommittee meeting 
14/05/2017 - Casablanca use cases/functional requirements endorsement
Hi all,

Here is the summary of our yesterday's meeting.
Thanks to all meeting participants!


1.   We have fully endorsed the following use cases/functional requirements:

a.   OSAM

b.  Auto Scaling out

c.   Consistent representation and identification of a cloud region in ONAP

d.  Edge Automation through ONAP



2.   5G group of functional requirements is endorsed, with the following 
exceptions:

a.   Terminology of SDN-R will be replaced by SDN-C, while it will be 
clarified what is the functionality of the SDN-C sub-module (used to be called 
SDN-R) to cover necessary enhancements

b.  SON and slice optimization topics will be re-discussed till next 
Monday's Usecase subcommittee meeting by all interested parties. There are 
concerns expressed by Cisco (Vladimir Yanover) which require additional 
discussions. We will monitor their progress and see if consensus is achieved or 
this issue needs to be raised and decided by the TSC



3.   Casablanca's HPA and Change Management authors - please upload your 
proposals under 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+endorsement

Re: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

2018-05-16 Thread Alla Goldner 
Guys,

All proponents of SDN-R terminology - when I asked during the meeting are there 
any concerns regarding the compromise proposal of saying "SDN-C" and then 
explicitly describing the functionality of this sub-module, there were no 
concerns about it.

One additional sub-compromise :) - can we agree on calling it "SDN-R (SDN-C 
sub-module)"?

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EDB8.E8F74180]

From: Dhananjay Pavgi [mailto:dp00476...@techmahindra.com]
Sent: Thursday, May 17, 2018 7:07 AM
To: SHANKARANARAYANAN, N K (N K) ; Alla Goldner 
; onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
Subject: RE: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Concur with views below from Shankar. Why confuse by changing it to SDN-C when 
we know it's functionality quite "Radio" and wireless domain specific.

thanks & regards,
Dhananjay Pavgi
+91 98220 22264

From: onap-tsc-boun...@lists.onap.org 
mailto:onap-tsc-boun...@lists.onap.org>> On 
Behalf Of SHANKARANARAYANAN, N K (N K)
Sent: Thursday, May 17, 2018 8:39 AM
To: Alla Goldner mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Alla,

I don't understand the decision to change the SDN-R term after the several 
discussions in the 5G and SDN-R groups
using this term to describe the single ONAP OA&M controller persona (derived 
from CC-SDK) for mobility and wireless PNF/VNFs.
The reasons were articulated in the discussions. There has been momentum in 
using the SDN-R term, and changing it to SDN-C now causes confusion.

Regards,

Shankar


From: 
onap-usecasesub-boun...@lists.onap.org
 [onap-usecasesub-boun...@lists.onap.org] on behalf of Alla Goldner 
[alla.gold...@amdocs.com]
Sent: Tuesday, May 15, 2018 4:21 AM
To: onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc
Subject: [Onap-usecasesub] The summary of Usecase subcommittee meeting 
14/05/2017 - Casablanca use cases/functional requirements endorsement
Hi all,

Here is the summary of our yesterday's meeting.
Thanks to all meeting participants!


1.   We have fully endorsed the following use cases/functional requirements:

a.   OSAM

b.  Auto Scaling out

c.   Consistent representation and identification of a cloud region in ONAP

d.  Edge Automation through ONAP



2.   5G group of functional requirements is endorsed, with the following 
exceptions:

a.   Terminology of SDN-R will be replaced by SDN-C, while it will be 
clarified what is the functionality of the SDN-C sub-module (used to be called 
SDN-R) to cover necessary enhancements

b.  SON and slice optimization topics will be re-discussed till next 
Monday's Usecase subcommittee meeting by all interested parties. There are 
concerns expressed by Cisco (Vladimir Yanover) which require additional 
discussions. We will monitor their progress and see if consensus is achieved or 
this issue needs to be raised and decided by the TSC



3.   Casablanca's HPA and Change Management authors - please upload your 
proposals under 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+endorsement.
 We will discuss them next Monday



4.   Cross Domain and Cross Layer VPN Service was presented for the first 
time yesterday. Some comments were received. Team will update according to the 
comments received and we will continue our discussion next Monday as well. 
Also, the team has asked for additional volunteering companies to participate 
in this development (please approach Lingli and Lin in case of interest)

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EDB8.E8F74180]

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

Re: [onap-tsc] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

2018-05-16 Thread Alla Goldner 
Hi Steve,

Sorry for omitting this from the summary, I will add it to the summary posted 
on wiki now.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EDB7.91CD3820]

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Thursday, May 17, 2018 12:34 AM
To: Alla Goldner ; onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
Subject: RE: [onap-tsc] The summary of Usecase subcommittee meeting 14/05/2017 
- Casablanca use cases/functional requirements endorsement

Hi Alla,

Thanks for the notes.

One clarification in the 5G group of functions - I recall correctly that SDN-R 
is to be replaced by SDN-C; and to extend that comment I also asked about the 
role of APPC (as that handles the higher layer VNFs) and the response was that 
is also a controller created from CCSDK (correct) and the split will be worked 
out in the architecture sub-committee.

BR,

Steve

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Tuesday, May 15, 2018 10:22 AM
To: onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: [onap-tsc] The summary of Usecase subcommittee meeting 14/05/2017 - 
Casablanca use cases/functional requirements endorsement

Hi all,

Here is the summary of our yesterday's meeting.
Thanks to all meeting participants!


  1.  We have fully endorsed the following use cases/functional requirements:
 *   OSAM
 *   Auto Scaling out
 *   Consistent representation and identification of a cloud region in ONAP
 *   Edge Automation through ONAP



  1.  5G group of functional requirements is endorsed, with the following 
exceptions:
 *   Terminology of SDN-R will be replaced by SDN-C, while it will be 
clarified what is the functionality of the SDN-C sub-module (used to be called 
SDN-R) to cover necessary enhancements
 *   SON and slice optimization topics will be re-discussed till next 
Monday's Usecase subcommittee meeting by all interested parties. There are 
concerns expressed by Cisco (Vladimir Yanover) which require additional 
discussions. We will monitor their progress and see if consensus is achieved or 
this issue needs to be raised and decided by the TSC



  1.  Casablanca's HPA and Change Management authors - please upload your 
proposals under 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+endorsement.
 We will discuss them next Monday



  1.  Cross Domain and Cross Layer VPN Service was presented for the first time 
yesterday. Some comments were received. Team will update according to the 
comments received and we will continue our discussion next Monday as well. 
Also, the team has asked for additional volunteering companies to participate 
in this development (please approach Lingli and Lin in case of interest)

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EDB7.91CD3820]

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
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] ONAP TSC Survey Results

2018-05-16 Thread Alla Goldner 
Hi Kenny,

Thanks a lot for sharing this!

I have 2 related questions:


1.   I see one proposal for exception “*Make the job role of “Release 
Manager”, which is an elected position, a TSC seat”. Have we ever discussed 
this? I don’t remember this being part of the survey

2.   If I remember correctly, there were also questions related to timing 
of elections – e.g. now, after Casablanca etc. I don’t see this reflected in 
the survey results.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EDB5.8B253010]

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kenny Paul
Sent: Thursday, May 17, 2018 3:43 AM
To: onap-tsc 
Subject: [onap-tsc] ONAP TSC Survey Results



Best Regards,
-kenny

Kenny Paul, Technical Program Manager, The Linux Foundation
kp...@linuxfoundation.org, 510.766.5945
San Francisco Bay Area, Pacific Time Zone


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
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

2018-05-16 Thread Dhananjay Pavgi 
Concur with views below from Shankar. Why confuse by changing it to SDN-C when 
we know it's functionality quite "Radio" and wireless domain specific.

thanks & regards,
Dhananjay Pavgi
+91 98220 22264

From: onap-tsc-boun...@lists.onap.org  On 
Behalf Of SHANKARANARAYANAN, N K (N K)
Sent: Thursday, May 17, 2018 8:39 AM
To: Alla Goldner ; onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
Subject: Re: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Alla,

I don't understand the decision to change the SDN-R term after the several 
discussions in the 5G and SDN-R groups
using this term to describe the single ONAP OA&M controller persona (derived 
from CC-SDK) for mobility and wireless PNF/VNFs.
The reasons were articulated in the discussions. There has been momentum in 
using the SDN-R term, and changing it to SDN-C now causes confusion.

Regards,

Shankar


From: 
onap-usecasesub-boun...@lists.onap.org
 [onap-usecasesub-boun...@lists.onap.org] on behalf of Alla Goldner 
[alla.gold...@amdocs.com]
Sent: Tuesday, May 15, 2018 4:21 AM
To: onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc
Subject: [Onap-usecasesub] The summary of Usecase subcommittee meeting 
14/05/2017 - Casablanca use cases/functional requirements endorsement
Hi all,

Here is the summary of our yesterday's meeting.
Thanks to all meeting participants!


1.   We have fully endorsed the following use cases/functional requirements:

a.   OSAM

b.  Auto Scaling out

c.   Consistent representation and identification of a cloud region in ONAP

d.  Edge Automation through ONAP



2.   5G group of functional requirements is endorsed, with the following 
exceptions:

a.   Terminology of SDN-R will be replaced by SDN-C, while it will be 
clarified what is the functionality of the SDN-C sub-module (used to be called 
SDN-R) to cover necessary enhancements

b.  SON and slice optimization topics will be re-discussed till next 
Monday's Usecase subcommittee meeting by all interested parties. There are 
concerns expressed by Cisco (Vladimir Yanover) which require additional 
discussions. We will monitor their progress and see if consensus is achieved or 
this issue needs to be raised and decided by the TSC



3.   Casablanca's HPA and Change Management authors - please upload your 
proposals under 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+endorsement.
 We will discuss them next Monday



4.   Cross Domain and Cross Layer VPN Service was presented for the first 
time yesterday. Some comments were received. Team will update according to the 
comments received and we will continue our discussion next Monday as well. 
Also, the team has asked for additional volunteering companies to participate 
in this development (please approach Lingli and Lin in case of interest)

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EDC2.9180EBE0]

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


Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at http://www.techmahindra.com/Disclaimer.html 
 externally 
http://tim.techmahindra.com/tim/disclaimer.html 
 internally within 
TechMahindra.


___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

2018-05-16 Thread SHANKARANARAYANAN, N K (N K) 
Alla,

I don't understand the decision to change the SDN-R term after the several 
discussions in the 5G and SDN-R groups
using this term to describe the single ONAP OA&M controller persona (derived 
from CC-SDK) for mobility and wireless PNF/VNFs.
The reasons were articulated in the discussions. There has been momentum in 
using the SDN-R term, and changing it to SDN-C now causes confusion.

Regards,

Shankar


From: onap-usecasesub-boun...@lists.onap.org 
[onap-usecasesub-boun...@lists.onap.org] on behalf of Alla Goldner 
[alla.gold...@amdocs.com]
Sent: Tuesday, May 15, 2018 4:21 AM
To: onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc
Subject: [Onap-usecasesub] The summary of Usecase subcommittee meeting 
14/05/2017 - Casablanca use cases/functional requirements endorsement

Hi all,

Here is the summary of our yesterday’s meeting.
Thanks to all meeting participants!


1.   We have fully endorsed the following use cases/functional requirements:

a.   OSAM

b.  Auto Scaling out

c.   Consistent representation and identification of a cloud region in ONAP

d.  Edge Automation through ONAP



2.   5G group of functional requirements is endorsed, with the following 
exceptions:

a.   Terminology of SDN-R will be replaced by SDN-C, while it will be 
clarified what is the functionality of the SDN-C sub-module (used to be called 
SDN-R) to cover necessary enhancements

b.  SON and slice optimization topics will be re-discussed till next 
Monday’s Usecase subcommittee meeting by all interested parties. There are 
concerns expressed by Cisco (Vladimir Yanover) which require additional 
discussions. We will monitor their progress and see if consensus is achieved or 
this issue needs to be raised and decided by the TSC



3.   Casablanca’s HPA and Change Management authors – please upload your 
proposals under 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+endorsement.
 We will discuss them next Monday



4.   Cross Domain and Cross Layer VPN Service was presented for the first 
time yesterday. Some comments were received. Team will update according to the 
comments received and we will continue our discussion next Monday as well. 
Also, the team has asked for additional volunteering companies to participate 
in this development (please approach Lingli and Lin in case of interest)

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EC3B.04166B00]

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
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

2018-05-16 Thread PUTHENPURA, SARAT (SARAT) 
Hi Alla,

That is not my understanding from the discussions in 5G use case forum.
This is my understanding:
SDN-R will continue to support 5G use case.
It will be using CCSDK and reusing applicable code (adaptors, mainly) from APPC.
SDN-R to be continued as a sub-project under SDN-C.

Thanks,
Sarat Puthenpura

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Stephen Terrill
Sent: Wednesday, May 16, 2018 5:34 PM
To: Alla Goldner ; onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
Subject: Re: [onap-tsc] The summary of Usecase subcommittee meeting 14/05/2017 
- Casablanca use cases/functional requirements endorsement

Hi Alla,

Thanks for the notes.

One clarification in the 5G group of functions - I recall correctly that SDN-R 
is to be replaced by SDN-C; and to extend that comment I also asked about the 
role of APPC (as that handles the higher layer VNFs) and the response was that 
is also a controller created from CCSDK (correct) and the split will be worked 
out in the architecture sub-committee.

BR,

Steve

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Tuesday, May 15, 2018 10:22 AM
To: onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: [onap-tsc] The summary of Usecase subcommittee meeting 14/05/2017 - 
Casablanca use cases/functional requirements endorsement

Hi all,

Here is the summary of our yesterday's meeting.
Thanks to all meeting participants!


  1.  We have fully endorsed the following use cases/functional requirements:
 *   OSAM
 *   Auto Scaling out
 *   Consistent representation and identification of a cloud region in ONAP
 *   Edge Automation through ONAP



  1.  5G group of functional requirements is endorsed, with the following 
exceptions:
 *   Terminology of SDN-R will be replaced by SDN-C, while it will be 
clarified what is the functionality of the SDN-C sub-module (used to be called 
SDN-R) to cover necessary enhancements
 *   SON and slice optimization topics will be re-discussed till next 
Monday's Usecase subcommittee meeting by all interested parties. There are 
concerns expressed by Cisco (Vladimir Yanover) which require additional 
discussions. We will monitor their progress and see if consensus is achieved or 
this issue needs to be raised and decided by the TSC



  1.  Casablanca's HPA and Change Management authors - please upload your 
proposals under 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+endorsement.
 We will discuss them next Monday



  1.  Cross Domain and Cross Layer VPN Service was presented for the first time 
yesterday. Some comments were received. Team will update according to the 
comments received and we will continue our discussion next Monday as well. 
Also, the team has asked for additional volunteering companies to participate 
in this development (please approach Lingli and Lin in case of interest)

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3ED50.2AF54500]

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
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] [onap-discuss] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

2018-05-16 Thread VAN BRAKLE, TRACY L 
Steve,
Alla,

Whatever we elect to call it, "SDN-R" is an ODL-based ONAP controller derived 
from CC-SDK that includes the logic & features/functionality of both SDN-C and  
APP-C, which are also derived from CC-SDK.

The "-R" connotes RAN, which is shorthand for Mobility & Fixed Wireless.

Referring to "SDN-R" as "SDN-C" would be misleading.  We could just as easily 
refer to the thing as "APP-R" (or perhaps "APP-C").

Until somebody comes up with a better nickname, let's continue using "SDN-R" 
unless there is a compelling technical reason not to, ok?

Tracy

From: onap-discuss-boun...@lists.onap.org  
On Behalf Of Stephen Terrill
Sent: Wednesday, May 16, 2018 5:34 PM
To: Alla Goldner ; onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
Subject: Re: [onap-discuss] [onap-tsc] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Hi Alla,

Thanks for the notes.

One clarification in the 5G group of functions - I recall correctly that SDN-R 
is to be replaced by SDN-C; and to extend that comment I also asked about the 
role of APPC (as that handles the higher layer VNFs) and the response was that 
is also a controller created from CCSDK (correct) and the split will be worked 
out in the architecture sub-committee.

BR,

Steve

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Tuesday, May 15, 2018 10:22 AM
To: onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
mailto:onap-tsc@lists.onap.org>>
Subject: [onap-tsc] The summary of Usecase subcommittee meeting 14/05/2017 - 
Casablanca use cases/functional requirements endorsement

Hi all,

Here is the summary of our yesterday's meeting.
Thanks to all meeting participants!


  1.  We have fully endorsed the following use cases/functional requirements:
 *   OSAM
 *   Auto Scaling out
 *   Consistent representation and identification of a cloud region in ONAP
 *   Edge Automation through ONAP



  1.  5G group of functional requirements is endorsed, with the following 
exceptions:
 *   Terminology of SDN-R will be replaced by SDN-C, while it will be 
clarified what is the functionality of the SDN-C sub-module (used to be called 
SDN-R) to cover necessary enhancements
 *   SON and slice optimization topics will be re-discussed till next 
Monday's Usecase subcommittee meeting by all interested parties. There are 
concerns expressed by Cisco (Vladimir Yanover) which require additional 
discussions. We will monitor their progress and see if consensus is achieved or 
this issue needs to be raised and decided by the TSC



  1.  Casablanca's HPA and Change Management authors - please upload your 
proposals under 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+endorsement.
 We will discuss them next Monday



  1.  Cross Domain and Cross Layer VPN Service was presented for the first time 
yesterday. Some comments were received. Team will update according to the 
comments received and we will continue our discussion next Monday as well. 
Also, the team has asked for additional volunteering companies to participate 
in this development (please approach Lingli and Lin in case of interest)

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3ED4D.D105F690]

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
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

2018-05-16 Thread Stephen Terrill 
Hi Alla,

Thanks for the notes.

One clarification in the 5G group of functions - I recall correctly that SDN-R 
is to be replaced by SDN-C; and to extend that comment I also asked about the 
role of APPC (as that handles the higher layer VNFs) and the response was that 
is also a controller created from CCSDK (correct) and the split will be worked 
out in the architecture sub-committee.

BR,

Steve

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Alla Goldner
Sent: Tuesday, May 15, 2018 10:22 AM
To: onap-usecase...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc 
Subject: [onap-tsc] The summary of Usecase subcommittee meeting 14/05/2017 - 
Casablanca use cases/functional requirements endorsement

Hi all,

Here is the summary of our yesterday's meeting.
Thanks to all meeting participants!


  1.  We have fully endorsed the following use cases/functional requirements:
 *   OSAM
 *   Auto Scaling out
 *   Consistent representation and identification of a cloud region in ONAP
 *   Edge Automation through ONAP



  1.  5G group of functional requirements is endorsed, with the following 
exceptions:
 *   Terminology of SDN-R will be replaced by SDN-C, while it will be 
clarified what is the functionality of the SDN-C sub-module (used to be called 
SDN-R) to cover necessary enhancements
 *   SON and slice optimization topics will be re-discussed till next 
Monday's Usecase subcommittee meeting by all interested parties. There are 
concerns expressed by Cisco (Vladimir Yanover) which require additional 
discussions. We will monitor their progress and see if consensus is achieved or 
this issue needs to be raised and decided by the TSC



  1.  Casablanca's HPA and Change Management authors - please upload your 
proposals under 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+endorsement.
 We will discuss them next Monday



  1.  Cross Domain and Cross Layer VPN Service was presented for the first time 
yesterday. Some comments were received. Team will update according to the 
comments received and we will continue our discussion next Monday as well. 
Also, the team has asked for additional volunteering companies to participate 
in this development (please approach Lingli and Lin in case of interest)

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3ED6E.675FBF70]

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
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] FW: [Onap-arch-tiger-team] Canceled: ONAP R3+ Architecture Tiger Team Weekly Call

2018-05-16 Thread Parviz Yegani 
Fyi...

From: onap-arch-tiger-team-boun...@lists.onap.org 
[mailto:onap-arch-tiger-team-boun...@lists.onap.org] On Behalf Of Parviz Yegani
Sent: Wednesday, May 16, 2018 5:17 AM
To: 'onap-arch-tiger-t...@lists.onap.org' 
Subject: Re: [Onap-arch-tiger-team] Canceled: ONAP R3+ Architecture Tiger Team 
Weekly Call

Hi Folks,

Next week's tiger team call is cancelled due to the OpenStack summit. Many of 
us are going to be in Vancouver for the summit. As you may know during the 
summit we will have a full-day ONAP Architecture session on Wed, May 23rd.

Please plan on attending.

Regards,
Parviz

---
PARVIZ YEGANI, PhD
Chief SDN/NFV Architect
CTO Office, Cloud Network Solutions

FutureWei Technologies, Inc.
2330 Central Express Way
Santa Clara, CA 95050, USA
Phone: +1 (408) 330-4668
Mobile : +1 (408) 759-1973
parviz.yeg...@huawei.com




-Original Appointment-
From: Parviz Yegani [mailto:parviz.yeg...@huawei.com]
Sent: Wednesday, May 16, 2018 4:39 AM
To: 'onap-arch-tiger-t...@lists.onap.org'
Cc: 'Stephen Terrill'; 'Wang, Le (Nokia - FI/Helsinki)'; 'BEGWANI, VIMAL'; 
'Pieczerak Janusz - Korpo'; Patrick Liu; 'Nemeth, Denes (Nokia - HU/Budapest)'; 
'Ramki Krishnan'; 'Lawrence Lepine'; 'Davis, Nigel'; 'Vul, Alex'; 
'mourad.ta...@verizon.com'; 'MAYER, ANDREW J'; 'Manoj K Nair'; 
'jamil.cha...@orange.com'; 'wangchen...@chinamobile.com'
Subject: [Onap-arch-tiger-team] Canceled: ONAP R3+ Architecture Tiger Team 
Weekly Call
When: Monday, May 21, 2018 5:00 AM-6:00 AM (UTC-08:00) Pacific Time (US & 
Canada).
Where: https://zoom.us/j/112544167
Importance: High


Hi All,

Per the result of the new doodle poll I am sending this invite for the 
architecture tiger team weekly call. The call will now be held every Monday 
5:00 AM - 6:00 AM PDT.

I will cancel all instances of the old meeting. Please make sure to update your 
calendar accordingly.

Thanks,
Parviz

I'll post a more detailed agenda prior to each meeting.
---
Agenda
* Review ONAP architecture contributions,
* Contributions are located at:,
https://wiki.onap.org/display/DW/Architecture+Tiger+Team

---
https://zoom.us/j/112544167
US numbers:
+1 646 558 8656 or +1 669 900 6833
Meeting ID: 112 544 167
International numbers available: 
https://zoom.us/zoomconference?m=D_WZofsWmNr8ZvyR_5uMQv1i2yKSoUpS

Please come prepared.

Thanks,
Parviz


  << File: ATT2.txt >>

___
Onap-arch-tiger-team mailing list
onap-arch-tiger-t...@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-arch-tiger-team
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc