Just tried pywinrm 0.2rc6. Both ansible_winrm_transport=ntlm and ansible_winrm_transport=kerberos work fine. Thanks!
Running on RHEL7 with Ansible 2.0.2. On Tuesday, May 10, 2016 at 12:33:33 AM UTC+2, Matt Davis wrote: > > A new pywinrm release that supports NTLM, kerberos delegation, and much > improved performance is just around the corner! Version 0.2.0 is at release > candidate, and a test build has been published to testpypi. Just waiting > for any final testing/review from Alexey before the final publish of the > release build to PyPI. > > > Feel like giving it a whirl? > > > pip install pywinrm[kerberos]==0.2rc3 -i https://testpypi.python.org/pypi > --extra-index-url https://pypi.python.org/pypi > > > will get you the RC3 test build from testpypi (along with the released > dependencies from the real pypi), and the optional kerberos dependencies. > If you don't want kerberos, just get rid of the [kerberos] extras part in > the pkgspec above. > > > This pywinrm build has been tested with Ansible 1.9.5, 2.0.2 and 2.1RC1. > > > Once you have it installed, ansible_winrm_transport=ntlm in your > inventory for Windows hosts (sorry, this one only works for Ansible 2.0+) > lets you use domain users with both domain\username and [email protected] > <javascript:> syntax. When using ansible_winrm_transport=kerberos, > kerberos delegation support can be enabled just by adding > ansible_winrm_kerberos_delegation=yes. > > > We've added a few new niceties around arg parsing in Ansible 2.1, like > warnings if you pass inventory args that your installed version of pywinrm > doesn't understand (and not requiring things like username when not > required) but otherwise, most of the goodies in here should work on older > versions of Ansible too. > > > This release of pywinrm has switched the HTTP(S) client from urllib2 to > requests, allowing us to take advantage of persistent connections, which > give another significant performance boost to Windows on Ansible > (especially over HTTPS, as we don't have to repeat the TLS handshake for > each WinRM request). In my testing, local VMs experienced about a 20% speed > boost on small tasks, while remote VMs (eg, AWS instances) got more like a > 50% speed boost to small tasks (due to the higher latency cost during > connection setup). File transfer performance (eg, win_copy) should also be > noticeably improved again with this release, though I haven't benchmarked > it. > > > Feel free to file issues at https://github.com/diyan/pywinrm/issues. > > > Enjoy! > > > Matt Davis > > Principal Software Engineer (Ansible Core Windows) > > Red Hat > -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/31e784b8-f9f7-4f8e-9eea-8b2bc9572f2e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
