Skip to content

Latest commit

 

History

History
103 lines (70 loc) · 5.1 KB

README.md

File metadata and controls

103 lines (70 loc) · 5.1 KB
Raw

Upgrade CSM

The process for upgrading Cray Systems Management (CSM) has many steps in multiple procedures which should be done in a specific order.

After the upgrade of CSM software, the CSM health checks will validate the system before doing any other operational tasks like the check and update of firmware on system components. Once the CSM upgrade has completed, other product streams for the HPE Cray EX system can be installed or upgraded.

  1. Prepare for upgrade
  2. Upgrade management nodes and CSM services
  3. Validate CSM health
  4. Check and Update Firmware
  5. Next topic

Note: If problems are encountered during the upgrade, some of the topics do have their own troubleshooting sections, but there is also a general troubleshooting topic.

  • If IMS image creation CFS jobs fail, see Known Issue: IMS image creation failure for a possible workaround.

  • On some systems, Ceph can begin to exhibit latency over time, and if this occurs it can eventually cause services like slurm and services that are backed by etcd clusters to exhibit slowness and possible timeouts. See Known Issue: Ceph OSD latency for a workaround.

1. Prepare for upgrade

See Prepare for Upgrade.

2. Upgrade management nodes and CSM services

The upgrade of CSM software will do a controlled, rolling reboot of all management nodes before updating the CSM services.

The upgrade is a guided process starting with Upgrade Management Nodes and CSM Services.

3. Validate CSM health

  • Before performing the health validation, be sure that at least 15 minutes have elapsed since the CSM services were upgraded. This allows the various Kubernetes resources to initialize and start.
  • If the site does not use UAIs, then skip UAS and UAI validation. If UAIs are used, then before validating UAS and UAI, first validate any products that configure UAS (such as Cray Analytics and Cray Programming Environment); the procedures for this are beyond the scope of this document. Failures in UAI creation that result from incorrect or incomplete installation of these products will generally take the form of UAIs stuck in waiting state, trying to set up volume mounts.
  • Although it is not recommended, the Booting CSM barebones image test may be skipped if all compute nodes are active running application workloads.

  1. (ncn-m002#) If a typescript session is already running in the shell, then first stop it with the exit command.

  2. (ncn-m002#) Start a typescript.

    script -af /root/csm_upgrade.$(date +%Y%m%d_%H%M%S).post_upgrade_health_validation.txt
export PS1='\u@\H \D{%Y-%m-%d} \t \w # '

    If additional shells are opened during this procedure, then record those with typescripts as well. When resuming a procedure after a break, always be sure that a typescript is running before proceeding.

  3. Validate CSM health.

    See Validate CSM Health.

  4. (ncn-m002#) Stop typescripts.

    For any typescripts that were started during the health validation procedure, stop them with the exit command.

  5. (ncn-m002#) Backup upgrade logs and typescript files to a safe location.

    1. If any typescript files are on different NCNs, then copy them to /root on ncn-m002.

    2. Create tar file containing the logs and typescript files.

      If any typescript file names are not of the form csm_upgrade.*.txt, then append their names to the following tar command in order to include them.

      TARFILE="csm_upgrade.$(date +%Y%m%d_%H%M%S).logs.tgz"
tar -czvf "/root/${TARFILE}" /root/csm_upgrade.*.txt /root/output.log

    3. Upload the tar file into S3.

      This step requires that the Cray Command Line Interface is configured on the node. This should have already been done on ncn-m002 during the upgrade process. If needed, see Configure the Cray CLI.

      cray artifacts create config-data "${TARFILE}" "/root/${TARFILE}"

4. Check and Update Firmware

Check and update firmware if not already at the correct versions. Make sure the latest version of the HPE Cray EX HPC Firmware Pack (HFP) has been installed. Follow the procedures for updating firmware with the Firmware Actions Service (FAS) document Update Firmware with FAS.

5. Next topic

After completion of the validation of CSM health, the CSM product stream has been fully upgraded and configured. Refer to the HPE Cray EX System Software Getting Started Guide S-8000 on the HPE Customer Support Center for more information on other product streams to be upgraded and configured after CSM.