spec

ControllerDomainManager Specification

Managed Elements

Measurement, Monitoring and Implementation are not included in the v1.0.0_spec.  
Please, ignore the Managed Elements segment during implementing v1.0.0_impl.  

• The following kinds of Elements are encapsulated:
  • Controller
    • OpenDaylight
  • LoadBalancer
    • nginx
• The following kind of Endpoint is managed, despite its holding Element is encapsulated by a neighboring domain:
  • ManagementDomainInterface (TcpClient at Applications encapsulated by ApplicationDomainManager)
• The following kinds of Connections are managed:
  • TCP: ManagementDomainInterface <---> LoadBalancer/Controller
  • TCP: LoadBalancer <---> Controller
  • HTTP: ManagementDomainInterface <---> Controller
  • (Copy: LogicalMountPoint ---> MountPoints)
  • (ManagementPlaneTransport: Application <---> LogicalController)
• A neighboring domain is managing the following kind of Endpoint, but CDM is mediating towards the Element:
  • TcpClient at MountPoints at Controllers

InformationStructure

• Internal Information Structure (includes definition of the terminology in the CDM)

Functions

• Public and Private Functions
• Example: Sequence of steps to the first ManagementPlaneTransport connection

Diagrams

• Collection of Diagrams

ServiceList

• ControllerDomainManager+services

ProfileList and ProfileInstanceList

• ControllerDomainManager+profiles
• ControllerDomainManager+profileInstances

ForwardingList

• ControllerDomainManager+forwardings

Open API specification (Swagger)

• ControllerDomainManager

CONFIGfile (JSON)

• ControllerDomainManager+config

Comments

A lot of conceptual work has been done, during specifying the DeviceDomainManager application.
The following concepts are base to the ControllerDomainManager, too:

• AutomationArchitecture
• NetworkTopology
• FunctionConcepts

.

Links to be updated after specification of DeviceDomainManager has been merged into develop branch

.