Hello,
1) SLOWDOWN
I just installed ansible-2.0.0-0.4.beta2-1.tar.gz and reran a playbook
against a local Vagrant instance which configures an Apache with
mod_proxy for ca. 60 hosts.
1.9.4:
- PLAY RECAP ********************************************************************
myhost : ok=85 changed=4 unreachable=0 failed=0
real 0m28.980s
user 0m4.650s
sys 0m2.883s
2.0.0
PLAY RECAP *********************************************************************
myhost : ok=94 changed=2 unreachable=0 failed=0
real 1m34.762s
user 1m5.606s
sys 0m6.789s
Besides of the realtime you see an enormous increase in user time as well.
2) File differences due to line ends
As you see with 1.9.4 4 files changed when switching back from 2.0 to
1.9.4. This is due to missing empty lines at the end of templates with
2.0
3) Files showing always as changed with 2.0:
- name: Create Cron-Jobs for foo on reboot
cron:
name: "foo-runs-reboot"
cron_file: "foo-runs-reboot"
job: "{{foo_command}}"
special_time: "reboot"
user: root
state: present
- name: Create Cron-Jobs for foo every hour
cron:
name: "foo-runs-hourly"
cron_file: "foo-runs-hourly"
job: "{{foo_command}}"
minute: "{{inventory_hostname|constant_sharding(60)}}"
user: root
state: present
These two commands are always shown as changed (constant_sharding is a
filter like Puppet's fqdn_rand) with 2.0 I could not see any changes
in sha1sum between different invocations.
Regards Mirko