Hello community, here is the log from the commit of package lio-utils for openSUSE:Factory checked in at 2016-05-19 12:15:14 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/lio-utils (Old) and /work/SRC/openSUSE:Factory/.lio-utils.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "lio-utils" Changes: -------- --- /work/SRC/openSUSE:Factory/lio-utils/lio-utils.changes 2014-12-08 16:56:14.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.lio-utils.new/lio-utils.changes 2016-05-19 12:15:17.000000000 +0200 @@ -1,0 +2,10 @@ +Mon May 16 22:15:12 UTC 2016 - [email protected] + +- Added in new source target_status, a helper script + to be installed in /usr/sbin (bsc#972717), adding: + * target_staus +- Updated HOWTO to talk about systemd instead of init + (bsc#972720), adding: + * lio-utils-update-HOWTO-for-systemd.patch + +------------------------------------------------------------------- New: ---- lio-utils-update-HOWTO-for-systemd.patch target_status ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ lio-utils.spec ++++++ --- /var/tmp/diff_new_pack.B3o5ja/_old 2016-05-19 12:15:18.000000000 +0200 +++ /var/tmp/diff_new_pack.B3o5ja/_new 2016-05-19 12:15:18.000000000 +0200 @@ -1,7 +1,7 @@ # # spec file for package lio-utils # -# Copyright (c) 2014 SUSE LINUX Products GmbH, Nuernberg, Germany. +# Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -26,6 +26,7 @@ Url: http://linux-iscsi.org/index.php/Lio-utils Source: lio-utils-4.1.tar.bz2 Source1: target.service +Source2: target_status BuildRequires: net-snmp-devel BuildRequires: python-devel %{?systemd_requires} @@ -85,6 +86,7 @@ Patch33: 0033-lio-utils-dont-dump-RO-attributes.patch Patch34: lio-utils-allow-clearing-discovery-auth.patch Patch35: lio-utils-fix-systemd-service-start.patch +Patch36: lio-utils-update-HOWTO-for-systemd.patch BuildRoot: %{_tmppath}/%{name}-%{version}-build @@ -189,6 +191,7 @@ %patch33 -p1 %patch34 -p1 %patch35 -p1 +%patch36 -p1 %build make %{?_smp_mflags} OPTFLAGS="$RPM_OPT_FLAGS" @@ -232,6 +235,7 @@ install -m 755 scripts/rc.target.suse $RPM_BUILD_ROOT/etc/init.d/target ln -sf ../../etc/init.d/target $RPM_BUILD_ROOT/usr/sbin/rctarget %endif +install -D -m 0755 %{S:2} ${RPM_BUILD_ROOT}/usr/sbin/ %preun %if %{?suse_version} > 1220 @@ -280,6 +284,7 @@ /usr/sbin/rctarget %{python_sitelib}/* %doc lio-utils.HOWTO +/usr/sbin/target_status %files -n lio-mibs %defattr(-,root,root,-) ++++++ lio-utils-update-HOWTO-for-systemd.patch ++++++ diff -aurp lio-utils-4.1.orig/lio-utils.HOWTO lio-utils-4.1/lio-utils.HOWTO --- lio-utils-4.1.orig/lio-utils.HOWTO 2016-05-16 14:32:59.826696797 -0700 +++ lio-utils-4.1/lio-utils.HOWTO 2016-05-16 15:11:04.361522496 -0700 @@ -35,28 +35,10 @@ lio-utils are deprecated and have been s Starting the Target -lio-utils will install an init.d script in /etc/init.d/target. Calling -/etc/init.d/target start mounts Target/configFS and loads the -target_core_mod. Upon successfully starting up the first time, you -should see the following: - -target:~# /etc/init.d/target start -Loading target_core_mod/ConfigFS core: [OK] - -And the following will appear in the kernel ring buffer (dmesg) and -klogd output in /var/log: - -TARGET_CORE[0]: Loading Generic Kernel Storage Engine: v3.0.0 on Linux/i686 on 2.6.30 -TARGET_CORE[0]: Initialized ConfigFS Fabric Infrastructure: v1.0.0 on Linux/i686 on 2.6.30 -SE_PC[0] - Registered Plugin Class: TRANSPORT -PLUGIN_TRANSPORT[1] - pscsi registered -PLUGIN_TRANSPORT[2] - stgt registered -CORE_STGT[0]: Bus Initalization complete -PLUGIN_TRANSPORT[4] - iblock registered -PLUGIN_TRANSPORT[5] - rd_mcp registered -PLUGIN_TRANSPORT[6] - fileio registered -SE_PC[1] - Registered Plugin Class: OBJ -PLUGIN_OBJ[1] - dev registered +lio-utils uses systemd to manage it's the service it provides. Calling +"systemctl start target" mounts target/configfs and loads the +target_core_mod. Running "systemctl status target" should show you +that the service has started correctly. Configuring the Target @@ -204,14 +186,14 @@ Successfully created TCM/ConfigFS storag Displaying the Target status -The status of the live Target can be displayed with /etc/init.d/target -status, which calls tcm_node --listhbas to show the current +The status of the live Target can be displayed with the target_status +script, which calls tcm_node --listhbas to show the current Target/configFS storage objects. Here is the target status after successfully registering the Linux/BLOCK, Linux/pSCSI, Linux/VFS and Target/RAMDISK objects with individual calls to tcm_node --block, --scsi, --scsibyudev, --fileio, and --ramdisk: -target:~# /etc/init.d/target status +target:~# target_status [---------------------------] TCM/ConfigFS Status [----------------------------] \------> rc_mcp_0 HBA Index: 3 plugin: rc_mcp version: v1.0.0 ++++++ target_status ++++++ #!/bin/bash # TCM_CFS_DIR="/sys/kernel/config/target/core" LIO_CFS_DIR="/sys/kernel/config/target/iscsi" ######################################################################### function lio_version () { if [ ! -d ${LIO_CFS_DIR} ]; then exit 1 fi lio_node --version } function lio_status () { if [ ! -d ${LIO_CFS_DIR} ]; then exit 1 fi lio_node --listendpoints } function tcm_version () { if [ ! -d ${TCM_CFS_DIR} ]; then exit 1 fi tcm_node --version } function tcm_status () { if [ ! -d ${TCM_CFS_DIR} ]; then exit 1 fi echo "[---------------------------] TCM/ConfigFS Status [----------------------------]" tcm_node --listhbas echo "" echo "[---------------------------] LIO-Target Status [----------------------------]" lio_status echo "" tcm_version lio_version } tcm_status
