New Delhi (ND)

India Gate in New Delhi, March 20, 2016 (Credit: A. Savin, WikiCommons)


Requirements

Priority legend
PreliminaryPriority AgreedIn ProgressPaused/BlockedCompletedDe-scoped

ONAP Best Practices (Global Requirements) and similar

ONAP RequirementNotesCPS- Jira(s)

REQ-439 - Getting issue details... STATUS




ONAP script might help us with common quality issues and save reviewing time

CPS-1324 - Getting issue details... STATUS

CPS-CORE / CPS-NCMP Requirements

PriorityEpic/Component/Owner/Team/TargetDescriptionNotesJira(s)
1
Data Write/Read Performance

See also CPS-Core Read & Write (large load) Test Results from  Wipro/Fujitsu

See Montreal Read/Write Performance for latest performance results (23/08)

Key Summary Assignee Status
Loading...
Refresh

2
Support update of cached data through a message driven solution.
Respond to  VES Events from Devices in ONAP
Receive VES Event and transform it into a 'standard DMI→NCMP events (schema owned by NCMP)

Key Summary Assignee Status
Loading...
Refresh


3
CM Handle Connectivity Freshness/Staleness

Need to model what staleness is (current CPS only has concept of model-sync state, nothing about connectivity)
kieran mccarthy to spec this

Staleness will be modelled as a public property and notification will be sent/ notifiable. 
Assumption is that the solution will accommodate the same behavior's for all public properties.

Done: Getting issues...

4
Update YANG schema-set for CM handle using ModuleSetTag
  1. Update YANG schema-set for CM handle without removing and adding it
  2. Cached data is not in scope.
  3. Need to specify orphan handling of YANG modules (already built in ?)
  4. Introduce concept of ModuleSetTag to prevent unnecessary trips to nodes to get al Modules
  5. will require NCMP module loader (for upgrade of Inventory model) instead of Liquibase steps!

Key Summary Assignee Status
Loading...
Refresh

5
Merge CM data subscriptions in NCMP when forwarding it to DMIImplementing Data Notifications & Subscription Notifications on a US by US basis

Scope add: What kind of access controls are required on topics? Spike is required for this.  Work Item created (23/05).

Key Summary Assignee Status
Loading...
Refresh

6

Support Alternate ID (3GPP) for CM Handle ID
Implement FDN base CMhandle, this should be done before patternmatch cmhandle can be implemented

NCMP's CmHandle registration endpoint shall be changed to accept a new String parameter which proposed name is alternateId.
NCMP Inventory CPS-NCMP-I-01 should be able to support alternate id update

Key Summary Assignee Status
Loading...
Refresh

7
CPS & NCMP Feature Enhancement for M Release: Delta Feature

Moved up on  Previously Priority 19

Key Summary Assignee Status
Loading...
Refresh

8

Update NCMP LCM events to include  alternate id

* NCMP LCM event should send notification events with FDN identifier in the alternateid (deprecation period: correlationid=md5-hash, alternateId=FDN)
* NCMP LCM event should send notification events with FDN identifier in the correlationid (after deprecation period: correlationid=md5-hash (existing) or uri-FDN (new ones), alternateId=FDN)

Done: Getting issues...

9

Support for Async datajobs

Not just for reading specific fdn, but rather QUERY Group of FDN , it's just a broadcast to every DMI plugin. The response should mimic sending a broadcast to 2 or more CM Handles 

CPS Team wil only do java interface. REST Interface is done in DCM

NEW interface aligning with 3GPP i.e FDN instead of CM-HandleIds

(Read use case can re-use existing dataOperationz impl. after mapping FDNs to CMHandleIds for input and back for output!)

Read, Create, Update, Delete and Action support. I.e for passthrough only
Note: Q(uery) is  SUBNETWORK-wide read and should be done separately using a different endpoint for clarity and separation!

* NCMP to introduce a qualifier to be used along with the DMI plugin so NCMP can break the request with multiple cmhandle into batches based on the DMI plugin and the Qualifier (where qualifier should be EMS name / id).
* NCMP shall create one or multiple EMS job ids depending on FDNs requested
* NCMP shall provide an interface to get status of an EMS job id (forward request)
* NCMP shall provide an interface to get results of an EMS job id
* NCMP shall send the results to Kafka topic

Key Summary Assignee Status
Loading...
Refresh

10
CPS/NCMP delivery process

Moved up on Not discussed for long time but need new attention so these problems don't continue while building DCM
Alignment
of CPS/NCMP build artifact versions with EIC  CPS-1933 - Getting issue details... STATUS

Key Summary Assignee Status
Loading...
Refresh

11
Retrieve single module resource
No Epic, Single User Story
/v1/ch/{cm-handle}/modules/definitions/{moduleName}

Done: CPS-1135 - Getting issue details... STATUS

12
  • CPS-2008 - Getting issue details... STATUS
  • CPS-NCMP
  • TBC
  • Q2 24'

Update existing single sync cmhandle APIs to support alternative id (containing FDNs)



13

NCMP to support the 3GPP ProvMnS CRUD interfaces. NCMP to Support new 3GPP sync single FDN request

Implement new NCMP CRUDAQ sync interface aligned with 3GPP API (Read and write use cases) - Wrapper on existing/legacy API


14
  • CPS-2009 - Getting issue details... STATUS
  • CPS-NCMP
  • CPS-NMCP
  • TBC
  • Q4 24'
Update remaining existing/legacy NCMP APIs to support alternateId (FDN)

Update existing/legacy NCMP APIs to support FDN / alternateId

Depends on CPS-1704 - Getting issue details... STATUS (which now has a lower priority)

Now includes  CPS-2058 - Getting issue details... STATUS


15
  • CPS-2010 - Getting issue details... STATUS
  • CPS-NCMP
  • CPS-NMCP
  • TBC
  • Q4 24'
NCMP to support datajob results in S3

NCMP to introduce a qualifier to be used along with the DMI plugin so NCMP can break the request with multiple cmhandle into batches based on the DMI plugin and the Qualifier (where qualifier should be EMS name / id).
* NCMP shall create one or multiple EMS job ids depending on FDNs requested
* NCMP shall provide an interface to get status of an EMS job id (forward request)
* NCMP shall provide an interface to get results of an EMS job id
* NCMP shall send the results to S3


16

TBAC - Access Control for resources to ensure that operators can restrict access control to only those users (human/machines) that are authorized to execute CRUD operations on those resources. 


TBAC Study still ongoing, schedule an internal meeting to go through study doc, until sidecar is well define and implemented cps can't do nothing. Sidecar should specify the interfaces.

Key Summary Assignee Status
Loading...
Refresh

17
  • CPS-1781 - Getting issue details... STATUS
  • CPS-NCMP
  • TBD
  • TBD

CM data subscriptions from application to DMI [Part 2].

For all cmhandle (general)

This epic was created to take on additional scope which got added to CPS-1616


Key Summary Assignee Status
Loading...
Refresh

18
  • CPS-1965 - Getting issue details... STATUS
  • CPS-NMCP
  • TBC
  • TBC

AVC Subscription, advance filter. Part 2 of cmhandles

It includes creating subscription with patternmatch cmhandles. 

Filter on 'Type' instead of list of CM Handle IDs → 'Type' could be defined as the yang module set containing a specific module (name and version)


19
  • TBC
  • CPS-NMCP
  • TBC
  • TBC
Event Digest

Additional field to help clients filter CM AVC Events
(S)



20

TBC

Support NCMP-CPS upgrade

Currently only custom upgrade is supported. (upon request)

Requirement: It shall be possible to upgrade NCMP-CPS from release N-1 to N (without requiring manual intervention/workarounds). N is defined as any release requested by ESH

  • Note. Need to agree version strategy: use current ONAP x.y.z. numbering. Ericsson to communicate when a version is to be 'delivered' and 'y' increased

Technical Debt to be addressed: Liquibase is used in CPS to manage data(upgrades) in CPS

Study: Resolve technical debt (mixed data). NCMP Data upgrade. CPS Core need to support model upgrade so that NCMP can use it,


Liquibase is used in CPS to manage data(upgrades) - Now available.

  • Still need to discuss the 'backward incompatible' → What interfaces should NOT be impacted Kieran mention NBI - northbound interfaces
  • Propose workshop, Spike needed from CPS


(XL) - Scope needs to be defined. Risk is scope not identified, efforts might increase.


CPS-1345 - Getting issue details... STATUS

21
  • CPS-1796 - Getting issue details... STATUS
  • CPS-CORE & NCMP
  • TBC
  • TBC

Spike for documenting Kafka interfaces using AsyncAPI

- Documentation Generation
- Interface Naming
- Cloud Events specifics asyncapi-cloud-events - Roll out for legacy events

- Code Generation (contract first, stubs)
Add label of techdebt Kolawole Adebisi-Adeolokun not an immediate req for


22
  • CPS-1704 - Getting issue details... STATUS
  • CPS-NMCP
  • TBC
  • TBC
Refactor legacy NCMP ASync Response Events to use Cloud Events format(M) TBC 

Key Summary Assignee Status
Loading...
Refresh

23
Access control for topics which are created by NCMP.

Spike needs to be conducted. Dependent of TBAC implementations.


24Invoke YANG modelled sync action

Invoke YANG modelled action

Invoke YANG modelled RPC, Specification required. Rebbot/Reset type of actions on node. Include to the sync one

Always on operational datastore.  Supported for nmcp:passthrough-operational and if executed against ncmp:operational then it is always forwarded to dmi plugin.  Is there another story for forwarding to be included as a dependency? Always run as sync request.  Is this dependent on CPS-1127  - see spin-off user stories table below this on.

KMC : Can we deprioritize - this can be run against passthrough-operational for now.  Just have to agree on the API / URL for the action to progress at this stage so that the passthrough-operational form is aligned with final operational form.

(S) - for passthrough. 

*Spec out before Sept'23. No implementation. 


 

can datajob cover this ?, currently no support for 'actions'. Action name at the end of resourceid. split ticket into, action with and without responses. 


25
Enhanced query support (fields)

Currently the passthrough has an 'fields' parameter to do a scoped query.  Propose to support this in non-passthrough so it is promoted to a fully supported option, e.g. {ncmp-root}/ncmp/v1/ch/335ff/data/ds/ncmp-datastore:passthrough-operational?
              resourceIdentifier=/&options=(fields=ericsson-enm-comtop:ManagedElement/ericsson-enm-
              gnbcucp:GNBCUCPFunction
/EndpointResource/LocalSctpEndpoint/attributes(sctpEndpointRef),
         

KMC : Do we support restconf like queries or xpath only?

(L) .

*Spec out before Sept'23. No implementation. 



26
Enhanced query support (scope)

Currently the passthrough has an 'fields' parameter to do a scoped query.  
              scope=ericsson-enm-comtop:ManagedElement/ericsson-enm-gnbcucp:GNBCUCPFunction/
               EndpointResource/LocalSctpEndpoint/attributes(interfaceUsed==X2))

KMC : Do we support restconf like queries or xpath only?

(L)

*Spec out before Sept'23. No implementation. 


27

TBC

Support ncmp-datastores:running 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.

Read from operations.

(S) - Forward only.  No validation or data enhancements (add prefixis)

28TBCSupport ncmp-datastores:running for writing data (single CM handle, synchronous only)(S)  As per #18
29

TBC

Support relationships for 'Instance Identifier'Should be possible to identify a cmhandle using multiple instance identifiers.
(M) - Not sure. Scope not known yet. 

CPS-1180 - Getting issue details... STATUS

30
Fine-grained cache configuration

31

Support for HTTPS and authentication

  • Use Service-Mesh? Both ONAP and Ericsson (applied ISTIO using Envoy Proxy side-car) are working towards this. Check with Gareth Roper 
Validation required whether this is still needed. 

CPS-703 - Getting issue details... STATUS

32TBCSend notifications on write operation in ncmp-datastores:running for (single CM handle, synchronous only)

33
schema-set update for CM handle with cached data presentNeed to address case with incompatible model changes.
Scope: Upgrade of model that is cached?  Lee Anjella to confirm. 


34
Invoke YANG modelled RPCSpecification required. Rebbot/Reset type of actions on node. 
35

CPS-1843 - Getting issue details... STATUS

DMI Audit for DMI restarts

After restart, trustlevel loses all data. TrustLevel is not currently in use now, however this becomes an issues after TrustLevel restart. The states goes to 'NONE' after TrustLevel restart


TBC

Key Summary Assignee Status
Loading...
Refresh

36

CPS-1872 - Getting issue details... STATUS

Fetch a list of cmhandles along with their private properties as response from NCMP.


37

EIC Stone tablet KPIs

TBC




Spin-off user stories, yet to be prioritized

 JiraComponent(s)Related Work ItemDescriptionNotes

CPS-1103 - Getting issue details... STATUS

CPS-NCMP


CPS-1127 - Getting issue details... STATUS

CPS-NCMP


CPS-1174 - Getting issue details... STATUS

CPS-NCMP


CPS-1139 - Getting issue details... STATUS

CPS-NCMP


CPS-1301 - Getting issue details... STATUS

CPS
Now handled by Fujitsu/Wipro (Work Item ?) ?

CPS-1348 - Getting issue details... STATUS

CPS


Functionalities

User Stories

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

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

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


Other Information

Platform Maturity

See the centralized wiki page: London Release Platform Maturity

Vendor Neutral

If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.

Free and Open Source Software

FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.

Each project must edit its project table available at Project FOSS.

Charter Compliance

The project team comply with the ONAP Charter.



  • No labels