[ansible-devel] New release candidate: ansible-core 2.14.4rc1

2023-03-21 Thread Matt Davis 
Hi all- we're happy to announce the following release candidate:

ansible-core 2.14.4rc1


How to get it
-

$ python3 -m pip install --user ansible-core==2.14.4rc1

The release artifacts can be found here:

#  Wheel: 2202442 bytes
# SHA256: a05e41e51fc9b2700249417501f40f3f72738832a4756d2ea907014940dd292d
https://files.pythonhosted.org/packages/4a/79/85fe2fcd89757f0bd5e3a6081bc82257f2293efd55ce59b5e7ff6f027085/ansible_core-2.14.4rc1-py3-none-any.whl
# Source: 11577844 bytes
# SHA256: 33bddb022b3de423a3ea86e332da35d4458d7248f78ba8ea98dc83197e22332f
https://files.pythonhosted.org/packages/69/45/fb26f8ff74861f7c24b3398c5904d0f1efb40e5049ca8f265a96f7489160/ansible-core-2.14.4rc1.tar.gz


What's new
--

This release is a maintenance release containing numerous bugfixes.

The full changelog can be found here:

https://github.com/ansible/ansible/blob/v2.14.4rc1/changelogs/CHANGELOG-v2.14.rst


Schedule for future releases


The release candidate will become a general availability release on 27
March 2023.


Porting help


If you discover any errors or if any of your working playbooks break when
you upgrade, please use the following link to report the regression:

https://github.com/ansible/ansible/issues/new/choose

In your issue, be sure to mention the version that works and the one that
doesn't.

Thanks!

-Matt Davis, Ansible Core Engineering

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-devel/CAJD0Ssh46RfgAUL8M6sfzoNpyDgFnm68p6oxRBmWerrx15WsCA%40mail.gmail.com.

[ansible-devel] New releases: ansible-core 2.12.1, ansible-core 2.11.7, ansible-base 2.10.16

2021-12-09 Thread Matt Davis 
Hi all- we're happy to announce the general release of:

- ansible-core 2.12.1
- ansible-core 2.11.7
- ansible-base 2.10.16


How to get it
-

$ pip install ansible-core==2.12.1 --user
or
$ pip install ansible-core==2.11.7 --user
or
$ pip install ansible-base==2.10.16 --user

The tar.gz of the release can be found here:

* ansible-core 2.12.1

https://pypi.python.org/packages/source/a/ansible-core/ansible-core-2.12.1.tar.gz
  SHA256: a4508707262be11bb4dd98a006f1b14817879a055e6b6c46ad9fca8894fb3073

* ansible-core 2.11.7

https://pypi.python.org/packages/source/a/ansible-core/ansible-core-2.11.7.tar.gz
  SHA256: b87188beacfac1bb6dc5cf65663f3c52e66e0f9990742db00a3dca71ebae2eee

* ansible-base 2.10.16

https://pypi.python.org/packages/source/a/ansible-base/ansible-base-2.10.16.tar.gz
  SHA256: d974214ed03ac129c299967aa4c98205943ba36f20040e7feb7248e0c3e2ea15


What's new
--

This release is a maintenance release containing numerous bugfixes.
 The full changelog is at:


* ansible-core 2.12.1

https://github.com/ansible/ansible/blob/v2.12.1/changelogs/CHANGELOG-v2.12.rst

* ansible-core 2.11.7

https://github.com/ansible/ansible/blob/v2.11.7/changelogs/CHANGELOG-v2.11.rst

* ansible-base 2.10.16

https://github.com/ansible/ansible/blob/v2.10.16/changelogs/CHANGELOG-v2.10.rst


What's the schedule for future maintenance releases?


The planned December releases have been deferred to account for holiday
staffing.
The next batch of release candidates is planned to be released on 24
January 2022.
The next general availability release will be one week after.


Porting Help


If you discover any errors or if any of your working playbooks break when
you
upgrade, please use the following link to report the regression:

  https://github.com/ansible/ansible/issues/new/choose

In your issue, be sure to mention the version that works and the one that
doesn't.

Thanks!

-Matt Davis, Ansible Core Engineering

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-devel/CAJD0SsjtbyGeRsKeFs8B2oEyWf-hWwzQ%3D7WAiEuwjB-%3D9UPQtw%40mail.gmail.com.

[ansible-devel] ansible-base 2.10.0b1 is available

2020-06-17 Thread Matt Davis 
Hi all- we're happy to announce a beta release of the new ansible-base 2.10 
package is now available! The ansible-base package consists of only the 
Ansible execution engine, related tools (e.g. ansible-galaxy, 
ansible-test), and a very small set of built-in plugins. Most content that 
was part of Ansible has been split off into individual Ansible Collections, 
which can be installed via the ansible-galaxy tool, or a forthcoming 
Ansible community distribution that will snapshot a set of collections 
roughly equivalent to what was in previous versions of Ansible. Most 
Ansible playbooks and roles will require the installation of some of these 
collections to be able to execute unmodified under ansible-base 2.10.


How to get it
-

$ pip install ansible-base==2.10.0b1 --user

The tar.gz of the release can be found here:

* ansible-base 2.10.0b1
  
https://pypi.python.org/packages/source/a/ansible-base/ansible-base-2.10.0b1.tar.gz
  SHA256: c0cbf9681088bcc10d873502ea7054eaadea5db0bf10ebd4926f908f28868234


What's new in ansible-base 2.10.0b1
---

In addition to numerous bugfixes, most new Ansible features in the 2.10 
release enhance Ansible's support for external plugins via collections. 
They include:

* Collection declaration of supported/tested Ansible versions
* Transparent redirection of plugins formerly included in Ansible to their 
destination collections
* Installation of collections from git repositories
* Various enhancements of test tooling

These features support our goal of allowing Ansible content that was 
written for previous versions of Ansible to run unmodified under 2.10, once 
the necessary collections are installed.


The full changelog is at:

  
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst


Thanks!

The Ansible Core Team

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-devel/1e689c57-2f3a-4372-ba7f-0075307bd9e1o%40googlegroups.com.

[ansible-devel] ansible-base 2.10 beta 1 delayed

2020-05-29 Thread Matt Davis 
Hi all,

The release of ansible-base 2.10 beta 1 (and the associated freeze) will be 
delayed by two weeks to Monday, June 15. There are a few features and 
infrastructure bits we want to make sure are included that just aren't 
quite ready yet. Thanks for your patience and understanding- happy 
automating!

Matt Davis (@nitzmahone)
Ansible Core Engineering

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-devel/8900de05-db5c-4f18-b6bb-8479a01d197f%40googlegroups.com.

[ansible-devel] New Ansible release 2.9.4

2020-01-20 Thread Matt Davis 
Hi all- we're happy to announce that the general release of Ansible 2.9.4 is
now available! This release contains a single bugfix to a regression in the
yum module, introduced in 2.9.3.


How do you get it?
--

$ pip install ansible==2.9.4 --user

The tar.gz of the release can be found here:

* 2.9.4
  https://releases.ansible.com/ansible/ansible-2.9.4.tar.gz
  SHA256: 2517bf4743d52f00d509396a41e9ce44e5bc1285bd7aa53dfe28ea02fc1a75a6


What's new in 2.9.4
---

This release is a maintenance release containing a single bugfix to the yum
module. The full changelog is at:

* 2.9.4
  
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst


What's the schedule for future maintenance releases?


Future maintenance releases will occur approximately every 3 weeks.  So 
expect
the next one around 2020-02-13.


Porting Help


We've published a porting guide at
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.9.html 
to
help migrate your content to 2.9.


If you discover any errors or if any of your working playbooks break when 
you
upgrade to 2.9.4, please use the following link to report the regression:

  https://github.com/ansible/ansible/issues/new/choose

In your issue, be sure to mention the Ansible version that works and the one
that doesn't.

Thanks!

-Matt Davis

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-devel/cfb2d7b1-228c-4e9f-9b22-1261b53c5767%40googlegroups.com.

[ansible-devel] New Ansible releases 2.9.3, 2.8.8, and 2.7.16

2020-01-15 Thread Matt Davis 
Hi all- we're happy to announce that the general release of Ansible 2.9.3,
2.8.8, and 2.7.16 are now available!


How do you get it?
--

$ pip install ansible==2.9.3 --user
or
$ pip install ansible==2.8.8 --user
or
$ pip install ansible==2.7.16 --user

The tar.gz of the releases can be found here:

* 2.9.3
  https://releases.ansible.com/ansible/ansible-2.9.3.tar.gz
  SHA256: 36f501a17fb15d210722b649d53582acf47835ea0bbda7eab79e13c945e4eac2
* 2.8.8
  https://releases.ansible.com/ansible/ansible-2.8.8.tar.gz
  SHA256: c364ff5807cb88af29b161a3a1d88ff737f10b930a24be66d88769ee204f4536
* 2.7.16
  https://releases.ansible.com/ansible/ansible-2.7.16.tar.gz
  SHA256: bb4a95a3e1a0f9e1aabd8cf628de68f5218fba3057b970b6b3c41cc53ab06268


What's new in 2.9.3, 2.8.8, and 2.7.16
--

These releases are maintenance releases containing security fixes for
CVE-2019-14904 (solaris_zone module) and CVE-2019-14905 (nxos_file_copy 
module),
as well as various bugfixes. The full changelogs are at:

* 2.9.3
  
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst
* 2.8.8
  
https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v2.8.rst
* 2.7.16
  
https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst


What's the schedule for future maintenance releases?


Future maintenance releases in the 2.9 series will occur approximately 
every 3
weeks.  So expect the next one around 2020-02-06. The 2.8 series is only 
accepting
critical bugfixes, and the 2.7 series is only accepting critical security
bugfixes, so releases will occur only as necessary.


Porting Help


We've published a porting guide at
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.9.html 
to
help migrate your content to 2.9.


If you discover any errors or if any of your working playbooks break when 
you
upgrade to 2.9.3, please use the following link to report the regression:

  https://github.com/ansible/ansible/issues/new/choose

In your issue, be sure to mention the Ansible version that works and the one
that doesn't.

Thanks!

-Matt Davis

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-devel/0e963f01-1ea8-45de-ac4d-5a0cc720a1a2%40googlegroups.com.

[ansible-devel] New Ansible release 2.9.2

2019-12-04 Thread Matt Davis 
Hi all- we're happy to announce that the general release of Ansible 2.9.2 is
now available!


How do you get it?
--

$ pip install ansible==2.9.2 --user

The tar.gz of the release can be found here:

* 2.9.2
  https://releases.ansible.com/ansible/ansible-2.9.2.tar.gz
  SHA256: 2f83f8ccc50640aa41a24f6e7757ac06b0ee6189fdcaacab68851771d3b42f3a


What's new in 2.9.2
---

This release is a maintenance release containing numerous bugfixes. The full
changelog is at:

* 2.9.2
  
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst


What's the schedule for future maintenance releases?


The next 2.9 series release is scheduled for early January, due to US 
holidays.
Future maintenance releases will occur approximately every 3 weeks.


Porting Help


We've published a porting guide at
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.9.html 
to
help migrate your content to 2.9.


If you discover any errors or if any of your working playbooks break when 
you
upgrade to 2.9.2, please use the following link to report the regression:

  https://github.com/ansible/ansible/issues/new/choose

In your issue, be sure to mention the Ansible version that works and the one
that doesn't.

Thanks!

-Matt Davis

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-devel/a8a28cf0-df5a-4bf5-ae7b-0e0fa025ebc2%40googlegroups.com.

[ansible-devel] New Ansible releases 2.7.15, 2.8.7, and 2.9.1

2019-11-13 Thread Matt Davis 
Hi all- we're happy to announce that the general release of Ansible 2.7.15,
2.8.7, and 2.9.1 are now available!


How do you get it?
--

$ pip install ansible==2.7.15 --user
or
$ pip install ansible==2.8.7 --user
or
$ pip install ansible==2.9.1 --user

The tar.gz of the releases can be found here:

* 2.7.15
  https://releases.ansible.com/ansible/ansible-2.7.15.tar.gz
  SHA256: 99bf683d069b3f73704182ece95b6618ae2090594a66e146f4d286c0cac858ce
* 2.8.7
  https://releases.ansible.com/ansible/ansible-2.8.7.tar.gz
  SHA256: 828239ca2b4d92865a00ab415caa932700f7c93f3e4838ddd55614ddf104c947
* 2.9.1
  https://releases.ansible.com/ansible/ansible-2.9.1.tar.gz
  SHA256: d87cb25df02284d59226ff1d935d7075a175f31d0db83564c2f1ca28bbbd4cb4


What's new in 2.7.15, 2.8.7, and 2.9.1
--

These releases are maintenance releases containing numerous bugfixes, 
including a
fix for CVE-2019-14864 (issue with Splunk and Sumologic callback plugins). 
The
full changelogs are at:

* 2.7.15
  
https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst
* 2.8.7
  
https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v2.8.rst
* 2.9.1
  
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst


What's the schedule for future maintenance releases?


Future 2.9 series maintenance releases will occur approximately every 3 
weeks, so
the next one can be expected around 2019-12-05. 2.8 is in critical bugfix 
only
mode, and 2.7 is in security bugfix only mode, so future releases for those 
will
be as needed.


Porting Help


We've published a porting guide at
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.9.html 
to
help migrate your content to 2.9.


If you discover any errors or if any of your working playbooks break when 
you
upgrade to 2.9.1, please use the following link to report the regression:

  https://github.com/ansible/ansible/issues/new/choose

In your issue, be sure to mention the Ansible version that works and the one
that doesn't.

Thanks!

-Matt Davis

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-devel/4bd04b7e-dc64-4159-846e-9b3ae5f4b7aa%40googlegroups.com.

[ansible-devel] New Ansible release 2.9.0rc5

2019-10-23 Thread Matt Davis 
Hi all- we're happy to announce that Ansible 2.9.0rc5 is now available! 
This is
anticipated as the final release candidate before Ansible 2.9.0 is generally
available within the next week or so.


How do you get it?
--

$ pip install ansible==2.9.0rc5 --user

The tar.gz of the release can be found here:

* 2.9.0rc5
  https://releases.ansible.com/ansible/ansible-2.9.0rc5.tar.gz
  SHA256: 0ef189c180a48d8702eba704093f7b7ab49ce54834a6a9848b33126f15e67ba8


What's new in 2.9.0rc5
--

This release is a maintenance release containing minor bugfixes. The full
changelog is at:

* 2.9.0rc5
  
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst


What's the schedule for 2.9.0 final?


Ansible 2.9.0 final is expected to be generally available within the next 
week
or so. Future 2.9 series maintenance releases will be every few weeks as 
needed.


Porting Help


We've published a porting guide at
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.9.html 
to
help migrate your content to 2.9.


If you discover any errors or if any of your working playbooks break when 
you
upgrade to 2.9.0rc5, please use the following link to report the regression:

  https://github.com/ansible/ansible/issues/new/choose

In your issue, be sure to mention the Ansible version that works and the one
that doesn't.

Thanks!

-Matt Davis

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-devel/4816a68b-0f6f-4eca-81b1-5e3f25d2ad41%40googlegroups.com.

[ansible-devel] Re: Powershell Version 2 - Got it working and would like to discuss

2017-03-31 Thread Matt Davis 
There are tools coming in Ansible 2.3 that should also help to do mass 
upgrades of PS2 hosts (eg, become/runas, win_psexec). The underlying WinRM 
exec wrapper in 2.3 has greatly increased reliance on Powershell 3 and .NET 
4 (which is why we didn't want to support back to PS2 in the first place), 
so especially if you want to use anything new that's happening in Ansible, 
I'd suggest looking into upgrading to at least PS3 (though PS5 is supported 
on 2008R2, and supposedly a much simpler upgrade path than 3 or 4, just 
sayin'). Unless you've got some obscure technical reason *not* to upgrade, 
you should be able to do it en-masse with Ansible. :)

-Matt

On Friday, March 31, 2017 at 9:25:34 AM UTC-7, jhawkesworth wrote:
>
> I'd suggest using the upgrade_to_ps3 script mentioned here 
> http://docs.ansible.com/ansible/intro_windows.html#getting-to-powershell-3-0-or-higher
>  
> on your s2008r2 machines.- powershell 2 pre-dates the remote management via 
> web services stuff..  You can just about get a remote shell with ps2 but 
> the capabilities will be very, very limited.  Be aware that there's also a 
> hotfix need on s2008r2 /WMF 3.0 http://support.microsoft.com/kb/2842230 
> (also mentioned on the same page).
>
> Jon
>
> On Friday, March 31, 2017 at 9:58:20 AM UTC+1, Herman Bergmans wrote:
>>
>> Hi Eric. 
>> I am very interested in what you had to do to get powershell 2 working 
>> with Ansible.
>> I am in a situation where I still have a LOT of Windows 2008 R2 out there 
>> that still have powershell 2 installed.
>> I'd love to know which changes you had to make to get it to work.
>>
>> Thx
>> - Herman -
>>
>>
>>
>> On Wednesday, March 16, 2016 at 3:22:59 AM UTC+1, Eric Mowry wrote:
>>>
>>> Matt,
>>>The code is uploaded as well as the changes to the setup.ps1, 
>>> win_copy.ps1, win_stat.ps1 under the stable-2.0 branch within the following 
>>> repos. 
>>>
>>> https://github.com/elum/ansible
>>> https://github.com/elum/ansible-modules-core
>>>
>>> -Eric
>>>
>>> On Tuesday, March 15, 2016 at 1:24:20 PM UTC-4, Eric Mowry wrote:
>>>>
>>>> Hi Matt,
>>>>
>>>> I just finished merging the changes into 2.0.1.0 and will be finishing 
>>>> testing/committing them to github later today. I 100% understand the 
>>>> desire 
>>>> to have the latest PS version supported and the issues with having to 
>>>> support PS2 going forward would not be the best use of time for the 
>>>> project. Long term I have even thought about just keeping a side install 
>>>> running for boxes that require PS2 or using PS2 specific modules if the 
>>>> winrm.py, powershell.py and powershell.ps1 changes could be considered 
>>>> acceptable. The PS2 requirement is only for XP/2003 and Windows 2008/7 
>>>> running Microsoft specific applications below these versions Exchange 2010 
>>>> SP3, SharePoint 2010 without the latest workaround for management tools, 
>>>> and System Center 2012.
>>>>
>>>> -Eric
>>>>
>>>> On Tuesday, March 15, 2016 at 12:55:41 PM UTC-4, Matt Davis wrote:
>>>>>
>>>>> Hi Eric,
>>>>>
>>>>> The decision to require PS3 at a minimum was made before I got here, 
>>>>> but in general I don't disagree with it. While I'm morbidly curious, I'd 
>>>>> have a lot of concerns about supporting PS2 generally. The biggest few 
>>>>> off 
>>>>> the top of my head:
>>>>> - We'd no longer be able to assume the presence of .NET 4.0, which 
>>>>> hampers a number of planned core Windows enhancements.
>>>>> - Increased testing matrix (we're already planning ~5 target 
>>>>> environments for Windows CI with PS3/4/5 and Server 2008R2, 2012R2, 2016).
>>>>> - Missing cmdlets and functionality for existing important Windows 
>>>>> modules
>>>>>
>>>>> That said, we could look at supporting just enough PS2 in the core 
>>>>> connection infrastructure and actions/modules to support bootstrapping to 
>>>>> PS3+ via Ansible. Do you have the updated code posted somewhere?
>>>>>
>>>>> -Matt Davis (Ansible Core Windows Lead)
>>>>>
>>>>>
>>>>> On Monday, March 14, 2016 at 7:52:13 PM UTC-7, Eric Mowry wrote:
>>>>>>
>>>>>> I have read on blogs, forums and mailing lists that Powershell 
>>>>>>

[ansible-devel] Windows Working Group IRC meetings

2017-02-28 Thread Matt Davis 
We're pleased to announce that the Ansible Windows Working Group will begin 
biweekly IRC meetings in the Freenode #ansible-meeting channel on March 
13/14, 2017 (depending on your time zone). This will be a regular developer 
forum to discuss and guide the overall direction of Ansible's support for 
managing Windows hosts, as well as to talk over specific pull requests and 
feature ideas. As with all Ansible working groups, the intent is to keep 
the meetings development-focused, so support questions and other discussion 
will be redirected to the public #ansible IRC channel and mailing list.

In an attempt to accommodate the wide home-timezone range of Ansible 
Windows contributors, we're initially scheduling the meetings to occur 
every other week, on Monday afternoons and Friday mornings (Pacific Time). 
More details, including calendar, agenda links, and minutes, can be found 
at https://github.com/ansible/community/blob/master/MEETINGS.md.

This has been a long time coming- we're looking forward to engaging with 
the community in a more regular and realtime fashion. Hope to see you there!

- Matt Davis, Principal Software Engineer, Ansible Core / Red Hat

-- 
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: Experimantal support for Windows Containers

2017-02-13 Thread Matt Davis 
Noice- looking forward to playing around with this a little more after 2.3 
is out the door (and Windows containers in general- haven't touched them 
since 2016 RTM'd). 

I think we can probably do something a little more integrated on the 
connection-side- Windows jump-host support in the WinRM connection plugin 
is something that's getting asked for a little more frequently, and this is 
basically the same use-case (except that it's an on-machine jump instead of 
networked). I've prototyped a couple different things over the years- maybe 
I ought to roadmap it for 2.4 and just get it done.

Thanks!

-Matt

On Sunday, February 12, 2017 at 10:59:32 AM UTC-8, Trond Hindenes wrote:
>
> Hi, 
> I've hacked a bit on Windows Container support for Ansible during the 
> weekend, and have pushed a working copy here:
> https://github.com/trondhindenes/ansible/tree/win_containers
>
> Essentially the win_containers thingy is implemented as separate 
> connection and shell types, and get invoked by using a hosts file entry 
> like this:
>
> awscontainer ansible_host=10.245.8.26 ansible_connection=winrm_containers 
> containerid=
>
> This works quite simply by "regular" remoting to the host, and then using 
> the "invoke-command -ContainerId " from  there to execute the 
> command.
>
> I've only tested this on Windows 2016 running a container based on the 
> "microsoft/windowsservercore" image.
>
> I think Ansible could be a powerful thing to use with Windows containers, 
> for the same reasons as the "ansible containers" project - it allows for 
> much more advanced configuration/building of an image than what a 
> Dockerfile does, and especially given Windows' reliance on api's instead of 
> text files for management, I'd say this is even more true on Windows than 
> on Linux.
>
> My code is very rough since I don't fully understand the internals of 
> Ansible, it was just meant as an excercise.
>
>
>

-- 
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: Public meeting on core/extras repo merges

2016-10-31 Thread Matt Davis 
This meeting has been postponed. We'll reschedule soon.

On Thursday, October 27, 2016 at 9:36:04 AM UTC-7, Matt Davis wrote:
>
> Hi all,
>
> The Ansible core team will be holding a public meeting on Monday Oct 31 at 
> 1700 UTC regarding logistics and timing around merging the 
> ansible-modules-core and ansible-modules-extras GitHub repos back into the 
> main ansible/ansible repo. We'll be streaming our discussion via Youtube 
> live at https://www.youtube.com/watch?v=wiq2dLjzOUw, and live chat will 
> be in Freenode IRC #ansible-meeting. Feel free to join us and participate 
> via IRC!
>
>
> Matt Davis
> Principal Software Engineer (Ansible Core)
> Red Hat
>

-- 
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: Windows wait_for module

2016-10-20 Thread Matt Davis 
Yeah, I had that one on my list as a planned core module build for 2.3, so 
if you've got a decent start on one, let's see it!

-Matt

On Wednesday, October 19, 2016 at 1:52:20 AM UTC-7, jhawkesworth wrote:
>
> Hi,
>
> Definitely create a pull request, its the best way to get your code 
> reviewed by others (and the only way to get it included with ansible).   
> Definitely worth working your way through this if you haven't read it yet - 
> http://docs.ansible.com/ansible/developing_modules.html
>
> Also, please create one pull request per module.
>
> Many thanks.
>
> Jon
>
>
>
> On Tuesday, October 18, 2016 at 9:38:03 PM UTC+1, paul.nor...@gmail.com 
> wrote:
>>
>> Hi,
>>  
>> I have developed a Windows version of the wait_for module that mimics* 
>> part* of functionality of the Linux wait_for module.
>>
>> Currently my module is capable of the following:
>>
>>
>>- wait for the existence of a file (path parameter) when state=present
>>- wait for a file (set by path parameter) to not exist when 
>>state=absent
>>- wait for a file (set by path parameter) to contain a string 
>>matching a regular expression (set by search_regex parameter)
>>
>>
>> I would like to share this with the community to enable others to add 
>> more functionality and to reuse what i have done so far.
>>
>> Should I create a pull request to contribute this?
>>
>> Also, if i have multiple modules to share, should this be done in one 
>> pull request or multiple? Sorry for the dumb question but i am new to this 
>> :)
>>
>> Thanks
>> Paul
>>
>

-- 
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: [RFC] - Migrating ansible's paramiko SSH client to asynchronous parallel SSH client

2016-06-28 Thread Matt Davis 
Hi Dan,

I suspect if you dig in a bit, you'll probably be looking at a pretty major 
architectural change to Ansible's TQM to avoid the subprocess overhead, as 
we currently fork host workers before the connection. Making a 
ParallelSSH-based connection plugin should be pretty straightforward, but 
I'm not sure you'd see a lot of benefit under Ansible's current process 
model (and would probably actually see a perf regression for lightly-loaded 
scenarios).

I've got selfish reasons for wanting to see the TQM process model 
abstracted (*cough* native Windows support *cough*) but it'd be a pretty 
big meatball IMO.

If you really want to pursue it, that's a thing that's big enough to write 
a proposal for .

-Matt


On Tuesday, June 28, 2016 at 9:12:36 AM UTC-7, Dan wrote:
>
> Bumpity bump :)
>
> Is there any interest in having asynchronous parallel SSH connections in 
> Ansible? 
>
> The use case is tasks in parallel over SSH on a number of servers which is 
> currently comparatively slow and very resource intensive, cpu usage and 
> system load wise.
>
> On Monday, June 6, 2016 at 10:58:35 AM UTC+1, Dan wrote:
>>
>> Hello dev list,
>>
>> Many thanks for your efforts on ansible, very useful tool.
>>
>> Have a new feature I'd like to work on that would like to float by you 
>> for comments and if it sounds like a good feature to implement before 
>> submitting a PR.
>>
>> In short, would like to add the ability to use the ParallelSSH client 
>> library  to run SSH commands 
>> via ansible. The library uses paramiko and gevent to provide an 
>> asynchronous parallel SSH client python library.
>>
>> This would greatly benefit ansible when running multiple commands in 
>> parallel. The current parallel implementation uses multiprocessing and 
>> increases system load on the host running ansible linearly as # of threads 
>> increases.
>>
>> Benefits of using the ParallelSSH library:
>>  
>>  * Asynchronous parallel SSH commands
>>  * No system load induced on the host running it, regardless of # of 
>> parallel connections
>>  * Persistent connections by default, one connection per host
>>  * Stdout/stderr and exit code retrieval built in
>>  * Configurable parallelism level
>>  * Native proxying/tunneling support, also asynchronous. No ProxyCommand, 
>> no subprocess per tunnel
>>  * Native SFTP support
>>  * Pure python library, no cmd line tools used
>>  * No openssh or other ssh cmd line tool dependencies
>>  * Posix systems and windows compatible
>>
>> Effect on ansible:
>>  * Uses gevent's monkey patching to make paramiko asynchronous. Monkey 
>> patching of subprocess in particular will also affect ansible's use of 
>> subprocess, though it should be compatible.
>>  * gevent library would be a new requirement for ansible
>>
>>
>> Is this of interest? If so, where do you think it should go, a new 
>> connection type perhaps or overriding existing paramiko implementation? I 
>> would think overriding paramiko implementation to use the library would 
>> make most sense. As the library itself uses paramiko it is already 
>> compatible.
>>
>> As a bonus if use of paramiko is overridden, most of the code in 
>> paramiko_ssh.py 
>> 
>>  
>> can go as the client implementation lives entirely in the library.
>>
>> Would argue that the subprocess use of the ssh binary in ssh.py should be 
>> overridden as well, at least for parallel commands, but given backwards 
>> compatibility requirements doubt that would be feasible.
>>
>> Comments appreciated, thanks.
>>
>> - Dan
>>
>>

-- 
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: Windows put_file performance (please test!)

2016-05-10 Thread Matt Davis 
You might want to try the new pywinrm 0.2.0 RC (see recent post here) - the 
entire guts got switched out, but I'm guessing you have something broken in 
Windows itself (major delay in AD auth or something) that's introducing 
those delays... But try the new pywinrm out just for giggles- on a normal 
local setup, it's still good for ~20% speed boost for most things.

On Tuesday, May 10, 2016 at 1:17:10 PM UTC-7, Matt Davis wrote:
>
> All of this shipped in 2.0.0 and pywinrm 0.1.1. You seem to have something 
> very ... special? going on that I've never figured out. The times you're 
> seeing are universally *abysmal* - I've seen better times from customers 
> running stuff over satellite connections.
>
> On Tuesday, May 10, 2016 at 12:39:45 PM UTC-7, Michael Perzel wrote:
>>
>> Matt,
>>
>> Did these improvements make it into ansible 2.0.1? I'm working on 
>> upgrading our infrastructure and running the winrm tests isn't showing the 
>> improvement I was expecting. I haven't been able to find any documentation 
>> about when these fixes were going to make into devel or a stable release.
>>
>> Thanks,
>>
>> Michael
>>
>> On Thursday, November 5, 2015 at 10:24:03 AM UTC-6, Matt Davis wrote:
>>>
>>> Once you've done the pywinrm upgrade, if it's still taking more than 
>>> about 2s between local servers, can I get you to post output from a run 
>>> where ANSIBLE_DEBUG=1 is set in the runner's environment? I'm just curious 
>>> what the heck it's doing that's taking so long (or if we need to add some 
>>> more instrumentation to figure it out).
>>>
>>> On Thursday, November 5, 2015 at 8:15:53 AM UTC-8, Michael Perzel wrote:
>>>>
>>>> Lol, my test rig is 2 local RHEL servers. It boggles my mind it takes 
>>>> so long but 22 seconds is a lot better than 45. raw mkdir c:\temp runs in 
>>>> a 
>>>> couple seconds. I am using an old version of pywinrm. I'll try out your 
>>>> patched version.
>>>>
>>>> Thanks,
>>>>
>>>> On Wednesday, November 4, 2015 at 8:22:46 PM UTC-6, Matt Davis wrote:
>>>>>
>>>>> Man, 22s is still *really* slow for a win_file dir create- are you 
>>>>> running this against a Cuisinart over a 300baud modem or something? ;)
>>>>>
>>>>> Make sure you're running with the new pywinrm 0.1.1 that just released 
>>>>> last week- that has my perf fix that halves the number of winrm 
>>>>> round-trips 
>>>>> when you're using Basic auth. 
>>>>>
>>>>> Just for reference, this branch with pywinrm 0.1.1 does 
>>>>>
>>>>> time ansible win2008r2-vagrant -i hosts -m win_file -a "path=c:/makeme 
>>>>> state=directory"
>>>>>
>>>>> in ~1.7s against a local VM, and ~6s against a t2.micro 2012R2 in AWS.
>>>>>
>>>>> -Matt
>>>>>
>>>>>
>>>>> On Tuesday, November 3, 2015 at 6:34:48 AM UTC-8, Michael Perzel wrote:
>>>>>>
>>>>>> I also had missed the step to switch branches. For completeness I 
>>>>>> also ran source hacking/env-setup after step "git submodule update" in 
>>>>>> Jon's directions.
>>>>>>
>>>>>> The use case I was most concerned with of creating one directory on 
>>>>>> one windows hosts has gone from 45 seconds to 22 seconds!
>>>>>> /opt/ansible/ansible-test/win_file> time ansible-playbook main.yml
>>>>>>
>>>>>> TASK [Create directory] 
>>>>>> 
>>>>>> changed: [host]
>>>>>>
>>>>>> real0m22.714s
>>>>>>
>>>>>> I also ran the winrm tests and task [test_win_copy : copy an empty 
>>>>>> file] hangs for me as well.
>>>>>>
>>>>>>
>>>>>> On Tuesday, November 3, 2015 at 2:56:00 AM UTC-6, jhawkesworth wrote:
>>>>>>>
>>>>>>> For info spotted another error in the integration tests
>>>>>>>
>>>>>>> for me, it fails during win_file tests at this point
>>>>>>>
>>>>>>> - name: win copy directory structure over
>>>>>>>   win_copy: src=foobar dest={{win_output_dir}}
>>>>>>>
>>>>>>> ran with -v but it hung.  When hit Ct

Re: [ansible-devel] Re: Windows put_file performance (please test!)

2016-05-10 Thread Matt Davis 
All of this shipped in 2.0.0 and pywinrm 0.1.1. You seem to have something 
very ... special? going on that I've never figured out. The times you're 
seeing are universally *abysmal* - I've seen better times from customers 
running stuff over satellite connections.

On Tuesday, May 10, 2016 at 12:39:45 PM UTC-7, Michael Perzel wrote:
>
> Matt,
>
> Did these improvements make it into ansible 2.0.1? I'm working on 
> upgrading our infrastructure and running the winrm tests isn't showing the 
> improvement I was expecting. I haven't been able to find any documentation 
> about when these fixes were going to make into devel or a stable release.
>
> Thanks,
>
> Michael
>
> On Thursday, November 5, 2015 at 10:24:03 AM UTC-6, Matt Davis wrote:
>>
>> Once you've done the pywinrm upgrade, if it's still taking more than 
>> about 2s between local servers, can I get you to post output from a run 
>> where ANSIBLE_DEBUG=1 is set in the runner's environment? I'm just curious 
>> what the heck it's doing that's taking so long (or if we need to add some 
>> more instrumentation to figure it out).
>>
>> On Thursday, November 5, 2015 at 8:15:53 AM UTC-8, Michael Perzel wrote:
>>>
>>> Lol, my test rig is 2 local RHEL servers. It boggles my mind it takes so 
>>> long but 22 seconds is a lot better than 45. raw mkdir c:\temp runs in a 
>>> couple seconds. I am using an old version of pywinrm. I'll try out your 
>>> patched version.
>>>
>>> Thanks,
>>>
>>> On Wednesday, November 4, 2015 at 8:22:46 PM UTC-6, Matt Davis wrote:
>>>>
>>>> Man, 22s is still *really* slow for a win_file dir create- are you 
>>>> running this against a Cuisinart over a 300baud modem or something? ;)
>>>>
>>>> Make sure you're running with the new pywinrm 0.1.1 that just released 
>>>> last week- that has my perf fix that halves the number of winrm 
>>>> round-trips 
>>>> when you're using Basic auth. 
>>>>
>>>> Just for reference, this branch with pywinrm 0.1.1 does 
>>>>
>>>> time ansible win2008r2-vagrant -i hosts -m win_file -a "path=c:/makeme 
>>>> state=directory"
>>>>
>>>> in ~1.7s against a local VM, and ~6s against a t2.micro 2012R2 in AWS.
>>>>
>>>> -Matt
>>>>
>>>>
>>>> On Tuesday, November 3, 2015 at 6:34:48 AM UTC-8, Michael Perzel wrote:
>>>>>
>>>>> I also had missed the step to switch branches. For completeness I also 
>>>>> ran source hacking/env-setup after step "git submodule update" in Jon's 
>>>>> directions.
>>>>>
>>>>> The use case I was most concerned with of creating one directory on 
>>>>> one windows hosts has gone from 45 seconds to 22 seconds!
>>>>> /opt/ansible/ansible-test/win_file> time ansible-playbook main.yml
>>>>>
>>>>> TASK [Create directory] 
>>>>> 
>>>>> changed: [host]
>>>>>
>>>>> real0m22.714s
>>>>>
>>>>> I also ran the winrm tests and task [test_win_copy : copy an empty 
>>>>> file] hangs for me as well.
>>>>>
>>>>>
>>>>> On Tuesday, November 3, 2015 at 2:56:00 AM UTC-6, jhawkesworth wrote:
>>>>>>
>>>>>> For info spotted another error in the integration tests
>>>>>>
>>>>>> for me, it fails during win_file tests at this point
>>>>>>
>>>>>> - name: win copy directory structure over
>>>>>>   win_copy: src=foobar dest={{win_output_dir}}
>>>>>>
>>>>>> ran with -v but it hung.  When hit Ctrl-C I got this traceback:
>>>>>>
>>>>>> Process WorkerProcess-2:
>>>>>> Traceback (most recent call last):
>>>>>>   File "/usr/lib/python2.7/multiprocessing/process.py", line 258, in 
>>>>>> _bootstrap
>>>>>> self.run()
>>>>>>   File 
>>>>>> "/home/jon/putfile/ansible/lib/ansible/executor/process/worker.py", line 
>>>>>> 100, in run
>>>>>> (host, task, basedir, job_vars, play_context, shared_loader_obj) 
>>>>>> = self._main_q.get()
>>>>>>   File "/usr/lib/python2.7/multiprocessing/queues.py", line 117, in 
>>>>>> get
>&