blob: 3bed0147a93d5af1a260e1cb30190a17383057ea (
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
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
|
# Functest
Network virtualization has dramatically modified our architectures which asks
for more automation and powerful testing tools like Functest, a collection of
state-of-the-art virtual infrastructure test suites, including automatic VNF
testing (cf.
[[1]](https://www.linuxfoundation.org/press-release/2019/05/opnfv-hunter-delivers-test-tools-ci-cd-framework-to-enable-common-nfvi-for-verifying-vnfs/)).
In context of OPNFV, Functest verifies any kind of OpenStack and Kubernetes
deployments including production environments. It conforms to upstream rules
and integrates smoothly lots of the test cases available in the opensource
market. It includes about 3000+ functional tests and 3 hours upstream API and
dataplane benchmarks. It’s completed by Virtual Network Function deployments
and testing (vIMS, vRouter and vEPC) to ensure that the platforms meet Network
Functions Virtualization requirements. Raspberry PI is also supported to verify
datacenters as the lowest cost (50 euros hardware and software included).
| Functest releases | Kubernetes releases |
|-------------------|---------------------------|
| Hunter | v1.13 |
| Iruya | v1.15 |
| Jerma | v1.17 |
| **Kali** | **v1.19** |
| Leguer | v1.20 |
| Master | v1.21.0-alpha.3 (rolling) |
## Prepare your environment
cat env
```
DEPLOY_SCENARIO=k8s-XXX
```
## Run healthcheck suite
```bash
sudo docker run --env-file env \
-v $(pwd)/config:/root/.kube/config \
opnfv/functest-kubernetes-healthcheck:kali
```
```
+-------------------+------------------+---------------------+------------------+----------------+
| TEST CASE | PROJECT | TIER | DURATION | RESULT |
+-------------------+------------------+---------------------+------------------+----------------+
| k8s_quick | functest | healthcheck | 00:24 | PASS |
| k8s_smoke | functest | healthcheck | 00:09 | PASS |
+-------------------+------------------+---------------------+------------------+----------------+
```
## Run smoke suite
```bash
sudo docker run --env-file env \
-v $(pwd)/config:/root/.kube/config \
opnfv/functest-kubernetes-smoke:kali
```
```
+---------------------------+------------------+---------------+------------------+----------------+
| TEST CASE | PROJECT | TIER | DURATION | RESULT |
+---------------------------+------------------+---------------+------------------+----------------+
| k8s_conformance | functest | smoke | 76:12 | PASS |
| xrally_kubernetes | functest | smoke | 12:22 | PASS |
+---------------------------+------------------+---------------+------------------+----------------+
```
## Run security suite
```bash
sudo docker run --env-file env \
-v $(pwd)/config:/root/.kube/config \
opnfv/functest-kubernetes-security:kali
```
```
+---------------------------+------------------+------------------+------------------+----------------+
| TEST CASE | PROJECT | TIER | DURATION | RESULT |
+---------------------------+------------------+------------------+------------------+----------------+
| kube_hunter | functest | security | 00:19 | PASS |
| kube_bench_master | functest | security | 00:01 | PASS |
| kube_bench_node | functest | security | 00:01 | PASS |
+---------------------------+------------------+------------------+------------------+----------------+
```
## Run benchmarking suite
```bash
sudo docker run --env-file env \
-v $(pwd)/config:/root/.kube/config \
opnfv/functest-kubernetes-benchmarking:kali
```
```
+--------------------------------+------------------+----------------------+------------------+----------------+
| TEST CASE | PROJECT | TIER | DURATION | RESULT |
+--------------------------------+------------------+----------------------+------------------+----------------+
| xrally_kubernetes_full | functest | benchmarking | 33:07 | PASS |
+--------------------------------+------------------+----------------------+------------------+----------------+
```
## Run cnf suite
```bash
sudo docker run --env-file env \
-v $(pwd)/config:/root/.kube/config \
opnfv/functest-kubernetes-cnf:kali
```
```
+-------------------------+------------------+--------------+------------------+----------------+
| TEST CASE | PROJECT | TIER | DURATION | RESULT |
+-------------------------+------------------+--------------+------------------+----------------+
| k8s_vims | functest | cnf | 09:09 | PASS |
| helm_vims | functest | cnf | 08:01 | PASS |
| cnf_conformance | functest | cnf | 02:15 | PASS |
+-------------------------+------------------+--------------+------------------+----------------+
```
## Use on air gap environments (no access to Internet)
To test a Kubernetes without access to Internet, repository mirrors needs to be
provided.
Currently, all tests supports this feature except cnf conformance.
There's two ways for providing the repository mirrors:
- Give an environment variable (`MIRROR_REPO`) which gives a repository with
all needed images.
- Gives an environment variable per needed repo:
- `DOCKERHUB_REPO` for DockerHub repository (`docker.io`)
- `GCR_REPO` for Google Cloud repository (`gcr.io`)
- `K8S_GCR_REPO` for Kubernetes repository (`k8s.gcr.io`)
- `QUAY_REPO` for Quay repository (`quay.io`)
All needed images are given in
[functest-kubernetes/ci/images.txt](functest-kubernetes/ci/images.txt)
For e2e tests, `docker.io` is hardcoded. it does mean that you'll have to set up
a mirror on docker. An example on how to set it up on docker daemon is provided
here:
[daemon-configuration-file](
https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-configuration-file)
|
