Description of Use Case / Requirement:

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

Owners (one of these should be the Assignee - use @ notation):

Link to HLD/LLD (if any):

Dependency Relationships with Other Projects:

Project Impact (Test Only (TO), Code (C)):

Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):

Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.

Integration Leads (use @ notation): 

Company Engagement: