| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
By default, configure the MTU of the management interface to the
conservative value of 1500: this will reduce the risk to get an
unmanageable VM. Else the MTU we will get will depend on the IaaS setup
and it could be high. And this will lead to troubles when we try to
manage the VM from a machine configured with a high MTU and when the
network path contains a link with a low MTU. This can typically happen
when we try to manage the VM from another VM in the same IaaS and when
the management traffic has to go outside the IaaS.
To set the MTU to a different value, configure the INTF_MGMT_MTU
variable in /etc/nfvbenchvm.conf. If INTF_MGMT_MTU is set to the
special value "auto", the MTU will not be configured and it will keep
the value set by the hypervisor ("legacy" nfvbenchvm behavior). If
INTF_MGMT_MTU is unset, the MTU will be set to 1500. In other cases,
the MTU will be set to the value of INTF_MGMT_MTU.
Change-Id: I5816113bbacec5fcdcc9672e20d8a4e2ac0c599a
Signed-off-by: Gwenael Lambrouin <gwenael.lambrouin@orange.com>
|
|
build-image.sh has a new option -s to build the generator VM image from
the local nfvbench code (Git working copy) instead of the master branch
of nfvbench repository on OPNFV Gerrit. This is useful for testing
during the development phases.
When this option is used, the version of the generator VM image is
extended with nfvbench development version number to be able to
distinguish the development images from the latest published image.
Change-Id: If21cbf2be59ff4f4110ebc157af0f934b98bddcb
Signed-off-by: Gwenael Lambrouin <gwenael.lambrouin@orange.com>
|
|
Attempting to build nfvbench VM images with diskimage_builder (dib)
3.16.0 leads to the following error:
diskimage_builder.element_dependencies.MissingElementException: Element
'block-device' not found
Something changed at some point of diskimage_builder history, and the
updated doc states: "When using the vm element, an element that provides
block-device should be included".
To fix this and prevent future similar issues, this patch:
- adds the "block-device-mbr" element to the dependency list
- sets diskimage_builder version
By the way:
- replace the deprecated "centos7" element with the more generic
"centos" element.
- add missing dependencies in the pre-requisites section of nfvbenchvm
doc
- install pip with package manager (the current latest version of
get-pip.py is not compatible with python 3.6, so let's use the
occasion to stop getting pip directly from the Internet)
- use Python 3 in build-image.sh
Change-Id: I3198a1042eca04224b2a62db443c39a76903cf22
Signed-off-by: Gwenael Lambrouin <gwenael.lambrouin@orange.com>
|
|
Change-Id: Ia741847f886a291f0b0d7276e36d5c18f7819185
Signed-off-by: fmenguy <francoisregis.menguy@orange.com>
|
|
Change-Id: I789caa7f46bd2b21af15ec5ffe4d857e10a7734c
Signed-off-by: fmenguy <francoisregis.menguy@orange.com>
|
|
inside VM)
Change-Id: Id919a1b9dbf5e04b198d022432ed5c64232a27ba
Signed-off-by: fmenguy <francoisregis.menguy@orange.com>
|
|
1. Add support to use vswitch to handle V2V in PVVP SRIOV scenario
2. Update nfvbenchvm to 0.5:
(1) Update VPP to 17.10;
(2) Update DPDK testpmd to 17.08;
(3) Change kernel to based on longterm lineup;
Change-Id: I944489579a4cd92d17075e80870bbdb32512a150
Signed-off-by: Yichen Wang <yicwang@cisco.com>
|
|
Change-Id: Ie2993886dc8e95c5f73ccdb871add8b96ffcc849
Signed-off-by: ahothan <ahothan@cisco.com>
|
Gwenael Lambrouin
fmenguy
Yichen Wang
ahothan