Verifying Hosts Connection
Verify connectivity from the Ansible Installation host to all of the machines where Lightbits will be installed.
First, verify that ping works. Then verify that SSH connectivity works using the normal user and then using a privileged (become) user.
For each command below, two variations are provided. Choose the "Ansible Method" if you are installing via Ansible, or follow the "Docker Method" if you are using Docker for installation.
Additionally, each Docker example requires the correct Docker URL: docker.lightbitslabs.com/lightos-3-(Minor Ver)-(Rev)-rhl-(8/9)/lb-ansible:v9.1.0. Note that the path bit is incomplete and requires substitution. Refer to the Lightbits Installation Customer Addendum for the correct Docker image URL.
Testing Connectivity via Ping
Use the ping command to verify that all machines in the cluster respond. Enter one of the following commands based on if Ansible or Docker method is used:
# If using Ansible Method, run this:cd ~/light-appansible -i ansible/inventories/cluster_example/hosts all -m ping# If using Docker Method, run this:cd ~/light-appdocker run -it --rm --net=host \ -e UID=`id -u` \ -e GID=`id -g` \ -e UNAME=$USER \ -v `pwd`:/ansible \ -w /ansible \ -e ANSIBLE_LOG_PATH=/ansible/ansible.log \ docker.lightbitslabs.com/lightos-3-(Minor Ver)-(Rev)-rhl-(8/9)/lb-ansible:v9.13.0 \ sh -c 'ansible -i ansible/inventories/cluster_example/hosts all -m ping'A successful response from this Ansible ping is as follows:
server02 | SUCCESS => { "ansible_facts": { "discovered_interpreter_python": "/usr/bin/python" }, "changed": false, "ping": "pong"}Server00 | SUCCESS => { "ansible_facts": { "discovered_interpreter_python": "/usr/bin/python" }, "changed": false, "ping": "pong"}server01 | SUCCESS => { "ansible_facts": { "discovered_interpreter_python": "/usr/bin/python" }, "changed": false, "ping": "pong"}If you see an error related to ssh-key authentication, see Troubleshooting.
Testing Connectivity via SSH
This tests a connection using the user configured with the ansible_ssh_user field in the "hosts" file. Enter one of the following commands based on if Ansible or Docker method is used:
# If using Ansible Method, run this:cd ~/light-app ansible all -i ansible/inventories/cluster_example/hosts -m command -a id# If using Docker Method, run this:cd ~/light-appdocker run -it --rm --net=host \ -e UID=`id -u` \ -e GID=`id -g` \ -e UNAME=$USER \ -v `pwd`:/ansible \ -w /ansible \ -e ANSIBLE_LOG_PATH=/ansible/ansible.log \ docker.lightbitslabs.com/lightos-3-(Minor Ver)-(Rev)-rhl-(8/9)/lb-ansible:v9.13.0 \ sh -c 'ansible all -i ansible/inventories/cluster_example/hosts -m command -a id'The expected output for each machine is its "id" output, which should return the username and groups.
The following is an example of a good output:
server00 | CHANGED | rc=0 >>uid=0(root) gid=0(root) groups=0(root)server01 | CHANGED | rc=0 >>uid=0(root) gid=0(root) groups=0(root)server02 | CHANGED | rc=0 >>uid=0(root) gid=0(root) groups=0(root)Any output other than an error is a good output. If there are connection issues, verify that SSH is properly set up and make sure that the ansible_ssh_user and ansible_ssh_pass are properly configured.
After the above command is successful, test that the privileged user can access the machines over SSH. Note that if the ansible_ssh_user is root, you can skip this final verification. However to run this command enter one of the following commands based on if Ansible or Docker method is used:
If using the Ansible method, run this:
cd ~/light-app ansible all -i ansible/inventories/cluster_example/hosts -m command -a id -bIf using the Docker method, run this:
cd ~/light-appdocker run -it --rm --net=host \ -e UID=`id -u` \ -e GID=`id -g` \ -e UNAME=$USER \ -v `pwd`:/ansible \ -w /ansible \ -e ANSIBLE_LOG_PATH=/ansible/ansible.log \ docker.lightbitslabs.com/lightos-3-(Minor Ver)-(Rev)-rhl-(8/9)/lb-ansible:v9.13.0 \ sh -c 'ansible all -i ansible/inventories/cluster_example/hosts -m command -a id -b'- The last test will use the ansible_become_user from the hosts file, which is usually root. This will ideally test connecting to each machine via ansible_ssh_user and ansible_ssh_pass, and raise the privilege to the ansible_become_user using the sudo password - which is configured via the ansible_become_pass.
- If key-based authentication is used instead and you get a connectivity error, make sure that it is properly configured.
##