Versions Compared

Old Version 12

changes.mady.by.user Manoop Talasila

Saved on

compared with

New Version 13

changes.mady.by.user Manoop Talasila

Saved on

Key

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

...

What is this release trying to address?

Scope: The scope of this release will be for the Portal Platform to support the below list:

  1. Internationalization language support (Platform Feature) - ChinaMobile support
    1. Design language/internationalization component in Portal and provide service apis to partnering apps like Policy, VID, SDC, AAI.
    2. This is collaborative work with larger community (Use Case UI ONAP Team), expecting implementation details soon from ChinaMobile resources. 
  2. Testing (Technical Debt) - AT&T, IBM, TechM support
    1. CSIT tests for new Casablanca features.
    2. Enable JavaScript Unit tests coverage.
  3. Reporting feature enhancement in portal/sdk (Platform Feature) - AT&T support
  4. Defect fixes

Originally planned priority items, but de-scoped due to lack of resources (below items are added to backlog and not being committed for Casablanca). 

  1. OOM integration and enhancement (Modularity)
    1. Support deployment, scalability issues of the platform (DB docker)
    2. Music cassandra as a service - integration
    3. Music team to provide DB as a service
  2. AAF integration (Technical Debt)
    1. Truning ON AAF and starting using role management for partners - Policy, SDC, VID, AAI requires SDK upgrade.
    2. AAF certificate management integration (both for FE HTTPs and BE rest API calls)
  3. Security issues from Nexus-IQ (Technical Debt)
    1. Angular upgrade to address the security issue - may impact partnering apps like Policy and VID.
    2. Possibly in phases - start removing the vulnerabilities that are maeked as - "Not vulnerable in ONAP".
    3. Fix pending Fortify issue
  4. API Versioning and Backward Compatibility (Technical Debt)
  5. Performance and Optimization (Technical Debt)
    1. Memory usage optimization
    2. Split DB, Portal and SDK docker images
    3. UI upgrades - Angular, Bower
    4. Simplify deployment by avoiding the etc/hosts file entries
    5. Logging enhancements
  6. Testing (Technical Debt)
    1. Convert ECOMP selenium tests into CSIT ONAP Robot Framework tests.
    2. Code Coverage needs to be improved to 50% on both portal and portal/sdk repos with JavaScript.

Not-in-Scope: Please check gaps section.

Use Cases

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

...

List the other ONAP projects your depends on. 

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

OOM

MUSIC

UsecaseUI for internationalization feature contribution.

Architecture

High level architecture diagram

...

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: 80% 50% code coverage is the goal for all repositories without javascript. 

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

...

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

Originally planned priority items, but de-scoped due to lack of resources (below items are added to backlog and not being committed for Casablanca release). 

  1. OOM integration and enhancement (Modularity)
    1. Support deployment, scalability issues of the platform (DB docker)
    2. Music cassandra as a service - integration
    3. Music team to provide DB as a service
  2. AAF integration (Technical Debt)
    1. Truning ON AAF and starting using role management for partners - Policy, SDC, VID, AAI requires SDK upgrade.
    2. AAF certificate management integration (both for FE HTTPs and BE rest API calls)
  3. Security issues from Nexus-IQ (Technical Debt)
    1. Angular upgrade to address the security issue - may impact partnering apps like Policy and VID.
    2. Possibly in phases - start removing the vulnerabilities that are maeked as - "Not vulnerable in ONAP".
    3. Fix pending Fortify issue
  4. API Versioning and Backward Compatibility (Technical Debt)
  5. Performance and Optimization (Technical Debt)
    1. Memory usage optimization
    2. Split DB, Portal and SDK docker images
    3. UI upgrades - Angular, Bower
    4. Simplify deployment by avoiding the etc/hosts file entries
    5. Logging enhancements
  6. Testing (Technical Debt)
    1. Convert ECOMP selenium tests into CSIT ONAP Robot Framework tests.
    2. Code Coverage needs to be improved to 50% on both portal and portal/sdk repos with JavaScript.

1) Policy, VID, AAI, SDC apps that use portal/sdk will be directly impacted under S3P for logging support; also impacted under Security for AAF CADI support; also impacted under the JavaScript coverage support.

2) OOM deployment is impacted if the DB scaling changes is not support by Portal team; also the changes for simplification of etc/hosts entries impacts the OOM deployment which cannot be committed by Portal team.

To fill outTo fill out

Known Defects and Issues

Provide a link toward the list of all known project bugs.

...

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

Resources

Fill out the Resources Committed to the Release centralized page.

...