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

3. Telco Cloud: a critical asset

4. We will not deploy OPNFV mainstream
Solution not mature
Internal organization not ready
Traditionnal relationship with vendors
We can mention that we have a meanstream product through Cloudwatt for Public Cloud

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. Legacy Service platforms
Integration Center
Tooling
& Support
NFVIs + VIMs
Innovation Center
Integration network
Fixed access
Network
Mobile access
Network
Legacy Service platforms
(TV, CDN, …)

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

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

10. And it is planned to leverage the other test projects

11. Orange Integration Center
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. Next steps Extend Functest (vIMS)
Extend Yardstick (lots of additional tests to be evaluated)
Add Storperf Qtip, VSPerf, Bottleneck, Dovetail support
Include feature tests (security_scan, ...)

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