Many thanks for this tip.
It's clever
On Wednesday, June 11, 2014 at 10:32:23 PM UTC+7, andreub wrote:
>
> Hi Jaime,
>
> I had the exact same problem. ec2_group modules recreates the rules every
> time you use the it, so if you're running it in a loop, it will create the
> group the rule for the
Correction of typo...
==
> Question:
> Need some advice on how to do in ansible.
>
> We are fetching the archive from artifactory url and calling a script to
> deploy the application.
> The archive would be different for different release and we need to
> replace the value into the property f
Question:
Need some advice on how to do in ansible.
We are fetching the archive from artifactory url and calling a script to
deploy the application.
The archive would be different for different release and we need to replace
the value into the property file before executing the script.
In simple
Hi,
I am currently working on using dynamic inventory for configuring ec2
instances on AWS environment. I would appreciate if someone can give an
example of how ec2.py can be used inside a playbook to provide dynamic
inventory information to other plays in the same playbook or to other
playbook
That fixed it... Thank you :)
On Thursday, 26 February 2015 08:06:55 UTC-8, Rahul Mehrotra wrote:
>
> I am working on creating an AWS infrastructure based on Ansible.
> I have a playbook which creates an RDS instance. When I run the playbook
> standalone it executes perfectly & creates RDS insta
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 have a PowerPoint with Ansible bas
Unless there's some other problem in the mix, this is enough to work:
local_action: wait_for state=started host="{{ inventory_hostname }}" port=22
On Thursday, 26 February 2015 12:41:31 UTC+1, Yariv Graf wrote:
>
> Hi,
> Try:
>
> - name: wait for SSH
> local_action: wait_for port=22 host="
Try this instead:
vpc_security_groups: "{{ sg_mysql.group_id }}"
On Thursday, 26 February 2015 17:40:41 UTC+1, Rahul Mehrotra wrote:
>
> I am not able to figure out which specific vars is bad...
> Is there a problem of file locking ???
> Because there is a sg_mysql.yml file being called before
I am also facing the same issue while creating security group on aws, using
Ansible 1.8.3 version and 1.6, not really sure but this is something wrong at
aws api library ?
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe fr
I am not able to figure out which specific vars is bad...
Is there a problem of file locking ???
Because there is a sg_mysql.yml file being called before rds.yml in main.yml
Something like
- include: sg_mysql.yml
- include: rds.yml
sg_mysql.yml is writing the security group id to be used by rds.
the error seems to indicate bad data is being passed to the rds module
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsub
it should be:
- include: rds.yml
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsubscr...@googlegroups.com.
To post to
The main playbook has it as
- include: rds.yml
On Feb 26, 2015 8:13 AM, "Brian Coca" wrote:
> it should be:
>
> - include: rds.yml
>
>
>
>
> --
> Brian Coca
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Ansible Project" group.
> To unsubscribe fr
I am working on creating an AWS infrastructure based on Ansible.
I have a playbook which creates an RDS instance. When I run the playbook
standalone it executes perfectly & creates RDS instance. However when that
playbook is called by another playbook using the
>
include: rds.yml
It gives t
Hi,
This E-mail is a little bit old but I am in the same situation.
ignore_errors: test_err | bool
doesn't work for me on ansible 1.8.4
Is there any work around?
Thank you,
WAKAYAMA Shirou
2014-10-08 1:58 GMT+09:00 Yasir Saleem :
> I tried few combinations:
>
> #
> - hosts: jump
>
We recently had a user question in regards to this thread, and wanted to
add a quick update as I see we never followed up on this here on the
group/mailing list.
These concerns were addressed as part of this commit:
commit 0d6f6ad282fd0d3fb581da9dcbafd33521eb67be
Author: James Tanner <>
Date:
On 26 February 2015 at 13:08, Florent B wrote:
> How can I do ?
>
Don't define complex vars in the ini hosts file, use group/host_vars file
or playbook vars for that.
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from t
Just to compare execution and inventory arragment:
I'm trying to get the same result based on tags (run task on limited
hosts-set from current hosts-group)
W dniu czwartek, 26 lutego 2015 13:05:35 UTC+1 użytkownik sirkubax napisał:
>
> Up to now I think the best would be generate "temporary" hos
Up to now I think the best would be generate "temporary" host list
(group_by).
You may intersect them later with other groups
However I do not like the idea of defining "hosts: " more than once in
a playbook.
I did post the idea first in the topic:
How to list all currently targeted hosts
Hi,
Try:
- name: wait for SSH
local_action: wait_for port=22 host="{{ inventory_hostname }}"
search_regex=OpenSSH delay=30
sudo: false
It will start to search for the regex after 30 secs.
On Thursday, February 26, 2015 at 10:32:46 AM UTC+2, hce h wrote:
>
> Hi,
>
> I have following wai
So you're saying that after running that the IGW is not associated with
your subnet(s)?
Also, can you confirm that the routing tables have the correct subnets
associations?
On Tuesday, 24 February 2015 21:37:04 UTC+1, Pablo Escobar wrote:
>
> Hi,
>
> I have been doing some tests to deploy a ec2
Sorry, the version is 1.9.
On Thursday, February 26, 2015 at 7:32:46 PM UTC+11, hce h wrote:
>
> Hi,
>
> I have following wait_for statement after reboot the host, but it stuck in
> the wait until the timeout even the host can be accessed manually when I
> run ssh the host. Is it a bug or what
Hi,
I have following wait_for statement after reboot the host, but it stuck in
the wait until the timeout even the host can be accessed manually when I
run ssh the host. Is it a bug or what I could be missing?
- name: Wait for restart
local_action: wait_for host="{{ inventory_hostname }}" por
23 matches
Mail list logo