STATUS: Under Construction

SDN-C / App-C:

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 same function).  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.

1 High Level Component Definition and

...

Architectural Relationships 

...

6. System Deployment Architecture

Clamp consists of 4 containersController consists of the following containers:

• CDS-UI container - Design Time
• SDC-CDS Listener 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 
• CLAMP container
• MariaDB container
• Kibana ontainer
• E_Search ontainer
• LogStash container 

7. New Release Capabilities

...