Agreed. This appears to be a significant change to the existing architecture, and should be discussed with the wider community. Let me know when you're ready, and I'll allocate a slot on the agenda.
Chris From: <[email protected]<mailto:[email protected]>> on behalf of Stephen Terrill <[email protected]<mailto:[email protected]>> Date: Wednesday, May 30, 2018 at 10:14 AM To: "VAN BRAKLE, TRACY L" <[email protected]<mailto:[email protected]>>, Parviz Yegani <[email protected]<mailto:[email protected]>>, "Ranganathan, Raghu" <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "TIMONEY, DAN" <[email protected]<mailto:[email protected]>>, "SMITH JR., PAUL" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, onap-tsc <[email protected]<mailto:[email protected]>> Subject: Re: [onap-tsc] [Onap-usecasesub] [**EXTERNAL**] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement Hi, The current practice we have is that these are taken in the Tuesday Architecture meetings as is done with other use cases with architecture considerations. Chris? BR, Steve From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of VAN BRAKLE, TRACY L Sent: Wednesday, May 30, 2018 12:15 PM To: Parviz Yegani <[email protected]<mailto:[email protected]>>; Ranganathan, Raghu <[email protected]<mailto:[email protected]>> Cc: TIMONEY, DAN <[email protected]<mailto:[email protected]>>; SMITH JR., PAUL <[email protected]<mailto:[email protected]>>; onap-tsc <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: Re: [onap-tsc] [Onap-usecasesub] [**EXTERNAL**] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement Parviz, Raghu, Please join the weekly SDN-R call (see below) to discuss this topic. We can allow 15 or 20 minutes on the agenda for the call today, May 30th, or for the call next week, June 6th - just let me know your preference. Thank you in advance, Tracy Tracy Van Brakle <[email protected]<mailto:[email protected]>> AT&T Labs - Wireless Network Architecture and Design +1 732.420.3003 office +1 732.306.2387 cell [sdnr] team meeting (updated Apr. 3, 2018) When Weekly from 9am to 10am on Wednesday from Wed Apr 4 to Wed Mar 13, 2019 Pacific Time Where https://zoom.us/j/502876187<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_502876187&d=DwQFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=7TfzZqNtM8rzzpoqgbTKTw&m=AHXO5YHRW_Gzfg7saO8FEW35tAJwGEXy3BnSeOEsA1E&s=z3Du9SfpzoCOGcpc-3C2At0v8ZB2iO0YQkVcZPhCfZA&e=> (map<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fj-252F502876187-26sa-3DD-26usd-3D2-26usg-3DAFQjCNGBy9wN4iPnChWbXF4om9L8rybi9A&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=7TfzZqNtM8rzzpoqgbTKTw&m=AHXO5YHRW_Gzfg7saO8FEW35tAJwGEXy3BnSeOEsA1E&s=IGK8tA7A0zQa4qBM1pNLcC3qERjT55I1_NHRjuQOFPw&e=>) Calendar [email protected]<mailto:[email protected]> From:[email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Parviz Yegani Sent: Wednesday, May 30, 2018 2:03 AM To: Ranganathan, Raghu <[email protected]<mailto:[email protected]>> Cc: TIMONEY, DAN <[email protected]<mailto:[email protected]>>; onap-tsc <[email protected]<mailto:[email protected]>>; Dhananjay Pavgi <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: Re: [Onap-usecasesub] [**EXTERNAL**] [onap-tsc] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement Hi Raghu, I think we need to have a call to discuss SDN-R and it’s relation to SDN-C. I’ll be happy to send an invite for this. How about Thursday, 1:00PM Pacific? 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 [email protected]<mailto:[email protected]> From: Ranganathan, Raghu [mailto:[email protected]] Sent: Tuesday, May 22, 2018 5:39 PM To: Parviz Yegani <[email protected]<mailto:[email protected]>> Cc: TIMONEY, DAN <[email protected]<mailto:[email protected]>>; Alla Goldner <[email protected]<mailto:[email protected]>>; Vladimir Yanover (vyanover) <[email protected]<mailto:[email protected]>>; Dhananjay Pavgi <[email protected]<mailto:[email protected]>>; SHANKARANARAYANAN, N K <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; onap-tsc <[email protected]<mailto:[email protected]>> Subject: Re: [**EXTERNAL**] [Onap-usecasesub] [onap-tsc] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement PY> DG config node in SDN-C is enhanced to enable 3rd party controllers I don’t think that is the right conclusion. Dan’s email had “a number of new components to SDNC”. So, I think Dan is referring to additional functions/apps in SDN-C (ODL). Depending on which set of functions/apps are needed, the role of ODL instances changes, ie., vanilla L0-3 vs vanilla L4-7 ….vs radio vs shortest-path-icecream-delivery vs….combinations, etc.. Hence, not an external 3rd party controller. SDN-R is either another controller in ONAP (if separation of work) or existing SDN-C/App-C (if just another app). Maybe, ONAP architecture diagram needs to show ’SDN-C/type1, SDN-C/type2, SDN-C/type3….etc.’….versus only 2 (SDN-C/APP-C). Of course, the ‘functions/apps’ enhancements would mostly be domain specific yang models (service/network) and directed graph nodes to execute. But could be others…. —Raghu [extraneous text deleted]
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
