PowerMan 2.3 [LSARC/2008/734 FastTrack timeout 12/4/2008]
Tom Childers
tom.childers at sun.com
Fri Dec 5 16:05:35 PST 2008
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 <james.d.carlson at sun.com
> >
> 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
More information about the opensolaris-arc
mailing list