...
Requirements
| Jira Legacy |
|---|
| server | System ONAP Jira |
|---|
| serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | REQ-717 |
|---|
|
| Jira Legacy |
|---|
| server | System ONAP Jira |
|---|
| serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | REQ-720 |
|---|
|
| Jira Legacy |
|---|
| server | System ONAP Jira |
|---|
| serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | REQ-721 |
|---|
|
Minimum Viable Product
...
Functionalities
Epics
| Jira Legacy |
|---|
| server | System ONAP Jira |
|---|
| serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | CPS-350 |
|---|
|
| Jira Legacy |
|---|
| server | System ONAP Jira |
|---|
| serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | CPS-384 |
|---|
|
| Jira Legacy |
|---|
| server | System ONAP Jira |
|---|
| serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | CPS-385 |
|---|
|
| Jira Legacy |
|---|
| server | System ONAP Jira |
|---|
| serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | CPS-388 |
|---|
|
| Jira Legacy |
|---|
| server | System ONAP Jira |
|---|
| serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | CPS-386 |
|---|
|
| Jira Legacy |
|---|
| server | System ONAP Jira |
|---|
| serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | CPS-382 |
|---|
|
| Jira Legacy |
|---|
| server | System ONAP Jira |
|---|
| serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | CPS-369 |
|---|
|
| Jira Legacy |
|---|
| server | System ONAP Jira |
|---|
| serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | CPS-370 |
|---|
|
| Jira Legacy |
|---|
| server | System ONAP Jira |
|---|
| serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | CPS-446 |
|---|
|
Stories
| Expand |
|---|
|
| Jira Legacy |
|---|
| server | System ONAP Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = CPS AND type = Story AND fixVersion = "Istanbul Release" AND status in (Closed, Done) ORDER BY updated DESC |
|---|
| serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
|
|
| Expand |
|---|
| title | Stories in progress or on backlog |
|---|
|
| Jira Legacy |
|---|
| server | System ONAP Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = CPS AND type = Story AND fixVersion = "Istanbul Release" AND status not in (Closed, Done) ORDER BY status DESC |
|---|
| serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
|
|
Longer term roadmap
- CPS-Core will have extended query capabilities based on XPath expression.
- CPS-Core will enforce and control ownership of data it holds
- NCMP will be able to sync CM Models and Data on any xNF in the network
- MCMP wil support the same query capabilities as CPS-Core and be extend with options similar to RESTConf's 'fields' and 'depth'
- Temporal DB?
...
For more detailed component description see ARC Configuration Persistence Service (CPS) Component Description - Istanbul-R9#6.SystemDeploymentArchitecture
Platform Maturity
Please fill out See the centralized wiki page:Frankfurt Istanbul Release Platform Maturity
API Incoming Dependencies
...
No gaps Identified
...
See dynamic Jira filter:
| Jira Legacy |
|---|
| server | System ONAP Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = CPS and type = bug and status = open |
|---|
| serverId | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
|
No Risks identified, see also Istanbul Risks
...
The milestones are defined at the Release LevelPlanning 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 recommended to provide these agreements and dates in this section.
Please update See the following centralized wiki: Frankfurt Documentation
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
- ...
...
...
Istanbul Documentation
Other Information
...