Automated tests completed - all good.
The summary is (details in the attached log):
$ cat 17.11.3-stable-run1.log
VIRT_SPAWNGUESTS
VIRT_TESTPMD
VIRT_L2FWD
BENCH_OVS
BENCH_OVSDPDK
BENCH_OVSDPDK_TUNED
ENDURANCE_STARTSTOP
ENDURANCE_ADDREMOVEPORT
1.0.0 (06:11:55): phys (BM) tests
1.1.0 (06:11:55): initialize environment
2.0.0 (06:13:17): prep virtual test environment
1.0.0 (06:14:51): virt tests
1.1.0 (06:14:51): initialize environment
3.0.0 (06:16:00): performance tests
3.1.0 (06:16:00): prep benchmarks
3.2.0 (06:16:20): performance tests
3.2.1 (06:16:24): test guest-openvswitch for OVS-5CPU => Pass
3.2.2 (07:10:32): test guest-dpdk-vhost-user-singleq for OVSDPDK => Pass
3.2.3 (08:02:02): test guest-dpdk-vhost-user-multiq for OVSDPDK-tuned =>
Pass
4.0.0 (08:54:44): endurance checks
4.1.0 (08:54:44): prep endurance tests
4.1.1 (09:03:56): start stop guests => Pass
4.1.2 (10:23:00): add/remove ports => Pass
4.2.0 (10:36:06): summarize benchmark results
4.3.0 (10:36:28): Final cleanup
** Attachment added: "Detailed test log"
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1784816/+attachment/5170796/+files/17.11.3-stable-run1.detail
** Description changed:
17.11.3-3 was made available in Cosmic now we should SRU the stable
fixes to our latest LTS as well.
This bug tracks an update for the DPDK packages, version 17.11.3.
This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/StableReleaseUpdates/DPDK.
There is one exception to that in this upload which is after working
with Mellanox on verification we will enable MLX based PMDs following
https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases for HW
exploitation (these extra PMDs do not change existing PMDs/Libs - think
of it as a few extra device drivers. TO be sure This was already pre-
discussed with Steve Langasek to have an ack in advance on doing such.
[Impact]
Stable release update so not directly applicable; see the exception
policy document.
[Major Changes]
Major Changes:
- from upstream: none but bugfixes
- from us: now enabling MLX4/5 PMds
=> The full release notes can be found at:
https://doc.dpdk.org/guides-17.11/rel_notes/release_17_11.html#id3
[Test Plan]
See https://wiki.ubuntu.com/StableReleaseUpdates/DPDK#SRU_TestVerify
- Autopkgtests worked: https://bileto.ubuntu.com/excuses/3334/bionic.html
- PPA:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3334/+packages
- Packaging MP:
https://code.launchpad.net/~paelzer/ubuntu/+source/dpdk/+git/dpdk/+merge/352006
- - TODO: attach a log of executing said tests from a ppa with the upload
- - TODO: if there are any non passing tests - explain why that is ok in this
case.
+ - Tests were ran and results added in
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1784816/comments/3
+ - all tests pass - nothing to excuse/explain
[Regression Potential]
Upstream performs extensive testing before release, giving us a high
degree of confidence in the general case. There problems are most likely
to manifest in Ubuntu-specific integrations, such as in relation to the
versions of dependencies available and other packaging-specific matters.
An extra risk might be due to the new drivers, but as I mentioned they
do not affect the existing ones. There could be a minor impact due to
dependencies - the new binary packages for MLX depend on ibverbs and
such from rdma-core. The development libs libdpdk-dev&dpdk-dev depends
on all libs+pmds as usual for such a lib. There could be a case where
one wanted to use external MLNX-OFED - part of the procedure to install
that is to remove and mask the "from Archive" libibverbs and such. Due
to that with the upgrade libdpdk-dev/dpdk-dev would no more be
installable (unless nodeps is used). But since this only hit non-
Archive-cases it is already unsupported anyway - never the less I wanted
to mention it for completeness.
** Description changed:
17.11.3-3 was made available in Cosmic now we should SRU the stable
fixes to our latest LTS as well.
This bug tracks an update for the DPDK packages, version 17.11.3.
This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/StableReleaseUpdates/DPDK.
There is one exception to that in this upload which is after working
with Mellanox on verification we will enable MLX based PMDs following
https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases for HW
exploitation (these extra PMDs do not change existing PMDs/Libs - think
of it as a few extra device drivers. TO be sure This was already pre-
discussed with Steve Langasek to have an ack in advance on doing such.
[Impact]
Stable release update so not directly applicable; see the exception
policy document.
[Major Changes]
Major Changes:
- from upstream: none but bugfixes
- from us: now enabling MLX4/5 PMds
=> The full release notes can be found at:
https://doc.dpdk.org/guides-17.11/rel_notes/release_17_11.html#id3
[Test Plan]
See https://wiki.ubuntu.com/StableReleaseUpdates/DPDK#SRU_TestVerify
- Autopkgtests worked: https://bileto.ubuntu.com/excuses/3334/bionic.html
- PPA:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3334/+packages
- Packaging MP:
https://code.launchpad.net/~paelzer/ubuntu/+source/dpdk/+git/dpdk/+merge/352006
- Tests were ran and results added in
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1784816/comments/3
- all tests pass - nothing to excuse/explain
[Regression Potential]
Upstream performs extensive testing before release, giving us a high
degree of confidence in the general case. There problems are most likely
to manifest in Ubuntu-specific integrations, such as in relation to the
versions of dependencies available and other packaging-specific matters.
An extra risk might be due to the new drivers, but as I mentioned they
do not affect the existing ones. There could be a minor impact due to
dependencies - the new binary packages for MLX depend on ibverbs and
such from rdma-core. The development libs libdpdk-dev&dpdk-dev depends
on all libs+pmds as usual for such a lib. There could be a case where
one wanted to use external MLNX-OFED - part of the procedure to install
that is to remove and mask the "from Archive" libibverbs and such. Due
to that with the upgrade libdpdk-dev/dpdk-dev would no more be
installable (unless nodeps is used). But since this only hit non-
Archive-cases it is already unsupported anyway - never the less I wanted
to mention it for completeness.
+
+ [Other]
+
+ FYI: The new MLX[45] PMD means new binary packages - so it will also hit
+ new queue on the SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784816
Title:
Update DPDK in Bionic to latest Stable version (17.11.3)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1784816/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs