Cluster Upgrade
Download Upgrade Contents
Info
Within the labs we have mounted some external media which houses the required files. You will need to mount your own drive or copy over the files using SCP or similar.
Additionally in a real world scenario you need to use your existing HyperStore license when extracting the binaries, this will be available for download from the customer portal. Care must be taken to ensure you select the correct license from those available to you.
Instructions
- SSH into your Config / Installer node (Node 1) as sa_admin and create a new session using option 0
- Create an upgrade directory
mkdir CloudianPackages7.5.3
- Change to that directory
cd CloudianPackages7.5.3
- Copy the upgrade binary to your upgrade directory
cp /studentfiles/CloudianHyperStore-7.5.3.bin .
- Copy the upgrade signature file to your upgrade directory
cp /studentfiles/CloudianHyperStore-7.5.3.bin.sig .
- Copy the license file to your upgrade directory
cp /opt/cloudian/conf/cloudian_license.lic .
- Ensure files are as expected
ls -l
Software Upgrade
Instructions
-
Modify the file permission to make it executable
chmod +x CloudianHyperStore-7.5.3.bin
-
Extract binary by executing
hsrun --root CloudianHyperStore-7.5.3.bin cloudian_12345.lic
Warning
Ensure that the version you are unpacking is the version you are upgrading to. Unpacking an older binary version (such as your current deployment version) will cause problems with your cluster.
Instructions
- Run the command
hspkg install
to continue with the upgradehspkg install
- You will be presented with a menu, and an option to upgrade from 7.5.2 to 7.5.3
- Type '3' to select the option to upgrade then press Enter
- When asked if you would like to run basic tests, answer No
- When asked if you want to proceed with upgrade, type Yes
The upgrade will take about 45 minutes to complete.
Instructions
- Once the upgrade finishes, you will return to the menu of the cloudianInstall.sh script
- Select 'x' to exit the script
Warning
It is important to exit out of the cloudianInstall.sh
script when you are done, as other
operations done through the CMC will also utilize the same script. If there is
a process using the script (such as your terminal), other operations will fail.