diff options
author | Manojkiran Eda <manojkiran.eda@gmail.com> | 2020-05-11 14:30:00 +0300 |
---|---|---|
committer | Andrew Geissler <geissonator@yahoo.com> | 2020-06-18 21:44:30 +0300 |
commit | df57e3a63ccc7adcf2d8aabe6586295e97a954d9 (patch) | |
tree | e09898da1b122e6a7c2a514d6e63f2175969206e /meta-ibm/recipes-phosphor/bmcweb | |
parent | 369e79374a82da93844928a3ab2d7f10008fda9d (diff) | |
download | openbmc-df57e3a63ccc7adcf2d8aabe6586295e97a954d9.tar.xz |
Enable JSON to Map Inventory Object with Network Interface
- This commit would enable a configuration JSON file, through which
one can map the inventory object paths to the actual ethernet
interfaces which are managed Network Service.
For Example:
- Lets say the Inventory path for a single ethernet Interface machine
would look something like below:
`/xyz/openbmc_project/inventory/system/chassis/motherboard/boxelder/bmc/ethernet`
Then the corresponding configuration JSON would looks something like below:
{
"eth0":"ethernet"
}
Note that the key (eth0) in the JSON is the actual ethernet Interface
managed by the Network Service, and the value (ethernet) is the search
pattern to be found in the Inventory Path String.
- The above JSON would help the phosphor-network service to look for a
match on the Interface Added signal under Inventory Path with an object
path that contains the pattern String ("ethernet"), and there it gets the
MAC address populated under the respective inventory path and set it as
the MAC address of the eth0 Interface.
(From meta-ibm rev: 0e69c800da414c88d24e4fa5fe8d9bf560b87637)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I9e0ab9d8368efae226334086f7b1c5b6fa821770
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Diffstat (limited to 'meta-ibm/recipes-phosphor/bmcweb')
0 files changed, 0 insertions, 0 deletions