From: Ed Tanous <ed@tanous.net>
To: manoj kiran <manojkiran.eda@gmail.com>
Cc: "james.feist@linux.intel.com" <james.feist@linux.intel.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Using bios-settings-mgr for setting hypervisor network attributes
Date: Wed, 16 Sep 2020 09:26:50 -0700 [thread overview]
Message-ID: <CACWQX83KnXz-+WB1xgMP4MAPfDGare_ZM=SAWrWzohhT--Jwrg@mail.gmail.com> (raw)
In-Reply-To: <C9C88F03-4715-444E-9B1A-3834995458EA@getmailspring.com>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
On Wed, Sep 16, 2020 at 7:47 AM manoj kiran <manojkiran.eda@gmail.com>
wrote:
> Hi Ed & James,
>
> Till now IBM was using phosphor-settings infrastructure as back-end and
> uses Ethernet Schema for Hypervisor computer
> system(hypervisor_ethernet.hpp) for setting the IP address of hypervisor.
> And now we are planning to leverage the capabilities of
> bios-settings-mgr(backend) as well to set the hypervisor attributes.
>
> do you see any concerns here ?
>
> Thanks,
> Manoj
> [image: Sent from Mailspring]
None that I can think of (although I don't know much about
bios-settings-mgr). Holding all the host data in one daemon seems like a
better way to do it than putting it in settings.
[-- Attachment #2: Type: text/html, Size: 1291 bytes --]
next prev parent reply other threads:[~2020-09-16 16:27 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 [this message]
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
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='CACWQX83KnXz-+WB1xgMP4MAPfDGare_ZM=SAWrWzohhT--Jwrg@mail.gmail.com' \
--to=ed@tanous.net \
--cc=james.feist@linux.intel.com \
--cc=manojkiran.eda@gmail.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).