STATUS: Under Construction

SDN-C / App-C:

1 High Level Component Definition and Architecteral Relationships

<< Short description

Controller provides the following interfaces:

Interface Name	Interface Definition	Interface Capabilities
CONE-1	OSS Interface	An interface to request for Lifecycle management operations on network resources
CONE-2	Operations Interface	An interface to request for Lifecycle management operations on network resources
CONE-3	Service Order Interface	An interface to request for Configuration and Lifecycle management operations on network resources
CONE-4	Policy Interface	An interface to support LCM requests such as Restart, Rebuild, Migrate, Evacuate operations on network resources
CONE-5	Resource Rest API	An interface for configuration and Lifecycle management of network resources using REST protocol
CONE-6	Resource Chef API	An interface for configuration and Lifecycle management of network resources using Chef protocol
CONE-7	Resource NetConf API	An interface for configuration and Lifecycle management of network resources using NetConf protocol
CONE-8	Resource Ansible API	An interface for configuration and Lifecycle management of network resources using Ansible protocol

Note: xxxI interface is a internal interface. xxxxE interface is a external interface

The current API documents can be found at:

xxxx consumes the following Interfaces:

Interface Name	Purpose Reason For Use
SDCE-6	To Recieve the Control Loop Blueprint from SDCTo recieve
PolicyE-2	To create and configure the closed Loop Operational Policies
DCAEE-x	Retrieve DCAE appplication status
DCAEE-y	Deploy/remove DCAE application.

A more detailed figure and description of the component.

<< For later inclusion >>

Runtime: None

Clamp data redundancy is dependant on kubernetes and the persisten volume.

Clamp appliation redundancy HA reliease on kubernetes

Clamp uses the following models:

Clamp consists of 4 containers:

<<>>