You can upgrade to Paragon Automation Release
22.1
from Releases 21.3 and
21.2.
If you are using Paragon Automation Release 21.1, you cannot upgrade to any later release and
must perform a fresh installation of Release
22.1.
Before you
upgrade:
- Verify that the control host and cluster nodes meet the preparation prerequisites
described in Installation Prerequisites on Ubuntu or Installation Prerequisites on CentOS as required.
- (Optional) Back up the config-dir directory on
your control host to an alternate directory or to a remote location. The
config-dir contains the
inventory, config.yml, and
id_rsa files for your current Release
21.3
setup.
If
the upgrade fails, you can reinstall your current setup with the same
installation configuration files. See Back Up the Control Host.
- (Optional) Back up your current Release
21.3
configuration.
If
the upgrade fails, you can restore your current deployment from the
backed-up configuration. See Back Up the Configuration.
Upgrade
from Release
21.3
to Release
22.1
-
Log in to the control host. You can use the same host that you used to install
Release
21.3.
-
Download the Release
22.1
files to a download folder on the control host.
Make the
run
script executable by using the chmod +x run command.
-
Initialize the new configuration folder. You can use the same folder name that you did
for Release
21.3,
as long as
you
backed up the contents of the folder to another location. For the purpose of this topic,
we will use the same folder name, config-dir.
# ./run -c config-dir init
-
Run the
inv command to input information into the inventory file. Use
the same IP
addresses of the primary and worker nodes
as
you did for your current Release
21.3
setup.
# ./run -c config-dir inv
-
Copy the private key that you generated while installing the SSH server during the
cluster node preparation
process to
the config-dir directory, where the inventory file is saved.
# cd config-dir
# cp ~/.ssh/id_rsa .
-
Configure the installer using the
conf command.
# ./run -c config-dir conf
Enter the same configuration values as you did for your current Release
21.3
setup.
Note:
If you choose to manually edit the config.yml file, ensure that
the format of the ingress_vip is a list of IP addresses. For
example:
ingress_vip:
- 10.10.3.4
- 10.10.6.7
-
Install the Release
22.1
Paragon Automation
cluster.
# ./run -c config-dir deploy
-
Log in to the worker nodes.
Use a text editor to configure the following recommended information for Paragon
Insights in the limits.conf and sysctl.conf
files.
-
# vi /etc/security/limits.conf
# End of file
* hard nofile 1048576
* soft nofile 1048576
root hard nofile 1048576
root soft nofile 1048576
influxdb hard nofile 1048576
influxdb soft nofile 1048576
-
# vi /etc/sysctl.conf
fs.file-max = 2097152
vm.max_map_count=262144
fs.inotify.max_user_watches=524288
fs.inotify.max_user_instances=512
Repeat this step for all worker nodes.
-
Open a browser, and enter in the URL
field either
the hostname of the main Web application or the VIP
address
of the ingress controller that you configured in of
the
installation wizard.
-
Log in using
admin as the username and the previously configured password for
Release
21.3.
The Dashboard page
appears.
You've
successfully upgraded and logged in to the Paragon Automation UI.
-
Update the URL to access the Paragon Automation UI in Administration
>
Authentication
>
Portal Settings to ensure that the activation e-mail sent to users for
activating their account contains the correct link to access the GUI. For more
information, see Configure Portal Settings.
Upgrade Failure Scenario
If upgrade fails and you are unable to install Release
22.1,
you must reinstall
Release
21.3
to restore operations. Use one or both of the following options to restore the
cluster.
You cannot restore a backed-up Release 22.1 setup on an upgraded Release 22.1
cluster.
That is, if you back up a Release
21.3
setup, and then successfully upgrade it to a Release
22.1
setup, you cannot restore the Release
21.3
configuration using the
backup.
