From: "Matuszczak, Piotr" <piotr.matuszczak@intel.com>
To: Milton Miller II <miltonm@us.ibm.com>,
Joseph Reynolds <jrey@linux.ibm.com>
Cc: Vijay Khemka <vijaykhemka@fb.com>,
"Khetan, Sharad" <sharad.khetan@intel.com>,
krtaylor <kurt.r.taylor@gmail.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: RE: OpenBMC health statistics
Date: Wed, 1 Jul 2020 15:05:23 +0000 [thread overview]
Message-ID: <CY4PR1101MB2311892FC6029422D65938B6866C0@CY4PR1101MB2311.namprd11.prod.outlook.com> (raw)
In-Reply-To: <OF5EABA8F0.4EA96F13-ON00258597.006CE4F4-00258597.006D1458@notes.na.collabserv.com>
Thank you for the meaningful discussion. This document is more relevant for the developers, because it contains information about how to implement BMC health statistics to be compliant with the OpenBMC sensor and telemetry architecture. So probably, the best place to put it, would be the development folder. Do you agree?
Piotr Matuszczak
---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
ul. Slowackiego 173, 80-298 Gdansk
KRS 101882
NIP 957-07-52-316
-----Original Message-----
From: Milton Miller II <miltonm@us.ibm.com>
Sent: Tuesday, June 30, 2020 9:51 PM
To: Joseph Reynolds <jrey@linux.ibm.com>
Cc: Vijay Khemka <vijaykhemka@fb.com>; Khetan, Sharad <sharad.khetan@intel.com>; krtaylor <kurt.r.taylor@gmail.com>; Matuszczak, Piotr <piotr.matuszczak@intel.com>; openbmc@lists.ozlabs.org
Subject: RE: OpenBMC health statistics
On 06/30/2020 around 01:54PM in some timezone, Joseph Reynolds wrote:
>On 6/29/20 3:20 PM, Vijay Khemka wrote:
>> We can have a folder "how to" under guidelines and this document
>should fit there.
>
>That makes sense to me. I want document stuff for both system
>integrators (who put together firmware images) and system
>administrators (who perform BMC initial configurations, oversee BMC
>operation, etc.).
>We also need a place for documentation for things like how to use
>BMCWeb's mTLS feature which cuts across system integration and
>administration.
Speaking of which, we added the document but didn't link to it in either the top level or the user guide section so you have to stumble across it.
https://github.com/openbmc/docs/blob/master/security/TLS-configuration.md
Maybe here? https://github.com/openbmc/docs/#openbmc-usage
> Details:
>https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ibm-2
>Dopenbmc_dev_issues_1531&d=DwIDaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=bvv7AJEE
>CoRKBU02rcu4F5DWd-EwX8As2xrXeO9ZSo4&m=XCL8eI954f4equF5mjno80k9RtQpNBr
>kFoWrttLHUF8&s=fzPBC2_zSgHFF0Ku_87QXPBll5CYqC9LTDO9BDVCvLQ&e=
>
>- Joseph
milton
next prev parent reply other threads:[~2020-07-01 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 15:54 OpenBMC health statistics Matuszczak, Piotr
2020-06-29 17:53 ` krtaylor
2020-06-29 18:49 ` Khetan, Sharad
2020-06-29 20:20 ` Vijay Khemka
2020-06-30 18:52 ` Joseph Reynolds
2020-06-30 19:51 ` Milton Miller II
2020-07-01 15:05 ` Matuszczak, Piotr [this message]
2020-07-01 17:25 ` Vijay Khemka
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=CY4PR1101MB2311892FC6029422D65938B6866C0@CY4PR1101MB2311.namprd11.prod.outlook.com \
--to=piotr.matuszczak@intel.com \
--cc=jrey@linux.ibm.com \
--cc=kurt.r.taylor@gmail.com \
--cc=miltonm@us.ibm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=sharad.khetan@intel.com \
--cc=vijaykhemka@fb.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.