LF Infra Collaboration Infra Alignment Workstream OPNFV Infra

LF Infra Collaboration Infra Alignment Workstream OPNFV Infra and Test Working Groups

Agenda • What OPNFV does? • Infra, CI/CD & Test Projects, Working Groups • Labs, Tools, CI/CD Setup • Test Ecosystem • Challenges • Ongoing/Planned Infra, CICD & Test Activities • How can we help each other? 1/18/17 LF Infra Collab

What OPNFV does? Additions Enhancements 1/18/17 LF Infra Collab

Infra, CI/CD & Test Projects, Working Groups Infra Working Group Pharos Releng Octopus Genesis 1/18/17 LF Infra Collab Testing Working Group Functest Bottlenecks Yardstick Vsperf Storperf Qtip Cperf

Infrastructure – Distributed Pharos Labs 1/18/17 LF Infra Collab

Pharos Architecture

The Tools 1/18/17 LF Infra Collab

OPNFV CI/CD – Project CI Google Cloud Storage Patch Poll changes Verified +1/-1 Upload ISO Clone repo Build new changes? yes Build Server Patchset Verification Push Image no Docker Hub 1/18/17 LF Infra Collab

OPNFV CI/CD – Platform CI Google Cloud Storage Download ISO Docker Hub Pull Down Functest Image Pull Down Yardstick Image Labs connected 24 x 7 using JNLP Initiate Run for certain Scenario Deploy Functest Yardstick Jumphost Pharos POD (SUT) 1/18/17 LF Infra Collab

OPNFV Test Ecosystem 1 1/18/17 LF Infra Collab

Challenges • Being a midstream project • OPNFV Development Workflow – slow feedback • OPNFV CI/CD – traceability, reproducibility, consistency, capability • Diverse infrastructure, low utilization/improper use of resources • Ever increasing number of feature combinations • Community awareness and resistance to change 1/18/17 LF Infra Collab

Ongoing and Planned Infra/CICD Activities Pharos Dashboard Lab as a Service CI Evolution 1/18/17 LF Infra Collab Common Config Files Dynamic POD Allocation Validator Cross Community CI

OPNFV Development Workflow Project Team OPNFV Gerrit OPNFV CI/Test OPNFV Release Upstream Gerrit Upstream CI/Test Upstream Release Requirement Patch Fast feedback Test Release Document Downstream Test Release 1/18/17 LF Infra Collab • • • Long developmentcycle Fast development Downstream will< delay Fast feedback, 1 day to next release Slow feedback, 5 months OPNFV specific>issues can be OPNFV specific in issues tested/detected time; cannot be tested/detected in time Correction in same release

Cross Community CI contribute 1/18/17 LF Infra Collab contribute pull from master, deploy, test and/or verify patchset, post feedback contribute

Ongoing and Planned Test Activities: Danube priorities Activity Goal Status Testing group reporting landing page Be more Scenario centric Get scenario status at glance Patch submited, integration in progress Evolution of Test API Test case catalog Provide a consistent way to discover all the test cases available Create a portal to describe the different test cases (possibility to declare them by domains, key words, . . ) Stress test Include a stress test for scenario validation Tooling was already there, discussion in progress to identify a realistic scenario Documentation Create an umbrella documentation In addition of cross review done in Colorado, create an umbrella document 1/18/17 LF Infra Collab

Ongoing and Planned Test Activities: beyond Danube • • • Promotion mechanism for test and scenario More stress tests Elaboration of KPI = f(Hardware) Tool to visualize domain activity and focus and uncovered or poorly covered area MANO stack testing New domain testing (monitoring, security, . . ) More Analytics VNF testing evolution Micro service evolution between the test projects (expose and consume API from different test projects) 1/18/17 LF Infra Collab

How can we help each other? • Make artifacts with known quality frequently available, easily consumable, automatically deployable and potentially in a similar way – Your artifacts every 6 months -> Feedback from OPNFV > 10 months – Your artifacts on a daily basis -> Feedback from OPNFV < 1 week • Treat all the artifact you produce as candidates for release (CD) – OPNFV should be able to pull them down with confidence any time without you knowing • Make sure to have traceability & reproducibility (CII Badging) – If you don’t keep record of what your build consists of and can’t reproduce them, we never can 1/18/17 LF Infra Collab

Questions?