I am using ec2.py dynamic inventory for provisioning with ansible. I have
placed the ec2.py in /etc/ansible/hosts file and marked it executable. I
also have the ec2.ini file in /etc/ansible/hosts.
[ec2]
regions = us-west-2 regions_exclude = us-gov-west-1,cn-north-1
destination_variable = pub
On Thu, 26 Feb 2015, Tiglath wrote:
I have used Ansible for our data center migration and now it's time to tell
the whole department about it.
The problem is that I did not need to make very advanced use of Ansible to
automate the big move, and covering it will be rather short and boring.
I ha
Is it possible to set ANSIBLE_HOST_KEY_CHECKING on a per host or host group
basis? This would help prevent my known_hosts file from becoming cluttered
with test boxes but still ensure when I talk to production hosts I can
verify their identity.
--
You received this message because you are subs
+1 :-)
Think that this scenario will always be a problem for someone adding a user
to a new group, when belonging to that group is important to for the rest
of the playbook orchestration. A good approach could be forcing a reconnect
after using groups with append=yes in the "user" module.
Than
On Thu, Feb 26, 2015 at 3:31 PM, Tiglath wrote:
> I have used Ansible for our data center migration and now it's time to tell
> the whole department about it.
>
> The problem is that I did not need to make very advanced use of Ansible to
> automate the big move, and covering it will be rather shor
That's great, thanks for the info.
Main issues have been with ec2 spot instances and the delegate_to bug.
Will have a read.
Cheers!
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails fr
Should have finished reading your email. I don't know about the issues, if
you're lucky they'll be linked from commit messages or PRs.
On Fri Feb 27 2015 at 9:20:37 AM Michael Schultz
wrote:
> Yeah, I should have seen that coming. I only know this because I went
> through the same thing last wee
Yeah, I should have seen that coming. I only know this because I went
through the same thing last week.
Changes from 1.8.2 to 1.8.4 can be seen here
https://github.com/ansible/ansible/compare/release1.8.2...release1.8.4
But if you're like me, you care more about the modules themselves, so those
c
Ah, yes thanks for that, though still none the wiser :)
Many bug fixes, for both core code and core modules.
Is there an easy way in github to list the issues that make it into a
release. Can find the commits, but not the issues
Thanks
--
You received this message because you are subscribed
That's the devel changelog, you probably want the release1.8.4 changelog:
https://github.com/ansible/ansible/blob/release1.8.4/CHANGELOG.md
--michael
On Fri Feb 27 2015 at 8:27:44 AM James Morgan
wrote:
> Hi,
>
> Is there another changelog to
> https://github.com/ansible/ansible/blob/devel/CHAN
Hi,
Is there another changelog
to https://github.com/ansible/ansible/blob/devel/CHANGELOG.md or is it just
not up-to-date.
Really keen to see the fixes in 1.8.3 & 1.8.4
Thanks
J
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubsc
Hi
You can use lineinfile module
http://docs.ansible.com/lineinfile_module.html but if I were you I would
just download deployment file as ZZZ_EAR-latest.ear and in your config file
it will always be DEPLOYMENTFILE=/x/y/_EAR-latest.ear
Edgars
ceturtdiena, 2015. gada 26. februāris 23:24:06
Can you post the output when running with -?
On Friday, 27 February 2015 09:57:41 UTC+1, nobody wrote:
>
> sorry, it does not seem able to detect the host back after the reboot, any
> workaround or alternative module to wait reboot?
>
>
> On Friday, February 27, 2015 at 7:56:12 PM UTC+11, no
sorry, it does not seem able to detect the host back after the reboot, any
workaround or alternative module to wait reboot?
On Friday, February 27, 2015 at 7:56:12 PM UTC+11, nobody wrote:
>
> Thanks Yariv and Dan, but non of your suggestions work, the wait_for does
> seem able to detect the h
Thanks Yariv and Dan, but non of your suggestions work, the wait_for does
seem able to detect the host up after reboot. I reckon it is a bug. Anyway,
are there any workaround or alternative module to wait reboot?
On Thursday, February 26, 2015 at 7:32:46 PM UTC+11, hce h wrote:
>
> Hi,
>
> I ha
If you have to generate exactly one file, you can try creating a dynamic
inventory
Florent B napisał:
>Hi,
>
>I would like to write a complex variable (list) for each host in my
>inventory file.
>I know it's not a best practice, but I cannot write a vars file per
>host (constrained
>by project
16 matches
Mail list logo