Dear all,

Currently there are 6 draft projects in ONAP that deal with modeling, 
onboarding and certification. The below table summarizes the 6 initiatives and 
presents the feature coverage of each one of them.


ONAP Project

Features covered by the project

VNF/Service Design

VNF Guidelines

VNF Certification

VNFD/VNF package onboard

Modeling - overall modeling issues

V







Incubation and Certification Entity (ICE)



V

V

V

Service Design and Create (SDC)

v

V

V

V

VNF-SDK

V

V

V

CLAMP

V







Policy Framework

V









Besides an overlap in content and resources allocation of contributors, my 
expectation is that there will be issues with synchronization of requirements 
such as VNF guidelines and requirements derived from Use cases as well as 
maintaining open source.
Therefore, I'm proposing to consider structuring the above described ONAP 
projects. One of possible umbrella projects may be SDC covering most if not all 
the design and onboarding related features.

The Service Design and Create can be seen as one candidate as unified platform 
for

*         Validation and verification of VNF guidelines,

*         VNF/Service Design studio

*         Standard VNFD/VNF package onboarding platform based on ETSI NFV 
SOL001, SOL004 specifications leveraging TOSCA YAML modeling and CSAR packaging

*         Multilayered VNF Certification including VNF package integrity and 
authenticity validation, VNF deployment and running VNF tests verifying 
non-functional VNF KPI's that are currently specified in ETSI NFV EVE011 work,
There may be different options of structuring all or part of the ONAP 
initiatives as shown in the following pictures.

Option 1: SDC umbrella
[cid:image007.png@01D2C9B5.447E30F0]


Option 2: "Design Automation" umbrella including on-boarding and certification
[cid:image008.png@01D2C9B5.447E30F0]


Option 3: "Design Automation" umbrella excluding on-boarding and certification
[cid:image009.png@01D2C9B5.447E30F0]


I would like to invite ONAP community members to provide their view on possible 
structuring.


BR,

Andrei



Andrei Kojukhov, PhD

Open Network Division
Amdocs Technology


[cid:image010.png@01D2C9B5.447E30F0]




This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
_______________________________________________
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Reply via email to