Upgrade All-In-One (Binary)
This page introduces how to upgrade BladePipe On-Premise Binary version.
Prerequisites
Please make sure that the BladePipe Console has been installed via Binary.
If not, please install the Console following the doc Install All-in-One (Binary).
Procedure
Download the Package
-
Get the link of the latest installation package at BladePipe website.
-
Switch to the user
bladepipeon the machine where BladePipe is deployed.sudo su - bladepipe -
Download the package to the tar_gz directory and extract it.
cd ~/tar_gz
wget "{paste the download link got from BladePipe website}" -O bladepipe.tgz
tar -xaf bladepipe.tgz
Upgrade Automatically
-
Make sure that the Console can log in to the target node through SSH.
infoIf the Console and Worker are deployed on the same server, also make sure that
ssh bladepipe@127.0.0.1can log in successfully on that server. The automatic upgrade executes upgrade scripts through this SSH channel.
Upgrade Console
-
Log in to the Console, and click Sync Settings > Console > Upgrade.
-
Enter the node's username and password or key address to upgrade.
Upgrade Worker
-
Log in to the Console, and click Sync Settings > Sync Worker > Workers > More > Upgrade Worker.
-
Enter the Worker's username and password or key address to upgrade.
-
(Optional) If an upgrade error occurs and BladePipe is not functional, you can roll back: click Sync Settings > Sync Worker > Workers > More > Roll Back Worker.
Upgrade Manually
-
Download and extract the manual upgrade scripts.
wget -cO "bp_upgrade_scripts.tgz" "https://bladepipe-docker.s3.amazonaws.com/scripts/bp_upgrade_scripts.tgz"
mkdir -p ~/tar_gz/scripts
tar -zxvf bp_upgrade_scripts.tgz -C ~/tar_gz/scripts
Upgrade Console
-
Run the upgrade script.
bash ~/tar_gz/scripts/upgrade_console.sh -
(Optional) If an upgrade error occurs and BladePipe is not functional, run the rollback script.
bash ~/tar_gz/scripts/rollback_console.sh
Upgrade a Worker
-
Run the upgrade script.
bash ~/tar_gz/scripts/upgrade_worker.sh -
(Optional) If an upgrade error occurs and BladePipe is not functional, run the rollback script.
bash ~/tar_gz/scripts/rollback_worker.sh