Skip to end of metadata
Go to start of metadata

Scope

What is this release trying to address?

More test automation, consolidate and extend Gating to ensure a better release stability

Requirements

N.R

Minimum Viable Product

A Fully validated release with as many automated cases as possible.

Functionalities

  • o-parent updated
  • new use cases
  • enhanced use cases
  • integration gate
  • Daily CI chains
  • Gating chains for OOM and other components


Recently Updated

Epics

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Stories

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Tasks

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Bugs

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Longer term roadmap

Integration gate shall be deployable and runnable on any ONAP solution to run use cases validated for a given release.

The traditionnal wiki page shoudl be progressively replaced by a fully programatic way to test your ONAP with realistic use cases

Release Deliverables


Deliverable Name

Deliverable Description

Heat and helm charts + associated scripts

scripts and descriptors needed to perform the use cases (new and update)
DocumentationUpdate of the existing documentation including verified use case documentation
Release Note

Sub-Components

  • integration
  • integration/csit
  • testsuite
  • testsuite-heatbridge
  • testsuite-python-testing-utils
  • demo
  • xtesting

Edit the Release Components name for your project in the centralized page.

Architecture

High level architecture diagram

N.R for Integration

API Incoming Dependencies

We are playing with the API of all the components or almost...

API Outgoing Dependencies

N.R

Third Party Products Dependencies

Done programatically trhough requirements.txt


Testing and Integration Plans

  • CSIT tests
  • Gating
  • Integration tests
  • Automation of the tests

Gaps

Known Defects and Issues

Risks

  • Lack of resource
    • Not enough people to create and automate the tests
    • Lack of hardware / labs
    • Low hardware capabilities in labs (experienced in the past)
  • Please update any risk on the centralized wiki page - Frankfurt Risks

Resources

Release Milestone

  • The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

Documentation, Training

  • No labels