How to deal with hardcoded E2E NW Slicing model, spike

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

Which 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

For E2E use case Honeycomb simulator wil be used. If needs be for certain non E2E functionality where this simulator has limitations the team can still decide to test/develop against NeToPeer simulator

Should (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

What datastores are supported/recognized by NCMP Interface in Istanbul Release

Suggested, see Datastore paths and format combinations section below

1. ncmp-datastores:operational (will use cached data when sync=On)

2. ncmp-datastores:running (will forward to DMI-Plugin in Istanbul release)

3. ncmp-datastores:passthrough-operational (always forward to DMI-Plugin)

4. ncmp-datastores:passthrough-running (always forward to DMI-Plugin)

Suggestions in previous column were agreed in CPS Weekly meeting Jun 4, 2021 

What datastores are supported/recognized by (ONAP) DMI-Plugin Interface in Istanbul Release

Suggested exact same as NCMP supported options

1. ncmp-datastores:operational (for cmhandles with sync=Off)

2. ncmp-datastores:running

3. ncmp-datastores:passthrough-operational

4. ncmp-datastores:passthrough-running

Suggestions in previous column were agreed in CPS Weekly meeting Jun 4, 2021 

How to handle any other (custom) datastore value

Agreed in CPS Weekly meeting Jun 4, 2021 : Both NCMP and DMI-Plugin wil not support any other datastore value in the Istanbul timeframe

What to do with old CM-Proxy interface implemented in H.

Methods never really used by E2E Network Slicing team. 

Methods will be 'deprecated' using Open API option for that.. Replace and refactor other layers as needs when new methods using the new API are being implemented

Publish and Share NCMP Rest interface proposal

detailed for Istanbul scope, general structure only for functionality related to later releases

Committed & Delivered

https://lf-onap.atlassian.net/browse/CPS-391

Publish and Share DMI Plugin Rest interface proposal

detailed for Istanbul scope, general structure only for functionality related to later releases

Committed & Delivered

https://lf-onap.atlassian.net/browse/CPS-390

Register a DMI Plugin with NCMP

DMI plugin registration is implicit part of CM handle registration (inventory update), REST endpoint on NCMP (can be multiple calls)

Committed & Delivered

https://lf-onap.atlassian.net/browse/CPS-350https://lf-onap.atlassian.net/browse/CPS-384https://lf-onap.atlassian.net/browse/CPS-352https://lf-onap.atlassian.net/browse/CPS-353https://lf-onap.atlassian.net/browse/CPS-389
https://lf-onap.atlassian.net/browse/CPS-442https://lf-onap.atlassian.net/browse/CPS-403https://lf-onap.atlassian.net/browse/CPS-404https://lf-onap.atlassian.net/browse/CPS-405

Support method to add initial inventory (e.g. hidden REST endpoint on ONAP DMI plugin)

Additional properties for ONAP plugin may need ODL mountpoint, stored by NCMP and later provided to DMI plugin for each request. The mountpoint is created outside of CPS and DMI plugin.

Note 1: This method (hidden REST endpoint) is expected to be a temporary solution, additional options are part of stretch goal (#13).
Note 2: Adding the initial inventory should also trigger a model-sync for each node in that inventory (step #8)

Committed & Delivered

https://lf-onap.atlassian.net/browse/CPS-445https://lf-onap.atlassian.net/browse/CPS-385https://lf-onap.atlassian.net/browse/CPS-406

Support ncmp-datastores:passthrough-operational for reading data (single CM handle, synchronous only)

See CPS-391 page for details about supported operations and combinations. Note: There can be some overlap between work items for #5, #6, #11 and #12.
RestConf: content=all
NO conversion. NO schema's in OpenAPI Ymll (just String)

Committed & Delivered

https://lf-onap.atlassian.net/browse/CPS-388https://lf-onap.atlassian.net/browse/CPS-394

https://lf-onap.atlassian.net/browse/CPS-486https://lf-onap.atlassian.net/browse/CPS-487

Support ncmp-datastores:passthrough-running for reading and writing data (single CM handle, synchronous only)

See CPS-391 page for details about supported operations and combinations. Note: There can be some overlap between work items for #5, #6, #11 and #12.
Almost identical to step #5 above just RestConf: content=config

Committed but Partly Delivered:

• 'create' delivered

• 'update' & 'delete' delayed until Jakarta. See R10 NCMP Requirements

https://lf-onap.atlassian.net/browse/CPS-395https://lf-onap.atlassian.net/browse/CPS-562

https://lf-onap.atlassian.net/browse/CPS-532https://lf-onap.atlassian.net/browse/CPS-575

Inventory Changes: define and implement interface in NCMP to allow DMI plugin to add, update & remove CM handles

Overlap with #3, used by #4 and #13

Committed & Delivered

https://lf-onap.atlassian.net/browse/CPS-443https://lf-onap.atlassian.net/browse/CPS-444

Model discovery (automatic retrieval and caching of model information in NCMP for a CM handle)

NCMP queries DMI plugin that provides information, for ONAP retrieved via SDNC/ODL

Committed & Delivered

https://lf-onap.atlassian.net/browse/CPS-386

https://lf-onap.atlassian.net/browse/CPS-483https://lf-onap.atlassian.net/browse/CPS-484https://lf-onap.atlassian.net/browse/CPS-505https://lf-onap.atlassian.net/browse/CPS-506

https://lf-onap.atlassian.net/browse/CPS-508

https://lf-onap.atlassian.net/browse/CPS-531

Retrieve list of modules (names) for a CM handle

Used by applications to get cached information from NCMP about models

Committed & Delivered

https://lf-onap.atlassian.net/browse/CPS-485

Explicit (initial) data-sync for a CM handle (extend model-sync started in step #8)

Triggered by client using REST endpoint on NCMP

Delayed until Jakarta

https://lf-onap.atlassian.net/browse/CPS-507

Support ncmp-datastores:operational for reading data (single CM handle, synchronous only)

See CPS-391 page for details about supported operations and combinations. Note: There can be some overlap between work items for #5, #6, #11 and #12.

Delayed until Jakarta

https://lf-onap.atlassian.net/browse/CPS-382

Support ncmp-datastores:running for reading and writing data (single CM handle, synchronous only)

See CPS-391 page for details about supported operations and combinations. Note: There can be some overlap between work items for #5, #6, #11 and #12.

Delayed until Jakarta

Support dynamic inventory changes (ONAP DMI Plugin)

React to events from AAI sent over DMaaP, in turn using API in #7 for updates

Possible in a generic way o it can also listen to similar events sent by SDN-R  (as suggested by @Ahila P)

Delayed until Jakarta

https://lf-onap.atlassian.net/browse/CPS-392https://lf-onap.atlassian.net/browse/CPS-393

Retrieve list of cm-handles that have a given module

Delayed until Jakarta

Automatic (optional) Data Sync 

Metadata (per cmHandle) controls whether this will happen or not

Out of Scope

Implement -async option for CRUD and Patch operations

Out of Scope

Support multiple cmHandles in a single call (bulk)

Out of Scope

Support all cmHandles in a single call?

Out of Scope

Invoke YANG modelled RPC or action

Out of Scope