Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

PriorityDescriptionNotesIstanbul commitmentJira(s)
1Publish and Share NCMP Rest interface proposaldetailed for Istanbul scope, general structure only for functionality related to later releasesCommitted

Jira
serverONAP Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-391

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

Jira
serverONAP Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-390

3

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

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-350
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-384
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-352
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-353
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-389

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-442
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-403
Jira
serverONAP Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-404
Jira
serverONAP Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-405


4

Initial Inventory (semi hardcoded e.g. hidden rest endpoint

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.Committed

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-406

5Read operations for operational data (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 

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

    Exact scope to be clarified

    i.e supported datastore(s) options

    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-394

    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
    Exact scope to be clarified

    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-395

    7Inventory Changes define and implement interface to add & remove cm handleRelated to #3Committed

    Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-443
    Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-444

    8Model discovery (get and store model for a cm-handle)NCMP queries DMI plugin that provides information, for ONAP retrieved via SDNC/ODLCommitted
    9Retrieve list of modules (names) for a cmHandle - make higher priority Used by applications to get cached information from NCMP about modelsCommitted
    10Manual (initial) data syncIncludes both NCMP and DMI APIsCommitted
    11Support dynamic inventory changes (ONAP DMU Plugin)React to events from AAI sent over DMaaP, in turn using API in #7 for updatesStretch

    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-392
    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCPS-393

    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

    ...