From markcarl@sac.sfbay.sun.com Thu Jan 8 07:13:28 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n08FDR4g013309 for ; Thu, 8 Jan 2009 07:13:27 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n08FDFgd006224; Thu, 8 Jan 2009 07:13:27 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KD500N19RMF0G00@brm-avmta-1.central.sun.com>; Thu, 08 Jan 2009 08:13:27 -0700 (MST) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KD500HNGRME4040@brm-avmta-1.central.sun.com>; Thu, 08 Jan 2009 08:13:27 -0700 (MST) Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n08FDPBN031091; Thu, 08 Jan 2009 07:13:25 -0800 (PST) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n08FDORQ013304; Thu, 08 Jan 2009 07:13:24 -0800 (PST) Received: (from markcarl@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n08FDN2Y013300; Thu, 08 Jan 2009 07:13:23 -0800 (PST) Date: Thu, 08 Jan 2009 07:13:23 -0800 (PST) From: Mark Carlson Subject: iSCSI Initiator SMF Service [PSARC/2009/011 FastTrack timeout 01/15/2009] To: PSARC-ext@sun.com Cc: Jack.Meng@sun.com Message-id: <200901081513.n08FDN2Y013300@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 3375 I am sponsoring this case for Jack Meng. It requests minor binding and times out on 01/15/2009. -- mark Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: iSCSI Initiator SMF Service 1.2. Name of Document Author/Supplier: Author: Jack Meng 1.3 Date of This Document: 08 January, 2009 2. Project Summary 2.1. Project Description This project makes the existing iSCSI initiator feature in Solaris a standard SMF service. 4. Technical Description 4.1. Details: Currently iSCSI initiator feature does not exist as an SMF service in Solaris. The existing service svc:/network/iscsi_initiator:default only represents the name resolutions service for the iSCSI kernel module. This is always confusing since the enable/disable of that service doesn't affect the behavior of iSCSI initiator. iSCSI module starts the kernel daemon in its attach routine, which is a behavior blind of the status of the OS and causing defects/limitation that can not be fixed win thin present architecture, few examples are listed below: 1. 'Unable to login to xxxxxxxxxxx' during system startup 2. Inconsistent connections may happen after system rebooted as the login failed during startup 3. Unable to add customized dependency for special usage, e.g., iSCSI disk is used as shared device in cluster, so iSCSI initiator should try to login after iSCSI target online. This project provides a new service, named svc:/network/iscsi/initiator:default to replace the existing service. the new service will provide following benefits, 1. Users are able to explicitly enable/disable iSCSI initiator feature in Solaris. 2. Avoid the blindly starting up by specifying dependencies. 3. iSCSI initiator will be more flexible to serve special requirements. The existing functionality in svc:/network/iscsi_initiator:default will be inherited. 4.5 Interfaces: Exported Interface | Stability | Description --------------------------------------|--------------|------------------- svc:/network/iscsi/initiator:default | Committed | iSCSI initiator service, | | renamed from iscsi_initiator:default | | with new functions Imported Interface | Stability | Description --------------------------------------|--------------|------------------- usr/share/man/man7d/iscsi.7d | Committed | manpage of iSCSI initiator usr/share/man/man1m/iscsiadm.1m | Committed | manpage of iSCSI initiator CLI usr/sbin/iscsiadm | Committed | iSCSI initiator CLI Removed Interface | Stability | Description --------------------------------------|--------------|------------------- svc:/network/iscsi_initiator:default | Committed | service for iSCSI name resolution Other documents: System Administration Guide: Devices and File Systems, Chapter 14 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ONNV 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From Darren.Moffat@sun.com Sun Jan 11 18:26:45 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n0C2Qj9o000102 for ; Sun, 11 Jan 2009 18:26:45 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n0C2QYGR021091 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Mon, 12 Jan 2009 02:26:43 GMT Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KDC001076SIVX00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sun, 11 Jan 2009 19:26:42 -0700 (MST) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KDC0001I6SH4C10@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sun, 11 Jan 2009 19:26:42 -0700 (MST) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n0C2Qe5Y012747 for ; Mon, 12 Jan 2009 02:26:40 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KDC00I016PMSF00@fe-emea-09.sun.com> (original mail from Darren.Moffat@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon, 12 Jan 2009 02:26:40 +0000 (GMT) Received: from [129.156.173.21] by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KDC004286SETQ10@fe-emea-09.sun.com>; Mon, 12 Jan 2009 02:26:39 +0000 (GMT) Date: Mon, 12 Jan 2009 02:26:38 +0000 From: Darren J Moffat Subject: Re: iSCSI Initiator SMF Service [PSARC/2009/011 FastTrack timeout 01/15/2009] In-reply-to: <200901081513.n08FDN2Y013300@sac.sfbay.sun.com> Sender: Darren.Moffat@sun.com To: Mark Carlson Cc: PSARC-ext@sun.com, Jack.Meng@sun.com Message-id: <496AAA5E.40002@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200901081513.n08FDN2Y013300@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Status: RO Content-Length: 102 I assume the correct thing happesn on upgrade to remove the old FMRI. If so +1. -- Darren J Moffat From Mark.Carlson@sun.com Wed Jan 14 14:32:54 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n0EMWqpm002427 for ; Wed, 14 Jan 2009 14:32:53 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n0EMWbSD006549 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 15 Jan 2009 06:32:52 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KDH00201FYQ2S00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Wed, 14 Jan 2009 14:32:50 -0800 (PST) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KDH009SBFYPVND0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Wed, 14 Jan 2009 14:32:49 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n0EMWnVW023325 for ; Wed, 14 Jan 2009 22:32:49 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KDH00C01DMKRC00@mail-amer.sun.com> (original mail from Mark.Carlson@Sun.COM) for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Wed, 14 Jan 2009 15:32:49 -0700 (MST) Received: from Macintosh-335.local ([129.150.32.109]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KDH0097VFYCNQ30@mail-amer.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Wed, 14 Jan 2009 15:32:38 -0700 (MST) Date: Wed, 14 Jan 2009 15:32:36 -0700 From: "Mark A. Carlson" Subject: Re: iSCSI Initiator SMF Service [PSARC/2009/011 FastTrack timeout 01/15/2009] In-reply-to: <496AAA5E.40002@Sun.COM> Sender: Mark.Carlson@sun.com To: Darren J Moffat Cc: PSARC-ext@sun.com, Jack.Meng@sun.com Message-id: <496E6804.1080000@sun.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_4YecN1VKcTJU3rd+yIVikA)" X-PMX-Version: 5.4.1.325704 References: <200901081513.n08FDN2Y013300@sac.sfbay.sun.com> <496AAA5E.40002@Sun.COM> User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) Status: RO Content-Length: 5137 This is a multi-part message in MIME format. --Boundary_(ID_4YecN1VKcTJU3rd+yIVikA) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT The project team has proved an updated spec: sac:/shared/sac/Archives/CaseLog/arc/PSARC/2009/011: -rw-r--r-- 1 markcarl sac 2585 Jan 14 14:29 iSCSI_init_smf.diff -rw-r--r-- 1 markcarl sac 3242 Jan 8 07:07 iSCSI_init_smf.old -rw-r--r-- 1 markcarl staff 4350 Jan 14 14:26 iSCSI_init_smf.txt (also attached) that specifies this. -- mark Darren J Moffat wrote: > I assume the correct thing happesn on upgrade to remove the old FMRI. > > If so +1. > > --Boundary_(ID_4YecN1VKcTJU3rd+yIVikA) Content-type: text/plain; name=iSCSI_init_smf.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=iSCSI_init_smf.txt 1. Introduction 1.1. Project/Component Working Name: iSCSI Initiator SMF Service 1.2. Name of Document Author/Supplier: Author: Jack Meng 1.3 Date of This Document: 25 December, 2008 2. Project Summary 2.1. Project Description This project makes the existing iSCSI initiator feature in Solaris a standard SMF service. 4. Technical Description 4.1. Details: Currently iSCSI initiator feature does not exist as an SMF service in Solaris. The existing service svc:/network/iscsi_initiator:default, came with PSARC/2003/126 iSCSI project, only represents the name resolutions service for the iSCSI kernel module. This is always confusing since the enable/disable of that service doesn't affect the behavior of iSCSI initiator. iSCSI module starts the kernel daemon in its attach routine, which is a behavior blind of the status of the OS and causing defects/limitation that can not be fixed within present architecture, few examples are listed below: 1. 'Unable to login to xxxxxxxxxxx' during system startup 2. Inconsistent connections may happen after system rebooted as the login failed during startup 3. Unable to add customized dependency for special usage, e.g., iSCSI disk is used as shared device in cluster, so iSCSI initiator should try to login after iSCSI target online. This project provides an upgraded service, named svc:/network/iscsi/initiator:default to replace the existing service with new functionality and existing nationalities in svc:/network/iscsi_initiator:default will be inherited. The upgraded service will provide following benefits, 1. Users are able to explicitly enable/disable iSCSI initiator feature in Solaris. 2. Avoid the blindly starting up by specifying dependencies. 3. iSCSI initiator will be more flexible to serve special requirements. All methods in the upgraded service will be provided with following least privilege, The default state of the upgraded service will be 'enabled' while it is 'disabled' in existing service. Also, the existing service is an uncommitted interface and this case will upgrade the stability to committed with a different name to unify the naming of services of iscsi software initiator/target. If the upgraded service is disabled, the current CLI, iscsiadm, will just prompt users that service is not running and then exits without doing any further actions, e.g., root@iscsi:$ iscsiadm list target The service of iSCSI software initiator is not running. The removal of the original service and install of the new one will be a part of Solaris upgrade install process. 4.5 Interfaces: Exported Interface | Stability | Description --------------------------------------|--------------|------------------- svc:/network/iscsi/initiator:default | Committed | iSCSI initiator service, | | upgraded from iscsi_initiator:default | | with new functions Imported Interface | Stability | Description --------------------------------------|--------------|------------------- usr/share/man/man7d/iscsi.7d | Committed | manpage of iSCSI initiator usr/share/man/man1m/iscsiadm.1m | Committed | manpage of iSCSI initiator CLI usr/sbin/iscsiadm | Committed | iSCSI initiator CLI Removed Interface | Stability | Description --------------------------------------|--------------|------------------- svc:/network/iscsi_initiator:default | Uncommitted | service for iSCSI name resolution Other documents: PSARC/2003/126 iSCSI project: http://sac.sfbay/PSARC/2003/126/ System Administration Guide: Devices and File Systems, Chapter 14 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ONNV 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open --Boundary_(ID_4YecN1VKcTJU3rd+yIVikA)-- From Mark.Carlson@sun.com Wed Jan 14 16:06:26 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n0F06POV029446 for ; Wed, 14 Jan 2009 16:06:25 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n0F065AI025347 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 15 Jan 2009 08:06:24 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KDH00E07KANK500@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Wed, 14 Jan 2009 16:06:23 -0800 (PST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KDH003JXKANJJ50@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Wed, 14 Jan 2009 16:06:23 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n0F06N7j019631 for ; Thu, 15 Jan 2009 00:06:23 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KDH00601JYU7J00@mail-amer.sun.com> (original mail from Mark.Carlson@Sun.COM) for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Wed, 14 Jan 2009 17:06:23 -0700 (MST) Received: from Macintosh-335.local ([129.150.32.109]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KDH00F5PKAALEE0@mail-amer.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Wed, 14 Jan 2009 17:06:11 -0700 (MST) Date: Wed, 14 Jan 2009 17:06:08 -0700 From: "Mark A. Carlson" Subject: Re: iSCSI Initiator SMF Service [PSARC/2009/011 FastTrack timeout 01/15/2009] In-reply-to: <200901081513.n08FDN2Y013300@sac.sfbay.sun.com> Sender: Mark.Carlson@sun.com To: PSARC-ext@sun.com Cc: Jack.Meng@sun.com Message-id: <496E7DF0.2050108@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200901081513.n08FDN2Y013300@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) Status: RO Content-Length: 48 This case was approved at PSARC today. -- mark From Mark.Carlson@sun.com Tue May 19 07:37:35 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n4JEbZ2q013006 for ; Tue, 19 May 2009 07:37:35 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n4JEbWcI000228 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Tue, 19 May 2009 07:37:35 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KJW00D07BAMAJ00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 19 May 2009 08:37:34 -0600 (MDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJW00D1GBAL9900@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 19 May 2009 08:37:33 -0600 (MDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n4JEbXKC001923 for ; Tue, 19 May 2009 14:37:33 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KJW00K00AJGL200@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 19 May 2009 08:37:33 -0600 (MDT) Received: from Macintosh-335.local ([unknown] [129.150.32.138]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KJW00IF4BAKZIA0@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 19 May 2009 08:37:33 -0600 (MDT) Date: Tue, 19 May 2009 08:37:32 -0600 From: "Mark A. Carlson" Subject: Re: iSCSI Initiator SMF Service [PSARC/2009/011 FastTrack timeout 01/15/2009] In-reply-to: <496E7DF0.2050108@sun.com> Sender: Mark.Carlson@sun.com To: PSARC-ext@sun.com Cc: Jack.Meng@sun.com Message-id: <4A12C42C.5040202@sun.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_TEJscaBbVPBtsRmKaJfd/w)" X-PMX-Version: 5.4.1.325704 References: <200901081513.n08FDN2Y013300@sac.sfbay.sun.com> <496E7DF0.2050108@sun.com> User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) Status: RO Content-Length: 5037 This is a multi-part message in MIME format. --Boundary_(ID_TEJscaBbVPBtsRmKaJfd/w) Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT The project team has requested patch binding for this case due to a requirement to back port to Solaris. I have updated the case materials and marked it closed approved automatic, but am willing to set a timer if an ARC member so desires. -- mark --Boundary_(ID_TEJscaBbVPBtsRmKaJfd/w) Content-type: text/plain; name=iSCSI_init_smf.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=iSCSI_init_smf.txt 1. Introduction 1.1. Project/Component Working Name: iSCSI Initiator SMF Service 1.2. Name of Document Author/Supplier: Author: Jack Meng 1.3 Date of This Document: 25 December, 2008 2. Project Summary 2.1. Project Description This project makes the existing iSCSI initiator feature in Solaris a standard SMF service. 4. Technical Description 4.1. Details: Currently iSCSI initiator feature does not exist as an SMF service in Solaris. The existing service svc:/network/iscsi_initiator:default, came with PSARC/2003/126 iSCSI project, only represents the name resolutions service for the iSCSI kernel module. This is always confusing since the enable/disable of that service doesn't affect the behavior of iSCSI initiator. iSCSI module starts the kernel daemon in its attach routine, which is a behavior blind of the status of the OS and causing defects/limitation that can not be fixed within present architecture, few examples are listed below: 1. 'Unable to login to xxxxxxxxxxx' during system startup 2. Inconsistent connections may happen after system rebooted as the login failed during startup 3. Unable to add customized dependency for special usage, e.g., iSCSI disk is used as shared device in cluster, so iSCSI initiator should try to login after iSCSI target online. This project provides an upgraded service, named svc:/network/iscsi/initiator:default to replace the existing service with new functionality and existing nationalities in svc:/network/iscsi_initiator:default will be inherited. The upgraded service will provide following benefits, 1. Users are able to explicitly enable/disable iSCSI initiator feature in Solaris. 2. Avoid the blindly starting up by specifying dependencies. 3. iSCSI initiator will be more flexible to serve special requirements. All methods in the upgraded service will be provided with following least privilege, The default state of the upgraded service will be 'enabled' while it is 'disabled' in existing service. Also, the existing service is an uncommitted interface and this case will upgrade the stability to committed with a different name to unify the naming of services of iscsi software initiator/target. If the upgraded service is disabled, the current CLI, iscsiadm, will just prompt users that service is not running and then exits without doing any further actions, e.g., root@iscsi:$ iscsiadm list target The service of iSCSI software initiator is not running. The removal of the original service and install of the new one will be a part of Solaris upgrade install process. 4.5 Interfaces: Exported Interface | Stability | Description --------------------------------------|--------------|------------------- svc:/network/iscsi/initiator:default | Committed | iSCSI initiator service, | | upgraded from iscsi_initiator:default | | with new functions Imported Interface | Stability | Description --------------------------------------|--------------|------------------- usr/share/man/man7d/iscsi.7d | Committed | manpage of iSCSI initiator usr/share/man/man1m/iscsiadm.1m | Committed | manpage of iSCSI initiator CLI usr/sbin/iscsiadm | Committed | iSCSI initiator CLI Removed Interface | Stability | Description --------------------------------------|--------------|------------------- svc:/network/iscsi_initiator:default | Uncommitted | service for iSCSI name resolution Other documents: PSARC/2003/126 iSCSI project: http://sac.sfbay/PSARC/2003/126/ System Administration Guide: Devices and File Systems, Chapter 14 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ONNV, ON10 6.4.2. Target Release/Binding This feature will be backported to S10U8 and requires a patch binding. 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open --Boundary_(ID_TEJscaBbVPBtsRmKaJfd/w)--