STATUS: CopyDraft
VNSDK:
1 High Level Component Definition and Architectural Relationships
...
2. VNFSDK API definitions
CLAMP provides VNFSDK provides the following interfaces:
| Interface Name | Interface Definition | Interface Capabilities |
|---|---|---|
| VNFSDKE-1 | VNF Package Management Interface. 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 command interface for:
|
| VNFSDKE-2 | Market Place GUI 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.A user interface for:
|
| VNFSDKE-3 | Market Place Exposed by the NF Marketplace as a programmatic API. Enables use of NF marketplace functions from command and graphical user interfaces. | VNFSKDE-3 provides the following capabilities
|
| VNFSDKE4 | VNF Test Platform 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. | An interface to:
|
Note: xxxI interface is a Component internal interface. xxxxE interface is a component external interface
The current API documents can be found at:
The provided UI interfaces are found at: CLAMP latest user guide
- CLAMP internal APIs can be found: clamp swagger pdf
...
Market place API: Market Place
- Validcation Test API: Validation Test Platform
VNFSDK consumes the following Interfaces:
| Interface Name | Purpose Reason For Use | |
|---|---|---|
| SDCE-6 | To receive the Control Loop Blueprint from SDCTo receive | |
| PolicyE-2 | To 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.N/A | N/A |
3. Component Description:
...
4. known system limitations
Runtime: None
Clamp data redundancy is dependent on Kubernetes and the persistent volume.
Clamp application redundancy HA relies on KubernetesNone known. Note, VNF-SDK is a design time component.
5. Used Models
Clamp VNFSDK uses the following models:
...
- VNF model (received from SDC)Policy Model.Package Model
- PNF Package Model
6. System Deployment Architecture
Clamp consists of 5 containers:
...
This needs to be checked
VNFSDKconsists of 3 components deployed in one container:
- VNF Test Platform
- Marketplace
- Package Builder
Drawio border true viewerToolbar true fitWindow false diagramName VNFSDK runtime architectrue simpleViewer false width diagramWidth 821231 revision 12
7. New Capabilities in this Release
This release, CLAMP VNFSDK 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
...
- Enhanced VTP features to run test case(s) and track the results
- Add VVP support for HEAT based VNF validation
- Support PNF Package basic Validation
8. References
- VNF Package Tool: https://docs.onap.readthedocs.ioorg/en/latestcasablanca/submodules/vnfsdk/clampmodel.git/docs/files/indexpkgtool.html CLAMP internal interfaces: ?highlight=VNFSDK
- Marketplace API: https://docs.onap.readthedocs.ioorg/en/latest/_downloads/d3c9f924c6586fe411d40a05ad9b1bb7/swagger.pdf /casablanca/submodules/vnfsdk/model.git/docs/files/vnfsdk-apis.html