From: Gunnar Mills <gmills@linux.vnet.ibm.com>
To: Deepak Kodihalli <deepak.kodihalli.83@gmail.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
Ed Tanous <ed@tanous.net>, Lei Yu <yulei.sh@bytedance.com>,
"Li, Yong B" <yong.b.li@intel.com>
Subject: Re: Switch SensorCollection to show all sensors as new power/thermal schemas implemented
Date: Mon, 15 Feb 2021 19:16:21 -0700 [thread overview]
Message-ID: <48458f34-53d0-3a61-b1bd-4d6ff513a2cb@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAM=TmwWkokfJMdT-Vd88SSui4ee7jYPudMmRXPo0uPO=6bCY4Q@mail.gmail.com>
On 1/19/2021 9:53 PM, Deepak Kodihalli wrote:
>
> Where would the sensor collection be rooted at?
> /redfish/v1/chassis/{ID}/sensors?
Late reply. Yes. Sensors are associated to a chassis via an association.
https://github.com/openbmc/docs/blob/919a7b6816a5f16aa72d298e81e0756d95d5031e/architecture/sensor-architecture.md#association-type-1-linking-a-chassis-to-all-sensors-within-the-chassis
https://gerrit.openbmc-project.xyz/c/openbmc/bmcweb/+/40169 is the code
for moving bmcweb to all sensors in the sensor collection.
If so, would this also contain
> sensors accessible to the system software (some CPU/DIMM sensors for
> eg)?
Yes, it could. There is nothing in the Redfish spec that prevents that.
The definition of what a sensor is in Redfish is very broad.
If you need additional "ReadingTypes", I'm sure Redfish would be willing
to add with a use case.
https://redfish.dmtf.org/schemas/v1/Sensor.v1_2_0.json
Hope this helps,
Gunnar
prev parent reply other threads:[~2021-02-16 3:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 18:19 Switch SensorCollection to show all sensors as new power/thermal schemas implemented Gunnar Mills
2021-01-19 18:20 ` Gunnar Mills
2021-01-20 4:53 ` Deepak Kodihalli
2021-02-16 2:16 ` Gunnar Mills [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=48458f34-53d0-3a61-b1bd-4d6ff513a2cb@linux.vnet.ibm.com \
--to=gmills@linux.vnet.ibm.com \
--cc=deepak.kodihalli.83@gmail.com \
--cc=ed@tanous.net \
--cc=openbmc@lists.ozlabs.org \
--cc=yong.b.li@intel.com \
--cc=yulei.sh@bytedance.com \
/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.