Michael DeHaan wrote:
Excellent, accelerated mode would have also been a good answer for 6.5 -
though I definitely prefer the native SSH transport when possible.
My Centos 6 control machine has an updated ssh client, built from the
Fedora ssh rpm (the server side has been left as is).
Howe
Excellent, accelerated mode would have also been a good answer for 6.5 -
though I definitely prefer the native SSH transport when possible.
Switch on pipelining if you haven't already, it should approximately double
in speed again (search for pipelining in ansible.cfg)
On Thu, Jul 31, 2014
CentOS 6.x doesnt support ControlPersist, so it will use paramiko.
I installed CentOS 7 to use as my Ansible deploy VM just for this
feature, speeds
things up on our 30 node / 50 role stack significantly.
On 28 July 2014 15:14, Michael DeHaan wrote:
> Since you are using CentOS as a control mach
Since you are using CentOS as a control machine you will want to select
paramiko as a transport or set the ssh arguments in ansible.cfg
I'm not sure how far Vagrant complicates this, as this isn't the Vagrant
list, but there are plenty of users here that could probably help answer
that question.
Hi,
I am using ansible to provision a vagrant box that's running with
virtualbox on a centos 6.5 host.
Apparently there is an issue with the config.ssh.forward_agent option.
I am a bit at loss to know if the issue is caused by vagrant or by ansible.
Every time I try to provision I get
fatal:
