From: Willy Tu <wltu@google.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Cc: Jie Yang <jjy@google.com>, Ed Tanous <edtanous@google.com>,
Derek Chan <dchanman@google.com>
Subject: Re: [Bmcweb/Redfish] Chassis Physical Connectivity Support on bmcweb
Date: Thu, 10 Jun 2021 09:43:51 -0700 [thread overview]
Message-ID: <CAHwn2X=VQKLtvFz0-nterDA1n6jmT09GOK1m-=0-Law3hY_weg@mail.gmail.com> (raw)
In-Reply-To: <CAHwn2Xkn5h2SJYHDriSgs2HYDv2WDMHqwOmaR5XAHaFFZjCLAg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]
Related doc for the Chassis Inventory Connections:
https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/41468
On Mon, Jun 7, 2021 at 6:22 PM Willy Tu <wltu@google.com> wrote:
> Hi all,
>
> I am thinking about adding better support for Physical Connectivity
> between Boards/Chassises in bmcweb. Since Inventory.Board is treated as a
> chassis, I want to have a way to better connect the different boards with
> the existing ContainedBy/Contains.
>
> I was thinking of using xyz.openbmc_project.Association to do it. Since
> it is a list with fixed order, we can use the first chassis it finds
> for ContainedBy and the rest for Contains. For the root Chassis, it will
> have itself as the first Chassis and then just not include it.
>
> Is this something we can work with? or do we need something more
> complicated to support chassis relationship?
>
> ----
>
> Another question that is kind of related.
> I am also thinking about using Physical Location for each Chassis.
> It is already using `xyz.openbmc_project.Inventory.Decorator.LocationCode`
> as the ServiceLabel
> https://github.com/openbmc/bmcweb/blob/90e97e1d26b78d899a543831a8051dacbbdde71a/redfish-core/lib/chassis.hpp#L295-L331
>
> With that in mind, I am wondering how LocationCode is configured with
> EntityManager? Since the number of FRUs is dynamic, there is no way to tell
> which location the FRU is connected to without a mapping. I am wondering
> how that can be done with Entity Manager.
>
> I was thinking of doing something like getEntityName
> <https://github.com/openbmc/google-ipmi-sys/blob/3b1b427c1fa4bcddcab1fc003410e5fa5d7a8334/handler.cpp#L235> in
> IPMI OEM handler which utilizes a json file for the mapping from entity
> instance to location. This is a simple way of doing it within
> EntityManager, but I am not sure if we want to do it this way.
>
> Maybe something related?
> https://gerrit.openbmc-project.xyz/c/openbmc/entity-manager/+/42971
>
> Best,
>
> Willy Tu
>
[-- Attachment #2: Type: text/html, Size: 4745 bytes --]
prev parent reply other threads:[~2021-06-10 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 1:22 [Bmcweb/Redfish] Chassis Physical Connectivity Support on bmcweb Willy Tu
2021-06-10 16:43 ` Willy Tu [this message]
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='CAHwn2X=VQKLtvFz0-nterDA1n6jmT09GOK1m-=0-Law3hY_weg@mail.gmail.com' \
--to=wltu@google.com \
--cc=dchanman@google.com \
--cc=edtanous@google.com \
--cc=jjy@google.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).