Each project should have its own page with all of the associated project pages / attachments under it.

SDNC Approved Project Proposal

Release Planning

Amsterdam Release

B Release

C Release


SDNC Weekly Meeting

UTC 1:00 PM - 2:00 PM
PST  6:00 AM - 7:00 AM
EST  9:00 AM - 10:00 AM

Zoom meeting. Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/330824945 Or iPhone one-tap (US Toll): +16465588656,,330824945# or +14086380968,,330824945# Or Telephone: Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll) +1 855 880 1246 (US Toll Free) +1 877 369 0926 (US Toll Free) Meeting ID: 330 824 945 International numbers available: https://zoom.us/zoomconference?m=rRItS256rDo_7UtkIznpz4jzZNmjTfbO

Meeting Minutes 


Link to SDNC APIs Page (Included below)

    • DMAAP listener : used to listen for event notifications from DMaaP. 
      •   For Amsterdam release, the vCPE use case posts a notification to DMAAP that alerts SDNC when a BRG receives an IP from DHCP.  The DMaap listener then will invoke the GENERIC-RESOURCE-API to set up a WAN connection for that BRG.
      • For Beijing release, SDN-C will also subscribe to an additional topic on DMaaP to receive LCM events, which will in turn invoke the LCM API.
    • New for Beijing release:
      • LCM (Lifecycle Management) API - used in Change Management and Manual Scale Out functional requirements to allow SDNC to process lifecycle events for L1-L3 VNFs.
      • The same rest api northbound is used in both SDNC (L1-L3) and APPC (L4-L7) - auto-generated from LCM-API.yang but the "action" parameters that can be sent via that API - some dont work on SDNC like start/stop/restart/evacuate - others like ModifyConfig will work on SDNC
      • See APP-C LCM API guide for additional information

  • Outgoing API:
    • A&AI : SDNC will read/write objects to A&AI.  The base aaa-service class is capable of reading/writing any object defined in A&AI XSD schema.  The directed graphs for the use cases will drive which specific objects are read/written.
    • External SDNC controllers : SDNC will interface to external SDNC controllers to create underlay/overlay networks (for VoLTE).  These external controllers expose a RESTCONF interface, which SDNC will invoke using its restapi-call-node interface.

APIs used by client projects:

Client ProjectAPI(s) used

Generic VNF API (vDNS, vFW, vCPE)


DMaaPDMaaP Listener
SDCSDC client

  • No labels


  1. Is it possible to integrate ONAP with ONOS controller (instead of ODL), is there a specific tutorial or document that describes how I could combine ONOS with ONAP?  In the project proposal I find a mention that SDN-C will support the ability to invoke other local SDN controllers, including third party SDN controllers. A tutorial or document explanation on this would be appreciated. 

  2. Could you please share the document link for adding third party SDN controllers