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

Compare with Current View Page History

« Previous Version 31 Next »

Reference Material

Open Issues & Decisions

#DescriptionNotesDecision
1How to deal with hardcoded E2E NW Slicing model, spike

  Discusdons started with E2E NW Slicing Team, to be continued next week


2Which Simulator to use? NetConf Simulator Netopeer v2
  1. Nokia  
  2. Ericsson 
  3. Honeycomb(?)

Rahul Tyagi Ericsson more lightweight, more experience.
Available CSIT standard setup

Swaminathan Seetharaman mentioned 'Honeycomb' simulator they used before. Need to investigate if it supports get-schema method over RESTConf/NetConf

Need to check if we can use it with E2E NW Slicing model


3Should (ONAP) dmi-instance be  as separate (springboot) application
Could be part of DMI Manager		DMI-Instance interface should be an open standard

Tony Finnerty and Team to allow easy integration of future 3rd part DMI-Plugin instances a separate application with its own REST Interface is required


Istanbul Roadmap

Suggested Epics & User Stories 


#EpicProject/ComponentDescription(Suggested) StoriesComments
1

E2E Network Slicing

CPS-382 - Getting issue details... STATUS


CPS/NCMP

create rest interface on northbound for GET/POST/PUT/DELETE to access yang data.
Note. Currently driven by "E2E Network Slicing" Use Case mix of CPS-CORE and NCMP Interface

  1. Spike API for Update and Delete Operations CPS-278 - Getting issue details... STATUS  
  2. 'List' support
    1. CPS-360 - Getting issue details... STATUS
    2. CPS-361 - Getting issue details... STATUS
    3. CPS-362 - Getting issue details... STATUS
  3. Remove/migrate? 'hardcoded generic models used in H release"
  1. interfaces for yang data are: operational, intended, pass-through (selection can be done by parameter)

  2. check with netconf-sim if current nw slicing yang model can be imported including its imports.

2

DMI-Registry

CPS-383 - Getting issue details... STATUS

(NCMP) DMI-Registry

Create  dmi-registry. Data Model Inventory Interface (DMI)

'Internal service' no public Java or REST API

responsibilities are

  1. Store & retrieve cm-handle/dmi-plugin mapping in yang modelled CPS data table.
    1. include additional data (key-value pars as provided by dmi-Plugin)
  2. Dmi manager is to select the dmi instance at runtime for cm handle for a northbound (write) request
  1. Define and Agree Yang Data Model  CPS-352 - Getting issue details... STATUS
  2. Create Dataspace & Anchor for DMI Registry  CPS-353 - Getting issue details... STATUS
  3. Spike: How will DMI Plugin (De-?)Register with NCMP (DMI Registry)  CPS-389 - Getting issue details... STATUS
  4. Implement Plugin Registration (DMI Registry Side)
  5. Add CMHandle (registration) incl. 'Additional properties'
  6. Remove CMHandle (registration)

3

DMI-Plugin

CPS-384 - Getting issue details... STATUS

DMI-Plugin (ONAP impl.)

Common standard (REST and Java?) interface for extensibility

create dmi plugin for onap. For production its responsibility of admin to provide instance of dmi. 

  1. Define and agree NCMP & DMI REST Interfaces (Ericsson will provide output internal study) 
    1. CPS-390 - Getting issue details... STATUS
    2. CPS-391 - Getting issue details... STATUS
  2. Implement Plugin Registration (DMI Plugin Side)
  3. create module dmi-onap-plugin Rest and Impl modules. Suggestion (TBC):
    1. sub-module dmi-notification-handler
    2. sub-module dmi-rest
    3. sub-module dmi-plugin
  4. create infra for separate spring boot application and docker image for dmi-plugin
  1. extract dmi-plugin into separate container consensus on rest interface is needed.
4

Inventory

CPS-385 - Getting issue details... STATUS

DMI-Plugin (ONAP impl.)
  1. At first, on A&AI change event over DMaap, create mapping for cm-handle and dmi instance and sync yang model and data.
    1.  Filter (register) only yang modelled xnf instances's cm-handle, based on event header information of Node
  1. MVP: hard-coded inventory list
  2. Spike A&AI inventory list   CPS-393 - Getting issue details... STATUS
  3. Spike A&AI event subscription & filtering   CPS-394 - Getting issue details... STATUS

5

Model & Data Sync

CPS-386 - Getting issue details... STATUS

DMI-Plugin (ONAP impl.)
  1. Spike SDNC Interface for Model Retrieval   CPS-395 - Getting issue details... STATUS

6

Pass-Thru Support

CPS-382 - Getting issue details... STATUS

DMI-Plugin (ONAP impl.)
  1. dmi plugin instance (onap-dmi) have sdnc connector to access sdnc.
  2. call get/post/put/delete towards restconf interface (forward northbound write requests)
  1. Spike SDNC Interface for CRUD Operations   CPS-395 - Getting issue details... STATUS
Possibly overlaps with #1 E2E Network Slicing

Interfaces


#modulerest apijava api
1onap/cps/ncmp/dmi-registry


#typenameparams
1POSTregister_dmi_plugin
  1. dmi-plugin-id
  2. name
  3. adress
  4. other-params
2POSTcreate_cm_handle
  1. cm-handle
  2. dmi-plugin-id
3DELETEdelete_cm_handle
  1. cm-handle
#method_nameparamsreturn
1getDmiPluginByCmHandlecm-handledmi-plugin-object
2onap/cps/ncmp/dmi-plugin

3onap/cps/ncmp/ncmp-rest

4onap/cps/cps-rest

JIRA Status Tracking

Epic:  CPS-321 - Getting issue details... STATUS

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh


Component description diagram


Sequence diagrams






























  • No labels