Date: Fri, 29 Mar 2024 09:36:18 +0000 (UTC) Message-ID: <1360343754.1546.1711704978419@759870d846b0> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1545_1099139619.1711704978418" ------=_Part_1545_1099139619.1711704978418 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The NFVbench project develops a toolkit that allows developers, = integrators, testers and customers to measure and assess the L2/L3 forwardi= ng performance of an NFV-infrastructure solution stack (i.e. OPNFV scenario= ) using a black-box approach.
NFVbench is available as a self-contained docker container that includes= the the main application and the Trex software traffic generator.
NFVbench is agnostic of the NFV platform, the controller used (ML2/OVS, = ODL...), the network stack used (OVS, OVS-DPDK, VPP, SR-IOV...) and support= s VLAN and VxLAN.
NFVbench is currently widely deployed in production NFV clouds around th= e world by multiple service providers and is mostly used for
NFVbench is also currently used as the traffic generator solution for th= e CNCF CNF testbed based on packet.net: CNF testbed slides.
There is no mailing=
list dedicated to NFVbench.
For inquiries and questions: =
;send an email to anuket-=
tech-discuss@lists.anuket.io with a Subject line starting with"#nfvbench"
The list archives can be&nbs=
p;consulted and searched here:
https://lists.anuket.io/g/anuket-tec=
h-discuss/search?q=3D%23nfvbench&ct=3D1
OPNFV list archives:
https://lists.o= pnfv.org/g/opnfv-tech-discuss/search?q=3D%23nfvbench&ct=3D1
Available versions of&nb=
sp;NFVbench Docker images can be found on&nbs=
p;Docker hub:
https://hub.docker.com/r/opnfv/nfvbench/tags=
span>
No ChangeLog, look = at NFVbench commit log on nfvbench.org.
Note: there is&nbs= p;also a GitH= ub mirror for NFVbench, but it is more complic= ated to see the= association between commit history and tags<= /span>
For a given version=
of NFVbench container image on Docker=
hub, TRex version can be found in the TREX_VER enviro=
nment variable in the image history. Fo=
r
instance, NFVbench&n=
bsp;Docker image version 3.4.1 is based on&nb=
sp;TRex 2.56 as can be seen here.
For a given =
;version of NFVbench code base, the&nb=
sp;version of TRex that would be embedded in a Docker contai=
ner built from that code base is given&n=
bsp;in the
TREX_VER=
span> environment variable =
found in docker/Dockerfi=
le For instance, =
span>NFVbench code base&nbs=
p;tagged 3.6.1=
a> is meant to =
be used with TRex 2.61 as can be se=
en in the Docke=
rfile.
The list of the&nbs=
p;artifacts generated by NFVbench project, includi=
ng all versions of&n=
bsp;NFVbench loop VM, can be found here:
https://art=
ifacts.opnfv.org/nfvbench.html. Look for nfvbench/images.