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

Compare with Current View Page History

« Previous Version 2 Next »


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.

Automated POC ONAP CD Infrastructure

Tracking JIRAs  INT-120 - 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 Dashboards24 hour Dashboard - filtered on "message: PASS"


Design Issues

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


Automated Official ONAP CI/CD Infrastructure

Pending

INT-332 - Getting issue details... STATUS


  • No labels