1.3. Upgrading From LOCKSS 2.0-alpha2

1.3.1. Recommended Approach

If you have been using LOCKSS 2.0-alpha2 (or LOCKSS 2.0-alpha1, or the LOCKSS 2.0-alpha technology preview), we thank you for helping us bring LOCKSS 2.0 closer to fruition through your testing and feedback.

Although there is an upgrade path from LOCKSS 2.0-alpha2, LOCKSS 2.0-alpha3 is organized significantly differently than prior alpha releases, and we recommend installing LOCKSS 2.0-alpha3 from scratch when possible.

1.3.2. Upgrade Path

If you intend to upgrade a LOCKSS 2.0-alpha2 system, please read this section.

1.3.2.1. Updating the LOCKSS Installer

On the command line, in the lockss-installer directory, type:

git checkout master
git pull

to update to the latest version of lockss-installer from GitHub.

1.3.2.2. Running the Upgrade Command

On the command line in the updated lockss-installer directory, type:

sudo scripts/upgrade-alpha2-to-alpha3

The script will purge your Docker environment of components, configuration files and images used by the LOCKSS system.

1.3.2.3. Installing Snap and MicroK8s

The LOCKSS system’s containers are no longer orchestrated by Docker Swarm and no longer require Docker to run. The system now uses MicroK8s, a lightweight Kubernetes environment. To install the MicroK8s application package, you will need to install and use Snap. See Installing Snap and Installing MicroK8s.

1.3.2.4. Modifying the Environment

In order for LOCKSS 2.0-alpha3 to work properly, you will need to disable frontends to iptables like firewalld or ufw, and configure MicroK8s to use DNS in a way that avoids loopback addresses. See Disabling Packet Filters and Configuring DNS for details.

1.3.2.5. Reconfiguring the System

Upon successful completion, you will prompted to run scripts/configure-lockss. Be advised that the configuration process will prompt you for the PostgreSQL database password.

1.3.2.6. Starting LOCKSS

Once configuration is complete you can run lockss as usual with scripts/start-lockss.