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
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | INT-120 |
---|
|
...
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 shows a rudimentry kibana dashboard of the current PASS numbers for ONAP OOM heath check.
![](/download/attachments/16007396/Screenshot%202017-11-13%2001.43.08.png?version=1&modificationDate=1510555529000&api=v2)
Design Issues
DI 1: 20171112: dockerdata-nfs mounted as root conflicts with Ubuntu or Jenkins user
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | OOM-422 |
---|
|
DI 2: 20171112: Reference ELK stack outside of ONAP for CD infrastructure
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-50 |
---|
|
DI 3: 20171112: DevOps Jenkins and CD Docker Infrastructure
On AWS as EC2 instances running docker versions of Jenkins, Nexus and Gitlab
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | OOM-417 |
---|
|
DI 4: 20171112: OOM Docker Image preload - to speed up pods to 8 min
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | OOM-328 |
---|
|
ONAP on Amazon EC2
Code Block |
---|
#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 |
Automated Official ONAP CI/CD Infrastructure
Links
OOM Deployment Status
Pending
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | INT-332 |
---|
|
...