Who needs this section¶

IMPORTANT: User that currently have foundation v1.3.4 installed and want to upgrade.

If you do not have foundation v1.3.4 installed, please skip to next section.

asciinema(../assets/migracao-1.3.4.asciinema)

Foundation migration v1.3.4 to latest¶

To facilitate the version upgrade, a bash script was created for a single execution, in which the data folder is backed up to preserve the data of the applications that use local storage in the Foundation directory and a secure reinstallation is performed from the old version to the new one.

The foundation 1.3.4 is very different internally, and the configuration need to be remade. Then it's a good idea to output and save the current connection data. For this, with foundation 1.3.4 running:

docker ps --filter name=foundation_accounts-pg --format 'docker exec {{ .ID }} psql accounts accounts -c "SELECT * FROM ACCOUNTS_PROVIDER;"' | sh

 provider_type |                provider_config
---------------+------------------------------------------------
 SOLFIS        | {"url":"jdbcdb","user":"user","password":"pw"}
(1 row)

Migration script¶

Before executing the script, it is necessary to highlight a few points:

1. Have the system root user password at hand

2. If you don't already download the migration script, download the Synchro-Foundation new version(RPM file) for your environment. You can get it at: Download Foundation

3. The script performs a backup of the local storage (minio) of Foundation 1.3.4 to the home of the system, a folder will be created with the name foundation-data-bkp-'data of the backup in format (year, month , day)'. Exp: foundation-data-bkp-20190605

4. For the containment of possible problems, v1.3.4 is also completely backed up, together with images and data from the local storage if any, all content will be moved to a folder named with the prefix -v134-bkp in the same directory where the Foundation was installed.

Performing the migration¶

At the beginning of the process you will be asked for the password sudo so that all commands can be entered correctly, and so that there is no problem related to permission during the entire execution.

execute the steps described in install

The following instruction will appear, and you will be asked to manually enter the path and file for the update:

$ ##### Start new package install #####

$ Enter the file path to foundation installation file: <TYPE_THE_FOUNDATION_RPM_PATH_HERE>

When the installation is complete, the first configuration of the foundation will start, which is very similar to the old version, and which can be found in detail step by step in this link.

The following options will be requested and need to be filled:

$ INFO[0000] Configuring Foundation
$ Foundation Namespace []:
$ Foundation volume location []:
$ Foundation volume driver []:
$ Change Network Configuration? (eno1 - y/n): y

$ Available network interfaces on this machine:
$ eno1 172.27.11.190 172.27.0.0/16
$ eno1 fe80::2d84:982c:1a61:aa32 fe80::/64

$ (Network) Define which interface to use []:
$ (Network) Foundation services custom subnet []:
$ (Network) Foundation ingress subnet []:
$ (Network) Foundation ingress gateway []:

$ Change Proxy Configuration? (y/n): y
$ Define new proxy port []:
$ Enable TLS (y/n) []:

$ Change Storage Configuration? (y/n): y
$ (Storage) Type (Local/Remote) []:

$ INFO[0049] Applying settings
$ INFO[0118] Done

After finishing the configuration, permissions of some directories will be changed for the non-root user of the system so that any future execution / maintenance does not require this type of access.

At the end, the Foundation will start and be ready for use.

Issues downloading older reports¶

If you have ant issue download older reports, maybe some issue in data copy step. You can fix it with:

cp -r <path-to-old-foundation-1.3.4>/system/objectstore/data/reinf/* <path-foundation>/system/<namespace>/foundation/storage/

If the error persist contact Foundation support team