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

Compare with Current View Page History

« Previous Version 9 Next »

CPS-333 - Getting issue details... STATUS

Open Issues & Decisions

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

Discuss with E2E NW Slicing Team


2Whish Simulator to use? NetConf Simulator Netopeer v2
  1. Nokia  
  2. Ericsson 

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

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

Reference Material

Scenario Scope In Istanbul

This scenario will demonstrate configuration management using NCMP.

There should be following functional requirements need to be fulfilled

  1. Add/remove *CM-Handle by using *DMI (Date Model Inventory) based on events.
    1. create component
    2. interface definition/agreement with community
    3. listen/filter to event 
    4. handle add event
    5. handle remote event
  2. Pass through read and write data from application to node via ncmp using SDNC
  3. Sync network model and data from node to cps via ncmp
  4. Read cached data model or data from cps  to application via ncmp


Data Model Inventory (DMI) consist out of 2 parts:

  1. DMI Manager (DMI registry?)
  2. DMI Instances e.g. ONAP DMI-Instance


Impacts

#Project/ComponentDescriptionSuggested Stories
1CPS/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. Mirror each CRUD operation
  2. Remove/migrate? 'hardcoded generic models used in H release"

2CPS/NCMP/DMI-Manager

Create  dmi-manager. Data Model Inventory (DMI)

'Internal service' no public Java or REST API

responsibilities are

  1. Store & retrieve cm-handle/dmi-since mapping in yang modelled CPS data table.
    1. include additional data (key-value pars as provided by dmi-instance)
  2. Dmi manager is to select the dmi instance at runtime for cm handle for a northbound (write) request
  1. Set up new module for DMI-manager (agree name)
  2. Create yang model for cm-handle and dmi instance identifier mapping
  3. CRUD operation on registry

3CPS/NCMP/DMI-Instance

Common standard (REST and Java?) interface for extensibility

create dmi instance for onap. For production its responsibility of admin to provide instance of dmi. This story is mainly for testing purpose.

  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
  2. dmi instance (onap-dmi) have sdnc connector to access sdnc.
  3. call get/post/put/delete towards restconf interface (forward northbound write requests)
  1. Defined and Agree common (java?) Interface

4CPS/NCMP
  1. enhance ncmp-cps interface (need to identify).


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




  • No labels