test/common: Provide {ext,null}glob by default in autotest suite

This requires adjustments in several test suites due to some bad
practices exposed by explicit use of nullglob.

Change-Id: Idbe7eeec

test/common: Provide {ext,null}glob by default in autotest suite

This requires adjustments in several test suites due to some bad
practices exposed by explicit use of nullglob.

Change-Id: Idbe7eeec598ffc06e98986898344e4e0d88f4a5d
Signed-off-by: Michal Berger <michal.berger@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/19551
Reviewed-by: Jim Harris <jim.harris@gmail.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>

show more ...

test/vhost: Perform verify only for the write job

Since fio-3.33, due to the following commit (bisect + revert):

https://github.com/axboe/fio/commit/191d6634e8a692bef15143715c88920987ecaa89

usin

test/vhost: Perform verify only for the write job

Since fio-3.33, due to the following commit (bisect + revert):

https://github.com/axboe/fio/commit/191d6634e8a692bef15143715c88920987ecaa89

using verification for *read jobs is foobar. For currently existing
configuration, fio >= 3.33 exits almost immediately causing the
migration test to fail - before VM is migrated, we check if fio is
actually running, however, due to this issue, it's not.

To mitigate, verify only the write job, allowing the randread job
to block for expected amount of time (20s).

Change-Id: I7c36e8f56635292426a15aeeb2395cecd454058a
Signed-off-by: Michal Berger <michal.berger@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/19543
Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Jim Harris <jim.harris@gmail.com>

show more ...

test/vhost: Remove {RDMA,MGMT}* opts from migration.sh

These are not used in any capacity.

Change-Id: Idd729025d0c14084c3505b1fed58c6c90f3acfa9
Signed-off-by: Michal Berger <michal.berger@intel.com

test/vhost: Remove {RDMA,MGMT}* opts from migration.sh

These are not used in any capacity.

Change-Id: Idd729025d0c14084c3505b1fed58c6c90f3acfa9
Signed-off-by: Michal Berger <michal.berger@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/19542
Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
Reviewed-by: Karol Latecki <karol.latecki@intel.com>
Reviewed-by: Kamil Godzwon <kamilx.godzwon@intel.com>
Reviewed-by: Jim Harris <jim.harris@gmail.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>

show more ...

test/vhost: Don't use RDMA for migration-TC2

This idea behind this test case is not to focus on a particular
transport protocol but rather use of nvmf during migration in
general. Since RDMA require

test/vhost: Don't use RDMA for migration-TC2

This idea behind this test case is not to focus on a particular
transport protocol but rather use of nvmf during migration in
general. Since RDMA requires specific hardware, it imposes
unnecessary limit on the CI pool as to where this test suite can
be executed. Avoid that and use TCP for which fallback to veth
setup is supported in case actual hw is not present.

Change-Id: I6ec3f701285e26e42f5d5cbdbc078a5d57778797
Signed-off-by: Michal Berger <michal.berger@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/19541
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
Reviewed-by: Jim Harris <jim.harris@gmail.com>

show more ...

misc: Fixes targeted for latest shellcheck

Following directives are being fixed:

- SC2317
- SC2004

Signed-off-by: Michal Berger <michal.berger@intel.com>
Change-Id: Ia080044aa5b7c885a01556b6927933

misc: Fixes targeted for latest shellcheck

Following directives are being fixed:

- SC2317
- SC2004

Signed-off-by: Michal Berger <michal.berger@intel.com>
Change-Id: Ia080044aa5b7c885a01556b6927933b81f98eb9d
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16025
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Pawel Piatek <pawelx.piatek@intel.com>
Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>

show more ...

test/vhost: use light IO workloads for live migration tests

Use lightweight workload test cases in VM for the purpose
to keep number of dirty pages is in low rate of VM's total
memory.

Fix issue #2

test/vhost: use light IO workloads for live migration tests

Use lightweight workload test cases in VM for the purpose
to keep number of dirty pages is in low rate of VM's total
memory.

Fix issue #2805.

Change-Id: I52efd0d0522ccef713ba2c3a451daac0683234dc
Signed-off-by: Changpeng Liu <changpeng.liu@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15954
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>

show more ...

add (c) and SPDX header to bash files as needed

per Intel policy to include file commit date using git cmd
below. The policy does not apply to non-Intel (C) notices.

git log --follow -C90% --forma

add (c) and SPDX header to bash files as needed

per Intel policy to include file commit date using git cmd
below. The policy does not apply to non-Intel (C) notices.

git log --follow -C90% --format=%ad --date default <file> | tail -1

and then pull just the year from the result.

Intel copyrights were not added to files where Intel either had
no contribution ot the contribution lacked substance (ie license
header updates, formatting changes, etc)

For intel copyrights added, --follow and -C95% were used.

Signed-off-by: paul luse <paul.e.luse@intel.com>
Change-Id: I2ef86976095b88a9bf5b1003e59f3943cd6bbe4c
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15209
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Community-CI: Mellanox Build Bot
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>

show more ...

test/fio: supress fio output files

verify.state files are not very useful because
we fail the tests at any first failure.
If there was something wrong with IO verification
then autotest.sh would fai

test/fio: supress fio output files

verify.state files are not very useful because
we fail the tests at any first failure.
If there was something wrong with IO verification
then autotest.sh would fail.

Fio files with metrics output (IOPS, BW, latency, etc)
are also not very useful as per-patch tests are not
focused on benchmarking.

Fixes #2546

Signed-off-by: Kamil Godzwon <kamilx.godzwon@intel.com>
Change-Id: I33fbe2fb0749d840f08ffe0d606d206268140991
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/13019
Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com>
Reviewed-by: Karol Latecki <karol.latecki@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>

show more ...