Versions Compared

Old Version 15

changes.mady.by.user Manoop Talasila

Saved on

compared with

New Version Current

changes.mady.by.user Manoop Talasila

Saved on

Key

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

...

  • Platform Maturity Guidelines (Highest Priority)
    • Integrating with MUSIC, OOM, and AAF
    • 50% JUnit Test
    Coverage (Highest Priority)Role Centralization capability for framework based partners (Medium Priority)
    • Coverage 
    • Addressing security issues
  • Bootstrapping of VID roles and tighter integration with AAF (Medium Priority)
  • Role Centralization capability for framework based partners - design related (Low Priority)
  • Platform Enhancements - Improved logging, Security Hardening, and SDK Simplification (Low Priority)

Additionally, this release will also support the continued development of the Portal Framework Platform to support future functionality not required for R1 Beijing. This body of work will be of a lower priority to the work required to support the Use Cases for the Release.

...

Describe the use case this release is targeted for (better if the reference to customer use case).

...

Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance01

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-171

  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability11CSIT tests shows the stability of the component - https://jenkins.onap.org/view/CSIT/job/portal-master-csit-testsuite/
  • 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
Resiliency112

Integrating with MUSIC

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-210

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-5

  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01

Image Modified

>30% >50% Test Coverage - https://sonar.onap.org/overviewdashboard?id=83099org.onap.portal%253Aonap-portal-parent

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-145
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-155
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-136

  • 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
Scalability01

Integrating with MUSIC

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-210

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-5

  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-170

  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability12

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-147

  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...

List the API this release is expecting from other releases.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

...

Risk identifiedMitigation PlanContingency Plan
ResourcesActively seeking community support.Current resources are only enough to satisfy the Highest Priority Epics (Platform Maturity, JUnit 50% test coverage). But that will be difficult to achieve.

Resources

Fill out the Resources Committed to the Release centralized page.

Release Milestone

...

The project team comply with the ONAP Charter.

Release Key Facts

Fill out and provide a link toward the centralized Release Artifacts.