Versions Compared

Old Version 3

changes.mady.by.user Toine Siebelink

Saved on

compared with

New Version Current

changes.mady.by.user Toine Siebelink

Saved on

Key

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

...

  • 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

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionmaximumIssues20jqlQueryproject=cps and issuetype in (epic)
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-189

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-183

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-168

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-120

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-118

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-86
 (stretch)


Stories

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = sanbox "Configuration Persistence Service" and issuetype in (story(Story) and ("Epic Link" = CPS-168 or fixVersion = "Honolulu Release" )
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

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


  • API Incoming Dependencies

...

NameDescriptionVersion
DockerVM Container18 and above
ODL Yang ToolsYang model and Data Parser5.0.66 
Postgres Docker imageVM container for Postgres13.1 (will use 'latest' image released at built time)
Open JDK imageBase image11-jre-slim
JettyApplication server9.4.31
SwaggerOpenAPI library2.1.4
SpringFoxOpenAPI library3.0.0
Hibernate typesSupport for Postgres datatype JSONB2.10.0
Spring BootApplication Framework2.3.3.RELEASE
cglib-nodep3pp3.1
commons-lang33pp3.11

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

  • 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
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-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.

Gaps identifiedImpact
To fill outTo fill outxNF-Proxy data mirroring and syncingdata instance hardcode (ie. loaded upon deploy)

  • Known Defects and Issues

Please refer to Frankfurt Defect Status CPS Release note when available


  • Risks

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Please update any risk on the centralized wiki page - Frankfurt Risks

  • Resources

Fill out the Resources Committed to the Release centralized page. Honolulu Risks  No risk identified at the moment

  • Release Milestone

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

...

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.It is not expected to have a detailed project plan.

...

...

  • Documentation, Training

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

That includes

  • Team contributions to the specific document related to he project (Config guide, installation guide...).
  • Team contributions to the overall Release Documentation and training asset
  • High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  • Documentation includes items such as:
    • Installation instructions
    • Configuration instructions
    • Developer guide
    • End User guide
    • Admin guide
    • ...

...