Configuring Global Variables in Ansible

Review the configuration of the global variables in the Ansible file all.yml, located in the following location:

~/light-app/ansible/inventories/cluster_example/group_vars/all.yml

File Example

#nvme_subsystem_nqn_suffix: "some_suffix"

ipacl_explicit_allow: false

persistent_memory: true

start_discovery_service_retries: 5

#nvme_subsystem_nqn_suffix: "some_suffix"

chrony_enabled: true

​

local_repo_base_url=https://dl.lightbitslabs.com/<YOUR_TOKEN>/lightos-3-(Minor Ver)-(Rev)-rhl-(8/9)/rpm/el/8/$basearch

​

#optional

#listen_on_all_interfaces: false 

​

#optional clusterId - if set will be injected to all nodes, else will be generated by the deployment.

#clusterId: ae7bdeef-897e-4c5b-abef-20234abf21bf

If all of the machines in the cluster have persistent memory (DCPMM) installed, the persistent_memory flag must be set as follows:

persistent_memory: true

If there are machines in the cluster that do not have PMEM installed, set this flag to false.

ipacl_explicit_allow

Support for restricted/non-restricted access to a cluster's data ports (nvme/tcp and discovery service). In restricted mode (ipacl_explicit_allow = true), the Lightbits cluster will maintain an allowed list of IPs per volume that allows clients to access this volume. In unrestricted mode (ipacl_explicit_allow = false), any IP address can be used to access the data ports. Any further port restrictions should be managed by your FW rules.

See IP ACL Configuration for additional information.

Chrony

Chrony is the default network synchronization method for Lightbits clusters.

chrony_enabled: true

Chrony

In Chrony configurations - which are the default for Red Hat 8 based releases and onward - configure the all.yml settings.

Make sure that the Chrony service is configured on your servers before the installation.

Listen on All Interfaces

Configure the frontend to bind to all network interfaces, rather than a specific one.

# Default to configure the system frontend to listen on all interfaces

# if true the param `ipAddr` in /etc/node-manager/duroslight-n.yaml: will be set to - '::'

listen_on_all_interfaces: true

Online Repo Information

local_repo_base_url=https://dl.lightbitslabs.com/<YOUR_TOKEN>/lightos-3-(Minor Ver)-(Rev)-rhl-(8/9)/rpm/el/8/$basearch

• The section describes from where Lightbits will be installed. In this case/example, the repo URL is provided, as this uses the online method. However, for the offline installation method, this section is different. For more, see Single-IP-Dual-NUMA Configuration.
• The "local___repo_base_url" field must be filled in with the <TOKEN> and the remainder of the URI, to properly direct the Ansible installation to the correct Lightbits repository. Different release versions will have slightly different paths. The “local_repo_base_url” must be correct or else the installation will fail. This can be a Cloudsmith link or any HTTP/HTTPS accessible point in the local network or internet. The link must point to a valid yum repo with a "repodata" directory. The value is used by Ansible for the the baseurl key in /etc/yum.repos.d/lightos.repo. The $basearch variable is replaced by the OS automatically with the architecture of the Lightbits server (e.g., x86_64).
• Also in this example, there is a “local_repo_base_url” entry that includes <YOUR_TOKEN>. This information was provided to you in the Lightbits Customer Addendum. You will need to enter this value here before proceeding.

Server Variables

Offline Installations

auto_reboot=true

cluster_identifier=ae7bdeef-897e-4c5b-abef-20234abf21bf

source_type=offline

source_etcd_binary="/root/install/deps/etcd-v3.4.1-linux-amd64.tar.gz"

source_rpms_dir="/root/install/target_rpms"

source_dependencies_rpms_dir="/root/install/deps"

dest_dir="/tmp/rpms"

• source_type: Set to "offline" for offline installations. The default is "online".
• source_etcd_binary, source_rpms_dir, source_dependencies_rpms_dir: Direct paths on the Ansible host to the etcd binary, RPMs, and dependencies directories. Paths must be relative to where the Ansible command is run (baremetal host or inside Docker).
• dest_dir: Where RPM packages are stored on the Lightbits node during installation.

Single IP Dual NUMA Configuration

The Single IP dual NUMA configuration (see Single-IP-Dual-NUMA Configuration), requires changes to the all.yml file. Follow the directions in that section to properly configure this setup.