Re: [SPDK] Jenkins Test System Updates

Re: [SPDK] Jenkins Test System Updates

[Luse, Paul E]

[-- Attachment #1: Type: text/plain, Size: 2475 bytes --]

Karol,

Please take a look at this when you get a chance.  These are updates needed to test systems in Jenkins to support Crypto.  Just ran latest patch through and all of the info below is still relevant (except for NVMe autotest which now passes, it was failing for unrelated reasons)

Thx
Paul

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
Sent: Friday, September 7, 2018 6:38 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] Jenkins Test System Updates

Hi Karol,

In CH test pool, we have 3 systems setup to run crypto testing in CI based on the flag SPDK_TEST_CRYPTO and on those systems a few things are needed:


*        Nasm of 2.12.2 or higher

*        Ipsec module installed as root

*        Some misc DPDK things enabled

The third is part of the patch so nothing needs to be done there however the first two need to be done via running pkgdep on the test machines.  If the packaged nasm isn't of high enough version the build log will let you know.  If ipsec isn't installed it will also let you know (see below from latest crypto patch w/Jenkins running BlobFS_autotest

To enable crypto you must first go to the intel-ipsec-mb directory and
run 'make' then 'sudo make install' then re-run this script.
  15:09:05     $ trap - ERR
  15:09:05     $ print_backtrace
  15:09:05     $ [[ ehxBE =~ e ]]
  15:09:05     $ local shell_options=ehxBE
  15:09:05     $ set +x
========== Backtrace start: ==========

Here is a list of the failed tests and what needs to be done to get them working with the Jenkins test pool, we don't need crypto running everywhere so if you can enable it just on a few machines (block dev tests) that would be great:

BlobFS_autotest: missing install of ipsec, run pkgdep.sh

CentOS test: missing nasm or old, maybe just don't run on this OS

FreeBSD: same as above

NVME autotest: LLooks to be configured correctly but crypto patch failed for what looks like unrelated reasons: https://ci.spdk.io/spdk-jenkins/results/autotest-per-patch/builds/10910/archive/nvme_autotest/build.log

Ubuntu16:  old nasm, maybe don't enable crypto testing on this one

Ubuntu17: needs ipsec insetall (pkgdep.sh) and this is probably a good candidate for crypto testing







_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk

Re: [SPDK] Jenkins Test System Updates

[Luse, Paul E]

[-- Attachment #1: Type: text/plain, Size: 4773 bytes --]

Looks perfect!  Thanks Karol!!

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Latecki, Karol
Sent: Tuesday, September 11, 2018 2:54 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Jenkins Test System Updates

Hi Paul!

Sorry, missed your e-mails, my bad.
I installed deps on our servers here so it should be OK now. I retriggered your latest patch set from: https://review.gerrithub.io/#/c/spdk/spdk/+/403107/
Looks good for me, but could you check output and logs and see if everything is as expected? 

Thanks,
Karol


-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
Sent: Monday, September 10, 2018 8:30 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Jenkins Test System Updates

And no pressure Karol but Seth made these changes in CH same day and the crypto patch is passing here now :)

-----Original Message-----
From: Luse, Paul E
Sent: Monday, September 10, 2018 11:06 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: RE: Jenkins Test System Updates

Karol,

Please take a look at this when you get a chance.  These are updates needed to test systems in Jenkins to support Crypto.  Just ran latest patch through and all of the info below is still relevant (except for NVMe autotest which now passes, it was failing for unrelated reasons)

Thx
Paul

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
Sent: Friday, September 7, 2018 6:38 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] Jenkins Test System Updates

Hi Karol,

In CH test pool, we have 3 systems setup to run crypto testing in CI based on the flag SPDK_TEST_CRYPTO and on those systems a few things are needed:


*        Nasm of 2.12.2 or higher

*        Ipsec module installed as root

*        Some misc DPDK things enabled

The third is part of the patch so nothing needs to be done there however the first two need to be done via running pkgdep on the test machines.  If the packaged nasm isn't of high enough version the build log will let you know.  If ipsec isn't installed it will also let you know (see below from latest crypto patch w/Jenkins running BlobFS_autotest

To enable crypto you must first go to the intel-ipsec-mb directory and run 'make' then 'sudo make install' then re-run this script.
  15:09:05     $ trap - ERR
  15:09:05     $ print_backtrace
  15:09:05     $ [[ ehxBE =~ e ]]
  15:09:05     $ local shell_options=ehxBE
  15:09:05     $ set +x
========== Backtrace start: ==========

Here is a list of the failed tests and what needs to be done to get them working with the Jenkins test pool, we don't need crypto running everywhere so if you can enable it just on a few machines (block dev tests) that would be great:

BlobFS_autotest: missing install of ipsec, run pkgdep.sh

CentOS test: missing nasm or old, maybe just don't run on this OS

FreeBSD: same as above

NVME autotest: LLooks to be configured correctly but crypto patch failed for what looks like unrelated reasons: https://ci.spdk.io/spdk-jenkins/results/autotest-per-patch/builds/10910/archive/nvme_autotest/build.log

Ubuntu16:  old nasm, maybe don't enable crypto testing on this one

Ubuntu17: needs ipsec insetall (pkgdep.sh) and this is probably a good candidate for crypto testing







_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
--------------------------------------------------------------------

Intel Technology Poland sp. z o.o.
ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.

Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek przegladanie lub rozpowszechnianie jest zabronione.
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by others is strictly prohibited.

_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk

Re: [SPDK] Jenkins Test System Updates

[Latecki, Karol]

[-- Attachment #1: Type: text/plain, Size: 4347 bytes --]

Hi Paul!

Sorry, missed your e-mails, my bad.
I installed deps on our servers here so it should be OK now. I retriggered your latest patch set from: https://review.gerrithub.io/#/c/spdk/spdk/+/403107/
Looks good for me, but could you check output and logs and see if everything is as expected? 

Thanks,
Karol


-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
Sent: Monday, September 10, 2018 8:30 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Jenkins Test System Updates

And no pressure Karol but Seth made these changes in CH same day and the crypto patch is passing here now :)

-----Original Message-----
From: Luse, Paul E 
Sent: Monday, September 10, 2018 11:06 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: RE: Jenkins Test System Updates

Karol,

Please take a look at this when you get a chance.  These are updates needed to test systems in Jenkins to support Crypto.  Just ran latest patch through and all of the info below is still relevant (except for NVMe autotest which now passes, it was failing for unrelated reasons)

Thx
Paul

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
Sent: Friday, September 7, 2018 6:38 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] Jenkins Test System Updates

Hi Karol,

In CH test pool, we have 3 systems setup to run crypto testing in CI based on the flag SPDK_TEST_CRYPTO and on those systems a few things are needed:


*        Nasm of 2.12.2 or higher

*        Ipsec module installed as root

*        Some misc DPDK things enabled

The third is part of the patch so nothing needs to be done there however the first two need to be done via running pkgdep on the test machines.  If the packaged nasm isn't of high enough version the build log will let you know.  If ipsec isn't installed it will also let you know (see below from latest crypto patch w/Jenkins running BlobFS_autotest

To enable crypto you must first go to the intel-ipsec-mb directory and run 'make' then 'sudo make install' then re-run this script.
  15:09:05     $ trap - ERR
  15:09:05     $ print_backtrace
  15:09:05     $ [[ ehxBE =~ e ]]
  15:09:05     $ local shell_options=ehxBE
  15:09:05     $ set +x
========== Backtrace start: ==========

Here is a list of the failed tests and what needs to be done to get them working with the Jenkins test pool, we don't need crypto running everywhere so if you can enable it just on a few machines (block dev tests) that would be great:

BlobFS_autotest: missing install of ipsec, run pkgdep.sh

CentOS test: missing nasm or old, maybe just don't run on this OS

FreeBSD: same as above

NVME autotest: LLooks to be configured correctly but crypto patch failed for what looks like unrelated reasons: https://ci.spdk.io/spdk-jenkins/results/autotest-per-patch/builds/10910/archive/nvme_autotest/build.log

Ubuntu16:  old nasm, maybe don't enable crypto testing on this one

Ubuntu17: needs ipsec insetall (pkgdep.sh) and this is probably a good candidate for crypto testing







_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
--------------------------------------------------------------------

Intel Technology Poland sp. z o.o.
ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.

Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek
przegladanie lub rozpowszechnianie jest zabronione.
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by
others is strictly prohibited.

Re: [SPDK] Jenkins Test System Updates

[Luse, Paul E]

[-- Attachment #1: Type: text/plain, Size: 2785 bytes --]

And no pressure Karol but Seth made these changes in CH same day and the crypto patch is passing here now :)

-----Original Message-----
From: Luse, Paul E 
Sent: Monday, September 10, 2018 11:06 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: RE: Jenkins Test System Updates

Karol,

Please take a look at this when you get a chance.  These are updates needed to test systems in Jenkins to support Crypto.  Just ran latest patch through and all of the info below is still relevant (except for NVMe autotest which now passes, it was failing for unrelated reasons)

Thx
Paul

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul E
Sent: Friday, September 7, 2018 6:38 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] Jenkins Test System Updates

Hi Karol,

In CH test pool, we have 3 systems setup to run crypto testing in CI based on the flag SPDK_TEST_CRYPTO and on those systems a few things are needed:


*        Nasm of 2.12.2 or higher

*        Ipsec module installed as root

*        Some misc DPDK things enabled

The third is part of the patch so nothing needs to be done there however the first two need to be done via running pkgdep on the test machines.  If the packaged nasm isn't of high enough version the build log will let you know.  If ipsec isn't installed it will also let you know (see below from latest crypto patch w/Jenkins running BlobFS_autotest

To enable crypto you must first go to the intel-ipsec-mb directory and run 'make' then 'sudo make install' then re-run this script.
  15:09:05     $ trap - ERR
  15:09:05     $ print_backtrace
  15:09:05     $ [[ ehxBE =~ e ]]
  15:09:05     $ local shell_options=ehxBE
  15:09:05     $ set +x
========== Backtrace start: ==========

Here is a list of the failed tests and what needs to be done to get them working with the Jenkins test pool, we don't need crypto running everywhere so if you can enable it just on a few machines (block dev tests) that would be great:

BlobFS_autotest: missing install of ipsec, run pkgdep.sh

CentOS test: missing nasm or old, maybe just don't run on this OS

FreeBSD: same as above

NVME autotest: LLooks to be configured correctly but crypto patch failed for what looks like unrelated reasons: https://ci.spdk.io/spdk-jenkins/results/autotest-per-patch/builds/10910/archive/nvme_autotest/build.log

Ubuntu16:  old nasm, maybe don't enable crypto testing on this one

Ubuntu17: needs ipsec insetall (pkgdep.sh) and this is probably a good candidate for crypto testing







_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk

[SPDK] Jenkins Test System Updates

[Luse, Paul E]

[-- Attachment #1: Type: text/plain, Size: 1783 bytes --]

Hi Karol,

In CH test pool, we have 3 systems setup to run crypto testing in CI based on the flag SPDK_TEST_CRYPTO and on those systems a few things are needed:


*        Nasm of 2.12.2 or higher

*        Ipsec module installed as root

*        Some misc DPDK things enabled

The third is part of the patch so nothing needs to be done there however the first two need to be done via running pkgdep on the test machines.  If the packaged nasm isn't of high enough version the build log will let you know.  If ipsec isn't installed it will also let you know (see below from latest crypto patch w/Jenkins running BlobFS_autotest

To enable crypto you must first go to the intel-ipsec-mb directory and
run 'make' then 'sudo make install' then re-run this script.
  15:09:05     $ trap - ERR
  15:09:05     $ print_backtrace
  15:09:05     $ [[ ehxBE =~ e ]]
  15:09:05     $ local shell_options=ehxBE
  15:09:05     $ set +x
========== Backtrace start: ==========

Here is a list of the failed tests and what needs to be done to get them working with the Jenkins test pool, we don't need crypto running everywhere so if you can enable it just on a few machines (block dev tests) that would be great:

BlobFS_autotest: missing install of ipsec, run pkgdep.sh

CentOS test: missing nasm or old, maybe just don't run on this OS

FreeBSD: same as above

NVME autotest: LLooks to be configured correctly but crypto patch failed for what looks like unrelated reasons: https://ci.spdk.io/spdk-jenkins/results/autotest-per-patch/builds/10910/archive/nvme_autotest/build.log

Ubuntu16:  old nasm, maybe don't enable crypto testing on this one

Ubuntu17: needs ipsec insetall (pkgdep.sh) and this is probably a good candidate for crypto testing