From: "Wludzik, Jozef" <jozef.wludzik@linux.intel.com>
To: openbmc@lists.ozlabs.org
Subject: Re: Discrete Sensors in OpenBMC
Date: Tue, 26 Jan 2021 09:56:52 +0100 [thread overview]
Message-ID: <5bf89d84-663a-45ad-4891-ce29d07830ae@linux.intel.com> (raw)
In-Reply-To: <CAH2-KxCY4bHin6yQELB9dKPcSZsJUMM61k2FLSs+hVcYG6TzgA@mail.gmail.com>
Thanks for responses. It sounds reasonable. As initial implementation
discrete threshold/trigger will allow to monitor sensor without
differentiate between type of sensor (e.g. thermal, power, voltage,
...). If anyone will require additional type of resource to be monitored
by Telemetry (e.g. intrinsic sensor to check if chassis is closed), than
it is possible to extend the implementation.
I liked the idea to stream resource events. It seems that it is the same
as discrete threshold but threshold allows to commit an action on
specific value of a resource/sensor. One of the trigger actions is
logging a Redfish Message that can be streamed as Event.
Thanks,
Jozef
On 1/21/2021 17:46 PM, Ed Tanous wrote:
> On Tue, Jan 19, 2021 at 6:23 AM Wludzik, Jozef
> <jozef.wludzik@linux.intel.com> wrote:
>>
>> Does anyone use or implement discrete sensor in OpenBMC? Redfish defines
>> discrete triggers that use discrete values to detect that threshold is
>> crossed and trigger action should be commited. Redfish does not mention
>> about discrete sensor/values in other topics/schemes than Telemetry
>> (e.g. MetricDefinition, MetricReportDefinition and MetricReport). I am
>> asking about it because we are trying to find an example of discrete
>> sensor to proceed with DiscreteTriggers implementation (aka Discrete
>> thresholds) from Triggers scheme.
>
> A "discrete" sensor is terminology that's only used in IPMI. The
> equivalent in Redfish would be an enum type property, of which there
> are many examples. The most obvious discrete-like sensor that we have
> an example of today would be the Systems PowerState parameter, which
> changes state based on the power state of the system.
>
> If you're looking to stream events through redfish, generally you
> would implement some kind of property, then you would implement a
> Resource Changed event that someone could subscribe to from here:
> https://redfish.dmtf.org/registries/ResourceEvent.1.0.3.json
>
> We don't have the subscription part implemented yet, but there was
> some talk about getting that going.
>
>>
>> Ref.:
>>
>> Redfish Telemetry White Paper -
>> https://www.dmtf.org/sites/default/files/standards/documents/DSP2051_1.0.0.pdf
>>
>> Thanks,
>> Jozef
>>
prev parent reply other threads:[~2021-01-26 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 14:22 Discrete Sensors in OpenBMC Wludzik, Jozef
2021-01-21 12:47 ` Patrick Williams
2021-01-21 16:46 ` Ed Tanous
2021-01-26 8:56 ` Wludzik, Jozef [this message]
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=5bf89d84-663a-45ad-4891-ce29d07830ae@linux.intel.com \
--to=jozef.wludzik@linux.intel.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.