ansible-playbook

Is there an option to format ansible output with the use of ansible (not any other scripts)? For instance name: Show version sudo: true hosts: web_front_end tasks: - name: Create yum cache shell: yum makecache - name: Check the version of Portal shell: rpm -qa | grep portal register: portal - debug: msg={{portal.stdout}} tags: - portal - wfe I would like to get only the TASK: [debug msg={{portal.stdout}}] part. Or even is there a way to get only the shell command output? I have a plugin to format the output. The gist is here but the gist's gist is: # Save as <folder with your playbook>

I am attempting to use Ansible 1.9.0.1 to configure Windows servers using a domain user name. I have successfully setup the Linux Ansible control box and have been able to use basic auth to run ansible/ansible-playbook plays. However running with a domain user fails. Kerberos is enabled on the Windows nodes: winrm get winrm/config/client/auth Auth Basic = true Digest = true Kerberos = true Negotiate = true Certificate = true CredSSP = true The playbook I am trying to run just references the win_ping module of ansible and the following is the output: PLAY [Manage SMI] **************************

I'm using ansible to deploy several sites to the same server. Each site is a separate 'host' in the ansible hosts inventory, which works really well. However, there are only two databases: production and testing. How can I make sure my database-migration task only runs once per database? I've read into the group_by , run_once and delegate_to features, but I'm not sure how to combine those. The hosts look something like: [production] site1.example.com ansible_ssh_host=webserver.example.com site2.example.com ansible_ssh_host=webserver.example.com [beta] beta-site1.example.com ansible_ssh_host

I have a playbook that prepare 3 different Vagrants in my machine, so I have create a role that create this Vagrant. I don't find the correct syntax. It looks like roles is not a module , so I don't have all options, only tutorials. playbook file : - hosts: localhost connection: local roles : - role: vagrant with_items: - {index: 1, ip: 192.168.222.1, name: mongo1, user: nicorama } - {index: 2, ip: 192.168.222.2, name: mongo2, user: nicorama } - {index: 3, ip: 192.168.222.3, name: mongo3, user: nicorama } And the tasks in the vagrant role - file: path=/linux/{{item.name}} state=directory owner

I would like to shape my directory structure of my ansible roles and playbooks. Currently I have a directory structure like. group_vars * all * group-one - group-vars.yml - group-vault.yml ... host_vars - server1.yml plays - java_plays * deploy_fun_java_stuff.yml * deploy_playbook.yml roles - role1 - tasks * main.yml - handlers - (the rest of the needed directories) - role2 - java - java_role1 - tasks * main.yml - handlers - (the rest of the needed directories) I would like to be able to call upon the role java_role1 in the play deploy_fun_java_stuff.yml I can call --- - name: deploy fun java

I observed that roles downloaded from galaxy get installed inside the roles/ directory, where we already have our in-house ones, making quite hard to distiguish between external ones and internal ones. Is there a way to keep them in separated directories, so we can avoid confusions? In most cases I would expect to have a script that is updating the galaxy ones and that we would not modify them internally. I think there is no standard way of doing this but you can use Ansibles behavior to your advantage. Ansible searches in two locations for roles: In the roles directory relative to your