Boto is required on the host it runs on.
There is no way to execute boto specific things on "test" when it is only
installed on local host.
What you can do is something like collect information on "test" then run
boto stuff on "localhost".
/martin
On Sat 6 Jun 2015 at 05:53 David Pires wrote:
Setting the interpreter for the remote host would require boto being
installed on the remote host, which isn't what I'm after.
Setting the variable on localhost and accessing it remotely using hostvars
does work, however, the real issue is how ansible can't seem to find boto
when its run inside
So set ansible_python_interpreter to the correct Python binary for the
virtualenv on the remote host.
Also, you can execute tasks on localhost and then reference it from another
host:
http://docs.ansible.com/playbooks_variables.html#magic-variables-and-how-to-access-information-about-other-hosts
>
> ---
> - hosts: remote_host
> pre_tasks:
> - name: Read host
> connection: local
> route53:
> command: get
> zone: ZONE
> record: RECORD
> type: A
> register: host_record
> roles:
> - test
When boto/ansib
I'm confused, what you are stating seems to contradict itself.
--
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.
T
I am trying to run the route53 module locally, register its output and use
that variable in a task for a remote host.
This works if i have boto installed globally, using connection: local. It
does not work when using inside a virtualenv.
I reproduced this in a virtual machine with boto availabl
I don't think I'm parsing what you are saying correctly. I thought you
were running the task that required boto locally.
ansible_python_interpreter is what you use to direct ansible to the
correct python with the correct dependencies, it only applies for
those hosts for which you set it.
--
B
I think I have found the issue, I'm running ansible in a virtualenv.
I have "ansible_python_interpreter" set for localhost, this doesn't work
for remote hosts.
When I run ansible with boto available globally, it works. Is there a
solution to get ansible to find dependencies for remote hosts?
then if you added connection: local to the task, it should be
executing locally and picking up boto
On Fri, Jun 5, 2015 at 8:33 PM, David Pires wrote:
> boto is installed on the ansible machine, not the remote host
>
> On Friday, June 5, 2015 at 8:31:04 PM UTC-4, Brian Coca wrote:
>>
>> Do you
boto is installed on the ansible machine, not the remote host
On Friday, June 5, 2015 at 8:31:04 PM UTC-4, Brian Coca wrote:
>
> Do you have boto installed on your machine?
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe f
Do you have boto installed on your machine?
--
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 to this grou
I am getting the same error: "failed=True msg='boto required for this
module"
My inventory file is as follows:
[localhost]
localhost ansible_python_interpreter=PATH
[test]
IP
And my playbook:
---
- hosts: test
pre_tasks:
- name: Read host
connection: local
rou
---
- hosts: remote_hosts
sudo: True
gather_facts: True
pre_tasks:
- name: Read current host
connection: local
sudo: False
route53:
command: get
zone: zone
record: record
type: A
register: host_record
roles:
- my
I am trying to use the route53 module in a playbook.
If i install boto and add credentials the play works (reading a record and
registering it), however I want to know if I can do this locally (where
boto is installed) and have that registered variable available on remote
hosts.
Example playb
14 matches
Mail list logo
