Performing an Offline Installation
The offline installation scenario is used when there is no internet access to download the required Lightbits RPMs and their dependencies. In such a case, the machine being used for installation should include the Lightbits cluster software RPM files and their dependencies.
During the offline installation, the software packages are copied to the target machine and installed locally.
To complete the offline installation:
- Copy the packages to the installation server.
- Enter the following commands on the installation machine. When installing offline, the relevant servers are configured in the Hosts file, as detailed in Inventory Structure and Adding the Ansible Hosts File. Starting with version 3.14, Ansible variables have been moved to all.yml. See Configuring Global Variables in Ansible for additional information.
source_type=offline
source_rpms_dir=<path to rpms>
source_dependencies_rpms_dir=<path to dependencies rpms>
dest_dir=<path>
For example:
[duros_nodes:vars]
source_type=offline
source_rpms_dir="/root/lightos_release/target_rpms"
source_dependencies_rpms_dir="/root/lightos_release/deps"
dest_dir="/tmp/rpms"
Offline Ansible Controller Installation and Self-Signed Certificates
The Lightbits cluster installation requires SSL certificates. You can provide these certificates, or the playbook will automatically generate self-signed certificates. To create these certificates, Ansible
downloads some binaries from the internet at runtime.
In case of an offline Ansible
controller, the installation script requires that certificates_directory
will be present and contain all needed certificates before running the playbook.
This directory and its content can come from two sources:
- If you bring your own organization certificates.
- Use the self-signed certificates generated by the initial cluster installation process.
You will need to copy the folder credentials_directory
to the Ansible Controller
machine, before running the installation script.
In the offline installation method, before executing the actual install/upgrade commands, it is necessary to ensure that YUM repositories on each local storage server are disabled to prevent attempts at remote access.