On Saturday, April 18, 2015 at 4:05:41 PM UTC-5, Anand Buddhdev wrote:
>
> On Saturday, 18 April 2015 19:20:32 UTC+2, Serge van Ginderachter wrote:
>
> Hi Serge,
>
> No. There is nothing in the api that allows this without an update to
>> the core code.
>> It is though something to consider, whe
On 19 April 2015 at 16:54, Don Harper wrote:
Hi Don,
Hum...could you make use of git or svn, and just checkout host specific
> branches? Might lead to a bit a bloat on the server side, but would keep
> the client side cleaner.
>
We floated this idea early on in our design, and our entire team
I would use a dictionary where the keys are the hostnames. Then the task
would pull the variable it needs.
--
Michael Peters
On Apr 18, 2015 10:09 PM, "Maruti Kumar" wrote:
> Need to execute a tak on muntiple nodes in parallel. And each execution
> takes one value from a list of values as input.
Looks like 1.8.4 the problem is fixed.
cheers
On Tuesday, 13 January 2015 19:28:56 UTC+10, Tristan Bessoussa wrote:
>
> I got the exact same problem on 1.8.2.
>
>
>
> Le mercredi 17 décembre 2014 05:57:52 UTC+1, Steve Kieu a écrit :
>>
>> Hi,
>>
>> Not sure if this is known, with ansible 1.8.2 I
I used to define variables in the following way:
---
mysql:
config:
bind_address: 127.0.0.1
root:
password: ''
remote_access: absent
This style of writing is appealing to read and non repititive. Inside the
artifacts of the role I can reference such variables like {{
mysql.ro
I am in the process of converting a large system from Chef to Ansible, and
this is pretty much my only blocker. I've read dozens of posts/articles
where this problem is discussed.
So far the answer from Ansible (DaHaan really) has been "I like it this way
so tough it up" or "its too late to ch
