Andrei,
 
Thank you for bringing this topic up.  It's important that we minimize overlap in projects to maximize the impact of the contributors.
 
In my basic understanding, VNF-SDK and ICE have substantial overlap.  Can we investigate how these two projects can merge?
 
As for CLAMP and Policy Framework, it seems that they both would contribute design tools into SDC.  As I understand it, SDC should be able to support the design of all the elements that make up a VNF package (including workflows, analytics microservices, directed graphs for controllers, policies, etc.)  I would expect that each project that requires a design element would create that design element themselves and plug that into SDC... rather than the SDC project trying to design everything. For example, today directed graphs in the controllers are built directly in the Node-RED tooling in the controller, but this should in the future be accessible via SDC.  Is that your understanding?
 
I welcome others' input on this.
 
Thanks!

Regards,
Jason Hunt
Executive Software Architect, IBM

Phone: +1-314-749-7422
Email: djh...@us.ibm.com
Twitter: @DJHunt
 
 
----- Original message -----
From: Andrei Kojukhov <andrei.kojuk...@amdocs.com>
Sent by: onap-tsc-boun...@lists.onap.org
To: onap-discuss <onap-disc...@lists.onap.org>, "onap-tsc@lists.onap.org" <onap-tsc@lists.onap.org>
Cc:
Subject: [onap-tsc] Proposal for structuring Modeling projects
Date: Wed, May 10, 2017 9:46 AM
 

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

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

 

 

Option 2: “Design Automation” umbrella including on-boarding and certification

 

 

Option 3: “Design Automation” umbrella excluding on-boarding and certification

 

 

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

 

 

 

 

 

 

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
_______________________________________________
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc
 

_______________________________________________
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Reply via email to