Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

draw.io Diagram
bordertrue
viewerToolbartrue
fitWindowfalse
diagramNameAAI System Context View
simpleViewerfalse
width
diagramWidth624951
revision14


The CLAMP functional entity provides the capability to manage runtime control loopsAAI (Available and active inventory function provides real-time views of the resrouces and services in managed by and their relationships.  It provides the capability to

  • Create control loop from DCAE blueprint sent by SDC
  • Create configuration policy from the policy Tosca sent by SDC
  •  Configure DCAE applications of the control loop
  • Associate µService configuration policies to the DCAE application
  • Configure the operations to be taken by the control loop (by creating/updating/deleting operational policies)
  • Deploy/un-deploy control loop flow (blueprints) to DCAE
  • Control loop visualization. 

CLAMP relies on Policy to communicate to App-C/VF-C/SDN-C/SO in runtime, hence these are not part of CLAMP 

2. API definitions

  • Realtime views of the managed resources and services and their relationships

  • The relivance of the managed resources and services to the ONAP components.

  • It is a registry of the active, available and assigned assets.

  • It maintains a multidimenstional relationship amonst the managed services and resouces. 

2. API definitions

AAI provides CLAMP provides the following interfaces:

Interface NameInterface Definition Interface Capabilities
CLAMPEAAIE-1Control Loop Lifecycle Management Inventary Service Interface.   A user interface for:
  • Selecting the control loop flow
  • Entering configuration policy parameters
  • Entering operational policy parameters
  • Managing life cycle of DCAE control flow blueprint 
  An interface to create, update, retrieve, query, delete the service, resources and relationship inventary information for:
  • Cloud infrastructure (including cloud infrastructure regions and availability zones, cloud infrastructure resources such as servers, storage, VLANs, cloud network technologies,...)
  • Paths and connectors
  • Business Customers and busines customer relationship to managed assets
  • Service Instances (including the relationship to used resources)
  • Resource instances (including allotted resources) (virtual and physical, including VNFs, PNFs, Switches, VNF modules)
  • External systems (systems that ONAP connects to)
  • Images
  • Networks
  • Infrastructure tenants
  • Relationships
  • Interfaces
  • IP addresses
  • Configurations
  • Licences
  • Site resources

AAI also provides Inventory History information

 AAIE-2AAI Graphical User Interfaces Provides the capability to view the inventory CLAMPE-2Control loop dashboard.  User interface to show the overall status of the control loop through DMAAP events

 Display and update:

Events received and actions taken on the control loop.

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

The current API documents can be found at:

AAI CLAMP consumes the following Interfaces:

Interface NamePurpose Reason For Use
SDCE-6To receive the Control Loop Blueprint from SDCTo receivePolicyE-2To create and configure the closed Loop Operational Policies and Configuration policies(DCAE Aps. Config.)
DCAEE-x Retrieve DCAE appplication status
DCAEE-y Deploy/remove DCAE application. 


3. Component Description:

...

4. known system limitations

Runtime: None

Clamp data redundancy is dependent on Kubernetes and the persistent volume.

...

  • Multithreaded concurrent operations on the same objects can cause duplicates in the graph - we have implemented stickiness in the haproxy that sits between AAI and clients to keep a client bound to the same node which can mitigate this, but we do not force locking on updates which means that malicious or careless clients can cause duplicates in the graph.  We provide cleanup utilities for data grooming, but we recommend that clients are careful not to send multiple requests on the same object within microseconds of one another.
  • Operators should pay special attention to giving cassandra enough space, because we have known issues where things go pretty bad (like unhelpful or just wrong error messages) when the disks fill up on the cassandra cluster nodes.


5. Used Models

Clamp uses the following models:

  • Service model (received from SDC)
  • VNF model (received from SDC)
  • Policy Model.Invetary Model


6. System Deployment Architecture


Clamp consists AAI consists of 5 X containers:

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

draw.io Diagram
bordertrue
viewerToolbartrue
fitWindowfalse
diagramNameAAI runtime architecture
simpleViewerfalse
width
diagramWidth821
revision12

7. New Capabilities in this Release

This release, CLAMP AAI adds the following Capabilities:

  • Introduction of the model driven approach for Control Loops
    • add policy-model to the SDC distribution
    • automatic rendering of configuration policy UI based on the distributed policy model
    •  better rending of the display of the control loop flow based on the distributed blueprint
  • enhanced internal model to better support model driven approach. Extended PNF support

8. References

  1.  CLAMP Overview & User Guide AAI read the docs: https://docs.onap.readthedocs.ioorg/en/latestcasablanca/submodules/aai/clampaai-common.git/docs/index.html?highlight=AAI CLAMP internal interfaces:  https://onap.readthedocs.io/en/latest/_downloads/d3c9f924c6586fe411d40a05ad9b1bb7/swagger.pdf 
  2. AAI REST API Documentation - Dublin
  3. AAI REST API Documentation on readthedocs.io

  4. AAI GUI: AAI Graphical User Interface