machines that will be provisioned (does not need to be PXE server).
- User `testuser` with password `Csit1234` is created with home folder
initialized on all target machines that will be provisioned.
-- SSH keys for no pass access are copied to all target machines that will be
- provisioned: `ssh-copy-id x.x.x.x`.
- Inventory directory is created with same or similar content as
`inventories/lf_inventory` in `inventories/` directory (`sample_inventory`
can be used).
.................
Ansible is defining roles `TG` (Traffic Generator), `SUT` (System Under Test),
-`VPP_DEVICE` (vpp_device host for functional testing).
+`VPP_DEVICE` (vpp_device host for functional testing). `COMMON` (Applicable
+for all servers in inventory).
Each Host has corresponding Ansible role mapped and is applied only if Host
with that role is present in inventory file. As a part of optimization the role
├── vault.yml # Ansible vualt storage.
└── vpp_device.yaml # vpp_device playbook.
+Tagging
+.......
+
+Every task, handler, role, playbook is tagged with self-explanatory tags that
+could be used to limit which objects are applied to target systems.
+
+You can see which tags are applied to tasks, roles, and static imports by
+running `ansible-playbook` with the `--list-tasks` option. You can display all
+tags applied to the tasks with the `--list-tags` option.
+
Running Ansible
...............
#. Go to ansible directory: `cd csit/resources/tools/testbed-setup/ansible`
#. Run ansible on selected hosts:
- `ansible-playbook --vault-id vault_pass --extra-vars '@vault.yml' --inventory <inventory_file> site.yaml --limit x.x.x.x`
+ `ansible-playbook --vault-password-file=vault_pass --extra-vars '@vault.yml'
+ --inventory <inventory_file> site.yaml --limit x.x.x.x`
.. note::