You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Enhance ONAP Portal and support Dublin release: (review Portal impacts based on SP priorities for Dublin)

  • Security
    • Portal and SDK upgrade to integrate with AAF-CADI.
    • Addressing security issues – NexusIQ Critical and Severe issues; maintaining CII badging;
  • New features
    • Locale/Internationalization language support – UsecaseUI project integration.
    • Reporting feature enhancement in portal/sdk.
    • Angular 5 upgrade
  • Address ONAP Platform Maturity Guidelines
    • 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
    • Improve code coverage from 65% to 80% - JUnit Test Coverage;
    • Address Sonar reported critical issues;
    • Improved logging, docker separation, and SDK Simplification.
      • Footprint optimization: reduce image size, avoid image duplications, reduce memory requirements.
    • Maintain documentation for the architecture, APIs and release notes.
  • Test Automation
    • 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.

Plan and Support next ONAP “ElAlto” release:

    • Requirements planning for the E release.
    • Analyzing the technical impacts and Architecture impacts.
    • Propose the new features and resource planning.
  • No labels