-
Story
-
Resolution: Done
-
High
-
None
-
OOM Sprint 5, OOM Sprint 7
2018010: update: CD POC on https://lists.onap.org/pipermail/onap-discuss/2018-January/007472.html
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.
#20171029 POC working on EC2 Spot using AMI preconfigured with Rancher 1.6 server/client aws ec2 request-spot-instances --spot-price "0.25" --instance-count 1 --type "one-time" --launch-specification file://aws_ec2_spot_cli.json aws ec2 associate-address --instance-id i-048637ed92da66bf6 --allocation-id eipalloc-375c1d02 aws ec2 reboot-instances --instance-ids i-048637ed92da66bf6 root@ip-172-31-68-153:~# kubectl cluster-info Kubernetes master is running at https://url.onap.info:8880/r/projects/1a7/kubernetes:6443 Heapster is running at https://url.onap.info:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/heapster/proxy KubeDNS is running at https://url.onap.info:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/kube-dns/proxy (4 more)
Work with Integration team - they have a framework
- blocks
-
AAI-189 AAI Deployment Integration Jenkins job using OOM-K8S - to validate branch
- Closed
-
INT-369 Team level notification+E2E testing of in/out dependency changes - procedure
- Closed
- duplicates
-
LOG-300 CD: OOM framework for continuous E2E deploy validation of tagged commit/merge trigger docker snapshots
- Closed
- is blocked by
-
OOM-328 Preload docker images to allow 7 min startup
- Closed
-
AAI-614 AAI: Refactor CHEF out or enable $TAG passed into chef branch git pull in traversal/resources to enable CI/CD
- Closed
- is duplicated by
-
CLAMP-671 ONAP on AWS
- Closed
- relates to
-
INT-284 Proper Release Management for Deployments
- Closed
-
LOG-289 CNCF CrossCloud Deployment/CI Integration with ONAP
- Closed
-
LOG-320 CD: OOM deployment templates for public cloud (Arm, CloudFormation, Heat)
- Closed
-
LOG-300 CD: OOM framework for continuous E2E deploy validation of tagged commit/merge trigger docker snapshots
- Closed
-
INT-120 Deployment Status Sanity - Daily auto E2E verification status of the build
- Closed
-
LOG-266 F2F: ONAP CI/CD using OOM Kubernetes
- Closed
-
INT-300 CI-CD For ONAP master branch
- Closed
-
OOM-494 Add create/clean ONAP config operation in oom/kubernestes/oneclick directory
- Closed
- mentioned in
-
Page Loading...