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.

Amazon AWS is currently hosting our RI for ONAP Continuous Deployment on my private account for now - I have requested a grant specific to the jenkins, kibana and cd instances.

see Cloud Native Deployment#AmazonAWS

see

TSC 2019-01-03

TSC-25: Task Force to implement CD (Continuous Deployment)Closed

https://lists.onap.org/g/onap-discuss/topic/cd_task_force_tsc_25_meetings/29001640?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,29001640

ONAP Live AWS CD Servers

CD Architecture

Open

CD Demo Videos

20171210 showing a full CD job on the jenkins server	Open

Kibana Dashboard of CD system diagnosing health check issues in an Hourly ONAP OOM Deploy

In the combined ELK and Kibana CD system below we can see that SDC is failing healthcheck on average about 35% of the time - this may be due to a gap between healthcheck using a 200 HTTP return, the SDC rest call timing out when Spring is still coming up on the servlet container or a dependency check in SDC itself on another component where a particular startup order or timing of calls exposes an issue - anyway the ELK system that consumes logs from the hourly build can identify issues like this or the 1 hour healthcheck failure in MSB below that for 14 components that was transient.

Open

SDC-739: CD healthcheck of SDC failing periodically 35% of the time (since Feb 75%)Closed

OOM-496: Readiness check is marking full availability of some components like SDC and SDNC before they would pass healthcheckClosed

@Shane Daniel has created a dashboard on our AWS POC that can be used to diagnose the health of the current hourly build based on logs generated by the health check running in robot off an hourly deploy of ONAP OOM (CI triggers are pending)

For example there was a hard coded token in kube2msb that was causing some healthcheck failures - notice the drop in failures 3 hours ago within an hour after the submit to the OOM framework (Immediate because the config is not currently part of the daily-only docker builds) 

https://gerrit.onap.org/r/#/c/27943/ for

https://jira.onap.org/browse/OOM-570

Automated POC ONAP CD Infrastructure

Tracking JIRAs

INT-120: Deployment Status Sanity - Daily auto E2E verification status of the buildClosed

LOG-332: Deployment CI/CD Integration Jenkins job using OOM-K8S - to validate branchClosed

https://lf-onap.atlassian.net/browse/OOM-393

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.

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: onap-config pod creation 12 min instead of 2 when dockerdata-nfs content was not deleted previouslyClosed

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

LOG-50: Reference ELK stack for testingClosed

DI 3: 20171112: DevOps Jenkins and CD Docker Infrastructure

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

LOG-268: F2F 201712 conf only: CD JenkinsClosed

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

https://lf-onap.atlassian.net/browse/OOM-328

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

ONAP on Kubernetes on Amazon EC2#AWSCLIEC2CreationandDeployment

DI 6: 20171112: Migrate Jenkins job to ONAP sandbox

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

current ssh config

/var/jenkins_home/workspace/shared_aws_201801.pem

/var/jenkins_home/workspace/shared_aws_201801.pem obr..._aws_20141115.pem

Automated ONAP CD Infrastructure

We need sufficient resources to run two (amsterdam and beijing/master) deployments either hourly or on commit-trigger demand. 

We also need devops infrastructure to provision the servers (an ARM DMZ jumbox), run the jenkins container and ELK containers (a single Kubernetes cluster)

Resources

ONAP Deployment Specification for Finance and Operations#AmazonAWS

Performance

Static Server 4 hour Deploy Frequency

Resource Deployment Scripts

Azure

Links

OOM Deployment Status

https://github.com/obrienlabs/onap-ci/issues/1

Pending

INT-332: Rework ROBOT healthcheck reporting logs for ELK friendly CD frameworksClosed