Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

« Previous Version 17 Next »

STATUS: Under Construction

SDN-C / App-C:


1 High Level Component Definition and Architecteral Relationships 



ONAP Controller Family (SDN-C / App-C) configures and maintains the health ofL1-7 Network Function (VNF, PNF, CNFs) and network services throughout their lifecycle
  • Configure Network Functions (VNF/PNF)
  • Provides programmable network application management platform:
    • Behavior patterns programmed via models and policies
    • Standards based models &protocols for multi-vendor implementation
    • Extensible SB adapters such as Netconf, Ansible, Rest API, etc.
    • Operational control, version management, software updates, etc.
  • Local source of truth
    • Manages inventory within its scope
    • Manages and stores state of NFs
    • Supports Configuration Audits

2. SDN-C API definitions

Controller provides the following interfaces:

Interface NameInterface Definition Interface Capabilities
CONE-1OSS Interface

An interface to request for Lifecycle management operations on network resources

CONE-2Operations Interface

An interface to request for Lifecycle management operations on network resources

CONE-3Service Order Interface

 An interface to request for Configuration and Lifecycle management operations on network resources

CONE-4Policy Interface

 An interface to support LCM requests such as Restart, Rebuild, Migrate, Evacuate operations on network resources

The current API documents can be found at:

https://onap.readthedocs.io/en/casablanca/submodules/appc.git/docs/index.html

Controller consumes the following interfaces:

Interface NameInterface Definition Interface Capabilities
CONE-5Rest APIAn interface for communication with external systems such as IP management
CONE-6Resource Chef APIAn interface for configuration and Lifecycle management of network resources using Chef protocol
CONE-7Resource NetConf APIAn interface for configuration and Lifecycle management of network resources using NetConf protocol
CONE-8Resource Ansible APIAn interface for configuration and Lifecycle management of network resources using Ansible protocol
SDCE-6SDC Interface

An interface to receive resource Templates from SDC design catalog

CDSE-1CDS Interface

An interface to receive resource blueprint from CDS

AAIE-1Inventory Service Interface

 An interface to create, update, query, and delete resource information and relationships

POE-2aPDP Query API

 Policy Decision Point query for IP address


3. Component Description:


4. known system limitations

  • Lack of clarity & roles in the controller (which controller does what?)
  • Proliferation of controller instances (many similar yet different controller instances)
  • Divergence of controller implementation (lack of common controller framework)
  • Duplicate and uncoordinated interfaces (lack of uniform common services in southbound interfaces)
  • Controller resiliency and horizontal scaling

5. Used Models

Controllers use the following models:

  • TOSCA
  • YANG

6. System Deployment Architecture


Clamp consists of 4 containers:

  • CLAMP container
  • MariaDB container
  • Kibana ontainer
  • E_Search ontainer
  • LogStash container 

7. New Release Capabilities

Upgrade of ODL to Fluorine SR2

Change Management use case support

Closed loop use case support

Platform maturity advancement (Scalability, Stability, Security, and Performance) 

Network discovery enhancements



8. References

  1.  CLAMP Overview & User Guide: https://onap.readthedocs.io/en/latest/submodules/clamp.git/docs/index.html 
  2. CLAMP internal interfaces:  https://onap.readthedocs.io/en/latest/_downloads/d3c9f924c6586fe411d40a05ad9b1bb7/swagger.pdf 



  • No labels