Versions Compared

Key

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

...

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

Epics

https://jira.onap.org/browse/OOM-10?jql=project%3D%22ONAP%20Operations%20Manager%22%20and%20issuetype%3DEpic%20and%20fixVersion%3D%22Casablanca%20Release%22%20and%20not%20status%3DClosed

Stories

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=oom and type=epic and fixversion="Casablanca Release"
serverId425b2b0a-557c-3c0c-b515-579789cceedb

Stories

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues50
jqlQueryproject=oom and type=story and fixversion="Casablanca Release"
serverId425b2b0a-557c-3c0c-b515-579789cceedb
https://jira.onap.org/browse/OOM-10?jql=project%3D%22ONAP%20Operations%20Manager%22%20and%20issuetype%3DStory%20and%20fixVersion%3D%22Casablanca%20Release%22%20and%20not%20status%3DClosed

Longer term roadmap

OOM will evolve to improve the production qualities of ONAP deployments and enable a wider variety of Cloud types including Kubernetes native public clouds.

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance*N/A*N/A
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability*N/A*N/A
  • 0 – none
  • 1 – 72 hours component level soak w/random transactions
  • 2 – 72 hours platform level soak w/random transactions
  • 3 – 6 months track record of reduced defect rate
Resiliency*N/A*N/A
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security*N/A*N/A
  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage
  • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
  • 3 – CII Gold
Scalability*N/A*N/A
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability*N/A*N/A
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11docs updated as required
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

*N/A - as mentioned above, OOM will support other projects to achieve their S3P requirements

  • API Incoming Dependencies

...

List of all known project bugs: 

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues50
jqlQueryproject=oom and type=Bug and fixversion="Casablanca Release"
serverId425b2b0a-557c-3c0c-b515-579789cceedb

https://jira.onap.org/browse/OOM-10?jql=project%3D%22ONAP%20Operations%20Manager%22%20and%20issuetype%3DBug%20and%20not%20status%3DClosed

...

As OOM is fully functional as is there are no significant risks to project.

  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

...