...

Note:  ONAP has two application level configuration and lifecycle management modules called SDN-C and App-C. Both provide similar services (application level configuration using NetConf, Chef, Ansible, RestConf, etc.) and life cycle management functions (e.g. Stop, resume, health check, etc.).  They share common code from CCSDK repo.  However, there are some differences between these two modules (SDN-C uses CDS only for onboarding and configuration / LCM flow design, whereas App-C uses CDT for the LCM functions for self service to provide artifacts storing in APP-C Database).  SDN-C has been used mainly for Layer1-3 network elements and App-C is being used for Layer4-7 network functions.  This is a very loose distinction and we expect that over time we will get better alignment and have common repository for controller code supporting application level configuration and lifecycle management of all network elements (physical or virtual, layer 1-7).  Because of these overlaps, we have documented SDN-C and App-C together.

...

• CDS-UI container - Design Time
• SDC-CDS Listener container - Design Time
• CDT-UI container - Design Time
• Controller Blueprint MS Container - Design Time
• Blueprint Processor MS Container - Run Time
• Command Executor Container - Run Time
• CDS Database Container - Run Time
• DG Builder Container - Design Time
• Admin Portal Container - Run Time
• SDC Listener Container - Run Time
• DMAAP Listener Container - Run Time
• Controller (ODL) Container - Run Time
• Network Name Gen MS Container - Run Time
• Ansible Server Container - Run Time
• MariaDB Galera - Platform Service
• Netbox - Platform Service 
• RunTime Config DB - Run Time
• A1 Polict Manager - Run Time

7. New Release Capabilities

• Upgrade of ODL to Aluminum Silicon SR (Service Release) 2Upgrade to Java 11 / Python 3.This was mostly completed in Guilin, but some cleanup is needed
• Removal of Java 8 / Python 2 executables
Upgrade to Python 3.91
• OpenDaylight separation:
  • In Honolulu release, SDNC will have

    For Istanbul, we plan to provide 2 implementations of

    its generic resource

    GENERIC-RESOURCE-API:

    • The current ODL-based implementationimplementation, implemented as an OSGi feature deployed in the OpenDaylight karaf container.
    • A new springboot-based implementationmicroservice, which runs in a pod outside of OpenDaylight

    We

    plan to test both versions to validate completeness of

    eventually would like to replace the current implementation with the springboot-based implementation, and run OpenDaylight as a separate pod.  However, there is still some work required to close feature gaps in the springboot-based implementation

    .  If successful, we would deprecate the ODL based version in Istanbul and remove it in Jakarta.
  Note: RunTime Config DB in CCSDK has been replaced by the standalone project CPS.

  • before we can do so without breaking existing functionality. 

    In Istanbul, we plan to conduct a proof of concept of the work done to date.  For this proof of concept, we will replace the SDNC controller in our local kubernetes test environment with the springboot-based version and run the standard OOM gating test suite to determine whether that the implementation to date is fully backwards compatible.  Any issues identified will be tracked in Jira so that we can plan to close any gaps discovered so that we can plan to introduce our springboot-based platform as the default SDNC implementation in Jakarta.

     

8. References

1.  APP-C overview & User Guide: https://docs.onap.org/en/casablanca/guides/onap-developer/developing/index.html#application-controller
2. SDN-C overview & User Guide:  https://docs.onap.org/en/casablanca/guides/onap-developer/developing/index.html#software-defined-network-controller

...