From markcarl@sac.sfbay.sun.com Wed Jan 14 15:42:26 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n0ENgPx3005338 for ; Wed, 14 Jan 2009 15:42:25 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n0ENgOXc049414; Wed, 14 Jan 2009 16:42:25 -0700 (MST) 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 <0KDH00B0FJ6NFW00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 14 Jan 2009 15:42:23 -0800 (PST) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KDH0036GJ6MJC30@nwk-avmta-1.sfbay.Sun.COM>; Wed, 14 Jan 2009 15:42:22 -0800 (PST) Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n0ENgLMb046586; Wed, 14 Jan 2009 15:42:21 -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 n0ENgGgc005328; Wed, 14 Jan 2009 15:42:16 -0800 (PST) Received: (from markcarl@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n0ENgG3X005324; Wed, 14 Jan 2009 15:42:16 -0800 (PST) Date: Wed, 14 Jan 2009 15:42:16 -0800 (PST) From: Mark Carlson Subject: SBLIMCIMClient [LSARC/2009/025 FastTrack timeout 01/21/2009] To: LSARC-ext@sun.com Cc: Bharath.Madakatte@sun.com Message-id: <200901142342.n0ENgG3X005324@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 2628 I am sponsoring this familiarity case for Bharath Kumar. It requests minor binding and times out on 01/21/2009. -- mark Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: SBLIMCIMClient 1.2. Name of Document Author/Supplier: Author: Bharath Kumar 1.3 Date of This Document: 14 January, 2009 4. Technical Description 1. Introduction 1.1. Project/Component Working Name: SBLIMCIMClient 1.2. Name of Document Author/Supplier: Author: Bharath Kumar 1.3. Date of This Document: 06 January 2009 2. Project Summary 2.1 Project Description This project introduces the package of SBLIMCIMClient 1.3.7 into the SFW consolidation. 4. Technical Description: SBLIM is an acronym for Standards Based Linux Instrumentation for Manageability. The goal of this project is to provide a complete Open Source implementation of a WBEM-based management solution for Linux. The SBLIM CIM Client for Java is an implementation of a WBEM services client that includes an IETF RFC 2614 compliant SLP client for CIM service discovery. It is intended to be used by management applications in all areas that leverage CIM technology such as SMI-S, SMASH, etc.The design of the SBLIM Client has put emphasis on low memory consumption and high performance. It offers different options to use the implemented XML parser (SAX, DOM, Pull). Furthermore, a comfortable way to debug interoperability issues by dumping the XML request and response to a log file is provided. 5. Interfaces Exported interface Classification Interface type =========================== ============== ============== SUNWSBLIMCIMClient Uncommitted SBLIMCIMClient Package SBLIMCIMClient API Uncommitted SBLIMCIMClient Classes sblimCIMClient.jar Uncommitted SBLIMCIMClient jar sblimSLPClient.jar Uncommitted SBLIMCIMClient jar /usr/share/lib/sblim Project Private SBLIMCIMClient directory /usr/share/doc/sblim Project Private SBLIMCIMClient doc directory Imported Interfaces ------------------- None 6. Resources and Schedule: 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: SFW 6.5. ARC review type: Automatic 6.6. ARC Exposure: open 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From James.Walker@sun.com Fri Jan 23 12:24:17 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n0NKOHEB000169 for ; Fri, 23 Jan 2009 12:24:17 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n0NKOF5c007055 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Fri, 23 Jan 2009 13:24:16 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KDX0030HY0FN200@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.COM); Fri, 23 Jan 2009 12:24:15 -0800 (PST) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KDX00ICSY0DE2A0@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.COM); Fri, 23 Jan 2009 12:24:13 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n0NKODIi018457 for ; Fri, 23 Jan 2009 20:24:13 +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 <0KDX00501XPX7900@mail-amer.sun.com> (original mail from James.Walker@Sun.COM) for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Fri, 23 Jan 2009 13:24:13 -0700 (MST) Received: from [172.20.25.153] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KDX000NPY02W1E0@mail-amer.sun.com> for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Fri, 23 Jan 2009 13:24:02 -0700 (MST) Date: Fri, 23 Jan 2009 13:49:03 -0700 From: Jim Walker Subject: SBLIMCIMClient [LSARC/2009/025 FastTrack timeout 01/21/2009] Sender: James.Walker@sun.com To: lsarc-ext@sun.com Cc: Bharath.Madakatte@sun.com, Mark Carlson Reply-to: James.Walker@sun.com Message-id: <497A2D3F.3070503@sun.com> Organization: Sun Microsystems, Inc. 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 User-Agent: Thunderbird 2.0.0.14 (X11/20080728) Status: RO Content-Length: 1172 I didn't follow this case until now, so pardon if this has already been discussed... I'm doing a code review for this sfw project and noticed the jar files are being delivered into /usr/share/lib/sblim instead of /usr/share/lib/java. Is that correct? Can more than one application use the jar files? Also, can the case materials be updated to reflect where the jar files are being delivered (I have learned not to assume anything :) 5. Interfaces Exported interface Classification Interface type =========================== ============== ============== SUNWSBLIMCIMClient Uncommitted SBLIMCIMClient Package SBLIMCIMClient API Uncommitted SBLIMCIMClient Classes sblimCIMClient.jar Uncommitted SBLIMCIMClient jar sblimSLPClient.jar Uncommitted SBLIMCIMClient jar /usr/share/lib/sblim Project Private SBLIMCIMClient directory /usr/share/doc/sblim Project Private SBLIMCIMClient doc directory BTW. From the code review, only the two jar files go in /usr/share/lib/sblim, so Uncommitted may be better if /usr/share/lib/java isn't used. Cheers, Jim From Bharath.Madakatte@sun.com Mon Jan 26 23:01:02 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 n0R712rf004769 for ; Mon, 26 Jan 2009 23:01:02 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n0R70wW7016227 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Mon, 26 Jan 2009 23:01:01 -0800 (PST) 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 <0KE400B0PBHP0000@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.COM); Mon, 26 Jan 2009 23:01:01 -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 <0KE400MF1BH8K740@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.COM); Mon, 26 Jan 2009 23:00:44 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n0R70hiW007551 for ; Tue, 27 Jan 2009 07:00:43 +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 <0KE400701BCFWD00@mail-amer.sun.com> (original mail from Bharath.Madakatte@Sun.COM) for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Tue, 27 Jan 2009 00:00:43 -0700 (MST) Received: from [10.114.58.92] ([203.91.196.62]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KE40086PBGZ0JC0@mail-amer.sun.com> for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Tue, 27 Jan 2009 00:00:43 -0700 (MST) Date: Tue, 27 Jan 2009 12:36:00 +0530 From: Bharath Kumar Subject: Re: SBLIMCIMClient [LSARC/2009/025 FastTrack timeout 01/21/2009] In-reply-to: <497A2D3F.3070503@sun.com> Sender: Bharath.Madakatte@sun.com To: James.Walker@sun.com Cc: lsarc-ext@sun.com, Mark Carlson Reply-to: Bharath.Madakatte@sun.com Message-id: <497EB258.6030702@Sun.Com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_73Wd3wDKqqYJIP2zu0hGBQ)" X-PMX-Version: 5.4.1.325704 References: <497A2D3F.3070503@sun.com> User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) Status: RO Content-Length: 20779 This is a multi-part message in MIME format. --Boundary_(ID_73Wd3wDKqqYJIP2zu0hGBQ) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Hi Jim, Jim Walker wrote: > I didn't follow this case until now, so pardon if this has already > been discussed... > > I'm doing a code review for this sfw project and noticed the > jar files are being delivered into /usr/share/lib/sblim > instead of /usr/share/lib/java. > > Is that correct? As mentioned during code review discussion, I had done a quick look at '/usr/share/lib', noticed that components like freetts, jato, slp had their own dirs where they installed their jars. Hence followed a similar approach. As requested in that review mail thread, can you please let know if there are specific rules/polices for deploying jars in specific dirs? (eg: /usr/share/lib/java) > > Can more than one application use the jar files? Yes, more than one application can use the jar files. Imperius (LSARC/2009/010) will be using it going forward. > > Also, can the case materials be updated to reflect where the > jar files are being delivered (I have learned not to assume > anything :) > Sure, I have updated the case material to show the path where the jars are getting delivered. Attaching them herewith. Thanks Bharath --Boundary_(ID_73Wd3wDKqqYJIP2zu0hGBQ) Content-type: text/plain; name=SBLIMCIMClient.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=SBLIMCIMClient.txt FCL--FOSS Check List 0. Introduction 0.1 Document History Version Author Changes Date 0.1 Bharath Kumar Initial Draft 01/06/2009 0.2 Purpose This checklist is to aid in the FastTrack ARC review process for the integration of SBLIMCIMClient Java project into OpenSolaris 1.0 Project Information 1.1 Name of project/component SBLIMCIMClient 1.2 Author of document Bharath Kumar Madakatte 2.0 Project Summary 2.1 Project Description SBLIM is an acronym for Standards Based Linux Instrumentation for Manageability. The goal of this project is to provide a complete Open Source implementation of a WBEM-based management solution for Linux. The SBLIM CIM Client for Java is an implementation of a WBEM services client that includes an IETF RFC 2614 compliant SLP client for CIM service discovery. It is intended to be used by management applications in all areas that leverage CIM technology such as SMI-S, SMASH, etc.The design of the SBLIM Client has put emphasis on low memory consumption and high performance. It offers different options to use the implemented XML parser (SAX, DOM, Pull). Furthermore, a comfortable way to debug interoperability issues by dumping the XML request and response to a log file is provided. 2.2 Release binding What is is the release binding? (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) [ ] Major [X] Minor [ ] Patch or Micro [ ] Unknown -- ARC review required 2.3 Type of project Is this case a Linux Familiarity project? [X] Yes [ ] No 2.4 Originating Community 2.4.1 Community Name http://sblim.wiki.sourceforge.net/CimClient 2.4.2 Community Involvement Indicate Sun's involvement in the community [ ] Maintainer [ ] Contributor [X] Monitoring Will the project team work with the upstream community to resolve architectural issues of interest to Sun? [X] Yes [ ] No - briefly explain Will we or are we forking from the community? [ ] Yes - ARC review required prior to forking [X] No 3.0 Technical Description 3.1 Installation & Sharable 3.1.1S Solaris Installation - section only required for Solaris Software (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) Does this project follow the Install Locations best practice? [X] Yes [ ] No - ARC review required Does this project install into /usr under [sbin|bin|lib|include|man|share]? [X] Yes [ ] No or N/A Does this project install into /opt? [ ] Yes - explain below [X] No or N/A Does this project install into a different directory structure? [ ] Yes - ARC review required [X] No or N/A Do any of the components of this project conflict with anything under /usr? (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) [ ] Yes - explain below [X] No If conflicts exist then will this project install under /usr/gnu? [ ] Yes [ ] No - ARC review required [X] N/A Is this project installing into /usr/sfw? [ ] Yes - ARC review required [X] No 3.1.1W Windows Installation - section only required for Windows Software (see http://sac.sfbay/WSARC/2002/494 for details) Does this project install software into a :\Program Files\Sun\ or :\Sun\ directory? [ ] Yes [ ] No - ARC review required Does the project use the Windows registry? [ ] Yes [ ] No - ARC review required Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ for the registry key? [ ] Yes [ ] No - ARC review required Is the project's stored location HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? [ ] Yes [ ] No - ARC review required 3.1.2 Share and Sharable Does the module include any components that are used or shared by other projects? [ ] Yes [X] No If yes are these components packaged to be shared with the other FOSS? [ ] Yes [ ] No - ARC review required [X] N/A Are these components already in the Solaris WOS? [ ] Yes [X] No - continue with next section (section 3.2) If yes are these newer versions being delivered? [ ] Yes [ ] No - ARC review required If yes are the newer versions replacing the existing versions? [ ] Yes [ ] No - ARC review required 3.2 Exported Libraries Are libraries being delivered by this project? [X] Yes [ ] No - continue with next section (section 3.3) Are 64-bit versions of the libraries being delivered? [X] Yes [ ] No - ARC review required Since these are Java jar libraries, there are no separate 64 bit jars. Are static versions of the libraries being delivered? [ ] Yes - ARC review required [X] No 3.3 Services and the /etc Directory (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) Does the project integrate anything into /etc/init.d or /etc/rc?.d? [ ] Yes - ARC review required [X] No Does the project integrate any new entries into /etc/inittab or /etc/inetd.conf? [ ] Yes - ARC review required [X] No Does the project integrate any private non-public files into /etc/default or /etc/ configuration files? [ ] Yes - ARC review required [X] No Does the service manifests method context grant rights above that of the noaccess user and basic privilege set? [ ] Yes - ARC review required [X] No 3.4 Security 3.4.1 Secure By Default (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for addtional details) Are there any network services provided by this project? [ ] Yes [X] No - continue with the next section (section 3.4.2) Are network services enabled by default? [ ] Yes - ARC review required [ ] No [ ] N/A Are network services automatically enabled by the project during installation? [ ] Yes - ARC review required [ ] No [ ] N/A Are inbound network communications denied by default? [ ] Yes [ ] No - ARC review required [ ] N/A Is inbound data checked to prevent content-based attacks? [ ] Yes [ ] No - ARC review required [ ] N/A Is the outbound receiver authenticated? [ ] Yes [ ] No - ARC review required [ ] N/A Is the receiver authenticated prior to receiving any sensitive outbound communication? [ ] Yes [ ] No - ARC review required [ ] N/A 3.4.2 Authorization (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ for details) Are there any setuid/setgid privileged binaries in the project? [ ] Yes - ARC review required [X] No - continue with next section (section 3.4.3) If yes then are the setuid/setgid privileges handled by the use of roles? [ ] Yes [ ] No - ARC review required 3.4.3 Auditing (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Does this component contain administrative or security enforcing software? [ ] Yes - ARC review required [X] No - continue to next section (section 3.4.4) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Do the components create audit logs detailing what took place including what event took place, who was involved, when the event took place? [ ] Yes - ARC contract and Audit project team review required [ ] No - ARC review required 3.4.4 Authentication (see http://opensolaris.org/os/community/arc/policies/PAM/) Do the components contain any authentication code? [ ] Yes [X] No - continue to next section (section 3.4.5) If yes do the components use PAM (plugable authentication modules) for authentication? [ ] Yes [ ] No - ARC review required If yes is a single PAM session maintained during authentication? [ ] Yes [ ] No - ARC review required If yes are the components sufficiently privileged to allow the requested operations (authentication, password change, process credential manipulation, audit state initialization)? [ ] Yes - briefly describe below [ ] No - ARC review required 3.4.5 Passwords (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) Do any of the components for the project deal with passwords? [X] Yes [ ] No - continue to next section (section 3.4.6) If yes are these passwords entered via the CLI or environment? [ ] Yes - ARC review required [X] No Are passwords stored within the file system for the component? [ ] Yes [X] No - continue to next section (section 3.4.6) If yes are the permissions on the file such to protect exposing the password(s)? [ ] Yes [ ] No - ARC review required 3.4.6 General Security Questions (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) Are there any network protocols used by this project? [X] Yes [ ] No - continue with the next section (section 3.5) Do the components use standard network protocols? [X] Yes [ ] No - ARC review required Do network services for the project make decisions based upon user, host or service identities? [ ] Yes - explain below [ ] No [X] N/A Do the components make use of secret information during authentication and/or authorization? [ ] Yes - explain below [ ] No [X] N/A 3.5 Networking Do the components access the network? [X] Yes [ ] No - continue with the next section (section 3.6) If yes do the components support IPv6? [X] Yes [ ] No - ARC review required 3.6 Core Solaris Components Do the components of this project compete with or duplicate core Solaris components? [ ] Yes - ARC review required [X] No Examples of Core Solaris Components include but are not limited to: Secure By Default Authorizations PAM -- Plugable Authentication Module Privilege PRM -- Process Rights Management -- Privilege Audit xVm -- Virtualization zones / Solaris Containers PRM -- Process Rights Management RBAC -- Role Based Access Control TX / Trusted Extensions ZFS SMF -- Service Management Facility FMA -- Fault Management Architecture SCF -- Smart Card Facility IPsec 4.0 Interfaces (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details) 4.1 Exported Interfaces Interface Name Classification Comments --------------------------- ---------------- --------------------------- SUNWSBLIMCIMClient Uncommitted SBLIMCIMClient Package SBLIMCIMClient API Uncommitted SBLIMCIMClient Classes /usr/share/lib/sblim/sblimCIMClient.jar Uncommitted SBLIMCIMClient jar /usr/share/lib/sblim/sblimSLPClient.jar Uncommitted SBLIMCIMClient jar /usr/share/lib/sblim Project Private SBLIMCIMClient directory /usr/share/doc/sblim Project Private SBLIMCIMClient doc directory 4.2 Imported Interfaces Interface Name Classification Comments ------------------------ ------------------ -------------------------- java.net.* Committed Java networking libraries Brief Interface Classifications - See Appendix C for definitions Volatile - interfaces are fluid and will follow a rapidly changing community Uncommitted - interfaces are still evolving in the community and might follow the community Committed - interfaces are stable in the community Project Private - no review required, just document in table Contracted (interface modifier) - further review required Appendix A - References 1. Solaris Installation Locations Policy http://opensolaris.org/os/community/arc/policies/install-locations/ 2. /usr/gnu Installation ARC case http://opensolaris.org/os/community/arc/caselog/2007/047/ 3. Secure By Default Policy http://opensolaris.org/os/community/arc/policies/secure-by-default/ 4. Network Install Time Securityuy Policy http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ 5. Adding RBAC Authorizations Policy http://opensolaris.org/os/community/arc/bestpractices/rbac-auths/ 6. When to use setuid -vs- RBAC roles and profiles http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and 7. Building RBAC Rights Profiles http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ 8. Solaris Audit Policy http://opensolaris.org/os/community/arc/policies/audit-policy/ 9. Security questionaire http://opensolaris.org/os/community/arc/bestpractices/security-questions/ 10. Interface Taxonomy http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ 11. Plugable Authentication Modules -- PAM http://opensolaris.org/os/community/arc/policies/PAM/ 12. Reusable Passwords In Command Line Arguments and Environment Variables http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ 13. Storing Reusable Passwords on a Filesystem http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ 14. Release Taxonomy http://opensolaris.org/os/community/arc/policies/release-taxonomy/ 15. Service Management Facility (SMF) usage http://opensolaris.org/os/community/arc/policies/SMF-policy/ Appendix B - Suggested case materials 1. man pages 2. SMF manifests 3. links to contracts Appendix C - Definitions Submitter an agent responsible for creation of an ARC project along with the materials describing that project. Owner the ARC agent responsible for shepherding the case through review and ensuring a formal opinion is written where required. Maintainer an agent responsible for releasing new versions of a program, typically the "main" contributor or person incharge of making Architectural decisions for the project Contributor an agent who make contributions to a project, typically has a voice in making Architectural decisions for the project Monitoring an agent who is only following the changes made in the community and has no Architectural input into the project Volatile* interfaces that are very fluid and typically follow the originating community. Typically these interfaces can not be imported by other projects. Uncommitted* interfaces that are still evolving but will most likely be present from release to release. Committed* interfaces that are stable and with Sun guaranteeing some level of compatibility from release to release. Project Private* interfaces that are exposed only to or intended to be used only by the project being reviewed. These interfaces can not be imported by other projects. Not-An-Interface* components that are not interfaces. Contracted* (interface modifier) - ARC review of Contract required interfaces that do not allow another project to import can be *Note: see http://opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details --Boundary_(ID_73Wd3wDKqqYJIP2zu0hGBQ) Content-type: text/plain; name=SBLIMCIMClient-Arc.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=SBLIMCIMClient-Arc.txt 1. Introduction 1.1. Project/Component Working Name: SBLIMCIMClient 1.2. Name of Document Author/Supplier: Author: Bharath Kumar 1.3. Date of This Document: 06 January 2009 2. Project Summary 2.1 Project Description This project introduces the package of SBLIMCIMClient 1.3.7 into the SFW consolidation. 4. Technical Description: SBLIM is an acronym for Standards Based Linux Instrumentation for Manageability. The goal of this project is to provide a complete Open Source implementation of a WBEM-based management solution for Linux. The SBLIM CIM Client for Java is an implementation of a WBEM services client that includes an IETF RFC 2614 compliant SLP client for CIM service discovery. It is intended to be used by management applications in all areas that leverage CIM technology such as SMI-S, SMASH, etc.The design of the SBLIM Client has put emphasis on low memory consumption and high performance. It offers different options to use the implemented XML parser (SAX, DOM, Pull). Furthermore, a comfortable way to debug interoperability issues by dumping the XML request and response to a log file is provided. 5. Interfaces Exported interfaces ------------------- Interface Name Classification Comments --------------------------- ---------------- --------------------------- SUNWSBLIMCIMClient Uncommitted SBLIMCIMClient Package SBLIMCIMClient API Uncommitted SBLIMCIMClient Classes /usr/share/lib/sblim/sblimCIMClient.jar Uncommitted SBLIMCIMClient jar /usr/share/lib/sblim/sblimSLPClient.jar Uncommitted SBLIMCIMClient jar /usr/share/lib/sblim Project Private SBLIMCIMClient directory /usr/share/doc/sblim Project Private SBLIMCIMClient doc directory Imported Interfaces ------------------- Interface Name Classification Comments ------------------------ ------------------ -------------------------- java.net.* Committed Java networking libraries 6. Resources and Schedule: 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: SFW 6.5. ARC review type: Automatic 6.6. ARC Exposure: open --Boundary_(ID_73Wd3wDKqqYJIP2zu0hGBQ)-- From James.Walker@sun.com Mon Jan 26 23:19:48 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 n0R7JlTk004933 for ; Mon, 26 Jan 2009 23:19:47 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n0R7JfJZ006310 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Tue, 27 Jan 2009 07:19:46 GMT 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 <0KE400F03CCXCL00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.COM); Mon, 26 Jan 2009 23:19:45 -0800 (PST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KE400M64CCWJZ50@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.COM); Mon, 26 Jan 2009 23:19:45 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n0R7Jiel007316 for ; Tue, 27 Jan 2009 07:19:44 +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 <0KE400A01CC3B000@mail-amer.sun.com> (original mail from James.Walker@Sun.COM) for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Tue, 27 Jan 2009 00:19:44 -0700 (MST) Received: from c-24-8-61-165.hsd1.co.comcast.net ([24.8.61.165]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KE4002XBCCW8QE0@mail-amer.sun.com> for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Tue, 27 Jan 2009 00:19:44 -0700 (MST) Date: Tue, 27 Jan 2009 00:19:44 -0700 From: Jim Walker Subject: Re: SBLIMCIMClient [LSARC/2009/025 FastTrack timeout 01/21/2009] In-reply-to: <497EB258.6030702@Sun.Com> Sender: James.Walker@sun.com To: Bharath.Madakatte@sun.com Cc: lsarc-ext@sun.com Reply-to: James.Walker@sun.com Message-id: <497EB590.4030508@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: <497A2D3F.3070503@sun.com> <497EB258.6030702@Sun.Com> User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) Status: RO Content-Length: 1000 Bharath Kumar wrote: > As mentioned during code review discussion, I had done a quick look > at '/usr/share/lib', noticed that components like freetts, jato, slp > had their own dirs where they installed their jars. Hence followed a > similar approach. As requested in that review mail thread, can you > please let know if there are specific rules/polices for deploying > jars in specific dirs? (eg: /usr/share/lib/java) During the discussion for Junit (LSARC/2008/633), /usr/share/lib/java was identified as the location for jar files used by multiple applications (ie. one common location, instead of many project specific locations). An opinion was proposed, but I lost track of that. >> Can more than one application use the jar files? > Yes, more than one application can use the jar files. Imperius > (LSARC/2009/010) will be using it going forward. This is why is suggested that the common location be used, unless you have a reason for creating a project specific location. Cheers, Jim From Bharath.Madakatte@Sun.COM Tue Jan 27 03:42:17 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 n0RBgH03027768 for ; Tue, 27 Jan 2009 03:42:17 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n0RBgHCx015354 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Tue, 27 Jan 2009 03:42:17 -0800 (PST) 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 <0KE40040BOIGW600@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.COM); Tue, 27 Jan 2009 03:42:16 -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 <0KE400D4UOIF1ZC0@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.COM); Tue, 27 Jan 2009 03:42:15 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n0RBgFvV005207 for ; Tue, 27 Jan 2009 11:42:15 +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 <0KE400601OCSCQ00@mail-amer.sun.com> (original mail from Bharath.Madakatte@Sun.COM) for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Tue, 27 Jan 2009 04:42:15 -0700 (MST) Received: from [10.114.58.92] ([203.91.196.62]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KE400EDAOI91R70@mail-amer.sun.com> for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Tue, 27 Jan 2009 04:42:14 -0700 (MST) Date: Tue, 27 Jan 2009 17:17:31 +0530 From: Bharath Kumar Subject: Re: SBLIMCIMClient [LSARC/2009/025 FastTrack timeout 01/21/2009] In-reply-to: <497EB590.4030508@sun.com> Sender: Bharath.Madakatte@Sun.COM To: James.Walker@Sun.COM Cc: lsarc-ext@Sun.COM Reply-to: Bharath.Madakatte@Sun.COM Message-id: <497EF453.3020306@Sun.Com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_QFRVWobqeH4vAb4BwKF52g)" X-PMX-Version: 5.4.1.325704 References: <497A2D3F.3070503@sun.com> <497EB258.6030702@Sun.Com> <497EB590.4030508@sun.com> User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) Status: RO Content-Length: 20806 This is a multi-part message in MIME format. --Boundary_(ID_QFRVWobqeH4vAb4BwKF52g) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Hi Jim, Jim Walker wrote: > Bharath Kumar wrote: >> As mentioned during code review discussion, I had done a quick look >> at '/usr/share/lib', noticed that components like freetts, jato, slp >> had their own dirs where they installed their jars. Hence followed a >> similar approach. As requested in that review mail thread, can you >> please let know if there are specific rules/polices for deploying >> jars in specific dirs? (eg: /usr/share/lib/java) > > During the discussion for Junit (LSARC/2008/633), /usr/share/lib/java > was identified as the location for jar files used by multiple > applications (ie. one common location, instead of many project > specific locations). > > An opinion was proposed, but I lost track of that. > >>> Can more than one application use the jar files? >> Yes, more than one application can use the jar files. Imperius >> (LSARC/2009/010) will be using it going forward. > > This is why is suggested that the common location be used, > unless you have a reason for creating a project specific > location. > I have modified the ARC docs as per your suggestion to deliver the jars into '/usr/share/lib/java'. Please find them attached. Thanks Bharath --Boundary_(ID_QFRVWobqeH4vAb4BwKF52g) Content-type: text/plain; name=SBLIMCIMClient.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=SBLIMCIMClient.txt FCL--FOSS Check List 0. Introduction 0.1 Document History Version Author Changes Date 0.1 Bharath Kumar Initial Draft 01/06/2009 0.2 Purpose This checklist is to aid in the FastTrack ARC review process for the integration of SBLIMCIMClient Java project into OpenSolaris 1.0 Project Information 1.1 Name of project/component SBLIMCIMClient 1.2 Author of document Bharath Kumar Madakatte 2.0 Project Summary 2.1 Project Description SBLIM is an acronym for Standards Based Linux Instrumentation for Manageability. The goal of this project is to provide a complete Open Source implementation of a WBEM-based management solution for Linux. The SBLIM CIM Client for Java is an implementation of a WBEM services client that includes an IETF RFC 2614 compliant SLP client for CIM service discovery. It is intended to be used by management applications in all areas that leverage CIM technology such as SMI-S, SMASH, etc.The design of the SBLIM Client has put emphasis on low memory consumption and high performance. It offers different options to use the implemented XML parser (SAX, DOM, Pull). Furthermore, a comfortable way to debug interoperability issues by dumping the XML request and response to a log file is provided. 2.2 Release binding What is is the release binding? (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) [ ] Major [X] Minor [ ] Patch or Micro [ ] Unknown -- ARC review required 2.3 Type of project Is this case a Linux Familiarity project? [X] Yes [ ] No 2.4 Originating Community 2.4.1 Community Name http://sblim.wiki.sourceforge.net/CimClient 2.4.2 Community Involvement Indicate Sun's involvement in the community [ ] Maintainer [ ] Contributor [X] Monitoring Will the project team work with the upstream community to resolve architectural issues of interest to Sun? [X] Yes [ ] No - briefly explain Will we or are we forking from the community? [ ] Yes - ARC review required prior to forking [X] No 3.0 Technical Description 3.1 Installation & Sharable 3.1.1S Solaris Installation - section only required for Solaris Software (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) Does this project follow the Install Locations best practice? [X] Yes [ ] No - ARC review required Does this project install into /usr under [sbin|bin|lib|include|man|share]? [X] Yes [ ] No or N/A Does this project install into /opt? [ ] Yes - explain below [X] No or N/A Does this project install into a different directory structure? [ ] Yes - ARC review required [X] No or N/A Do any of the components of this project conflict with anything under /usr? (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) [ ] Yes - explain below [X] No If conflicts exist then will this project install under /usr/gnu? [ ] Yes [ ] No - ARC review required [X] N/A Is this project installing into /usr/sfw? [ ] Yes - ARC review required [X] No 3.1.1W Windows Installation - section only required for Windows Software (see http://sac.sfbay/WSARC/2002/494 for details) Does this project install software into a :\Program Files\Sun\ or :\Sun\ directory? [ ] Yes [ ] No - ARC review required Does the project use the Windows registry? [ ] Yes [ ] No - ARC review required Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ for the registry key? [ ] Yes [ ] No - ARC review required Is the project's stored location HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? [ ] Yes [ ] No - ARC review required 3.1.2 Share and Sharable Does the module include any components that are used or shared by other projects? [ ] Yes [X] No If yes are these components packaged to be shared with the other FOSS? [ ] Yes [ ] No - ARC review required [X] N/A Are these components already in the Solaris WOS? [ ] Yes [X] No - continue with next section (section 3.2) If yes are these newer versions being delivered? [ ] Yes [ ] No - ARC review required If yes are the newer versions replacing the existing versions? [ ] Yes [ ] No - ARC review required 3.2 Exported Libraries Are libraries being delivered by this project? [X] Yes [ ] No - continue with next section (section 3.3) Are 64-bit versions of the libraries being delivered? [X] Yes [ ] No - ARC review required Since these are Java jar libraries, there are no separate 64 bit jars. Are static versions of the libraries being delivered? [ ] Yes - ARC review required [X] No 3.3 Services and the /etc Directory (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) Does the project integrate anything into /etc/init.d or /etc/rc?.d? [ ] Yes - ARC review required [X] No Does the project integrate any new entries into /etc/inittab or /etc/inetd.conf? [ ] Yes - ARC review required [X] No Does the project integrate any private non-public files into /etc/default or /etc/ configuration files? [ ] Yes - ARC review required [X] No Does the service manifests method context grant rights above that of the noaccess user and basic privilege set? [ ] Yes - ARC review required [X] No 3.4 Security 3.4.1 Secure By Default (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for addtional details) Are there any network services provided by this project? [ ] Yes [X] No - continue with the next section (section 3.4.2) Are network services enabled by default? [ ] Yes - ARC review required [ ] No [ ] N/A Are network services automatically enabled by the project during installation? [ ] Yes - ARC review required [ ] No [ ] N/A Are inbound network communications denied by default? [ ] Yes [ ] No - ARC review required [ ] N/A Is inbound data checked to prevent content-based attacks? [ ] Yes [ ] No - ARC review required [ ] N/A Is the outbound receiver authenticated? [ ] Yes [ ] No - ARC review required [ ] N/A Is the receiver authenticated prior to receiving any sensitive outbound communication? [ ] Yes [ ] No - ARC review required [ ] N/A 3.4.2 Authorization (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ for details) Are there any setuid/setgid privileged binaries in the project? [ ] Yes - ARC review required [X] No - continue with next section (section 3.4.3) If yes then are the setuid/setgid privileges handled by the use of roles? [ ] Yes [ ] No - ARC review required 3.4.3 Auditing (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Does this component contain administrative or security enforcing software? [ ] Yes - ARC review required [X] No - continue to next section (section 3.4.4) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Do the components create audit logs detailing what took place including what event took place, who was involved, when the event took place? [ ] Yes - ARC contract and Audit project team review required [ ] No - ARC review required 3.4.4 Authentication (see http://opensolaris.org/os/community/arc/policies/PAM/) Do the components contain any authentication code? [ ] Yes [X] No - continue to next section (section 3.4.5) If yes do the components use PAM (plugable authentication modules) for authentication? [ ] Yes [ ] No - ARC review required If yes is a single PAM session maintained during authentication? [ ] Yes [ ] No - ARC review required If yes are the components sufficiently privileged to allow the requested operations (authentication, password change, process credential manipulation, audit state initialization)? [ ] Yes - briefly describe below [ ] No - ARC review required 3.4.5 Passwords (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) Do any of the components for the project deal with passwords? [X] Yes [ ] No - continue to next section (section 3.4.6) If yes are these passwords entered via the CLI or environment? [ ] Yes - ARC review required [X] No Are passwords stored within the file system for the component? [ ] Yes [X] No - continue to next section (section 3.4.6) If yes are the permissions on the file such to protect exposing the password(s)? [ ] Yes [ ] No - ARC review required 3.4.6 General Security Questions (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) Are there any network protocols used by this project? [X] Yes [ ] No - continue with the next section (section 3.5) Do the components use standard network protocols? [X] Yes [ ] No - ARC review required Do network services for the project make decisions based upon user, host or service identities? [ ] Yes - explain below [ ] No [X] N/A Do the components make use of secret information during authentication and/or authorization? [ ] Yes - explain below [ ] No [X] N/A 3.5 Networking Do the components access the network? [X] Yes [ ] No - continue with the next section (section 3.6) If yes do the components support IPv6? [X] Yes [ ] No - ARC review required 3.6 Core Solaris Components Do the components of this project compete with or duplicate core Solaris components? [ ] Yes - ARC review required [X] No Examples of Core Solaris Components include but are not limited to: Secure By Default Authorizations PAM -- Plugable Authentication Module Privilege PRM -- Process Rights Management -- Privilege Audit xVm -- Virtualization zones / Solaris Containers PRM -- Process Rights Management RBAC -- Role Based Access Control TX / Trusted Extensions ZFS SMF -- Service Management Facility FMA -- Fault Management Architecture SCF -- Smart Card Facility IPsec 4.0 Interfaces (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details) 4.1 Exported Interfaces Interface Name Classification Comments --------------------------- ---------------- --------------------------- SUNWSBLIMCIMClient Uncommitted SBLIMCIMClient Package SBLIMCIMClient API Uncommitted SBLIMCIMClient Classes /usr/share/lib/java/sblimCIMClient.jar Uncommitted SBLIMCIMClient jar /usr/share/lib/java/sblimSLPClient.jar Uncommitted SBLIMCIMClient jar /usr/share/doc/sblim Project Private SBLIMCIMClient doc directory 4.2 Imported Interfaces Interface Name Classification Comments ------------------------ ------------------ -------------------------- /usr/share/lib/java Uncommitted Java Directory java.net.* Committed Java networking libraries Brief Interface Classifications - See Appendix C for definitions Volatile - interfaces are fluid and will follow a rapidly changing community Uncommitted - interfaces are still evolving in the community and might follow the community Committed - interfaces are stable in the community Project Private - no review required, just document in table Contracted (interface modifier) - further review required Appendix A - References 1. Solaris Installation Locations Policy http://opensolaris.org/os/community/arc/policies/install-locations/ 2. /usr/gnu Installation ARC case http://opensolaris.org/os/community/arc/caselog/2007/047/ 3. Secure By Default Policy http://opensolaris.org/os/community/arc/policies/secure-by-default/ 4. Network Install Time Securityuy Policy http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ 5. Adding RBAC Authorizations Policy http://opensolaris.org/os/community/arc/bestpractices/rbac-auths/ 6. When to use setuid -vs- RBAC roles and profiles http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and 7. Building RBAC Rights Profiles http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ 8. Solaris Audit Policy http://opensolaris.org/os/community/arc/policies/audit-policy/ 9. Security questionaire http://opensolaris.org/os/community/arc/bestpractices/security-questions/ 10. Interface Taxonomy http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ 11. Plugable Authentication Modules -- PAM http://opensolaris.org/os/community/arc/policies/PAM/ 12. Reusable Passwords In Command Line Arguments and Environment Variables http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ 13. Storing Reusable Passwords on a Filesystem http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ 14. Release Taxonomy http://opensolaris.org/os/community/arc/policies/release-taxonomy/ 15. Service Management Facility (SMF) usage http://opensolaris.org/os/community/arc/policies/SMF-policy/ Appendix B - Suggested case materials 1. man pages 2. SMF manifests 3. links to contracts Appendix C - Definitions Submitter an agent responsible for creation of an ARC project along with the materials describing that project. Owner the ARC agent responsible for shepherding the case through review and ensuring a formal opinion is written where required. Maintainer an agent responsible for releasing new versions of a program, typically the "main" contributor or person incharge of making Architectural decisions for the project Contributor an agent who make contributions to a project, typically has a voice in making Architectural decisions for the project Monitoring an agent who is only following the changes made in the community and has no Architectural input into the project Volatile* interfaces that are very fluid and typically follow the originating community. Typically these interfaces can not be imported by other projects. Uncommitted* interfaces that are still evolving but will most likely be present from release to release. Committed* interfaces that are stable and with Sun guaranteeing some level of compatibility from release to release. Project Private* interfaces that are exposed only to or intended to be used only by the project being reviewed. These interfaces can not be imported by other projects. Not-An-Interface* components that are not interfaces. Contracted* (interface modifier) - ARC review of Contract required interfaces that do not allow another project to import can be *Note: see http://opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details --Boundary_(ID_QFRVWobqeH4vAb4BwKF52g) Content-type: text/plain; name=SBLIMCIMClient-Arc.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=SBLIMCIMClient-Arc.txt 1. Introduction 1.1. Project/Component Working Name: SBLIMCIMClient 1.2. Name of Document Author/Supplier: Author: Bharath Kumar 1.3. Date of This Document: 06 January 2009 2. Project Summary 2.1 Project Description This project introduces the package of SBLIMCIMClient 1.3.7 into the SFW consolidation. 4. Technical Description: SBLIM is an acronym for Standards Based Linux Instrumentation for Manageability. The goal of this project is to provide a complete Open Source implementation of a WBEM-based management solution for Linux. The SBLIM CIM Client for Java is an implementation of a WBEM services client that includes an IETF RFC 2614 compliant SLP client for CIM service discovery. It is intended to be used by management applications in all areas that leverage CIM technology such as SMI-S, SMASH, etc.The design of the SBLIM Client has put emphasis on low memory consumption and high performance. It offers different options to use the implemented XML parser (SAX, DOM, Pull). Furthermore, a comfortable way to debug interoperability issues by dumping the XML request and response to a log file is provided. 5. Interfaces Exported interfaces ------------------- Interface Name Classification Comments --------------------------- ---------------- --------------------------- SUNWSBLIMCIMClient Uncommitted SBLIMCIMClient Package SBLIMCIMClient API Uncommitted SBLIMCIMClient Classes /usr/share/lib/java/sblimCIMClient.jar Uncommitted SBLIMCIMClient jar /usr/share/lib/java/sblimSLPClient.jar Uncommitted SBLIMCIMClient jar /usr/share/doc/sblim Project Private SBLIMCIMClient doc directory Imported Interfaces ------------------- Interface Name Classification Comments ------------------------ ------------------ -------------------------- /usr/share/lib/java Uncommitted Java Directory java.net.* Committed Java networking libraries 6. Resources and Schedule: 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: SFW 6.5. ARC review type: Automatic 6.6. ARC Exposure: open --Boundary_(ID_QFRVWobqeH4vAb4BwKF52g)-- From Mark.Carlson@sun.com Tue Jan 27 10:12:52 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 n0RICpIL016592 for ; Tue, 27 Jan 2009 10:12:52 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n0RICVI6008316 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 27 Jan 2009 18:12:50 GMT 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 <0KE50070V6LEKN00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Tue, 27 Jan 2009 10:12:50 -0800 (PST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KE500KKQ6LDBKC0@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Tue, 27 Jan 2009 10:12:49 -0800 (PST) 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 n0RICnK6005991 for ; Tue, 27 Jan 2009 18:12: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 <0KE500B013RSDS00@mail-amer.sun.com> (original mail from Mark.Carlson@Sun.COM) for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Tue, 27 Jan 2009 11:12:49 -0700 (MST) Received: from Macintosh-335.local ([129.150.34.235]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KE500EWY6L04R10@mail-amer.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Tue, 27 Jan 2009 11:12:37 -0700 (MST) Date: Tue, 27 Jan 2009 11:12:36 -0700 From: "Mark A. Carlson" Subject: Re: SBLIMCIMClient [LSARC/2009/025 FastTrack timeout 01/21/2009] In-reply-to: <200901142342.n0ENgG3X005324@sac.sfbay.sun.com> Sender: Mark.Carlson@sun.com To: LSARC-ext@sun.com Cc: Bharath.Madakatte@sun.com Message-id: <497F4E94.40607@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: <200901142342.n0ENgG3X005324@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) Status: RO Content-Length: 50 This case was approved in LSARC today. -- mark From James.Walker@sun.com Tue Jan 27 10:41:17 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 n0RIfG4q018120 for ; Tue, 27 Jan 2009 10:41:16 -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 n0RIf2wo002660 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Wed, 28 Jan 2009 02:41:15 +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 <0KE500A0D7WPZD00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.COM); Tue, 27 Jan 2009 10:41:13 -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 <0KE5009ZD7WK9R90@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@Sun.COM); Tue, 27 Jan 2009 10:41:08 -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 n0RIf80b000814 for ; Tue, 27 Jan 2009 18:41:08 +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 <0KE500I0171B5U00@mail-amer.sun.com> (original mail from James.Walker@Sun.COM) for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Tue, 27 Jan 2009 11:41:08 -0700 (MST) Received: from [172.20.25.153] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KE5004CT7W6OVB0@mail-amer.sun.com> for lsarc-ext@Sun.COM (ORCPT lsarc-ext@Sun.COM); Tue, 27 Jan 2009 11:40:54 -0700 (MST) Date: Tue, 27 Jan 2009 12:06:23 -0700 From: Jim Walker Subject: Re: SBLIMCIMClient [LSARC/2009/025 FastTrack timeout 01/21/2009] In-reply-to: <497EF453.3020306@Sun.Com> Sender: James.Walker@sun.com To: Bharath.Madakatte@sun.com Cc: LSARC-ext@sun.com Reply-to: James.Walker@sun.com Message-id: <497F5B2F.6030909@sun.com> Organization: Sun Microsystems, Inc. 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: <497A2D3F.3070503@sun.com> <497EB258.6030702@Sun.Com> <497EB590.4030508@sun.com> <497EF453.3020306@Sun.Com> User-Agent: Thunderbird 2.0.0.14 (X11/20080728) Status: RO Content-Length: 335 Bharath Kumar wrote: > I have modified the ARC docs as per your suggestion to deliver the jars > into '/usr/share/lib/java'. Please find them attached. Thanks. BTW. I don't see any man page in the arc case materials directory. Also, I don't see any class interface description/list which is customary for java cases. Cheers, Jim