Hello Michael,
thanks for your answer. I now tried to reproduce the bug with a tiny
project. I now read that in 1.8 the modules are not part of ansible
anymore, so I checked out the core and extras seperately.
What I have done (this is on Mac OS X 10.10.1):
--- snip ---
#
Hi John,
There are homebrew and macport modules in extra.
As far as I know [Nix](https://nixos.org/nix/) package manager runs on
Mac OS X as well but there is no module for Nix in ansible yet.
-- Best, Igor
On Tue, Nov 25, 2014 at 3:54 AM, John Oliver jno...@gmail.com wrote:
Is there any kind
Server: Linux Mint 17
Remote host: Ubuntu Server 14.04 LTS
--
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
Hi Evgeny,
You've missed `sudo: yes` in a first task
`sudo: yes` is mandatory `sudo_user` doesn't enable 'sudoing'
-- Best, Igor
On Tue, Nov 25, 2014 at 1:13 PM, Volkov Evgeny eovol...@gmail.com wrote:
Server: Linux Mint 17
Remote host: Ubuntu Server 14.04 LTS
--
You received this
Ok thanks for the info Michael
On Monday, 24 November 2014 22:31:32 UTC, Michael DeHaan wrote:
EPEL testing picks things up really quick as @nirik is super quick on
those things.
It takes a while dependent on package karma to hit EPEL-EPEL.
On Mon, Nov 24, 2014 at 1:14 PM, James Morgan
Bug filed: https://github.com/ansible/ansible/issues/9618 :-)
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Mon, Nov 24, 2014 at 11:36 PM, Michael DeHaan mich...@ansible.com
Thanx !!
On Monday, November 24, 2014 3:52:09 PM UTC+1, Brian Coca wrote:
why not just use host_vars?
they will always be 'included', so q1 and q2 become mute.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
Ansible Project group.
To
Hola,
I have a playbook with multiple roles mapped to multiple vms. I'm registering a
variable in the output of one of the tasks in role A and need to pass it to
role B. Calling register or set_facts in the role A tasks file works as
expected within role A, but this var doesn't seem to make it
Hi Igor. I didn't mean to retrieve packages, but to install them. If I
have an RPM file, I can 'yum: name=/path/to/file.rpm state=present' I'd
like to do the same thing with an Apple .pkg file... 'pkg:
name=/path/to/file.pkg state=present' and have that file actually
installed. I see
- name: Check if postgres is already allowed via IPv4
shell: grep '^-A\ INPUT\ -s\ {{roundcube_host}}\ -p\ tcp\ -m\ state\
--state\ NEW\ -m\ tcp\ --dport\ 5432\ -j\ ACCEPT' /etc/sysconfig/iptables
/dev/null 21
ignore_errors: true
register: result
- name: Allow incoming IPv4 PostGreSQL
http://docs.ansible.com/route53_module.html doesn't mention being a way to
list all the records in a zone;
http://docs.aws.amazon.com/Route53/latest/APIReference/API_ListResourceRecordSets.html
talks about an API call to do it. Does Ansible support this in a way other
than what's on that
Hello all,
Was just curious how to accomplish this. Right now I am launching all
instances at once, so I am maximizing my chances to have all the EC2s as
close as possible. As AWS and common sense advises, it's desirable to have
it like so, any subsequent EC2 launch targeting the same
Np, Matt,
Ok. That makes sense.
Thanks,
-T
On Mon, Nov 24, 2014 at 2:05 PM, Matt Davis nitzmah...@gmail.com wrote:
Sorry for going dark on this thread- I had my notification settings for
both GG and Github pointing at a dead work email.
I'm sure ping wouldn't work on a private host out of
Greetings,
I'm very new to ansible and I created this simple playbook to install new
relic, however I'm trying to see if there's a way for the first task to see
if the RPM is present. New Relic's documenation has me installing the repo
with the following command: rpm -Uvh
Occasionally, I get SSH timeouts or other network errors in the middle of a
play. These cause that task to fail, but not the whole playbook, which
continues on, but without the node that failed. You see output something
like this:
...
2014-11-24 23:54:08,717 p=21193 u=ubuntu | TASK: [common |
Hello,
I am trying to create a dynamic inventory module that returns hosts like
this:
## hosts
[applicationservers:children]
dev1_appserver
dev2_appserver
[dev1_appserver]
host1
[dev2_appserver]
host1
[dev1_appserver:vars]
appserver_name=dev1
appserver_home=somepath/dev1/...
I wanted to accomplish something like this. I wanted to use the ansible
facts like ansible_eth0.ipv4.address to check if this fact is defined.
- name: Check if eth0 interface setup
fail: msg=eth0 interface not setup
when: ansible_eth0.ipv4.address is not defined
But ansible is
Dear All,
Is there a way to keep replaying the playbook until there are no hosts
remaining in site.retry file?
Regards,
--
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
Dear all,
is there any way of replaying the playbook until there are no hosts in
myPlaybook.retry file?
regards,
--
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
Hi,
Started discussing this on Twitter with a.o. @laserllama. I'm facing a nice
(*) challenge:
- As a regular user (no special sudo / root privileges),
- I need to run Ansible from source
- on a Linux which has /usr/bin/python == Python 2.6.8
- with F-Secure SSH instead of OpenSSH
*) For small
I'm in a Windows IIS shop that is trying to convert from using a using a VM
master image that is continually updated to a bare OS install starting
point. There is a lot of manual playbooking and simple scripting
currently. We are implementing a more robust system for configuration
Is there a way to have a group_vars file for a group of groups? For
example, I have
[qa-webservers]
[qa-dbservers]
[qa:children]
qa-webservers
qa-dbservers
[qa:vars]
some_var=asdf
other_var=fdsa
I'd like to put the QA variables in group_vars/qa.yml, but that doesn't
seem to be working. Is
I want to update INI configuration files.
Today, I store my informations in a var file (in group_vars) this way :
# Identity configuration information
identity_servers_conf:
DEFAULT:
admin_token: {{identity_admin_token}}
verbose: True
database:
connection: mysql://{{
First, that's a really old version of ansible, and you need to upgrade.
Second, the when clause uses jinja syntax and it's complaining that
it can't evaluate your syntax: it's a syntax error, not a fact error.
In jinja, the not needs to come before the expression it's negating.
Try something like
On Tue, Nov 25, 2014 at 4:11 PM, Ed Voncken e...@edvoncken.net wrote:
Hi,
Started discussing this on Twitter with a.o. @laserllama. I'm facing a nice
(*) challenge:
- As a regular user (no special sudo / root privileges),
- I need to run Ansible from source
- on a Linux which has
The only way I've seen to control the parallelism of a task is with the
--fork flag. Is there any way to control this at the task level?
# First three tasks can occur fully concurrently
- task 1
- task 2
- task 3
# Then I want to perform this block one host at a time to perform a rolling
The closest I've come to this has been by using wait_for, but I'm not sure
what the guarantees are here:
- local_action wait_for: path=/tmp/ansible.lock state=absent
// touch /tmp/ansible.lock
// perform task4/5
// delete /tmp/ansible.lock
If I run with --fork=5, isn't it possible that more
check this setting, I believe it will allow you to do what you want
http://docs.ansible.com/playbooks_delegation.html#maximum-failure-percentage
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
Ansible Project group.
To unsubscribe from this group and
Matt Hughes wrote:
The only way I've seen to control the parallelism of a task is with the
--fork flag. Is there any way to control this at the task level?
Split your tasks into separate plays for the parallelisable, and single
host sections.
On the single host section add a serial: 1 to
dynamic inventory modules are supposed to return json, not ini
this has examples:
http://docs.ansible.com/developing_inventory.html
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
Ansible Project group.
To unsubscribe from this group and stop
That the group is just hosts or has other groups, should not matter at
all, this should work.
what version of ansible, python, OS? dir structure, etc?
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
Ansible Project group.
To unsubscribe from this
Hi all,
We have released Ansible 1.8.0, which adds some exciting new features and
modules, as well as many enhancements to cloud modules and other various
bug fixes:
* Fact caching support, pluggable, initially supports Redis (DOCS pending)
* The new omit value can be used to leave off a
yum: can take a URL, or alternatively you can download the file
(preferably using get_url which is easy to make idempotent)
and then pass yum: the downloaded path to the RPM.
Cheers
Dick
On 25 November 2014 at 00:37, Ovidio B. ovidioborr...@gmail.com wrote:
Greetings,
I'm very new to ansible
For those looking for fact-caching docs BTW:
http://docs.ansible.com/playbooks_variables.html#id34
Hastily produced blog post:
http://www.ansible.com/blog
:)
On Tue, Nov 25, 2014 at 5:56 PM, James Cammarata jcammar...@ansible.com
wrote:
Hi all,
We have released Ansible 1.8.0, which
Cool! I've got a couple of questions:
On Tuesday, November 25, 2014 5:56:21 PM UTC-5, James Cammarata wrote:
For developers writing modules:
* The 'baby JSON' support in module responses, originally intended for
writing modules in bash, is removed as a feature to simplify logic, script
The question in (A) means that modules must emit json, and key=value pairs
one per line are not acceptable module stdout any longer.
The capability of modules to not take JSON for non-Python modules still is
around, ergo the WANT_JSON thing is still there. However, I can see this
eventually
Hello,
I am trying to make a playbook with the following inventory work:
## hosts
[applicationservers:children]
dev1_appserver
dev2_appserver
[dev1_appserver]
host1
[dev2_appserver]
host1
[dev1_appserver:vars]
appserver_name=dev1
appserver_home=somepath/dev1/...
appserver_port=9090
Sorry, my question was not clear. I created a new topic.
This one can be deleted.
Am Dienstag, 25. November 2014 22:31:39 UTC+1 schrieb Brian Coca:
dynamic inventory modules are supposed to return json, not ini
this has examples:
http://docs.ansible.com/developing_inventory.html
--
Hi all,
As some of you might already know, there will be a cfgmgmtcamp
organized in 2015.
The CFP is online and people who would like to speak can submit their talk.
more info on the website : http://cfgmgmtcamp.eu/
Grtz,
Vincent.
--
You received this message because you are subscribed to the
39 matches
Mail list logo