Parallel Session SDC

Owned by Rich Bennett
Last updated: May 03, 2017 by David Shadmi
2 min read

Purpose

This template is to be used for the “Parallel Deep Dive Sessions to Align with architecture / Use cases” at the may ONAP developers event

Instructions.

The purpose of each section is to translate the use cases and functional architecture into specific identified needs for the components, and to identify potential projects to be proposed.  There are three parts to this exercise:

  1. Identify needs based on the use case and architecture on this module, and potential dependencies on other modules or external artifacts.

  2. Group these into projects.  Consider that coding, documentation, and testing is required.   Include an initial scope for the project.

  3. If time, mapping the needs into the projects.

The need identification table has the following columns

-          Identified need: <slogan for the identified need>

-          Brief need description: <a few sentences describing the need>

-          Driver:<Related use case or architecture change, if any>

-          Dependencies:<identify dependencies on other modules or artifacts (e.g. other onap module, models, …)

-          Project: <If time, after the projects are identified, suggest in which project the need would best fit>

Time keeping suggestion:  The exercise time is 45 minutes.  A good practice would be to split into 20 minutes on need identification and 20 minutes on project proposals.

Exercise output.

ONAP Meeting Session name: SDC

Need Identification:

Identified Need

Description

Driver

Dependencies

Project fit
(if time)

Northbound Onboarding API

API for onboarding VNFs and Service definitions

onto SDC from external systems.







Centralized VNF Image Management

Ability to centrally onboard a VNF image,

yet distribute to disparate infrastructure

instances.







Support different cloud infrastructure

Uploaded different deployment recipes, or import TOSCA to bootstrap VNF







Support the merge architecture in ONAP

for design projects





VNF SDK, Workflow designer, VNF design, VNF guidelines, VNF certification



Support integration with new and modified projects, as part of merged architecture in ONAP





VF-C, SO, modeling



Multi-tenancy









Design deployment flavors, geo redundancy, availability

(ex. policies)







Service function chain











Project proposals.

[repeat for each project.  Note: This is not a complete project proposal skeleton, only sufficient enough for this discussion]

Project 1:

Project Name: Support ONAP Release 1 Architecture

Project Description

-          Enhance the existing platform for ONAP release 1 Architecture 

Scope:

-          Integrate with  projects like Modeling, VNF SDK, VF-C

-          Convergence with OPEN-O and OpenEcomp

-          Service function chaining Design

-          Design deployment flavors (GeoR, HA).



Project 2:

Project Name: -  Image Management Platform



Project Description

-          Provide an image management platform, for multiple VIM, with multiple versions

Scope:

-          Onboard image

-          Image distribution

-          Versioning 

-          Quarantine area 



Project 3:

Project Name: -  VNF onboarding Northbound API



Project Description

-          API for onboarding VNFs and Service definitions onto SDC from external systems.



Scope:

-          API for onboarding and updating VNF into the SDC catalog