Versions Compared

Old Version 11

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.

...

Table of Contents
outlinetrue

Overview

Project NameEnter the name of the projectPortal Platform
Target Release NameR1 Beijing R4 Dublin Release
Project Lifecycle StateIncubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company AT&T, ChinaMobile, TechM, IBM, HuaweiAmdocs

Scope

What is this release trying to address?

Scope: The scope of this release will be for the Portal Platform to support the below list: (provided the lead developers names who will be providing status on these committed features in weekly scrums)

5G Usecase Impacts on Portal platform (AT&T resources - Former user (Deleted) )

...

    • Locale/Internationalization language support – UsecaseUI project integration. (Chinamobile resources committed for this feature - Tao Shen)
    • Reporting feature enhancement in portal/sdk (AT&T resources - Former user (Deleted) )
    • Angular 6 Upgrade of ONAP Portal and SDK with 1 or 2 new UI screens (IBM and AT&T resources partially committed - Deven and Saravanan Madheswaran)
      • may impact partnering apps like Policy and VID 

House Keeping (AT&T resources - Lorraine A. Welch, Amdocs resources)

    • Maintain documentation for the architecture, APIs and release notes. (AT&T resources - Lorraine A. Welch)
    • Improved logging - (Amdocs resource - Michael O'Brien )

Test Automation (IBM resources partially committed - Sireesh Chintamani (Deactivated) )

...

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

Portal support top menu for "5G PNF Plug and Play" use case.

Minimum Viable Product

Describe Supporting 5G use case, Internationalization language support, and technology stack upgrade is the MVP for this release.

...

Indicate at a high level the longer term roadmap. This is to put things into the big perspective.

Requirements for Dublin release - road map

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

...

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

...

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.

...

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
InternationalizationAPIsTo support language and localeM3M4

UsecaseUI team to contribute the details as they collaborating with Portal team on this requirement.

*Multi-Language Functionality API List:

  • GET  /auxapi/languageSetting/user/{loginId}                    Gets login user language setting in Portal
  • PUT  /auxapi/languageSetting/user/loginId}                     Updates login user language setting in Portal
  • POST  /auxapi/language                                                          Adds a language option in Portal
  • DELETE  /auxapi/language                                                     Deletes a language option in Portal
  • GET  /auxapi/languages                                                          Gets all language options in Portal

 

Third Party Products Dependencies

...

Gaps identifiedImpact

Security (No committed resources)

    • AAF integration for partners - SDC, AAI requires SDK upgrade.
    • AAF certificate management integration (both for FE HTTPs and BE rest API calls, widget MicroService, Cassandra, DB)
    • API Access restrictions - Utilize CADI Integration to secure system to system communication
    • Addressing security issues – NexusIQ Critical and Severe issues; maintaining CII badging;

New features (No committed resources)

    • Onboarding Apps: Pomba, SDN Self Service Portal & Admin Portal, Use Case UI (FW Mode), MSB (FW Mode), CLAMP Designer 
    • Simplified Self Service Onboarding – Phase1 

Address ONAP Platform Maturity Guidelines (No committed resources)

    • Support deployment, scalability issues of the platform (DB docker- Galera Cluster)
    • Music Cassandra as a service - integration
    • Music team to provide DB as a service
    • Improve integration with OOM deployment.
    • Switch from dedicated MariaDB to centralized ONAP Database as a service (OOM Team integration).
    • Some dockers use mysql in onap, some use mariadb, different dockers use the same database version is also inconsistent, resulting in very confusing, it is recommended to have a unified version and software.
    • API versioning and backward compatibility support

House Keeping (No committed resources)

    • Improve code coverage from 65% to 80% - JUnit Test Coverage;
    • Address Sonar reported critical issues;
    • Improved logging, docker separation, and SDK Simplification.
      • Split DB, Portal and SDK docker images
      • Simplify deployment by avoiding the etc/hosts file entries
    • Footprint optimization: reduce image size, avoid image duplications, reduce memory requirements.

Updated in Dublin Risks

Risk#3 - Security impact on Policy, VID apps that use portal/sdk regarding addressing NexusIQ security issues and AAF integration which is not committed by Portal team so far due to lack of resources;

Risk#4 - Impacts Dublin platform maturity requirements (Footprint Optimization, Logging Capabilities). Also, OOM deployment is impacted if the DB scaling changes are not supported by Portal team; also the changes for simplification of etc/hosts entries impacts the OOM deployment which is not committed by Portal team so far due to lack of resources.


...

Risk identifiedMitigation PlanContingency Plan
ResourcesActively seeking community support.Current resources are not enough to satisfy even the Highest Priority Epics

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.