So my original response was:
So this is completely and totally a real thing, because the handlers are
stored in a giant dictionary, by name.
We don't make that a failure because if two roles define "restart apache"
that shouldn't be a conflict someone has to resolve, nor should Apache
restart twi
So, untested ... but, possibly using the wait_for module to do the test and
ignoring errors, and then setting the inventory variable named
'ansible_ssh_port' using set_fact ?
I'm thinking maybe like:
- wait_for: port=22 # some amount of delay
register: port_test
failed_when: False
- set_fac
Totally fine with that.
Yeah FWIW, something like "riak-common" would be good for Galaxy, I think,
or even maybe "basho-common", but I'd avoid naming a role just "common" and
making a miscellaneous bucket. Just because people might not be clear
that username.common was really username-appcommon.
Hi,
I'm new to ansible, did a good amount of simple things with it in the last
couple of days, but I'm still trying to figure out the best way to do what
I need, I have looked at the examples, some are close to it, but not quite.
To simplify say I have N instances, and a number M of services of
I'd argue that having a common role would be the approach to take, with
follow-on roles having a dependency on the common role. For ease of
maintenance, that's the way to go. I don't think in-depth standards for
Galaxy roles has been discussed yet, at least not that I've heard (and not
on this to
I'd argue that having a common role would be the approach to take, with
follow-on roles having a dependency on the common role. For ease of
maintenance, that's the way to go. I don't think in-depth standards for
Galaxy roles has been discussed yet, at least not that I've heard (and not
on this to
This does not work...please test your code before posting.
--
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 po
I am still working on bootstrapping compute instances and exploring the
boundary between where a provisioning service (e.g. Vagrant) stops and
Ansible starts.
I prefer to run SSH on a non-standard port () instead of 22. I could
have Vagrant set up an instance with SSH running on port ,
Hello Ansible devs,
I seem to have hit a regression in Ansible 1.4.3. I have a very simple
ansible playbook with one role and a handler file that contains two
notification. The role calls notify against the name of the handlers (same
name for both) but only the first handler is called. In Ansib
It will be included in the tarball that is downloaded from github, but I
think the correct place to show at least some examples would be in the
README, as that's what most people will see. You can include documentation
there to show that there are more complex example playbooks in the examples
dire
Replies are inline.
On Tue, Feb 11, 2014 at 4:39 PM, Christopher O'Connell wrote:
> Was: Re: Reducing tickets queue
>
> Hello Ansible Community,
>
> When we stop contributing to an open source community, common courtesy
> compels me to declare the causes of such action.
>
First off, Ansible
Stan, we are not keeping the core/Tower versions in sync, it's mainly been
coincidental that it's worked out that way so far. That said, we will
probably be releasing an Ansible 1.4.5 in the near future, to address one
reported bug.
If you have any further questions, let us know.
Thanks!
On Tue
If they're common to all of the roles you're writing, best to make the
common part a role of its own and use the dependency system we have in
place. Just be sure that when you're listing the deps, that you do so in
the "username.rolename" format so that galaxy will properly link them as
dependencie
Thank you very much! Your solution works.
On Tuesday, February 11, 2014 5:27:50 PM UTC+1, David Adams wrote:
>
> This is a good point. Tomcat does NOT detach, so running startup.sh
> directly from an Ansible ssh session may well immediately shut down. You've
> got to wrap it in something that wi
As I noted on an early message -- I'm working on some riak related roles
for galaxy -- a number of the roles do some similar operations -- setting
up some repositories, doing some simple configurations, etc.
Is it better to contain those common operations in a common role and have
the other roles
Hi folks,
let me start by thanking the great people on the #ansible IRC channel,
notably jtanner, for pointing me into the right direction.
A quick word about the system I'm dealing with:
I've recently inherited a compute cluster at an academic institution that
also has central IT services. IT
did you look into the group_vars? for the default template create a
variable to specify which template (location/name of of file) under
group_vars/all, and if the other templates correspond to different host
groups in your inventory then override them in their specific group_var
On 11 February 2
Hi,
I have agent-install.yml that installs our application agent and deploys
the agent-config template, since agent-install.yml is shared by many roles
it's located under the common role tasks :
role/common/tasks/agent-install.yml
role/common/template/agent-config.j2
This tasks will be run f
I'm putting some finishing touches on a number of riak related roles.
Since riak is a distributed system, these roles really don't shine unless
they are used on a number of hosts. I'd like to provide some example
playbooks with the roles that show how to do this, but it seems there is
no convent
I have created a couple of tomcat init scripts that actually 'work' to
avoid these issues.
Let me look and see if i can publish one for general usage.
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop re
This is a good point. Tomcat does NOT detach, so running startup.sh
directly from an Ansible ssh session may well immediately shut down. You've
got to wrap it in something that will detach correctly. The easiest would
be nohup. startup.sh is also kind of pointless. You can just call
catalina.sh dir
Hi Wouter,
Thank you for looking into this and sharing your findings Wouter.
Good to hear that enabling management fixed it for you.
Alas for me that's not the case.
[root@geppetto ansible]# cobbler system list
metop-20.oma.be
metop-28.oma.be
zotac-09
zotac-24.oma.be
zotac-29
zo
Just using {{ ansible_ssh_user }} works for me - probably that got improved
meanwhile.
Am Montag, 15. April 2013 19:37:27 UTC+2 schrieb Steve Weber:
>
> I found this workaround
>
>
>> # fill fact $ansible_user_id while not sudo as root
>> - hosts: any
>> sudo: no
>> gather_facts: yes
>>
>
Hi
On Sun, Feb 09, 2014 at 12:25:06PM -0800, Alain Sahli wrote:
> Hi!
>
> I wrote a simple playbook that downloads, extracts and starts Tomcat. Here are
> the relevant parts of it:
>
> - name: Download Tomcat 7.0.42
> get_url: url=http://archive.apache.org/dist/tomcat/tomcat-7/v7.0.42/bin/
> a
I've noticed that Tower 1.4.5 has already been released
http://blog.ansibleworks.com/2014/02/10/tower-1-4-5-formerly-awx-released/,
but no ansible yet.
Shouldn't they be in sync?
If not, when ansible 1.4.5 is going to be available?
Thanks
Stan
--
You received this message because you are
use template and generate the lines, with a single IF that skips
ansible_hostname or ansible_fqdn (from facts).
--
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
t
Hi,
I have a postfix transport table on all the mailservers.
The file is pretty the same, but the line pointing the the very server
this file is on, is deactivated (by comment or by deleting).
What would be the sanest way to build this in ansible?
A template would be one option, but there mus
27 matches
Mail list logo
