2. Upgrading From LOCKSS 2.0-alpha5

Note

This chapter describes how to upgrade an existing LOCKSS 2.0-alpha5 system to 2.0-alpha6. If you are installing the LOCKSS 2.x system for the first time, please see the installation instructions in the next chapter:

Installing the LOCKSS System

Tip

Before you begin the upgrade, we strongly recommend you first bring your operating system up to date by applying security updates and upgrading installed packages. Ask your system administrator or see Operating System Updates in the appendix.

2.1. Stop LOCKSS 2.0-alpha5

The first step is to stop the LOCKSS 2.0-alpha5 system. Log in as the lockss user and run the following command in the LOCKSS Installer Directory (by default $HOME/lockss-installer, typically /home/lockss/lockss-installer).

scripts/stop-lockss

You may verify all LOCKSS components have stopped by running the following command:

k3s kubectl get deployments -n lockss

which should return:

No resources found in lockss namespace.

2.2. Update the LOCKSS Installer

As of 2.0-alpha5, the official way to install and upgrade the LOCKSS Installer is using the LOCKSS Downloader, rather than cloning the LOCKSS Installer as a Git project. The instructions below detail the use of the LOCKSS Downloader. (Advanced users may continue to use git if they wish; please see Downloading the LOCKSS Installer using git for instructions.)

As the lockss user, run either this curl command:

curl -sSfL https://lockss.org/downloader | sh -s -

Or this wget command:

wget -qO- https://lockss.org/downloader | sh -s -

This will download and invoke the LOCKSS Downloader, which in turn will install the latest version of the LOCKSS Installer into the default LOCKSS Installer Directory ($HOME/lockss-installer). If you are using a custom LOCKSS Installer Directory DIR, remember to use --download-dir=DIR; see Running the LOCKSS Downloader for details.

2.3. Run the Upgrade Script

The next step is to update archived content from the previous release version. As the lockss user, run the following command in the LOCKSS Installer Directory:

scripts/upgrades/upgrade-to-alpha6

Hint

If it takes more than a few seconds for upgrade-to-alpha6 above to run, the reindexing of all previously archived content which occurs the first time you start 2.0-alpha6 after upgrading from 2.0-alpha5 may take prohibitively long. This performance issue will be addressed in the next release. If you do not need the previously stored content during alpha testing, you could delete it and skip this reindexing step; see Resetting the System to a Blank State.

2.4. Re-run the Configure Script

Re-run the configuration script by running the command below and follow the instructions in Configuring the LOCKSS System to ensure all existing configuration parameters are still correct and to configure any new parameters:

scripts/configure-lockss

2.5. Start LOCKSS 2.0-alpha6

Follow the instructions in Running the LOCKSS System to start your LOCKSS 2.0-alpha6 instance:

scripts/start-lockss

Hint

If it takes more than a few seconds for upgrade-to-alpha6 above to run, the reindexing of all previously archived content which occurs the first time you start 2.0-alpha6 after upgrading from 2.0-alpha5 may take prohibitively long. This performance issue will be addressed in the next release. If you do not need the previously stored content during alpha testing, you could delete it and skip this reindexing step; see Resetting the System to a Blank State.