Versions Compared

Key

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

DRAFT PROPOSAL FOR COMMENTS

The content of this template is expected to be fill out for M1 Release Planning Milestone.

...

  • 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)
  • Bootstrapping of VID roles and tighter integration with AAF (Medium Priority)
  • Platform Enhancements - Improved logging, Security Hardening, and SDK Simplification (Low Priority)

...

AAF (Application Authorization Framework) - for role/user creation, authentication, authorization.

OOM

MUSIC

Architecture

High level architecture diagram

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance101
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability01
  • 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
Resiliency11

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

>30% Test Coverage - https://sonar.onap.org/overview?id=83099

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPORTAL-145
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

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

...

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
AAFRestful APIs for fetching available roles to portal onboarded application usersJan. 10Jan 31Link toward the detailed API description
AAFPush Portal/VID roles to AAFJan 10Jan 31Link toward the detailed API description

API Outgoing Dependencies

API this release is delivering to other releases.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
AAFPush Portal/VID roles to AAFJan 10Jan 31Link toward the detailed API description





Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

NameDescriptionVersion
MariaDBThe MariaDB is the repository that holds
onboarded applications, onboarded microservices and widgets
all the policies, templates, PDP group, and deployment information.

10.0

.31

NexusThe Nexus repository holds all the currently deployed Operational (i.e. Drools policies) and their dependent artifacts.

2.14.2-01

ElasticSearch

Used to search text within policy.

5.4.0

UbuntuOperating system14.04

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

...

Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.

JUnit tests: 50% code coverage is the goal for all repositories. 

If resources become available, we will add more CSIT test cases.

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

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.

...

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuerykey in (PORTAL-15,PORTAL-13,PORTAL-10,PORTAL-8project = PORTAL AND fixVersion = "Beijing Release" and issuetype in (Bug)
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill outResourcesActively 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.

...