Architecture Changes since Beijing

  1. New repositories added :
    1. sdnc/apps : for applications intended to run outside of OpenDaylight container, such as microservices
    2. sdnc/features : for code intended to be deployed as Karaf features that is not related to the Service Logic Interpreter (SLI) infrastructure
  2. Ansible server support:
    1. In Beijing, SDNC took a copy of APPC's Ansible server and wrapped it as a docker container to support Change Management functional requirements.  In Casablanca, this code will be refactored, with a base docker container in CCSDK for the Ansible server itself, and then SDNC and APPC will create their own docker containers for their project-specific needs.

S3P Updates

  1. Resiliency : significantly improved startup time for OpenDaylight container.  Optional support for geo-redundancy (see SDNC: Geo-redundancy Enhancements)
  2. Security : focusing on closing critical vulnerabilities under our control.  
  3. CII Badging status : CII Best Practices

IM/DM Alignment

  1. SDNC uses standard TOSCA models distributed by SDC to drive processing of its "generic resource" API.

API updates

  1. Most APIs are stable.  New interface to OOF still in progress.
  2. All APIs have Swagger documentation, which is referenced in readthedocs (see https://onap.readthedocs.io/en/latest/submodules/sdnc/oam.git/docs/offeredapis.html)

  • No labels