X-Git-Url: https://gerrit.fd.io/r/gitweb?a=blobdiff_plain;f=resources%2Ftools%2Ftestbed-setup%2FREADME.rst;h=01be10b5d3ba80308bc670588da6546c20aea3fe;hb=0ca4a9ec1a8fc53a679b1c635a6e1b6afae0299d;hp=738dffad4916769c6b51a0a0b797c0010e924c30;hpb=53153e114017d193cdf9b88f21f4eac31bad72b7;p=csit.git

diff --git a/resources/tools/testbed-setup/README.rst b/resources/tools/testbed-setup/README.rst
index 738dffad49..01be10b5d3 100644
--- a/resources/tools/testbed-setup/README.rst
+++ b/resources/tools/testbed-setup/README.rst
@@ -98,12 +98,6 @@ Set CIMC/IPMI address, username, password and hostname an BIOS.
 Bootstrap the host
 ``````````````````
 
-Convenient way to re-stage host via script:
-
-.. code-block:: bash
-
-   sudo ./bootstrap_setup_testbed.sh <linux_ip> <mgmt_ip> <username> <pass>
-
 Optional: CIMC - From PXE boostrap server
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -173,8 +167,6 @@ Prerequisities for running Ansible
   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).
@@ -187,7 +179,8 @@ Ansible structure
 .................
 
 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
@@ -228,12 +221,23 @@ Ansible structure is described below:
    ├── 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::