to ec2_group.
:D #happy
On Sunday, 17 May 2015 00:35:01 UTC+5:30, Sankalp Khare wrote:
I've faced this, with an elasticsearch sg being one of my requirements (in
my setup I'd have to make a directed acylic graph of the security groups in
order to have them all created in a single run).
Resorted
I've faced this, with an elasticsearch sg being one of my requirements (in
my setup I'd have to make a directed acylic graph of the security groups in
order to have them all created in a single run).
Resorted to a playbook with two plays, one that creates my security groups
(no rules), tagged
Thanks! that helped :)
I had a machine with 2FA for SSH enabled. I needed to apply my playbook
there. SSH into localhost from localhost was also not working for obvious
reasons. Had almost given up when I found this! :) Saved me a considerable
amount of manual labour!
On Sunday, 21 July 2013
On Wednesday, 25 December 2013 18:14:37 UTC+5:30, Brian Coca wrote:
end/start the playbook with a pause: action
@Bryan, how would that help if I had multiple plays in the playbook, only
one (or a few) of which I was doing with serial, and between whose
iterations I would like to have
I am using ansible to create instances in EC2. I set disableApiTermination
to true using an AWS CLI invocation for each instance that I create (On
that note, I hope https://github.com/ansible/ansible-modules-core/pull/205 gets
accepted into the devel branch soon).
However, I would like to
for which all else has completed without failure.
Still, the original feature request seems like a useful thing to have.
On Friday, 14 November 2014 02:45:39 UTC-6, Sankalp Khare wrote:
I am using ansible to create instances in EC2. I set disableApiTermination
to true using an AWS CLI invocation
registration right there, before finishing the playbook run.
I really hope this sounds like something useful and worth adding.
Thanks!
On Friday, 14 November 2014 02:53:06 UTC-6, Sankalp Khare wrote:
Also note that using tasks labelled with when:
some-registered-variable|failed doesn't cover my
request on github for the ansible-modules-core project,
this should not be hard to add
On Mon, Nov 10, 2014 at 9:21 PM, Sankalp Khare sankal...@gmail.com
javascript: wrote:
In comparison, here is the output of the apt module, with the stdout_lines
field that I find readable:
TASK: [apt
Hi,
I've been trying to get some helpful output from playbook runs that use the
yum and apt modules.
When I register the results of an invocation of these modules, I notice
that the apt module very conveniently returns a stdout_lines field which
contains something that is much more readable
I second Giorgio. Dmitry, you're a lifesaver :D
On Friday, 6 December 2013 03:46:13 UTC-6, Giorgio Crivellari wrote:
Dmitry you're a f* genius!!
Michael, please add Dimitry example in variables website documentation
page... many users will appreciate!
Thanks guys!
Giorgio
Il
Hi Renaud,
I totally get what you are looking to achieve. Perhaps you've achieved it
already in the past year. Assuming that you are happy with specifying a start
index = x and a count = N to produce machines with names containing x, x+1,
x+2, ... x+N, I think the following playbook example
I must also add that I've got a central group_vars/all file from which I
pull all the variables like region, instance types, environment specific
load balancer names, etc.
On Wednesday, 29 October 2014 04:02:19 UTC-5, Sankalp Khare wrote:
Hi Renaud,
I totally get what you are looking
The end-goal is to get the variables loaded into your ansible run. How
about separating out your task into two distinct activities:
1. Fetching the file from S3 *on the machine where you are doing the
ansible run*, and loading variables from it
2. Uploading a copy of the file to the
The documentation says:
Modules can be written in any language and are found in the path specified
by ANSIBLE_LIBRARY or the --module-path command line option.
[ http://docs.ansible.com/developing_modules.html ]
On Tuesday, 28 October 2014 14:01:26 UTC-5, Tiglath wrote:
Error is
Be that as it may, i've found this tip invaluable in quickly applying
chosen roles to a few servers / test servers.
On Thursday, 17 October 2013 01:20:02 UTC+5:30, Michael DeHaan wrote:
Yeah the trailing comma is a hack, we should not suggest it in most cases.
On Wed, Oct 16, 2013 at 3:43
Hi,
Over the past few months using Ansible, I've accumulated a handy bunch of
playbooks which create different varieties of servers. The top-level
directory looks like this :
modular-role-based-playbooks
|-- [-rw-r--r--] create-bare-micro-instance-amazon.yml
|-- [-rw-r--r--]
Hi,
I often come across the situation where I need to apply some roles X,Y,Z on
a bunch of machines. How do I do that without having to edit the list of
roles in a playbook? In other words, could there be something of the type :
$ ansible-playbook -i inven role-applier.yml --extra-vars
Hi,
Does ansible support uploading of .crt, .key (and optionally .chain) files
into AWS? I would like to complete the whole cycle, i.e. upload a cert, and
then refer to it in aws_elb_lb
http://docs.ansible.com/ec2_elb_lb_module.html listeners.
Thanks,
Sankalp
--
You received this message
Just saw the responses. Thanks, Michael, for the workaround (syntax
update). The cowsay thing was just an offhand question, as I didn't, for
the life of me, know why Ansible would start doing that all of a sudden :P
On Wednesday, 27 August 2014 17:48:55 UTC+5:30, Michael DeHaan wrote:
this
Doesn't the ec2_metric_alarm module do this already? Or was this post from
a time before that module was added...
On Thursday, 13 March 2014 21:09:16 UTC+5:30, Michael DeHaan wrote:
There's no specific plan for adding this, but we're always open to pull
requests for upgrades.
Not sure if
20 matches
Mail list logo
