Status

OOM Deployment Status

Heat and OOM JIRA Tracking

Auto Continuous Deployment via Jenkins and Kibana

Live CD

https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/

AWS http://jenkins.onap.info/job/oom-cd-master/

Azure http://jenkins.onap.cloud/job/oom-cd-master/

Design Issues

Full CI/CD at ONAP

DI 1: Scheduled daily CD build

DI 2: Align Jienkins snapshot tagging timestamp format

DI 3: New Gerrit commands like runcsit-closed-loop

DI 4: LF: Add OOM Helm charts as values.yaml inputs into the OOM CD deploy

Jessica Wagantall of the Linux foundation

Meetings

Meeting 20180125

https://lists.onap.org/pipermail/onap-discuss/2018-January/007636.html

LOG-300: CD: OOM framework for continuous E2E deploy validation of tagged commit/merge trigger docker snapshotsClosed

Discussion for LF:

 tagging? snapshot/staging - https://nexus3.onap.org/#browse/browse/components:docker.snapshot 

https://nexus.onap.org/content/repositories/snapshots/org/onap/aai/traversal/aai-traversal/1.2.0-SNAPSHOT/

matches

https://jenkins.onap.org/view/aai/job/aai-traversal-master-merge-java/

Tests themselves (SRG/LRG)?

Deployment (full, upgrade)

Depending on project level of interface (rest API) testing - full deployment testing not as relevant

Q we are asking? maybe only relevant for developers

For dev is this mornings build broken?

---------------------

Alexis proposals:

LF/Jenkins-devops: New Gerrit commands: runcsit-closed-loop on demand in gerrit - Michael O'Brien drive

Daily granularity to full CD - daily scheduled

single snapshot

short regression deploy test (upgrade single container)

LF task: oom Helm charts from a dev/customer into the CD process - down

(configurable by nexus server, docker image names, docker tags) - Jessica Wagantall

Michael to put up wiki on integration project page for CI/CD - all can edit

Meeting 20180201

TBD

DevOps

Infrastructure

Links