We are going to verify that our nodes can communicate with each other, first via the ping command and then via SSH. Follow the steps given below to verify node connectivity in Jenkins:
- Connect to the master node using vagrant SSH master and ping both the IP addresses of node1 and node2 as follows:
The -c flag just specifies to send 4 packets to the nodes. The output shows that the nodes can communicate as there is 0% packet loss.
- Connect to the two nodes from our master using SSH. Run ssh [email protected] to connect to node1 as follows:
- Enter yes if a prompt asking you about the authenticity of the host is displayed and use vagrant as the password.
- Note that, as you type in the password, it will not be displayed.
When Vagrant provisions VMs, you do not want to specify any SSH settings. You can find out more at https://www.vagrantup.com/docs/vagrantfile/ssh_settings.html. This will create a user with the username vagrant and password vagrant by default. We will use this default user to access both our nodes since we did not specify any users in our Vagrantfile.
- Repeat this process to connect to node2. You can do this from either the master or node2. Note The connection will work as long as you provide the correct credentials, since all nodes are on the same network.
With that, you have successfully verified that the nodes can communicate with each other; thus, the next steps we will take in this chapter should work without any problems.