From apai@sac.sfbay.sun.com Fri Oct 3 10:25:47 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 m93HPlpl028113 for ; Fri, 3 Oct 2008 10:25:47 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m93HPkG9008457; Fri, 3 Oct 2008 10:25:46 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K860030HB2YHD00@brm-avmta-1.central.sun.com>; Fri, 03 Oct 2008 11:25:46 -0600 (MDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K8600JT8B2Y4LD0@brm-avmta-1.central.sun.com>; Fri, 03 Oct 2008 11:25:46 -0600 (MDT) 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 m93HPkko005121; Fri, 03 Oct 2008 10:25:46 -0700 (PDT) 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 m93HPiah028108; Fri, 03 Oct 2008 10:25:44 -0700 (PDT) Received: (from apai@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id m93HPiM4028104; Fri, 03 Oct 2008 10:25:44 -0700 (PDT) Date: Fri, 03 Oct 2008 10:25:44 -0700 (PDT) From: Aarti Pai Subject: NetBeans DTrace GUI Plug-in [LSARC/2008/620 FastTrack timeout 10/17/2008] To: lsarc-ext@sun.com Message-id: <200810031725.m93HPiM4028104@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 12196 Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: NetBeans DTrace GUI Plug-in 1.2. Name of Document Author/Supplier: Author: Ivan Vlasyuk 1.3 Date of This Document: 03 October, 2008 4. Technical Description 1.0 Project Information The NetBeans DTrace GUI Plug-in is a graphical user interface (GUI) for Solaris Dynamic Tracing (DTrace), and can be installed into the Sun Studio IDE and NetBeans IDE. For more information please see: http://www.netbeans.org/kb/docs/ide/NetBeans_DTrace_GUI_Plugin_0_4.html 1.1 Name of project/component NetBeans DTrace GUI Plug-in 1.2 Author of document Nasser Nouri 2.0 Project Summary 2.1 Project Description A NetBeans Plug-in for DTrace 2.2 Release binding What is is the release binding? (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) [X] Major [ ] 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 NetBeans and Sun Studio communities 2.4.2 Community Involvement Indicate Sun's involvement in the community [X] Maintainer [ ] Contributor [ ] 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]? [ ] Yes [X] 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? [ ] Yes [X] No - continue with next section (section 3.3) Are 64-bit versions of the libraries being delivered? [ ] Yes [ ] No - ARC review required Are static versions of the libraries being delivered? [ ] Yes - ARC review required [ ] No 3.3 Services and the /etc Directory (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) Does the project integrate anything into /etc/init.d or /etc/rc?.d? [ ] Yes - ARC review required [X] No Does the project integrate any new entries into /etc/inittab or /etc/inetd.conf? [ ] Yes - ARC review required [X] No Does the project integrate any private non-public files into /etc/default or /etc/ configuration files? [ ] Yes - ARC review required [X] No Does the service manifests method context grant rights above that of the noaccess user and basic privilege set? [ ] Yes - ARC review required [X] No 3.4 Security 3.4.1 Secure By Default (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for addtional details) Are there any network services provided by this project? [ ] Yes [X] No - continue with the next section (section 3.4.2) Are network services enabled by default? [ ] Yes - ARC review required [ ] No [ ] N/A Are network services automatically enabled by the project during installation? [ ] Yes - ARC review required [ ] No [ ] N/A Are inbound network communications denied by default? [ ] Yes [ ] No - ARC review required [ ] N/A Is inbound data checked to prevent content-based attacks? [ ] Yes [ ] No - ARC review required [ ] N/A Is the outbound receiver authenticated? [ ] Yes [ ] No - ARC review required [ ] N/A Is the receiver authenticated prior to receiving any sensitive outbound communication? [ ] Yes [ ] No - ARC review required [ ] N/A 3.4.2 Authorization (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ for details) Are there any setuid/setgid privileged binaries in the project? [ ] Yes - ARC review required [X] No - continue with next section (section 3.4.3) If yes then are the setuid/setgid privileges handled by the use of roles? [ ] Yes [ ] No - ARC review required 3.4.3 Auditing (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Does this component contain administrative or security enforcing software? [ ] Yes - ARC review required [X] No - continue to next section (section 3.4.4) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Do the components create audit logs detailing what took place including what event took place, who was involved, when the event took place? [ ] Yes - ARC contract and Audit project team review required [ ] No - ARC review required 3.4.4 Authentication (see http://opensolaris.org/os/community/arc/policies/PAM/) Do the components contain any authentication code? [ ] Yes [X] No - continue to next section (section 3.4.5) If yes do the components use PAM (plugable authentication modules) for authentication? [ ] Yes [ ] No - ARC review required If yes is a single PAM session maintained during authentication? [ ] Yes [ ] No - ARC review required If yes are the components sufficiently privileged to allow the requested operations (authentication, password change, process credential manipulation, audit state initialization)? [ ] Yes - briefly describe below [ ] No - ARC review required 3.4.5 Passwords (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) Do any of the components for the project deal with passwords? [ ] 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 [ ] 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 Dothe 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 --------------------------- ------------------- --------------------------- NetBeans DTrace GUI Committed Package version 0.4 4.2 Imported Interfaces Interface Name Classification Comments --------------------------- -------------------- -------------------------- NetBeans Committed Package version 6.5 References: [1] http://www.netbeans.org 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: u 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From tom.childers@sun.com Tue Oct 7 10:30:38 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 m97HUcB7004750 for ; Tue, 7 Oct 2008 10:30:38 -0700 (PDT) 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 m97HUWTt010091; Tue, 7 Oct 2008 11:30:38 -0600 (MDT) 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 <0K8D00D0JPZ0F200@nwk-avmta-1.sfbay.Sun.COM>; Tue, 07 Oct 2008 10:30:36 -0700 (PDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K8D004DHPZ0K1B0@nwk-avmta-1.sfbay.Sun.COM>; Tue, 07 Oct 2008 10:30:36 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m97HUaCf014280; Tue, 07 Oct 2008 10:30:36 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K8D00501P4GY900@fe-sfbay-10.sun.com> (original mail from tom.childers@sun.com); Tue, 07 Oct 2008 10:30:35 -0700 (PDT) Received: from labnis-qfe4.SFBay.Sun.COM ([75.101.10.233]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K8D00EJXPYW5D60@fe-sfbay-10.sun.com>; Tue, 07 Oct 2008 10:30:33 -0700 (PDT) Date: Tue, 07 Oct 2008 10:30:28 -0700 From: Tom Childers Subject: Re: NetBeans DTrace GUI Plug-in [LSARC/2008/620 FastTrack timeout 10/17/2008] In-reply-to: <200810031725.m93HPiM4028104@sac.sfbay.sun.com> Sender: Thomas.Childers@sun.com To: nassar.nouri@sun.com Cc: lsarc-ext@sun.com, Ivan.Vlasyuk@sun.com Message-id: MIME-version: 1.0 X-Mailer: Apple Mail (2.928.1) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200810031725.m93HPiM4028104@sac.sfbay.sun.com> Status: RO Content-Length: 12845 Nassar, As we mentioned in the LSARC meeting this morning, the DTrace Java API was established by PSARC case 2006/054, http://sac.sfbay/PSARC/ 2006/054. It looks like the interfaces and stability are only described in the mail contents, and dtrace.jar is described as "Evolving". Can you please update the case materials to show you import this interface (or whichever one you use)? Thanks, -tdc On Oct 3, 2008, at 10:25 AM, Aarti Pai wrote: > > Template Version: @(#)sac_nextcase %I% %G% SMI > This information is Copyright 2008 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > NetBeans DTrace GUI Plug-in > 1.2. Name of Document Author/Supplier: > Author: Ivan Vlasyuk > 1.3 Date of This Document: > 03 October, 2008 > 4. Technical Description > > 1.0 Project Information > The NetBeans DTrace GUI Plug-in is a graphical user interface > (GUI) for > Solaris Dynamic Tracing (DTrace), and can be installed into the > Sun Studio > IDE and NetBeans IDE. > > For more information please see: > http://www.netbeans.org/kb/docs/ide/NetBeans_DTrace_GUI_Plugin_0_4.html > > 1.1 Name of project/component > NetBeans DTrace GUI Plug-in > > 1.2 Author of document > Nasser Nouri > > 2.0 Project Summary > 2.1 Project Description > A NetBeans Plug-in for DTrace > > 2.2 Release binding > What is is the release binding? > (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) > [X] Major > [ ] 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 > NetBeans and Sun Studio communities > > 2.4.2 Community Involvement > Indicate Sun's involvement in the community > [X] Maintainer > [ ] Contributor > [ ] 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]? > [ ] Yes > [X] 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? > [ ] Yes > [X] No - continue with next section (section 3.3) > > Are 64-bit versions of the libraries being delivered? > [ ] Yes > [ ] No - ARC review required > > Are static versions of the libraries being delivered? > [ ] Yes - ARC review required > [ ] No > > 3.3 Services and the /etc Directory > (see http://opensolaris.org/os/community/arc/policies/SMF- > policy/) > Does the project integrate anything into /etc/init.d or /etc/ > rc?.d? > [ ] Yes - ARC review required > [X] No > > Does the project integrate any new entries into /etc/inittab or > /etc/inetd.conf? > [ ] Yes - ARC review required > [X] No > > Does the project integrate any private non-public files into / > etc/default > or /etc/ configuration files? > [ ] Yes - ARC review required > [X] No > > Does the service manifests method context grant rights above that > of the noaccess user and basic privilege set? > [ ] Yes - ARC review required > [X] No > > 3.4 Security > 3.4.1 Secure By Default > (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ > for details) > (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ > for details) > (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ > for > addtional details) > Are there any network services provided by this project? > [ ] Yes > [X] No - continue with the next section (section 3.4.2) > > Are network services enabled by default? > [ ] Yes - ARC review required > [ ] No > [ ] N/A > > Are network services automatically enabled by the project > during installation? > [ ] Yes - ARC review required > [ ] No > [ ] N/A > > Are inbound network communications denied by default? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > > Is inbound data checked to prevent content-based attacks? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > > Is the outbound receiver authenticated? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > > Is the receiver authenticated prior to receiving any sensitive > outbound communication? > [ ] Yes > [ ] No - ARC review required > [ ] N/A > > 3.4.2 Authorization > (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ > and > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ > and > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ > for details) > Are there any setuid/setgid privileged binaries in the project? > [ ] Yes - ARC review required > [X] No - continue with next section (section 3.4.3) > > If yes then are the setuid/setgid privileges handled by the use > of roles? > [ ] Yes > [ ] No - ARC review required > > 3.4.3 Auditing > (see http://opensolaris.org/os/community/arc/policies/audit-policy/ > for details) > (see http://opensolaris.org/os/community/arc/caselog/2003/397 > for details) > Does this component contain administrative or security > enforcing software? > [ ] Yes - ARC review required > [X] No - continue to next section (section 3.4.4) > > (see http://opensolaris.org/os/community/arc/caselog/2003/397 > for details) > Do the components create audit logs detailing what took place > including what event > took place, who was involved, when the event took place? > [ ] Yes - ARC contract and Audit project team review required > [ ] No - ARC review required > > > 3.4.4 Authentication > (see http://opensolaris.org/os/community/arc/policies/PAM/) > Do the components contain any authentication code? > [ ] Yes > [X] No - continue to next section (section 3.4.5) > > If yes do the components use PAM (plugable authentication > modules) for authentication? > [ ] Yes > [ ] No - ARC review required > > If yes is a single PAM session maintained during authentication? > [ ] Yes > [ ] No - ARC review required > > If yes are the components sufficiently privileged to allow the > requested > operations (authentication, password change, process credential > manipulation, > audit state initialization)? > [ ] Yes - briefly describe below > [ ] No - ARC review required > > 3.4.5 Passwords > (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ > and > http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ > for details) > Do any of the components for the project deal with passwords? > [ ] 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 > [ ] 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 > Dothe 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 > --------------------------- ------------------- > --------------------------- > NetBeans DTrace GUI Committed Package version 0.4 > > 4.2 Imported Interfaces > Interface Name Classification Comments > --------------------------- -------------------- > -------------------------- > NetBeans Committed Package version 6.5 > > > References: > > [1] http://www.netbeans.org > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > u > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > From carlsonj@phorcys.east.sun.com Tue Oct 7 10:37:40 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 m97HbeQ1006389 for ; Tue, 7 Oct 2008 10:37:40 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m97HbZOT002918; Tue, 7 Oct 2008 10:37:39 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K8D00G07QAOES00@brm-avmta-1.central.sun.com>; Tue, 07 Oct 2008 11:37:36 -0600 (MDT) 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 <0K8D005G4QAO9CC0@brm-avmta-1.central.sun.com>; Tue, 07 Oct 2008 11:37:36 -0600 (MDT) 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 m97HbaqD029743; Tue, 07 Oct 2008 13:37:36 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id m97HbaZL029740; Tue, 07 Oct 2008 13:37:36 -0400 (EDT) Date: Tue, 07 Oct 2008 13:37:36 -0400 From: James Carlson Subject: Re: NetBeans DTrace GUI Plug-in [LSARC/2008/620 FastTrack timeout 10/17/2008] In-reply-to: To: Tom Childers Cc: nassar.nouri@sun.com, lsarc-ext@sun.com, Ivan.Vlasyuk@sun.com Message-id: <18667.40544.255890.901567@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: <200810031725.m93HPiM4028104@sac.sfbay.sun.com> Status: RO Content-Length: 771 Tom Childers writes: > As we mentioned in the LSARC meeting this morning, the DTrace Java API > was established by PSARC case 2006/054, http://sac.sfbay/PSARC/ > 2006/054. It looks like the interfaces and stability are only > described in the mail contents, and dtrace.jar is described as > "Evolving". Can you please update the case materials to show you > import this interface (or whichever one you use)? Nit: it's in the OS/Net consolidation and reviewed by PSARC, so the old "Evolving" used here maps into the current "Committed." -- 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 Nasser.Nouri@sun.com Tue Oct 7 19:13: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 m982DutG019651 for ; Tue, 7 Oct 2008 19:13:57 -0700 (PDT) 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 m982DsRU024044 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Wed, 8 Oct 2008 03:13:56 +0100 (BST) 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 <0K8E00809E76SP00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 07 Oct 2008 20:13:54 -0600 (MDT) Received: from brmea-mail-3.sun.com ([192.18.98.34]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K8E007T8E76HLD0@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 07 Oct 2008 20:13:54 -0600 (MDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m982Dsxm003352 for ; Wed, 08 Oct 2008 02:13:54 +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 <0K8E00701E4AC000@mail-amer.sun.com> (original mail from Nasser.Nouri@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 07 Oct 2008 20:13:54 -0600 (MDT) Received: from [129.146.84.118] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K8E002J3E745PB0@mail-amer.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 07 Oct 2008 20:13:54 -0600 (MDT) Date: Tue, 07 Oct 2008 19:11:33 -0700 From: Nasser Nouri Subject: Re: Fwd: NetBeans DTrace GUI Plug-in [LSARC/2008/620 FastTrack timeout 10/17/2008] In-reply-to: <1A52D2E3-6651-4877-B71F-BBA128A83787@sun.com> Sender: Nasser.Nouri@sun.com To: Tom Childers Cc: lsarc-ext@sun.com, Ivan Vlasyuk Message-id: <48EC16D5.8010202@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: <1A52D2E3-6651-4877-B71F-BBA128A83787@sun.com> User-Agent: Thunderbird 2.0.0.0 (X11/20070501) Status: RO Content-Length: 14525 Hi Tom, As mentioned this morning, the NetBeans DTrace GUI Plug-in utilizes Chime for DTrace output visualization. Chime is an OpenSolaris project which uses the dtrace.jar API to communicate with Solaris kernel. The dtrace.jar file resides in "/usr/share/lib/java/" directory. Please send me more instructions on how to update the case materials for DTrace GUI. Are you asking me to update the onepager documentation for DTrace GUI? Please advise. Thanks, __Nasser Tom Childers wrote: > > > Begin forwarded message: > >> *From: *Tom Childers > >> *Date: *October 7, 2008 10:30:28 AM PDT >> *To: *nassar.nouri@sun.com >> *Cc: *lsarc-ext@sun.com , >> ivan.vlasyuk@sun.com >> *Subject: **Re: NetBeans DTrace GUI Plug-in [LSARC/2008/620 FastTrack >> timeout 10/17/2008]* >> >> Nassar, >> >> As we mentioned in the LSARC meeting this morning, the DTrace Java >> API was established by PSARC case 2006/054, >> http://sac.sfbay/PSARC/2006/054. It looks like the interfaces and >> stability are only described in the mail contents, and dtrace.jar is >> described as "Evolving". Can you please update the case materials to >> show you import this interface (or whichever one you use)? >> >> Thanks, >> -tdc >> >> >> On Oct 3, 2008, at 10:25 AM, Aarti Pai wrote: >> >>> >>> Template Version: @(#)sac_nextcase %I% %G% SMI >>> This information is Copyright 2008 Sun Microsystems >>> 1. Introduction >>> 1.1. Project/Component Working Name: >>> NetBeans DTrace GUI Plug-in >>> 1.2. Name of Document Author/Supplier: >>> Author: Ivan Vlasyuk >>> 1.3 Date of This Document: >>> 03 October, 2008 >>> 4. Technical Description >>> >>> 1.0 Project Information >>> The NetBeans DTrace GUI Plug-in is a graphical user interface >>> (GUI) for >>> Solaris Dynamic Tracing (DTrace), and can be installed into the >>> Sun Studio >>> IDE and NetBeans IDE. >>> >>> For more information please see: >>> http://www.netbeans.org/kb/docs/ide/NetBeans_DTrace_GUI_Plugin_0_4.html >>> >>> 1.1 Name of project/component >>> NetBeans DTrace GUI Plug-in >>> >>> 1.2 Author of document >>> Nasser Nouri >>> >>> 2.0 Project Summary >>> 2.1 Project Description >>> A NetBeans Plug-in for DTrace >>> >>> 2.2 Release binding >>> What is is the release binding? >>> (see >>> http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >>> >>> [X] Major >>> [ ] 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 >>> NetBeans and Sun Studio communities >>> >>> 2.4.2 Community Involvement >>> Indicate Sun's involvement in the community >>> [X] Maintainer >>> [ ] Contributor >>> [ ] 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]? >>> [ ] Yes >>> [X] 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 >> drive>:\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? >>> [ ] Yes >>> [X] No - continue with next section (section 3.3) >>> >>> Are 64-bit versions of the libraries being delivered? >>> [ ] Yes >>> [ ] No - ARC review required >>> >>> Are static versions of the libraries being delivered? >>> [ ] Yes - ARC review required >>> [ ] No >>> >>> 3.3 Services and the /etc Directory >>> (see >>> http://opensolaris.org/os/community/arc/policies/SMF-policy/) >>> >>> Does the project integrate anything into /etc/init.d or /etc/rc?.d? >>> [ ] Yes - ARC review required >>> [X] No >>> >>> Does the project integrate any new entries into /etc/inittab or >>> /etc/inetd.conf? >>> [ ] Yes - ARC review required >>> [X] No >>> >>> Does the project integrate any private non-public files into >>> /etc/default >>> or /etc/ configuration files? >>> [ ] Yes - ARC review required >>> [X] No >>> >>> Does the service manifests method context grant rights above that >>> of the noaccess user and basic privilege set? >>> [ ] Yes - ARC review required >>> [X] No >>> >>> 3.4 Security >>> 3.4.1 Secure By Default >>> (see >>> http://opensolaris.org/os/community/arc/policies/secure-by-default/ >>> for details) >>> (see >>> http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ >>> for details) >>> (see parts of >>> http://opensolaris.org/os/community/arc/policies/SMF-policy/ for >>> addtional details) >>> Are there any network services provided by this project? >>> [ ] Yes >>> [X] No - continue with the next section (section 3.4.2) >>> >>> Are network services enabled by default? >>> [ ] Yes - ARC review required >>> [ ] No >>> [ ] N/A >>> >>> Are network services automatically enabled by the project during >>> installation? >>> [ ] Yes - ARC review required >>> [ ] No >>> [ ] N/A >>> >>> Are inbound network communications denied by default? >>> [ ] Yes >>> [ ] No - ARC review required >>> [ ] N/A >>> >>> Is inbound data checked to prevent content-based attacks? >>> [ ] Yes >>> [ ] No - ARC review required >>> [ ] N/A >>> >>> Is the outbound receiver authenticated? >>> [ ] Yes >>> [ ] No - ARC review required >>> [ ] N/A >>> >>> Is the receiver authenticated prior to receiving any sensitive >>> outbound communication? >>> [ ] Yes >>> [ ] No - ARC review required >>> [ ] N/A >>> >>> 3.4.2 Authorization >>> (see >>> http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and >>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >>> and >>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >>> for details) >>> Are there any setuid/setgid privileged binaries in the project? >>> [ ] Yes - ARC review required >>> [X] No - continue with next section (section 3.4.3) >>> >>> If yes then are the setuid/setgid privileges handled by the use >>> of roles? >>> [ ] Yes >>> [ ] No - ARC review required >>> >>> 3.4.3 Auditing >>> (see >>> http://opensolaris.org/os/community/arc/policies/audit-policy/ for >>> details) >>> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >>> for details) >>> Does this component contain administrative or security enforcing >>> software? >>> [ ] Yes - ARC review required >>> [X] No - continue to next section (section 3.4.4) >>> >>> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >>> for details) >>> Do the components create audit logs detailing what took place >>> including what event >>> took place, who was involved, when the event took place? >>> [ ] Yes - ARC contract and Audit project team review required >>> [ ] No - ARC review required >>> >>> >>> 3.4.4 Authentication >>> (see http://opensolaris.org/os/community/arc/policies/PAM/) >>> >>> Do the components contain any authentication code? >>> [ ] Yes >>> [X] No - continue to next section (section 3.4.5) >>> >>> If yes do the components use PAM (plugable authentication >>> modules) for authentication? >>> [ ] Yes >>> [ ] No - ARC review required >>> >>> If yes is a single PAM session maintained during authentication? >>> [ ] Yes >>> [ ] No - ARC review required >>> >>> If yes are the components sufficiently privileged to allow the >>> requested >>> operations (authentication, password change, process credential >>> manipulation, >>> audit state initialization)? >>> [ ] Yes - briefly describe below >>> [ ] No - ARC review required >>> >>> 3.4.5 Passwords >>> (see >>> http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and >>> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ >>> for details) >>> Do any of the components for the project deal with passwords? >>> [ ] 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 >>> [ ] 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 >>> Dothe 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 >>> --------------------------- ------------------- >>> --------------------------- >>> NetBeans DTrace GUI Committed Package version 0.4 >>> >>> 4.2 Imported Interfaces >>> Interface Name Classification Comments >>> --------------------------- -------------------- >>> -------------------------- >>> NetBeans Committed Package version 6.5 >>> >>> >>> References: >>> >>> [1] http://www.netbeans.org >>> >>> >>> 6. Resources and Schedule >>> 6.4. Steering Committee requested information >>> 6.4.1. Consolidation C-team Name: >>> u >>> 6.5. ARC review type: FastTrack >>> 6.6. ARC Exposure: open >>> >> > From tom.childers@sun.com Wed Oct 8 11:48:48 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 m98ImlhU023877 for ; Wed, 8 Oct 2008 11:48:48 -0700 (PDT) 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 m98ImfeJ006545 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Wed, 8 Oct 2008 19:48:46 +0100 (BST) 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 <0K8F00C0TO99F700@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 08 Oct 2008 12:48:45 -0600 (MDT) 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 <0K8F00B3BO98N110@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 08 Oct 2008 12:48:45 -0600 (MDT) 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 m98ImiCv007240 for ; Wed, 08 Oct 2008 11:48:44 -0700 (PDT) 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 <0K8F00301NBRHY00@fe-sfbay-09.sun.com> (original mail from tom.childers@sun.com) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 08 Oct 2008 11:48:44 -0700 (PDT) Received: from labnis-qfe4.SFBay.Sun.COM ([75.101.10.233]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K8F00IV5O95GSB0@fe-sfbay-09.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 08 Oct 2008 11:48:42 -0700 (PDT) Date: Wed, 08 Oct 2008 11:48:40 -0700 From: Tom Childers Subject: Re: NetBeans DTrace GUI Plug-in [LSARC/2008/620 FastTrack timeout 10/17/2008] In-reply-to: <48EC16D5.8010202@sun.com> Sender: Thomas.Childers@sun.com To: Nasser Nouri Cc: lsarc-ext@sun.com, Ivan Vlasyuk Message-id: <57F498BD-C449-4D5C-ADE4-12912D1EAE20@sun.com> MIME-version: 1.0 X-Mailer: Apple Mail (2.928.1) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <1A52D2E3-6651-4877-B71F-BBA128A83787@sun.com> <48EC16D5.8010202@sun.com> Status: RO Content-Length: 15692 Hi, Nasser. Since the interfaces are documented in the one-pager for this case, then yes, we will need an updated one-pager. I'm not aware of Chime, so I went and read the articles on opensolaris.org, including your July announcement of the DTrace plugin. I see that Chime is available for separate download, but I cannot find an ARC case where it was reviewed and approved. If you are importing Chime, then that is what will go into the one- pager. If Chime has not been through ARC review, then we need to get it reviewed before we can approve your case. Or, if Chime is one of your deliverables from this project, I suppose it can become a part of your case, and the Chime download becomes an exported interface. It would probably be easier to get a fasttrack rolling to review Chime separately. -tdc On Oct 7, 2008, at 7:11 PM, Nasser Nouri wrote: > Hi Tom, > > As mentioned this morning, the NetBeans DTrace GUI Plug-in utilizes > Chime for DTrace output visualization. Chime is an OpenSolaris > project which uses the dtrace.jar API to communicate with Solaris > kernel. The dtrace.jar file resides in "/usr/share/lib/java/" > directory. > > Please send me more instructions on how to update the case materials > for DTrace GUI. Are you asking me to update the onepager > documentation for DTrace GUI? > > Please advise. > > Thanks, > __Nasser > > Tom Childers wrote: >> >> >> Begin forwarded message: >> >>> *From: *Tom Childers >> >> >>> *Date: *October 7, 2008 10:30:28 AM PDT >>> *To: *nassar.nouri@sun.com >>> *Cc: *lsarc-ext@sun.com , ivan.vlasyuk@sun.com >>> >>> *Subject: **Re: NetBeans DTrace GUI Plug-in [LSARC/2008/620 >>> FastTrack timeout 10/17/2008]* >>> >>> Nassar, >>> >>> As we mentioned in the LSARC meeting this morning, the DTrace Java >>> API was established by PSARC case 2006/054, http://sac.sfbay/PSARC/2006/054 >>> . It looks like the interfaces and stability are only described in >>> the mail contents, and dtrace.jar is described as "Evolving". Can >>> you please update the case materials to show you import this >>> interface (or whichever one you use)? >>> >>> Thanks, >>> -tdc >>> >>> >>> On Oct 3, 2008, at 10:25 AM, Aarti Pai wrote: >>> >>>> >>>> Template Version: @(#)sac_nextcase %I% %G% SMI >>>> This information is Copyright 2008 Sun Microsystems >>>> 1. Introduction >>>> 1.1. Project/Component Working Name: >>>> NetBeans DTrace GUI Plug-in >>>> 1.2. Name of Document Author/Supplier: >>>> Author: Ivan Vlasyuk >>>> 1.3 Date of This Document: >>>> 03 October, 2008 >>>> 4. Technical Description >>>> >>>> 1.0 Project Information >>>> The NetBeans DTrace GUI Plug-in is a graphical user interface >>>> (GUI) for >>>> Solaris Dynamic Tracing (DTrace), and can be installed into the >>>> Sun Studio >>>> IDE and NetBeans IDE. >>>> >>>> For more information please see: >>>> http://www.netbeans.org/kb/docs/ide/NetBeans_DTrace_GUI_Plugin_0_4.html >>>> >>>> 1.1 Name of project/component >>>> NetBeans DTrace GUI Plug-in >>>> >>>> 1.2 Author of document >>>> Nasser Nouri >>>> >>>> 2.0 Project Summary >>>> 2.1 Project Description >>>> A NetBeans Plug-in for DTrace >>>> >>>> 2.2 Release binding >>>> What is is the release binding? >>>> (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >>>> >>> > >>>> [X] Major >>>> [ ] 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 >>>> NetBeans and Sun Studio communities >>>> >>>> 2.4.2 Community Involvement >>>> Indicate Sun's involvement in the community >>>> [X] Maintainer >>>> [ ] Contributor >>>> [ ] 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]? >>>> [ ] Yes >>>> [X] 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? >>>> [ ] Yes >>>> [X] No - continue with next section (section 3.3) >>>> >>>> Are 64-bit versions of the libraries being delivered? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> Are static versions of the libraries being delivered? >>>> [ ] Yes - ARC review required >>>> [ ] No >>>> >>>> 3.3 Services and the /etc Directory >>>> (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) >>>> >>>> Does the project integrate anything into /etc/init.d or /etc/ >>>> rc?.d? >>>> [ ] Yes - ARC review required >>>> [X] No >>>> >>>> Does the project integrate any new entries into /etc/inittab or >>>> /etc/inetd.conf? >>>> [ ] Yes - ARC review required >>>> [X] No >>>> >>>> Does the project integrate any private non-public files into / >>>> etc/default >>>> or /etc/ configuration files? >>>> [ ] Yes - ARC review required >>>> [X] No >>>> >>>> Does the service manifests method context grant rights above >>>> that >>>> of the noaccess user and basic privilege set? >>>> [ ] Yes - ARC review required >>>> [X] No >>>> >>>> 3.4 Security >>>> 3.4.1 Secure By Default >>>> (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ >>>> for details) >>>> (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ >>>> for details) >>>> (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ >>>> for >>>> addtional details) >>>> Are there any network services provided by this project? >>>> [ ] Yes >>>> [X] No - continue with the next section (section 3.4.2) >>>> >>>> Are network services enabled by default? >>>> [ ] Yes - ARC review required >>>> [ ] No >>>> [ ] N/A >>>> >>>> Are network services automatically enabled by the project >>>> during installation? >>>> [ ] Yes - ARC review required >>>> [ ] No >>>> [ ] N/A >>>> >>>> Are inbound network communications denied by default? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> [ ] N/A >>>> >>>> Is inbound data checked to prevent content-based attacks? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> [ ] N/A >>>> >>>> Is the outbound receiver authenticated? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> [ ] N/A >>>> >>>> Is the receiver authenticated prior to receiving any sensitive >>>> outbound communication? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> [ ] N/A >>>> >>>> 3.4.2 Authorization >>>> (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ >>>> and >>>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >>>> and >>>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >>>> for details) >>>> Are there any setuid/setgid privileged binaries in the project? >>>> [ ] Yes - ARC review required >>>> [X] No - continue with next section (section 3.4.3) >>>> >>>> If yes then are the setuid/setgid privileges handled by the >>>> use of roles? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> 3.4.3 Auditing >>>> (see http://opensolaris.org/os/community/arc/policies/audit-policy/ >>>> for details) >>>> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >>>> for details) >>>> Does this component contain administrative or security >>>> enforcing software? >>>> [ ] Yes - ARC review required >>>> [X] No - continue to next section (section 3.4.4) >>>> >>>> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >>>> for details) >>>> Do the components create audit logs detailing what took place >>>> including what event >>>> took place, who was involved, when the event took place? >>>> [ ] Yes - ARC contract and Audit project team review required >>>> [ ] No - ARC review required >>>> >>>> >>>> 3.4.4 Authentication >>>> (see http://opensolaris.org/os/community/arc/policies/PAM/) >>> > >>>> Do the components contain any authentication code? >>>> [ ] Yes >>>> [X] No - continue to next section (section 3.4.5) >>>> >>>> If yes do the components use PAM (plugable authentication >>>> modules) for authentication? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> If yes is a single PAM session maintained during authentication? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> If yes are the components sufficiently privileged to allow the >>>> requested >>>> operations (authentication, password change, process >>>> credential manipulation, >>>> audit state initialization)? >>>> [ ] Yes - briefly describe below >>>> [ ] No - ARC review required >>>> >>>> 3.4.5 Passwords >>>> (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ >>>> and >>>> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ >>>> for details) >>>> Do any of the components for the project deal with passwords? >>>> [ ] 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 >>>> [ ] 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 >>>> Dothe 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 >>>> --------------------------- ------------------- >>>> --------------------------- >>>> NetBeans DTrace GUI Committed Package version >>>> 0.4 >>>> >>>> 4.2 Imported Interfaces >>>> Interface Name Classification Comments >>>> --------------------------- -------------------- >>>> -------------------------- >>>> NetBeans Committed Package version >>>> 6.5 >>>> >>>> >>>> References: >>>> >>>> [1] http://www.netbeans.org >>>> >>>> >>>> 6. Resources and Schedule >>>> 6.4. Steering Committee requested information >>>> 6.4.1. Consolidation C-team Name: >>>> u >>>> 6.5. ARC review type: FastTrack >>>> 6.6. ARC Exposure: open >>>> >>> >> > From Nasser.Nouri@Sun.COM Wed Oct 8 20:04:10 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 m99349lo009026 for ; Wed, 8 Oct 2008 20:04:09 -0700 (PDT) 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 m9933vcm006391 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 9 Oct 2008 11:04:06 +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 <0K8G0040BB6T8W00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 08 Oct 2008 21:04:05 -0600 (MDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K8G00CUTB6SMT80@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 08 Oct 2008 21:04:04 -0600 (MDT) 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 m99344pA024998 for ; Thu, 09 Oct 2008 03:04:04 +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 <0K8G00401B08PD00@mail-amer.sun.com> (original mail from Nasser.Nouri@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 08 Oct 2008 21:04:04 -0600 (MDT) Received: from [129.146.84.118] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K8G000W6B6QJ820@mail-amer.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 08 Oct 2008 21:04:04 -0600 (MDT) Date: Wed, 08 Oct 2008 20:01:41 -0700 From: Nasser Nouri Subject: Re: NetBeans DTrace GUI Plug-in [LSARC/2008/620 FastTrack timeout 10/17/2008] In-reply-to: <57F498BD-C449-4D5C-ADE4-12912D1EAE20@sun.com> Sender: Nasser.Nouri@Sun.COM To: Tom Childers Cc: lsarc-ext@Sun.COM, Ivan Vlasyuk Message-id: <48ED7415.9030000@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: <1A52D2E3-6651-4877-B71F-BBA128A83787@sun.com> <48EC16D5.8010202@sun.com> <57F498BD-C449-4D5C-ADE4-12912D1EAE20@sun.com> User-Agent: Thunderbird 2.0.0.0 (X11/20070501) Status: RO Content-Length: 16729 Hi Tom, Chime is fully integrated with NetBeans DTrace GUI Plug in. Users are not required to download Chime separately in order to use NetBeans DTrace GUI. Basically, Chime is a component of NetBeans DTrace GUI. Users are not required to download Chime separately. Users can download Chime and install it on their system if they need to invoke Chime outside of NetBeans. The NetBeans DTrace GUI does not have any dependencies on any packages the are installed by Chime. Basically, they are two different products. Please advise. Thanks, __Nasser Tom Childers wrote: > Hi, Nasser. > > Since the interfaces are documented in the one-pager for this case, > then yes, we will need an updated one-pager. > > I'm not aware of Chime, so I went and read the articles on > opensolaris.org, including your July announcement of the DTrace > plugin. I see that Chime is available for separate download, but I > cannot find an ARC case where it was reviewed and approved. > > If you are importing Chime, then that is what will go into the > one-pager. If Chime has not been through ARC review, then we need to > get it reviewed before we can approve your case. Or, if Chime is one > of your deliverables from this project, I suppose it can become a part > of your case, and the Chime download becomes an exported interface. > It would probably be easier to get a fasttrack rolling to review Chime > separately. > -tdc > > On Oct 7, 2008, at 7:11 PM, Nasser Nouri wrote: > >> Hi Tom, >> >> As mentioned this morning, the NetBeans DTrace GUI Plug-in utilizes >> Chime for DTrace output visualization. Chime is an OpenSolaris >> project which uses the dtrace.jar API to communicate with Solaris >> kernel. The dtrace.jar file resides in "/usr/share/lib/java/" directory. >> >> Please send me more instructions on how to update the case materials >> for DTrace GUI. Are you asking me to update the onepager >> documentation for DTrace GUI? >> >> Please advise. >> >> Thanks, >> __Nasser >> >> Tom Childers wrote: >>> >>> >>> Begin forwarded message: >>> >>>> *From: *Tom Childers >>> > >>>> *Date: *October 7, 2008 10:30:28 AM PDT >>>> *To: *nassar.nouri@sun.com >>>> *Cc: *lsarc-ext@sun.com , >>>> ivan.vlasyuk@sun.com >>>> *Subject: **Re: NetBeans DTrace GUI Plug-in [LSARC/2008/620 >>>> FastTrack timeout 10/17/2008]* >>>> >>>> Nassar, >>>> >>>> As we mentioned in the LSARC meeting this morning, the DTrace Java >>>> API was established by PSARC case 2006/054, >>>> http://sac.sfbay/PSARC/2006/054. It looks like the interfaces and >>>> stability are only described in the mail contents, and dtrace.jar >>>> is described as "Evolving". Can you please update the case >>>> materials to show you import this interface (or whichever one you >>>> use)? >>>> >>>> Thanks, >>>> -tdc >>>> >>>> >>>> On Oct 3, 2008, at 10:25 AM, Aarti Pai wrote: >>>> >>>>> >>>>> Template Version: @(#)sac_nextcase %I% %G% SMI >>>>> This information is Copyright 2008 Sun Microsystems >>>>> 1. Introduction >>>>> 1.1. Project/Component Working Name: >>>>> NetBeans DTrace GUI Plug-in >>>>> 1.2. Name of Document Author/Supplier: >>>>> Author: Ivan Vlasyuk >>>>> 1.3 Date of This Document: >>>>> 03 October, 2008 >>>>> 4. Technical Description >>>>> >>>>> 1.0 Project Information >>>>> The NetBeans DTrace GUI Plug-in is a graphical user interface >>>>> (GUI) for >>>>> Solaris Dynamic Tracing (DTrace), and can be installed into the >>>>> Sun Studio >>>>> IDE and NetBeans IDE. >>>>> >>>>> For more information please see: >>>>> http://www.netbeans.org/kb/docs/ide/NetBeans_DTrace_GUI_Plugin_0_4.html >>>>> >>>>> >>>>> 1.1 Name of project/component >>>>> NetBeans DTrace GUI Plug-in >>>>> >>>>> 1.2 Author of document >>>>> Nasser Nouri >>>>> >>>>> 2.0 Project Summary >>>>> 2.1 Project Description >>>>> A NetBeans Plug-in for DTrace >>>>> >>>>> 2.2 Release binding >>>>> What is is the release binding? >>>>> (see >>>>> http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >>>>> >>>>> [X] Major >>>>> [ ] 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 >>>>> NetBeans and Sun Studio communities >>>>> >>>>> 2.4.2 Community Involvement >>>>> Indicate Sun's involvement in the community >>>>> [X] Maintainer >>>>> [ ] Contributor >>>>> [ ] 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]? >>>>> [ ] Yes >>>>> [X] 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 >>>> drive>:\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? >>>>> [ ] Yes >>>>> [X] No - continue with next section (section 3.3) >>>>> >>>>> Are 64-bit versions of the libraries being delivered? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> >>>>> Are static versions of the libraries being delivered? >>>>> [ ] Yes - ARC review required >>>>> [ ] No >>>>> >>>>> 3.3 Services and the /etc Directory >>>>> (see >>>>> http://opensolaris.org/os/community/arc/policies/SMF-policy/) >>>>> >>>>> Does the project integrate anything into /etc/init.d or >>>>> /etc/rc?.d? >>>>> [ ] Yes - ARC review required >>>>> [X] No >>>>> >>>>> Does the project integrate any new entries into /etc/inittab or >>>>> /etc/inetd.conf? >>>>> [ ] Yes - ARC review required >>>>> [X] No >>>>> >>>>> Does the project integrate any private non-public files into >>>>> /etc/default >>>>> or /etc/ configuration files? >>>>> [ ] Yes - ARC review required >>>>> [X] No >>>>> >>>>> Does the service manifests method context grant rights above that >>>>> of the noaccess user and basic privilege set? >>>>> [ ] Yes - ARC review required >>>>> [X] No >>>>> >>>>> 3.4 Security >>>>> 3.4.1 Secure By Default >>>>> (see >>>>> http://opensolaris.org/os/community/arc/policies/secure-by-default/ for >>>>> details) >>>>> (see >>>>> http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for >>>>> details) >>>>> (see parts of >>>>> http://opensolaris.org/os/community/arc/policies/SMF-policy/ for >>>>> addtional details) >>>>> Are there any network services provided by this project? >>>>> [ ] Yes >>>>> [X] No - continue with the next section (section 3.4.2) >>>>> >>>>> Are network services enabled by default? >>>>> [ ] Yes - ARC review required >>>>> [ ] No >>>>> [ ] N/A >>>>> >>>>> Are network services automatically enabled by the project >>>>> during installation? >>>>> [ ] Yes - ARC review required >>>>> [ ] No >>>>> [ ] N/A >>>>> >>>>> Are inbound network communications denied by default? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> [ ] N/A >>>>> >>>>> Is inbound data checked to prevent content-based attacks? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> [ ] N/A >>>>> >>>>> Is the outbound receiver authenticated? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> [ ] N/A >>>>> >>>>> Is the receiver authenticated prior to receiving any sensitive >>>>> outbound communication? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> [ ] N/A >>>>> >>>>> 3.4.2 Authorization >>>>> (see >>>>> http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and >>>>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and >>>>> >>>>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >>>>> for details) >>>>> Are there any setuid/setgid privileged binaries in the project? >>>>> [ ] Yes - ARC review required >>>>> [X] No - continue with next section (section 3.4.3) >>>>> >>>>> If yes then are the setuid/setgid privileges handled by the use >>>>> of roles? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> >>>>> 3.4.3 Auditing >>>>> (see >>>>> http://opensolaris.org/os/community/arc/policies/audit-policy/ for >>>>> details) >>>>> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >>>>> for details) >>>>> Does this component contain administrative or security >>>>> enforcing software? >>>>> [ ] Yes - ARC review required >>>>> [X] No - continue to next section (section 3.4.4) >>>>> >>>>> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >>>>> for details) >>>>> Do the components create audit logs detailing what took place >>>>> including what event >>>>> took place, who was involved, when the event took place? >>>>> [ ] Yes - ARC contract and Audit project team review required >>>>> [ ] No - ARC review required >>>>> >>>>> >>>>> 3.4.4 Authentication >>>>> (see http://opensolaris.org/os/community/arc/policies/PAM/) >>>>> >>>>> Do the components contain any authentication code? >>>>> [ ] Yes >>>>> [X] No - continue to next section (section 3.4.5) >>>>> >>>>> If yes do the components use PAM (plugable authentication >>>>> modules) for authentication? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> >>>>> If yes is a single PAM session maintained during authentication? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> >>>>> If yes are the components sufficiently privileged to allow the >>>>> requested >>>>> operations (authentication, password change, process credential >>>>> manipulation, >>>>> audit state initialization)? >>>>> [ ] Yes - briefly describe below >>>>> [ ] No - ARC review required >>>>> >>>>> 3.4.5 Passwords >>>>> (see >>>>> http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and >>>>> >>>>> >>>>> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for >>>>> details) >>>>> Do any of the components for the project deal with passwords? >>>>> [ ] 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 >>>>> [ ] 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 >>>>> Dothe 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 >>>>> --------------------------- ------------------- >>>>> --------------------------- >>>>> NetBeans DTrace GUI Committed Package version 0.4 >>>>> >>>>> 4.2 Imported Interfaces >>>>> Interface Name Classification Comments >>>>> --------------------------- -------------------- >>>>> -------------------------- >>>>> NetBeans Committed Package version 6.5 >>>>> >>>>> >>>>> References: >>>>> >>>>> [1] http://www.netbeans.org >>>>> >>>>> >>>>> 6. Resources and Schedule >>>>> 6.4. Steering Committee requested information >>>>> 6.4.1. Consolidation C-team Name: >>>>> u >>>>> 6.5. ARC review type: FastTrack >>>>> 6.6. ARC Exposure: open >>>>> >>>> >>> >> > From Ivan.Vlasyuk@sun.com Thu Oct 9 05:34:47 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 m99CYkSt022115 for ; Thu, 9 Oct 2008 05:34:46 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m99CYTCm024434 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 9 Oct 2008 13:34:45 +0100 (BST) 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 <0K8H00L011LV5Z00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 09 Oct 2008 05:34:43 -0700 (PDT) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K8H005KR1LUY570@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 09 Oct 2008 05:34:43 -0700 (PDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m99CYfFC008132 for ; Thu, 09 Oct 2008 12:34:41 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K8H007010CU4P00@fe-emea-09.sun.com> (original mail from Ivan.Vlasyuk@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 09 Oct 2008 13:34:41 +0100 (BST) Received: from [129.157.20.52] by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K8H00C7L1LEDGB0@fe-emea-09.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 09 Oct 2008 13:34:26 +0100 (BST) Date: Thu, 09 Oct 2008 14:34:05 +0200 From: Ivan Vlasyuk Subject: Re: NetBeans DTrace GUI Plug-in [LSARC/2008/620 FastTrack timeout 10/17/2008] In-reply-to: <57F498BD-C449-4D5C-ADE4-12912D1EAE20@sun.com> Sender: Ivan.Vlasyuk@sun.com To: Tom Childers Cc: Nasser Nouri , lsarc-ext@sun.com Message-id: <48EDFA3D.7090202@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: <1A52D2E3-6651-4877-B71F-BBA128A83787@sun.com> <48EC16D5.8010202@sun.com> <57F498BD-C449-4D5C-ADE4-12912D1EAE20@sun.com> User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) Status: RO Content-Length: 16305 Tom, In your opinion, if we to become engineering sponsor to drive Chime technology via LSARC review, will it also qualify for fast track? -Ivan Tom Childers wrote: > Hi, Nasser. > > Since the interfaces are documented in the one-pager for this case, then > yes, we will need an updated one-pager. > > I'm not aware of Chime, so I went and read the articles on > opensolaris.org, including your July announcement of the DTrace plugin. > I see that Chime is available for separate download, but I cannot find > an ARC case where it was reviewed and approved. > > If you are importing Chime, then that is what will go into the > one-pager. If Chime has not been through ARC review, then we need to get > it reviewed before we can approve your case. Or, if Chime is one of > your deliverables from this project, I suppose it can become a part of > your case, and the Chime download becomes an exported interface. It > would probably be easier to get a fasttrack rolling to review Chime > separately. > -tdc > > On Oct 7, 2008, at 7:11 PM, Nasser Nouri wrote: > >> Hi Tom, >> >> As mentioned this morning, the NetBeans DTrace GUI Plug-in utilizes >> Chime for DTrace output visualization. Chime is an OpenSolaris project >> which uses the dtrace.jar API to communicate with Solaris kernel. The >> dtrace.jar file resides in "/usr/share/lib/java/" directory. >> >> Please send me more instructions on how to update the case materials >> for DTrace GUI. Are you asking me to update the onepager documentation >> for DTrace GUI? >> >> Please advise. >> >> Thanks, >> __Nasser >> >> Tom Childers wrote: >>> >>> >>> Begin forwarded message: >>> >>>> *From: *Tom Childers >>> > >>>> *Date: *October 7, 2008 10:30:28 AM PDT >>>> *To: *nassar.nouri@sun.com >>>> *Cc: *lsarc-ext@sun.com , >>>> ivan.vlasyuk@sun.com >>>> *Subject: **Re: NetBeans DTrace GUI Plug-in [LSARC/2008/620 >>>> FastTrack timeout 10/17/2008]* >>>> >>>> Nassar, >>>> >>>> As we mentioned in the LSARC meeting this morning, the DTrace Java >>>> API was established by PSARC case 2006/054, >>>> http://sac.sfbay/PSARC/2006/054. It looks like the interfaces and >>>> stability are only described in the mail contents, and dtrace.jar is >>>> described as "Evolving". Can you please update the case materials >>>> to show you import this interface (or whichever one you use)? >>>> >>>> Thanks, >>>> -tdc >>>> >>>> >>>> On Oct 3, 2008, at 10:25 AM, Aarti Pai wrote: >>>> >>>>> >>>>> Template Version: @(#)sac_nextcase %I% %G% SMI >>>>> This information is Copyright 2008 Sun Microsystems >>>>> 1. Introduction >>>>> 1.1. Project/Component Working Name: >>>>> NetBeans DTrace GUI Plug-in >>>>> 1.2. Name of Document Author/Supplier: >>>>> Author: Ivan Vlasyuk >>>>> 1.3 Date of This Document: >>>>> 03 October, 2008 >>>>> 4. Technical Description >>>>> >>>>> 1.0 Project Information >>>>> The NetBeans DTrace GUI Plug-in is a graphical user interface >>>>> (GUI) for >>>>> Solaris Dynamic Tracing (DTrace), and can be installed into the >>>>> Sun Studio >>>>> IDE and NetBeans IDE. >>>>> >>>>> For more information please see: >>>>> http://www.netbeans.org/kb/docs/ide/NetBeans_DTrace_GUI_Plugin_0_4.html >>>>> >>>>> >>>>> 1.1 Name of project/component >>>>> NetBeans DTrace GUI Plug-in >>>>> >>>>> 1.2 Author of document >>>>> Nasser Nouri >>>>> >>>>> 2.0 Project Summary >>>>> 2.1 Project Description >>>>> A NetBeans Plug-in for DTrace >>>>> >>>>> 2.2 Release binding >>>>> What is is the release binding? >>>>> (see >>>>> http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >>>>> >>>>> [X] Major >>>>> [ ] 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 >>>>> NetBeans and Sun Studio communities >>>>> >>>>> 2.4.2 Community Involvement >>>>> Indicate Sun's involvement in the community >>>>> [X] Maintainer >>>>> [ ] Contributor >>>>> [ ] 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]? >>>>> [ ] Yes >>>>> [X] 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 >>>> drive>:\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? >>>>> [ ] Yes >>>>> [X] No - continue with next section (section 3.3) >>>>> >>>>> Are 64-bit versions of the libraries being delivered? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> >>>>> Are static versions of the libraries being delivered? >>>>> [ ] Yes - ARC review required >>>>> [ ] No >>>>> >>>>> 3.3 Services and the /etc Directory >>>>> (see >>>>> http://opensolaris.org/os/community/arc/policies/SMF-policy/) >>>>> >>>>> Does the project integrate anything into /etc/init.d or /etc/rc?.d? >>>>> [ ] Yes - ARC review required >>>>> [X] No >>>>> >>>>> Does the project integrate any new entries into /etc/inittab or >>>>> /etc/inetd.conf? >>>>> [ ] Yes - ARC review required >>>>> [X] No >>>>> >>>>> Does the project integrate any private non-public files into >>>>> /etc/default >>>>> or /etc/ configuration files? >>>>> [ ] Yes - ARC review required >>>>> [X] No >>>>> >>>>> Does the service manifests method context grant rights above that >>>>> of the noaccess user and basic privilege set? >>>>> [ ] Yes - ARC review required >>>>> [X] No >>>>> >>>>> 3.4 Security >>>>> 3.4.1 Secure By Default >>>>> (see >>>>> http://opensolaris.org/os/community/arc/policies/secure-by-default/ for >>>>> details) >>>>> (see >>>>> http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for >>>>> details) >>>>> (see parts of >>>>> http://opensolaris.org/os/community/arc/policies/SMF-policy/ for >>>>> addtional details) >>>>> Are there any network services provided by this project? >>>>> [ ] Yes >>>>> [X] No - continue with the next section (section 3.4.2) >>>>> >>>>> Are network services enabled by default? >>>>> [ ] Yes - ARC review required >>>>> [ ] No >>>>> [ ] N/A >>>>> >>>>> Are network services automatically enabled by the project during >>>>> installation? >>>>> [ ] Yes - ARC review required >>>>> [ ] No >>>>> [ ] N/A >>>>> >>>>> Are inbound network communications denied by default? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> [ ] N/A >>>>> >>>>> Is inbound data checked to prevent content-based attacks? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> [ ] N/A >>>>> >>>>> Is the outbound receiver authenticated? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> [ ] N/A >>>>> >>>>> Is the receiver authenticated prior to receiving any sensitive >>>>> outbound communication? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> [ ] N/A >>>>> >>>>> 3.4.2 Authorization >>>>> (see >>>>> http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and >>>>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and >>>>> >>>>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >>>>> for details) >>>>> Are there any setuid/setgid privileged binaries in the project? >>>>> [ ] Yes - ARC review required >>>>> [X] No - continue with next section (section 3.4.3) >>>>> >>>>> If yes then are the setuid/setgid privileges handled by the use >>>>> of roles? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> >>>>> 3.4.3 Auditing >>>>> (see >>>>> http://opensolaris.org/os/community/arc/policies/audit-policy/ for >>>>> details) >>>>> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >>>>> for details) >>>>> Does this component contain administrative or security enforcing >>>>> software? >>>>> [ ] Yes - ARC review required >>>>> [X] No - continue to next section (section 3.4.4) >>>>> >>>>> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >>>>> for details) >>>>> Do the components create audit logs detailing what took place >>>>> including what event >>>>> took place, who was involved, when the event took place? >>>>> [ ] Yes - ARC contract and Audit project team review required >>>>> [ ] No - ARC review required >>>>> >>>>> >>>>> 3.4.4 Authentication >>>>> (see http://opensolaris.org/os/community/arc/policies/PAM/) >>>>> >>>>> Do the components contain any authentication code? >>>>> [ ] Yes >>>>> [X] No - continue to next section (section 3.4.5) >>>>> >>>>> If yes do the components use PAM (plugable authentication >>>>> modules) for authentication? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> >>>>> If yes is a single PAM session maintained during authentication? >>>>> [ ] Yes >>>>> [ ] No - ARC review required >>>>> >>>>> If yes are the components sufficiently privileged to allow the >>>>> requested >>>>> operations (authentication, password change, process credential >>>>> manipulation, >>>>> audit state initialization)? >>>>> [ ] Yes - briefly describe below >>>>> [ ] No - ARC review required >>>>> >>>>> 3.4.5 Passwords >>>>> (see >>>>> http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and >>>>> >>>>> >>>>> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for >>>>> details) >>>>> Do any of the components for the project deal with passwords? >>>>> [ ] 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 >>>>> [ ] 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 >>>>> Dothe 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 >>>>> --------------------------- ------------------- >>>>> --------------------------- >>>>> NetBeans DTrace GUI Committed Package version 0.4 >>>>> >>>>> 4.2 Imported Interfaces >>>>> Interface Name Classification Comments >>>>> --------------------------- -------------------- >>>>> -------------------------- >>>>> NetBeans Committed Package version 6.5 >>>>> >>>>> >>>>> References: >>>>> >>>>> [1] http://www.netbeans.org >>>>> >>>>> >>>>> 6. Resources and Schedule >>>>> 6.4. Steering Committee requested information >>>>> 6.4.1. Consolidation C-team Name: >>>>> u >>>>> 6.5. ARC review type: FastTrack >>>>> 6.6. ARC Exposure: open >>>>> >>>> >>> >> > From Nasser.Nouri@Sun.COM Fri Oct 10 15:28:59 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 m9AMSw1B009284 for ; Fri, 10 Oct 2008 15:28:59 -0700 (PDT) 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 m9AMSvu7001475 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Sat, 11 Oct 2008 06:28:57 +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 <0K8J00H01NS88D00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 10 Oct 2008 16:28:56 -0600 (MDT) Received: from brmea-mail-3.sun.com ([192.18.98.34]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K8J006J9NS7VM50@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 10 Oct 2008 16:28:55 -0600 (MDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m9AMStSI019251 for ; Fri, 10 Oct 2008 22:28:55 +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 <0K8J00A01NOAS700@mail-amer.sun.com> (original mail from Nasser.Nouri@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 10 Oct 2008 16:28:55 -0600 (MDT) Received: from [129.146.85.202] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K8J002BVNRYHB60@mail-amer.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 10 Oct 2008 16:28:54 -0600 (MDT) Date: Fri, 10 Oct 2008 15:28:39 -0700 From: Nasser Nouri Subject: Re: NetBeans DTrace GUI Plug-in [LSARC/2008/620 FastTrack timeout 10/17/2008] In-reply-to: <57F498BD-C449-4D5C-ADE4-12912D1EAE20@sun.com> Sender: Nasser.Nouri@Sun.COM To: Tom Childers Cc: lsarc-ext@Sun.COM, Ivan Vlasyuk Message-id: <48EFD717.6070706@sun.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_9unYD12SOzkVFUiYcbsblg)" X-PMX-Version: 5.4.1.325704 References: <1A52D2E3-6651-4877-B71F-BBA128A83787@sun.com> <48EC16D5.8010202@sun.com> <57F498BD-C449-4D5C-ADE4-12912D1EAE20@sun.com> User-Agent: Thunderbird 2.0.0.6 (X11/20071119) Status: RO Content-Length: 6618 This is a multi-part message in MIME format. --Boundary_(ID_9unYD12SOzkVFUiYcbsblg) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Hi Tom, The one-pager document is updated based on your request. The DTrace Java API (PSARC case 2006/054) is added to the list of interfaces that DTrace GUI uses to communicate with Solaris kernel. 4.5. Interfaces: - NetBeans DTrace GUI Plug-in NBM file. - DTrace Java API: PSARC case 2006/054 The dtrace jar file resides in the following directory: /usr/share/lib/java/dreate.jar The new version of one-pager doc is attached. Thanks, __Nasser --Boundary_(ID_9unYD12SOzkVFUiYcbsblg) Content-type: text/plain; name=dtracegui_onepager.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=dtracegui_onepager.txt Template Version: @(#)onepager.txt 1.35 07/11/07 SMI Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: NetBeans DTrace GUI Plug-in 1.2. Name of Document Author/Supplier: Nasser Nouri (nasser.nouri@sun.com) 1.3. Date of This Document: 09/19/08 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Tools PAC 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Don Kretsch 1.4.4. The name of your business unit: Software Tools 1.5. Email Aliases: 1.5.1. Responsible Manager: vijay.tatkar@sun.com 1.5.2. Responsible Engineer: nasser.nouri@sun.com 1.5.3. Marketing Manager: 1.5.4. Interest List: ivan.vlasyuk@sun.com alexandre.iline@sun.com 2. Project Summary 2.1. Project Description: The NetBeans DTrace GUI Plug-in is a graphical user interface (GUI) for SolarisTM Dynamic Tracing (DTrace). It works with both Sun Studio IDE and NetBeans IDE. For more information please see: http://www.netbeans.org/kb/docs/ide/NetBeans_DTrace_GUI_Plugin_0_4.html 2.2. Risks and Assumptions: Risk Schedule - assuming review and approval time will be 2 weeks, i.e. subission to the LARC on 22-Sep-08, Mon and approval obtained due 3 Oct, Fri. Risk Schedule - the schedule looks tight and does not accomodate any time for correction of possible SVR4-> IPS packages conversion errors. Also it should tried to be done accurately only once and of course there is a risk on how long the conversion time would take NB/OS teams. 3. Business Summary The NetBeans DTrace GUI Plug-in enables users to utilize DTrace in Solaris environment without learning D language. Users can run D scripts and visualize the output of D scripts with a few mouse clicks in Netbeans or Sun Studio IDE. 3.1. Problem Area: DTrace is a comprehensive tracing facility built into the Solaris Operating System that can be used by developers and administrators on live production systems to examine the behavior of both user programs and of the operating system itself. However, users are required to learn D language before they can utilize DTrace. This may become a problematic issue for some users. 3.2. Market/Requester: OpenSolaris, Netbeans, and Sun Studio communities. 3.3. Business Justification: Attracting developers, users, and university students to learn about Sun's technologies such as OpenSolaris, NetBeans and Sun Studio. 3.4. Competitive Analysis: Apple Instruments (former XRay) is a Graphical User Interface (GUI) for DTrace on Mac. OpenSolaris requires a similar GUI for DTrace in order to stay competitive in the market. 3.5. Opportunity Window/Exposure: Target is to be included into OS 2008.11 repository together with NB 6.5 in October timeframe. 3.6. How will you know when you are done?: The version 0.4 is already released and can be downloaded from NetBeans Update Center. When the following version is kept in the OS 2008.11 repositorium 4. Technical Description: 4.1. Details: The NetBeans DTrace GUI Plug-in is an open-source project in NetBeans.org. 4.2. Bug/RFE Number(s): None. 4.3. In Scope: Application (and system) performance tuning and debugging in OpenSolaris. 4.4. Out of Scope: 4.5. Interfaces: - NetBeans DTrace GUI Plug-in NBM file. - DTrace Java API: PSARC case 2006/054 The dtrace jar file resides in the following directory: /usr/share/lib/java/dreate.jar 4.6. Doc Impact: 4.7. Admin/Config Impact: No impact. 4.8. HA Impact: N/A 4.9. I18N/L10N Impact: It uses NetBeans localization modules and implementation. 4.10. Packaging & Delivery: One package: NetBeans DTrace GUI version 0.4. 4.11. Security Impact: None. 4.12. Dependencies: NetBeans IDE and Sun Studio IDE. 5. Reference Documents: http://www.netbeans.org/kb/docs/ide/NetBeans_DTrace_GUI_Plugin_0_4.html 6. Resources and Schedule: 6.1. Projected Availability: The NetBeans DTrace GUI Plug-in can be download from NetBeans Update Center. 6.2. Cost of Effort: N/A 6.3. Cost of Capital Resources: N/A 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: NetBeans DTrace GUI Plug-in 6.4.3. Type of CPT Review and Approval expected: FastTrack 6.4.4. Project Boundary Conditions: 6.4.5. Is this a necessary project for OEM agreements: N/A 6.4.6. Notes: 6.4.7. Target RTI Date/Release: October 13, 2008 6.4.8. Target Code Design Review Date: 6.4.9. Update approval addition: 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open 6.6.1. Rationale: 7. Prototype Availability: 7.1. Prototype Availability: The NetBeans DTrace GUI Plug-in can be download from NetBeans Update Center. 7.2. Prototype Cost: N/A --Boundary_(ID_9unYD12SOzkVFUiYcbsblg)--