ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

test: removal deprecated sys_sgsw user location

Browse Source 
Replace old '/home/sys_sgsw' location by new created
'/home/sys_sgci/spdk_dependencies'
Also update readme with current user name.

Signed-off-by: Maciej Wawryk <maciejx.wawryk@intel.com>
Change-Id: Ifcea15f704183c7ae0044ee02bd28b6bd891b262
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6927
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Karol Latecki <karol.latecki@intel.com>
This commit is contained in:
Maciej Wawryk 2021-03-17 11:51:55 +01:00 committed by Jim Harris
parent dad0a60778
commit 67dd38285f
5 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
test/common/autotest_common.sh
View File

@ -188,7 +188,7 @@ export LSAN_OPTIONS=suppressions="$asan_suppression_file"
export DEFAULT_RPC_ADDR="/var/tmp/spdk.sock"
if [ -z "$DEPENDENCY_DIR" ]; then
export DEPENDENCY_DIR=/home/sys_sgsw
export DEPENDENCY_DIR=/home/sys_sgci/spdk_dependencies
else
export DEPENDENCY_DIR
fi

4
test/common/config/README.md
View File

@ -17,7 +17,7 @@ to emulate an RDMA enabled NIC. NVMe controllers can also be virtualized in emul
## VM Specs
When creating the user during the fedora installation, it is best to use the name sys_sgsw. Efforts are being made
When creating the user during the fedora installation, it is best to use the name sys_sgci. Efforts are being made
to remove all references to this user, or files specific to this user from the codebase, but there are still some
trailing references to it.
@ -33,7 +33,7 @@ configuration file. For a full list of the variable declarations available for a
1. Download a fresh Fedora 26 image.
2. Perform the installation of Fedora 26 server.
3. Create an admin user sys_sgsw (enabling passwordless sudo for this account will make life easier during the tests).
3. Create an admin user sys_sgci (enabling passwordless sudo for this account will make life easier during the tests).
4. Run the vm_setup.sh script which will install all proper dependencies.
5. Modify the autorun-spdk.conf file in the home directory.
6. Reboot the VM.

2
test/vhost/manual.sh
View File

@ -5,7 +5,7 @@ rootdir=$(readlink -f $testdir/../..)
source $rootdir/test/common/autotest_common.sh
source $rootdir/test/vhost/common.sh
DEFAULT_FIO_BIN="/home/sys_sgsw/fio_ubuntu"
DEFAULT_FIO_BIN="$DEPENDENCY_DIR/fio"
case $1 in
-h | --help)

2
test/vhost/vhost.sh
View File

@ -12,7 +12,7 @@ if [[ $(uname -s) != Linux ]]; then
exit 0
fi
DEFAULT_FIO_BIN="/home/sys_sgsw/fio_ubuntu"
DEFAULT_FIO_BIN="$DEPENDENCY_DIR/fio"
: ${FIO_BIN="$DEFAULT_FIO_BIN"}
vhosttestinit

2
test/vhost/windows/windows_scsi_compliance.sh
View File

@ -9,7 +9,7 @@ source $rootdir/test/vhost/common.sh
# and OS Version: 6.3.9600 N/A Build 9600
# In order to run this test with windows vm
# windows virtio scsi driver must be installed
WINDOWS_IMG="/home/sys_sgsw/windows_scsi_compliance/windows_vm_image.qcow2"
WINDOWS_IMG="$DEPENDENCY_DIR/windows_scsi_compliance/windows_vm_image.qcow2"
aio_file="$SPDK_TEST_STORAGE/aio_disk"
ssh_pass=""
vm_num=1