Packaging and deploying multiple firmware image types in one

Adriana Kobylak anoo at linux.ibm.com
Wed Nov 20 06:22:54 AEDT 2019


On 2019-11-15 09:46, Andrew Geissler wrote:
> On Fri, Nov 15, 2019 at 8:50 AM Adriana Kobylak <anoo at linux.ibm.com> 
> wrote:
> 
>> New expanded option for bundled images:
>> 
>> /xyz/openbmc_project/software/<system-version-id>/
>>    - Activation: Ready
>>    - Purpose: .System
>>    - Version: CompanyZ-v1.0
>>    /xyz/openbmc_project/software/<sysrem-version-id>/<bmc-version-id>/
>>      - Purpose: .BMC
>>      - Version: 2.8.0
>>    
>> /xyz/openbmc_project/software/<sysrem-version-id>/<host-version-id>/
>>      - Purpose: .Host
>>      - Version: 1.2.3

Ended up adding an array instead for the proposal, to avoid confusion 
with multiple version ids:

https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-dbus-interfaces/+/27395

       "Purpose": 
"xyz.openbmc_project.Software.Version.VersionPurpose.System",
       "Version": "2.8.0-dev-882-gf0cbf42",
       "VersionAggregate": [
         [
           "xyz.openbmc_project.Software.Version.VersionPurpose.BMC",
           "2.8.0-dev",
           ""
         ],
         [
           "xyz.openbmc_project.Software.Version.VersionPurpose.Host",
           "open-power-witherspoon-v2.2",
           
"buildroot-2018.11.1-7-g5d7cc8c,skiboot-v6.2,hostboot-17ba81e-pb264a73,occ-12c8088"
         ]
       ]

> 
> Makes sense to me. The phosphor-webui code could look for a system 
> object
> and if found, only allow the user to update/switch images based on 
> system
> level. They could still easily show the BMC, host, PSU levels though.
> Or maybe this will just be a config option for the GUI? Either way I
> think the GUI would want to show both the system and individual levels
> of firmware.

Yeah, it'd make sense to also show the individual levels to provide the 
user with more information about the image.

> 
> Redfish code in bmcweb can continue to work as-is for bmc, host, psu
> firmware inventory.

Yeah, I'd just need to make a change in bmcweb to get the version string 
from that new Aggregate interface to populate the BMC FirmwareVersion 
field.

> I think we should see if we can get the DMTF to
> add a FirmwareVersion property to the ComputerSystem object where
> we could store this new system version.

Agree.


More information about the openbmc mailing list