From johnf@sac.sfbay.sun.com Tue Nov 25 09:32:45 2008 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 mAPHWi3w025523 for ; Tue, 25 Nov 2008 09:32:45 -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 mAPHWdTg016699; Wed, 26 Nov 2008 01:32:43 +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 <0KAW00M1ZGQISD00@nwk-avmta-1.sfbay.Sun.COM>; Tue, 25 Nov 2008 09:32:42 -0800 (PST) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAW0077MGQGL6B0@nwk-avmta-1.sfbay.Sun.COM>; Tue, 25 Nov 2008 09:32:40 -0800 (PST) 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 mAPHWbUi034253; Tue, 25 Nov 2008 09:32:37 -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 mAPHWZrr025518; Tue, 25 Nov 2008 09:32:35 -0800 (PST) Received: (from johnf@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id mAPHWZUO025514; Tue, 25 Nov 2008 09:32:35 -0800 (PST) Date: Tue, 25 Nov 2008 09:32:35 -0800 (PST) From: John Fischer Subject: LAPACK [LSARC/2008/733 FastTrack timeout 12/04/2008] To: LSARC-ext@sun.com Cc: bruce.rothermal@sun.com Message-id: <200811251732.mAPHWZUO025514@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 12883 Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: LAPACK 1.2. Name of Document Author/Supplier: Author: Bruce Rothermal 1.3 Date of This Document: 25 November, 2008 4. Technical Description 1.0 Project Information 1.1 Name of project/component LAPACK 1.2 Author of document Bruce Rothermal 2.0 Project Summary 2.1 Project Description Port LAPACK Opensource utility to SFW consolidation. Linear Algebra package. LAPACK provides routines for solving systems of simultaneous linear equations, least-squares solutions of linear systems of equations, eigenvalue problems, and singular value problems. The associated matrix factorizations (LU, Cholesky, QR, SVD, Schur, generalized Schur) are also provided, as are related computations such as reordering of the Schur factorizations and estimating condition numbers. Dense and banded matrices are handled, but not general sparse matrices. In all areas, similar functionality is provided for real and complex matrices, in both single and double precision. 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? [ ] Yes [x ] No 2.4 Originating Community 2.4.1 Community Name LAPACK http://www.netlib.org/lapack/ 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 Are static versions of the libraries being delivered? [x ] Yes - ARC review required [ ] No The package as is only generates static libraries. I would have to change the opensource package to make it generate dynamic. 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? [ ] Yes [x ] No - continue to next section (section 3.4.6) If yes are these passwords entered via the CLI or environment? [ ] Yes - ARC review required [ ] No Are passwords stored within the file system for the component? [ ] Yes [ ] 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? [ ] Yes [x ] No - continue with the next section (section 3.5) Do the components use standard network protocols? [ ] Yes [ ] No - ARC review required Do network services for the project make decisions based upon user, host or service identities? [ ] Yes - explain below [ ] No [ ] N/A Do the components make use of secret information during authentication and/or authorization? [ ] Yes - explain below [ ] No [ ] N/A 3.5 Networking Do the components access the network? [ ] Yes [x ] No - continue with the next section (section 3.6) If yes do the components support IPv6? [ ] 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 --------------------------- ------------------- --------------------------- SUNWlapack Volatile lapack libraries for Volatile for sparc and x86, 32b and 64b. 4.2 Imported Interfaces Interface Name Classification Comments --------------------------- -------------------- -------------------------- LAPACK Volatile version 3.2 Package compiles with SunStudio f90 no special compiler needed. Package requires BLAS and intent is to use functionality from Sun Cluster Tools. Which is optimized for Solaris. If not the package contains the opensource BLAS. 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 johnf@sac.sfbay.sun.com Tue Nov 25 09:39:58 2008 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 mAPHdwjx025940 for ; Tue, 25 Nov 2008 09:39:58 -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 mAPHdvWu037251 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 25 Nov 2008 10:39:58 -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 <0KAW00H13H2LD600@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 25 Nov 2008 09:39:57 -0800 (PST) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAW00AWGH2JZE80@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 25 Nov 2008 09:39:55 -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 mAPHdtHc024325; Tue, 25 Nov 2008 09:39:55 -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 mAPHdt30025938; Tue, 25 Nov 2008 09:39:55 -0800 (PST) Received: (from johnf@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id mAPHdtJv025937; Tue, 25 Nov 2008 09:39:55 -0800 (PST) Date: Tue, 25 Nov 2008 09:39:55 -0800 (PST) From: John Fischer Subject: Re: LAPACK [LSARC/2008/733 FastTrack timeout 12/04/2008] To: LSARC-ext@sun.com, johnf@sac.sfbay.sun.com Cc: bruce.rothermal@sun.com Message-id: <200811251739.mAPHdtJv025937@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 13049 LSARC, I am sponsoring this project for Bruce Rothermal from the High Perfomance Computing group in Menlo Park. The case directory contains this proposal. I have set the time out for Thursday, December 4th, 2008 due to the U.S. holiday. This project proposes to integrate the LAPACK (Linear Algebra package) into a Minor release of Solaris. LAPACK provides routines for solving systems of equations. It is written in Fortran and requires no special compiler. The only issue that caused it to fail the check list and require a review is the fact that it will only deliver static libraries. This is how the community delivers its components. Thanks, John 1.0 Project Information 1.1 Name of project/component LAPACK 1.2 Author of document Bruce Rothermal 2.0 Project Summary 2.1 Project Description Port LAPACK Opensource utility to SFW consolidation. Linear Algebra package. LAPACK provides routines for solving systems of simultaneous linear equations, least-squares solutions of linear systems of equations, eigenvalue problems, and singular value problems. The associated matrix factorizations (LU, Cholesky, QR, SVD, Schur, generalized Schur) are also provided, as are related computations such as reordering of the Schur factorizations and estimating condition numbers. Dense and banded matrices are handled, but not general sparse matrices. In all areas, similar functionality is provided for real and complex matrices, in both single and double precision. 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? [ ] Yes [x ] No 2.4 Originating Community 2.4.1 Community Name LAPACK http://www.netlib.org/lapack/ 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 Are static versions of the libraries being delivered? [x ] Yes - ARC review required [ ] No The package as is only generates static libraries. I would have to change the opensource package to make it generate dynamic. 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? [ ] Yes [x ] No - continue to next section (section 3.4.6) If yes are these passwords entered via the CLI or environment? [ ] Yes - ARC review required [ ] No Are passwords stored within the file system for the component? [ ] Yes [ ] 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? [ ] Yes [x ] No - continue with the next section (section 3.5) Do the components use standard network protocols? [ ] Yes [ ] No - ARC review required Do network services for the project make decisions based upon user, host or service identities? [ ] Yes - explain below [ ] No [ ] N/A Do the components make use of secret information during authentication and/or authorization? [ ] Yes - explain below [ ] No [ ] N/A 3.5 Networking Do the components access the network? [ ] Yes [x ] No - continue with the next section (section 3.6) If yes do the components support IPv6? [ ] 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 --------------------------- ------------------- --------------------------- SUNWlapack Volatile lapack libraries for Volatile for sparc and x86, 32b and 64b. 4.2 Imported Interfaces Interface Name Classification Comments --------------------------- -------------------- -------------------------- LAPACK Volatile version 3.2 Package compiles with SunStudio f90 no special compiler needed. Package requires BLAS and intent is to use functionality from Sun Cluster Tools. Which is optimized for Solaris. If not the package contains the opensource BLAS. From John.Fischer@sun.com Tue Nov 25 09:42:22 2008 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 mAPHgMSJ026133 for ; Tue, 25 Nov 2008 09:42:22 -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 mAPHgL0K039605 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 25 Nov 2008 10:42:22 -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 <0KAW00H0JH6LH300@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Tue, 25 Nov 2008 09:42:21 -0800 (PST) Received: from brmea-mail-3.sun.com ([192.18.98.34]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAW00A5VH6KZ290@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Tue, 25 Nov 2008 09:42:20 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mAPHgKoL010239 for ; Tue, 25 Nov 2008 17:42:20 +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 <0KAW00H01FNIC300@mail-amer.sun.com> (original mail from John.Fischer@Sun.COM) for LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Tue, 25 Nov 2008 10:42:20 -0700 (MST) Received: from 129.145.154.66 ([129.145.154.66]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KAW000WGH621870@mail-amer.sun.com> for LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Tue, 25 Nov 2008 10:42:02 -0700 (MST) Date: Tue, 25 Nov 2008 09:42:02 -0800 From: John Fischer Subject: Re: LAPACK [LSARC/2008/733 FastTrack timeout 12/04/2008] In-reply-to: <200811251739.mAPHdtJv025937@sac.sfbay.sun.com> Sender: John.Fischer@sun.com To: LSARC-ext@sun.com Cc: Bruce.Rothermal@sun.com Reply-to: John.Fischer@sun.com Message-id: <1227634920.9050.37.camel@sr1-umpk-16> MIME-version: 1.0 X-Mailer: Ximian Evolution 1.4.6.301 Content-type: text/plain; charset=ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200811251739.mAPHdtJv025937@sac.sfbay.sun.com> Status: RO Content-Length: 13994 All, One other note this project does not set any precedent with regards to the mentioned non-shared library. Thanks, John On Tue, 2008-11-25 at 09:39, John Fischer wrote: > LSARC, > > I am sponsoring this project for Bruce Rothermal from the High Perfomance > Computing group in Menlo Park. The case directory contains this proposal. > I have set the time out for Thursday, December 4th, 2008 due to the > U.S. holiday. > > This project proposes to integrate the LAPACK (Linear Algebra package) into > a Minor release of Solaris. LAPACK provides routines for solving systems of > equations. It is written in Fortran and requires no special compiler. The > only issue that caused it to fail the check list and require a review is > the fact that it will only deliver static libraries. This is how the > community delivers its components. > > Thanks, > > John > > > 1.0 Project Information > 1.1 Name of project/component > > LAPACK > > 1.2 Author of document > > Bruce Rothermal > > 2.0 Project Summary > 2.1 Project Description > > Port LAPACK Opensource utility to SFW consolidation. Linear Algebra package. > > LAPACK provides routines for solving systems of simultaneous > linear equations, least-squares solutions of linear systems of equations, > eigenvalue problems, and singular value problems. The associated matrix > factorizations (LU, Cholesky, QR, SVD, Schur, generalized Schur) are also > provided, as are related computations such as reordering of the Schur > factorizations and estimating condition numbers. Dense and banded matrices > are handled, but not general sparse matrices. In all areas, similar > functionality is provided for real and complex matrices, in both single and > double precision. > > 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? > [ ] Yes > [x ] No > > 2.4 Originating Community > 2.4.1 Community Name > > LAPACK > http://www.netlib.org/lapack/ > > 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 > > Are static versions of the libraries being delivered? > [x ] Yes - ARC review required > [ ] No > > The package as is only generates static libraries. I would have to > change the opensource package to make it generate dynamic. > > 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? > [ ] Yes > [x ] No - continue to next section (section 3.4.6) > > If yes are these passwords entered via the CLI or environment? > [ ] Yes - ARC review required > [ ] No > > Are passwords stored within the file system for the component? > [ ] Yes > [ ] 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? > [ ] Yes > [x ] No - continue with the next section (section 3.5) > > Do the components use standard network protocols? > [ ] Yes > [ ] No - ARC review required > > Do network services for the project make decisions based upon user, host or > service identities? > [ ] Yes - explain below > [ ] No > [ ] N/A > > > Do the components make use of secret information during authentication and/or > authorization? > [ ] Yes - explain below > [ ] No > [ ] N/A > > 3.5 Networking > Do the components access the network? > [ ] Yes > [x ] No - continue with the next section (section 3.6) > > If yes do the components support IPv6? > [ ] 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 > --------------------------- ------------------- --------------------------- > SUNWlapack Volatile > lapack libraries for Volatile > for sparc and x86, 32b > and 64b. > > 4.2 Imported Interfaces > Interface Name Classification Comments > --------------------------- -------------------- -------------------------- > LAPACK Volatile version 3.2 > > Package compiles with SunStudio f90 no special compiler needed. > Package requires BLAS and intent is to use functionality from Sun Cluster > Tools. Which is optimized for Solaris. If not the package contains the > opensource BLAS. > > From carlsonj@phorcys.east.sun.com Tue Nov 25 09:50:26 2008 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 mAPHoQ3j026596 for ; Tue, 25 Nov 2008 09:50:26 -0800 (PST) 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 mAPHoPls010351; Tue, 25 Nov 2008 09:50:25 -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 <0KAW00I51HK0K100@brm-avmta-1.central.sun.com>; Tue, 25 Nov 2008 10:50:24 -0700 (MST) Received: from phorcys.east.sun.com ([129.148.174.143]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAW007HIHJZ2Z90@brm-avmta-1.central.sun.com>; Tue, 25 Nov 2008 10:50:23 -0700 (MST) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id mAPHoMCP021438; Tue, 25 Nov 2008 12:50:22 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id mAPHoMRG021435; Tue, 25 Nov 2008 12:50:22 -0500 (EST) Date: Tue, 25 Nov 2008 12:50:22 -0500 From: James Carlson Subject: Re: LAPACK [LSARC/2008/733 FastTrack timeout 12/04/2008] In-reply-to: <200811251739.mAPHdtJv025937@sac.sfbay.sun.com> To: John Fischer Cc: LSARC-ext@sun.com, Bruce.Rothermal@sun.com Message-id: <18732.15070.124749.955874@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200811251739.mAPHdtJv025937@sac.sfbay.sun.com> Status: RO Content-Length: 1357 John Fischer writes: > This project proposes to integrate the LAPACK (Linear Algebra package) into > a Minor release of Solaris. LAPACK provides routines for solving systems of > equations. It is written in Fortran and requires no special compiler. The > only issue that caused it to fail the check list and require a review is > the fact that it will only deliver static libraries. This is how the > community delivers its components. [...] > Will the project team work with the upstream community to resolve > architectural issues of interest to Sun? > [x ] Yes > [ ] No - briefly explain [...] > Are static versions of the libraries being delivered? > [x ] Yes - ARC review required > [ ] No > > The package as is only generates static libraries. I would have to > change the opensource package to make it generate dynamic. Given that avoiding static libraries _is_ an issue of architectural interest to Sun, could you explain how difficult it might be to generate normal dynamic libraries? Is it significantly harder than at least changing "ar c" to "ld -r"? -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Bruce.Rothermal@sun.com Tue Nov 25 10:01:57 2008 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 mAPI1u0s027624 for ; Tue, 25 Nov 2008 10:01:57 -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 mAPI1qfl016720 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 25 Nov 2008 18:01:56 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 <0KAW00J1BI36QX00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 25 Nov 2008 11:01:54 -0700 (MST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAW007KNI352ZA0@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 25 Nov 2008 11:01:54 -0700 (MST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mAPI1rs2005206 for ; Tue, 25 Nov 2008 10:01:53 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KAW00401HNPEO00@fe-sfbay-09.sun.com> (original mail from Bruce.Rothermal@Sun.COM) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue, 25 Nov 2008 10:01:53 -0800 (PST) Received: from [192.168.1.101] ([129.150.20.226]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KAW006A4I33SQB0@fe-sfbay-09.sun.com>; Tue, 25 Nov 2008 10:01:52 -0800 (PST) Date: Tue, 25 Nov 2008 11:01:50 -0700 From: Bruce Rothermal Subject: Re: LAPACK [LSARC/2008/733 FastTrack timeout 12/04/2008] In-reply-to: <18732.15070.124749.955874@gargle.gargle.HOWL> Sender: Bruce.Rothermal@sun.com To: James Carlson Cc: John Fischer , LSARC-ext@sun.com Message-id: MIME-version: 1.0 X-Mailer: Apple Mail (2.929.2) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200811251739.mAPHdtJv025937@sac.sfbay.sun.com> <18732.15070.124749.955874@gargle.gargle.HOWL> Status: RO Content-Length: 1646 I'm going to look into how difficult the change would be and I'm also requesting input from the LAPACK group to find out the reason for it not be so by default. Bruce On Nov 25, 2008, at 10:50 AM, James Carlson wrote: > John Fischer writes: >> This project proposes to integrate the LAPACK (Linear Algebra >> package) into >> a Minor release of Solaris. LAPACK provides routines for solving >> systems of >> equations. It is written in Fortran and requires no special >> compiler. The >> only issue that caused it to fail the check list and require a >> review is >> the fact that it will only deliver static libraries. This is how the >> community delivers its components. > [...] >> Will the project team work with the upstream community to >> resolve >> architectural issues of interest to Sun? >> [x ] Yes >> [ ] No - briefly explain > [...] >> Are static versions of the libraries being delivered? >> [x ] Yes - ARC review required >> [ ] No >> >> The package as is only generates static libraries. I would >> have to >> change the opensource package to make it generate dynamic. > > Given that avoiding static libraries _is_ an issue of architectural > interest to Sun, could you explain how difficult it might be to > generate normal dynamic libraries? Is it significantly harder than at > least changing "ar c" to "ld -r"? > > -- > James Carlson, Solaris Networking > > Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 > 2084 > MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 > 1677 From Terry.Dontje@sun.com Wed Nov 26 09:09:46 2008 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 mAQH9kPQ008012 for ; Wed, 26 Nov 2008 09:09:46 -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 mAQH9ggx030789 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 26 Nov 2008 10:09:46 -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 <0KAY00E03AC8LA00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Wed, 26 Nov 2008 09:09:44 -0800 (PST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAY008F6AC7LA80@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Wed, 26 Nov 2008 09:09:43 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mAQH9hKj018305 for ; Wed, 26 Nov 2008 17:09: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 <0KAY00F019RT5Y00@mail-amer.sun.com> (original mail from Terry.Dontje@Sun.COM) for LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Wed, 26 Nov 2008 10:09:43 -0700 (MST) Received: from tddmobile1.local ([129.150.64.16]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KAY004XIABSZ930@mail-amer.sun.com>; Wed, 26 Nov 2008 10:09:30 -0700 (MST) Date: Wed, 26 Nov 2008 12:09:27 -0500 From: Terry Dontje Subject: Re: LAPACK [LSARC/2008/733 FastTrack timeout 12/04/2008] In-reply-to: <200811251732.mAPHWZUO025514@sac.sfbay.sun.com> Sender: Terry.Dontje@sun.com To: John Fischer Cc: LSARC-ext@sun.com, Bruce.Rothermal@sun.com, Gregory Tarsy , Rebecca Arney Message-id: <492D82C7.7080409@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: <200811251732.mAPHWZUO025514@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914) Status: RO Content-Length: 14381 On behalf of the Perflib I'd like to derail or at least suspend the timeout for this fast-track. The Perflib group already delivers LAPACK as a part of their product which was ARCd as a part of cases LSARC/1995/406 and 1999/489. I worry that the delivery of the below fast-track might have some interfering consequences for our customers. I believe the Perflib group and the group submitting this fast-track need to resolve the issue of what our customers see when both versions of LAPACK are installed. There are actually a few similar instances of this (SCALAPACK is another) that could really benefit the resolutions of dual packages delivering the same API at different levels of optimization and support. --td John Fischer wrote: > Template Version: @(#)sac_nextcase %I% %G% SMI > This information is Copyright 2008 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > LAPACK > 1.2. Name of Document Author/Supplier: > Author: Bruce Rothermal > 1.3 Date of This Document: > 25 November, 2008 > 4. Technical Description > 1.0 Project Information > 1.1 Name of project/component > > LAPACK > > 1.2 Author of document > > Bruce Rothermal > > 2.0 Project Summary > 2.1 Project Description > > Port LAPACK Opensource utility to SFW consolidation. Linear Algebra package. > > LAPACK provides routines for solving systems of simultaneous > linear equations, least-squares solutions of linear systems of equations, > eigenvalue problems, and singular value problems. The associated matrix > factorizations (LU, Cholesky, QR, SVD, Schur, generalized Schur) are also > provided, as are related computations such as reordering of the Schur > factorizations and estimating condition numbers. Dense and banded matrices > are handled, but not general sparse matrices. In all areas, similar > functionality is provided for real and complex matrices, in both single and > double precision. > > 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? > [ ] Yes > [x ] No > > 2.4 Originating Community > 2.4.1 Community Name > > LAPACK > http://www.netlib.org/lapack/ > > 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 > > Are static versions of the libraries being delivered? > [x ] Yes - ARC review required > [ ] No > > The package as is only generates static libraries. I would have to > change the opensource package to make it generate dynamic. > > 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? > [ ] Yes > [x ] No - continue to next section (section 3.4.6) > > If yes are these passwords entered via the CLI or environment? > [ ] Yes - ARC review required > [ ] No > > Are passwords stored within the file system for the component? > [ ] Yes > [ ] 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? > [ ] Yes > [x ] No - continue with the next section (section 3.5) > > Do the components use standard network protocols? > [ ] Yes > [ ] No - ARC review required > > Do network services for the project make decisions based upon user, host or > service identities? > [ ] Yes - explain below > [ ] No > [ ] N/A > > > Do the components make use of secret information during authentication and/or > authorization? > [ ] Yes - explain below > [ ] No > [ ] N/A > > 3.5 Networking > Do the components access the network? > [ ] Yes > [x ] No - continue with the next section (section 3.6) > > If yes do the components support IPv6? > [ ] 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 > --------------------------- ------------------- --------------------------- > SUNWlapack Volatile > lapack libraries for Volatile > for sparc and x86, 32b > and 64b. > > 4.2 Imported Interfaces > Interface Name Classification Comments > --------------------------- -------------------- -------------------------- > LAPACK Volatile version 3.2 > > Package compiles with SunStudio f90 no special compiler needed. > Package requires BLAS and intent is to use functionality from Sun Cluster > Tools. Which is optimized for Solaris. If not the package contains the > opensource BLAS. > > > > 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 John.Fischer@sun.com Wed Nov 26 09:27:36 2008 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 mAQHRa6A021009 for ; Wed, 26 Nov 2008 09:27:36 -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 mAQHRZ46046390 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 26 Nov 2008 10:27:36 -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 <0KAY0091PB5Z8B00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Wed, 26 Nov 2008 09:27:35 -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 <0KAY00G79B5XN1A0@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Wed, 26 Nov 2008 09:27:34 -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 mAQHRXm1003985 for ; Wed, 26 Nov 2008 17:27:33 +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 <0KAY00F019RT5Y00@mail-amer.sun.com> (original mail from John.Fischer@Sun.COM) for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Wed, 26 Nov 2008 10:27:33 -0700 (MST) Received: from 129.145.154.66 ([129.145.154.66]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KAY00HXBB5JAA70@mail-amer.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Wed, 26 Nov 2008 10:27:20 -0700 (MST) Date: Wed, 26 Nov 2008 09:27:19 -0800 From: John Fischer Subject: Re: LAPACK [LSARC/2008/733 FastTrack timeout 12/04/2008] In-reply-to: <492D82C7.7080409@sun.com> Sender: John.Fischer@sun.com To: Terry Dontje Cc: LSARC-ext@sun.com, Bruce.Rothermal@sun.com, Gregory Tarsy , Rebecca Arney Reply-to: John.Fischer@sun.com Message-id: <1227720438.27877.15.camel@sr1-umpk-16> MIME-version: 1.0 X-Mailer: Ximian Evolution 1.4.6.301 Content-type: text/plain; charset=ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200811251732.mAPHWZUO025514@sac.sfbay.sun.com> <492D82C7.7080409@sun.com> Status: RO Content-Length: 15369 Terry, I have placed the project in waiting need spec. Once the issue is resolved if needed we can restart the timer. Thanks, John On Wed, 2008-11-26 at 09:09, Terry Dontje wrote: > On behalf of the Perflib I'd like to derail or at least suspend the > timeout for this fast-track. The Perflib group already delivers LAPACK > as a part of their product which was ARCd as a part of cases > LSARC/1995/406 and 1999/489. I worry that the delivery of the below > fast-track might have some interfering consequences for our customers. > I believe the Perflib group and the group submitting this fast-track > need to resolve the issue of what our customers see when both versions > of LAPACK are installed. > > There are actually a few similar instances of this (SCALAPACK is > another) that could really benefit the resolutions of dual packages > delivering the same API at different levels of optimization and support. > > --td > > John Fischer wrote: > > Template Version: @(#)sac_nextcase %I% %G% SMI > > This information is Copyright 2008 Sun Microsystems > > 1. Introduction > > 1.1. Project/Component Working Name: > > LAPACK > > 1.2. Name of Document Author/Supplier: > > Author: Bruce Rothermal > > 1.3 Date of This Document: > > 25 November, 2008 > > 4. Technical Description > > 1.0 Project Information > > 1.1 Name of project/component > > > > LAPACK > > > > 1.2 Author of document > > > > Bruce Rothermal > > > > 2.0 Project Summary > > 2.1 Project Description > > > > Port LAPACK Opensource utility to SFW consolidation. Linear Algebra package. > > > > LAPACK provides routines for solving systems of simultaneous > > linear equations, least-squares solutions of linear systems of equations, > > eigenvalue problems, and singular value problems. The associated matrix > > factorizations (LU, Cholesky, QR, SVD, Schur, generalized Schur) are also > > provided, as are related computations such as reordering of the Schur > > factorizations and estimating condition numbers. Dense and banded matrices > > are handled, but not general sparse matrices. In all areas, similar > > functionality is provided for real and complex matrices, in both single and > > double precision. > > > > 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? > > [ ] Yes > > [x ] No > > > > 2.4 Originating Community > > 2.4.1 Community Name > > > > LAPACK > > http://www.netlib.org/lapack/ > > > > 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 > > > > Are static versions of the libraries being delivered? > > [x ] Yes - ARC review required > > [ ] No > > > > The package as is only generates static libraries. I would have to > > change the opensource package to make it generate dynamic. > > > > 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? > > [ ] Yes > > [x ] No - continue to next section (section 3.4.6) > > > > If yes are these passwords entered via the CLI or environment? > > [ ] Yes - ARC review required > > [ ] No > > > > Are passwords stored within the file system for the component? > > [ ] Yes > > [ ] 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? > > [ ] Yes > > [x ] No - continue with the next section (section 3.5) > > > > Do the components use standard network protocols? > > [ ] Yes > > [ ] No - ARC review required > > > > Do network services for the project make decisions based upon user, host or > > service identities? > > [ ] Yes - explain below > > [ ] No > > [ ] N/A > > > > > > Do the components make use of secret information during authentication and/or > > authorization? > > [ ] Yes - explain below > > [ ] No > > [ ] N/A > > > > 3.5 Networking > > Do the components access the network? > > [ ] Yes > > [x ] No - continue with the next section (section 3.6) > > > > If yes do the components support IPv6? > > [ ] 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 > > --------------------------- ------------------- --------------------------- > > SUNWlapack Volatile > > lapack libraries for Volatile > > for sparc and x86, 32b > > and 64b. > > > > 4.2 Imported Interfaces > > Interface Name Classification Comments > > --------------------------- -------------------- -------------------------- > > LAPACK Volatile version 3.2 > > > > Package compiles with SunStudio f90 no special compiler needed. > > Package requires BLAS and intent is to use functionality from Sun Cluster > > Tools. Which is optimized for Solaris. If not the package contains the > > opensource BLAS. > > > > > > > > 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 Bruce.Rothermal@sun.com Mon Dec 1 09:02:48 2008 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 mB1H2lNx018924 for ; Mon, 1 Dec 2008 09:02:48 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mB1H2lch005154 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 1 Dec 2008 10:02:47 -0700 (MST) 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 <0KB700E0VJCNNN00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 01 Dec 2008 10:02:47 -0700 (MST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KB7006UWJCK9GD0@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 01 Dec 2008 10:02:44 -0700 (MST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mB1H2i42013716 for ; Mon, 01 Dec 2008 09:02:44 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KB700L01INU3000@fe-sfbay-09.sun.com> (original mail from Bruce.Rothermal@Sun.COM) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 01 Dec 2008 09:02:44 -0800 (PST) Received: from [192.168.1.101] ([75.71.129.47]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KB700JE4JCENX80@fe-sfbay-09.sun.com>; Mon, 01 Dec 2008 09:02:39 -0800 (PST) Date: Mon, 01 Dec 2008 10:02:38 -0700 From: Bruce Rothermal Subject: Re: LAPACK [LSARC/2008/733 FastTrack timeout 12/04/2008] In-reply-to: <18732.15070.124749.955874@gargle.gargle.HOWL> Sender: Bruce.Rothermal@sun.com To: James Carlson Cc: John Fischer , LSARC-ext@sun.com Message-id: <0CDBD1AA-F508-40BA-8CE3-EBE555856C13@Sun.COM> MIME-version: 1.0 X-Mailer: Apple Mail (2.929.2) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200811251739.mAPHdtJv025937@sac.sfbay.sun.com> <18732.15070.124749.955874@gargle.gargle.HOWL> Status: RO Content-Length: 2415 Regarding the static libraries. From LAPACK group: "Because trying to support every shared library kind and method of generation is far outside our scope. Yes, we know of libtool. We also have many users on AIX, which uses XCOFF and where libtool falls flat. CMake is an option, but it takes more work than anyone can devote right now. Plus, to build a shared, ATLAS-tuned version, you need the shared objects in an ar archive. Yet another variation. wheee... Check the build scripts for GNU/Linux distributions for building ELF-based shared libraries. In particular, Debian GNU/Linux does a good job. Jason" Also this package will not be integrated to any of the Solaris consolidations. It will be integrated to the "Developer Tools" consolidation. This is a special process be developed for integrating this type of tool to OpenSolaris. It is following the same process used to integrate SunStudio to OpenSolaris. Bruce On Nov 25, 2008, at 10:50 AM, James Carlson wrote: > John Fischer writes: >> This project proposes to integrate the LAPACK (Linear Algebra >> package) into >> a Minor release of Solaris. LAPACK provides routines for solving >> systems of >> equations. It is written in Fortran and requires no special >> compiler. The >> only issue that caused it to fail the check list and require a >> review is >> the fact that it will only deliver static libraries. This is how the >> community delivers its components. > [...] >> Will the project team work with the upstream community to >> resolve >> architectural issues of interest to Sun? >> [x ] Yes >> [ ] No - briefly explain > [...] >> Are static versions of the libraries being delivered? >> [x ] Yes - ARC review required >> [ ] No >> >> The package as is only generates static libraries. I would >> have to >> change the opensource package to make it generate dynamic. > > Given that avoiding static libraries _is_ an issue of architectural > interest to Sun, could you explain how difficult it might be to > generate normal dynamic libraries? Is it significantly harder than at > least changing "ar c" to "ld -r"? > > -- > James Carlson, Solaris Networking > > Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 > 2084 > MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 > 1677 From Bruce.Rothermal@sun.com Mon Dec 1 09:10:34 2008 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 mB1HAXsu019079 for ; Mon, 1 Dec 2008 09:10:34 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id mB1HAShE024829 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 2 Dec 2008 01:10:32 +0800 (SGT) 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 <0KB700F1JJPJG200@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Mon, 01 Dec 2008 10:10:31 -0700 (MST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KB700FQPJPI0700@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Mon, 01 Dec 2008 10:10:30 -0700 (MST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mB1HAUSl000725 for ; Mon, 01 Dec 2008 09:10:30 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KB700301GHQZ700@fe-sfbay-09.sun.com> (original mail from Bruce.Rothermal@Sun.COM) for LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Mon, 01 Dec 2008 09:10:30 -0800 (PST) Received: from [192.168.1.101] ([75.71.129.47]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KB700JGHJP2NXC0@fe-sfbay-09.sun.com>; Mon, 01 Dec 2008 09:10:15 -0800 (PST) Date: Mon, 01 Dec 2008 10:10:14 -0700 From: Bruce Rothermal Subject: Re: LAPACK [LSARC/2008/733 FastTrack timeout 12/04/2008] In-reply-to: <492D82C7.7080409@sun.com> Sender: Bruce.Rothermal@sun.com To: Terry Dontje Cc: John Fischer , LSARC-ext@sun.com, Gregory Tarsy , Rebecca Arney , jasmine Ocegueda Message-id: MIME-version: 1.0 X-Mailer: Apple Mail (2.929.2) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200811251732.mAPHWZUO025514@sac.sfbay.sun.com> <492D82C7.7080409@sun.com> Status: RO Content-Length: 14852 Hi Terry The process to integrate these (Blas, LAPACK and ScaLAPACK) has already been approved by Rebecca Arney and Jasmine Ocegueda following the same process used by Sun Studio to be integrated to OpenSolaris. So please check with Rebecca and remove your objection. Thank you Bruce On Nov 26, 2008, at 10:09 AM, Terry Dontje wrote: > On behalf of the Perflib I'd like to derail or at least suspend the > timeout for this fast-track. The Perflib group already delivers > LAPACK as a part of their product which was ARCd as a part of cases > LSARC/1995/406 and 1999/489. I worry that the delivery of the below > fast-track might have some interfering consequences for our > customers. I believe the Perflib group and the group submitting > this fast-track need to resolve the issue of what our customers see > when both versions of LAPACK are installed. > There are actually a few similar instances of this (SCALAPACK is > another) that could really benefit the resolutions of dual packages > delivering the same API at different levels of optimization and > support. > > --td > > John Fischer wrote: >> Template Version: @(#)sac_nextcase %I% %G% SMI >> This information is Copyright 2008 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> LAPACK >> 1.2. Name of Document Author/Supplier: >> Author: Bruce Rothermal >> 1.3 Date of This Document: >> 25 November, 2008 >> 4. Technical Description >> 1.0 Project Information >> 1.1 Name of project/component >> >> LAPACK >> >> 1.2 Author of document >> >> Bruce Rothermal >> >> 2.0 Project Summary >> 2.1 Project Description >> >> Port LAPACK Opensource utility to SFW consolidation. Linear >> Algebra package. >> LAPACK provides routines for solving systems of simultaneous >> linear equations, least-squares solutions of linear systems of >> equations, eigenvalue problems, and singular value problems. The >> associated matrix >> factorizations (LU, Cholesky, QR, SVD, Schur, generalized Schur) >> are also provided, as are related computations such as reordering >> of the Schur factorizations and estimating condition numbers. >> Dense and banded matrices are handled, but not general sparse >> matrices. In all areas, similar functionality is provided for >> real and complex matrices, in both single and double precision. >> >> 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? >> [ ] Yes >> [x ] No >> >> 2.4 Originating Community >> 2.4.1 Community Name >> LAPACK >> http://www.netlib.org/lapack/ >> >> 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 >> Are static versions of the libraries being delivered? >> [x ] Yes - ARC review required >> [ ] No The package as is only generates static >> libraries. I would have to change the opensource package to >> make it generate dynamic. >> >> 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? >> [ ] Yes >> [x ] No - continue to next section (section 3.4.6) >> If yes are these passwords entered via the CLI or >> environment? >> [ ] Yes - ARC review required >> [ ] No >> Are passwords stored within the file system for the >> component? >> [ ] Yes >> [ ] 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? >> [ ] Yes >> [x ] No - continue with the next section (section 3.5) >> Do the components use standard network protocols? >> [ ] Yes >> [ ] No - ARC review required >> Do network services for the project make decisions based >> upon user, host or service identities? >> [ ] Yes - explain below >> [ ] No >> [ ] N/A >> >> Do the components make use of secret information during >> authentication and/or >> authorization? >> [ ] Yes - explain below >> [ ] No >> [ ] N/A >> 3.5 Networking >> Do the components access the network? >> [ ] Yes >> [x ] No - continue with the next section (section 3.6) >> If yes do the components support IPv6? >> [ ] 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 >> --------------------------- ------------------- >> --------------------------- >> SUNWlapack Volatile >> lapack libraries for Volatile >> for sparc and x86, 32b >> and 64b. 4.2 Imported Interfaces >> Interface Name Classification Comments >> --------------------------- -------------------- >> -------------------------- >> LAPACK Volatile version 3.2 >> >> Package compiles with SunStudio f90 no special compiler needed. >> Package requires BLAS and intent is to use functionality from >> Sun Cluster >> Tools. Which is optimized for Solaris. If not the package >> contains the opensource BLAS. >> >> >> >> 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 Rebecca.Arney@SUN.COM Mon Dec 1 09:53:06 2008 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 mB1Hr63F020009 for ; Mon, 1 Dec 2008 09:53:06 -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 mB1Hr4eI024688 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 1 Dec 2008 09:53:06 -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 <0KB700DANLOHCC00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 01 Dec 2008 09:53:05 -0800 (PST) Received: from brmea-mail-3.sun.com ([192.18.98.34]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KB7003K2LOAE2A0@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 01 Dec 2008 09:52:59 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mB1HqwhO003492 for ; Mon, 01 Dec 2008 17:52:58 +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 <0KB700401KFKG100@mail-amer.sun.com> (original mail from Rebecca.Arney@Sun.COM) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 01 Dec 2008 10:52:58 -0700 (MST) Received: from [129.146.73.151] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KB700GFLLNY55B0@mail-amer.sun.com>; Mon, 01 Dec 2008 10:52:47 -0700 (MST) Date: Mon, 01 Dec 2008 09:52:45 -0800 From: Rebecca Arney Subject: Re: LAPACK [LSARC/2008/733 FastTrack timeout 12/04/2008] In-reply-to: Sender: Rebecca.Arney@SUN.COM To: Bruce Rothermal Cc: Terry Dontje , John Fischer , LSARC-ext@SUN.COM, Gregory Tarsy , jasmine Ocegueda Message-id: <483325C2-643A-4AD5-80D5-A2717A499DF4@Sun.COM> MIME-version: 1.0 X-Mailer: Apple Mail (2.753.1) Content-type: text/plain; format=flowed; delsp=yes; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200811251732.mAPHWZUO025514@sac.sfbay.sun.com> <492D82C7.7080409@sun.com> Status: RO Content-Length: 16406 Bruce, Our discussion was only about ScaLAPACK, not Blas and LAPACK. The issue of having untuned versions of LAPACK looking like perhaps recommended libraries for OpenSolaris is a much bigger issue than untuned ScaLAPACK (which currently is not in Studio but will be). LAPACK is in Studio (and is a highly tuned version which is what is expected for Sun systems, for both the customer/user and Sun benefit). This is the original issue discussed (not the "how to port issue"), and we have not changed our view that this all requires additional direction/information be provided to users/downloaders instructing them on just what they are getting and what other alternatives exist or are recommended (and why they may be better). The lack of such info may mean people simply see LAPACK and download it , without knowing to utilize these same highly tuned libraries that are part of the Sun Studio package in OpenSolaris (Perflib being the component that provides BLAS, LAPACK, and in the next release also ScaLAPACK). Rebecca On Dec 1, 2008, at 9:10 AM, Bruce Rothermal wrote: > Hi Terry > > The process to integrate these (Blas, LAPACK and ScaLAPACK) has > already been approved by Rebecca Arney and Jasmine Ocegueda > following the same process used by Sun Studio to be integrated to > OpenSolaris. > > So please check with Rebecca and remove your objection. > > Thank you > > Bruce > > On Nov 26, 2008, at 10:09 AM, Terry Dontje wrote: > >> On behalf of the Perflib I'd like to derail or at least suspend >> the timeout for this fast-track. The Perflib group already >> delivers LAPACK as a part of their product which was ARCd as a >> part of cases LSARC/1995/406 and 1999/489. I worry that the >> delivery of the below fast-track might have some interfering >> consequences for our customers. I believe the Perflib group and >> the group submitting this fast-track need to resolve the issue of >> what our customers see when both versions of LAPACK are installed. >> There are actually a few similar instances of this (SCALAPACK is >> another) that could really benefit the resolutions of dual >> packages delivering the same API at different levels of >> optimization and support. >> >> --td >> >> John Fischer wrote: >>> Template Version: @(#)sac_nextcase %I% %G% SMI >>> This information is Copyright 2008 Sun Microsystems >>> 1. Introduction >>> 1.1. Project/Component Working Name: >>> LAPACK >>> 1.2. Name of Document Author/Supplier: >>> Author: Bruce Rothermal >>> 1.3 Date of This Document: >>> 25 November, 2008 >>> 4. Technical Description >>> 1.0 Project Information >>> 1.1 Name of project/component >>> >>> LAPACK >>> >>> 1.2 Author of document >>> >>> Bruce Rothermal >>> >>> 2.0 Project Summary >>> 2.1 Project Description >>> >>> Port LAPACK Opensource utility to SFW consolidation. Linear >>> Algebra package. >>> LAPACK provides routines for solving systems of simultaneous >>> linear equations, least-squares solutions of linear systems of >>> equations, eigenvalue problems, and singular value problems. >>> The associated matrix >>> factorizations (LU, Cholesky, QR, SVD, Schur, generalized Schur) >>> are also provided, as are related computations such as >>> reordering of the Schur factorizations and estimating condition >>> numbers. Dense and banded matrices are handled, but not general >>> sparse matrices. In all areas, similar functionality is >>> provided for real and complex matrices, in both single and >>> double precision. >>> >>> 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? >>> [ ] Yes >>> [x ] No >>> >>> 2.4 Originating Community >>> 2.4.1 Community Name >>> LAPACK >>> http://www.netlib.org/lapack/ >>> >>> 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 >> drive>:\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 >>> Are static versions of the libraries being delivered? >>> [x ] Yes - ARC review required >>> [ ] No The package as is only generates static >>> libraries. I would have to change the opensource package to >>> make it generate dynamic. >>> >>> 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? >>> [ ] Yes >>> [x ] No - continue to next section (section 3.4.6) >>> If yes are these passwords entered via the CLI or >>> environment? >>> [ ] Yes - ARC review required >>> [ ] No >>> Are passwords stored within the file system for the >>> component? >>> [ ] Yes >>> [ ] 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? >>> [ ] Yes >>> [x ] No - continue with the next section (section 3.5) >>> Do the components use standard network protocols? >>> [ ] Yes >>> [ ] No - ARC review required >>> Do network services for the project make decisions >>> based upon user, host or service identities? >>> [ ] Yes - explain below >>> [ ] No >>> [ ] N/A >>> >>> Do the components make use of secret information during >>> authentication and/or >>> authorization? >>> [ ] Yes - explain below >>> [ ] No >>> [ ] N/A >>> 3.5 Networking >>> Do the components access the network? >>> [ ] Yes >>> [x ] No - continue with the next section (section 3.6) >>> If yes do the components support IPv6? >>> [ ] 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 >>> --------------------------- ------------------- >>> --------------------------- >>> SUNWlapack Volatile >>> lapack libraries for Volatile >>> for sparc and x86, 32b >>> and 64b. 4.2 Imported Interfaces >>> Interface Name Classification Comments >>> --------------------------- -------------------- >>> -------------------------- >>> LAPACK Volatile version 3.2 >>> >>> Package compiles with SunStudio f90 no special compiler needed. >>> Package requires BLAS and intent is to use functionality from >>> Sun Cluster >>> Tools. Which is optimized for Solaris. If not the package >>> contains the opensource BLAS. >>> >>> >>> >>> 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 Gregory.Tarsy@sun.com Mon Dec 1 10:22:30 2008 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 mB1IMTnY021459 for ; Mon, 1 Dec 2008 10:22:30 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mB1IMOi2028657 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 1 Dec 2008 18:22:28 GMT 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 <0KB700J1FN1DTS00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Mon, 01 Dec 2008 10:22:25 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KB700ELMN1CIVD0@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Mon, 01 Dec 2008 10:22:25 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mB1IMO0k011957 for ; Mon, 01 Dec 2008 10:22:24 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KB700301MMTUU00@fe-sfbay-09.sun.com> (original mail from Gregory.Tarsy@Sun.COM) for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Mon, 01 Dec 2008 10:22:24 -0800 (PST) Received: from [129.150.19.218] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KB700EFYN15T5F0@fe-sfbay-09.sun.com>; Mon, 01 Dec 2008 10:22:18 -0800 (PST) Date: Mon, 01 Dec 2008 10:22:20 -0800 From: Gregory Tarsy Subject: Re: LAPACK [LSARC/2008/733 FastTrack timeout 12/04/2008] In-reply-to: <483325C2-643A-4AD5-80D5-A2717A499DF4@Sun.COM> Sender: Gregory.Tarsy@sun.com To: Rebecca Arney Cc: Bruce Rothermal , Terry Dontje , John Fischer , LSARC-ext@sun.com, jasmine Ocegueda Message-id: <49342B5C.4050303@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: <200811251732.mAPHWZUO025514@sac.sfbay.sun.com> <492D82C7.7080409@sun.com> <483325C2-643A-4AD5-80D5-A2717A499DF4@Sun.COM> User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) Status: RO Content-Length: 17623 From my point of view as well the discussion was about Scalapack and also it was agreed that the case of other libraries, like LAPACK, for which there are tuned versions from Sun, would be resolved with further discussion. If Sun Studio is also in Opensolaris, as is an ongoing consideration, then there would be two versions of LAPACK in Opensolaris (as well as BLAS, PBLAS, BLACS and Scalapack). I think we need to figure this out together. Probably better to do this in a prior meeting rather than in LSARC. Gregory Rebecca Arney wrote: > Bruce, > > Our discussion was only about ScaLAPACK, not Blas and LAPACK. The > issue of having untuned versions of LAPACK looking like perhaps > recommended libraries for OpenSolaris is a much bigger issue than > untuned ScaLAPACK (which currently is not in Studio but will be). > LAPACK is in Studio (and is a highly tuned version which is what is > expected for Sun systems, for both the customer/user and Sun benefit). > This is the original issue discussed (not the "how to port issue"), and > we have not changed our view that this all requires additional > direction/information be provided to users/downloaders instructing them > on just what they are getting and what other alternatives exist or are > recommended (and why they may be better). The lack of such info may > mean people simply see LAPACK and download it , without knowing to > utilize these same highly tuned libraries that are part of the Sun > Studio package in OpenSolaris (Perflib being the component that provides > BLAS, LAPACK, and in the next release also ScaLAPACK). > > Rebecca > > > On Dec 1, 2008, at 9:10 AM, Bruce Rothermal wrote: > >> Hi Terry >> >> The process to integrate these (Blas, LAPACK and ScaLAPACK) has >> already been approved by Rebecca Arney and Jasmine Ocegueda following >> the same process used by Sun Studio to be integrated to OpenSolaris. >> >> So please check with Rebecca and remove your objection. >> >> Thank you >> >> Bruce >> >> On Nov 26, 2008, at 10:09 AM, Terry Dontje wrote: >> >>> On behalf of the Perflib I'd like to derail or at least suspend the >>> timeout for this fast-track. The Perflib group already delivers >>> LAPACK as a part of their product which was ARCd as a part of cases >>> LSARC/1995/406 and 1999/489. I worry that the delivery of the below >>> fast-track might have some interfering consequences for our >>> customers. I believe the Perflib group and the group submitting this >>> fast-track need to resolve the issue of what our customers see when >>> both versions of LAPACK are installed. >>> There are actually a few similar instances of this (SCALAPACK is >>> another) that could really benefit the resolutions of dual packages >>> delivering the same API at different levels of optimization and support. >>> >>> --td >>> >>> John Fischer wrote: >>>> Template Version: @(#)sac_nextcase %I% %G% SMI >>>> This information is Copyright 2008 Sun Microsystems >>>> 1. Introduction >>>> 1.1. Project/Component Working Name: >>>> LAPACK >>>> 1.2. Name of Document Author/Supplier: >>>> Author: Bruce Rothermal >>>> 1.3 Date of This Document: >>>> 25 November, 2008 >>>> 4. Technical Description >>>> 1.0 Project Information >>>> 1.1 Name of project/component >>>> >>>> LAPACK >>>> >>>> 1.2 Author of document >>>> >>>> Bruce Rothermal >>>> >>>> 2.0 Project Summary >>>> 2.1 Project Description >>>> >>>> Port LAPACK Opensource utility to SFW consolidation. Linear Algebra >>>> package. >>>> LAPACK provides routines for solving systems of simultaneous >>>> linear equations, least-squares solutions of linear systems of >>>> equations, eigenvalue problems, and singular value problems. The >>>> associated matrix >>>> factorizations (LU, Cholesky, QR, SVD, Schur, generalized Schur) >>>> are also provided, as are related computations such as reordering >>>> of the Schur factorizations and estimating condition numbers. >>>> Dense and banded matrices are handled, but not general sparse >>>> matrices. In all areas, similar functionality is provided for real >>>> and complex matrices, in both single and double precision. >>>> >>>> 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? >>>> [ ] Yes >>>> [x ] No >>>> >>>> 2.4 Originating Community >>>> 2.4.1 Community Name >>>> LAPACK >>>> http://www.netlib.org/lapack/ >>>> >>>> 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 >>> drive>:\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\>>> id>\\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 >>>> Are static versions of the libraries being delivered? >>>> [x ] Yes - ARC review required >>>> [ ] No The package as is only generates static >>>> libraries. I would have to change the opensource package to >>>> make it generate dynamic. >>>> >>>> 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? >>>> [ ] Yes >>>> [x ] No - continue to next section (section 3.4.6) >>>> If yes are these passwords entered via the CLI or >>>> environment? >>>> [ ] Yes - ARC review required >>>> [ ] No >>>> Are passwords stored within the file system for the >>>> component? >>>> [ ] Yes >>>> [ ] 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? >>>> [ ] Yes >>>> [x ] No - continue with the next section (section 3.5) >>>> Do the components use standard network protocols? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> Do network services for the project make decisions based >>>> upon user, host or service identities? >>>> [ ] Yes - explain below >>>> [ ] No >>>> [ ] N/A >>>> >>>> Do the components make use of secret information during >>>> authentication and/or >>>> authorization? >>>> [ ] Yes - explain below >>>> [ ] No >>>> [ ] N/A >>>> 3.5 Networking >>>> Do the components access the network? >>>> [ ] Yes >>>> [x ] No - continue with the next section (section 3.6) >>>> If yes do the components support IPv6? >>>> [ ] 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 >>>> --------------------------- ------------------- >>>> --------------------------- >>>> SUNWlapack Volatile >>>> lapack libraries for Volatile >>>> for sparc and x86, 32b >>>> and 64b. 4.2 Imported Interfaces >>>> Interface Name Classification Comments >>>> --------------------------- -------------------- >>>> -------------------------- >>>> LAPACK Volatile version 3.2 >>>> >>>> Package compiles with SunStudio f90 no special compiler needed. >>>> Package requires BLAS and intent is to use functionality from Sun >>>> Cluster >>>> Tools. Which is optimized for Solaris. If not the package >>>> contains the opensource BLAS. >>>> >>>> >>>> >>>> 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 >>>> >>>> >>> >> > -- *Gregory V. Tarsy Ph.D. *Senior Manager Floating Point & Numerical Computing Fortran & Sun Performance Library 831.515.3163 831.818.2198 (cell) gregory.tarsy@sun.com