That did the trick!
Here's my configuration now, for completeness:
vars:
splunkforwarder_log_items:
- app1_name: var_log
source: /var/log
recursive: true
index: testindex
splunkforwarder_log_files:
- logfile: messages
app_name: var_log
sourcetype: linux_messages_syslog
Hello,
Hope you had a good holiday :) My holiday starts this Friday luckily.
These are the versions we use:
Red Hat Enterprise Virtualization Manager Version: 3.4.1-0.31.el6ev
ansible: 1.6.6
module: ovirt
author: Vincent Van der Kussen
short_description: oVirt/RHEV platform management
Also, what is the intended mechanism for pinning versions in dependencies in
meta/main.yml?
dependencies:
- git+http://git.example.com/repos/role-abc,v1.0
There's probably some work to trim the .git off the role_name too (I just don't
bother putting the .git in the repo url but maybe not all
Hi,
We have a requirement to pass for example, *-o RemoteForward 8080
host.behind.the.firewall.com:80* to some hosts so that the host can
reverse tunnel to some private resources on our local network. For example
we use a private git repo that is not publicly accessible, yet we need to
use it
Hi,
Apart from the fact that *set_fact* is a task on its own and *register*
captures the result of a task, is there any difference between the
resulting variables' scope or lifecycle (or anything else) for example.
Thanks,
Steve
--
You received this message because you are subscribed to the
I've solved the trimming the .git off the end and also the ability to specify
role_version in meta/main.yml
It doesn't work with an upgrade of a dependency because the check is currently
for if the role exists, not if it's a particular version.
I've added an integration test for all of this
Fundamentally they do the same thing, though register applies to task
results.
They enter into the same per-inventory-host scope.
On Thu, Aug 14, 2014 at 5:55 AM, Steven Ringo goo...@stevenringo.com
wrote:
Hi,
Apart from the fact that *set_fact* is a task on its own and *register*
Ansible views Vagrant as no different than any other computer.
I believe it should set ansible_ssh_port in inventory.
If you can paste what kind of errors you are seeing and your ansible
version it might be more clear what you're talking about, but I don't
understand get hit by the special
Hello,
Again, a very BIG thank you for your efforts on the deploy module.
I would like to share my suggestion, perhaps as an idea to generate a
future pull request:
With capistrano, it is possible to run some of the tasks only on specific
hosts. Any plans for such a feature?
Problem is that in
You are right about the intersection of groups - it's a shame you cannot
declare hosts like (excuse any syntax issues - code looks funny on a
phone):
Can you elaborate on what you think is missing? :children to define
child groups is how that part works, so I'm missing the understanding of
what
Mixing groups between dynamic and static works in Ansible 1.7 and higher,
so if you are not running that version, I'd upgrade.
To re-use this same method with static host inventories, the only way I
can see is to put each inventory file in a separate directory along with a
copy of rollup groups.
Is this something that should be fixed or
just documented as a difference?
Nope. It's fine, because the system has no hint to decide you asked for
anything other than a string.
On Wed, Aug 13, 2014 at 1:43 PM, Michael Peters michael00pet...@gmail.com
wrote:
Also, isn't it weird the with
It's not possible to use inventory variables in the host spec (-
hosts:).
Also, don't use debug with register, instead, if you need to set a variable:
- set_fact:
foo: tag_Name_{{ aws.ec2.Name }}
- hosts: {{ hostvars.localhost.aws_host_target.msg
This is also an error because the
Clarification: they are used for the -c ssh connection type.
This is the default on all platforms except RHEL/CentOS 6 and earlier,
which have an old SSH, and can't benefit from the (very useful)
ControlPersist speedups.
You could still manually pick this in your ansible.cfg, though I'd
The Zabbix installation manual recommends some settings in
/etc/php5/apache2/php.ini:
post_max_size = 16M
max_execution_time = 300
max_input_time = 300
date.timezone = UTC
Other PHP applications have different recommendations. Here are a few
recommended values for post_max_size, for example:
Can you please upgrade to the latest version of Ansible and try from there?
This is version 1.7.
What remote OS are you managing?
Can you run with -c ssh - and see if you get any particular messages
from SSH debugging?
On Thu, Aug 14, 2014 at 1:31 AM, fscomm fis...@gmail.com wrote:
would just add one more requirement - being able to overwrite the
role-name and rely on the git repo name exclusively. Idea for syntax if you
want to keep the *role_name/url, role_version* format:
While interesting, we don't want to do this because we already have
,version used for describing
I think this is the problem in the module:
env = dict(type='list'),
If it were type='dict' we could do:
docker:
env:
options: {foo:bar,baz:qux}
other_arguments_here: 1234
And basically use full YAML, without any splitting magic.
If someone would like to help test that
In your case, I recommend setting feature bits for things, or keying of the
group in a template.
{% if inventory_hostname in groups['webservers'] %}
{% else %}
{% endif %}
etc
{% if needs_more_power|defined %}
{% endif %}
etc
On Wed, Aug 13, 2014 at 11:50 PM, Joel Shprentz
That's right. But I was referring to another thing.
Basically, I'm trying to use their deployment role as a whole, to perform
certain operations only on certain hosts, while leaving all the
hosts/groups, listed in the the main 'hosts' directive.
In my other roles, I've been using host_vars or
On 14 August 2014 05:50, Joel Shprentz jshpre...@his.com wrote:
Has anyone else encountered this problem? Have you found an approach for
tracking a maximum (or minimum, etc.) value across multiple roles and using
the maximum in a task?
Instead of looking to Ansible to work around this
Basically, I'm trying to use their deployment role as a whole, to perform
certain operations only on certain hosts, while leaving all the
hosts/groups, listed in the the main 'hosts' directive.
This is there too :)
ansible-playbook foo.yml --limit groupname
ansible-playbook foo.yml --limit
Yes, I realize the difference between a string and a boolean. But I've
never seen a system where foo and not foo evaluate to the same
thing.
On Thu, Aug 14, 2014 at 7:47 AM, Michael DeHaan mich...@ansible.com wrote:
Also, isn't it weird the with the variable foo set to string false
both when:
both when: foo and when: not foo evaluate to false?
Don't recall it ever working that way.
Can you share a playbook that reproduces this?
On Thu, Aug 14, 2014 at 9:08 AM, Michael Peters michael00pet...@gmail.com
wrote:
Yes, I realize the difference between a string and a boolean. But I've
Sure: test.yml
---
- hosts: 127.0.0.1
connection: local
tasks:
- set_fact: foo=false
- command: ls /
when: foo
- command: ls /
when: not foo
Executed like ansible-playbook -i '127.0.0.1,' test.yml
Results in both tasks being skipped:
PLAY [127.0.0.1]
On Thu, Aug 14, 2014 at 7:42 AM, Michael DeHaan mich...@ansible.com wrote:
You are right about the intersection of groups - it's a shame you cannot
declare hosts like (excuse any syntax issues - code looks funny on a
phone):
Can you elaborate on what you think is missing? :children to
I think I get where you are going with the idea of different plays, but
they way I understand it, I would need a different play for every user that
had different host/group requirements.
So, with 100+ users, 70 might need the same access for a given set of hosts
(1 play), but there could be 30
I can think a few cases where being able to control local role folder names
would make things cleaner. For example: referencing repos with the same
name in the end, too long or obscure repo names, etc.
None of this is a blocker that would stop us from using this feature. I am
looking forward to
I can create a new a group as a union of other groups (groups of groups),
but AFAIK there's no way to create a new group as the intersection of other
groups.
Shouldn't be needed in the inventory file, as this is something you can
address using the host spec:
- hosts: alpha:beta
or also
-
Can I execute an action when variable1=x OR variable2=y?
--
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
Thanks! - that clarifies it for me.
On Thursday, 14 August 2014 04:52:39 UTC-7, Michael DeHaan wrote:
It's not possible to use inventory variables in the host spec (-
hosts:).
Also, don't use debug with register, instead, if you need to set a
variable:
- set_fact:
foo:
Submitted bug: https://github.com/ansible/ansible/issues/8629
Thanks
On Thu, Aug 14, 2014 at 1:24 PM, Michael DeHaan mich...@ansible.com wrote:
The inconsistent booleanification is definitely not something I'd want to
see here.
Can you please file a bug on github for this one?
On Thu,
Hi,
I want to manage the license file (the license key of proprietary software)
within Ansible for each host.
There is few resource on the web on this subject or maybe I use the wrong
vocabulary.
So can someone tell me if there is a better ansible way to handle this case.
Here is what is
Hi all!
We have released 1.7.1, which addresses one security issue reported by
Tomasz Kontusz, as well as some other bugs.
- A security fix to disallow specifying 'args:' as a string, which could
allow the insertion of extra module parameters through variables.
- Performance
Perhaps I am doing it wrongly (thus the idiomatic keyword), but I find that
less declarative then being able to define intersections in groups.
On Friday, August 15, 2014 3:25:35 AM UTC+10, Michael DeHaan wrote:
I can create a new a group as a union of other groups (groups of
groups), but
I have an inventory file like this:
[webservers]
10.0.0.1
10.0.0.2
10.0.0.3
[postgresservers]
10.0.0.4
And I'm trying to run this playbook against my Postgres host:
---
- name: Allow eth1 port 5432 access to Web servers
ufw: rule=allow interface=eth1 direction=in port=5432 proto=tcp src={{
Yes.
Apologies for the weird archive link instead of the forum, but this is what
Google juice turned up when I was looking for my post.
https://www.mail-archive.com/ansible-project@googlegroups.com/msg07964.html
On Thu, Aug 14, 2014 at 12:26 PM, Thijs Cadier th...@appsignal.com wrote:
Any
37 matches
Mail list logo
