You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

As part of the ONAP Amsterdam release, the seed code that was originally contributed in March for form the basis of the SDNC project is being refactored into 2 projects:

  • Code related to the underlying platform which should be shared across controllers (e.g. SDNC, APP-C) is being moved to the new Common Controller SDK (CCSDK) project
  • Code related to the ONAP SDN Controller itself (that is, code that implements a specific network controller) will remain in the SDNC project


To allow for backward compatibility, the original SDNC seed code will remain in the SDNC ONAP repository for release 1, but will be deprecated.  It is anticipated that this code will be removed in the Beijing release.


Clients of these classes will need to:

  • Update the parent pom if they are currently using the org.openecomp.sdnc.core/root as their parent.   CCSDK has a separate repository (ccsdk/parent) for root poms.  We plan to offer several different parent poms, based on the OpenDaylight release they support.  The following table shows the currently supported parent POMs and which should be used for each supported OpenDaylight release
OpenDaylight releaseParent pom
Boron SR3
<parent>
    <groupId>org.onap.ccsdk.parent</groupId>
    <artifactId>odlparent-boron-sr3</artifactId>
    <version>0.0.1-SNAPSHOT</version>
</parent>


Carbon SR1*
<parent>
    <groupId>org.onap.ccsdk.parent</groupId>
    <artifactId>odlparent-carbon-sr1</artifactId>
    <version>0.0.1-SNAPSHOT</version>
</parent>


    • Note: at this writing, the Carbon port is still underway and the Carbon root pom is not yet available.  This page will be updated when it is available for use.


  • Update to use the new Maven artifacts, which will retain the same artifactId but will have a new groupId, which changes from org.openecomp.sdnc.* to org.onap.ccsdk.sli.* and to use the new package names. The following table lists the mappings of SDNC seed repositories to CCSDK repositories for the code that is moving.  Clients should note that the maven groupIds and Java package names are impacted by this change, which is needed to move from the old org.openecomp name to org.onap.



Seed codeAmsterdam release
FeatureGerrit repoMaven groupIdJava packageGerrit repoMaven groupIdJava package
dblibsdnc/coreorg.openecomp.sdnc.coreorg.openecomp.sdnc.sli.resource.dblibccsdk/sli/coreorg.onap.ccsdk.sli.coreorg.onap.ccsdk.sli.core.dblib
filterssdnc/coreorg,openecomp.sdnc.coreorg.openecomp.sdnc.filtersccsdk/sli/coreorg,onap.ccsdk.sli.coreorg.onap.ccsdk.sli,core.filters
slisdnc/coreorg.openecomp.sdnc.coreorg.openecomp.sdnc.sliccsdk/sli/coreorg.onap.ccsdk.sli.coreorg.onap.ccsdk.sli.core.sli
sliapisdnc/coreorg,openecomp.sdnc.coreorg.openecomp.sdnc.sliapiccsdk/sli/coreorg.onap.ccsdk.sli.coreorg.onap.ccsdk.sli.core.sliapi
sliPluginUtilssdnc/coreorg.openecomp.sdnc.coreorg.openecomp.sdnc.sli.SliPluginUtilsccsdk/sli/coreorg,onap.ccsdk.sli.coreorg.onap.ccsdk.sli.core.slipluginutils
aai-servicesdnc/adaptorsorg,openecomp.sdnc.adaptorsorg.openecomp.sdnc.sli.aaiccsdk/sli/adaptorsorg.onap.ccsdk.sli.adaptorsorg.onap.ccsdk.sli.core.adaptors.







  • No labels