Hi Dan, Since we will be maintaining only the bierman-draft style RESTCONF API from ODL and not the entire ODL codebase so my suggestion for name is: ccsdk/odl-legacy-bireman-draft Regards, Vishal Var

#ccsdk

Hi Dan. If you plan to include documentation to the repo that should show up in ReadTheDocs, please add ccsdk/odl-legacy to the CCSDK section in https://wiki.onap.org/x/EYAMC . Best regards, Thomas Ku

#ccsdk

CCSDK team, As many of you are aware, we have a need to create a new repository in CCSDK to take over support for OpenDaylight modules that we still need, but which are no longer supported in the “off

#ccsdk

CCSDK/SDNC Users: This is to advise you of an upcoming change in the OpenDaylight platform which will introduce breaking changes for some users of our RESTCONF interface. This change will NOT impact o

#ccsdk #sdnc

CCSDK/SDNC team, Our weekly call this week – 6/15 – is cancelled due to conflict with the DTF event in Porto, Portugal this week. Talk you all next week! Dan

#sdnc #ccsdk

Thanks Martin for the clarification. Regards, Niranjana

#sdnc #sdnr #ccsdk

Hi Niranjana, The "network-map" icon will be removed in future versions. Background the data to be displayed is not "open" we are not allowed to share such data in LFN repos. Therefore the team has de

#sdnc #sdnr #ccsdk

Hi All, I was trying to view the network map page in the ODLUX app, its not able to load the network data and was displaying the error as shown in the screenshot. I had checked many wiki pages but I c

#sdnc #sdnr #ccsdk

CCSDK/SDNC team, Please note that the bridge for our weekly calls has CHANGED for 2022. The new Zoom meeting link is: https://zoom.us/j/93528690549?pwd=RE5KaEJsRTcra25JU0VTZmZoZndvdz09 Talk to you tom

#ccsdk #sdnc

CDS team, Please note that the Zoom meeting bridge has CHANGED for 2022. The new link is: https://zoom.us/j/99098594837?pwd=cmkwWDJIUHhCOVF0dVpXclFKL3Rzdz09 Thanks! Dan

#cds #ccsdk

CCSDK/SDNC team, Sorry for the late notice, but I need to cancel our weekly CCSDK/SDNC call today due to a conflict. Dan

#ccsdk

CCSDK/SDNC team, I’ll be on vacation next week, so there will be no ccsdk/sdnc call next week. We’ll meet again on Weds 12/1. Thanks! Dan

#ccsdk #sdnc

Hi, But you have more than one policy. One reason that your problem may occur can be that you have policies with identical contents. Then the simulator will reject the PUT like in your case. Therefore

#ccsdk #a1

Hi Patrik, PFA of the application_configuration.json file which we are using currently and earlier what I sent was not having an IP address only. Please find below policy payload { "policy_id": "first

#ccsdk #a1

Hi, It is clear that the second policy is rejected by the simulator for some reason. If the contents of 2 policies are identical, the simulator will reject. If the synchronization fails (like in this

#ccsdk #a1

Hi, From the logs we can see that the synchronizations fails because the simulator rejects the PUT of the second policy. Fault code 400 is returned from the NearRT Simulator (using the OSC A1 API) whe

#ccsdk #a1

Hi Patrik , PFA of policy schema for policy type id 20000 which is used in ric2 and ric3 @John Keeny, PFA of applicaion_configuration.json file and yes we have 2 rics of A1 simulator and 1 ric is ente

#ccsdk #a1

Hi Vishal Thanks for sending the logs. We are checking your logs now. Please also forward your configuration file ("application_configuration.json") From your log file you seem to have 3 rics. Can you

#ccsdk #a1

Hi Team, I have a query on usage of A1-Policy-Management-Service which I have mentioned on onap wiki at below link. https://wiki.onap.org/display/DW/O-RAN+A1+Policies+in+ONAP+Honolulu with respect to

#ccsdk #a1

Ccsdk / SDNC team I will be on vacation this week, so am canceling our call for 6/2. I also need to cancel our call on 6/9 due to conflict with the June LFN DDF event. We’ll meet next on 6/16. Dan Sen

#ccsdk #sdnc