Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I122607f24844eda15920b514a29e4efba9a7c4e6
Signed-off-by: Gwenael Lambrouin <gwenael.lambrouin@orange.com>
|
|
It is now possible to configure nfvbench server IP address and port number
with environment variables: NFVBENCH_SERVER_HOST and NFVBENCH_SERVER_PORT.
It is still possible to configure them in feature files, and the values found
in feature files take precedence.
This allows to have behave tests and nfvbench server running on different
machines without changing feature files, which is especially useful for
testing.
Signed-off-by: Gwenael Lambrouin <gwenael.lambrouin@orange.com>
Change-Id: I98dc7f87a1a233b90b44dfc8b26a1e63961fff3c
|
|
Change-Id: I2b4ea4ee6e6442d4ceac268e7bf3c6bf9277ff54
Signed-off-by: Gwenael Lambrouin <gwenael.lambrouin@orange.com>
|
|
Change-Id: I5c976dd49a2c17b47559b1d6a565a6e78f7cfd0e
Signed-off-by: fmenguy <francoisregis.menguy@orange.com>
|
|
Change-Id: I2f050f8a6f193c4e04ac8a427aedb7c241633b73
Signed-off-by: fmenguy <francoisregis.menguy@orange.com>
|
|
|
|
In some cases, the 50 seconds timeout to wait for nfvbench HTTP server to be
ready is too short. (Convoluted but real example: when the DNS servers are not
properly configured and nfvbench tries to reach the OpenStack APIs while it
does not need them because we just want to do a loopback test without loop VM)
The new timeout is 120 seconds.
Change-Id: I4932eff7c9a100370e7ceaaa2a467efbbceb5993
Signed-off-by: Gwenael Lambrouin <gwenael.lambrouin@orange.com>
|
|
Add a quick test at low packet rate for troubleshooting purpose:
- duration: 10s
- fixed packet rate: 10kpps
- frame size: 64
- flow count: 128
Change-Id: Ib736dbe7ade6d0b6e4d484a6d8bfca34bb5c4c5a
Signed-off-by: Gwenael Lambrouin <gwenael.lambrouin@orange.com>
|
|
Change-Id: I19895eae9a3e68999cdde15f3f21520dcf6e6897
Signed-off-by: fmenguy <francoisregis.menguy@orange.com>
|
|
Change-Id: I708eee21a9fd11e7a276707fb0b43d8598381ce7
Signed-off-by: fmenguy <francoisregis.menguy@orange.com>
|