1 NFVBENCH VM IMAGES FOR OPENSTACK
2 ++++++++++++++++++++++++++++++++
4 This repo will build two centos 7 images with:
5 - testpmd and VPP installed for loop VM use case
6 - NFVbench and TRex installed for generator VM use case
7 These VMs will come with a pre-canned user/password: nfvbench/nfvbench
15 - the following packages must be installed prior to using this script:
23 - update the version number for the image (if needed) by modifying __version__ in build-image.sh
24 - setup your http_proxy if needed
25 - to build loop VM image only:
26 - `bash build-image.sh -l`
27 - to build generator VM image only:
28 - `bash build-image.sh -g`
29 - to build both images only:
30 - `bash build-image.sh`
32 LOOP VM IMAGE INSTANCE AND CONFIG
33 =================================
35 Interface Requirements
36 ----------------------
37 The instance must be launched using OpenStack with 2 network interfaces.
38 For best performance, it should use a flavor with:
42 - cpu pinning set to exclusive
46 nfvbench VM will automatically find the two virtual interfaces to use, and use the forwarder specifed in the config file.
48 In the case testpmd is used, testpmd will be launched with mac forwarding mode where the destination macs rewritten according to the config file.
50 In the case VPP is used, VPP will set up a L3 router, and forwarding traffic from one port to the other.
54 nfvbenchvm config file is located at ``/etc/nfvbenchvm.conf``.
59 INTF_MAC1=FA:16:3E:A2:30:41
60 INTF_MAC2=FA:16:3E:10:DA:10
61 TG_MAC1=00:10:94:00:0A:00
62 TG_MAC2=00:11:94:00:0A:00
63 VNF_GATEWAY1_CIDR=1.1.0.2/8
64 VNF_GATEWAY2_CIDR=2.2.0.2/8
67 TG_GATEWAY1_IP=1.1.0.100
68 TG_GATEWAY2_IP=2.2.0.100
71 Launching nfvbenchvm VM
72 -----------------------
74 Normally this image will be used together with NFVBench, and the required configurations will be automatically generated and pushed to VM by NFVBench. If launched manually, no forwarder will be run. Users will have the full control to run either testpmd or VPP via VNC console.
76 To check if testpmd is running, you can run this command in VNC console:
80 sudo screen -r testpmd
82 To check if VPP is running, you can run this command in VNC console:
89 Hardcoded Username and Password
90 --------------------------------
95 GENERATOR IMAGE INSTANCE AND CONFIG
96 ===================================
100 To use openstack APIs, NFVbench generator VM will use `clouds.yaml` file as openstack configuration.
101 The OpenStack clouds configuration from clouds.yaml file to use.
102 clouds.yaml file must be in one of the following paths:
103 - ~/.config/openstack
106 Example of `clouds.yaml`:
113 auth_url: http://192.168.122.10:35357/
117 region_name: RegionOne
119 .. note:: Add `CLOUD_DETAIL` property with the accurate value for your openstack configuration (`devstack` in the above example) in ``/etc/nfvbenchvm.conf``
121 Interface Requirements
122 ----------------------
123 The instance must be launched using OpenStack with 2 network interfaces for dataplane traffic (using SR-IOV function) and 1 management interface to control nfvbench.
124 For best performance, it should use network interfaces for dataplane traffic with a `vnic_type` to `direct-physical` (or `direct` if physical function is not possible)
129 - cpu pinning set to exclusive
131 .. note:: For the management interface: any interface type can be used. This interface required a routable IP (through floating IP or direct) and an access to the openstack APIs.
132 .. note:: CPU pinning: 1 core dedicated for guest OS and NFVbench process, other provided cores are used by TRex
134 Template of a genarator profile using CPU pinning:
142 zmq_pub_port: {{zmq_pub_port}}
143 zmq_rpc_port: {{zmq_rpc_port}}
144 software_mode: {{software_mode}}
147 master_thread_id: '0'
148 latency_thread_id: '1'
151 threads: [{{CORE_THREADS}}]
155 pci: "{{PCI_ADDRESS_1}}"
158 pci: "{{PCI_ADDRESS_2}}"
162 .. note:: `CORE_THREADS` value is determined automatically based on the cores available on the VM starting from 2 to last worker core available.
166 nfvbench VM will automatically find the two virtual interfaces to use for dataplane based on MAC addresses or openstack port name (see config part below).
167 This applies to the management interface as well.
171 nfvbenchvm config file is located at ``/etc/nfvbenchvm.conf``.
173 Example of configuration:
178 LOOPBACK_INTF_MAC1=FA:16:3E:A2:30:41
179 LOOPBACK_INTF_MAC2=FA:16:3E:10:DA:10
180 E2E_INTF_MAC1=FA:16:3E:B0:E2:43
181 E2E_INTF_MAC2=FA:16:3E:D3:6A:FC
183 .. note:: `ACTION` parameter is not mandatory but will permit to start NFVbench with the accurate ports (loopback or e2e).
184 .. note:: Set of MAC parameters cannot be used in parallel as only one NFVbench/TRex process is running.
185 .. note:: Switching from `loopback` to `e2e` action can be done manually using `/nfvbench/start-nfvbench.sh <action>` with the accurate keyword for `action` parameter. This script will restart NFVbench with the good set of MAC.
187 nfvbenchvm config file with management interface:
192 LOOPBACK_INTF_MAC1=FA:16:3E:A2:30:41
193 LOOPBACK_INTF_MAC2=FA:16:3E:10:DA:10
194 INTF_MAC_MGMT=FA:16:3E:06:11:8A
195 INTF_MGMT_CIDR=172.20.56.228/2
196 INTF_MGMT_IP_GW=172.20.56.225
198 .. note:: `INTF_MGMT_IP_GW` and `INTF_MGMT_CIDR` parameters are used by the VM to automatically configure virtual interface and route to allow an external access through SSH.
201 Using pre-created direct-physical ports on openstack, mac addresses value are only known when VM is deployed. In this case, you can pass the port name in config:
205 LOOPBACK_PORT_NAME1=nfvbench-pf1
206 LOOPBACK_PORT_NAME2=nfvbench-pf2
207 E2E_PORT_NAME1=nfvbench-pf1
208 E2E_PORT_NAME1=nfvbench-pf3
209 INTF_MAC_MGMT=FA:16:3E:06:11:8A
210 INTF_MGMT_CIDR=172.20.56.228/2
211 INTF_MGMT_IP_GW=172.20.56.225
212 DNS_SERVERS=8.8.8.8,dns.server.com
214 .. note:: A management interface is required to automatically find the virtual interface to use according to the MAC address provided (see `INTF_MAC_MGMT` parameter).
215 .. note:: NFVbench VM will call openstack API through the management interface to retrieve mac address for these ports
216 .. note:: If openstack API required a host name resolution, add the parameter DNS_SERVERS to add IP or DNS server names (multiple servers can be added separated by a `,`)
218 Control nfvbenchvm VM and run test
219 ----------------------------------
221 By default, NFVbench will be started in server mode (`--server`) and will act as an API.
223 NFVbench VM will be accessible through SSH or HTTP using the management interface IP.
225 NFVbench API endpoint is : `http://<management_ip>:<port>`
226 .. note:: by default port value is 7555
231 To check NFVbench is up and running use REST request:
235 curl -XGET '<management_ip>:<port>/status'
242 "error_message": "nfvbench run still pending",
249 To start a test run using NFVbench API use this type of REST request:
253 curl -XPOST '<management_ip>:<port>/start_run' -H "Content-Type: application/json" -d @nfvbenchconfig.json
255 Example of return when the submission is successful:
260 "error_message": "NFVbench run still pending",
261 "request_id": "42cccb7effdc43caa47f722f0ca8ec96",
266 Start NFVbench test using Xtesting
267 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
269 To start a test run using Xtesting python library and NFVbench API use this type of command on the VM:
273 run_tests -t nfvbench-demo
275 .. note:: `-t` option determine which test case to be runned by Xtesting
276 (see `xtesting/testcases.yaml` file content to see available list of test cases)
279 Connect to the VM using SSH keypair
280 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
282 If a key is provided at VM creation you can use it to log on the VM using `cloud-user` username:
286 ssh -i key.pem cloud-user@<management_ip>
289 Connect to VM using SSH username/password
290 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
292 VM is accessible over SSH using the hardcoded username and password (see below):
296 ssh nfvbench@<management_ip>
299 Launching nfvbenchvm VM
300 -----------------------
302 Normally this image will be deployed using Ansible role, and the required configurations will be automatically generated and pushed to VM by Ansible.
303 If launched manually, users will have the full control to configure and run NFVbench via VNC console.
305 To check if NFVbench is running, you can run this command in VNC console:
309 sudo screen -r nfvbench
312 Hardcoded Username and Password
313 --------------------------------