Hello there,
I have one question (possibly stupid one, sorry for that).
You wrote that SDN-R will be SDN-C + APP-C functionality but for Mobility
Wireless. Does that mean, that these functions can't be provided by some
combination/cooperation of SDN-C and APP-C themselves?
Regards
Andrej Záň
Od: VAN BRAKLE, TRACY L
Odoslané: štvrtok, 3. mája 2018 15:07
Komu: Vladimir Yanover (vyanover); BEGWANI, VIMAL; Stephen Terrill; Alla
Goldner; onap-usecase...@lists.onap.org
Kópia: onap-...@lists.onap.org; onap-discuss@lists.onap.org;
onap-...@lists.onap.org
Predmet: Re: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of
30/4/2018 - the summary
Vladimir,
As of now, the expectation is that all categories of parameters would be
supported by the ONAP controller derived from CC-SDK for Mobility Wireless.
We have dubbed this controller “SDN-R,” as you know, because this particular
label has meaning (traction, actually) within both ONAP and ONF.
SDN-R = SDN-C + APP-C for Mobility Wireless, in other words.
What we do not yet know is what will be configured via Netconf/YANG versus what
will be configured via Ansible, but I believe the community will have this
question answered fairly early within the Casblanca release timeframe.
Tracy
From: Vladimir Yanover (vyanover)
Sent: Thursday, May 03, 2018 4:09 AM
To: VAN BRAKLE, TRACY L ; BEGWANI, VIMAL ;
Stephen Terrill ; Alla Goldner
; onap-usecase...@lists.onap.org
Cc: onap-...@lists.onap.org; onap-discuss@lists.onap.org;
onap-...@lists.onap.org
Subject: RE: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of
30/4/2018 - the summary
Tracy, Steve and Vimal
I have to admit that I am confused as well and need your help.
Which categories of parameters will be supported by the SDN-R?
Which categories of “the parameters needed for DU & CUs” cannot be supported by
the SDN-R (why?) and will be supported by the APP-C?
Thanks
Vladimir
From:
onap-usecasesub-boun...@lists.onap.org<mailto:onap-usecasesub-boun...@lists.onap.org>
mailto:onap-usecasesub-boun...@lists.onap.org>>
On Behalf Of VAN BRAKLE, TRACY L
Sent: Thursday, May 3, 2018 12:04 AM
To: BEGWANI, VIMAL mailto:vb1...@att.com>>; 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@lists.onap.org<mailto:onap-discuss@lists.onap.org>;
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Subject: Re: [Onap-usecasesub] [onap-discuss] Usecase subcommittee meeting of
30/4/2018 - the summary
Whatever we elect to call it, “SDN-R” in Casablanca is evolving to include all
(or most) logic + features/functionality derived from CC-SDK, whether
considered “SDN-C” or “APP-C.” This will include Ansible and Chef interfaces
as well as the additional parameters that may be defined/documented within ONAP
or within a related open source project.
Refer to the “ONAP OAM Controller” slides on SDN-R wiki page
(https://wiki.onap.org/display/DW/SDN-R+Documents<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_SDN-2DR-2BDocuments&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=7TfzZqNtM8rzzpoqgbTKTw&m=Q5JxkgYqaNRcy-dbGrOPxcUcPx4i1VI3cGkYOqVGzy4&s=qCAHXnOCV8awLKHYscHZRvZJhSVb4tTkGsxyJCDbsZs&e=>)
that were reviewed with you and with others last month.
The seed code is already packaged and will be uploaded to the repository as
soon as it becomes available.
From:
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>
mailto:onap-discuss-boun...@lists.onap.org>>
On Behalf Of BEGWANI, VIMAL
Sent: Wednesday, 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@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 ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
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 controllers (as we might combine CU-UP,
a RAN element, with UPF, a core elements). Hence, we need some of the
capabilities from SD
