ednesday, May 02, 2018 4:30 PM
To: Stephen Terrill
mailto:stephen.terr...@ericsson.com>>; Alla
Goldner mailto:alla.gold...@amdocs.com>>;
onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Cc: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>;
onap-discuss
ap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; onap-discuss@lists.onap.org;
onap-...@lists.onap.org
Subject: RE: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of
30/4/2018 - the summary
Whatever we elect to call it, "SDN-R" in Casablanca is evolving to include
tephen.terr...@ericsson.com>>; Alla
Goldner mailto:alla.gold...@amdocs.com>>;
onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Cc: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>;
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.o
s@lists.onap.org<mailto:onap-discuss@lists.onap.org>;
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Subject: Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of
30/4/2018 - the summary
***Security Advisory: This Message Originated Outside of AT&T ***
Refe
t;>; Alla
Goldner mailto:alla.gold...@amdocs.com>>;
onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Cc: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>;
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>;
onap-...@lists.
nap-...@lists.onap.org<mailto:onap-...@lists.onap.org>;
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>;
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Subject: Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of
30/4/2018 - the s
lists.onap.org;
onap-...@lists.onap.org
Subject: Re: [onap-discuss] [Onap-usecasesub] Usecase subcommittee meeting of
30/4/2018 - the summary
***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Steve,
We
Hi Vimal,
Thanks for the reply. Can you please elaborate on the motivation that 1. It
has to be one controller and 2. Why the SDN-C and APP-C is insufficient.
While I appreciate the value of creating controller persona's from CCSDK, I see
a headacke in bringing these persona variants into the
Steve,
We have a SDN-C sub-project called SND-R, that focuses on radio configuration
using NetConf Yang, but it did not cover all the parameters needed for DU & CUs
(and UPF) and need support Ansible. We also realized that all mobility network
elements should be managed by the same controller