- Host Configuration
- Runtime Node Configuration
- SDF Configuration
- Managing the Runtime
- Logfile Management
- Application Development
- Dynamic Driver Development
- Ecosystem Tools
Migrating from Pre-Release to Core
1. Migrating from earlier versions of PolySync
If you have a pre-release version of PolySync installed─2.0.1-pr.1 to 2.0.8-pr.8─you must follow the migration steps before upgrading to PolySync Core and Ubuntu 16.04.
Not following these steps will result in missing configuration and logfile sessions.
1.1 Prepare your files for migration
PolySync has provided a migration script for those of you who are upgrading from a pre-release version to PolySync Core.
The migration script is going to look in the default location of
/usr/local/polysync/ for the existing install and do two things:
- Import the configuration and logfile sessions that are currently in $PSYNC_HOME to theexpected locations in
- Creates a backup tarball of the existing installation
- The backup tarball can be copied to any Ubuntu 16.04.1 machine and the migration script will place the files where they’re expected for PolySync Core
- Note: the migration script will delete the contents of
$PSYNC_HOMEafter creating the backup tarball
The migration script
polysync-prerelease-migrate ships with the PolySync Core release packages.
1.1.1 Run the migration script on the pre-release host
- Run the pre-release migration script
$ cd ~/Downloads
$ tar xf polysync-core_2.0.11.tar.gz
$ cd polysync-core_2.0.11
$ sudo ./polysync-prerelease-migrate
- Copy the generated
/opt/polysync-backup-<UTC-timestamp-here>.tar.gzto a temporary USB storage device
- Install Ubuntu 16.04.1
2. Migrate pre-release files to Ubuntu 16.04.1
Once the ECU has been updated to the supported Ubuntu distribution the migration script can be run a second time. The migration script will take a path to the backup file created in the previous step as a command line argument.
- Copy the
polysync-prerelease-migratescript from the PolySync Core release package
- Copy the
- Run the migration script, and pass in a path to the pre-release backup archive
$ sudo ./polysync-prerelease-migrate /opt/polysync-backup-<your-UTC-timestamp-here>.tar.gz
The migration script will decompress the archive in a temporary location and then copy the configuration and logfile files to the expected locations on the system in
The script can take some time, especially if there were large logfile sessions on the pre-release host.
Note: if the migration script detects an existing SDF on the new system, it will not overwrite the newer SDF in
$HOME/.local/share/polysync/config with the SDF from the original machine.
2.1 Replacing the original SDF
To install the original SDF on the new system, extract the SDF file from the
polysync-backup-*.tar.gz tarball and copy it to the new location:
$ cd ~/Downloads $ tar xf polysync-backup-<UTC-timestamp-here>.tar.gz $ cp polysync/db/psync.sdf $PSYNC_USER_HOME/config/
Now that your pre-release files have been migrated to your new system you can install PolySync.
2.2 Moving your license to a new host
On your pre-release host run:
$ polysync-license-tool -a ***************************** *** PolySync License Tool *** API Build Version: 2.0.8-1478129437 Host ID: '(Ethernet) xxxxxxxxxxxx' [...] License status: valid *****************************
After upgrading to Core 2.0 run the
polysync-license-tool -a command once more.
Send an email to email@example.com telling them you are migrating to a new host. Be sure to include the
Host ID: '(Ethernet) xxxxxxxxxxxx' from your pre-release and new host systems.