Skip to content

rflash_streamline_procedure

Yuan Bai edited this page Nov 23, 2017 · 9 revisions

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, like this:

rflash <noderange> -d /path-to-directory/

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. Power OFF the Host
  4. Activate the BMC
  5. Activate the PNOR
  6. Wait here until the BMC and PNOR become Active
  7. Once both active:
    • Reboot the bmc
    • Wait for BMC to become BMCReady (takes 4-5 minutes or so...
  8. Power ON the host
  9. Exit command.

Status Machine

LOGIN
    |
RFLASH_FILE_UPLOAD_REQUEST            -------> upload bmc+pnor tar ball
    |
RFLASH_FILE_UPLOAD_RESPONSE      
    |
RPOWER_OFF_REQUEST                    -------> power off host
    |
RPOWER_OFF_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_ON_REQUEST                     -------> power on host 
    |
RPOWER_ON_RESPONSE

News

History

  • Oct 22, 2010: xCAT 2.5 released.
  • Apr 30, 2010: xCAT 2.4 is released.
  • Oct 31, 2009: xCAT 2.3 released. xCAT's 10 year anniversary!
  • Apr 16, 2009: xCAT 2.2 released.
  • Oct 31, 2008: xCAT 2.1 released.
  • Sep 12, 2008: Support for xCAT 2 can now be purchased!
  • June 9, 2008: xCAT breaths life into (at the time) the fastest supercomputer on the planet
  • May 30, 2008: xCAT 2.0 for Linux officially released!
  • Oct 31, 2007: IBM open sources xCAT 2.0 to allow collaboration among all of the xCAT users.
  • Oct 31, 1999: xCAT 1.0 is born!
    xCAT started out as a project in IBM developed by Egan Ford. It was quickly adopted by customers and IBM manufacturing sites to rapidly deploy clusters.
Clone this wiki locally