You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »


In collaboration with the ONAP Operations Manager project at ONAP - our current RI.

The goal of this page is to provide an E2E infrastructure for testing an hourly or triggered master/tagged build for the purposes of declaring it ready in terms of health check and use case functionality.  CD functionality includes providing real-time and historical analytics of build health via stored/indexed logs from the deployment jobs in our ELK stack that sits outside of ONAP.

Build status and history

Automated POC ONAP CD Infrastructure

Tracking JIRAs

INT-120 - Getting issue details... STATUS

OOM-150 - Getting issue details... STATUS

OOM-393 - Getting issue details... STATUS

A custom Jenkins job that runs a full deployment of ONAP OOM on another 64G VM is currently in progress.  There are pending design issues under vFirewall automation, reporting results and general resiliency.  


OOM Jenkins Automated Continuous Deployment Results

There are several methods of communicating the current deployment status being worked out.  Currently raw Jenkins build pages and POC dashboards in Kibana are being worked out.

Hourly Deployment Results
Jenkins Jobshttp://jenkins.onap.info/job/oom-cd/
Live Kibana Dashboards

24 hour Dashboard - filtered on "message: PASS"

24 hour live deployment logs


The following is a split screen on an hourly build of OOM and the logs generated by the deployment process.

The following shows a rudimentry kibana dashboard of the current PASS numbers for ONAP OOM heath check.

Design Issues

DI 1: 20171112: dockerdata-nfs mounted as root conflicts with Ubuntu or Jenkins user

OOM-422 - Getting issue details... STATUS

DI 2: 20171112: Reference ELK stack outside of ONAP for CD infrastructure

LOG-50 - Getting issue details... STATUS

DI 3: 20171112: DevOps Jenkins and CD Docker Infrastructure

On AWS as EC2 instances running docker versions of Jenkins, Nexus and Gitlab

OOM-417 - Getting issue details... STATUS

CD instance is currently static until Rancher 2.0 is finished acceptance testing at ONAP

DI 4: 20171112: OOM Docker Image preload - to speed up pods to 8 min

OOM-328 - Getting issue details... STATUS

DI 5: 20171112: Strategy for Manual Config of Rancher 1.6 for Auto Create/Delete of CD VM

ONAP on Amazon EC2

#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:6


DI 6: 20171112: Migrate Jenkins job to ONAP sandbox

Cannot get creation access to https://jenkins.onap.org/sandbox/ via Configuring Jenkins

Automated Official ONAP CI/CD Infrastructure

Links

OOM Deployment Status

Pending

INT-332 - Getting issue details... STATUS

  • No labels