From: Ratan Gupta <ratagupt@linux.vnet.ibm.com>
To: openbmc@lists.ozlabs.org
Subject: Re: Using bios-settings-mgr for setting hypervisor network attributes
Date: Sat, 19 Sep 2020 11:11:05 +0530 [thread overview]
Message-ID: <c007630e-54e2-df13-e6da-0af0b2998279@linux.vnet.ibm.com> (raw)
In-Reply-To: <20200917153601.GH6152@heinlein>
On 9/17/20 9:06 PM, Patrick Williams wrote:
> On Thu, Sep 17, 2020 at 01:10:06PM +0530, Ratan Gupta wrote:
>> We need to address the below two concerns with the existing settings infra.
> Both of these seem like missing features based on our now greater
> understanding of the problem domain from where we were 3-4 years ago
> when phosphor-settings-manager was originally written, right? That
> doesn't seem like a good reason to entirely throw out the approach.
>
>> * Pending v/s configured value: Currently settings have single Dbus
>> Object, Some properties which is for host firmware we need to have
>> two placeholders one for Pending values and one for Configured
>> values. Bios settings have this concept.
>> o Should we add two Dbus objects in settings infra?
> This was going to be my suggestion, yes. You could have two sets of the
> objects: current and pending. 'current' objects may not be written by
> dbus-clients. These are the same terms used by the BIOSConfig proposal.
Thanks Patrick, seems reasonable to have two D-bus objects.
>
> What I am not seeing in BIOSConfig and is equally applicable here is
> _when_ pending is applied to current. You will need some interface that
> IPMI / PLDM can call to apply those settings? Or, do you monitor host
> state signals automatically?
>
>> * Dynamic Dbus objects: Currently settings infrastructure is only for
>> static objects, Objects which gets added on runtime, settings infra
>> doesn't support that.
>> o Eg: IP address on ethernet interface is dynamic in nature, An
>> ethernet interface can have multiple IP address on it.
>> considering if SLAAC is enabled(ipV6).
>> o Seems this problem is common for both(settings v/s bios-settings)
> I assume these would be requested for creation by IPMI / PLDM? We could
> use a similar model to xyz.openbmc_project.Inventory.Manager where
> objects are requested for creation dynamically through a method.
We don't have this requirement now but in near future it is going to
be there, we can improve the settings infra to support this.
>
next prev parent reply other threads:[~2020-09-19 5:41 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 [this message]
2020-09-22 9:09 ` Ratan Gupta
2020-09-22 12:08 ` Deepak Kodihalli
2020-11-05 16:48 ` Brad Bishop
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=c007630e-54e2-df13-e6da-0af0b2998279@linux.vnet.ibm.com \
--to=ratagupt@linux.vnet.ibm.com \
--cc=openbmc@lists.ozlabs.org \
/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).