Re: [ansible-devel] Re: Playbook help - syntax

2016-05-25 Thread Kai Stian Olstad

On 25.05.2016 07:23, 'jhawkesworth' via Ansible Development wrote:
Single line ansible module calls can use the key=value key=value 
syntax,
but when you are using the multi-line yaml style syntax it needs to be 
key:

value


This statement is not correct.


yamllint.com or a yaml-aware text editor can be a help when you are 
getting

used to writing playbooks.


Code like this work
- name: Update the Apache config
  copy: >
src=httpd.conf
dest=/etc/httpd/httpd.conf

Even dropping the bigger than and it works, also yamllint.com says it is 
valid.


More about multiline here
https://support.ansible.com/hc/en-us/articles/201957837-How-do-I-split-an-action-into-a-multi-line-format-

--
Kai Stian Olstad

--
You received this message because you are subscribed to the Google Groups "Ansible 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[ansible-devel] "with_items" skipping with module "include'

2016-05-25 Thread Clément VALENTIN
Hi,

I encounter a bug when i want to use "with_items" in include file when 
module "include" already use 'with_items"...

Exemple :

*tasks/main.yml :*
>   include: 'includes/filesystem.yml'
>   vars:
> project_config: "{{ item }}"
>   with_items:
> - "{{ host_web_apps_applications }}"
>   when: 
> - "project_config.host_web_apps_vg_name is defined"
>
 

> *tasks/includes/filesystem.yml :*
> - name: "[FILESYSTEM] Check mysql data"
>   stat: path="{{ apache_default_path }}"
>   register: fs_www
>   
> - debug: msg="{{ fs_www }}"
>   with_items: "{{ fs_www }}"
>
 

> *Result :* 
>
 

> TASK [web_apps : [P300] [OM] [FILESYSTEM] Check mysql data] 
>> 
>
> ok: [DEBIANVM]
>
>
>> TASK [web_apps : debug] 
>> 
>
> skipping: [DEBIANVM] => (item=stat)
>
> skipping: [DEBIANVM] => (item=changed)
>
>
>
Anybody say why debug is skipping in my include file ?? oO
When i remove when condition in include module, debug work fine...

Thx for your help :) 

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[ansible-devel] Why items automaticaly skipped when i use with_items in "include" module ??

2016-05-25 Thread Clément VALENTIN
Hi,

I encounter a bug when i want to use "with_items" in include file when 
module "include" already use 'with_items"...

Exemple :

*tasks/main.yml :*
>   include: 'includes/filesystem.yml'
>   vars:
> project_config: "{{ item }}"
>   with_items:
> - "{{ host_web_apps_applications }}"
>   when: 
> - "project_config.host_web_apps_vg_name is defined"
>
 

> *tasks/includes/filesystem.yml :*
> - name: "[FILESYSTEM] Check mysql data"
>   stat: path="{{ apache_default_path }}"
>   register: fs_www
>   
> - debug: msg="{{ fs_www }}"
>   with_items: "{{ fs_www }}"
>
 

> *Result :* 
>
 

> TASK [web_apps : [FILESYSTEM] Check mysql data] 
>
> ok: [DEBIANVM]
>
>
>> TASK [web_apps : debug] 
>> 
>
> skipping: [DEBIANVM] => (item=stat)
>
> skipping: [DEBIANVM] => (item=changed)
>
>
>
Anybody say why debug is skipping in my include file ?? oO
When i remove when condition in include module, debug work fine...

Thx for your help :) 

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[ansible-devel] Re: Ansible with Windows - 401 Error

2016-05-25 Thread Bud Calabrese
Do you think it worked because I did a kinit bud@V-BLOG.LOCAL? So when that 
ticket expires it will fail? 

On Wednesday, May 25, 2016 at 12:17:52 AM UTC-5, jhawkesworth wrote:
>
> Don't forget the kerberos tickets expire after a while.
>
> Also another thing to watch out for is that kerberos is time-sensitive, so 
> make sure your ansible controller's clock is synchronized with your windows 
> domain controllers.
>
> If you ntp you can set it up to sync with your domain controllers - I 
> found some instructions here: 
> https://community.spiceworks.com/topic/143891-possible-to-synchronize-ntp-on-a-linux-server-to-a-windows-domain-controller
>
> Hope this helps,
>
> Jon
>
> On Wednesday, May 25, 2016 at 1:22:55 AM UTC+1, Bud Calabrese wrote:
>>
>> Its crazy cause I could login as the user bud last night into the server. 
>> Tried again and today it works! 
>>
>> Thank you for your help. 
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[ansible-devel] Re: Ansible with Windows - 401 Error

2016-05-25 Thread Bud Calabrese
I just tried rerunning the playbook and it failed...How do I fix it so I do 
not have to run a kinit bud@V-BLOG.LOCAL? 

fatal: [SVR2k8-Update.V-BLOG.LOCAL]: FAILED! => {"failed": true, "msg": 
"kerberos: (('Unspecified GSS failure.  Minor code may provide more 
information', 851968), ('No Kerberos credentials available', -1765328243)), 
ssl: 401 Unauthorized. basic auth failed"}

On Wednesday, May 25, 2016 at 7:56:43 AM UTC-5, Bud Calabrese wrote:
>
> Do you think it worked because I did a kinit bud@V-BLOG.LOCAL? So when 
> that ticket expires it will fail? 
>
>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[ansible-devel] Re: Issue 15405 : Synchronized failed with delegate_to and sudo password

2016-05-25 Thread Guillaume Dufour
up

Le lundi 2 mai 2016 22:43:25 UTC+2, Guillaume Dufour a écrit :
>
> Hello,
>
> i found a regression (maybe it's a normal change of API) on the 
> synchronized module on the 2.0.1. I try on 1.9.5 and it' work.
>
> My use case is :
>
>- i have a bastion to access to all host and my ssh config use the 
>proxycommand to do it.
>- i use my personnal account to access to host and then do a sudo to 
>deploy with the applicative account
>- and i want to synchronized tow nodes
>
> My problem is in 1.9.5, ansible do the following process : 
>
>- ssh connect with my account
>- sudo and provide my password
>- do the rsync with the deploy account to the other host with the same 
>account
>
> In 2.0.1, ansible do:
>
>- ssh connect
>- rsync (with my account) with rsync with sudo (when become is 
>activate) but don't use the become user and don't provide my sudo passord.
>
>
> So rsync return, sudo ask a password but there no tty normal ;o(
>
>
> So i propose 3 solutions :
>
>- keep the become on the delegate_to side as before
>- add specific args to module to move become on delegate side
>- provide password with an echo 'password' | sudo -s -u become_user 
>rsync on rsync path
>
> For this last one, i try it , but not work due to a exclamation point in 
> my password so i think i have a problem with single quote
>
>
> what i can do ? what do you prefere ?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [ansible-devel] Re: Ansible 2.1.0 RC4 is ready for testing

2016-05-25 Thread Toshio Kuratomi
Just an update for the mailing list -- we finished reviewing and merging
this too late for 2.1.0  but it is now merged into the stable-2.1 branch
for inclusion into 2.1.1.

-Toshio

On Mon, May 23, 2016 at 7:23 AM, Bernhard L.  wrote:

> Hi,
>>
>>
> It would be nice if this issue
> https://github.com/ansible/ansible-modules-extras/issues/2144 could be
> resolved before 2.1.0 gets released.
> There is already a pull request with the fix:
> https://github.com/ansible/ansible-modules-extras/pull/2149
> Otherwise the pkgutil-module would be unusable.
>
> Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-devel+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [ansible-devel] Re: Playbook help - syntax

2016-05-25 Thread 'jhawkesworth' via Ansible Development
Kai,

Thanks for this, I didn't know that should make converting ad hoc ansible 
command into playbook style entries easier.
Stylistically I wouldn't want to mix key: value and key=value though as in 
the example above.

Jon

On Wednesday, May 25, 2016 at 9:52:30 AM UTC+1, Kai Stian Olstad wrote:
>
> On 25.05.2016 07:23, 'jhawkesworth' via Ansible Development wrote: 
> > Single line ansible module calls can use the key=value key=value 
> > syntax, 
> > but when you are using the multi-line yaml style syntax it needs to be 
> > key: 
> > value 
>
> This statement is not correct. 
>
>
> > yamllint.com or a yaml-aware text editor can be a help when you are 
> > getting 
> > used to writing playbooks. 
>
> Code like this work 
> - name: Update the Apache config 
>copy: > 
>  src=httpd.conf 
>  dest=/etc/httpd/httpd.conf 
>
> Even dropping the bigger than and it works, also yamllint.com says it is 
> valid. 
>
> More about multiline here 
>
> https://support.ansible.com/hc/en-us/articles/201957837-How-do-I-split-an-action-into-a-multi-line-format-
>  
>
> -- 
> Kai Stian Olstad 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[ansible-devel] Re: Ansible with Windows - 401 Error

2016-05-25 Thread 'jhawkesworth' via Ansible Development
Yes, once the ticket expires you are no longer authorized to do things, so 
it will fail.

You have a few options for dealing with this.

If you happen to log into your ansible controller machine using your 
windows domain username and password (it is possible to use active 
directory for this) then you will likely have a kerberos ticket as a result 
of logging in.  If you want to use that ticket I think you can just put a @ 
in the ansible_user name in your windows group vars and ansible will 
attempt to use the ticket you got when you logged in.

Another way of dealing with it is to wrap ansible in a script that calls 
kinit before you start running ansible.

I use an ansible connection plugin which acquires the ticket for me and 
then removes it at the end of each run of ansible or ansible-playbook.
If you are interested in using it, there's a version of it here 
https://github.com/ansible/ansible/pull/14972 but its not likely to be 'the 
ansible way' of doing things in future and may need some tweaks to get 
working.

Also, now that 2.1 is out you can use NTLM instead of kerberos if that is 
an option for you.

Hope this helps,

Jon



On Wednesday, May 25, 2016 at 1:59:36 PM UTC+1, Bud Calabrese wrote:
>
> I just tried rerunning the playbook and it failed...How do I fix it so I 
> do not have to run a kinit bud@V-BLOG.LOCAL? 
>
> fatal: [SVR2k8-Update.V-BLOG.LOCAL]: FAILED! => {"failed": true, 
> "msg": "kerberos: (('Unspecified GSS failure.  Minor code may 
> provide more information', 851968), ('No Kerberos credentials available', 
> -1765328243)), ssl: 401 Unauthorized. basic auth failed"}
>
> On Wednesday, May 25, 2016 at 7:56:43 AM UTC-5, Bud Calabrese wrote:
>>
>> Do you think it worked because I did a kinit bud@V-BLOG.LOCAL? So when 
>> that ticket expires it will fail? 
>>
>>>


-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[ansible-devel] OpenStack heat ansible modules

2016-05-25 Thread Sridhar L
I searched for heat ansible module for deploying the VMs in OpenStack cloud 
but could not find any. Are there any modules available for heat to deploy 
the stacks using ansible?

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [ansible-devel] OpenStack heat ansible modules

2016-05-25 Thread Bryce Walter
You could check the official OpenStack Ansible project.
https://github.com/OpenStack/openstack-ansible

Also documentation on extending the Ansible core-modules into the
openstack-ansible project.
http://docs.openstack.org/developer/openstack-ansible/developer-docs/extending.html

Bryce Walter
On May 25, 2016 8:48 PM, "Sridhar L"  wrote:

> I searched for heat ansible module for deploying the VMs in OpenStack
> cloud but could not find any. Are there any modules available for heat to
> deploy the stacks using ansible?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-devel+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.