From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: Deepak Kodihalli <dkodihal@linux.vnet.ibm.com>
Cc: openbmc@lists.ozlabs.org, Ed Tanous <ed@tanous.net>,
Ratan Gupta <ratagupt@linux.vnet.ibm.com>
Subject: Re: Using bios-settings-mgr for setting hypervisor network attributes
Date: Thu, 5 Nov 2020 11:48:12 -0500 [thread overview]
Message-ID: <20201105164812.ylk4wlkjnczykwpy@thinkpad.fuzziesquirrel.com> (raw)
In-Reply-To: <08d2b666-91cf-d60a-1f2b-028e6ca6eaa5@linux.vnet.ibm.com>
On Tue, Sep 22, 2020 at 05:38:32PM +0530, Deepak Kodihalli wrote:
>To add to this, from a PLDM perspective, we plan to send up the
>hypervisor network config properties to the host as BIOS attributes.
Would we need to hide these from a future redfish bios settings schema
implementation?
>There isn't a PLDM network config schema. The PLDM daemon talks to the
>new bios-settings-mgr app to find BIOS properties that have been
>updated out of band. The Redfish schema we plan to use here is
>EthernetInterface though, and not the Redfish BIOS schema. All this is
>causing a need for some conversion layers.
>
>My initial thought was bmcweb can update the BIOS backend store that's
>implemented by the bios-settings-mgr, but it looks like Patrick and Ed
>have concerns with that approach. I think I agree their reasoning, but
>at the same time I don't think there should be special code in the
>PLDM daemon (timers/special knowledge about a set of BIOS
>attributes/special BIOS attribute which indicates other BIOS
>attributes have been updated/etc) for this, and this should be
>processed like any other BIOS attribute that the PLDM daemon deals
>with. This implies these attributes should also make it to the store
>that bios-settings-mgr owns (that likely means an additional D-Bus
>hop). So, another option (proposal 4) could be an intermediate app
>that accumulates (for eg by means of watching the 'Enabled' property
>that's in the Object.Enable interface; the hypervisor settings object
>would have to additionally implement this interface) the hypervisor
>network config property updates, and then provides these as key-value
>pairs to the bios-settings-mgr app.
I get the feeling this option 4 might have been overlooked because it
was buried in this long thread. Anyone care to weigh in on this as an
option?
next prev parent reply other threads:[~2020-11-05 16:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 14:47 Using bios-settings-mgr for setting hypervisor network attributes manoj kiran
2020-09-16 16:26 ` Ed Tanous
2020-09-16 16:33 ` James Feist
2020-09-16 17:20 ` Patrick Williams
2020-09-16 17:44 ` Ed Tanous
2020-09-17 7:40 ` Ratan Gupta
2020-09-17 12:21 ` Deepak Kodihalli
2020-09-17 14:20 ` Thomaiyar, Richard Marian
2020-09-17 15:36 ` Patrick Williams
2020-09-19 5:41 ` Ratan Gupta
2020-09-22 9:09 ` Ratan Gupta
2020-09-22 12:08 ` Deepak Kodihalli
2020-11-05 16:48 ` Brad Bishop [this message]
2020-09-23 19:24 ` Patrick Williams
2020-09-23 20:51 ` Ed Tanous
2020-09-23 21:26 ` Patrick Williams
2020-09-24 13:08 ` Deepak Kodihalli
2020-09-24 15:36 ` Ed Tanous
2020-09-30 15:05 ` Ratan Gupta
2020-09-30 15:56 ` Ed Tanous
2020-10-01 11:17 ` Ratan Gupta
2020-10-16 11:40 ` manoj kiran
2020-10-20 10:43 ` Ratan Gupta
2020-09-24 7:30 ` Ratan Gupta
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=20201105164812.ylk4wlkjnczykwpy@thinkpad.fuzziesquirrel.com \
--to=bradleyb@fuzziesquirrel.com \
--cc=dkodihal@linux.vnet.ibm.com \
--cc=ed@tanous.net \
--cc=openbmc@lists.ozlabs.org \
--cc=ratagupt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).