blob: 87fba1306d03add97ba1bc123b6a73c52ed5790b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
|
---
author: Cédric Ollivier
title: OPNFV/CNTT CI assets
date: 2020/12/01
---
## Continuous integration
### A few CNTT reqs
- OPNFV has built a complete CI/CD toolchain for continuously deploying and
testing cloud infrastructure
- Reference conformance only requires for the local deployment of the
same components
- all test cases must be delivered as **Docker containers** including the
common test case execution and the unified way to manage all the interactions
**Integrate smoothly and deploy fastly**
### How OPNFV/CNTT helps?
- **Functest** offers a collection of state-of-the-art virtual infrastructure
test suites
- **Xtesting** helps assembling sparse test cases and accelerating the adoption
of CI/CD best practices
- **XtestingCI** eases deploying anywhere plug-and-play CI/CD toolchains in a
few commands
- **CNTT** defines conformance suites and its playbooks leveraging this 3
testing frameworks
**Leverage best opensource tools and practices**
### Testing [FTTH](https://en.wikipedia.org/wiki/Fiber_to_the_x) equipment
### Deploy your CI toolchain
```
virtualenv xtesting
. xtesting/bin/activate
pip install ansible
ansible-galaxy install collivier.xtesting
git clone https://gerrit.opnfv.org/gerrit/functest-xtesting functest-xtesting-src
ansible-playbook functest-xtesting-src/ansible/site.yml
deactivate
rm -rf functest-xtesting-src xtesting
```
**More scenarios in [[1]](https://wiki.opnfv.org/pages/viewpage.action?pageId=32015004)**
## Testing
### Verif', Compliance and Interop'
- verification allows skipping test if optional services or capabilities are
missing
- compliance forces the full API descriptions as currently proposed by
CNTT and then skips all optional capability testing
- the opensource certifications are driven by simple interoperability testing
(RefStack and OVP are about less than 10% of Functest. **trustability?**)
**Fine tune the same test frameworks**
### [CNTT RC1](https://build.opnfv.org/ci/view/functest/job/functest-leguer-daily/12/)
## Conclusion
### Key takeaways
- **test integration requirements** are crucial to smoothly assemble all
test cases
- leverage **existing** OPNFV testing knowledge (projects) and experience
(history) by utilising the OPNFV toolchain design already in-place
- **3000+** functional tests, **3 hours** upstream API and dataplane benchmarks
and VNFs automatically onboarded and tested **can be reused asis**
**Keep it simple and do not reivent the wheel**
|
