
IPU-POD128 build and test guide
5.3.1 Download IPU-M2000 software update bundle
The management server needs to be loaded with the correct IPU-M2000 software update bundle before the
software update of the IPU-M2000s can be performed. To perform the download, follow these steps:
1. Log in as
ipuuser
2. Go to the Graphcore
and download the latest release into the
$HOME /IPU-M_releases
directory
3. Follow the install instructions in the release notes, and perform:
tar xvfz <tar-ball.tgz>
The unpacking of the IPU-M2000 software onto the management server’s file system will automatically create a
directory tree with a leading directory containing the release version number. This allows several releases to be
kept on the management server, in case there is a need to revert to a previous release on the IPU-M2000s. If
you do not need to keep them, the older releases (both the unpacked files and the downloaded tar file) can be
removed from the management server.
5.3.2 Software update of all IPU-M2000s
Having unpacked the software release onto the server file system, follow these steps:
1. Change directory:
cd $HOME/IPU-M_releases/IPU-M_SW_<release version>
2. Run the commands:
$
virtualenv -p python3 venv
$
source
venv/bin/activate
$
pip3 install -r requirements.txt
$
./rack_tool.py upgrade
rack_tool
will read a default config file to learn how to access the IPU-M2000s. The default location of this file
is:
$HOME/ipuuser/.rack_tool/rack_config.json
.
This file can be edited by a site administrator who integrates the IPU-POD
64
into the site-specific network in
cases where the default IPU-POD
64
IP address plan collides with the site-specific network.
The upgrade process will take several minutes and all the IPU-M2000s will be upgraded in parallel to make this
time as short as possible.
The upgrade process at the end will perform a few reboots in order to activate the new software.
rack_tool
finally verifies that the upgrade completes with all sub-components being upgraded to the same ver-
sion. Verify that this version corresponds to what is defined in the release notes to check that the upgrade pro-
cedures have been followed correctly.
5.3.3 IPU-M2000 GW root file system config files
The IPU-POD
64
and IPU-M2000 support a simple concept where a set of IPU-M2000 Gateway OS config files
residing on the management server will be copied to the IPU-M2000 Gateway after an update. This feature is
optional.
With multiple IPU-POD
64
racks installed, this overwriting (overlay) concept will support a site-specific config con-
trol on top of the standard Gateway distribution that always brings default config files. The current implementation
requires all IPU-M2000s to be identically configured.
Any config files on the Debian OS in the Gateway can be overwritten by these server-side maintained overlay
files.
These files reside under
ipuuser
at
$HOME/.rack_tool/root-overlay/
.
Note:
Make sure the IP addresses in these files are correct and point to the management server’s IP address
Version: latest (2021-11-25)
78