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

Compare with Current View Page History

« Previous Version 52 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(?)
  4. lighty netconf simulator

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

Priorities & Scope for Istanbul Release

PriorityDescriptionNotesIstanbul commitment
1Publish and Share NCMP Rest interface proposaldetailed for Istanbul scope, general structure only for functionality related to later releasesCommitted
2Publish and Share DMI Plugin Rest interface proposaldetailed for Istanbul scope, general structure only for functionality related to later releasesCommitted
3

Register a DMI Plugin (NCMP)

sends an event with initial inventory (TBC)Committed
4

Initial Inventory (semi hardcoded e.g. hidden rest endpoint or some kind of properties file, ONAP only)


Committed
5Read operations for single cmHandle, synchronous only

using 'pass-through' scenario (default on no data present for cm-handle)

In I timeframe ncmp will support the following datastore parameters 

  1. If nothing is specified it attempts to read from the cache, if there is no cache then it will try to access the plugin
  2. pass-through 
  3. operation-running (this means getting it from the cache if there is no data then you will get an error)
Committed
6

Create, Update & Delete operations for single cmHandle , synchronous only  (fall back to plugin - this means your not specifying any datastore and there is no cache)

using 'pass-through' scenario (default on no data present for cm-handle)
I don’t expect them to be different at all from a NCMP/DMI plugin perspective		Commited
7Inventory Changes define and implement interface to add & remove cm handle
Committed
8Model discovery (get and store model for a cm-handle)
Committed
9Retrieve list of modules (names) for a cmHandle - make higher priority 
Committed
10Manual (initial) data sync
Committed
11Support dynamic inventory changes (ONAP DMU Plugin)react to DMaapP events using methods define under #5Stretch
12Yang Patch operations for single cmHandle with ds = pass-through, synchronous only
Stretch
13Retrieve list of cm-handles that have a given module
Stretch
14Support yang-date+json output for all datastores
Stretch
15Trigger (initial) Data SyncMetadata (per cmHandle) controls whether this will happen or notOut of Scope
16

Implement -async option for CRUD and Patch operations


Out of Scope
17Support multiple cmHandles in a single call (bulk)
Out of Scope
18Support all cmHandles in a single call?
Out of Scope
19Support ds = operation-running for read and query operations
Out of Scope
20Support yang-data+json output format for ds = operational running
Out of Scope

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-362 - Getting issue details... STATUS
    3. CPS-361 - 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-350 - 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. Its responsibility of admin to provide instance of dmi. 

  1. Create module dmi-onap-plugin Rest and Impl modules.    CPS-403 - Getting issue details... STATUS Suggestion (TBC):
    1. sub-module dmi-notification-handler
    2. sub-module dmi-rest
    3. sub-module dmi-plugin
  2. Create infra for separate spring boot application and docker image for dmi-plugin  CPS-404 - Getting issue details... STATUS
  3. Implement Plugin Registration (DMI Plugin Side)  CPS-405 - Getting issue details... STATUS
  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.)
  • Capability to get initial Inventory
  • Process Inventory updates
  1. MVP: hard-coded inventory list  CPS-406 - Getting issue details... STATUS
  2. Spike A&AI inventory list   CPS-392 - Getting issue details... STATUS
  3. Spike A&AI event subscription & filtering  only yang modelled xNF instances's CPS-393 - 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-394 - Getting issue details... STATUS

6

Pass-Through Support

CPS-388 - 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. 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. Spike SDNC Interface for CRUD Operations   CPS-395 - Getting issue details... STATUS
Possibly overlaps with #1 E2E Network Slicing

Interfaces


Preliminary Interface Overview (Work-in-Progress)


#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