Overview
This section walks the installer through the process of moving a LILT deployed system to an offline location. Please follow this documentation only if the internal IP of the server has changed during the migration.Required Tools
You will need to use SSH to connect to the systems.- On the Mac or Linux, you can open a terminal window and use ssh.
- On Windows, you can use the PuTTY ssh client.
Installer Privileges
Many sections of this document include text formatted to indicate console input and output. The commands are prefixed with a $ or # depending on if the administrator should run them as root or not. Additionally, to assist the user to know which machine to run commands on, the prefix node, master, and gpu will be given when the machine should be switched. All following commands after a switch should use those.Non-root commands
Root commands
Prerequisites
This upgrade document is only valid for an existing on-premise install previously installed using on-prem-installer scripts. Before running the scripts, we must prepare dependencies.Data Location
Please ensure that:- Docker images and RPM packages are mounted and available at $package_dir to all of the nodes (master, non-GPU, and GPU).
Host Name
This install is only valid if the Kubernetes node name is consistent during the process, eg. node machines should have the host names as: localhost.localdomain or localhost.node1 etc. You can set it using below commands:Backup
We will back-up the running system prior to upgrade. This backup is optional, but recommended, and will be used to restore the projects, documents and memory content in case of any issues.InstallDir
Backup Old Install Directory (used for previous install), referred asbackupInstall
in next steps.
Database
Backup database by running below commands on the installer system:Documents, Memory
Backup documents by copyingopenebs
mount folders in k8s-node.
Migration steps
After the server has been moved to the offline location, ensure its hostname still remains the same (eg. localhost.localdomain) and the IP address changes.Kubernetes will stop working due to the updated IP address. Follow the steps below to complete the migration.