Update DPDK in Bionic to latest Stable version (17.11.3)

Bug #1784816 reported by  Christian Ehrhardt  on 2018-08-01
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dpdk (Ubuntu)
Medium
Unassigned
Bionic
Undecided
Unassigned

Bug Description

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.

Related branches

Prepping PPA and Tests to add them above...

Changed in dpdk (Ubuntu):
status: New → Triaged
importance: Undecided → Medium

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

description: updated
description: updated

Tests complete, MP review complete, SRU Teamplate (including details for the DPDK stable release exception) complete - ready for upload and a final check by the SRU Team.

=> is in Bionic-unapproved now [1]

[1]: https://launchpadlibrarian.net/381543019/dpdk_17.11.3-3~ubuntu0.18.04_source.changes

Changed in dpdk (Ubuntu Bionic):
status: New → Triaged
Changed in dpdk (Ubuntu):
status: Triaged → Fix Released

Make sure tasks are ok (complete in cosmic, waiting for SRU Team in Bionic)

Hello , or anyone else affected,

Accepted dpdk into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dpdk/17.11.3-3~ubuntu0.18.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in dpdk (Ubuntu Bionic):
status: Triaged → Fix Committed
tags: added: verification-needed verification-needed-bionic

Please do mind that this is in the new queue as I mentioned upfront - for the two new PMDs.
Build is complete but while waiting for NEW to be accepted it can't be tested yet from proposed.

Passed new queue, started tests yesterday and looking as good as from the PPA (see comment #3).
I want to do some manual tests to be sure on the MLX PMDs as they are new and then will come back here to set verified.

New install of new PMDs work as planned (by Dep from base pkg like the -dev package if needed).
Restart of OVS-DPDK onto the new libs worked fine as well.

Together with the automated testing I think that all looks good.
Setting verified.

1.0.0 (09:15:02): phys (BM) tests
  1.1.0 (09:15:02): initialize environment
    1.1.1 (09:17:08): testpmd => Pass
    1.1.2 (09:17:44): check testpmd output => Pass
2.0.0 (09:18:01): prep virtual test environment
1.0.0 (09:19:29): virt tests
  1.1.0 (09:19:29): initialize environment
3.0.0 (09:20:22): performance tests
  3.1.0 (09:20:22): prep benchmarks
  3.2.0 (09:20:43): performance tests
    3.2.1 (09:20:47): test guest-openvswitch for OVS-5CPU => Pass
    3.2.2 (09:59:46): test guest-dpdk-vhost-user-singleq for OVSDPDK => Pass
    3.2.3 (10:51:17): test guest-dpdk-vhost-user-multiq for OVSDPDK-tuned => Pass
4.0.0 (11:44:28): endurance checks
  4.1.0 (11:44:28): prep endurance tests
    4.1.1 (11:53:04): start stop guests => Pass
    4.1.2 (13:14:56): add/remove ports => Pass
  4.2.0 (13:27:58): Final cleanup

tags: added: verification-done verification-done-bionic
removed: verification-needed verification-needed-bionic
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers