Update README.md

ansible/tasks/README.md

@@ -4,27 +4,34 @@ Ansible[^1] involves a common set of concepts and tools for system automation. A
 
 [^1]: https://www.ansible.com/
 
+#<center>
+#<figure>
+#  <img src="https://gitlab.inria.fr/fmorlano/mitik_management/-/raw/main/Figures/ansible.png" alt="ansible_architecture"/>
+#  <figcaption>Figure 1. Ansible architecture.</figcaption>
+#</figure>
+#</center>
+
+The proposed topology is shown in Figure 1. One goal of using Ansible-based automation is to configure all sniffers simultaneously to guarantee that all nodes receive the same configuration, in addition to facilitating the manipulation of each device to be configured.
+
 <center>
 <figure>
-  <img src="https://gitlab.inria.fr/fmorlano/mitik_management/-/raw/main/Figures/ansible.png" alt="ansible_architecture"/>
-  <figcaption>Figure 1. Ansible architecture.</figcaption>
+  <img src="https://gitlab.inria.fr/fmorlano/mitik_management/-/raw/main/Figures/mitik_topology.png" width="70%" height="70%" alt="mitik_topology"/>
+  <figcaption>Figure 1. Topology of Mitik project.</figcaption>
 </figure>
 </center>
 
-The proposed topology is shown in Figure 2. One goal of using Ansible-based automation is to configure all sniffers simultaneously to guarantee that all nodes receive the same configuration, in addition to facilitating the manipulation of each device to be configured.
+The sniffers' deployment require two roles to be developed. The first environment has been created to perform the installation and configuration tasks required on the hardware and the O.S.; the second environment executes the tasks necessary to start the sniffer according to the required parameters, in addition to synchronizing the data with the sniffer manager (Mitik laptop) and the Mitik server. Figure 3 shows the scenario to be automated by the Ansible management tool.
 
 <center>
 <figure>
-  <img src="https://gitlab.inria.fr/fmorlano/mitik_management/-/raw/main/Figures/mitik_topology.png" width="50%" height="50%" alt="mitik_topology"/>
-  <figcaption>Figure 2. Topology of Mitik project.</figcaption>
+  <img src="https://gitlab.inria.fr/fmorlano/mitik_management/-/raw/main/Figures/ansible_implementation.png" width="70%" height="70%" alt="ansible_implementation"/>
+  <figcaption>Figure 3. Automating super-sniffers deployment.</figcaption>
 </figure>
 </center>
 
-The Sniffers' configuration requires two configuration environments to be developed. A single configuration environment has been created to perform the installation and configuration tasks required on the hardware and the OS. A second environment executes the tasks necessary to start the sniffer according to the required parameters, in addition to synchronizing the data with the sniffer manager and the mitik server.
-
-## **Phase 1. Hardware and OS requirements**
+## **Role 1. Hardware and software requirements**
 
-A modified version of Raspian has been provided by [1], as part of the experiments evaluating the performance of low-level libraries to capture network traffic in the sniffer. However, it is necessary to carry out additional configurations in the sniffer to add new functionalities in it.
+A modified version of Raspian has been provided by [1], as part of the experiments evaluating the performance of low-level libraries to capture network traffic in the sniffer. However, it is necessary to carry out additional configurations in the sniffer to add new functionalities on it.
 
 ## **Sniffer manager**
 
@@ -66,7 +73,7 @@ ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb",  KERNELS=="1-1.2",       NAM
 
 It is also defined a wireless network to connect each sniffer to the remote server through wlan0. These parameters are defined in _playbook_NIC_config_.
 
-## **Phase 2. Sniffer parameters**
+## **Role 2. Sniffer parameters**
 
 # ------------------todo-------------------
 
@@ -76,7 +83,7 @@ Tasks:
 
 - [x] UPLOAD FUNCTIONAL PLAYBOOKS OF THE FIRST TESTBED
 - [x] SPECIFY FEATURES OF EACH PLAYBOOK
-- [ ] ORGANIZE FEATURES IN PLAYBOOKS BY TASK TYPE
+- [x] ORGANIZE FEATURES IN PLAYBOOKS BY TASK TYPE
 - [ ] CREATE MAIN.YML TO EXECUTE ALL THE PLAYBOOKS
 
 ## **References**