multiple telemetry designs

[Matuszczak, Piotr]

Hi, 

Thank you all for reviews and comments. Is there anything else required in order to push this design to the Github repository?

Regards
Piotr

From: Paul Vancil [mailto:pwvancil at gmail.com] 
Sent: Tuesday, November 12, 2019 3:39 PM
To: Justin Thaler <thalerj at linux.vnet.ibm.com>
Cc: Brad Bishop <bradleyb at fuzziesquirrel.com>; James Feist <james.feist at linux.intel.com>; Matuszczak, Piotr <piotr.matuszczak at intel.com>; Mihm, James <james.mihm at intel.com>; apparao.puli at linux.intel.com; neladk at microsoft.com; openbmc at lists.ozlabs.org; vishwa <vishwa at linux.vnet.ibm.com>
Subject: Re: multiple telemetry designs

Paul here. 
I also commented and approved the intel design. 
It looks good to me. 


On Tue, Nov 12, 2019 at 9:36 AM Justin Thaler <thalerj at linux.vnet.ibm.com> wrote:


On 11/5/19 10:58 AM, vishwa wrote:
> Thanks.
> 
> So, looks like we are getting zeroed in on Intel's proposal ?. I see Kun 
> approving Intel version.
> 
> Paul: Did you have anything ?
> 
> !! Vishwa !!
> 
> On 11/5/19 2:26 PM, Matuszczak, Piotr wrote:
>> 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 ?
Sorry for the slow response. Piotr was kind enough to walk me through 
how the proposal works and it does allow for a true subscription model. 
I still have a to do to determine how much data we will be using with 
this model so I can understand how well it scales. This is a concern for 
us as we are shifting from receiving sensor updates in an "on-change" 
model to updates every second, regardless of change. There's also 
changes in the data format that's sent, which will likely make this less 
of a concern.

Thanks,
Justin

>>
>> !! 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