Note: The CSM upgrade to CSM 1.6 is done with IUF.
This procedure is used when performing an upgrade of Cray System Management (CSM) along with additional HPE Cray EX software products at the same time. This procedure would be used when upgrading from one HPC CSM Software Recipe release to another.
This procedure is not used to perform an initial install or upgrade of HPE Cray EX software products when CSM itself is not being upgraded. See Install or upgrade additional products with IUF for that procedure.
This procedure streamlines the rollout of new images to management nodes. These images are based on the new images provided by the CSM product and customized by the additional HPE Cray EX software products, including the User Services Software (USS) and Slingshot Host Software (SHS).
All stages of iuf
are executed in this option. All of the new product software provided in the
recipe release is deployed and all management NCNs and managed
compute nodes and application nodes are
rebooted to new images and Configuration Framework Service (CFS)
configurations. Manual operations are documented for procedures that are not currently managed by IUF.
The upgrade workflow comprises the following procedures. The diagram shows the workflow and the steps below it provide detailed instructions which must be executed in the order shown.
The CSM upgrade steps are run automatically, either directly through IUF stages or by a hook automatically executed at the beginning or end of an IUF stage. For more detail about about the CSM upgrade hooks, see the section description of CSM upgrade hooks.
Read the Important Notes section of the CSM 1.5.0 or later to 1.6.0 Upgrade Process documentation.
Prepare for Upgrade to Next CSM Major Version in the CSM 1.5 documentation.
Prepare for the upgrade procedure and download product media
Follow the IUF Prepare for the install or upgrade instructions to set environment variables used during the upgrade process.
Download the desired HPE product media defined by the HPC CSM Software Recipe to ${MEDIA_DIR}
, which was defined in the previous step.
Product delivery
NOTE The CSM upgrade prerequisites are automatically executed in a hook run before
pre-install-check
.
Follow the IUF Product delivery instructions.
SMA 1.10.15 and later includes an upgraded LDMS that introduces an incompatibility with configuration files used in prior versions.
Configuration
Follow the IUF Configuration instructions.
Image preparation
Follow the IUF Image preparation instructions.
Backup
Follow the IUF Backup instructions.
Management rollout
NOTE The upgrade of CSM services and validation of CSM health occur automatically in a hook executed before the first management node is rolled out.
Follow the IUF Management rollout instructions.
Deploy product
NOTE The application of networking changes and CoreDNS anti-affinity changes along with the upgrade of the Kubernetes control plane is performed in a hook automatically executed after
deploy-product
.
Follow these IUF instructions in order:
Managed rollout
Follow the IUF Managed rollout instructions.
The IUF upgrade workflow is now complete. Exit any typescript sessions created during the upgrade procedure and remove any installation artifacts, if desired.
The hooks below are automatically executed when CSM is being upgraded with IUF.
CSM upgrade prerequisites
CSM upgrade prerequisites are executed in a hook run before pre-install-check
. This executes steps that are dependencies for later CSM upgrade steps.
This includes some service chart upgrades, uploading base NCN images to be used later in prepare-images
, and other setup steps.
The specific script that is being executed is /usr/share/doc/csm/upgrade/scripts/upgrade/prerequisites.sh
.
Upgrade of CSM services and validation of CSM health
The upgrade of CSM services and validation of CSM health are performed in a hook executed before management-nodes-rollout
. This hook is only executed before the first NCN is upgraded.
The specific script that executes the CSM services upgrade is /usr/share/doc/csm/upgrade/scripts/upgrade/csm-upgrade.sh
.
Application of networking changes, CoreDNS anti-affinity, upgrade of the Kubernetes control plane
The application of networking changes and CoreDNS anti-affinity changes along with the upgrade of the Kubernetes control plane is performed in a hook executed after deploy-product
.
The specific scripts executed as part of this hook are /srv/cray/scripts/common/apply-networking-manifests.sh
, /usr/share/doc/csm/upgrade/scripts/k8s/apply-coredns-pod-affinity.sh
, and /usr/share/doc/csm/upgrade/scripts/k8s/upgrade_control_plane.sh
.