3 Network virtualization has dramatically modified our architectures which asks
4 for more automation and powerful testing tools like Functest, a collection of
5 state-of-the-art virtual infrastructure test suites, including automatic VNF
7 [[1]](https://www.linuxfoundation.org/press-release/2019/05/opnfv-hunter-delivers-test-tools-ci-cd-framework-to-enable-common-nfvi-for-verifying-vnfs/)).
9 In context of OPNFV, Functest verifies any kind of OpenStack and Kubernetes
10 deployments including production environments. It conforms to upstream rules
11 and integrates smoothly lots of the test cases available in the opensource
12 market. It includes about 3000+ functional tests and 3 hours upstream API and
13 dataplane benchmarks. It’s completed by Virtual Network Function deployments
14 and testing (vIMS, vRouter and vEPC) to ensure that the platforms meet Network
15 Functions Virtualization requirements. Raspberry PI is also supported to verify
16 datacenters as the lowest cost (50 euros hardware and software included).
18 | Functest releases | Kubernetes releases |
19 |-------------------|-------------------------------|
25 | **Master** | **v1.24.0-alpha.1 (rolling)** |
27 ## Prepare your environment
31 DEPLOY_SCENARIO=k8s-XXX
34 ## Run healthcheck suite
37 sudo docker run --env-file env \
38 -v $(pwd)/config:/root/.kube/config \
39 opnfv/functest-kubernetes-healthcheck
43 +-------------------+------------------+---------------------+------------------+----------------+
44 | TEST CASE | PROJECT | TIER | DURATION | RESULT |
45 +-------------------+------------------+---------------------+------------------+----------------+
46 | k8s_quick | functest | healthcheck | 00:18 | PASS |
47 | k8s_smoke | functest | healthcheck | 01:14 | PASS |
48 +-------------------+------------------+---------------------+------------------+----------------+
54 sudo docker run --env-file env \
55 -v $(pwd)/config:/root/.kube/config \
56 opnfv/functest-kubernetes-smoke
60 +----------------------------------+------------------+---------------+------------------+----------------+
61 | TEST CASE | PROJECT | TIER | DURATION | RESULT |
62 +----------------------------------+------------------+---------------+------------------+----------------+
63 | xrally_kubernetes | functest | smoke | 13:00 | PASS |
64 | k8s_conformance | functest | smoke | 16:31 | PASS |
65 | k8s_conformance_serial | functest | smoke | 15:34 | PASS |
66 | sig_api_machinery | functest | smoke | 09:01 | PASS |
67 | sig_api_machinery_serial | functest | smoke | 01:24 | PASS |
68 | sig_apps | functest | smoke | 03:45 | PASS |
69 | sig_apps_serial | functest | smoke | 00:31 | PASS |
70 | sig_auth | functest | smoke | 09:04 | PASS |
71 | sig_cluster_lifecycle | functest | smoke | 00:26 | PASS |
72 | sig_instrumentation | functest | smoke | 00:03 | PASS |
73 | sig_network | functest | smoke | 05:43 | PASS |
74 | sig_node | functest | smoke | 28:03 | PASS |
75 | sig_scheduling_serial | functest | smoke | 08:03 | PASS |
76 | sig_storage | functest | smoke | 09:17 | PASS |
77 | sig_storage_serial | functest | smoke | 02:40 | PASS |
78 +----------------------------------+------------------+---------------+------------------+----------------+
84 sudo docker run --env-file env \
85 -v $(pwd)/config:/root/.kube/config \
86 opnfv/functest-kubernetes-security
90 +---------------------------+------------------+------------------+------------------+----------------+
91 | TEST CASE | PROJECT | TIER | DURATION | RESULT |
92 +---------------------------+------------------+------------------+------------------+----------------+
93 | kube_hunter | functest | security | 00:19 | PASS |
94 | kube_bench_master | functest | security | 00:02 | PASS |
95 | kube_bench_node | functest | security | 00:01 | PASS |
96 +---------------------------+------------------+------------------+------------------+----------------+
99 ## Run benchmarking suite
102 sudo docker run --env-file env \
103 -v $(pwd)/config:/root/.kube/config \
104 opnfv/functest-kubernetes-benchmarking
108 +--------------------------------+------------------+----------------------+------------------+----------------+
109 | TEST CASE | PROJECT | TIER | DURATION | RESULT |
110 +--------------------------------+------------------+----------------------+------------------+----------------+
111 | xrally_kubernetes_full | functest | benchmarking | 33:07 | PASS |
112 +--------------------------------+------------------+----------------------+------------------+----------------+
118 sudo docker run --env-file env \
119 -v $(pwd)/config:/root/.kube/config \
120 opnfv/functest-kubernetes-cnf
124 +-----------------------+------------------+--------------+------------------+----------------+
125 | TEST CASE | PROJECT | TIER | DURATION | RESULT |
126 +-----------------------+------------------+--------------+------------------+----------------+
127 | k8s_vims | functest | cnf | 09:06 | PASS |
128 | helm_vims | functest | cnf | 08:54 | PASS |
129 | cnf_testsuite | functest | cnf | 00:00 | SKIP |
130 +-----------------------+------------------+--------------+------------------+----------------+
134 ## Use on air gap environments (no access to Internet)
136 To test a Kubernetes without access to Internet, repository mirrors needs to be
139 Currently, all tests supports this feature except cnf conformance.
141 There's two ways for providing the repository mirrors:
143 - Give an environment variable (`MIRROR_REPO`) which gives a repository with
145 - Gives an environment variable per needed repo:
146 - `DOCKERHUB_REPO` for DockerHub repository (`docker.io`)
147 - `GCR_REPO` for Google Cloud repository (`gcr.io`)
148 - `K8S_GCR_REPO` for Kubernetes repository (`k8s.gcr.io`)
149 - `QUAY_REPO` for Quay repository (`quay.io`)
151 All needed images are given in
152 [functest-kubernetes/ci/images.txt](functest-kubernetes/ci/images.txt)
154 For e2e tests, `docker.io` is hardcoded. it does mean that you'll have to set up
155 a mirror on docker. An example on how to set it up on docker daemon is provided
157 [daemon-configuration-file](
158 https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-configuration-file)