2
0
mirror of https://github.com/xcat2/xcat-core.git synced 2024-11-21 17:11:52 +00:00
9 rflash_streamline_procedure
Yuan Bai edited this page 2017-12-01 19:15:27 +08:00

Mini-design for streamline the rflash procedure to run unattended

Background

OpenBMC implemented a flash for their FW process that allows for great flexibility, but with that, introduces complexity that most system admins may not want to deal with. While a system admin could upload the FW files to the BMC before a maintenance window, the upload step doesn't take hours, so the savings in time vs the added steps may not be worth it for some. In the past, BMCs also provided a single image with BMC+PNOR or a utility to perform the correct actions on the target node to ensure that the software updates with minimal issues. None of this is currently provided by OpenBMC So for OpenBMC, we can streamline the firmware flash process to do the necessary steps against the target node to help ensure that the BMC and PNOR are updated correctly and the BMC and Host are rebooted for the update to apply.

Interface

In the past, [-d|--delete] is to delete update image from BMC. In this enhancement, keeping --delete to delete update image as original function, while using -d <path-to-directory> to specify BMC+PNOR tar ball directory. If disable reboot host, using --no-host-reboot option like this:

rflash <noderange> -d /path-to-directory/
rflash <noderange> -d /path-to-directory/ --no-host-reboot

Plugin file

  • /opt/xcat/lib/perl/xCAT_plugin/openbmc.pm
  • /opt/xcat/lib/perl/xCAT/OPENBMC.pm

The main function logic

  1. Parse input argument -d
  2. Look in the tar ball path-to-directory
    • do some error checking, only 1 PNOR and 1 BMC are allowed
    • If there is only 1 tar ball file, suggest : user put both 1 PNOR and 1 BMC in this directory or using -a option, exit command
    • upload the 2 tar ball files
  3. Activate the BMC
  4. Activate the PNOR
  5. Wait here until the BMC and PNOR become Active
  6. Once both active:
    • Reboot the bmc
    • Wait for BMC to become BMCReady (takes 4-5 minutes or so...
  7. Power reset the Host
  8. Exit command.

Status Machine

LOGIN
    |
RFLASH_FILE_UPLOAD_REQUEST            -------> upload bmc+pnor tar ball
    |
RFLASH_FILE_UPLOAD_RESPONSE      
    |
RFLASH_UPDATE_CHECK_ID_REQUEST 
    |
RFLASH_UPDATE_CHECK_ID_RESPONSE 
    |
RFLASH_UPDATE_ACTIVATE_REQUEST        -------> update and activate bmc
    |
RFLASH_UPDATE_ACTIVATE_RESPONSE
    |
RFLASH_UPDATE_HOST_ACTIVATE_REQUEST   -------> update and activate pnor
    |
RFLASH_UPDATE_HOST_ACTIVATE_RESPONSE
    |
RFLASH_UPDATE_CHECK_STATE_REQUEST    
    |
RFLASH_UPDATE_CHECK_STATE_RESPONSE
    |
RPOWER_BMCREBOOT_REQUEST              -------> if BMCReady, reboot bmc
    |
RPOWER_RESET_RESPONSE
    |
RPOWER_OFF_REQUEST                    -------> power off host
    |
RPOWER_OFF_RESPONSE
    |
RPOWER_ON_REQUEST                     -------> power on host 
    |
RPOWER_ON_RESPONSE