Multi host bios upgrade support in phosphor-bmc-code-mgmt:

Vijay Khemka vijaykhemka at
Fri Oct 16 06:28:12 AEDT 2020

Can we use extraversion field in manifest file to identify host id.
In manifest file, if purpose is host then we can check extra version
and find out which host it is applicable for.

Or lese we can add another property in /xyz/openbmc_project/software,
name as host id and user can set this property after uploading image.
I don’t agree with creating multiple interfaces for single image
upgrade.  Because image will be deleted after successful activation.

From: openbmc < at> on behalf of "P. Priyatharshan" <PriyatharshanP at>
Date: Thursday, October 15, 2020 at 10:18 AM
To: Adriana Kobylak <anoo at>
Cc: "openbmc at" <openbmc at>, "anoo at" <anoo at>, "ojayanth at" <ojayanth at>, "gmills at" <gmills at>, "Velumani T-ERS, HCLTech" <velumanit at>, "ratagupt at" <ratagupt at>
Subject: Re: Multi host bios upgrade support in phosphor-bmc-code-mgmt:

Thanks Adriana for the clarification.

For host bios update, the images will be copied to BMC(/tmp/images) and will start flashing by making RequestedActivation field "xyz.openbmc_project.Software.Activation.RequestedActivations.Active". In our case, the device location will be same for all the bios images (BMC /tmp/images).So I think the above design you proposed[id = version+volume ID]  may not work effectively for multi host as the id is still going to be same for all the hosts.

We would like to propose the following approach for your review.Kindly go through the below steps and share your valuable suggestions.

1.Number of host will be identified from machine layer [OBMC_HOST_INSTANCES]

2.Code will be modified to create n number of objects based on number of hosts

  Ex: Log taken in YosemiteV2 [4 host]

root at yosemitev2:~# busctl tree xyz.openbmc_project.Software.BMC.Updater
      | `-/xyz/openbmc_project/software/host1/28bd62d9
      | `-/xyz/openbmc_project/software/host2/28bd62d9
      | `-/xyz/openbmc_project/software/host3/28bd62d9
root at yosemitev2:~# busctl tree xyz.openbmc_project.Software.Version
      | `-/xyz/openbmc_project/software/host1/28bd62d9
      | `-/xyz/openbmc_project/software/host2/28bd62d9
      | `-/xyz/openbmc_project/software/host3/28bd62d9

3.This will create activation interface for each host. For a multi-host system if the  RequestedActivation is set to "xyz.openbmc_project.Software.Activation.RequestedActivations.Active", then different bios service file will be called based the host.

For single host : biosServiceFile = "obmc-flash-host-bios@" + versionId + ".service";
For multi host  : biosServiceFile =  "obmc-flash-host" + host + "-bios@" + versionId + ".service";

Then it can be used for multi host even if the firmware image we want to install is the same for multiple host targets.

I have created a WIP patch for the design proposed above.Kindly have a glance and share your comments.<>

Priyatharshan P

From: Adriana Kobylak <anoo at>
Sent: 06 October 2020 03:11
To: P. Priyatharshan <PriyatharshanP at>
Cc: Patrick Williams <patrick at>; Velumani T-ERS,HCLTech <velumanit at>; openbmc at <openbmc at>; anoo at <anoo at>; ojayanth at <ojayanth at>; gmills at <gmills at>; ratagupt at <ratagupt at>
Subject: Re: Multi host bios upgrade support in phosphor-bmc-code-mgmt:

[CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.]

Hi Priyatharshan,

>  Object : /xyz/openbmc_project/software/[FIRMWARE_VERSION]_[DEVICE]
> where device could be host1, 2, ...,N
>  Interface : xyz.openbmc_project.Software.Activation
>  Please confirm if our understanding is correct.

I meant that to generate the id, which currently uses the version
string, would instead use the version string plus the string for the
name of the device where it's stored in order to generate the hash. For
example, today the code calls "SHA512_Update("version")", where
"version" is for example "2.9.0-dev-663-g2e34bb673". Instead the code
would detect this version is stored let's say in device "mtd1" or
"mmcblk0p1", it'd then append that device string to version, ex:
"2.9.0-dev-663-g2e34bb673-mmcblk0p1" and pass that string to
SHA512_Update(), therefore creating a different hash depending where
that version of bmc code is stored.

Note that this is for BMC versions only. We discussed that for host
versions, we'd need to modify the code to add a "os-release" file under
/media/ that contained the host version information similar to the BMC's
os-release file. In addition, we'd need to somehow determine that those
files were for host (Bios) versions instead of BMC ones. Perhaps
os-release could have an additional field added to specify the purpose.

> Adriana, Any tentative timeline on your commits availability [generate
> the id based on firmware version plus the device or volume ]

I'd say by early next year at the latest.
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the openbmc mailing list