# How do I know pipelining is turned on? **URL:** \ **Category:** Ansible Project\ **Created:** [July 15, 2015, 8:50pm UTC](https://forum.ansible.com/t/how-do-i-know-pipelining-is-turned-on/18777 "2015-07-15T20:50:35Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Yuri\_Niyazov](https://avatars.discourse-cdn.com/v4/letter/y/e9bcb4/32.png) [@Yuri\_Niyazov](https://forum.ansible.com/u/Yuri_Niyazov)\ **Post date:** [July 15, 2015, 8:50pm UTC](https://forum.ansible.com/t/how-do-i-know-pipelining-is-turned-on/18777/1 "2015-07-15T20:50:35Z")
I am trying to provision a machine on EC2 (I am provisioning it to be a management node for a larger fleet of machines, this is why it has Vagrant and Ansible installed on it) [https://github.com/yn/provisioner](https://github.com/yn/provisioner) If I understand correctly, then the following line: ansible.raw\_arguments = [‘-e pipelining=True’] should reduce the number of operations that ansible performs. AFAICT the number of operations is the same with that line and without, and the output log between the two provisions looks identical, except for different temporary filenames and time-date differences. I double checked, and the machine that I am provisioning doesn’t have “requiretty” in the /etc/sudoers file. You can test it yourself, the AMI is public. Any help is appreciated! ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [July 15, 2015, 8:57pm UTC](https://forum.ansible.com/t/how-do-i-know-pipelining-is-turned-on/18777/2 "2015-07-15T20:57:46Z")
No idea what ansible.raw\_arguments = ['-e pipelining=True'] does, but setting pipeline to true in the ansible.cfg enables it ONLY for connection plugins that support it. This setting is not intended to have ansible execute less operations, just allows it to use a streaming pipe instead of having to scp/sftp everything over. ---
**Author:** ![Yuri\_Niyazov](https://avatars.discourse-cdn.com/v4/letter/y/e9bcb4/32.png) [@Yuri\_Niyazov](https://forum.ansible.com/u/Yuri_Niyazov)\ **Post date:** [July 15, 2015, 9:18pm UTC](https://forum.ansible.com/t/how-do-i-know-pipelining-is-turned-on/18777/3 "2015-07-15T21:18:00Z")
I created a github gist: [https://gist.github.com/yn/4efebad9d72835318ab1](https://gist.github.com/yn/4efebad9d72835318ab1) In it, you will see the results of executing two ansible-playbook commands: ansible-playbook --user=ubuntu --connection=ssh --limit=‘p2’ --inventory-file=/Users/yn/code/mine/provisioner/.vagrant/provisioners/ansible/inventory -vvvv -e pipelining=False playbook.yml and ansible-playbook --user=ubuntu --connection=ssh --limit=‘p2’ --inventory-file=/Users/yn/code/mine/provisioner/.vagrant/provisioners/ansible/inventory -vvvv -e pipelining=True playbook.yml If I understand the documentation correctly, the -e option allows one to override the configuration variables from ansible.cfg on the command line. The outputs look identical except for various IDs that are generated randomly. How does one know if ansible is using the streaming pipe or not? ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [July 15, 2015, 9:19pm UTC](https://forum.ansible.com/t/how-do-i-know-pipelining-is-turned-on/18777/4 "2015-07-15T21:19:17Z")
wrong, -e is 'extra vars', it does not override configurations, it overrides variable values, pipelining is not a variable value. ---
**Author:** ![Yuri\_Niyazov](https://avatars.discourse-cdn.com/v4/letter/y/e9bcb4/32.png) [@Yuri\_Niyazov](https://forum.ansible.com/u/Yuri_Niyazov)\ **Post date:** [July 15, 2015, 9:24pm UTC](https://forum.ansible.com/t/how-do-i-know-pipelining-is-turned-on/18777/5 "2015-07-15T21:24:16Z")
thanks!