Morgan Richomme, Orange OPNFV provides lots of tooling that can be adopted and adapted to Service providers solution. These solutions are OpenStack based but not necessarily OPNFV solutions. This session will detail how some components developed in OPNFV have been introduced in Orange Integration Center, an OpenStack based vendor solution including Contrail SDN controller and third party elements. The best practices learned in OPNFV were used to design and build a CI chain including jenkins, functest, yardstick, the test API and the Test DB.

2. How to Reuse OPNFV Testing
Components in Telco Validation Chain
M.Richomme, Orange
T.Alleno, Orange
14/06/2017

3. Telco Cloud: a critical asset

5. Tooling & methodology needed
to qualify the Telco Cloud

6. Orange Integration Center
Organization & Labs to
• provide a flexible, performant,
context aware on demand Telco
Cloud for Orange Affiliates &
Business units
• Help on the industrialization of vUse
cases (vEPC, vCDN, vIMS, vCPE,
vWhatever…)

7. Integration network
Legacy Service
platforms
(TV, CDN, …)
Fixed access
Network
Mobile access
Network
NFVIs + VIMs
Tooling
& Support
Integration Center
Innovation
Center

8. OPNFV CI/CD – Platform CI
Jumphost
Initiate
Run for certain
Scenario
Download
ISO
Deploy Functest Yardstick
Pull Down
Functest Image
Pull Down
Yardstick Image
Labs connected 24x7
using JNLP
Google Cloud
Storage
Docker
Hub
Docker
Hub
Pharos POD
(SUT)

9. OPNFV CI/CD – Platform CI
Jumphost
Initiate
Run Tests for target
Scenario
Functest
(Acceptance)
Yardstick
(Performance)
Pull Down
Functest Image
Pull Down
Yardstick Image
Jenkins Automation
Docker
Hub
Docker
Hub
Integration Center
PODs
Versioning of tests & env
Customized configuration files
Additional test suites
Internal Test Result
Database

11. Community Orange Integration Center
Installers 4 in Danube (Apex, compass, Fuel,
Joid)
Preproduction
Director.: Environment is pre-
deployed. Work on installation
automation planned
Experimental
2 OPNFV community labs
(Compass/Fuel(x86 &
aarch64)/Joid/Openstack
Ansible)
Scenarios more than 35 in Danube! 1: OpenStack + Contrail Mainly focusing on « generic »
scenario
Tests Tests (automation): relying on several
test projects:
• Functest* for functional testing
• Yardstick* for performance testing
• Qtip for bench HW
• Storeperf for ceph
• Vsperf for Vswitch qualification
• Bottleneck to optimize Yardstick runs
* used for release validation
Tests (automation): reuse Functest
and Yardstick with some
adaptations on test environment
and configuration files
Some tests are excluded
Functest & Yardstick (CI)
Qtip (Plugfest)
Features Doctor, promise, bgpvpn, fdio, sfc, kvm,
barometer, open-o, and many more
Not used for now Depends on scenario

13. SLA

14. • Extend Functest (vIMS)
• Extend Yardstick (lots of additional tests to be
evaluated)
• Add Storperf Qtip, VSPerf, Bottleneck, Dovetail
support
• Include feature tests (security_scan, ...)
Next steps

15. Conclusions
• Integration of OPNFV tooling is very
valuable
• Adaptations (to non OPNFV system) are
relatively simple
• Possibility to compare with community
results also very valuable
• It will be great if VNF vendors could
develop test suites integrable on such
ecosystems

16. 谢谢 Thank you