Perfect thanks.
--
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 group, send email to ansible-pr
I'm not sure I understand what it is your trying to do here...
If you are trying to have some hosts execute another group's role, you can
use *includes*.
Otherwise, if you can explain why you are nesting *group3/4 *under *roles*
when you have *group1* set as *hosts*.
On Monday, December 14, 20
I actually just transitioned from saltstack to ansible a few weeks ago.
For me ansible's playbook structure is much easier to grasp than salt.
Everything is clearly defined, you know exactly what hosts, perform what
roles, and which variables are associated.
Speed wise, ansible's transportation
>>> glanceclient.__version__
'1.2.0'
>>> print requests.__version__
2.2.1
On Friday, December 11, 2015 at 9:08:53 AM UTC-8, David Shrewsbury wrote:
>
> What version of python-glanceclient and requests do you have installed?
>
>
>
--
You received this message because you are subscribed to the Go
This is from the inventory script. Everything is fine until it hits glance
to pull the image object.
Couldn't construct image object
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/shade/openstackcloud.py",
line 254, in _get_client
**kwargs)
File
"/usr/lo
Running into an issue on 2.0 rc2 and latest dev version (2.1)
TASK [common : launch a compute instance]
**
task path:
/home/cluser/automata_ansible/automata_ansible_openstack/openstack/roles/common/tasks/main.yml:2
ESTABLISH LOCAL CONNECTION FOR USER: root
loc
Currently the playbook runs a task which generates a result file in
/tmp/result.out
Then it runs a parsing python script I put in common/files/parser.py and
passes /tmp/result.out to the script as a parameter. The script prints to
STDOUT the parsed results in a JSON format as such
{
"elapsed