-
Story
-
Resolution: Done
-
High
-
None
-
None
Issue: We need a way to validate the build as part of ONAP in a running environment
This will require bringing all docker containers dependent on AAI.
For example until 20170810 AAI failed to come up due to a v11 schema issue - although this could have been verified using a clean install of AAI and some robot rest calls - a full deployment integration test should be required.
Ideally we write up a jenkins job that brings up all or parts of ONAP in OOM Kubernetes on a VM and runs E2E robot health checks for a start.
Work with Integration team - they have a framework
- is blocked by
-
LOG-332
Deployment CI/CD Integration Jenkins job using OOM-K8S - to validate branch
-
- Closed
-
- relates to
-
AAI-140 AAI1 rackspace fails to start 8443 API model-loader and 8446 graph/traversal container - resources container timeout
-
- Closed
-
-
LOG-320
CD: OOM deployment templates for public cloud (Arm, CloudFormation, Heat)
-
- Closed
-
-
INT-106
Stabilizing the ONAP master branch
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-