Ansible
This section demonstrates a few Ansible operations with Ubuntu servers in a VMware ESXi environment.
Infrastructure and user accounts
| Node | Type | Role | User | Password | |
|---|---|---|---|---|---|
| uvm0 | virtual machine | Ubuntu 24 LTS | control node | aadmin | apass00 |
| esxihost | physical server | WMwae ESXi 6.5 | managed node | esxiadmin | passESXi |
| uvm26 | virtual machine | Ubuntu 24 LTS | managed node | aadmin | apass26 |
| uvm27 | virtual machine | Ubuntu 24 LTS | managed node | aadmin | apass27 |
From the point of view of Ansible, the nodes in this documentation were either a physical server or virtual machines.
An automation administrator performed these operations with the help of user accounts called aadmin. These accounts did not have to have the same names. Moreover, they needed elevated privileges only on the managed nodes.
Although uvm0 resided on esxihost, it could manage it via Ansible.
This documentation demonstrates the use of Ansible playbooks. It does not address Ansible roles.
Networking
The aadmin@uvm0 was able to ping any of the managed nodes. In this particular case, all nodes belonged to the same local area network.