All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Thaler <thalerj@linux.vnet.ibm.com>
To: vishwa <vishwa@linux.vnet.ibm.com>,
	"Matuszczak, Piotr" <piotr.matuszczak@intel.com>,
	Paul Vancil <pwvancil@gmail.com>
Cc: "Mihm, James" <james.mihm@intel.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	"neladk@microsoft.com" <neladk@microsoft.com>,
	James Feist <james.feist@linux.intel.com>,
	"apparao.puli@linux.intel.com" <apparao.puli@linux.intel.com>,
	Brad Bishop <bradleyb@fuzziesquirrel.com>
Subject: Re: multiple telemetry designs
Date: Tue, 12 Nov 2019 08:36:35 -0600	[thread overview]
Message-ID: <6474a709-fa41-2dd5-538e-e04fb6e25431@linux.vnet.ibm.com> (raw)
In-Reply-To: <1db5a5bd-6be6-cb93-5865-99416cc31646@linux.vnet.ibm.com>



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@linux.vnet.ibm.com]
>> Sent: Tuesday, November 5, 2019 8:31 AM
>> To: Brad Bishop <bradleyb@fuzziesquirrel.com>
>> Cc: Mihm, James <james.mihm@intel.com>; Justin Thaler 
>> <thalerj@linux.vnet.ibm.com>; openbmc@lists.ozlabs.org; 
>> neladk@microsoft.com; James Feist <james.feist@linux.intel.com>; 
>> apparao.puli@linux.intel.com; Matuszczak, Piotr 
>> <piotr.matuszczak@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@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

  reply	other threads:[~2019-11-12 14:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 16:38 multiple telemetry designs Brad Bishop
2019-10-23 17:39 ` James Feist
2019-10-23 17:47   ` James Feist
2019-10-23 20:30     ` Justin Thaler
2019-10-24  8:48       ` Matuszczak, Piotr
2019-10-24 16:14         ` James Feist
2019-10-25 12:07           ` Brad Bishop
2019-10-25 16:46             ` Matuszczak, Piotr
2019-10-25 16:59               ` Brad Bishop
2019-10-28 16:35                 ` Matuszczak, Piotr
2019-10-28 16:42                   ` Brad Bishop
2019-11-05  7:31                     ` vishwa
2019-11-05  8:56                       ` Matuszczak, Piotr
2019-11-05 16:58                         ` vishwa
2019-11-12 14:36                           ` Justin Thaler [this message]
2019-11-12 14:39                             ` Paul Vancil
2019-11-14 16:37                               ` Matuszczak, Piotr
2019-10-24 17:13 ` Shawn McCarney
2019-10-24 17:27   ` Kun Yi
2019-10-24 17:31     ` Neeraj Ladkani
2019-10-24 17:45       ` Brad Bishop
2019-10-25 12:15     ` Brad Bishop
2019-10-25 12:59   ` Brad Bishop
2019-10-25 15:08     ` Matuszczak, Piotr
2019-10-25 17:31       ` Brad Bishop
2019-10-28 16:42         ` Matuszczak, Piotr

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=6474a709-fa41-2dd5-538e-e04fb6e25431@linux.vnet.ibm.com \
    --to=thalerj@linux.vnet.ibm.com \
    --cc=apparao.puli@linux.intel.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=james.feist@linux.intel.com \
    --cc=james.mihm@intel.com \
    --cc=neladk@microsoft.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=piotr.matuszczak@intel.com \
    --cc=pwvancil@gmail.com \
    --cc=vishwa@linux.vnet.ibm.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.