...

• CPS can store the module used for E2E Network Slicing and SON PCI (but any other model could be stored too)
• Yang json dat file can be stored for same model (with some validation)
• Support concept of Anchors (data entry points) even if only used one for MVP
• An xNfProxy interface wil be used to access xNF configuration data in CPS (hide soem of teh CPS housekeeping from xNF data users)
• Dataspace, model and dat will be hardcoded as part of xNfProxy stub in this release
• Query support wil be limited to whatever is needed for  E2E Network Slicing use cases

Functionalities

Epics

...

Please fill out the centralized wiki page: Honolulu Release Platform Maturity

• API Incoming Dependencies

...

...

• Testing and Integration Plans

Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

...

1. CPS has high level of built jUnit test (>90%) which is enforced by our maven build scripts
2. CPS has built in Persistence Layer test ie. test that integrate with real DB covering all use cases and are part of  WoW
3. CIST test need to be identified as part of Deployment Epic but will be included in Honolulu timeframe
   See 

   Jira Legacy
   server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CPS-188

• Gaps

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.

...

The milestones are defined at the Release LevelPlanning: Honolulu  and all the supporting project agreed to comply with these dates.

...

Please update the following centralized wiki: Honolulu Documentation – To be updated when avail

...