All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: RFC: Inventory functional state tracking
Date: Sun, 22 Jan 2017 21:51:45 -0600	[thread overview]
Message-ID: <20170123035145.GF5120@heinlein.lan> (raw)
In-Reply-To: <94DF8B09-DBBB-4388-8070-57B933450886@fuzziesquirrel.com>

[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]

On Sun, Jan 22, 2017 at 09:31:54PM -0500, Brad Bishop wrote:
> Looking for ideas on tracking inventory item functional state.  If this interests you, please read on.
> 
> One approach would be to add a functional state DBus interface to inventory objects.  I was hoping to
> keep dynamic/state information out of the inventory namespace as much as possible, but the inventory manager
> could probably be made to set properties on an interface when specific conditions are met.
> 
> Another approach would be a new class of sensor applications that do whatever is required to monitor the functional
> state of one or more inventory items.  For functional status of inventory coming from the host this would
> probably be host-ipmid.  These applications would provide sensor objects in a sensors/fault
> namespace, possibly with a xyz.openbmc_project.Sensors.Fault interface.  The fault sensor objects would be associated
> back to their inventory item via an association object.

I'm not a fan of calling something a Sensor unless it really is.  That
is what IPMI does and it ends up being a catch-all for everything else.

Something under xyz.openbmc_project.State seems more appropriate to me
but following the rest of your concept the same.

> 
> Please poke holes..ask questions.

What process would end up managing functional states?  The same process
that handles the inventory for an element or some other process?

-- 
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2017-01-23  3:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23  2:31 RFC: Inventory functional state tracking Brad Bishop
2017-01-23  3:51 ` Patrick Williams [this message]
2017-01-23  4:28   ` Brad Bishop

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170123035145.GF5120@heinlein.lan \
    --to=patrick@stwcx.xyz \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.