Versions Compared

Old Version 16

changes.mady.by.user Alessandro Gerardo D'Alessandro

Saved on

compared with

New Version 17

changes.mady.by.user Alessandro Gerardo D'Alessandro

Saved on

Key

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

...

Key Contacts - Alessandro Gerardo D'Alessandromarco.signorelli@telecomitalia.it

Executive Summary -

...

ONAP code stability is steadly improved over the releases. Similarly is being happening for ONAP installation success rate. Anyway while it is recognized the OOM project efforts in providing an automation tool for ONAP installation, it is evident that further efforts are required among the ONAP projects to provide an overall solution that bring to a deterministic installation result.

Proposed non-functional requirements for Guiling release:

  1. ONAP installation result shall be determinstic at k8s level with 99% success rate  (e.g. all POD are up and running)
  2. ONAP installation result shall be deterministic at functional level with 97% success rate (e.g. all functional modules are up and running, APIs are responsiveness, etc)
  3. ONAP installation result shall be determinstic at service level with 95% success rate (e.g. a service can be designed, distributed and deployed successfully)

  4. Same requirements shall apply when one or more ONAP functional modules are re-installed

     

...