Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 3 Next »

STATUS: Copy

VNSDK:

1 High Level Component Definition and Architectural Relationships 



The VNF SDK provides the functionality to create VNF and PNF packages, test VNF and VNF ONAP compliance and provides market place functionality to store VNF and PNF packages. It supports:

  • The ability to create a HEAT and ETSI compliant (SOL004,SOL001) based VNF&PNF packages in a csar format.

  • Test VNFand PNF packages for ONAP compliance.

  • Upload and download VNF pages to/from a marketplace

In addition VNF SDK is used outside of ONAP by the LFN compliance and verification functionality.

2. VNFSDK API definitions

CLAMP provides the following interfaces:

Interface NameInterface Definition Interface Capabilities
VNFSDKE-1

VNF Package Management Interface.
(Also called sdk-Md)

Provides the VNF SDK as commands and client side language bindings. Enables use of VNF SDK functions from graphical user interfaces, shell scripts, programs and command line interfaces

 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 
VNFSDKE-2

Market Place GUI
(also called Sdk-Mp)

Provides the VNF SDK as commands and client side language bindings. Enables use of VNF SDK functions from graphical user interfaces, shell scripts, programs and command line interfaces

 Display and update:

  • Events received and actions taken on the control loop.
 VNFSDKE-3

Market Place
(also called Mp-API)

 Exposed by the NF Marketplace as a programmatic API. Enables use of NF marketplace functions from command and graphical user interfaces.

 
VNFSDKE4 

VNF Test Platform
(Also called Mp-Tf)

Exposed by the NF Marketplace as a programmatic API. Enables use of the NF Marketplace's PnP test framework for validation of uploaded VNF products.

 

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

The current API documents can be found at:

CLAMP consumes the following Interfaces:

Interface NamePurpose Reason For Use
SDCE-6To receive the Control Loop Blueprint from SDCTo receive
PolicyE-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:

A more detailed figure and description of the component.

<< For later inclusion >>

4. known system limitations

Runtime: None

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

Clamp application redundancy HA relies on Kubernetes

5. Used Models

Clamp uses the following models:

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


6. System Deployment Architecture


Clamp consists of 5 containers:

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

7. New Capabilities in this Release

This release, CLAMP 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. 

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