Updating within the same version
Online update
Before updating, open the page v1.2_1.5 Stable versions and determine whether a new Ansible playbooks archive, listed in the Online installation column, has been released as part of the update.
No new archive for online installation playbooks has been released
Updating within the same version to newer packages does not require running a playbook. It is sufficient to perform the following steps:
Log in to the server and navigate to the directory where Eltex NAICE is installed (default: /etc/docker-naice):
cd /etc/docker-naice
Run the commands to stop the containers, download new images, and start the containers using the new version:
docker compose pull && docker compose down && docker compose up -d
If newer builds are available in the remote repository, they will be updated. When using a multi-host high-availability deployment, these commands must be executed on each host where the system is deployed.
An alternative option is to use a dedicated playbook that executes the commands above:
ansible-playbook update-naice-images.yml
A new archive for online installation playbooks has been released
Download the installation playbook archive again and repeat the installation procedure according to the installation instructions:
- for a single-host installation: v1.2_3.4 Installation using Ansible playbooks (stand-alone)
- for a high-availability installation: v1.2_3.5 High-availability installation (using VRRP) or v1.2_3.6 High-availability installation (without using VRRP).
If any variables in group_vars/all.yml have been modified, the values from the old all.yml file must be transferred to the new one before installation. Verify that the same Docker subnets used by the current installation are specified in group_vars/networks.yml.
After completing the repeated installation, you must update the images manually as described above, or run the following playbook on each host:
ansible-playbook update-naice-images.yml
Updating container images after reinstalling with the playbook is a necessary step, since the images are not downloaded automatically when updating within the same version.
Updating an installation in an isolated network
Updating within the same version in offline installation mode requires downloading the installation archive again and performing the update by reinstalling according to the selected deployment mode and operating system type.
- for a single-host installation: v1.2_3.4.1 Installation in an isolated network (stand-alone).
- for a high-availability installation: v1.2_3.5.1 High-availability installation in an isolated network (using VRRP) or v1.2_3.6.1 High-availability installation in an isolated network (without using VRRP).
If any variables in group_vars/all.yml have been modified, the values from the old all.yml file must be transferred to the new one before installation. Verify that the same Docker subnets used by the current installation are specified in group_vars/networks.yml.
After completing the repeated installation, you must update the images manually as described above, or run the following playbook on each host:
ansible-playbook update-naice-images.yml
Updating installation containers in an isolated network
If there have been no significant changes to the variables and configuration (i.e., no new archive with the online installation playbooks has been released), you can update the containers in an isolated network without running the Ansible playbooks. To do this:
- Download the offline installation archive.
- Extract the archive.
- Transfer the naice_images.tar archive to the NAICE host (all hosts in case of a high-availability installation). After extracting the archive, the file is located at:
naice_install/naice_images/naice_images.tar
- Load the container images on each host using the following command:
sudo docker load -i naice_images.tar
- Stop the NAICE services on each node. Run the command from the installation directory (by default,
/etc/docker-naice):sudo docker compose down
- If a high-availability installation is used, in addition to the NAICE services, stop the PostgreSQL database on each node. Run the commands from the installation directory (by default,
/etc/docker-naice):# for the first database node sudo docker compose -f docker-compose.repmgr.yml down postgres-1 # for the second database node sudo docker compose -f docker-compose.repmgr.yml down postgres-2
- For a multi-host installation, start the database sequentially on each node:
sudo docker compose -f docker-compose.repmgr.yml up -d
- Start the NAICE services:
sudo docker compose up -d