...
5G Usecase Impacts on Portal platform (AT&T resources)
- Impact on Functional Menu for the usecase flows to different components.
- User next step recommendation feature can help new users that are not familiar with the 5G steps.
Security (AT&T 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
New features (Chinamobile, AT&T resources)
- Locale/Internationalization language support – UsecaseUI project integration. (Chinamobile resources committed for this feature)
- Angular 6 Upgrade of ONAP Portal and SDK
may impact partnering apps like Policy and VID
- Onboarding Apps: Pomba, SDN Self Service Portal & Admin Portal(Manoop/Sunder to validate) Use Case UI (FW Mode), MSB (FW Mode), CLAMP Designer
- Simplified Self Service Onboarding – Phase1Locale/Internationalization language support – UsecaseUI project integration.
- Reporting feature enhancement in portal/sdk.
Address ONAP Platform Maturity Guidelines
- 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
House Keeping (AT&T 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.
- Maintain documentation for the architecture, APIs and release notes.
Test Automation (IBM resources partially committed)
- Add new tests through Robot Framework for the new features.
- Perform pairwise testing – through automated tests for CLI, SDC, MSB, VID, Policy, AAI.
- Stability for Portal - platform level soak w/random transactions.
...
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 identified | Impact |
---|---|
Security (No committed resources)
Address ONAP Platform Maturity Guidelines (No committed resources)
New features (No committed resources - originally supported by IBM resource, so partially done - but not available anymore)
House Keeping (No committed resources)
| Risk1 - Security impact on Policy, VID apps that use portal/sdk regarding addressing NexusIQ security issues which is not committed by Portal team so far due to lack of resources; Risk2 - 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. |
Known Defects and Issues
Provide a link toward the list of all known project bugs.
...