anchor.diff:  
   2 - **Ansible Galaxy Web UI Search**. 
   
  -Go to https://galaxy.ansible.com/[the Ansible Galaxy web site] and start exploring or browsing for a role. Let's use the same example as before and just search for Jenkins. Click on "Browse Roles" and type "Jenkins" on keyword (or just https://galaxy.ansible.com/list#/roles?page=1&page_size=10&autocomplete=jenkins[click here]). You'll see a nice interface and a sort function that will make all the difference: `Stargazers`. That means we can filter by the most relevant and upvoted role by the community. Prefer to take that one with the most starts. For this example, the chosen role will be the https://galaxy.ansible.com/geerlingguy/jenkins/[geerlingguy one].
  +Go to https://galaxy.ansible.com/[the Ansible Galaxy web site] and start exploring or browsing for a role. Let's use the same example as before and just search for Jenkins. Click on "Browse Roles" and type "Jenkins" on keyword (or just https://galaxy.ansible.com/list#/roles?page=1&page_size=10&autocomplete=jenkins[click here]). You'll see a nice interface and a sort function that will make all the difference: `Stargazers`. That means we can filter by the most relevant and upvoted roles by the community. Prefer to take that one with the most starts. For this example, the chosen role will be the https://galaxy.ansible.com/geerlingguy/jenkins/[geerlingguy one].
   
   3 - **Google it**. 
   
  
positive.code: 
  You should see the Jenkins role installed on your system provided with the version and all the other dependencies it needs. Ansible Galaxy works like many others package managers over there: it downloads all other required dependencies so you can work with it without any worries. Remember the Ansible Role's path set on step #2? Try to list the directory and you'll see all the roles there too.
  
  Explore their work by looking for what the role really do. Start by exploring the `$ANSIBLE_ROLES_PATH/roles/geerlingguy.jenkins/tasks/main.yml`. Normally this is the starting point of the role and you really could see what's going on. Try to understand their code and how things are been doing there. It's a very nice exercise to learn by example and to absorb concepts harder to get on books or manuals.
  
  After that, be comfortable with their code and explore everything else, trying to understand how the pieces are working together to make the role that awesome.
  
  
negative.code: $ sudo chown -R myuser:myuser /etc/ansible/roles
  ```
  
  Then you should work on a virtual machine environment. For that you could use http://docs.ansible.com/ansible/latest/guide_vagrant.html[Vagrant on top of libvirt].
  
  And that's it! You should have your environment set up. For more detailed information about the installation and configuration of Ansible Galaxy, please http://docs.ansible.com/ansible/latest/galaxy.html[check the docs].
  
  
  === 3) Looking for roles that you need
  
  So now you have the plan for what you need to do and the Ansible Galaxy configured on your environment. Let's search for the roles that we need to **compose** our playbook so we can provision all the three servers at once.
  
  Remember that you just need to bring all these roles from the Galaxy repository and run them on a orchestrate fashion to do what you need.
  
  