multiple telemetry designs

[Matuszczak, Piotr]

Hi,

I looked at this design briefly and it seems to be focusing on Redfish Telemetry Service implementation, which our design (https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/24357) also covers. Dell's design assumes using collecd for gathering sensor readings.

-----Original Message-----
From: vishwa [mailto:vishwa at linux.vnet.ibm.com]
Sent: Tuesday, November 5, 2019 8:31 AM
To: Brad Bishop <bradleyb at fuzziesquirrel.com>
Cc: Mihm, James <james.mihm at intel.com>; Justin Thaler <thalerj at linux.vnet.ibm.com>; openbmc at lists.ozlabs.org; neladk at microsoft.com; James Feist <james.feist at linux.intel.com>; apparao.puli at linux.intel.com; Matuszczak, Piotr <piotr.matuszczak at intel.com>
Subject: Re: multiple telemetry designs

There is also this version from Dell:
https://gerrit.openbmc-project.xyz/#/c/openbmc/docs/+/23758/. Was this considered in this discussion ?.

Also, from IBM's standpoint, Justin Thaler was mentioning that we wanted a "true subscription" model, in that, clients can pick and chose the specific sensors.

Justin: Could you add here please ?

!! Vishwa !!

On 10/28/19 10:12 PM, Brad Bishop wrote:
>> On Oct 28, 2019, at 12:35 PM, Matuszczak, Piotr <piotr.matuszczak at intel.com> wrote:
>>
>> I would like to make the code opened from the very beginning.
> Glad to hear it - that sounds like the best way to me :-)
>
> FWIW, whenever you are ready to share it, I’d still like to see whatever code Intel has for the monitoring service.  It will help me understand your design better.  It is fine if it has bugs or it isn’t polished.  Thanks Piotr.
>
> -brad