[WIMS] Re: Proposal - Power Log only on System object

[WIMS] Re: Proposal - Power Log only on System object

[WIMS] Re: Proposal - Power Log only on System object

Ira McDonald blueroofmusic at gmail.com
Mon Oct 26 22:21:41 UTC 2009


Hi,

We didn't quite have a quorum today for our WIMS WG call
(Bill W, Lee F, Rick L, Ira McD).  So there won't be official
minutes.

But, we talked about Power Log group - Rick provided some
relevant recent DMTF CIM modeling experience (not PWG).

So we decided to make Power Log *only* occur on System
object - to avoid having to crawl through references in the
various Subunit objects (some of which might be powered
down - eek!).

So add PowerComponentType andPowerComponentID to
the Power Log group.  Values of PowerComponentTypeWKV
will be aligned with values of PrtAlertCodeTC (Printer MIB)
and IcSubunitTypeTC (Counter MIB).  Basically, System plus
every PWG Semantic Model first-class Subunit type - not
MarkerSupplies or specific Finisher types (Stapler, etc.).

We also talked about allowing the Power Management
Model groups (except Power General and Power Log)
to be instantiated on *any* Subunit (not just the major
hardware ones).  Also adding an ambiguity warning about
the corner case (Interpreter - software - similar to Service).

I plan to release a new version of the Power Management
Model this week that reflects these changes.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic at gmail.com
winter:
  579 Park Place  Saline, MI  48176
  734-944-0094
summer:
  PO Box 221  Grand Marais, MI 49839
  906-494-2434



On Fri, Oct 23, 2009 at 3:58 PM, Ira McDonald <blueroofmusic at gmail.com> wrote:
> Hi,
>
> [ Thinking about the Power MIB in relation to the
> Printer MIB (especially prtAlertTable and trap) ]
>
> I propose that Power Log occurs only on System
> object.
>
> DMTF CIM (and Printer MIB and other IETF MIBs)
> instantiates logs only on whole Systems or Devices
> (but not on minor components like Subunits).
>
> DMTF CIM won't *let* us put a log on a minor
> component, so the current Power Model has a
> serious mapping issue.
>
> I propose that the revised Power Log group
> should have the same single key (LogID) and
> two new elements named:
>
> ComponentType
> - existing powMonitorComponentType in MIB
> ComponentID
> - add new powMonitorComponentIndex in MIB
>
> which, in turn, correspond to prtAlertGroup and
> prtAlertGroupIndex in Printer MIB.
>
> Both ComponentType and ComponentID are
> implicit in the XML Schema - first is the enclosing
> object type and second is either '1' for System or
> <subunit>ID (like InputTrayID / prtInputIndex).
>
> Comments?
>
> Ira McDonald (Musician / Software Architect)
> Chair - Linux Foundation Open Printing WG
> Blue Roof Music/High North Inc
> email: blueroofmusic at gmail.com
> winter:
>  579 Park Place  Saline, MI  48176
>  734-944-0094
> summer:
>  PO Box 221  Grand Marais, MI 49839
>  906-494-2434
>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.




More information about the wims mailing list