Upgrade Paragon Automation
You can upgrade your existing older version of Paragon Automation to a later version of the same release using Paragon Shell. The upgrade functionality enables you to upgrade your Paragon Automation installation and all the applications running on it.
We do not support upgrading from Paragon Automation Release 2.0.0 to Release 2.1.0.
The upgrade process is automated by a set of Paragon Shell commands and carries out the required pre-upgrade system checks, retrieves the upgrade package, and executes the upgrade process on the cluster nodes. You can upgrade using an upgrade file that is either downloaded locally on your primary node or downloaded directly from a Web page.
During an upgrade, it's important that no change activities including onboarding of devices, provisioning of services or changing other configurations are done in the system. The upgrade will automatically reboot all components and there will be short unavailability during that time. The upgrade process does not affect the traffic through the network and once the upgrade is complete, the devices and services are not reconfigured.
We recommend that you back up your configuration before upgrading. For information on backing up your current configuration, see Back Up and Restore Paragon Automation.
To upgrade your Paragon Automation cluster:
Upgrade your installation and all the applications running on it using either the local option or the url option.
- Upgrade Paragon Shell and the OVA System Files.
Prerequisites to the Upgrade Process
Before you upgrade the Paragon Automation cluster, ensure the following.
-
Paragon Shell is accessible and operational.
-
The cluster nodes have the following free disk space available:
-
The primary node from which the cluster was deployed must have 15% of the total disk space + three times the upgrade file size free.
-
The other two primary and worker nodes must have 15% of the total disk space + the same amount as the upgrade file size free.
-
The worker node must have 15% of the total disk space free.
-
Upgrade Paragon Automation using one of the following options.
Upgrade using the local Option
Use this option for air-gapped environments where your paragon Automation installation does not have access to the Internet. However, you need to be able to copy the upgrade_paragon-release-build-id.tgz and upgrade_paragon-release-build-id.tgz.psig files to your primary node.
Log in as root user to the primary node from which the current cluster was installed. You are logged in to Paragon Shell.
Type
exitto exit from Paragon Shell to the Linux root shell.Copy the upgrade_paragon-release-build-id.tgz and upgrade_paragon-release-build-id.tgz.psig files, of the version to which you want to upgrade, to the /root/epic/temp folder.
You might need to download the upgrade_paragon-release-build-id.tgz and upgrade_paragon-release-build-id.tgz.psig files from the Juniper Software Download site to your local computer before copying it to the primary node.
(Optional) Use the
gpg --verifycommand to validate the digital signature of the upgrade file. For example:root@primary1:~# gpg --verify upgrade_paragon-release-2.1.0.6824.g83b20ea7fd.tgz.psig upgrade_paragon-release-2.1.0.6824.g83b20ea7fd.tgz gpg: Signature made Tue Apr 23 01:00:09 2024 UTC gpg: using RSA key 4B7B22C9C4FE32CF gpg: Good signature from "Northstar Paragon Automation 2024 ca@juniper.net" [ultimate]
Here
primary1is the installer primary node. Validation takes a couple of minutes to complete.Type
clito enter Paragon Shell.Use the following command to upgrade Paragon Automation.
request paragon cluster upgrade local filename upgrade_paragon-release-build-id.tgzFor example:
root@primary1> request paragon cluster upgrade local filename upgrade_paragon-release-2.1.0.6824.g83b20ea7fd.tgz Using local file /root/epic/temp/upgrade_paragon-release-2.1.0.6824.g83b20ea7fd.tgz for upgrade Upgrade is in progress ... Updated to build: paragon-release-2.1.0.6824.g83b20ea7fd Upgrade is successful
Your Paragon Automation installation and all the applications running on it are upgraded.
You can now upgrade Paragon Shell and the OVA system files. Go to Upgrade Paragon Shell and the OVA System Files.
Note that, the upgrade process takes a little over an hour to complete. Also, if you get disconnected from the VM during the upgrade process, you can periodically check the upgrade log file until you see an output similar to this:
root@primary1:~# cat /root/upgrade/upgrade.log <output-snipped> … PLAY RECAP ********************************************************************* 10.1.2.3 : ok=1819 changed=430 unreachable=0 failed=0 r escued=0 ignored=2 10.1.2.4 : ok=185 changed=26 unreachable=0 failed=0 r escued=0 ignored=0 10.1.2.5 : ok=185 changed=26 unreachable=0 failed=0 r escued=0 ignored=0 10.1.2.6 : ok=177 changed=25 unreachable=0 failed=0 r escued=0 ignored=0 Saturday 03 August 2024 09:41:53 +0000 (0:00:00.665) 1:26:57.926 ******* =============================================================================== user-registry : Push Docker Images from local registry to paragon registry - 532 .34s jcloud/airflow2 : Install Helm Chart ---------------------------------- 278.28s Install Helm Chart ---------------------------------------------------- 147.88s delete existing install config-map - if any --------------------------- 111.87s Save installer config to configmap ------------------------------------- 98.15s jcloud/papi : Install Helm Chart --------------------------------------- 97.77s Create Kafka Topics ---------------------------------------------------- 79.97s user-registry : Push Helm Charts to paragon registry ------------------- 78.70s systemd ---------------------------------------------------------------- 67.23s kubernetes/addons/helper-commands : Install Pathfinder Utility scripts -- 44.65s kubernetes/addons/helper-commands : Copy profiler to /opt/paragon/bin -- 39.79s registry : Copy nginx image on 10.1.2.4 -------------------------------- 37.46s registry : Copy nginx image on 10.1.2.5 -------------------------------- 37.04s registry : Copy nginx image on 10.1.2.6 -------------------------------- 36.80s registry : Copy nginx image on 10.1.2.3 -------------------------------- 36.03s Install Helm Chart ----------------------------------------------------- 34.49s registry : Copy zot image on 10.1.2.4 ---------------------------------- 33.29s registry : Copy zot image on 10.1.2.5 ---------------------------------- 32.46s registry : Copy zot image on 10.1.2.6 ---------------------------------- 31.67s registry : Copy zot image on 10.1.2.3 ---------------------------------- 30.25s Playbook run took 0 days, 1 hours, 26 minutes, 57 seconds registry-14272 Application Cluster upgraded to version build: paragon-release-2.1.0.6824.g83b20ea7fd!!!
Upgrade using the url Option
Use this option if your Paragon Automation installation has access to the Internet.
Log in as root user to the primary node from which the current cluster was installed. You are logged in to Paragon Shell.
Use the following command to upgrade Paragon Automation.
request paragon cluster upgrade url "https://juniper.software.download.site/upgrade_paragon-release-build-id.tgz?query_string"For example:
root@primary1> request paragon cluster upgrade url "https://cdn.juniper.net/software/paragon-images/upgrade_paragon-release-2.1.0.6688.g63026f4af7.tgz?query_string" Upgrading paragon cluster from https://cdn.juniper.net/software/paragon-images Downloading tarball file upgrade_paragon-release-2.1.0.6688.g63026f4af7.tgz Download file size: 19,526,900,113 bytes Current disk Usage: Total: 263,622,004,736 bytes Used: 83,496,677,376 bytes Available: 168,297,881,600 bytes Please wait for current download to finish... (File is large. It may take a while.) Upgrade tarball file is downloaded. Upgrade is in progress ... Updated to build: paragon-release-2.1.0.6688.g63026f4af7 Upgrade is successfulHere
primary1is the installer primary node.Your Paragon Automation installation and all the applications running on it are upgraded.
You can now upgrade Paragon Shell and the OVA system files. Go to Upgrade Paragon Shell and the OVA System Files.
Note that, the upgrade process takes a little over an hour to complete. Also, if you get disconnected from the VM during the upgrade process, you can periodically check the upgrade log file until you see an output similar to this:
root@primary1:~# cat /root/upgrade/upgrade.log <output-snipped> … PLAY RECAP ********************************************************************* 10.1.2.3 : ok=1820 changed=409 unreachable=0 failed=0 rescued=0 ignored=2 10.1.2.4 : ok=186 changed=28 unreachable=0 failed=0 rescued=0 ignored=0 10.1.2.5 : ok=186 changed=28 unreachable=0 failed=0 rescued=0 ignored=0 10.1.2.6 : ok=178 changed=26 unreachable=0 failed=0 rescued=0 ignored=0 Tuesday 20 August 2024 21:17:24 +0000 (0:00:00.812) 1:22:50.798 ******** =============================================================================== user-registry : Push Docker Images from local registry to paragon registry - 536.73s Create Kafka Topics --------------------------------------------------- 119.48s Install Helm Chart ---------------------------------------------------- 117.67s Save installer config to configmap ------------------------------------ 115.97s delete existing install config-map - if any --------------------------- 101.82s user-registry : Push Helm Charts to paragon registry ------------------- 86.73s systemd ---------------------------------------------------------------- 70.71s paragon-shell-config : Load paragon-shell initial configs on master node -- 64.99s kubernetes/addons/helper-commands : Install Pathfinder Utility scripts -- 51.74s jcloud/papi : Install Helm Chart --------------------------------------- 48.21s kubernetes/addons/helper-commands : Copy profiler to /opt/paragon/bin -- 44.40s kubernetes/addons/resource-reservation : Apply resource-reservation kube-cfg file -- 36.58s Install Helm Chart ----------------------------------------------------- 34.83s Verify Zookeeper ------------------------------------------------------- 27.61s Check activeReplicas --------------------------------------------------- 26.45s Create Database for pathfinder ----------------------------------------- 21.67s registry : copy cert files from control host to non first registry on 10.1.2.6 -- 21.56s registry : copy cert files from control host to non first registry on 10.1.2.5 -- 20.80s Update Kafka test topic configuration ---------------------------------- 20.05s Unpack 3rdparty OS packages -------------------------------------------- 19.89s Playbook run took 0 days, 1 hours, 22 minutes, 50 seconds registry-14112 Application Cluster upgraded to version build: paragon-release-2.1.0.6824.g83b20ea7fd!!!
Upgrade Paragon Shell and the OVA System Files
When your Paragon Automation installation and all the applications running on it are succesfully upgraded, you must upgrade Paragon Shell and the OVA system files.
Exit from the installer primary node Paragon Shell to the Linux root shell by typing
exit.Verify that the
upgrade_paragon-shell_ova-system.shshell script andrunscript are present in the /root/epic/ directory using theroot@primary1:~# ls /root/epiccommand.If the scripts are present, go to Step 3.
If the scripts are not present, copy the
upgrade_paragon-shell_ova-system.shandrunscripts from the /root/upgrade directory to the /root/epic/ directory.root@primary1:~# cp /root/upgrade/upgrade_paragon-shell_ova-system.sh /root/epic/ root@primary1:~# cp /root/upgrade/run /root/epic
Execute the Paragon Shell upgrade shell script.
root@primary1:~# bash /root/epic/upgrade_paragon-shell_ova-system.sh Upgrading paragon-shell... Updating paragon-shell for primary1...... Container paragon-shell Stopping Container paragon-shell Stopped Container paragon-shell Removing Container paragon-shell Removed paragon-shell Pulling paragon-shell Pulled Container paragon-shell Creating Container paragon-shell Created Container paragon-shell Starting Container paragon-shell Started Updating paragon-shell for primary2...... Container paragon-shell Stopping <output snipped> primaryname update-status primary1 ok primary3 ok primary2 ok primary4 ok paragon-shell upgrade successful! Updating OVA system files... OVA system files update successful!
Paragon Shell and the OVA system files are upgraded.
Note that, if you are rerunning upgrade on a node that has already been upgraded,
you won't need to copy the upgrade_paragon-shell_ova-system.sh
shell script and the run script to the
/root/epic/ directory, since the scripts must already
be present and updated in the directory. You can directly run the bash
/root/epic/upgrade_paragon-shell_ova-system.sh
command.
When rerunning upgrade, the CLI output is slightly different than when you are
upgrading a version for the first time. For example:
root@primary1> request paragon cluster upgrade url "https://cdn.juniper.net/software/paragon-images/upgrade_paragon-release-2.1.0.6688.g63026f4af8.tgz?query_string"
Upgrading paragon cluster from https://cdn.juniper.net/software/paragon-images
Downloading tarball file upgrade_paragon-release-2.1.0.6688.g63026f4af8.tgz
Download file size: 19,550,561,802 bytes
Current disk Usage:
Total: 263,622,004,736 bytes
Used: 101,841,793,024 bytes
Available: 149,952,765,952 bytes
Please wait for current download to finish... (File is large. It may take a while.)
Upgrade tarball file is downloaded.
Upgrade is in progress ...
Updated to build: paragon-release-2.1.0.6688.g63026f4af8
Paragon Cluster upgrade is successful!
Please continue to primary host node to upgrade Paragon-shell and update OVA system files by:
/root/epic/upgrade_paragon-shell_ova-system.sh