, Frank Perks wrote:
>
> Thanks. Unfortunately it is not part of my dynamic inventory.
>
> Anisble runs a tool that provisions a bunch of ec2 instances, installs and
> configures a bunch of software on the systems (eventually this will be
> replaced by ansible i hope). The too
So i have a small problem, the only thing i have from the output of another
tool is just an instance_id, along with its region. I need to grab some
more information about the ec2 instance (such as the platform, tags, etc)
in order to actually determine what inventory groups it belongs in.
Thanks. Unfortunately it is not part of my dynamic inventory.
Anisble runs a tool that provisions a bunch of ec2 instances, installs and
configures a bunch of software on the systems (eventually this will be
replaced by ansible i hope). The tool returns a series of instance ids and
their
Thanks brian. action_plugins directory worked fine for me. :D
On Friday, September 25, 2015 at 6:08:18 PM UTC-4, Brian Coca wrote:
>
> first, you should be able to just write the var into a facts file on
> the target machine and fact gathering shoudl automatically pick it up
>
ample - so hope this
> helps! and it may prompt some 'better' suggestions! ; )
> https://groups.google.com/d/msg/ansible-project/X1Q93QOk6Ew/ZygP5rXmfEkJ
>
> On Tuesday, September 22, 2015 at 12:49:13 AM UTC+1, Frank Perks wrote:
>>
>> I am trying to shrink ~30+ roles into a single ro
Any ideas? This is really blocking me.
On Monday, September 21, 2015 at 7:49:13 PM UTC-4, Frank Perks wrote:
>
> I am trying to shrink ~30+ roles into a single role to drastically reduce
> the amount of duplicate and copy and pasted code into a single nice and
> neat role. One of
I am trying to shrink ~30+ roles into a single role to drastically reduce
the amount of duplicate and copy and pasted code into a single nice and
neat role. One of the problems is each role sets a specifically named fact
basically like:
ec2__foo
What i want to do is this:
set_fact:
"{{
I am dumb, and the issue is because i have:
- rescue
when it should be:
rescue
My mistake.
On Tuesday, September 15, 2015 at 9:03:04 AM UTC-4, Frank Perks wrote:
>
> So i was hoping to use blocks as an easy way to notify success/failure of
> ansible runs.
>
> - block
So i was hoping to use blocks as an easy way to notify success/failure of
ansible runs.
- block:
- include: build.yml
- include: deploy_site.yml
- name: Notify Slack it successfully deployed
slack:
- rescue:
- name: Notify Slack it failed
slack:
When there is an error in
hostname_fqdn instead.
On Tuesday, September 15, 2015 at 1:41:52 AM UTC-4, Kuberboef wrote:
>
>
>
> On Monday, 14 September 2015 18:01:34 UTC+2, Frank Perks wrote:
>>
>> ansible-hostname is a role, and should be in the roles directory.
>>
>> Assuming /home/stefaansm/trust
ansible-hostname is a role, and should be in the roles directory.
Assuming /home/stefaansm/trusty64/Ansible/ is where your playbooks are.
Then ansible-hostname should be located at
/home/stefaansm/trusty64/Ansible/roles/ansible-hostname
On Monday, September 14, 2015 at 8:20:06 AM UTC-4,
You make an variable mandatory to throw an error if a var is not defined:
- hosts:
vars:
var_required_by_role:
- name: "{{ variable | mandatory }}"
user: "foo"
roles:
- myrole
Alternatively you can edit ansible.cfg to change this setting to True
I didn't realize you can specify the ansible connection on a per task level!
That completely changes stuff!
I will give this a shot!
On Tuesday, September 8, 2015 at 4:51:48 PM UTC-4, Brian Coca wrote:
>
> have you tried this?
>
> - hosts: windows
> gather_facts: false
> tasks:
>
>
I am trying to reboot a windows server after installing .net + a bunch of
dependencies. I have a super simple PS module to schedule a reboot. However
afterwords i would like to wait for the WinRM connection to come back:
- name: Configuring windows
hosts: windows
roles:
- win_dotnet_46
This is running latest version of devel (i updated this morning).
delegate_to / connnection: local does not seem to work.
On Wednesday, September 9, 2015 at 8:45:47 AM UTC-4, Brian Coca wrote:
>
> What version of ansible? have you tried with connection: local or
> delegate_to: localhost:?
>
>
IHV0js
On Wednesday, September 9, 2015 at 7:30:25 AM UTC-4, Frank Perks wrote:
>
> I didn't realize you can specify the ansible connection on a per task
> level!
>
> That completely changes stuff!
>
> I will give this a shot!
>
> On Tuesday, September 8, 2015
gt; as for connection: local, I've had far better results with delegate_to:
> localhost on the current devel branch.
>
> On Wednesday, September 9, 2015 at 3:38:03 PM UTC+2, Frank Perks wrote:
>>
>> This is running latest version of devel (i updated this morning).
&g
Just to add something else, in 1.9.4 both Trond and my stuff works fine.
On Wednesday, September 9, 2015 at 10:44:35 AM UTC-4, Frank Perks wrote:
>
> Hi Trond,
>
> I tried your module, and it fails with the same issue as above.
>
> fatal: [52.8.31.205]: FAILED! => {"fa
Hi,
I am unsure exactly how i am supposed to handle and work with windows
passwords when working with EC2 and inventories. I know i can query the
passwords by using ec2_win_password, however i am unsure exactly how i can
use this value to set the ansible_ssh_pass. For that connection.
For
19 matches
Mail list logo
