From tom.childers@sun.com Tue Nov 25 15:12:00 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 mAPNBMwn026147 for ; Tue, 25 Nov 2008 15:11:30 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mAPNBK9U003520 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Tue, 25 Nov 2008 16:11:22 -0700 (MST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KAW00407WEWZG00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 25 Nov 2008 16:11:20 -0700 (MST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAW00HNGWEP6Q70@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 25 Nov 2008 16:11:18 -0700 (MST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mAPNB9pB004623 for ; Tue, 25 Nov 2008 15:11:09 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KAW00901WDFHA00@fe-sfbay-09.sun.com> (original mail from tom.childers@sun.com) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 25 Nov 2008 15:11:09 -0800 (PST) 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 <0KAW0053BWEJ8OA0@fe-sfbay-09.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 25 Nov 2008 15:11:08 -0800 (PST) Date: Tue, 25 Nov 2008 15:11:03 -0800 From: Tom Childers Subject: PowerMan 2.3 [LSARC/2008/734 FastTrack timeout 12/4/2008] Sender: Thomas.Childers@sun.com To: lsarc-ext@sun.com Cc: Bruce Rothermal Message-id: <4799AA23-FA7F-4DC9-85B5-840DCA0016BA@sun.com> MIME-version: 1.0 X-Mailer: Apple Mail (2.929.2) Content-type: multipart/alternative; boundary="Boundary_(ID_IkmFcU06QXdI9JUe3TVCfA)" X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 33123 --Boundary_(ID_IkmFcU06QXdI9JUe3TVCfA) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT I'm sponsoring this case, with a time-out next Thursday to account for the US holiday this week. I've already asked about security issues, since PowerMan establishes a TCP/IP listener. Bruce Rothermal reports that the listener is not active by default; it requires configuration after installation. Furthermore, the project lead says: "Powerman has no authentication between client and server. This is a limitation that should probably be made more explicit in the documentation. What we do at Livermore is run the powerman daemon on a management node that only privileged users have access to, and then lock it down with firewall software so only localhost is permitted to connect to the daemon (in other words powerman and powermand must run on the same host)." Bruce concludes that security depends on how the user configures the system. I think this is consistent with all other products that establish listeners :-) Tom Childers Sr. Staff Engineer Sun Microsystems, Inc. SOA/Business Integration Engineering Phone x31943/+1 415-226-3398 Mobile +1 415-272-3565 Fax +1 415-226-3398 Email Tom.Childers@Sun.COM 1.0 Project Information 1.1 Name of project/component PowerMan 2.3 1.2 Author of document Bruce Rothermal 2.0 Project Summary 2.1 Project Description Port PowerMan Opensource utility to SFW consolidation. 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 PowerMan http://sourceforge.net/projects/powerman 2.4.2 Community Involvement Indicate Sun's involvement in the community [ ] Maintainer [x ] 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]? [x ] Yes [ ] No or N/A Does this project install into /opt? [ ] Yes - explain below [x ] No or N/A Does this project install into a different directory structure? [ ] Yes - ARC review required [x ] No or N/A Do any of the components of this project conflict with anything under /usr? (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) [ ] Yes - explain below [x ] No If conflicts exist then will this project install under /usr/gnu? [ ] Yes [ ] No - ARC review required [x ] N/A Is this project installing into /usr/sfw? [ ] Yes - ARC review required [x ] No 3.1.1W Windows Installation - section only required for Windows Software (see http://sac.sfbay/WSARC/2002/494 for details) Does this project install software into a :\Program Files\Sun\ or :\Sun \ directory? [ ] Yes [ ] No - ARC review required Does the project use the Windows registry? [ ] Yes [ ] No - ARC review required Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ for the registry key? [ ] Yes [ ] No - ARC review required Is the project's stored location HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? [ ] Yes [ ] No - ARC review required 3.1.2 Share and Sharable Does the module include any components that are used or shared by other projects? [ ] Yes [x ] No If yes are these components packaged to be shared with the other FOSS? [ ] Yes [ ] No - ARC review required [x ] N/A Are these components already in the Solaris WOS? [ ] Yes [x ] No - continue with next section (section 3.2) If yes are these newer versions being delivered? [ ] Yes [ ] No - ARC review required If yes are the newer versions replacing the existing versions? [ ] Yes [ ] No - ARC review required 3.2 Exported Libraries Are libraries being delivered by this project? [ ] 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? [x ] Yes - ARC review required [ ] 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? [x ] Yes - ARC review required [ ] No Installs its own configuration directory /etc/powerman Does the service manifests method context grant rights above that of the noaccess user and basic privilege set? [ ] Yes - ARC review required [x ] No I don't believe so. It is not installed as a service. 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? [x ] Yes [ ] No - continue with the next section (section 3.4.2) Are network services enabled by default? [ ] Yes - ARC review required [x ] No [ ] N/A Are network services automatically enabled by the project during installation? [ ] Yes - ARC review required [x ] No [ ] N/A Are inbound network communications denied by default? [ ] Yes [ ] No - ARC review required [ ] N/A Need clarification on question. Server/Daemon software does not function by default install. It must be specifically configured and can be setup with trusted hosts configuration. Is inbound data checked to prevent content-based attacks? [ ] Yes [ ] No - ARC review required [ ] N/A Don't know at this time. Is the outbound receiver authenticated? [ ] Yes [ ] No - ARC review required [ ] N/A Not sure how to answer this. It does an RPC type function. Server/ Daemon responds only with result code to request. Is the receiver authenticated prior to receiving any sensitive outbound communication? [ ] Yes [x ] No - ARC review required [ ] N/A Receiving is only done as a response to an RPC request. Request can be controlled by trusted host functionality. 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? [x ] Yes [ ] No - continue with the next section (section 3.5) Do the components use standard network protocols? [x ] Yes [ ] No - ARC review required Do network services for the project make decisions based upon user, host or service identities? [ ] Yes - explain below [x ] No [ ] N/A Do the components make use of secret information during authentication and/or authorization? [ ] Yes - explain below [x ] No [ ] N/A 3.5 Networking Do the components access the network? [x ] Yes [ ] No - continue with the next section (section 3.6) If yes do the components support IPv6? [x ] Yes [ ] No - ARC review required 3.6 Core Solaris Components Do the components of this project compete with or duplicate core Solaris components? [ ] Yes - ARC review required [x ] No Examples of Core Solaris Components include but are not limited to: Secure By Default Authorizations PAM -- Plugable Authentication Module Privilege PRM -- Process Rights Management -- Privilege Audit xVm -- Virtualization zones / Solaris Containers PRM -- Process Rights Management RBAC -- Role Based Access Control TX / Trusted Extensions ZFS SMF -- Service Management Facility FMA -- Fault Management Architecture SCF -- Smart Card Facility IPsec 4.0 Interfaces (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details) 4.1 Exported Interfaces Interface Name Classification Comments --------------------------- ------------------- --------------------------- 4.2 Imported Interfaces Interface Name Classification Comments --------------------------- -------------------- -------------------------- Powerman Volatile version 2.3 > --Boundary_(ID_IkmFcU06QXdI9JUe3TVCfA) Content-type: text/html; charset=US-ASCII Content-transfer-encoding: QUOTED-PRINTABLE I'm sponsoring this case, w= ith a time-out next Thursday to account for the US holiday this week.=

I've already asked about security issues, since P= owerMan establishes a TCP/IP listener. Bruce Rothermal reports that t= he listener is not active by default; it requires configuration after= installation. Furthermore, the project lead says: 
"Powerman has no authentication between client and serve= r. This is a limitation that should probably be made more explicit in= the documentation.  What we do at Livermore is run the powerman= daemon on a management node that only privileged users have access t= o, and then lock it down with firewall software so only localhost is = permitted to connect to the daemon (in other words powerman and power= mand must run on the same host)."

Bruce conc= ludes that security depends on how the user configures the system. I = think this is consistent with all other products that establish liste= ners :-)


Tom Childers
Sr. Staff Engineer

Sun Microsystems, Inc.
= SOA/Business Integration Engineering
Phone x31943/+1 415-226-3398=
Mobile +1 415-272-3565
Fax +1 415-226-3398
Email Tom.Childers@Sun.COM


=
1.0 Project Information
1.1 Name of project/compone= nt

PowerMan 2.3

1.2 Author of document

Bruce Rot= hermal

2.0 Project Summary
2.1 Project Description

P= ort PowerMan Opensource utility to SFW consolidation.

2.2 Rele= ase binding
   What is is the release binding?
&= nbsp;  (see http://opensolaris.org/os/commu= nity/arc/policies/release-taxonomy/)
   [X ] Ma= jor
   [ ] Minor
   [ ] Patch or = Micro
   [ ] Unknown -- ARC review required

= 2.3 Type of project
   Is this case a Linux Familia= rity project?
   [ ] Yes
   [x ] = No

2.4 Originating Community
 2.4.1 Community Name
=
PowerMan
= http://sourceforge.net/projects/powerman

 2.4.2 Commu= nity Involvement
   Indicate Sun's involvement in t= he community
   [ ] Maintainer
   = ;[x ] Contributor
   [ ] Monitoring

 &n= bsp; Will the project team work with the upstream community to r= esolve
   architectural issues of interest to Sun?<= br>   [x ] Yes
   [ ] No - briefly e= xplain

   Will we or are we forking from the co= mmunity?
   [ ] Yes - ARC review required prior to = forking
   [x ] No

3.0 Technical Description=
3.1 Installation & Sharable
 3.1.1S Solaris Installat= ion - section only required for Solaris Software
   = ;(see http://opensolaris.org/os/community/arc/policie= s/install-locations/ for details)
   Does = this project follow the Install Locations best practice?
 &nb= sp; [x ] Yes
   [ ] No - ARC review required
   Does this project install into /usr under [sb= in|bin|lib|include|man|share]?
   [x ] Yes
 = ;  [ ] No or N/A

   Does this project= install into /opt?
   [ ] Yes - explain below
&= nbsp;  [x ] No or N/A

   Does this pr= oject install into a different directory structure?
  &n= bsp;[ ] Yes - ARC review required
   [x ] No or N/A=

   Do any of the components of this project co= nflict with anything under /usr?
   (see http= ://opensolaris.org/os/community/arc/caselog/2007/047/ for de= tails)
   [ ] Yes - explain below
  &n= bsp;[x ] No

   If conflicts exist then will thi= s project install under /usr/gnu?
   [ ] Yes
&nb= sp;  [ ] No - ARC review required
   [x ]= N/A

   Is this project installing into /usr/sf= w?
   [ ] Yes - ARC review required
  =  [x ] No

 3.1.1W Windows Installation - section only= required for Windows Software
   (see http://sac.sfbay/WSARC/2002/494<= /a> for details)
   Does this project install = software into a
   <system drive>:\Program Files= \Sun\<product> or <system drive>:\Sun\<product>
 &nb= sp; directory?
   [ ] Yes
   = ;[ ] No - ARC review required

   Does the proje= ct use the Windows registry?
   [ ] Yes
 &n= bsp; [ ] No - ARC review required

   Does = the project use
   HKEY_LOCAL_MACHINE\SOFTWARE\Sun = Microsystems\<product>\<version>
   for the r= egistry key?
   [ ] Yes
   [ ] No= - ARC review required

   Is the project's stor= ed location
   HKEY_LOCAL_MACHINE\SOFTWARE\Sun Micr= osystems\<product id>\<version id>\Path?
   [= ] Yes
   [ ] No - ARC review required

 = ;3.1.2 Share and Sharable
   Does the module includ= e any components that are used or shared by
   othe= r projects?
   [ ] Yes
   [x ] No=

   If yes are these components packaged to be = shared with the other FOSS?
   [ ] Yes
 &nb= sp; [ ] No - ARC review required
   [x ] N/A
   Are these components already in the Solaris W= OS?
   [ ] Yes
   [x ] No - conti= nue with next section (section 3.2)

   If yes a= re these newer versions being delivered?
   [ ] Yes=
   [ ] No - ARC review required

  = ; If yes are the newer versions replacing the existing versions?=
   [ ] Yes
   [ ] No - ARC revie= w required

3.2 Exported Libraries
   Are lib= raries being delivered by this project?
   [ ] Yes<= br>   [x ] No - continue with next section (section 3.= 3)

   Are 64-bit versions of the libraries bein= g delivered?
   [ ] Yes
   [ ] No= - ARC review required

   Are static versions o= f the libraries being delivered?
   [ ] Yes - ARC r= eview required
   [ ] No

3.3 Services and th= e /etc Directory
   (see http://opensolar= is.org/os/community/arc/policies/SMF-policy/)
  &nbs= p;Does the project integrate anything into /etc/init.d or /etc/rc?.d?=
   [x ] Yes - ARC review required
  &= nbsp;[ ] No

   Does the project integrate any n= ew entries into /etc/inittab or
   /etc/inetd.conf?=
   [ ] Yes - ARC review required
  &n= bsp;[X ] No

   Does the project integrate any p= rivate non-public files into /etc/default
   or /et= c/ configuration files?
   [x ] Yes - ARC review re= quired
   [ ] No

Installs its own configurat= ion directory /etc/powerman

   Does the service= manifests method context grant rights above that
  &nbs= p;of the noaccess user and basic privilege set?
   = [ ] Yes - ARC review required
   [x ] No

I d= on't believe so. It is not installed as a service.

3.4 Securit= y
 3.4.1 Secure By Default
   (see http://opensolaris.org/os/community/arc/policies/secure-by-de= fault/ for details)
   (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details)
   (see parts of htt= p://opensolaris.org/os/community/arc/policies/SMF-policy/ fo= r
    addtional details)
   = Are there any network services provided by this project?
 &nb= sp; [x ] Yes
   [ ] No - continue with the nex= t section (section 3.4.2)

   Are network servic= es enabled by default?
   [ ] Yes - ARC review requ= ired
   [x ] No
   [ ] N/A
   Are network services automatically enabled by the = project during installation?
   [ ] Yes - ARC revie= w required
   [x ] No
   [ ] N/A<= br>
   Are inbound network communications denied by= default?
   [ ] Yes
   [ ] No - = ARC review required
   [ ] N/A

Need clarific= ation on question. Server/Daemon software does not function by defaul= t install. It must be specifically configured and can be setup with t= rusted hosts configuration.

   Is inbound data = checked to prevent content-based attacks?
   [ ] Ye= s
   [ ] No - ARC review required
  &n= bsp;[ ] N/A
Don't know at this time.

   Is t= he outbound receiver authenticated?
   [ ] Yes
&= nbsp;  [ ] No - ARC review required
   [ = ] N/A

Not sure how to answer this. It does an RPC type functio= n. Server/Daemon responds only with result code to request.

&n= bsp;  Is the receiver authenticated prior to receiving any = sensitive outbound communication?
   [ ] Yes
&nb= sp;  [x ] No - ARC review required
   [ ]= N/A

Receiving is only done as a response to an RPC request. R= equest can be controlled by trusted host functionality.

 = 3.4.2 Authorization
   (see http://op= ensolaris.org/os/community/arc/bestpractices/rbac-intro/ and=
=09   http://opensolaris.org/os/communit= y/arc/bestpractices/rbac-profiles/ and
=09   = ;http://opensolaris.org/os/community/arc/bestpractices/rb= ac-profiles/
        f= or details)
   Are there any setuid/setgid privileg= ed binaries in the project?
   [ ] Yes - ARC review= required
   [x ] No - continue with next section (= section 3.4.3)

   If yes then are the setuid/se= tgid 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 cre= ate audit logs detailing what took place including what event
&nbs= p;  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?
 &nb= sp; [ ] Yes
   [x ] No - continue to next sect= ion (section 3.4.5)

   If yes do the components= use PAM (plugable authentication modules) for authentication?
&nb= sp;  [ ] Yes
   [ ] No - ARC review requi= red

   If yes is a single PAM session maintaine= d during authentication?
   [ ] Yes
  =  [ ] No - ARC review required

   If yes ar= e the components sufficiently privileged to allow the requested
&n= bsp;  operations (authentication, password change, process = credential manipulation,
   audit state initializat= ion)?
   [ ] Yes - briefly describe below
 =   [ ] No - ARC review required

 3.4.5 Passwords=
   (see http://opensolaris.org/os= /community/arc/bestpractices/passwords-cli/ and
 &nb= sp;      http://opensolar= is.org/os/community/arc/bestpractices/passwords-files/ for d= etails)
   Do any of the components for the project= deal with passwords?
   [ ] Yes
  &nb= sp;[x ] No - continue to next section (section 3.4.6)

 &n= bsp; If yes are these passwords entered via the CLI or environme= nt?
   [ ] Yes - ARC review required
  = ; [ ] No

   Are passwords stored within th= e file system for the component?
   [ ] Yes
&nbs= p;  [ ] No - continue to next section (section 3.4.6)
   If yes are the permissions on the file such to pr= otect exposing the password(s)?
   [ ] Yes
 = ;  [ ] No - ARC review required

 3.4.6 General = Security Questions
   (see ht= tp://opensolaris.org/os/community/arc/bestpractices/security-question= s/ for details)
   Are there any network p= rotocols used by this project?
   [x ] Yes
 = ;  [ ] No - continue with the next section (section 3.5)
   Do the components use standard network protoco= ls?
   [x ] Yes
   [ ] No - ARC r= eview required

   Do network services for the p= roject make decisions based upon user, host or
   s= ervice identities?
   [ ] Yes - explain below
&n= bsp;  [x ] No
   [ ] N/A


 = ;  Do the components make use of secret information during = authentication and/or
   authorization?
 &n= bsp; [ ] Yes - explain below
   [x ] No
&nb= sp;  [ ] N/A

3.5 Networking
   Do = the components access the network?
   [x ] Yes
&= nbsp;  [ ] No - continue with the next section (section 3.6= )

   If yes do the components support IPv6?
=    [x ] Yes
   [ ] No - ARC review r= equired

3.6 Core Solaris Components
   Do th= e components of this project compete with or duplicate core
 =   Solaris components?
   [ ] Yes - ARC re= view required
   [x ] No

   E= xamples of Core Solaris Components include but are not limited to:
     Secure By Default
  &= nbsp;  Authorizations
     PAM = -- Plugable Authentication Module
     Pr= ivilege
     PRM -- Process Rights Manage= ment -- Privilege
     Audit
 &nb= sp;   xVm -- Virtualization
    = ; zones / Solaris Containers
     PR= M -- Process Rights Management
     RBAC = -- Role Based Access Control
     TX / Tr= usted Extensions
     ZFS
  =    SMF -- Service Management Facility
  &= nbsp;  FMA -- Fault Management Architecture
  =    SCF -- Smart Card Facility
   &nb= sp; IPsec

4.0 Interfaces
(see htt= p://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/=  for details)
4.1 Exported Interfaces

 Interf= ace Name= =09=09Classification      Comments
&= nbsp;--------------------------- ------------------- ----------------= -----------


4.2 Imported Interfaces
 Interface Nam= e=09=09Classification       Comments
&nb= sp;--------------------------- -------------------- -----------------= ---------
 Powerman=09=09=09    Volatile &n= bsp;          versi= on 2.3


= --Boundary_(ID_IkmFcU06QXdI9JUe3TVCfA)-- From Alan.Coopersmith@sun.com Tue Nov 25 15:31:31 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 mAPNVQal025902 for ; Tue, 25 Nov 2008 15:31:31 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mAPNUtP2015195 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Tue, 25 Nov 2008 16:31:26 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KAW00M0JXCD3W00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 25 Nov 2008 15:31:25 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAW002GAXCCYFB0@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 25 Nov 2008 15:31:24 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mAPNVO1X006989 for ; Tue, 25 Nov 2008 15:31:24 -0800 (PST) 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 <0KAW00001X952D00@fe-sfbay-10.sun.com> (original mail from Alan.Coopersmith@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 25 Nov 2008 15:31:24 -0800 (PST) Received: from almas.sfbay.sun.com ([129.146.106.93]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KAW00FQ5XC7BH20@fe-sfbay-10.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Tue, 25 Nov 2008 15:31:19 -0800 (PST) Date: Tue, 25 Nov 2008 15:31:19 -0800 From: Alan Coopersmith Subject: Re: PowerMan 2.3 [LSARC/2008/734 FastTrack timeout 12/4/2008] In-reply-to: <4799AA23-FA7F-4DC9-85B5-840DCA0016BA@sun.com> Sender: Alan.Coopersmith@sun.com To: Tom Childers Cc: lsarc-ext@sun.com, Bruce Rothermal Message-id: <492C8AC7.3000702@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 X-Enigmail-Version: 0.95.1 References: <4799AA23-FA7F-4DC9-85B5-840DCA0016BA@sun.com> User-Agent: Thunderbird 2.0.0.17 (X11/20081014) Status: RO Content-Length: 963 Tom Childers wrote: > 2.2 Release binding > What is is the release binding? > (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) > [X ] Major What incompatible change does this make that requires a Major release? (I think the checklist should actually be updated to specify "ARC review required" for Major - while Solaris/OpenSolaris has been opened to limited Major release changes, they are still limited, and we should know exactly what they all are. For most FOSS cases that qualify for using the checklist, "Major" simply indicates a misunderstanding of the question - adding completely new software should normally be "Patch or Micro", and cases should choose the smallest release binding possible, to avoid needless re-review if someone ever has a business case to backport to a previous release.) -- -Alan Coopersmith- alan.coopersmith@sun.com Sun Microsystems, Inc. - X Window System Engineering From carlsonj@phorcys.east.sun.com Wed Nov 26 05:05:33 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 mAQD5WDd015759 for ; Wed, 26 Nov 2008 05:05:33 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id mAQD5MSR005618; Wed, 26 Nov 2008 21:05:29 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KAX00M01Z13WH00@nwk-avmta-2.sfbay.sun.com>; Wed, 26 Nov 2008 05:05:27 -0800 (PST) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAX00IZSZ12ZH30@nwk-avmta-2.sfbay.sun.com>; Wed, 26 Nov 2008 05:05:27 -0800 (PST) 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 mAQD5Qol024558; Wed, 26 Nov 2008 08:05:26 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id mAQD5Qro024555; Wed, 26 Nov 2008 08:05:26 -0500 (EST) Date: Wed, 26 Nov 2008 08:05:26 -0500 From: James Carlson Subject: Re: PowerMan 2.3 [LSARC/2008/734 FastTrack timeout 12/4/2008] In-reply-to: <4799AA23-FA7F-4DC9-85B5-840DCA0016BA@sun.com> To: Tom Childers Cc: lsarc-ext@sun.com, Bruce Rothermal Message-id: <18733.18838.721595.384416@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: <4799AA23-FA7F-4DC9-85B5-840DCA0016BA@sun.com> Status: RO Content-Length: 1055 Tom Childers writes: > I'm sponsoring this case, with a time-out next Thursday to account for > the US holiday this week. > > I've already asked about security issues, since PowerMan establishes a > TCP/IP listener. Bruce Rothermal reports that the listener is not > active by default; it requires configuration after installation. > Furthermore, the project lead says: Sigh; another telnet wannabe. :-/ The way something like this is often used is to set up the server so that it's bound to 127.0.0.1, and then use ssh to access the server system and invoke the client. That dodge fixes the security problem. That aside, this sounds like it's related to conserver (http://conserver.com/). Do we have anyone working on that? It'd be really nice to see these two things integrated together and delivered on Solaris. -- 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 Danek.Duvall@sun.com Wed Nov 26 08:21:22 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 mAQGLMqe006942 for ; Wed, 26 Nov 2008 08:21:22 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mAQGL31a027844; Wed, 26 Nov 2008 16:21:20 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KAY0000V83I3F00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 26 Nov 2008 08:21:18 -0800 (PST) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAY00GO783HN140@nwk-avmta-1.sfbay.Sun.COM>; Wed, 26 Nov 2008 08:21:17 -0800 (PST) Received: from mumak.SFBay.Sun.COM (mumak.SFBay.Sun.COM [129.146.229.4]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mAQGLHQx008785; Wed, 26 Nov 2008 08:21:17 -0800 (PST) Received: from mumak.SFBay.Sun.COM (mumak [127.0.0.1]) by mumak.SFBay.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id mAQGMkOd007370; Wed, 26 Nov 2008 08:22:46 -0800 (PST) Received: (from dduvall@localhost) by mumak.SFBay.Sun.COM (8.14.3+Sun/8.14.3/Submit) id mAQGMkaV007369; Wed, 26 Nov 2008 08:22:46 -0800 (PST) Date: Wed, 26 Nov 2008 08:22:46 -0800 From: Danek Duvall Subject: Re: PowerMan 2.3 [LSARC/2008/734 FastTrack timeout 12/4/2008] In-reply-to: <4799AA23-FA7F-4DC9-85B5-840DCA0016BA@sun.com> To: Tom Childers Cc: lsarc-ext@sun.com, Bruce Rothermal Message-id: <20081126162246.GY3046@mumak.SFBay.Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <4799AA23-FA7F-4DC9-85B5-840DCA0016BA@sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 109 So in all of this, there's no description of what powerman actually *is*. Or what the interfaces are. Danek From carlsonj@phorcys.east.sun.com Wed Nov 26 09:14:50 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 mAQHEoCO008129 for ; Wed, 26 Nov 2008 09:14:50 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mAQHEmJo035505; Wed, 26 Nov 2008 10:14:49 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KAY00E13AKOUP00@nwk-avmta-2.sfbay.sun.com>; Wed, 26 Nov 2008 09:14:48 -0800 (PST) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KAY008Y1AKNL080@nwk-avmta-2.sfbay.sun.com>; Wed, 26 Nov 2008 09:14:47 -0800 (PST) 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 mAQHElJ0025441; Wed, 26 Nov 2008 12:14:47 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id mAQHElkN025438; Wed, 26 Nov 2008 12:14:47 -0500 (EST) Date: Wed, 26 Nov 2008 12:14:47 -0500 From: James Carlson Subject: Re: PowerMan 2.3 [LSARC/2008/734 FastTrack timeout 12/4/2008] In-reply-to: <20081126162246.GY3046@mumak.SFBay.Sun.COM> To: Danek Duvall Cc: Tom Childers , Bruce Rothermal , LSARC-ext@sun.com Message-id: <18733.33799.98981.585909@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: <4799AA23-FA7F-4DC9-85B5-840DCA0016BA@sun.com> <20081126162246.GY3046@mumak.SFBay.Sun.COM> Status: RO Content-Length: 489 Danek Duvall writes: > So in all of this, there's no description of what powerman actually *is*. It centralizes control of power control units, often used in a lab, much in the way conserver centralizes console servers. > Or what the interfaces are. Good point. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Bruce.Rothermal@sun.com Mon Dec 1 08:25:52 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 mB1GPqFL018158 for ; Mon, 1 Dec 2008 08:25:52 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mB1GPplX043572 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Mon, 1 Dec 2008 09:25:52 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KB700229HN3ES00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 01 Dec 2008 08:25:51 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KB700ASIHN38PD0@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 01 Dec 2008 08:25:51 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mB1GPpXY024336 for ; Mon, 01 Dec 2008 08:25:51 -0800 (PST) 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 <0KB700G01HD8NT00@fe-sfbay-10.sun.com> (original mail from Bruce.Rothermal@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 01 Dec 2008 08:25:51 -0800 (PST) Received: from [192.168.1.101] ([75.71.129.47]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KB700CKJHMLA730@fe-sfbay-10.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 01 Dec 2008 08:25:34 -0800 (PST) Date: Mon, 01 Dec 2008 09:25:33 -0700 From: Bruce Rothermal Subject: Re: PowerMan 2.3 [LSARC/2008/734 FastTrack timeout 12/4/2008] In-reply-to: <492C8AC7.3000702@sun.com> Sender: Bruce.Rothermal@sun.com To: Alan Coopersmith Cc: Tom Childers , lsarc-ext@sun.com Message-id: MIME-version: 1.0 X-Mailer: Apple Mail (2.929.2) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <4799AA23-FA7F-4DC9-85B5-840DCA0016BA@sun.com> <492C8AC7.3000702@sun.com> Status: RO Content-Length: 1156 Changing it to "Patch or Micro". It was a misunderstanding of the question. Bruce On Nov 25, 2008, at 4:31 PM, Alan Coopersmith wrote: > Tom Childers wrote: >> 2.2 Release binding >> What is is the release binding? >> (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >> [X ] Major > > What incompatible change does this make that requires a Major release? > > (I think the checklist should actually be updated to specify "ARC > review > required" for Major - while Solaris/OpenSolaris has been opened to > limited > Major release changes, they are still limited, and we should know > exactly > what they all are. For most FOSS cases that qualify for using the > checklist, > "Major" simply indicates a misunderstanding of the question - adding > completely > new software should normally be "Patch or Micro", and cases should > choose the > smallest release binding possible, to avoid needless re-review if > someone ever > has a business case to backport to a previous release.) > > -- > -Alan Coopersmith- alan.coopersmith@sun.com > Sun Microsystems, Inc. - X Window System Engineering > From Bruce.Rothermal@sun.com Mon Dec 1 08:53:03 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 mB1Gr22S018472 for ; Mon, 1 Dec 2008 08:53:03 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mB1GqwZ7021545 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 1 Dec 2008 16:53:01 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KB700E07IWCKR00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Mon, 01 Dec 2008 08:53:00 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KB700E48IWBIP00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Mon, 01 Dec 2008 08:52:59 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mB1GqxGs012387 for ; Mon, 01 Dec 2008 08:52:59 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KB700L01INU3000@fe-sfbay-09.sun.com> (original mail from Bruce.Rothermal@Sun.COM) for LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Mon, 01 Dec 2008 08:52:59 -0800 (PST) Received: from [192.168.1.101] ([75.71.129.47]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KB700JT5IVYNX20@fe-sfbay-09.sun.com>; Mon, 01 Dec 2008 08:52:47 -0800 (PST) Date: Mon, 01 Dec 2008 09:52:46 -0700 From: Bruce Rothermal Subject: Re: PowerMan 2.3 [LSARC/2008/734 FastTrack timeout 12/4/2008] In-reply-to: <18733.33799.98981.585909@gargle.gargle.HOWL> Sender: Bruce.Rothermal@sun.com To: James Carlson Cc: Danek Duvall , Tom Childers , LSARC-ext@sun.com Message-id: MIME-version: 1.0 X-Mailer: Apple Mail (2.929.2) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <4799AA23-FA7F-4DC9-85B5-840DCA0016BA@sun.com> <20081126162246.GY3046@mumak.SFBay.Sun.COM> <18733.33799.98981.585909@gargle.gargle.HOWL> Status: RO Content-Length: 1784 Lets see if I can explain this better and you all can let me know how much of this to put in the questionare. Powerman consists of a client and server process for the purpose of consolidating power management (turn systems on and off as found in a lab environment or remote unmanned dark equipment rooms). A user would login to the system. In this case a Solaris system which provides all the security within the OS and protocols such as ssh. The user runs the client program powerman with options specifying the name of the device to turn on or off and the command of on or off. It can also request status. This client sends the RPC request to the server and the server spawns off a process to handle this request. The server side is configured with information about the devices it manages how they are interacted with (terminal or proprietary protocol, serial line or network connection). The server uses specialized scripts similar to expect functionality to then communicate with the device to power it on or off. This communication is configured to be done over point to point connections or private sub networks. Hope this makes things clearer. Thank you Bruce On Nov 26, 2008, at 10:14 AM, James Carlson wrote: > Danek Duvall writes: >> So in all of this, there's no description of what powerman actually >> *is*. > > It centralizes control of power control units, often used in a lab, > much in the way conserver centralizes console servers. > >> Or what the interfaces are. > > Good point. > > -- > 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 danek.duvall@sun.com Mon Dec 1 09:14:41 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 mB1HEfqv019211 for ; Mon, 1 Dec 2008 09:14:41 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mB1HEJbV006678; Mon, 1 Dec 2008 17:14:38 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KB700F15JWDNI00@nwk-avmta-2.sfbay.sun.com>; Mon, 01 Dec 2008 09:14:37 -0800 (PST) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KB700EK5JWDIV30@nwk-avmta-2.sfbay.sun.com>; Mon, 01 Dec 2008 09:14:37 -0800 (PST) Received: from mumak.SFBay.Sun.COM (mumak.SFBay.Sun.COM [129.146.229.4]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mB1HEblh022183; Mon, 01 Dec 2008 09:14:37 -0800 (PST) Received: from mumak.SFBay.Sun.COM (mumak [127.0.0.1]) by mumak.SFBay.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id mB1HG8tj021699; Mon, 01 Dec 2008 09:16:08 -0800 (PST) Received: (from dduvall@localhost) by mumak.SFBay.Sun.COM (8.14.3+Sun/8.14.3/Submit) id mB1HG84w021698; Mon, 01 Dec 2008 09:16:08 -0800 (PST) Date: Mon, 01 Dec 2008 09:16:08 -0800 From: Danek Duvall Subject: Re: PowerMan 2.3 [LSARC/2008/734 FastTrack timeout 12/4/2008] In-reply-to: To: Bruce Rothermal Cc: James Carlson , Tom Childers , LSARC-ext@sun.com Message-id: <20081201171608.GB19872@mumak.SFBay.Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <4799AA23-FA7F-4DC9-85B5-840DCA0016BA@sun.com> <20081126162246.GY3046@mumak.SFBay.Sun.COM> <18733.33799.98981.585909@gargle.gargle.HOWL> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 322 On Mon, Dec 01, 2008 at 09:52:46AM -0700, Bruce Rothermal wrote: > Hope this makes things clearer. Yes, thanks. But we still need interfaces -- command names, paths, package names, SMF FMRIs, port numbers, environment variables -- and their stability levels. Your sponsor can help you figure those out. Thanks, Danek From carlsonj@phorcys.east.sun.com Mon Dec 1 09:26:12 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 mB1HQCsL019448 for ; Mon, 1 Dec 2008 09:26:12 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mB1HQ9hx003634; Mon, 1 Dec 2008 09:26:11 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KB700G0TKFMFK00@nwk-avmta-2.sfbay.sun.com>; Mon, 01 Dec 2008 09:26:10 -0800 (PST) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KB700EUPKFKIP40@nwk-avmta-2.sfbay.sun.com>; Mon, 01 Dec 2008 09:26:08 -0800 (PST) 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 mB1HQ8tT003221; Mon, 01 Dec 2008 12:26:08 -0500 (EST) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id mB1HQ7Vo003218; Mon, 01 Dec 2008 12:26:07 -0500 (EST) Date: Mon, 01 Dec 2008 12:26:07 -0500 From: James Carlson Subject: Re: PowerMan 2.3 [LSARC/2008/734 FastTrack timeout 12/4/2008] In-reply-to: To: Bruce Rothermal Cc: Danek Duvall , Tom Childers , LSARC-ext@sun.com Message-id: <18740.7727.959223.801767@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: <4799AA23-FA7F-4DC9-85B5-840DCA0016BA@sun.com> <20081126162246.GY3046@mumak.SFBay.Sun.COM> <18733.33799.98981.585909@gargle.gargle.HOWL> Status: RO Content-Length: 2385 Bruce Rothermal writes: > Lets see if I can explain this better and you all can let me know how > much of this to put in the questionare. > > Powerman consists of a client and server process for the purpose of > consolidating power management (turn systems on and off as found in a > lab environment or remote unmanned dark equipment rooms). A user would [...] That explains what it does, but not what the interfaces are, which was the previous question: > On Nov 26, 2008, at 10:14 AM, James Carlson wrote: > > > Danek Duvall writes: > >> So in all of this, there's no description of what powerman actually > >> *is*. > > > > It centralizes control of power control units, often used in a lab, > > much in the way conserver centralizes console servers. > > > >> Or what the interfaces are. > > > > Good point. The interfaces provided by this project are empty. Worse still, the project (as documented) claims to "import" an interface called "Powerman," but it can't do that as there's no other project (ARC case) that exports it ... this is the project that *defines* it, so it can't import it. Your fast-track sponsor should have helped with this part. To give you some help here (rather than playing fetch-a-rock), here's a _guess_ at the sorts of interfaces this project might be exporting: Interface Stability Comments --------- --------- -------- /usr/bin/powerman Committed binary location powerman Volatile command line arguments and output /usr/bin/pm Committed symlink to `powerman' /etc/powerman/ Committed directory /etc/powerman/powerman.conf Committed file location powerman.conf Unstable file syntax *.dev Project Private control files in /etc/powerman/ svc:/network/powerman Committed SMF FMRI for server /usr/lib/powermand Project Private daemon /usr/lib/httppower Project Private connector for HTTP-based PDUs /usr/lib/plmpower Project Private connector for Insteon/X10+PLM 2412S /var/run/powerman/ Project Private local state storage (Guessing based by what I see in SourceForge.) The imports would likely be the protocols used by those PDUs, and I'm not sure how to classify them. They're probably Unstable. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Bruce.Rothermal@sun.com Mon Dec 1 09:50:13 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 mB1HoDve019883 for ; Mon, 1 Dec 2008 09:50:13 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mB1Ho2Vw045508 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 1 Dec 2008 10:50:12 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KB700D27LJOCB00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 01 Dec 2008 09:50:12 -0800 (PST) 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 <0KB700365LIIE890@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 01 Dec 2008 09:49:30 -0800 (PST) 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 mB1HnUin020497 for ; Mon, 01 Dec 2008 09:49:30 -0800 (PST) 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 <0KB700B01KSNG600@fe-sfbay-10.sun.com> (original mail from Bruce.Rothermal@Sun.COM) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 01 Dec 2008 09:49:30 -0800 (PST) Received: from [192.168.1.101] ([75.71.129.47]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KB7009ESLIG6A90@fe-sfbay-10.sun.com>; Mon, 01 Dec 2008 09:49:30 -0800 (PST) Date: Mon, 01 Dec 2008 10:49:28 -0700 From: Bruce Rothermal Subject: Re: PowerMan 2.3 [LSARC/2008/734 FastTrack timeout 12/4/2008] In-reply-to: <18740.7727.959223.801767@gargle.gargle.HOWL> Sender: Bruce.Rothermal@sun.com To: James Carlson Cc: Danek Duvall , Tom Childers , LSARC-ext@sun.com Message-id: <915891DD-475B-4147-A9D1-FE0DBF33C89E@Sun.COM> MIME-version: 1.0 X-Mailer: Apple Mail (2.929.2) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <4799AA23-FA7F-4DC9-85B5-840DCA0016BA@sun.com> <20081126162246.GY3046@mumak.SFBay.Sun.COM> <18733.33799.98981.585909@gargle.gargle.HOWL> <18740.7727.959223.801767@gargle.gargle.HOWL> Status: RO Content-Length: 2590 Thanks for the help. I'll work on making these changes. Bruce On Dec 1, 2008, at 10:26 AM, James Carlson wrote: > Bruce Rothermal writes: >> Lets see if I can explain this better and you all can let me know how >> much of this to put in the questionare. >> >> Powerman consists of a client and server process for the purpose of >> consolidating power management (turn systems on and off as found in a >> lab environment or remote unmanned dark equipment rooms). A user >> would > [...] > > That explains what it does, but not what the interfaces are, which was > the previous question: > >> On Nov 26, 2008, at 10:14 AM, James Carlson wrote: >> >>> Danek Duvall writes: >>>> So in all of this, there's no description of what powerman actually >>>> *is*. >>> >>> It centralizes control of power control units, often used in a lab, >>> much in the way conserver centralizes console servers. >>> >>>> Or what the interfaces are. >>> >>> Good point. > > The interfaces provided by this project are empty. Worse still, the > project (as documented) claims to "import" an interface called > "Powerman," but it can't do that as there's no other project (ARC > case) that exports it ... this is the project that *defines* it, so it > can't import it. > > Your fast-track sponsor should have helped with this part. To give > you some help here (rather than playing fetch-a-rock), here's a > _guess_ at the sorts of interfaces this project might be exporting: > > Interface Stability Comments > --------- --------- -------- > /usr/bin/powerman Committed binary location > powerman Volatile command line arguments and output > /usr/bin/pm Committed symlink to `powerman' > /etc/powerman/ Committed directory > /etc/powerman/powerman.conf > Committed file location > powerman.conf Unstable file syntax > *.dev Project Private control files in /etc/powerman/ > svc:/network/powerman Committed SMF FMRI for server > /usr/lib/powermand Project Private daemon > /usr/lib/httppower Project Private connector for HTTP-based PDUs > /usr/lib/plmpower Project Private connector for Insteon/X10+PLM 2412S > /var/run/powerman/ Project Private local state storage > > (Guessing based by what I see in SourceForge.) > > The imports would likely be the protocols used by those PDUs, and I'm > not sure how to classify them. They're probably Unstable. > > -- > 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 tom.childers@sun.com Fri Dec 5 16:06:12 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 mB606BXu022149 for ; Fri, 5 Dec 2008 16:06:11 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mB6069fv009521 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Sat, 6 Dec 2008 00:06:10 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBF0047MHMA7O00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 05 Dec 2008 16:06:10 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBF00J3FHLR7I80@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 05 Dec 2008 16:05:51 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mB605pkk021194 for ; Fri, 05 Dec 2008 16:05:51 -0800 (PST) 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 <0KBF00A01HFSP600@fe-sfbay-10.sun.com> (original mail from tom.childers@sun.com) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 05 Dec 2008 16:05:51 -0800 (PST) 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 <0KBF00AFTHLQ4D10@fe-sfbay-10.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 05 Dec 2008 16:05:51 -0800 (PST) Date: Fri, 05 Dec 2008 16:05:35 -0800 From: Tom Childers Subject: Re: PowerMan 2.3 [LSARC/2008/734 FastTrack timeout 12/4/2008] In-reply-to: <18740.7727.959223.801767@gargle.gargle.HOWL> Sender: Thomas.Childers@sun.com To: LSARC-ext@sun.com Cc: Bruce Rothermal Message-id: <32E95431-86EB-4E73-910C-DEAE58FF680B@sun.com> MIME-version: 1.0 X-Mailer: Apple Mail (2.929.2) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <4799AA23-FA7F-4DC9-85B5-840DCA0016BA@sun.com> <20081126162246.GY3046@mumak.SFBay.Sun.COM> <18733.33799.98981.585909@gargle.gargle.HOWL> <18740.7727.959223.801767@gargle.gargle.HOWL> Status: RO Content-Length: 4038 Bruce has provided the interface info for PowerMan, and I've updated the one-pager. The relevant section now reads as follows: 4.0 Interfaces (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ f or details) 4.1 Exported Interfaces Interface Name Classification Comments --------------------------- ------------------- --------------------------- /usr/bin/powerman Volatile client to power on/off nodes /usr/bin/pm (same) /usr/sbin/powermand Volatile power control & monitoring daemon /usr/sbin/plmpower Volatile helper program which enables communication with insteon/x10 devices. powermand runs interactively with this helper man pages Volatile /usr/share/man/man1/powerman.1 /usr/share/man/man5/powerman.conf.5 /usr/share/man/man5/powerman.dev.5 /usr/share/man/man7/powerman-devices.7 /usr/share/man/man8/powermand.8 4.2 Imported Interfaces Interface Name Classification Comments --------------------------- -------------------- -------------------------- SUNWlibms Committed /usr/lib/libm.so2 Math & Microtasking Libraries I'm extending the timer to Wednesday, December 10th. Please respond with any additional issues or comments by then. -tdc On Dec 1, 2008, at 9:26 AM, James Carlson wrote: > Bruce Rothermal writes: >> Lets see if I can explain this better and you all can let me know how >> much of this to put in the questionare. >> >> Powerman consists of a client and server process for the purpose of >> consolidating power management (turn systems on and off as found in a >> lab environment or remote unmanned dark equipment rooms). A user >> would > [...] > > That explains what it does, but not what the interfaces are, which was > the previous question: > >> On Nov 26, 2008, at 10:14 AM, James Carlson wrote: >> >>> Danek Duvall writes: >>>> So in all of this, there's no description of what powerman actually >>>> *is*. >>> >>> It centralizes control of power control units, often used in a lab, >>> much in the way conserver centralizes console servers. >>> >>>> Or what the interfaces are. >>> >>> Good point. > > The interfaces provided by this project are empty. Worse still, the > project (as documented) claims to "import" an interface called > "Powerman," but it can't do that as there's no other project (ARC > case) that exports it ... this is the project that *defines* it, so it > can't import it. > > Your fast-track sponsor should have helped with this part. To give > you some help here (rather than playing fetch-a-rock), here's a > _guess_ at the sorts of interfaces this project might be exporting: > > Interface Stability Comments > --------- --------- -------- > /usr/bin/powerman Committed binary location > powerman Volatile command line arguments and output > /usr/bin/pm Committed symlink to `powerman' > /etc/powerman/ Committed directory > /etc/powerman/powerman.conf > Committed file location > powerman.conf Unstable file syntax > *.dev Project Private control files in /etc/powerman/ > svc:/network/powerman Committed SMF FMRI for server > /usr/lib/powermand Project Private daemon > /usr/lib/httppower Project Private connector for HTTP-based PDUs > /usr/lib/plmpower Project Private connector for Insteon/X10+PLM 2412S > /var/run/powerman/ Project Private local state storage > > (Guessing based by what I see in SourceForge.) > > The imports would likely be the protocols used by those PDUs, and I'm > not sure how to classify them. They're probably Unstable. > > -- > 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 tom.childers@sun.com Thu Dec 11 17:46:35 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBC1kZfB023854 for ; Thu, 11 Dec 2008 17:46:35 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBC1kYrN029971 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Thu, 11 Dec 2008 17:46:34 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBQ00009Q9MCY00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu, 11 Dec 2008 17:46:34 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBQ00DLQQ9LICE0@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu, 11 Dec 2008 17:46:33 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mBC1kXWE023246 for ; Thu, 11 Dec 2008 17:46:33 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KBQ00G01Q5XLB00@fe-sfbay-09.sun.com> (original mail from tom.childers@sun.com) for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu, 11 Dec 2008 17:46:33 -0800 (PST) Received: from [192.168.15.2] ([98.210.230.195]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KBQ00KZJQ98CX70@fe-sfbay-09.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu, 11 Dec 2008 17:46:33 -0800 (PST) Date: Thu, 11 Dec 2008 17:46:19 -0800 From: Tom Childers Subject: Re: PowerMan 2.3 [LSARC/2008/734 FastTrack timeout 12/4/2008] In-reply-to: <32E95431-86EB-4E73-910C-DEAE58FF680B@sun.com> Sender: Thomas.Childers@sun.com To: LSARC-ext@sun.com Cc: Bruce Rothermal Message-id: <0F2D1265-05F5-4935-B61E-EE3092AF90E9@sun.com> MIME-version: 1.0 X-Mailer: Apple Mail (2.929.2) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <4799AA23-FA7F-4DC9-85B5-840DCA0016BA@sun.com> <20081126162246.GY3046@mumak.SFBay.Sun.COM> <18733.33799.98981.585909@gargle.gargle.HOWL> <18740.7727.959223.801767@gargle.gargle.HOWL> <32E95431-86EB-4E73-910C-DEAE58FF680B@sun.com> Status: RO Content-Length: 4311 Without further comment, this case is closed approved as of yesterday, 12/10. -tdc On Dec 5, 2008, at 4:05 PM, Tom Childers wrote: > Bruce has provided the interface info for PowerMan, and I've updated > the one-pager. The relevant section now reads as follows: > > 4.0 Interfaces > (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ > f > or details) > 4.1 Exported Interfaces > > Interface Name Classification Comments > --------------------------- ------------------- > --------------------------- > /usr/bin/powerman Volatile client to power on/off > nodes > /usr/bin/pm (same) > > /usr/sbin/powermand Volatile power control & > monitoring daemon > > /usr/sbin/plmpower Volatile helper program which > enables > communication with > insteon/x10 > devices. powermand runs > interactively with this > helper > man pages Volatile > /usr/share/man/man1/powerman.1 > /usr/share/man/man5/powerman.conf.5 > /usr/share/man/man5/powerman.dev.5 > /usr/share/man/man7/powerman-devices.7 > /usr/share/man/man8/powermand.8 > > 4.2 Imported Interfaces > Interface Name Classification Comments > --------------------------- -------------------- > -------------------------- > SUNWlibms Committed > /usr/lib/libm.so2 > Math & Microtasking > Libraries > > > I'm extending the timer to Wednesday, December 10th. Please respond > with any additional issues or comments by then. > -tdc > > > On Dec 1, 2008, at 9:26 AM, James Carlson wrote: > >> Bruce Rothermal writes: >>> Lets see if I can explain this better and you all can let me know >>> how >>> much of this to put in the questionare. >>> >>> Powerman consists of a client and server process for the purpose of >>> consolidating power management (turn systems on and off as found >>> in a >>> lab environment or remote unmanned dark equipment rooms). A user >>> would >> [...] >> >> That explains what it does, but not what the interfaces are, which >> was >> the previous question: >> >>> On Nov 26, 2008, at 10:14 AM, James Carlson wrote: >>> >>>> Danek Duvall writes: >>>>> So in all of this, there's no description of what powerman >>>>> actually >>>>> *is*. >>>> >>>> It centralizes control of power control units, often used in a lab, >>>> much in the way conserver centralizes console servers. >>>> >>>>> Or what the interfaces are. >>>> >>>> Good point. >> >> The interfaces provided by this project are empty. Worse still, the >> project (as documented) claims to "import" an interface called >> "Powerman," but it can't do that as there's no other project (ARC >> case) that exports it ... this is the project that *defines* it, so >> it >> can't import it. >> >> Your fast-track sponsor should have helped with this part. To give >> you some help here (rather than playing fetch-a-rock), here's a >> _guess_ at the sorts of interfaces this project might be exporting: >> >> Interface Stability Comments >> --------- --------- -------- >> /usr/bin/powerman Committed binary location >> powerman Volatile command line arguments and output >> /usr/bin/pm Committed symlink to `powerman' >> /etc/powerman/ Committed directory >> /etc/powerman/powerman.conf >> Committed file location >> powerman.conf Unstable file syntax >> *.dev Project Private control files in /etc/powerman/ >> svc:/network/powerman Committed SMF FMRI for server >> /usr/lib/powermand Project Private daemon >> /usr/lib/httppower Project Private connector for HTTP-based PDUs >> /usr/lib/plmpower Project Private connector for Insteon/X10+PLM 2412S >> /var/run/powerman/ Project Private local state storage >> >> (Guessing based by what I see in SourceForge.) >> >> The imports would likely be the protocols used by those PDUs, and I'm >> not sure how to classify them. They're probably Unstable. >> >> -- >> 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 >