Hi Michal,
The SDN Agent project is not part of ONAP.
SDNC component is actually the global controller which is used to integrate
with 3rd party SDN controllers potentially such as ONOS
So you should investigate it , e.g. adding generic plugin which call ONOS.
Notices that ccsdk project is
Adding the help desk
From: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Sauvageau, David
Sent: Wednesday, August 2, 2017 5:07 PM
To: onap-discuss@lists.onap.org; Kenny Paul
Subject: [onap-discuss] [OOM] urgent: can't
for creating the per application files.
https://wiki.onap.org/pages/worddav/preview.action?fileName=ONAP+CM+v3.pptx=8229355
Thanks,
Avi Chapnick
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at https
Hi,
Some of the questions below refers to SDNC managed devices YANG schemas , which
ODL gets from the devices once the device is mounted.
Are we planning to allow getting customized version of those schemas from SDC
for allowing fixing problems on the managed devices yang?
Some of the
Hi,
Reading the project scope it seems to me a real time configuration repository
for external system location and credential specifically for VIM.
Probably this should be part of the multi-vim project which should own and
manage this configuration.
I assume that the component which is used
Re the integration between NFVO and GVNFM , it's done via the MS layer
More specifically lcm/pub/msapi/vnfmdrive.py
Its build a URL, where the VNFM should be available , and execute it.
Avi,
From: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of