from:"Toshio Kuratomi"

[ansible-project] Ansible-4.6.0 release

2021-09-21 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-4.6.0 package has been
released! The update contains bugfixes and new, backwards compatible
features in the contained collections.

How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 3 (or
earlier), you need to uninstall Ansible and Ansible Base before
installing Ansible 4:

```
$ pip uninstall ansible ansible-base
$ pip install ansible==4.6.0 --user
```

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

* Ansible 4.6.0
https://pypi.python.org/packages/source/a/ansible/ansible-4.6.0.tar.gz
* SHA256: 2955fcbf51367f8bd88c38a86f8be83d4fcd05f778afb4feed31abfe8dcff639

What's new in Ansible 4.6.0
---

* We've added a way to get the version of the Ansible package that is
installed programmatically:

```
 $ python -c 'from ansible_collections.ansible_release import
ansible_version; print(ansible_version)'
 4.6.0
```

* Collections which have opted into being a part of the Ansible-4
unified changelog will have an entry on this page:
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst#v4-6-0

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/ansible-4.6.0.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-4.6.0.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-core-2.11.5 which this release of ansible
installs: 
https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst

What's the schedule for new Ansible releases after 4.6.0?
-

* Except for ansible-2.9.x, older versions of ansible are not seeing
maintenance releases.  If there is a desire for maintenance releases
of older versions, drop by a Community Working Group Meeting to
discuss how you can help. (
https://github.com/ansible/community/tree/main/meetings#wednesdays )

* Maintenance releases of ansible-4.x will occur roughly every three
weeks.  Expect 4.6.0 roughly on October 12.

* We're planning to release Ansible-5.0.0 at the end of November, 2021.

Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html

-Toshio

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

[ansible-project] Ansible-4.5.0 has been released

2021-08-31 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-4.5.0 package has been
released! The update contains bugfixes and new, backwards compatible
features in the contained collections.

How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 3 (or
earlier), you need to uninstall Ansible and Ansible Base before
installing Ansible 4:

```
$ pip uninstall ansible ansible-base
$ pip install ansible==4.5.0 --user
```

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

* Ansible 4.5.0
https://pypi.python.org/packages/source/a/ansible/ansible-4.5.0.tar.gz
* SHA256: cc5352b2351a381015ece79eab783a1b0668f97b377810fed3c746e2f1d50db1


What's new in Ansible 4.5.0
---

* We've added a way to get the version of the Ansible package that is
installed programmatically:

```
 $ python -c 'from ansible_collections.ansible_release import
ansible_version; print(ansible_version)'
 4.5.0
```

* Collections which have opted into being a part of the Ansible-4
unified changelog will have an entry on this page:
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst#v4-5-0

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/ansible-4.5.0.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-4.4.0.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-core-2.11.4 which this release of ansible
installs: 
https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst

What's the schedule for new Ansible releases after 4.5.0?
-

* Except for ansible-2.9.x, older versions of ansible are not seeing
maintenance releases.  If there is a desire for maintenance releases
of older versions, drop by a Community Working Group Meeting to
discuss how you can help. (
https://github.com/ansible/community/tree/main/meetings#wednesdays )

* Maintenance releases of ansible-4.x will occur roughly every three
weeks.  Expect 4.6.0 roughly on September 21.

* We're planning to release Ansible-5.0.0 at the end of November, 2021.

Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html

-Toshio

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

[ansible-project] Ansible-4.4.0 released

2021-08-10 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-4.4.0 package has been
released! The update contains bugfixes and new, backwards compatible
features in the contained collections.

How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 3 (or
earlier), you need to uninstall Ansible and Ansible Base before
installing Ansible 4:

```
$ pip uninstall ansible ansible-base
$ pip install ansible==4.4.0 --user
```

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

* Ansible 4.4.0
https://pypi.python.org/packages/source/a/ansible/ansible-4.4.0.tar.gz
* SHA256: 4f19820ba2762e02051e6fdd00bf270b191990daf399687a32b06a0aa410360c

What's new in Ansible 4.4.0
---

* We've added a way to get the version of the Ansible package that is
installed programmatically:

```
 $ python -c 'from ansible_collections.ansible_release import
ansible_version; print(ansible_version)'
 4.3.0
```

* Collections which have opted into being a part of the Ansible-4
unified changelog will have an entry on this page:
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst#v4-4-0

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/ansible-4.4.0.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-4.4.0.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-core-2.11.3 which this release of ansible
installs: 
https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst

What's the schedule for new Ansible releases after 4.4.0?
-

* Except for ansible-2.9.x, older versions of ansible are not seeing
maintenance releases.  If there is a desire for maintenance releases
of older versions, drop by a Community Working Group Meeting to
discuss how you can help. (
https://github.com/ansible/community/tree/main/meetings#wednesdays )

* Maintenance releases of ansible-4.x will occur roughly every three
weeks.  Expect 4.4.0 roughly on August 10.

* We're planning to release Ansible-5.0.0 in November, 2021.

Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html

-Toshiox

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

[ansible-project] Ansible-4.3.0 has been released

2021-07-20 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-4.3.0 package has been
released! The update contains bugfixes and new, backwards compatible
features in the contained collections.

How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 3 (or
earlier), you need to uninstall Ansible and Ansible Base before
installing Ansible 4:

```
$ pip uninstall ansible ansible-base
$ pip install ansible==4.3.0 --user
```

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

* Ansible 4.3.0
https://pypi.python.org/packages/source/a/ansible/ansible-4.3.0.tar.gz
* SHA256: aeb0007a18e8914dd3ffe0acb2c4377f2d1f25e01c39e845c6cb8b16bdc1018b
*
What's new in Ansible 4.3.0
---

* We've added a way to get the version of the Ansible package that is
installed programmatically:

```
 $ python -c 'from ansible_collections.ansible_release import
ansible_version; print(ansible_version)'
 4.3.0
```

* Collections which have opted into being a part of the Ansible-4
unified changelog will have an entry on this page:
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst#v4-3-0

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/ansible-4.3.0.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-4.3.0.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-core-2.11.2 which this release of ansible
installs: 
https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst

What's the schedule for new Ansible releases after 4.3.0?
-

* Except for ansible-2.9.x, older versions of ansible are not seeing
maintenance releases.  If there is a desire for maintenance releases
of older versions, drop by a Community Working Group Meeting to
discuss how you can help. (
https://github.com/ansible/community/tree/main/meetings#wednesdays )

* Maintenance releases of ansible-4.x will occur roughly every three
weeks.  Expect 4.4.0 roughly on August 10.

* We're planning to release Ansible-5.0.0 in November, 2021.

Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html

-Toshio

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQfOXQDqv-24%3DWZhoY4OYsYf3fquB%3DawUQ5rDckeEXPNQ%40mail.gmail.com.

[ansible-project] Ansible 4.2.0 released

2021-06-30 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-4.2.0 package has been
released! The update contains bugfixes and new, backwards compatible
features in the contained collections.

How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 3 (or
earlier), you need to uninstall Ansible and Ansible Base before
installing Ansible 4:

```
$ pip uninstall ansible ansible-base
$ pip install ansible==4.2.0 --user
```

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

* Ansible 4.2.0
https://pypi.python.org/packages/source/a/ansible/ansible-4.2.0.tar.gz
* SHA256: 737d819ffbd7a80c28795b4edd93e59ad21e6e6d53af0d19f57412814f9260d0

What's new in Ansible 4.2.0
---

* We've added a way to get the version of the Ansible package that is
installed programmatically:

```
 $ python -c 'from ansible_collections.ansible_release import
ansible_version; print(ansible_version)'
 4.2.0
```

* Collections which have opted into being a part of the Ansible-4
unified changelog will have an entry on this page:
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst#v4-2-0

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/ansible-4.2.0.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-4.2.0.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-core-2.11.2 which this release of ansible
installs: 
https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst

What's the schedule for new Ansible releases after 4.2.0?
-

* Except for ansible-2.9.x, older versions of ansible are not seeing
maintenance releases.  If there is a desire for maintenance releases
of older versions, drop by a Community Working Group Meeting to
discuss how you can help. (
https://github.com/ansible/community/tree/main/meetings#wednesdays )

* Maintenance releases of ansible-4.x will occur roughly every three
weeks.  Expect 4.3.0 roughly on July 20.

* We're planning to release Ansible-5.0.0 in November, 2021.

Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html

-Toshio

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQtoc2wXPHmXj6JRg7RSQavMzzb71FGh-CXS1h3S%2B%3Di5g%40mail.gmail.com.

[ansible-project] Ansible-4.1.0 release

2021-06-10 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-4.1.0 package has been
released! The update contains bugfixes and new, backwards compatible
features in the contained collections.

How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 3 (or
earlier), you need to uninstall Ansible and Ansible Base before
installing Ansible 4:

```
$ pip uninstall ansible ansible-base
$ pip install ansible==4.1.0 --user
```

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

* Ansible 4.1.0
https://pypi.python.org/packages/source/a/ansible/ansible-4.1.0.tar.gz
* SHA256: f561cca7fbc4daa14d98e18cd0cb74bd8b173f1501b8fa11543f6ef002de3167

What's new in Ansible 4.1.0
---

* We've added a way to get the version of the Ansible package that is
installed programmatically:

```
 $ python -c 'from ansible_collections.ansible_release import
ansible_version; print(ansible_version)'
 4.1.0
```

* Collections which have opted into being a part of the Ansible-4
unified changelog will have an entry on this page:
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst#v4-1-0

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/ansible-4.1.0.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-4.1.0.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.11.1 which this release of ansible
installs: 
https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst

What's the schedule for new Ansible releases after 4.1.0?
-

* Except for ansible-2.9.x, older versions of ansible are not seeing
maintenance releases.  If there is a desire for maintenance releases
of older versions, drop by a Community Working Group Meeting to
discuss how you can help. (
https://github.com/ansible/community/tree/main/meetings#wednesdays )

* Maintenance releases of ansible-4.x will occur roughly every three
weeks.  Expect 4.2.0 roughly on June 29.

* We're tentatively planning to release Ansible-5.0.0 in November, 2021.

Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html

-Toshio

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaRLCQekL6Ws9E%3DkCYW%3DhWhyT3vEdKnSkriy%3DzVMw-tRGA%40mail.gmail.com.

[ansible-project] Ansible 4.0.0 final has been released!

2021-05-18 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-4.0.0 package is now
available! This update is based on the ansible-core-2.11.x package
which is a major update from the one used by Ansible 3.  Ansible 3 was
based on Ansible Base 2.10.x. There may be backwards incompatibilities
in the core playbook language.  Please see the porting guide for
details.


How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 3 (or
earlier), you need to uninstall Ansible and Ansible Base before
installing Ansible 4:

```
$ pip uninstall ansible ansible-base
$ pip install ansible==4.0.0 --user
```

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

* Ansible 4.0.0:
https://pypi.python.org/packages/source/a/ansible/ansible-4.0.0.tar.gz
  SHA256: 6f67ca5c634e4721d1f8e206dc71d60d1a114d147945355bfc902bd37eb07080

What's new in Ansible 4.0.0
---

* This version of Ansible is based on Ansible Core 2.11 which is a new
major update of the ansible-core package.  It may contain backwards
incompatible changes to the playbook language and command line
programs.  Please see the porting guide (linked at the bottom) for
more information.

* We've added a way to get the version of the Ansible package that is
installed programmatically:

```
 $ python -c 'from ansible_collections.ansible_release import
ansible_version; print(ansible_version)'
 4.0.0
```

* Collections which have opted into being a part of the Ansible 4.0.0
unified changelog will have an entry on this page:
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/ansible-4.0.0.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* The changelog for Ansible Core 2.11, which this release of ansible
installs, is located here:
https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst


What's the schedule for new Ansible releases after 4.0.0?
-

* New minor releases will occur approximately every three weeks
(Ansible 4.1.0, Ansible 4.2.0, etc).  They will contain bugfixes and
new features but no backwards incompatibilities.

* Now that Ansible 4 has been released, updates to Ansible 3 will stop.
  *  We've been putting together a document on issues that would need
to be addressed if someone would like to volunteer to create long term
updates to Ansible 3: https://hackmd.io/plQlGzcFRFGLnPXIeg3cwQ

* In case you missed the shift in version numbers and split of the
Ansible Core and Ansible packages that have been taking place over the
past year, here are some blog posts explaining the changes that
culminated in the Ansible 3 release:
  * https://www.ansible.com/blog/announcing-the-community-ansible-3.0.0-package
  * https://www.ansible.com/blog/ansible-3.0.0-qa


Porting Help
-

A unified porting guide for collections which have opted-in is
available here:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html

-Toshio Kuratomi

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

[ansible-project] Ansible-3.4.0 released

2021-05-11 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-3.4.0 package has been
released! The update contains bugfixes and new, backwards compatible
features in the contained collections.

If you would like to learn about how and why we got to version 3.0.0,
we invite you to visit our blog for the background as well as a Q:

- https://www.ansible.com/blog/announcing-the-community-ansible-3.0.0-package
- https://www.ansible.com/blog/ansible-3.0.0-qa

How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
earlier), you need to uninstall ansible before installing the 3.x
version:

```
$ pip uninstall ansible
$ pip install ansible==3.4.0 --user
```

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

* Ansible 3.4.0
https://pypi.python.org/packages/source/a/ansible/ansible-3.4.0.tar.gz
SHA256: ca34e2c0c3f92cad5e528c94c133e620845feb11cc62f42e98d28271fe5bd924

What's new in Ansible 3.4.0
---

* The Ansible package has moved to semantic versioning
(https://semver.org/). This standard allows you to tell if a new
version of Ansible contains incompatibilities by looking at the
version number. We've moved from 3.3.0 to 3.4.0 to show that this
release should be backwards compatible with Ansible-3.3.0 but may
contain new features.  Read the semver specification for more
information.

* Collections which have opted into being a part of the Ansible-3
unified changelog will have an entry on this page:
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/3/CHANGELOG-v3.rst#v3-4-0

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/3/ansible-3.4.0.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-3.4.0.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.10.9 which this release of ansible
installs: 
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst

What's the schedule for new Ansible releases after 3.4.0?
-

* Except for ansible-2.9.x, older versions of ansible are not seeing
maintenance releases.  If there is a desire for maintenance releases
of older versions, drop by a Community Working Group Meeting to
discuss how you can help. (
https://github.com/ansible/community/tree/main/meetings#wednesdays )

* We're currently planning to release Ansible-4.0.0 next week, on May
18, 2021.  When this release happens, we will no longer be providing
updates of the Ansible-3 package.  See the Ansible 4 Roadmap for
details:  https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_4.html

Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_3.html

-Toshio

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

[ansible-project] Ansible-4.0.0rc1

2021-05-11 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the Ansible-4.0.0 release candidate 1
package is now available! This update is based on the
Ansible-core-2.11.x package which is a major update from the Ansible 3
package (Ansible 3 was based on Ansible-base-2.10.x). There may be
backwards incompatibilities in the core playbook language.  Please see
the porting guide for details.


How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible-2.9.x
(or earlier), you need to uninstall ansible before installing Ansible
4.  It is also recommended to uninstall ansible-base before upgrading:

```
$ pip uninstall ansible ansible-base
$ pip install ansible==4.0.0rc1 --user
```

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

* Ansible 4.0.0rc1:
https://pypi.python.org/packages/source/a/ansible/ansible-4.0.0rc1.tar.gz
  SHA256: 0221b6503e602fb9a442f170876aa9dbbe8d1204b740a656e0111fbe6c7f4c81

What's new in Ansible 4.0.0
---

* This version of Ansible is based on ansible-core-2.11.x which is a
new major update of the ansible-core package.  It may contain
backwards incompatible changes to the playbook language and command
line programs.  Please see the porting guide (linked at the bottom)
for more information.

* We've added a way to get the version of the ansible package that is
installed programmatically::

 $ python -c 'from ansible_collections.ansible_release import
ansible_version; print(ansible_version)'
 4.0.0rc1

* Collections which have opted into being a part of the Ansible-4.0.0
unified changelog will have an entry on this page:
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/ansible-4.0.0rc1.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-core-2.11 which this release of ansible
installs: 
https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst


What's the schedule for new Ansible releases after 4.0.0rc1?
---

* Please see the ansible roadmap for the full release schedule for
ansible-4.0.0: https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_4.html

* Unless a blocker bug is found, ansible-4.0.0 final is scheduled for 5-18-2021

* Once ansible-4.0.0 is released, new minor releases will occur
approximately every three weeks (ansible-4.1.0, ansible-4.2.0, etc).
They will contain bugfixes and new features but no backwards
incompatibilities.

* At the moment, the plan is for updates to ansible-3 to stop once
ansible-4.0.0 final is released.
  *  We've been putting together a document on issues that would need
to be addressed if someone would like to volunteer to create long term
updates to Ansible-3: https://hackmd.io/plQlGzcFRFGLnPXIeg3cwQ


Porting Help
-

A unified porting guide for collections which have opted-in is
available here:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html

-Toshio

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

[ansible-project] Ansible-4.0.0 beta2 released

2021-05-05 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the Ansible-4.0.0 beta2 package is now
available! This update is based on the Ansible-core-2.11.x package
which is a major update from the Ansible-3 package (Ansible-3 was
based on Ansible-base-2.10.x). There may be backwards
incompatibilities in the core playbook language.  Please see the
porting guide for details.


How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible-2.9.x
(or earlier), you need to uninstall ansible before installing
Ansible-4.  It is also recommended to uninstall ansible-base before
upgrading:

```
$ pip uninstall ansible ansible-base
$ pip install ansible==4.0.0b2 --user
```

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

* Ansible 4.0.0b2:
https://pypi.python.org/packages/source/a/ansible/ansible-4.0.0b2.tar.gz
  SHA256: 194ea15deb1724090242f680ae5501094543aadb65222511b9fc55df55d0ff4b

What's new in Ansible 4.0.0
---

* This version of Ansible is based on ansible-core-2.11.x which is a
new major update of the ansible-core package.  It may contain
backwards incompatible changes to the playbook language and command
line programs.  Please see the porting guide (linked at the bottom)
for more information.

* We've added a way to get the version of the ansible package that is
installed programmatically::

 $ python -c 'from ansible_collections.ansible_release import
ansible_version; print(ansible_version)'
 4.0.0b2

* Collections which have opted into being a part of the Ansible-4.0.0
unified changelog will have an entry on this page:
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/ansible-4.0.0b2.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-core-2.11 which this release of ansible
installs: 
https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst


What's the schedule for new Ansible releases after 4.0.0b2?
---

* This is the last anticipated beta of Ansible-4.  Release Candidate 1
is scheduled for next week.

* Unless a blocker bug is found, Ansible-4.0.0 final is scheduled for 5-18-2021

* Please see the ansible roadmap for the full release schedule for
ansible-4.0.0: https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_4.html

* Once ansible-4.0.0 is released, new minor releases will occur
approximately every three weeks (ansible-4.1.0, ansible-4.2.0, etc).
They will contain bugfixes and new features but no backwards
incompatibilities.

* At the moment, the plan is for updates to ansible-3 to stop once
ansible-4.0.0 final is released.
  *  We've been putting together a document on issues that would need
to be addressed if someone would like to volunteer to create long term
updates to Ansible-3: https://hackmd.io/plQlGzcFRFGLnPXIeg3cwQ


Porting Help
-

There is a unified porting guide for collections which have opted-in
available here:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html

-Toshio

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaTZ-vWrqFXOZfrxsab-F%3DrdwZhL4pe2uJcxPkq5FsRJ%2BQ%40mail.gmail.com.

[ansible-project] FYI: Reminder about ansible 3 & 4 release dates

2021-05-04 Thread Toshio Kuratomi

Just a brief reminder about the Ansible 3 and 4 schedule:

* The last Ansible 3 release is planned for May 11, 2021
* Ansible 4.0.0 release candidate 1 is also planned for May 11, 2021
* If there are no blocker bugs discovered, Ansible 4.0.0 final will be
made on May 18, 2021

-Toshio

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

[ansible-project] Ansible 4.0.0 beta1 release

2021-04-29 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the Ansible-4.0.0 beta1 package is now
available! This update is based on the Ansible-core-2.11.x package
which is a major update from the Ansible-3 package (Ansible-3 was
based on Ansible-base-2.10.x). There may be backwards
incompatibilities in the core playbook language.  Please see the
porting guide for details.


How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
earlier), you need to uninstall ansible before installing the 3.0.0
version.  It is also recommended to uninstall ansible-base before
upgrading:

```
$ pip uninstall ansible ansible-base
$ pip install ansible==4.0.0b1 --user
```

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

* Ansible 4.0.0b1:
https://pypi.python.org/packages/source/a/ansible/ansible-4.0.0b1.tar.gz
  SHA256: 81a183469d90c86c69531b735be77b034a8ba1f8628acb7d7c8fdb1ec8e790d8

What's new in Ansible 4.0.0
---

* This version of Ansible is based on ansible-core-2.11.x which is a
new major update of the ansible-core package.  It may contain
backwards incompatible changes to the playbook language and command
line programs.
  * We maintain a porting guide which will continue to be updated as
we move closer to the ansible-4.0.0 final release:
  * https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html

* We've added a way to get the version of the ansible package that is
installed programmatically::

 $ python -c 'from ansible_collections.ansible_release import
ansible_version; print(ansible_version)'
 4.0.0b1

* Collections which have opted into being a part of the Ansible-4.0.0
unified changelog will have an entry on this page:
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/CHANGELOG-v4.rst

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/4/ansible-4.0.0b1.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-core-2.11 which this release of ansible
installs: 
https://github.com/ansible/ansible/blob/stable-2.11/changelogs/CHANGELOG-v2.11.rst


What's the schedule for new Ansible releases after 4.0.0b1?
---

* Please see the ansible roadmap for the full release schedule for
ansible-4.0.0: https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_4.html

* Unless a blocker bug is found, ansible-4.0.0 final is scheduled for 5-18-2021

* Once ansible-4.0.0 is released, new minor releases will occur
approximately every three weeks (ansible-4.1.0, ansible-4.2.0, etc).
They will contain bugfixes and new features but no backwards
incompatibilities.

* At the moment, the plan is for updates to ansible-3 to stop once
ansible-4.0.0 final is released.
  *  We've been putting together a document on issues that would need
to be addressed if someone would like to volunteer to create long term
updates to Ansible-3: https://hackmd.io/plQlGzcFRFGLnPXIeg3cwQ


Porting Help
-

A unified porting guide for collections which have opted-in is being
worked on: 
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaStaTORZiM8FkgOFUmWpibNTOnURt%2BKB1okTc%2B5Y075Og%40mail.gmail.com.

[ansible-project] Ansible3.3.0

2021-04-22 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-3.3.0 package was released on
April 20! The update contains bugfixes and new, backwards compatible
features in the contained collections.

If you would like to learn about how and why we got to version 3.0.0,
we invite you to visit our blog for the background as well as a Q:

- https://www.ansible.com/blog/announcing-the-community-ansible-3.0.0-package
- https://www.ansible.com/blog/ansible-3.0.0-qa

How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
earlier), you need to uninstall ansible before installing the 3.x
version:

```
$ pip uninstall ansible
$ pip install ansible==3.3.0 --user
```

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

* Ansible 3.3.0
https://pypi.python.org/packages/source/a/ansible/ansible-3.3.0.tar.gz
SHA256: 2de5385c48a2a24a19f6cbaccc7d7684c64b6194f9a9b175aba7949d53b07bc9

What's new in Ansible 3.3.0
---

* The Ansible package has moved to semantic versioning
(https://semver.org/). This standard allows you to tell if a new
version of Ansible contains incompatibilities by looking at the
version number. We've moved from 3.2.0 to 3.3.0 to show that this
release should be backwards compatible with Ansible-3.2.0 but may
contain new features. Read the semver specification for more
information.

* Collections which have opted into being a part of the Ansible-3
unified changelog will have an entry on this page:
*
https://github.com/ansible-community/ansible-build-data/blob/main/3/CHANGELOG-v3.rst#v3-3-0

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.
*
https://github.com/ansible-community/ansible-build-data/blob/main/3/ansible-3.3.0.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-3.3.0.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.10.8 which this release of ansible
installs:
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst

What's the schedule for new Ansible releases after 3.3.0?
-

* Minor releases of ansible-3 will be released approximately every
three weeks. Since we're now using semantic versioning, these new
releases will be 3.1.0, 3.2.0, etc. They will contain bugfixes and
new features but no backwards incompatibilities.
* Expect 3.4.0 around April 11.

Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_3.html

-Toshio

--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSpc31cOzdW%2BCHxUZQHVF8B14cN72i87Nav0i19eky%2BOg%40mail.gmail.com.

[ansible-project] Ansible-3.2.0 released

2021-03-30 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-3.2.0 package is now
available! This update contains bugfixes and new, backwards compatible
features in the contained collections.

If you would like to learn about how and why we got to version 3.0.0,
we invite you to visit our blog for the background as well as a Q:

- https://www.ansible.com/blog/announcing-the-community-ansible-3.0.0-package
- https://www.ansible.com/blog/ansible-3.0.0-qa

How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
earlier), you need to uninstall ansible before installing the 3.x
version:

```
$ pip uninstall ansible
$ pip install ansible==3.2.0 --user
```

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

* Ansible 3.2.0
https://pypi.python.org/packages/source/a/ansible/ansible-3.2.0.tar.gz
SHA256: 01774d8b4778844f29920812f0dab7a90c8643e8f826460a941565b2620e5b7d

What's new in Ansible 3.2.0
---

* The Ansible package has moved to semantic versioning
(https://semver.org/). This standard allows you to tell if a new
version of Ansible contains incompatibilities by looking at the
version number. We've moved from 3.1.0 to 3.2.0 to show that this
release should be backwards compatible with Ansible-3.1.0 but may
contain new features. Read the semver specification for more
information.

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-3.2.0.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.10.7 which this release of ansible
installs:
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst

What's the schedule for new Ansible releases after 3.2.0?
-

Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_3.html

-Toshio

--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSVp%3D4Xg-3K8R2TjTifFvajcGhTrBXrJaKZJpGFBxnpug%40mail.gmail.com.

[ansible-project] Ansible-3.1.0 release and ansible-4.0 alpha1 delay

2021-03-11 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-3.1.0 package is now
available! This update contains bugfixes and new, backwards compatible
features in the contained collections.

If you would like to learn about how and why we got to version 3.0.0,
we invite you to visit our blog for the background as well as a Q:

- https://www.ansible.com/blog/announcing-the-community-ansible-3.0.0-package
- https://www.ansible.com/blog/ansible-3.0.0-qa

How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
earlier), you need to uninstall ansible before installing the 3.x
version:

```
$ pip uninstall ansible
$ pip install ansible==3.1.0 --user
```

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

* Ansible 3.1.0
https://pypi.python.org/packages/source/a/ansible/ansible-3.1.0.tar.gz
SHA256: 8a8faab85161f2e6d173d9e0885b1c3ab43fedf419691122e1547fb65eb982d1

What's new in Ansible 3.1.0
---

* The Ansible package has moved to semantic versioning
(https://semver.org/). This standard allows you to tell if a new
version of Ansible contains incompatibilities by looking at the
version number. We've moved from 3.0.0 to 3.1.0 to show that this
release should be backwards compatible with Ansible-3.0.0 but may
contain new features. Read the semver specification for more
information.

* This release catches the ansible-3.x series up with the collection
versions in the last ansible-2.10.x release, ansible-2.10.7. The
collections in this release should all be the same version or newer
than what was in 2.10.7.

* Collections which have opted into being a part of the Ansible-3.1.0
unified changelog will have an entry on this page:
*
https://github.com/ansible-community/ansible-build-data/blob/main/3/CHANGELOG-v3.rst#v3-1-0

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-3.1.0.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.10.6 which this release of ansible
installs:
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst

What's the schedule for new Ansible releases after 3.1.0?
-

* We're currently planning to release Ansible-4.0.0 in the middle of
May, roughly a month after Ansible-core-2.11 releases. See the
Ansible 4 Roadmap for details:
https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_4.html
* We're having to rework some of our release tools due to the rename
of the ansible-base package to ansible-core so ansible-4.0.0alpha1 has
been delayed. We hope to have it released next week.

Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst

--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSYXXVk2s_to%3Dj%3DcPmdEL4Yqfy5499gM%3DZmLQsiizLt5g%40mail.gmail.com.

[ansible-project] Ansible-3.0.0 released

2021-02-18 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-3.0.0 package is now
available! This update is based on the ansible-base-2.10.x package
just like ansible-2.10 was so the changes shouldn't be too major.
However, it does contain new major versions of many collections which
means that there will be some backwards incompatible changes in the
modules and plugins.

If you would like to learn about how and why we got to version 3.0.0,
we invite you to visit our blog for the background as well as a Q:

- https://www.ansible.com/blog/announcing-the-community-ansible-3.0.0-package
- https://www.ansible.com/blog/ansible-3.0.0-qa

How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
earlier), you need to uninstall ansible before installing the 3.0.0
version:

```
$ pip uninstall ansible
$ pip install ansible==3.0.0 --user
```

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

* Ansible 3.0.0:
https://pypi.python.org/packages/source/a/ansible/ansible-3.0.0.tar.gz
  SHA256: 843aa807813318b0c8a6684a2895c74a4ccfb3c01d2bb41a53856b2434ebaaec

What's new in Ansible 3.0.0
---

* The Ansible package has moved to semantic versioning
(https://semver.org/). This standard allows you to tell if a new
version of Ansible contains incompatibilities by looking at the
version number. Read the semver specification for more information.

* The `cisco.nxos`, `community.crypto`, `community.docker`,
`community.general`, `community.network`, and `community.sops`
collections had multiple modules updated to specify that the
parameters should not be logged as they could contain secret
information. Collectively, these problems are listed in the Common
Vulnerabilities database as CVE-2021-20191, CVE-2020-25646,
CVE-2021-20180, and CVE-2021-20178

* Collections which have opted into being a part of the Ansible-3.0.0
unified changelog will have an entry on this page:
https://github.com/ansible-community/ansible-build-data/blob/main/3/CHANGELOG-v3.rst

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/3/ansible-3.0.0.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-3.0.0.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.10.5 which this release of ansible
installs: 
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst

What's the schedule for new Ansible releases after 3.0.0?
-

* Except for ansible-2.9.x, older versions of ansible are not seeing
maintenance releases.  If there is a desire for maintenance releases
of older versions, drop by a Community Working Group Meeting to
discuss how you can help. (
https://github.com/ansible/community/tree/main/meetings#wednesdays )

* Minor releases of ansible-3.0.0 will be released approximately every
three weeks.  Since we're now using semantic versioning, these new
releases will be 3.1.0, 3.2.0, etc.  They will contain bugfixes and
new features but no backwards incompatibilities.

* We're currently planning to release Ansible-4.0.0 in the middle of
May, roughly a month after Ansible-core-2.11 releases.  See the
Ansible 4 Roadmap for details:
https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_4.html

Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_3.rst


Thanks!
-Toshio

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQqyV%3DS0cTibL1feFfSxWtxBO_n8TOFHs_MmT1gj%3DrvnQ%40mail.gmail.com.

[ansible-project] Re: Ansible-3.0.0 release candidate 1

2021-02-11 Thread Toshio Kuratomi

Hi all,

Just a brief update on the Ansible-3.0.0 release schedule.  We've been
getting feedback that the switch to semantic versioning of the Ansible
package is confusing to people so we're putting together some
information on that to go out with the release. This might take a few
extra days so at yesterday's Community IRC meeting we voted to allow a
slip to Thursday, February, 18th if we needed it.

I just didn't want anyone to be surprised if Ansible-3.0.0 shows up a
few days late!

Thanks,
-Toshio

On Tue, Feb 9, 2021 at 3:59 PM Toshio Kuratomi  wrote:
>
> Hi all,
>
> We're happy to announce that the ansible-3.0.0 release candidate 1
> package is now available for testing! This update is based on the
> ansible-base-2.10.x package just like ansible-2.10 was so the changes
> shouldn't be too major.  However, it does contain new major versions
> of many collections which means that there will be some backwards
> incompatible changes in the modules and plugins.
>
> How to get it
> -
>
> Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
> earlier), you need to uninstall ansible before installing the 3.0.0rc1
> version:
>
> ```
> $ pip uninstall ansible
> $ pip install ansible==3.0.0rc1 --user
> ```
>
> The tar.gz of the release can be found here:
>
> * Ansible 3.0.0rc1
> https://pypi.python.org/packages/source/a/ansible/ansible-3.0.0rc1.tar.gz
> SHA256: a15dabde2d433766bbeede1435ec1bca7b7a44619b919ddb4e6f8a186053eb43
>
> What's new in Ansible 3.0.0rc1
> --
>
> * The Ansible package has moved to semantic versioning
> (https://semver.org/).  This standard allows you to tell if a new
> version of Ansible contains incompatibilities by looking at the
> version number. Read the semver specification for more information.
>
> * The `cisco.nxos`, `community.crypto`, `community.docker`,
> `community.general`, `community.network`, and `community.sops`
> collections had multiple modules updated to specify that the
> parameters should not be logged as they could contain secret
> information. Collectively, these problems are listed in the Common
> Vulnerabilities database as CVE-2021-20191, CVE-2020-25646,
> CVE-2021-20180, and CVE-2021-20178
>
> * Collections which have opted into being a part of the
> Ansible-3.0.0rc1 unified changelog will have an entry on this page:
> https://github.com/ansible-community/ansible-build-data/blob/main/3/CHANGELOG-v3.rst
>
> * For collections which have not opted into the unified changelog,
> consult the list of included collections in the link below and check
> their entry on https://galaxy.ansible.com for information about their
> changes.
>   * 
> https://github.com/ansible-community/ansible-build-data/blob/main/3/ansible-3.0.0rc1.deps
>
> * You can find more information for those on
> https://galaxy.ansible.com/. For instance, the community.crypto
> collection listed in the ansible-3.0.0rc1.deps file has a galaxy page
> at https://galaxy.ansible.com/community/crypto/
>
> * Changelog for ansible-base-2.10.5 which this release of ansible
> installs: 
> https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst
>
> What's the schedule for new Ansible releases after 3.0.0rc1?
> ---
>
> * Except for ansible-2.9.x, older versions of ansible are not seeing
> maintenance releases.  If there is a desire for maintenance releases
> of older versions, drop by a Community Working Group Meeting to
> discuss how you can help. (
> https://github.com/ansible/community/tree/main/meetings#wednesdays )
>
> * Since we have not updated the ansible-base major version in this
> release, we decided that a quick release schedule was preferred. If no
> blockers are discovered, Ansible-3.0.0 final will happen on February
> 16, 2021.
>
> * Minor releases of ansible-3.0.0 will be released approximately every
> three weeks.  Since we're now using semantic versioning, these new
> releases will be 3.1.0, 3.2.0, etc.  They will contain bugfixes and
> new features but no backwards incompatibilities.
>
>
> Porting Help
> -
>
> There's a unified porting guide for collections which have opted-in.
> You can find that at:
> https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_3.rst
>
>
> Thanks for testing!
> -Toshio Kuratomi

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

[ansible-project] Ansible-3.0.0 release candidate 1

2021-02-09 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-3.0.0 release candidate 1
package is now available for testing! This update is based on the
ansible-base-2.10.x package just like ansible-2.10 was so the changes
shouldn't be too major. However, it does contain new major versions
of many collections which means that there will be some backwards
incompatible changes in the modules and plugins.

How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
earlier), you need to uninstall ansible before installing the 3.0.0rc1
version:

```
$ pip uninstall ansible
$ pip install ansible==3.0.0rc1 --user
```

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

* Ansible 3.0.0rc1
https://pypi.python.org/packages/source/a/ansible/ansible-3.0.0rc1.tar.gz
SHA256: a15dabde2d433766bbeede1435ec1bca7b7a44619b919ddb4e6f8a186053eb43

What's new in Ansible 3.0.0rc1
--

* The `cisco.nxos`, `community.crypto`, `community.docker`,
`community.general`, `community.network`, and `community.sops`
collections had multiple modules updated to specify that the
parameters should not be logged as they could contain secret
information. Collectively, these problems are listed in the Common
Vulnerabilities database as CVE-2021-20191, CVE-2020-25646,
CVE-2021-20180, and CVE-2021-20178

* Collections which have opted into being a part of the
Ansible-3.0.0rc1 unified changelog will have an entry on this page:
https://github.com/ansible-community/ansible-build-data/blob/main/3/CHANGELOG-v3.rst

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-3.0.0rc1.deps file has a galaxy page
at https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.10.5 which this release of ansible
installs:
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst

What's the schedule for new Ansible releases after 3.0.0rc1?
---

* Since we have not updated the ansible-base major version in this
release, we decided that a quick release schedule was preferred. If no
blockers are discovered, Ansible-3.0.0 final will happen on February
16, 2021.

* Minor releases of ansible-3.0.0 will be released approximately every
three weeks. Since we're now using semantic versioning, these new
releases will be 3.1.0, 3.2.0, etc. They will contain bugfixes and
new features but no backwards incompatibilities.

Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_3.rst

Thanks for testing!
-Toshio Kuratomi

--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQV1F7u_EcL08eqsvhyofgxUFquXr4NzyqsOBatC-7F%2Bg%40mail.gmail.com.

[ansible-project] Re: Ansible-2.10.7 released.

2021-02-09 Thread Toshio Kuratomi

Small correction.  The pip install instructions should read:

$ pip uninstall ansible
$ pip install ansible==2.10.7 --user


Thanks!
-Toshio

On Tue, Feb 9, 2021 at 1:28 PM Toshio Kuratomi  wrote:
>
> Hi all,
>
> We're happy to announce that the ansible-2.10.7 package is now
> available! This update contains bugfixes and new, backwards compatible
> features in the contained collections.
>
> Ansible-2.10.x is a big change in how the Ansible package is built so
> if you missed out on all the changes that have gone into the
> ansible-2.10.x packages, please read the announcement for
> ansible-2.10.0:
> https://groups.google.com/g/ansible-announce/c/QxIOml3i62A
>
> How to get it
> -
>
> Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
> earlier), you need to uninstall ansible before installing the 2.10
> version:
>
> ```
> $ pip uninstall ansible
> $ pip install ansible==2.10.6 --user
> ```
>
> The tar.gz of the release can be found here:
>
> * Ansible 2.10.6
> https://pypi.python.org/packages/source/a/ansible/ansible-2.10.7.tar.gz
> SHA256: 9ff024500116d53c460cb09ea92e3c9404119f100d1d1ff0de69a9dafca561d5
>
> What's new in Ansible 2.10.7
> 
>
> We had planned on Ansible-2.10.6 being the last release in the
> ansible-2.10.x series but decided that one more release was
> appropriate to fix a few important issues.
>
> * The community.docker, community.general, and community.network
> collections had multiple modules updated to specify that the
> parameters should not be logged as they could contain secret
> information. Collectively, these problems are listed in the Common
> Vulnerabilities database as CVE-2021-20191.
>
> * The community.general.utm_proxy_auth_profile module has had the
> frontend_cookie_secret return value replaced with a placeholder value
> as known secret values should not be returned from modules.
>
> * The community.okd collection was downgraded from version 1.0.1 to
> version 1.0.0.  This was done because 1.0.1 depends on kubernetes.core
> which was not shipped in ansible-2.10.x.  community.okd-1.0.0 is the
> same code but with a dependency on community.kubernetes (which is
> included in ansible-2.10.7) instead.  The intention for Ansible-3.x is
> to include both kubernetes.core and newer versions of community.okd.
>
> * Collections which have opted into being a part of the Ansible-2.10.7
> unified changelog will have an entry on this page:
>   * 
> https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst#v2-10-7
>
> * For collections which have not opted into the unified changelog,
> consult the list of included collections in the link below and check
> their entry on https://galaxy.ansible.com for information about their
> changes.
>   * 
> https://github.com/ansible-community/ansible-build-data/blob/main/2.10/ansible-2.10.7.deps
>
> * You can find more information for those on
> https://galaxy.ansible.com/. For instance, the community.crypto
> collection listed in the ansible-2.10.6.deps file has a galaxy page at
> https://galaxy.ansible.com/community/crypto/
>
> * Changelog for ansible-base-2.10.5 which this release of ansible
> installs: 
> https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst
>
> What's the schedule for new Ansible releases after 2.10.7?
> --
>
> * We expect Ansible-2.10.7 to be the last 2.10.x release.
> Ansible-3.0.0rc1 is due out later today.  If no blockers are found,
> Ansible-3.0.0 final will be released next week.  If there is a desire
> for further maintenance releases of the 2.10.x version, drop by a
> Community Working Group Meeting to discuss how you can help. (
> https://github.com/ansible/community/tree/main/meetings#wednesdays )
>
> * The next major release of Ansible (3.0.0) is scheduled for February
> 16, 2021. This release will still be based on ansible-base-2.10 but
> will contain potential incompatible changes to the included
> collections.
>
> * We are adopting semantic versioning in that version, so it will be
> Ansible-3.0.0 rather than Ansible-2.11.0.
>
> * Patch releases will continue to be released approximately every
> three weeks with bugfixes and new features as long as those features
> do not cause incompatibilities.
>
> Porting Help
> -
>
> There's a unified porting guide for collections which have opted-in.
> You can find that at:
> https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst

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

[ansible-project] Ansible-2.10.7 released.

2021-02-09 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-2.10.7 package is now
available! This update contains bugfixes and new, backwards compatible
features in the contained collections.

Ansible-2.10.x is a big change in how the Ansible package is built so
if you missed out on all the changes that have gone into the
ansible-2.10.x packages, please read the announcement for
ansible-2.10.0:
https://groups.google.com/g/ansible-announce/c/QxIOml3i62A

How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
earlier), you need to uninstall ansible before installing the 2.10
version:

```
$ pip uninstall ansible
$ pip install ansible==2.10.6 --user
```

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

* Ansible 2.10.6
https://pypi.python.org/packages/source/a/ansible/ansible-2.10.7.tar.gz
SHA256: 9ff024500116d53c460cb09ea92e3c9404119f100d1d1ff0de69a9dafca561d5

What's new in Ansible 2.10.7

We had planned on Ansible-2.10.6 being the last release in the
ansible-2.10.x series but decided that one more release was
appropriate to fix a few important issues.

* The community.docker, community.general, and community.network
collections had multiple modules updated to specify that the
parameters should not be logged as they could contain secret
information. Collectively, these problems are listed in the Common
Vulnerabilities database as CVE-2021-20191.

* The community.general.utm_proxy_auth_profile module has had the
frontend_cookie_secret return value replaced with a placeholder value
as known secret values should not be returned from modules.

* The community.okd collection was downgraded from version 1.0.1 to
version 1.0.0. This was done because 1.0.1 depends on kubernetes.core
which was not shipped in ansible-2.10.x. community.okd-1.0.0 is the
same code but with a dependency on community.kubernetes (which is
included in ansible-2.10.7) instead. The intention for Ansible-3.x is
to include both kubernetes.core and newer versions of community.okd.

* Collections which have opted into being a part of the Ansible-2.10.7
unified changelog will have an entry on this page:
*
https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst#v2-10-7

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-2.10.6.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.10.5 which this release of ansible
installs:
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst

What's the schedule for new Ansible releases after 2.10.7?
--

* We expect Ansible-2.10.7 to be the last 2.10.x release.
Ansible-3.0.0rc1 is due out later today. If no blockers are found,
Ansible-3.0.0 final will be released next week. If there is a desire
for further maintenance releases of the 2.10.x version, drop by a
Community Working Group Meeting to discuss how you can help. (
https://github.com/ansible/community/tree/main/meetings#wednesdays )

* The next major release of Ansible (3.0.0) is scheduled for February
16, 2021. This release will still be based on ansible-base-2.10 but
will contain potential incompatible changes to the included
collections.

* We are adopting semantic versioning in that version, so it will be
Ansible-3.0.0 rather than Ansible-2.11.0.

* Patch releases will continue to be released approximately every
three weeks with bugfixes and new features as long as those features
do not cause incompatibilities.

Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst

--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQCb30v%3De7DMTHYRDbCvtYQ842oJ5zZ-LZXhq9hpKEayA%40mail.gmail.com.

[ansible-project] Ansible-3.0.0 beta1 released

2021-02-02 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-3.0.0 beta1 package is now
available! This update is based on the ansible-base-2.10.x package
just like ansible-2.10 was so the changes shouldn't be too major.
However, it does contain new major versions of many collections which
means that there will be some backwards incompatible changes in the
modules and plugins.

How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
earlier), you need to uninstall ansible before installing the 3.0.0b1
version:

```
$ pip uninstall ansible
$ pip install ansible==3.0.0b1 --user
```

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

* Ansible 3.0.0b1
https://pypi.python.org/packages/source/a/ansible/ansible-3.0.0b1.tar.gz
SHA256: 1da8059604136e520cd4f6e0792309dbf6ef79b927e6c41afc194fb418b23855

What's new in Ansible 3.0.0b1
-

* Collections which have opted into being a part of the
Ansible-3.0.0b1 unified changelog will have an entry on this page:
https://github.com/ansible-community/ansible-build-data/blob/main/3/CHANGELOG-v3.rst

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-3.0.0b1.deps file has a galaxy page
at https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.10.6 which this release of ansible
installs:
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst

What's the schedule for new Ansible releases after 3.0.0b1?
---

* Except for ansible-2.9.x, older versions of ansible are not seeing
maintenance releases. If there is a desire for maintenance releases
of older versions, drop by a Community Working Group Meeting to
discuss how you can help. (
https://github.com/ansible/community/tree/main/meetings#wednesdays )
* Since we have not updated the ansible-base major version in this
release, we decided that a quick release schedule was preferred. There
will be one release candidate, on February 9. If no blockers are
discovered, Ansible-3.0.0 final will happen on February 16, 2021.
* Minor releases of ansible-3.0.0 will be released approximately every
three weeks. Since we're now using semantic versioning, these new
releases will be 3.1.0, 3.2.0, etc. They will contain bugfixes and
new features but no backwards incompatibilities.

Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_3.rst

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

[ansible-project] Ansible-2.10.6 has been released

2021-01-26 Thread Toshio Kuratomi

Hi all,

We're happy to announce that the ansible-2.10.6 package is now
available! This update contains bugfixes and new, backwards compatible
features in the contained collections.

Ansible-2.10.x is a big change in how the Ansible package is built so
if you missed out on all the changes that have gone into the
ansible-2.10.x packages, please read the announcement for
ansible-2.10.0:
https://groups.google.com/g/ansible-announce/c/QxIOml3i62A

How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
earlier), you need to uninstall ansible before installing the 2.10
version:

```
$ pip uninstall ansible
$ pip install ansible==2.10.6 --user
```

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

* Ansible 2.10.6
https://pypi.python.org/packages/source/a/ansible/ansible-2.10.6.tar.gz
SHA256: ae97002e4fb1ed3de947428ff43906c76c66751fe104721cf6b25fa115dbbe8d

What's new in Ansible 2.10.6


* This release includes the community.fortios Ansible collection which
originates from modules and plugins migrated from the
community.general collection. These plugins will continue to work from
their old location but aren't expected to be maintained beyond
Ansible-3.0.0. Please use the new location for the latest updates and
features, for example: community.general.fmgr_query ->
community.fortios.fmgr_query

* This release fixes two potential disclosure of information
(CVE-2021-20178 and CVE-2021-20180) in the
`community.general.bitbucket_pipeline_variable` and
`community.general.snmp_facts` modules. Please see the unified
changelog for more information.

* Collections which have opted into being a part of the Ansible-2.10.6
unified changelog will have an entry on this page:
https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst#v2-10-6

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.
  * 
https://github.com/ansible-community/ansible-build-data/blob/main/2.10/ansible-2.10.6.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-2.10.6.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.10.5 which this release of ansible
installs: 
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst

What's the schedule for new Ansible releases after 2.10.6?
--

* We expect Ansible-2.10.6 to be the last 2.10.x release. Further
releases will be of Ansible-3.0.x. If there is a desire for
maintenance releases of older versions, drop by a Community Working
Group Meeting to discuss how you can help. (
https://github.com/ansible/community/tree/main/meetings#wednesdays )
* The next major release of Ansible (3.0.0) is scheduled for February
16, 2021. This release will still be based on ansible-base-2.10 but
will contain potential incompatible changes to the included
collections.
* We are adopting semantic versioning in that version, so it will be
Ansible-3.0.0 rather than Ansible-2.11.0.
* Patch releases will continue to be released approximately every
three weeks with bugfixes and new features as long as those features
do not cause incompatibilities.

Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSoVsreMCNfbmoFtsZx49Ld5WPUYsG-4ROb%3DBmS1vgBSg%40mail.gmail.com.

[ansible-project] Ansible-2.10.3 released: quick fix for installation issue

2020-11-04 Thread Toshio Kuratomi

Greetings all,

Yesterday's release of Ansible-2.10.2 contained some output from
running tests which amounted to a 30% increase in the size of the
Ansible tarball.  The size ended up doubling the time necessary to
install ansible using pip.  The Ansible-2.10.3 release removes the
test output to bring the size back down to a more normal level.  Other
than that, it should be the same as the 2.10.2 release.

If you've already upgraded to 2.10.2, the only benefit of 2.10.3 will
be a smaller installed size.


How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
earlier), you need to uninstall ansible before installing the 2.10 version:

$ pip uninstall ansible
$ pip install ansible==2.10.3 --user

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

* Ansible 2.10.3
https://pypi.python.org/packages/source/a/ansible/ansible-2.10.3.tar.gz
SHA256: eb1d08b9b98a60e90e7123a12f40770780f29f9d73168da55d449106a9f4d348


What's new in Ansible 2.10.3
--

* Collections which have opted into being a part of the Ansible-2.10
unified changelog will have an entry on this page:
https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.

* List of collections included in the 2.10.3 release:
https://github.com/ansible-community/ansible-build-data/blob/2.10.3/2.10/ansible-2.10.3.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-2.10.3.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.10.3 which this release of ansible
installs: 
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst


What's the schedule for new Ansible releases after 2.10.0?
---

* Patch releases will continue to be released approximately every
three weeks with bugfixes and new features as long as those features
do not cause incompatibilities.
* These releases will all be based on ansible-base-2.10.x
* However, the US Thanksgiving Holiday is happening three weeks from
now so expect the next release one week later, around December 1st.

* We're still discussing the release schedule for ansible-2.11.0.
* We're tentatively thinking of releasing ansible-2.11.0, with
potential backwards incompatible changes to the collections but based
on ansible-base-2.10 in early February, 2021.
* Take this information as being subject to change as we're in the
early stages of discussion.


Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst


Thanks!
-Toshio Kuratomi

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

[ansible-project] Re: Ansible-2.10.2 has been released

2020-11-03 Thread Toshio Kuratomi

I forgot to change the checksums and URL for the tarballs.  The proper
sha256sum and URL is:

* Ansible 2.10.2
  URL: https://pypi.python.org/packages/source/a/ansible/ansible-2.10.2.tar.gz
  SHA256SUM: 396ff188c7c1a2bb2e4be78d8a2f87e729c32c34946afbee04c09b68fbd8c2d0

-Toshio

On Tue, Nov 3, 2020 at 4:42 PM Toshio Kuratomi  wrote:
>
> Hi all-
>
> We're happy to announce that the ansible-2.10.2 package is now
> available! This update contains bugfixes and new, backwards
> compatible features in the contained collections as well as bringing
> in ansible-base-2.10.3 as a dependency.
>
> Ansible-2.10.x is a big change in how the Ansible package is built so
> If you missed out on all the changes that have gone into the
> ansible-2.10.x packages, please read the announcement for
> ansible-2.10.0:
> https://groups.google.com/g/ansible-announce/c/QxIOml3i62A
>
>
> How to get it
> -
>
> Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
> earlier), you need to uninstall ansible before installing the 2.10 version:
>
> $ pip uninstall ansible
> $ pip install ansible==2.10.2 --user
>
> The tar.gz of the release can be found here:
>
> * Ansible 2.10.1
> https://pypi.python.org/packages/source/a/ansible/ansible-2.10.1.tar.gz
> SHA256: 75708c67e2ac926cea42856af72cbc9494bf8008197652f9609089f7b4c2515a
>
>
>
> What's new in Ansible 2.10.1
> --
>
> * Collections which have opted into being a part of the Ansible-2.10.0
> unified changelog will have an entry on this page:
> https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst
>
> * For collections which have not opted into the unified changelog,
> consult the list of included collections in the link below and check
> their entry on https://galaxy.ansible.com for information about their
> changes.
>
> * List of collections included in the 2.10.2 release:
> https://github.com/ansible-community/ansible-build-data/blob/2.10.2/2.10/ansible-2.10.2.deps
>
> * You can find more information for those on
> https://galaxy.ansible.com/. For instance, the community.crypto
> collection listed in the ansible-2.10.2.deps file has a galaxy page at
> https://galaxy.ansible.com/community/crypto/
>
> * Changelog for ansible-base-2.10.2 which this release of ansible
> installs: 
> https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst
>
>
> What's the schedule for new Ansible releases after 2.10.0?
> ---
>
> * Patch releases will continue to be released approximately every
> three weeks with bugfixes and new features as long as those features
> do not cause incompatibilities.
> * These releases will all be based on ansible-base-2.10.x
> * However, the US Thanksgiving Holiday is happening three weeks from
> now so expect the next release one week later, around December 1st.
>
> * We're still discussing the release schedule for ansible-2.11.0.
> * We're tentatively thinking of releasing ansible-2.11.0, with
> potential backwards incompatible changes to the collections but based
> on ansible-base-2.10 in early February, 2021.
> * Take this information as being subject to change as we're in the
> early stages of discussion.
>
>
> Porting Help
> -----
>
> There's a unified porting guide for collections which have opted-in.
> You can find that at:
> https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst
>
>
> Thanks!
> -Toshio Kuratomi

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQ2s0wVc%3DQcE3w2Y%3DqBmwDEsOQjjt3BvD9LtvQaX5c9jA%40mail.gmail.com.

[ansible-project] Ansible-2.10.2 has been released

2020-11-03 Thread Toshio Kuratomi

Hi all-

We're happy to announce that the ansible-2.10.2 package is now
available! This update contains bugfixes and new, backwards
compatible features in the contained collections as well as bringing
in ansible-base-2.10.3 as a dependency.

Ansible-2.10.x is a big change in how the Ansible package is built so
If you missed out on all the changes that have gone into the
ansible-2.10.x packages, please read the announcement for
ansible-2.10.0:
https://groups.google.com/g/ansible-announce/c/QxIOml3i62A


How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
earlier), you need to uninstall ansible before installing the 2.10 version:

$ pip uninstall ansible
$ pip install ansible==2.10.2 --user

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

* Ansible 2.10.1
https://pypi.python.org/packages/source/a/ansible/ansible-2.10.1.tar.gz
SHA256: 75708c67e2ac926cea42856af72cbc9494bf8008197652f9609089f7b4c2515a



What's new in Ansible 2.10.1
--

* Collections which have opted into being a part of the Ansible-2.10.0
unified changelog will have an entry on this page:
https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.

* List of collections included in the 2.10.2 release:
https://github.com/ansible-community/ansible-build-data/blob/2.10.2/2.10/ansible-2.10.2.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-2.10.2.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.10.2 which this release of ansible
installs: 
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst


What's the schedule for new Ansible releases after 2.10.0?
---

* Patch releases will continue to be released approximately every
three weeks with bugfixes and new features as long as those features
do not cause incompatibilities.
* These releases will all be based on ansible-base-2.10.x
* However, the US Thanksgiving Holiday is happening three weeks from
now so expect the next release one week later, around December 1st.

* We're still discussing the release schedule for ansible-2.11.0.
* We're tentatively thinking of releasing ansible-2.11.0, with
potential backwards incompatible changes to the collections but based
on ansible-base-2.10 in early February, 2021.
* Take this information as being subject to change as we're in the
early stages of discussion.


Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst


Thanks!
-Toshio Kuratomi

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaS%3D5%2BvR6seS_US6FaeDGOjd7%3DJ5cJ4jfT0Zdf%2Bg2VJNuA%40mail.gmail.com.

[ansible-project] Ansible-2.10.1 has been released

2020-10-13 Thread Toshio Kuratomi

Hi all-

**Important:** If you are upgrading from Ansible 2.9.x or older,
please see the `How to get it` section for an important limitation.

We're happy to announce that the ansible-2.10.1 package is now
available!  This update contains bugfixes and new, backwards
compatible features in the contained collections as well as bringing
in ansible-base-2.10.2 as a dependency.

This is the first minor release of the ansible-2.10 package.  If you
missed out on all the changes that have gone into the ansible-2.10.x
packages, please read the announcement for ansible-2.10.0:
https://groups.google.com/g/ansible-announce/c/QxIOml3i62A


How to get it
-

Due to a limitation in pip, if you are upgrading from Ansible 2.9 (or
earlier), you need to uninstall ansible before installing the 2.10 version:

$ pip uninstall ansible
$ pip install ansible==2.10.1 --user

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

* Ansible 2.10.1
https://pypi.python.org/packages/source/a/ansible/ansible-2.10.1.tar.gz
SHA256: 75708c67e2ac926cea42856af72cbc9494bf8008197652f9609089f7b4c2515a



What's new in Ansible 2.10.1
--

* Collections which have opted into being a part of the Ansible-2.10.0
unified changelog will have an entry on this page:
https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst

* This release fixes a potential disclosure of information
(CVE-2020-25646) in several community.crypto modules.  Please see the
unified changelog for more information.

* For collections which have not opted into the unified changelog,
consult the list of included collections in the link below and check
their entry on https://galaxy.ansible.com for information about their
changes.

* List of collections included in the 2.10.1 release:
https://github.com/ansible-community/ansible-build-data/blob/2.10.1/2.10/ansible-2.10.1.deps

* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-2.10.1.deps file has a galaxy page at
https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.10.2 which this release of ansible
installs: 
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst


What's the schedule for new Ansible releases after 2.10.0?
---

* Patch releases will continue to be released approximately every
three weeks with bugfixes and new features as long as those features
do not cause incompatibilities.
* These releases will all be based on ansible-base-2.10.x
* Expect ansible-2.10.2 around November 3.

* We're still discussing the release schedule for ansible-2.11.0.
* We're tentatively thinking of releasing ansible-2.11.0, with
potential backwards incompatible changes to the collections but based
on ansible-base-2.10 in early February, 2021.
* Take this information as being subject to change as we're in the
early stages of discussion.


Porting Help
-

There's a unified porting guide for collections which have opted-in.
You can find that at:
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst


Thanks!
-Toshio Kuratomi

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

Re: [ansible-project] Ansible-2.10.0 has been released!

2020-09-23 Thread Toshio Kuratomi

I'm not sure if the why but yes, the official location is now supposed to
be pypi.

We had decided to no longer ship rpms upstream early in the cycle because
the rpm distributions were doing a much better job of packaging than we
were.  That turned into the tarballs as well which I don't see a problem
with as pypi is generally the go to location for python packages anyway but
I can't remember what the reasoning was.

Thanks for checking on that!

-Toshio

On Wed, Sep 23, 2020, 1:35 AM Michael Ströder  wrote:

> On 9/23/20 1:22 AM, Toshio Kuratomi wrote:
> > The tar.gz of the release can be found here:
> >
> > * Ansible 2.10.0
> > https://pypi.python.org/packages/source/a/ansible/ansible-2.10.0.tar.gz
> > SHA256: 3aadd662ac3f04e46054c99cfe533a92ba33d97982f19e49f01dbe137f31d346
>
> Any particular reason why the source is not available here like with
> older releases?
>
> https://releases.ansible.com/ansible/
>
> I'm asking because the openSUSE package .spec contains:
>
> Source:
> https://releases.ansible.com/ansible/ansible-%{version}.tar.gz
> Source1:
> https://releases.ansible.com/ansible/ansible-%{version}.tar.gz.sha
>
> If this download location is not the official URL anymore I can change
> that of course.
>
> Ciao, Michael.
>
>

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

[ansible-project] Ansible-2.10.0 has been released!

2020-09-22 Thread Toshio Kuratomi

ch have opted-in.
You can find that at:
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst


Thanks!
-Toshio Kuratomi

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaT4mSBx%2Btd5hYReHtcrMmzVUVpGFyXUcLYoN3-kVpwz2w%40mail.gmail.com.

[ansible-project] Ansible-2.10.0 release candidate 1

2020-09-16 Thread Toshio Kuratomi

Hi all-

For all those wanting to test the next version of Ansible, we're happy
to announce that Ansible 2.10.0 release candidate 1 is now available
on PyPI!

Ansible 2.10.0rc1 pulls in the ansible-base-2.10.1 package via a
dependency and includes a range of Ansible Collections.  The Ansible
2.10 PyPI packages provide similar functionality to Ansible 2.9 and
earlier versions, but from multiple sources. The included Ansible
Collections are maintained by a host of open source contributors who
want to add to what ansible-base has to offer.

For an overview of "Ansible Collections" and the differences between
`ansible-base` and `ansible` please see
https://github.com/ansible-collections/overview/blob/master/README.rst

We need your help
-

This new `ansible` package *should* be a drop-in replacement for
Ansible 2.9. The roles and playbooks that you currently use should
work out of the box with ansible-2.10.0 rc1.

Please let us know if:

* Your playbooks don't work
* There are any installation issues
* Whether the collections are found OK
* If the updated and new modules in the collections work

How to get it
-

Due to a limitation in pip, you need to uninstall Ansible 2.9 (or
earlier) before installing the 2.10 version:

$ pip uninstall ansible
$ pip install ansible==2.10.0rc1 --user

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

* Ansible 2.10.0rc1
https://pypi.python.org/packages/source/a/ansible/ansible-2.10.0rc1.tar.gz
SHA256: 86a69fe18f086e1c857de81e230ff08ab8d4610220cb71f366dfc43093e0f65d


What's new in Ansible 2.10.0rc1
---

* Collections which have opted into being a part of the Ansible-2.10.0
unified changelog will have an entry on this page:
  
https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst

* For other collections, consult the list of included collections in
the link below and check their entry on https://galaxy.ansible.com for
information about their changes.

* List of collections included in the 2.10.0rc1 release:
* 
https://github.com/ansible-community/ansible-build-data/blob/2.10.0rc1/2.10/ansible-2.10.0rc1.deps
* You can find more information for those on
https://galaxy.ansible.com/. For instance, the community.crypto
collection listed in the ansible-2.10.0rc1.deps file has a galaxy page
here at https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.10.1 which this release of ansible installs:
  
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst


Caveats and known bugs
--

* The individual collections that make up the ansible-2.10.0 package
can be viewed independently. However, they aren't currently listed by
ansible-galaxy. A workaround for this is to explicitly specify where
ansible has installed the collections::

  COLLECTION_INSTALL=$(python -c 'import ansible, os.path ;
print("%s/../ansible_collections" %
os.path.dirname(ansible.__file__))') ansible-galaxy collection list -p
"$COLLECTION_INSTALL"

* A fix has been proposed but was not be merged for 2.10.0. This is
being tracked in this bug report:
  https://github.com/ansible/ansible/issues/70147

* Due to a limitation in pip, you cannot `pip install --upgrade` from
ansible-2.9 or earlier to ansible-2.10 or higher. Instead, you must
explicitly `pip uninstall ansible` before pip installing the new
version. The install of the ansible package has been modified to warn
you if you attempt to upgrade via pip with instructions to uninstall
first.

* A few fortios modules aren't being redirected from their 2.9.x names
to their names inside of the 2.10.x collections.  You'll need to
modify your playbooks to use fully qualified names for those modules.
You can use the documentation for the fortinet.fortios collection to
determine those:
https://docs.ansible.com/ansible/2.10/collections/fortinet/fortios/


What's the schedule for the rest of the 2.10.0 release cycle?
-

If no blocker bugs are found, ansible-2.10.0 final will be released on
2020-09-22.

The ansible-2.10 roadmap reflects these dates:
https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_2_10.html

Porting Help


There's a unified porting guide for collections which have opted-in.
You can find that at:
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst

If you encounter any bugs, please report them. We're putting together
a draft document which includes where to report bugs on various parts
of the ansible package:
* 
https://github.com/ansible/community/wiki/User-testing-of-ansible-2.10-pre-releases

If you aren't sure where your bug falls, pick which you feel is
closest and the Community Team will always move it if needed.

Thanks!

-Toshio Kuratomi

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project&quo

[ansible-project] Re: Nominating blockers to 2.10.0 [Was Re: Ansible 2.10.0 beta 1]

2020-09-10 Thread Toshio Kuratomi

And yes... apparently I suck at email :-(.  Posting this to the
correct subthread in case anyone is following this conversation on the
google groups forum interface instead of via a threaded email client:

One more piece of information:  The meeting on the 17th of September
will take place in the #ansible-community channel on irc.freenode.net.
Note that if you haven't used freenode before, you can use online
webchat to access freenode: https://webchat.freenode.net/

Because of issues with spam and harassment, you'll need to register to
participate in our channels:
https://freenode.net/kb/answer/registration  I highly recommend
registering and testing that you are able to participate in
#ansible-community discussions before the meeting on the 17th!

-Toshio

On Thu, Sep 10, 2020 at 8:29 AM Toshio Kuratomi  wrote:
>
> Howdy folks!
>
> We're entering the final weeks of the Ansible 2.10.0 release cycle and
> I wanted to let anyone testing the Ansible betas and release candidate
> on how to nominate a bug as a release blocker.
>
> * If you find something major enough to block the Ansible release,
> please add a comment on the Community Meeting Agenda:
> https://github.com/ansible/community/issues/539 asking us to consider
> whether the issue is a blocker.  If the issue has a ticket open
> elsewhere, linking to the ticket will be appreciated.
>
> * If at all possible, attend the IRC meeting on Thursday, September
> 17th, 2020, 18:00 UTC to state your case as to why the issue should
> block the release.
>
> * We'll decide at the meeting whether to slip the Ansible-2.10.0 final
> release for any of the listed blockers.
>
> *Important*: If the Meeting Agenda does not contain any comments
> listing potential blockers when the meeting starts on Thursday, we'll
> end the meeting early.  We will wait for five minutes or so to see if
> anyone proposes a blocker at   the start of the meeting itself but
> otherwise we'll cut the meeting short.  So please, if you have a
> candidate blocker; get your issue listed on the Community Agenda ASAP.
>
> What should you do if you notice a blocker after the meeting time?
> You can still report it on the Community Meeting Agenda.  However,
> it's likely that only myself and a few other people will be able to
> look at and evaluate it before   the release date and we'll likely
> lean towards fixing anything that wasn't noticed previously in the
> Ansible-2.10.1 release.  So please test out the beta and release
> candidate now and report candidate blockers before the meeting.
>
> Thank you,
> Toshio Kuratomi
>
> On Tue, Sep 1, 2020 at 11:21 PM Toshio Kuratomi  wrote:
> >
> > Hi all-
> >
> > For all those wanting to test the next version of Ansible, we're happy
> > to announce that Ansible 2.10.0 beta1 is now available on PyPI!
> >
> > Ansible 2.10.0b1 pulls in the ansible-base-2.10.1 (presently rc2)
> > package via a dependency and includes a range of Ansible Collections.
> > The Ansible 2.10 PyPI packages provide similar functionality to
> > Ansible 2.9 and earlier versions, but from multiple sources. The
> > included Ansible Collections are maintained by a host of open source
> > contributors who want to add to what ansible-base has to offer.
> >
> > For an overview of "Ansible Collections" and the differences between
> > `ansible-base` and `ansible`  please see
> > https://github.com/ansible-collections/overview/blob/master/README.rst
> >
> > We need your help
> > -
> >
> > This new `ansible` package *should* be a drop-in replacement for
> > Ansible 2.9. The roles and playbooks that you currently use should
> > work out of the box with ansible-2.10.0 beta1.
> >
> > Please let us know if:
> >
> > * Your playbooks don't work
> > * There are any installation issues
> > * Whether the collections are found OK
> > * If the updated and new modules in the collections work
> >
> > How to get it
> > -
> >
> > Due to a limitation in pip, you need to uninstall Ansible 2.9 (or
> > earlier) before installing the 2.10 version:
> >
> > $ pip uninstall ansible
> > $ pip install ansible==2.10.0b1 --user
> >
> > The tar.gz of the release can be found here:
> >
> > * Ansible 2.10.0b1
> >   https://pypi.python.org/packages/source/a/ansible/ansible-2.10.0b1.tar.gz
> >   SHA256: 081c1b1ea95a0b67f8bf1e5c3c45b8e8dd8bafd1f8d05838f96239da3496ce8f
> >
> >
> > What's new in Ansible 2.10.0b1
> > --
> >
> > * Collections which have opted into being a part of the Ansible-2.10.0
> > unified changelog will have an entry on th

[ansible-project] Re: Ansible 2.10.0 beta 1

2020-09-10 Thread Toshio Kuratomi

One more piece of information:  The meeting on the 17th of September
will take place in the #ansible-community channel on irc.freenode.net.
Note that if you haven't used freenode before, you can use online
webchat to access freenode: https://webchat.freenode.net/

Because of issues with spam and harassment, you'll need to register to
participate in our channels:
https://freenode.net/kb/answer/registration  I highly recommend
registering and testing that you are able to participate in
#ansible-community discussions before the meeting on the 17th!

-Toshio

On Tue, Sep 1, 2020 at 11:21 PM Toshio Kuratomi  wrote:
>
> Hi all-
>
> For all those wanting to test the next version of Ansible, we're happy
> to announce that Ansible 2.10.0 beta1 is now available on PyPI!
>
> Ansible 2.10.0b1 pulls in the ansible-base-2.10.1 (presently rc2)
> package via a dependency and includes a range of Ansible Collections.
> The Ansible 2.10 PyPI packages provide similar functionality to
> Ansible 2.9 and earlier versions, but from multiple sources. The
> included Ansible Collections are maintained by a host of open source
> contributors who want to add to what ansible-base has to offer.
>
> For an overview of "Ansible Collections" and the differences between
> `ansible-base` and `ansible`  please see
> https://github.com/ansible-collections/overview/blob/master/README.rst
>
> We need your help
> -
>
> This new `ansible` package *should* be a drop-in replacement for
> Ansible 2.9. The roles and playbooks that you currently use should
> work out of the box with ansible-2.10.0 beta1.
>
> Please let us know if:
>
> * Your playbooks don't work
> * There are any installation issues
> * Whether the collections are found OK
> * If the updated and new modules in the collections work
>
> How to get it
> -
>
> Due to a limitation in pip, you need to uninstall Ansible 2.9 (or
> earlier) before installing the 2.10 version:
>
> $ pip uninstall ansible
> $ pip install ansible==2.10.0b1 --user
>
> The tar.gz of the release can be found here:
>
> * Ansible 2.10.0b1
>   https://pypi.python.org/packages/source/a/ansible/ansible-2.10.0b1.tar.gz
>   SHA256: 081c1b1ea95a0b67f8bf1e5c3c45b8e8dd8bafd1f8d05838f96239da3496ce8f
>
>
> What's new in Ansible 2.10.0b1
> --
>
> * Collections which have opted into being a part of the Ansible-2.10.0
> unified changelog will have an entry on this page:
> https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst
>
> * For other collections, consult the list of included collections in
> the link below and check their entry on https://galaxy.ansible.com for
> information about their changes.
>
> * List of collections included in the 2.10.0b1 release:
>   * 
> https://github.com/ansible-community/ansible-build-data/blob/2.10.0b1/2.10/ansible-2.10.0b1.deps
>   * You can find more information for those on
> https://galaxy.ansible.com/.  For instance, the community.crypto
> collection listed in the ansible-2.10.0b1.deps file has a galaxy page
> here at https://galaxy.ansible.com/community/crypto/
>
> * Changelog for ansible-base-2.10.1 which this release of ansible installs:
>   
> https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst
>
>
> Caveats and known bugs
> --
>
> * The individual collections that make up the ansible-2.10.0 package
> can be viewed independently.  However, they aren't currently listed by
> ansible-galaxy.  A workaround for this is to explicitly specify where
> ansible has installed the collections::
>
> COLLECTION_INSTALL=$(python -c 'import ansible, os.path ;
> print("%s/../ansible_collections" %
> os.path.dirname(ansible.__file__))') ansible-galaxy collection list -p
> "$COLLECTION_INSTALL"
>
>   * A fix has been proposed but was not be merged for 2.10.0. This is
> being tracked in this bug report:
> https://github.com/ansible/ansible/issues/70147
>
> * Due to a limitation in pip, you cannot `pip install --upgrade` from
> ansible-2.9 or earlier to ansible-2.10 or higher.  Instead, you must
> explicitly `pip uninstall ansible` before pip installing the new
> version.  The install of the ansible package has been modified to warn
> you if you attempt to upgrade via pip with instructions to uninstall
> first.
>
>
> What's the schedule for the rest of the 2.10.0 release cycle?
> -
>
> ansible-2.10.0rc1 is due to be released on 2020-09-10
> ansible-2.10.0 final is due out on 2020-09-22
>
> The ansible-2.10 roadmap reflects these dates:
> https://docs.ansible.com

[ansible-project] Nominating blockers to 2.10.0 [Was Re: Ansible 2.10.0 beta 1]

2020-09-10 Thread Toshio Kuratomi

Howdy folks!

We're entering the final weeks of the Ansible 2.10.0 release cycle and
I wanted to let anyone testing the Ansible betas and release candidate
on how to nominate a bug as a release blocker.

* If you find something major enough to block the Ansible release,
please add a comment on the Community Meeting Agenda:
https://github.com/ansible/community/issues/539 asking us to consider
whether the issue is a blocker.  If the issue has a ticket open
elsewhere, linking to the ticket will be appreciated.

* If at all possible, attend the IRC meeting on Thursday, September
17th, 2020, 18:00 UTC to state your case as to why the issue should
block the release.

* We'll decide at the meeting whether to slip the Ansible-2.10.0 final
release for any of the listed blockers.

*Important*: If the Meeting Agenda does not contain any comments
listing potential blockers when the meeting starts on Thursday, we'll
end the meeting early.  We will wait for five minutes or so to see if
anyone proposes a blocker at   the start of the meeting itself but
otherwise we'll cut the meeting short.  So please, if you have a
candidate blocker; get your issue listed on the Community Agenda ASAP.

What should you do if you notice a blocker after the meeting time?
You can still report it on the Community Meeting Agenda.  However,
it's likely that only myself and a few other people will be able to
look at and evaluate it before   the release date and we'll likely
lean towards fixing anything that wasn't noticed previously in the
Ansible-2.10.1 release.  So please test out the beta and release
candidate now and report candidate blockers before the meeting.

Thank you,
Toshio Kuratomi

On Tue, Sep 1, 2020 at 11:21 PM Toshio Kuratomi  wrote:
>
> Hi all-
>
> For all those wanting to test the next version of Ansible, we're happy
> to announce that Ansible 2.10.0 beta1 is now available on PyPI!
>
> Ansible 2.10.0b1 pulls in the ansible-base-2.10.1 (presently rc2)
> package via a dependency and includes a range of Ansible Collections.
> The Ansible 2.10 PyPI packages provide similar functionality to
> Ansible 2.9 and earlier versions, but from multiple sources. The
> included Ansible Collections are maintained by a host of open source
> contributors who want to add to what ansible-base has to offer.
>
> For an overview of "Ansible Collections" and the differences between
> `ansible-base` and `ansible`  please see
> https://github.com/ansible-collections/overview/blob/master/README.rst
>
> We need your help
> -
>
> This new `ansible` package *should* be a drop-in replacement for
> Ansible 2.9. The roles and playbooks that you currently use should
> work out of the box with ansible-2.10.0 beta1.
>
> Please let us know if:
>
> * Your playbooks don't work
> * There are any installation issues
> * Whether the collections are found OK
> * If the updated and new modules in the collections work
>
> How to get it
> -
>
> Due to a limitation in pip, you need to uninstall Ansible 2.9 (or
> earlier) before installing the 2.10 version:
>
> $ pip uninstall ansible
> $ pip install ansible==2.10.0b1 --user
>
> The tar.gz of the release can be found here:
>
> * Ansible 2.10.0b1
>   https://pypi.python.org/packages/source/a/ansible/ansible-2.10.0b1.tar.gz
>   SHA256: 081c1b1ea95a0b67f8bf1e5c3c45b8e8dd8bafd1f8d05838f96239da3496ce8f
>
>
> What's new in Ansible 2.10.0b1
> --
>
> * Collections which have opted into being a part of the Ansible-2.10.0
> unified changelog will have an entry on this page:
> https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst
>
> * For other collections, consult the list of included collections in
> the link below and check their entry on https://galaxy.ansible.com for
> information about their changes.
>
> * List of collections included in the 2.10.0b1 release:
>   * 
> https://github.com/ansible-community/ansible-build-data/blob/2.10.0b1/2.10/ansible-2.10.0b1.deps
>   * You can find more information for those on
> https://galaxy.ansible.com/.  For instance, the community.crypto
> collection listed in the ansible-2.10.0b1.deps file has a galaxy page
> here at https://galaxy.ansible.com/community/crypto/
>
> * Changelog for ansible-base-2.10.1 which this release of ansible installs:
>   
> https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst
>
>
> Caveats and known bugs
> --
>
> * The individual collections that make up the ansible-2.10.0 package
> can be viewed independently.  However, they aren't currently listed by
> ansible-galaxy.  A workaround for this is to explicitly specify where
> ansible has installed the collections::
>
> COLLECT

[ansible-project] Ansible-2.10.0 beta2

2020-09-08 Thread Toshio Kuratomi

Hi all-

For all those wanting to test the next version of Ansible, we're happy
to announce that Ansible 2.10.0 beta2 is now available on PyPI!

Ansible 2.10.0b2 pulls in the ansible-base-2.10.1 (presently rc3)
package via a dependency and includes a range of Ansible Collections.
The Ansible 2.10 PyPI packages provide similar functionality to
Ansible 2.9 and earlier versions, but from multiple sources. The
included Ansible Collections are maintained by a host of open source
contributors who want to add to what ansible-base has to offer.

For an overview of "Ansible Collections" and the differences between
`ansible-base` and `ansible`  please see
https://github.com/ansible-collections/overview/blob/master/README.rst

We need your help
-

This new `ansible` package *should* be a drop-in replacement for
Ansible 2.9. The roles and playbooks that you currently use should
work out of the box with ansible-2.10.0 beta2.

Please let us know if:

* Your playbooks don't work
* There are any installation issues
* Whether the collections are found OK
* If the updated and new modules in the collections work

How to get it
-

Due to a limitation in pip, you need to uninstall Ansible 2.9 (or
earlier) before installing the 2.10 version:

$ pip uninstall ansible
$ pip install ansible==2.10.0b2 --user

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

* Ansible 2.10.0b2
  https://pypi.python.org/packages/source/a/ansible/ansible-2.10.0b2.tar.gz
  SHA256: 5a833071b5b4ce66f7ed80fe76b9b523fef753cb32916d2954beed8b9cc56365


What's new in Ansible 2.10.0b2
--

* Collections which have opted into being a part of the Ansible-2.10.0
unified changelog will have an entry on this page:
https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst

* For other collections, consult the list of included collections in
the link below and check their entry on https://galaxy.ansible.com for
information about their changes.

* List of collections included in the 2.10.0b2 release:
  * 
https://github.com/ansible-community/ansible-build-data/blob/2.10.0b2/2.10/ansible-2.10.0b2.deps
  * You can find more information for those on
https://galaxy.ansible.com/.  For instance, the community.crypto
collection listed in the ansible-2.10.0b2.deps file has a galaxy page
here at https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.10.1 which this release of ansible installs:
  
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst


Caveats and known bugs
--

* The individual collections that make up the ansible-2.10.0 package
can be viewed independently.  However, they aren't currently listed by
ansible-galaxy.  A workaround for this is to explicitly specify where
ansible has installed the collections::

COLLECTION_INSTALL=$(python -c 'import ansible, os.path ;
print("%s/../ansible_collections" %
os.path.dirname(ansible.__file__))') ansible-galaxy collection list -p
"$COLLECTION_INSTALL"

  * A fix has been proposed but was not be merged for 2.10.0. This is
being tracked in this bug report:
https://github.com/ansible/ansible/issues/70147

* Due to a limitation in pip, you cannot `pip install --upgrade` from
ansible-2.9 or earlier to ansible-2.10 or higher.  Instead, you must
explicitly `pip uninstall ansible` before pip installing the new
version.  The install of the ansible package has been modified to warn
you if you attempt to upgrade via pip with instructions to uninstall
first.


What's the schedule for the rest of the 2.10.0 release cycle?
-

There has been a small change to the pre-release schedule but the
2.10.0 final date has not yet changed:

* 2020-09-15: ansible-2.10.0 rc1 and final freeze.
* 2020-09-22 ansible-2.10.0 final

The ansible-2.10 roadmap reflects these dates:
https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_2_10.html

Porting Help


There's a unified porting guide for collections which have opted-in.
You can find that at:
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst

If you encounter any bugs, please report them.  We're putting together
a draft document which includes where to report bugs on various parts
of the ansible package:
  * 
https://github.com/ansible/community/wiki/User-testing-of-ansible-2.10-pre-releases

If you aren't sure where your bug falls, pick which you feel is
closest and the Community Team will always move it if needed

Thanks!

-Toshio Kuratomi

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSv4x

[ansible-project] Changes to the ansible-2.10.0 pre-release schedule

2020-09-04 Thread Toshio Kuratomi

Hi all,

Due to the one week slip in ansible-base-2.10.0, there will be some
changes to the ansible-2.10.0 pre-release schedule.  At this time, the
ansible-2.10.0 final release will still occur on September 22.

Here are the new dates along with relevant dates from ansible-base-2.10.1:

* 07-Sep-2020: ansible-base 2.10.1rc3
* 08-Sep-2020: ansible-2.10.0b2 (new pre-release to depend on
ansible-base-2.10.1rc3)
* 14-Sep-2020: ansible-base-2.10.1 final
* 15-Sep-2020: ansible-2.10.0rc1 (moved from 10-Sep)
  * Collection owners who feel there are blocker bugs in the versions
of their collections included in 2.10.0rc1 should add them to the IRC
meeting agenda for 17-Sep-2020, 18:00UTC, and, if at all possible,
show up to discuss whether to slip the final release to include fixes
for them:
* Agenda: https://github.com/ansible/community/issues/539
* ics to import the meeting time:
https://raw.githubusercontent.com/ansible/community/master/meetings/ical/community.ics

* 22-Sep-2020: If no blockers are found, ansible-2.10.0 final will
release as previously scheduled.

Thanks for understanding!
-Toshio Kuratomi

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaTtiwf30DxfX%2BxHKNZ2oAAvtzn%2Bc5w6diqxkuQgV-VG%2BA%40mail.gmail.com.

[ansible-project] Ansible 2.10.0 beta 1

2020-09-02 Thread Toshio Kuratomi

Hi all-

For all those wanting to test the next version of Ansible, we're happy
to announce that Ansible 2.10.0 beta1 is now available on PyPI!

Ansible 2.10.0b1 pulls in the ansible-base-2.10.1 (presently rc2)
package via a dependency and includes a range of Ansible Collections.
The Ansible 2.10 PyPI packages provide similar functionality to
Ansible 2.9 and earlier versions, but from multiple sources. The
included Ansible Collections are maintained by a host of open source
contributors who want to add to what ansible-base has to offer.

For an overview of "Ansible Collections" and the differences between
`ansible-base` and `ansible`  please see
https://github.com/ansible-collections/overview/blob/master/README.rst

We need your help
-

This new `ansible` package *should* be a drop-in replacement for
Ansible 2.9. The roles and playbooks that you currently use should
work out of the box with ansible-2.10.0 beta1.

Please let us know if:

* Your playbooks don't work
* There are any installation issues
* Whether the collections are found OK
* If the updated and new modules in the collections work

How to get it
-

Due to a limitation in pip, you need to uninstall Ansible 2.9 (or
earlier) before installing the 2.10 version:

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

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

* Ansible 2.10.0b1
  https://pypi.python.org/packages/source/a/ansible/ansible-2.10.0b1.tar.gz
  SHA256: 081c1b1ea95a0b67f8bf1e5c3c45b8e8dd8bafd1f8d05838f96239da3496ce8f


What's new in Ansible 2.10.0b1
--

* Collections which have opted into being a part of the Ansible-2.10.0
unified changelog will have an entry on this page:
https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst

* For other collections, consult the list of included collections in
the link below and check their entry on https://galaxy.ansible.com for
information about their changes.

* List of collections included in the 2.10.0b1 release:
  * 
https://github.com/ansible-community/ansible-build-data/blob/2.10.0b1/2.10/ansible-2.10.0b1.deps
  * You can find more information for those on
https://galaxy.ansible.com/.  For instance, the community.crypto
collection listed in the ansible-2.10.0b1.deps file has a galaxy page
here at https://galaxy.ansible.com/community/crypto/

* Changelog for ansible-base-2.10.1 which this release of ansible installs:
  
https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst


Caveats and known bugs
--

* The individual collections that make up the ansible-2.10.0 package
can be viewed independently.  However, they aren't currently listed by
ansible-galaxy.  A workaround for this is to explicitly specify where
ansible has installed the collections::

COLLECTION_INSTALL=$(python -c 'import ansible, os.path ;
print("%s/../ansible_collections" %
os.path.dirname(ansible.__file__))') ansible-galaxy collection list -p
"$COLLECTION_INSTALL"

  * A fix has been proposed but was not be merged for 2.10.0. This is
being tracked in this bug report:
https://github.com/ansible/ansible/issues/70147

* Due to a limitation in pip, you cannot `pip install --upgrade` from
ansible-2.9 or earlier to ansible-2.10 or higher.  Instead, you must
explicitly `pip uninstall ansible` before pip installing the new
version.  The install of the ansible package has been modified to warn
you if you attempt to upgrade via pip with instructions to uninstall
first.


What's the schedule for the rest of the 2.10.0 release cycle?
-

ansible-2.10.0rc1 is due to be released on 2020-09-10
ansible-2.10.0 final is due out on 2020-09-22

The ansible-2.10 roadmap reflects these dates:
https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_2_10.html

Porting Help


There's a unified porting guide for collections which have opted-in.
You can find that at:
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst

If you encounter any bugs, please report them.  We're putting together
a draft document which includes where to report bugs on various parts
of the ansible package:
  * 
https://github.com/ansible/community/wiki/User-testing-of-ansible-2.10-pre-releases

If you aren't sure where your bug falls, pick which you feel is
closest and the Community Team will always move it if needed

Thanks!

-Toshio Kuratomi

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaS%3DNDNp5%3DHg52kR6dMa-pkpgsmpGO45DjaaP5b3xcMGOg%40mail.gmail.com.

[ansible-project] Minor change to the license listed in the project's README to GPLv3+

2019-11-26 Thread Toshio Kuratomi

Greetings all,

I'm just letting you all know that I'm merging this PR today:
https://github.com/ansible/ansible/pull/65124

It changes the license listed in the README from "GNU General Public
License v3.0" to "GNU General Public License v3.0 or later".  We
consider this a clarification rather than a relicensing as both the
Ansible documentation[1]_ and the headers for contributed Ansible code
(for instance, this [2]_ and [3]_) say either "GNU Public License v3.0
or later" or the abbreviated form "GNU General Public License v3.0+".

.. _[1]: 
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/dev_guide/developing_modules_checklist.rst#contributing-to-ansible-objective-requirements
.. _[2]: https://github.com/ansible/ansible/blob/devel/lib/ansible/release.py
.. _[3]: https://github.com/ansible/ansible/blob/devel/lib/ansible/context.py#L3

-Toshio

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

[ansible-project] New Ansible release 2.9.0

2019-10-31 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general release of Ansible
2.9.0 is now available!

How do you get it?
--

$ pip install ansible==2.9.0 --user

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

* 2.9.0
https://releases.ansible.com/ansible/ansible-2.9.0.tar.gz
SHA256: 9f9a9ace1d63cd8a4692ab6ee6ed04823743f1bd339a6ef188860c02cf7f46f1

What's new in 2.9.0
---

The major theme of this release has been polishing the support for
collections. Please consult the changelog for the changes related to
this. as well as the other changes and bugfixes included in 2.9.0:

* 2.9.0

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 2019-11-21.

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.0, 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!

-Toshio Kuratomi

--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQOs-KGfJWpnehi%2BvZfoY9OQPK-raYibn1AvUukKHVO0g%40mail.gmail.com.

[ansible-project] New Ansible releases 2.8.6, 2.7.14, 2.6.20, and 2.9.0rc4

2019-10-17 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general release of Ansible
2.8.6, 2.7.14, 2.6.20, and a new prerelease of 2.9.0, 2.9.0rc4, are
now available!


How do you get it?
--

$ pip install ansible==2.8.6 --user
or
$ pip install ansible==2.7.14 --user
or
$ pip install ansible==2.6.20 --user
or
$ pip install ansible==2.9.0rc4 --user

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

* 2.8.6
  https://releases.ansible.com/ansible/ansible-2.8.6.tar.gz
  SHA256: 31203b27c9d61123e8c86b6eb5116a21859ed4f26d55a1a71eaf27bd92bce355
* 2.7.14
  https://releases.ansible.com/ansible/ansible-2.7.14.tar.gz
  SHA256: 6a52f43b5e4446aa04f3907a750010fbbf41eb050cb726065c6c877ed3a98d02
* 2.6.20
  https://releases.ansible.com/ansible/ansible-2.6.20.tar.gz
  SHA256: 16cfb99d7f321cec408afcd3ead538337ebc3247c7a77080e5cabb58054e2a0b
* 2.9.0rc4
  https://releases.ansible.com/ansible/ansible-2.9.0rc4.tar.gz
  SHA256: 563f21d7720efbf4def9820ca17790eed33b2c16dacea99d28f8fe2e5237


What's new in 2.8.6, 2.7.14, 2.6.20, and 2.9.0rc4
-

These releases contain fixes for three CVEs:

* ansible: Incomplete fix for CVE-2019-10206 (CVE-2019-14856)
* ansible: sub parameters marked as no_log are not masked in certain failure
scenarios (CVE-2019-14858)
* ansible: secrets disclosed on logs when no_log enabled
(CVE-2019-14846)  [Note: This cve did not affect 2.9.0rc4 as Ansible
2.9 had changed the affected code as part of an unrelated cleanup]

Ansible-2.6.20 is only seeing security fixes at this point in its
lifecycle but 2.7.x, 2.8.x, and 2.9.x saw other bugfixes as well.
Please see the full changelogs for each release to see what's changed:

* 2.8.6
  
https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v2.8.rst
* 2.7.14
  
https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst
* 2.6.20
  
https://github.com/ansible/ansible/blob/stable-2.6/changelogs/CHANGELOG-v2.6.rst
* 2.9.0rc4
  
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst


What's the schedule for future maintenance releases?


Ansible-2.6 and Ansible-2.7 are only updated as needed for security
and critical bugfixes respectively.

Ansible-2.8 will have one more scheduled release after Ansible-2.9.0
comes out. Since the Ansible-2.9.0 release date has slipped to the
31st of October, expect the Ansible-2.8.7 release in the beginning of
November.

Ansible-2.9.0 may have an rc5 next week if any bugs which deserve an
rc5 are discovered between now and then.  Otherwise, expect to see
Ansible-2.9.0 on October 31st!

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.

and

https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.8.html to
help migrate your content to 2.8.


If you discover any errors or if any of your working playbooks break when you
upgrade to 2.8.6, 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!

-Toshio Kuratomi

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQet4Z%3D%2BrRSkcW%2Bh8cdc_fuoLuBf4zRe4kTwvNBj_w-7w%40mail.gmail.com.

[ansible-project] New Ansible pre-release 2.9.0rc1

2019-09-20 Thread Toshio Kuratomi

Hi all- we're happy to announce that the first release candidate of
Ansible 2.9, Ansible-2.9.0rc1 rc1 is now available!


How do you get it?
--

$ pip install ansible==2.9.0rc1 --user

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

* 2.9.0rc1
  https://releases.ansible.com/ansible/ansible-2.9.0rc1.tar.gz
  SHA256: a24bac21f1cc15130b74851a1d3b5128c48d235d940ead25997c85337965e703


What's new in 2.9.0rc1
--

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

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


What's the schedule for the rest of 2.9.0?


Please see the ROADMAP for the schedule of future 2.9.0 releases
leading up to 2.9.0 final:
https://docs.ansible.com/ansible/devel/roadmap/ROADMAP_2_9.html

The 2.9.0rc1 release cycle was a little messy with some bugfixes that
were a little closer to features than normal making their way in.
Despite that, we think that this is a solid release candidate and we
currently don't see any blockers for the 2.9.0 release.

Please test out this release candidate, report any problems that you
encounter, and draw our attention to any that you'd like us to
consider as blockers for the 2.9.0 final release.  The more time we
have to look at a potential blocker, the more likely we'll consider it
a blocker for release rather than something that we will fix in 2.9.1
instead.

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.0rc1, 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!

-Toshio Kuratomi

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQUCPpHAPGfQWApGu%2BEohrKTkoppnXf%3DyqrCoP1ZB6JbA%40mail.gmail.com.

[ansible-project] New Ansible release 2.8.5

2019-09-12 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general release of Ansible
2.8.5 is now available!

How do you get it?
--

$ pip install ansible==2.8.5 --user

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

* 2.8.5
https://releases.ansible.com/ansible/ansible-2.8.5.tar.gz
SHA256: 8e9403e755ce8ef27b6066cdd7a4c567aa80ebe2fd90d0ff8efa0a725d246986

What's new in 2.8.5
---

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

* 2.8.5

https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v2.8.rst

What's the schedule for future maintenance releases?

The 2.9.0 release is just around the corner. (Release candidates
should hopefully start next week). So just as we did when 2.8.0
entered the final stages before release, we'll be deferring releases
of the older branch until after the 2.9.0 release is out. At that
point we'll release 2.8.6 and then end the regularly scheduled
releases of 2.8.x (only critical and maintenance bugfixes from that
point forward).

Porting Help

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

If you discover any errors or if any of your working playbooks break when you
upgrade to 2.8.5, 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!

-Toshio Kuratomi

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

[ansible-project] New Ansible releases 2.8.4, 2.7.13, and 2.6.19

2019-08-15 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general releases of Ansible
2.8.4, 2.7.13, and 2.6.19 are now available!


How do you get it?
--

$ pip install ansible==2.8.4 --user
or
$ pip install ansible==2.7.13 --user
or
$ pip install ansible==2.6.19 --user

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

* 2.8.4
  https://releases.ansible.com/ansible/ansible-2.8.4.tar.gz
  SHA256: a0153e2de3619b7e307df179cd91a3c3804cf1fe048273fe4ea5238b76679ff1
* 2.7.13
  https://releases.ansible.com/ansible/ansible-2.7.13.tar.gz
  SHA256: 339c87a1bf9e8555ce1e1c1a9452d8ed1df240944ec1a3fc2e813e6c7d70aeae
* 2.6.19
  https://releases.ansible.com/ansible/ansible-2.6.19.tar.gz
  SHA256: dbcfc9ddf620d05e1147b4c713738045a67c32be7260b11cbdbd84e92b77ca06


What's new in 2.8.4, 2.7.13, and 2.6.19
---

2.7.13 and 2.6.19 are security releases containing a fix for
CVE-2019-10206.  2.8.4 is a maintenance release containing numerous
bugfixes in addition to a fix for CVE-2019-10206 and CVE-2019-10217
(the latter does not affect 2.7.13 and 2.6.19).

CVEs fixed:
* CVE-2019-10206:  Avoid templating passwords from the command prompt
as templating may reveal secret information.
* CVE-2019-10217: Add no_log to credential fields in gcp_* modules so
that these modules do not display credentials on stdout or save them
to log iles.

The full changelogs for these releases are at:

* 2.8.4
  
https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v2.8.rst
* 2.7.13
  
https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst
* 2.6.19
  
https://github.com/ansible/ansible/blob/stable-2.6/changelogs/CHANGELOG-v2.6.rst


What's the schedule for future maintenance releases?


Future maintenance releases of 2.8.4 will occur approximately every 3
weeks.  So expect
the next one around 2019-09-05.

2.7.x and 2.6.x are released on an as needed basis for critical and
security bugfixes respectively.

Porting Help


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


If you discover any errors or if any of your working playbooks break when you
upgrade to 2.8.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!

-Toshio Kuratomi

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaTKB%3DTsY8JZ3K7LR4tqU4NgHXVz28HGbNs7yx%2BbQhb6bQ%40mail.gmail.com.

[ansible-project] New Ansible release 2.8.3

2019-07-25 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general release of Ansible
2.8.3 is now available!


How do you get it?
--

$ pip install ansible==2.8.3 --user

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

* 2.8.3
  https://releases.ansible.com/ansible/ansible-2.8.3.tar.gz
  SHA256: 05f9ed3ca3e06dffaa87a73a8e6f7f322825bc3f609f8b71c4fe22dbbdf72abc


What's new in 2.8.3
---

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

* 2.8.3
  
https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v2.8.rst


What's the schedule for future maintenance releases?


Future maintenance releases will occur approximately every 3 weeks.  So expect
the next one around 2019-08-15.


Porting Help


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


If you discover any errors or if any of your working playbooks break when you
upgrade to 2.8.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!

-Toshio Kuratomi

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaRuvZkheKYwLN6jU%2BMQS-q213AdnOhFC1%2BOrJKt4yY8ww%40mail.gmail.com.

[ansible-project] Re: New Ansible releases 2.8.2, 2.7.12, and 2.6.18

2019-07-03 Thread Toshio Kuratomi

One additional note:  The Deb builds for the Ansible PPA failed.
We're working on getting those built and uploaded but no ETA yet.
(Tomorrow is a US holiday so it cuts into the time available to
diagnose, fix, and then release those).

-Toshoi

On Wed, Jul 3, 2019 at 1:56 PM Toshio Kuratomi  wrote:
>
> Hi all- we're happy to announce that the general release of Ansible 2.8.2,
> 2.7.12, and 2.6.18 are now available!
>
>
> How do you get it?
> --
>
> $ pip install ansible==2.8.2 --user
> or
> $ pip install ansible==2.7.12 --user
> or
> $ pip install ansible==2.6.18 --user
>
> The tar.gz of the releases can be found here:
>
> * 2.8.2
>   https://releases.ansible.com/ansible/ansible-2.8.2.tar.gz
>   SHA256: 1e5ba829ca0602c55b33da399b06f99b135a34014b661d1c36d8892a1e2d3730
> * 2.7.12
>   https://releases.ansible.com/ansible/ansible-2.7.12.tar.gz
>   SHA256: d1e2941087e7778df34af14d2271d16f17ce2dbf03f01043162fb11a0a2708cc
> * 2.6.18
>   https://releases.ansible.com/ansible/ansible-2.6.18.tar.gz
>   SHA256: 588e4d85ec21cddf959a66cbe62bbfcff6236a1cd44b1264b14a19d34b8dffdf
>
>
> What's new in 2.8.2, 2.7.12, and 2.6.18
> ---
>
> These releases contain a security fix for CVE-2019-10156.  In
> addition, the 2.8.2 release is a maintenance release containing
> numerous bugfixes other bugfixes. The full changelogs are at:
>
> * 2.8.2
>   
> https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v2.8.rst
> * 2.7.12
>   
> https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst
> * 2.6.18
>   
> https://github.com/ansible/ansible/blob/stable-2.6/changelogs/CHANGELOG-v2.6.rst
>
>
> What's the schedule for future maintenance releases?
> 
>
> Future maintenance releases will occur approximately every 3 weeks.  So expect
> 2.8.3 around 2019-07-25.
>
> 2.7 and 2.6 are only open for critical and security bugfixes
> respectively so those will see new releases on an as-needed basis.
>
> Porting Help
> 
>
> We've published a porting guide at
> https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.8.html 
> to
> help migrate your content to 2.8.
>
>
> If you discover any errors or if any of your working playbooks break when you
> upgrade to 2.8.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!
>
> -Toshio Kuratomi

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSiYdMZji0NiLPSePE8sAr%3Da9CaiLbMY6e8aZdveGwZPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] New Ansible releases 2.8.2, 2.7.12, and 2.6.18

2019-07-03 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general release of Ansible 2.8.2,
2.7.12, and 2.6.18 are now available!


How do you get it?
--

$ pip install ansible==2.8.2 --user
or
$ pip install ansible==2.7.12 --user
or
$ pip install ansible==2.6.18 --user

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

* 2.8.2
  https://releases.ansible.com/ansible/ansible-2.8.2.tar.gz
  SHA256: 1e5ba829ca0602c55b33da399b06f99b135a34014b661d1c36d8892a1e2d3730
* 2.7.12
  https://releases.ansible.com/ansible/ansible-2.7.12.tar.gz
  SHA256: d1e2941087e7778df34af14d2271d16f17ce2dbf03f01043162fb11a0a2708cc
* 2.6.18
  https://releases.ansible.com/ansible/ansible-2.6.18.tar.gz
  SHA256: 588e4d85ec21cddf959a66cbe62bbfcff6236a1cd44b1264b14a19d34b8dffdf


What's new in 2.8.2, 2.7.12, and 2.6.18
---

These releases contain a security fix for CVE-2019-10156.  In
addition, the 2.8.2 release is a maintenance release containing
numerous bugfixes other bugfixes. The full changelogs are at:

* 2.8.2
  
https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v2.8.rst
* 2.7.12
  
https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst
* 2.6.18
  
https://github.com/ansible/ansible/blob/stable-2.6/changelogs/CHANGELOG-v2.6.rst


What's the schedule for future maintenance releases?


Future maintenance releases will occur approximately every 3 weeks.  So expect
2.8.3 around 2019-07-25.

2.7 and 2.6 are only open for critical and security bugfixes
respectively so those will see new releases on an as-needed basis.

Porting Help


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


If you discover any errors or if any of your working playbooks break when you
upgrade to 2.8.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!

-Toshio Kuratomi

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaTcFEE9bd%2BBJ8c1g5UyozWOEzBdJ2%2BGtTn2uEjiE%3D5_Hw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] New Ansible releases 2.8.1

2019-06-07 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general release of Ansible
2.8.1 is now available!

How do you get it?
--

$ pip install ansible==2.8.1 --user

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

* 2.8.1
https://releases.ansible.com/ansible/ansible-2.8.1.tar.gz
SHA256: e1d51d3a88e21238f9e7a49b2b17a49e76c13880242b936ac8a37aee4fe84445

What's new in 2.8.1
---

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

* 2.8.1

https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v2.8.rst

What's the schedule for future maintenance releases?

Future maintenance releases will occur approximately every 3 weeks. So expect
the next one around 2019-06-27.

Porting Help

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

If you discover any errors or if any of your working playbooks break when you
upgrade to 2.8.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!

-Toshio Kuratomi

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQaw%2BQG1crtnD1QwiJ%3DfxLvzwGEbFUaK0X3nrxnPLYeiw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] New Ansible releases 2.7.11 and 2.6.17

2019-05-23 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general release of Ansible 2.7.11 and
2.6.17 are now available!


How do you get it?
--

$ pip install ansible==2.7.11 --user
or
$ pip install ansible==2.6.17 --user

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

* 2.7.11
  https://releases.ansible.com/ansible/ansible-2.7.11.tar.gz
  SHA256: e7e6de461b7d07cb4d8b2dd2a32b231af7c56e6bf39b851024671aaa52fd377e
* 2.6.17
  https://releases.ansible.com/ansible/ansible-2.6.17.tar.gz
  SHA256: 230c00dd173350b714759d887a868717498d9efaeba0e9315d5d8065c31bb947


What's new in 2.7.11 and 2.6.17
---

These releases are maintenance releases containing numerous bugfixes. The full
changelogs are at:

* 2.7.11
  
https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst
* 2.6.17
  
https://github.com/ansible/ansible/blob/stable-2.6/changelogs/CHANGELOG-v2.6.rst


What's the schedule for future maintenance releases?


These are the last regularly scheduled maintenance releases of
Ansible-2.7.x and Ansible-2.6.x.  From here on, releases of these two
branches will be as needed.  Ansible-2.7.x will continue to get fixes
for critical bugfixes and security issues.  Ansible-2.6.x will only
receive updates for security issues.

Please see the Release and Maintenance page in our docs if you want
more information:
https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html#release-status

Porting Help


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


If you discover any errors or if any of your working playbooks break when you
upgrade to 2.7.11, 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!

-Toshio Kuratomi

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaR_ZgsnJDnmAvZca_0FjE1COq_Om8b65tKLk2GNk8R8BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] New Ansible release 2.8.0

2019-05-16 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general release of Ansible
2.8.0 is now available!


How do you get it?
--

$ pip install ansible==2.8.0 --user

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

* 2.8.0
  https://releases.ansible.com/ansible/ansible-2.8.0.tar.gz
  SHA256: 7234dd7d89150dc5bf035bc1ec3c084a8a0699d89e1c9b06b2af6dd34b2ef3ae


What's new in 2.8.0
---

This release is a new major release containing numerous bugfixes and
features.  A few highlights of the new features:

* Automatic discovery of Python interpreter location for common platforms
* Experimental support for managing Windows hosts via SSH
* Official RHEL8 support including AppStream installation and removal
via the dnf module
* Become plugins which allows sites to customize how ansible escalates
privileges


The full changelog is at:

* 2.8.0
  
https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v2.8.rst


What's the schedule for future maintenance releases?


Future maintenance releases will occur approximately every 3 weeks.  So expect
the next one around 2019-06-06.


Porting Help


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


If you discover any errors or if any of your working playbooks break when you
upgrade to 2.8.0, 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!

-Toshio Kuratomi

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaT3N4ZpzKPY1%2BFJZgEGEXKv0XGFhvk1sS4vMQ0%3DHbvmjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] New Ansible release 2.7.10 and 2.6.16

2019-04-04 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general release of Ansible 2.7.10 and
2.6.16 is now available!


How do you get it?
--

$ pip install ansible==2.7.10 --user
or
$ pip install ansible==2.6.16 --user

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

* 2.7.10
  https://releases.ansible.com/ansible/ansible-2.7.10.tar.gz
  SHA256: 84a42d1e371c4222c82e575cb6961fafd3afe920d84e4b6d87affabe400be294
* 2.6.16
  https://releases.ansible.com/ansible/ansible-2.6.16.tar.gz
  SHA256: e883fe2a662bdd1f6e8bbe03caf1d8466fda6caba2a771528dc17b31a91d2716


What's new in 2.7.10 and 2.6.16
---

These releases are maintenance release containing numerous bugfixes. The full
changelogs are at:

* 2.7.10
  
https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst
* 2.6.16
  
https://github.com/ansible/ansible/blob/stable-2.6/changelogs/CHANGELOG-v2.6.rst


What's the schedule for future maintenance releases?


A few non-standard things to note about future maintenance releases
this time around:

* As you may be aware, 2.8.0-alpha1 is scheduled to come out very
soon, with 2.8.0 final scheduled for mid-May.  The run up to 2.8.0
final includes many prereleases so there will be quite a bit of work
for release engineering to do.  As such, the next maintenance release
for 2.7.x (2.7.11) and 2.6.x  (2.6.17) will come after 2.8.0 final is
out.  If 2.8.0 does not slip further, those releases will come out on
May 23rd.

* 2.7.11 and 2.6.17 will also mark the transition from regularly
scheduled maintenance releases for those two branches to as-needed
releases.  2.7.x will have further releases if there's a bugfix deemed
critical while 2.6.x will have further releases if there's a security
bug that needs fixing.[1]_

* For contributors, this means that those wanting to get bugfixes in
to 2.7.x or 2.6.x should get it merged to devel and the backport
merged to the stable branch before May 20th.  This is the date that
the backport needs to be merged so you should try to have the backport
PR opened well before that.  Otherwise you may not have time to
address any problems that are noticed in the backport before May 20th
has come and gone.

.. [1]_: If you want more information about the lifecycle of an
Ansible release, please see:
https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html#development-and-stable-version-maintenance-workflow

Porting Help


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


If you discover any errors or if any of your working playbooks break when you
upgrade to 2.7.10, 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!

-Toshio Kuratomi

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaRdMXHS2sN3vnOn%2Bo2OtdOGgBBurzapYTBtPbPq3W9zQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.7.9 and 2.6.15

2019-03-15 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general release of Ansible
2.7.9 and Ansible 2.6.15 are now available!

How do you get it?
--

$ pip install ansible==2.6.15 --user
or
$ pip install ansible==2.7.9 --user

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

* 2.7.9
https://releases.ansible.com/ansible/ansible-2.7.9.tar.gz
SHA256:
* 2.6.15
https://releases.ansible.com/ansible/ansible-2.6.15.tar.gz
SHA256:

What's new in 2.7.9 and 2.6.15?
---

These releases are maintenance releases containing numerous bugfixes.
The full changelog is at:

* 2.7.9

https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst
* 2.6.15

https://github.com/ansible/ansible/blob/stable-2.6/changelogs/CHANGELOG-v2.6.rst

What's the schedule for future maintenance releases?

Future maintenance releases will occur approximately every 3 weeks.
So expect the next one around April 4th.

We've published a porting guide at
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.7.html
to help migrate your content to 2.7. If you discover any errors, or if
you see any regressions from playbooks which work on 2.7.8 and prior,
please open a GitHub issue, and be sure to mention you're using 2.7.9.

Thanks!

-Toshio Kuratomi

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaReQaRnwg2fQJ%3DT9tqxZo_eF0HravVzz4Z-U55PiHZ%2BmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.7.8, 2.6.14, and 2.5.15

2019-02-21 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general release of Ansible
2.7.8, Ansible 2.6.14, and Ansible 2.5.15 are now ready to be
installed.

How do you get it?
--

$ pip install ansible==2.7.8 --user
or
$ pip install ansible==2.6.14 --user
or
$ pip install ansible==2.5.15 --user

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

* 2.7.8
https://releases.ansible.com/ansible/ansible-2.7.8.tar.gz
SHA256: 3d67db258b492f3c8828c68dcb92438e67cb5b20c12924089eafdc0ada3edd87
* 2.6.14
https://releases.ansible.com/ansible/ansible-2.6.14.tar.gz
SHA256: 412f130f4c5d1953ccd95f01b5a4675cbff4ba225762bafb74a2f3bb6c807827
* 2.5.15
https://releases.ansible.com/ansible/ansible-2.5.15.tar.gz
SHA256: ffbc2b093290c72a0a79be457ba47c57ecce7f32d65418fadc064ba1c3763cf1

What's new in 2.7.8, 2.6.14, and 2.5.15?

These releases are maintenance releases containing numerous bugfixes.
Of special note is that these releases fix CVE-2019-3828 where a
compromised remote machine could cause ansible's fetch module to
overwrite files on the Ansible controller. The full changelog is at:

* 2.7.8

https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst
* 2.6.14

https://github.com/ansible/ansible/blob/stable-2.6/changelogs/CHANGELOG-v2.6.rst
* 2.5.15

https://github.com/ansible/ansible/blob/stable-2.5/changelogs/CHANGELOG-v2.5.rst

What's the schedule for future maintenance releases?

Ansible 2.5 is in security fix-only mode so there will only be another
release if it's needed to fix a security bug. Ansible 2.6 and Ansible
2.7 have maintenance releases approximately every 3 weeks. So expect
the next one around March 14th.

We've published a porting guide at
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.7.html
to help migrate your content to 2.7. If you discover any errors, or if
you see any regressions from playbooks which work on 2.7.7 and prior,
please open a GitHub issue, and be sure to mention you're using 2.7.8.

Thanks!

-Toshio Kuratomi

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSmmARwuv%3DfVT9BALQF-9Dc7zxR9OmCVs%3DUyXYH3akjUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Dropping Fedora rpms from https://releases.ansible.com/

2019-02-18 Thread Toshio Kuratomi

Hey all,

Recently we had a discussion internally about whether to build
upstream Ansible rpms on Fedora 29 using Python3 or Python2. This
lead to a question about how useful the Fedora rpms Ansible releases
on https://releases.ansible.com/ are. We found that for each of the
Fedora releases, the rpms are being downloaded 300-350 times a week
(including downloads that seem to simply be mirrors of all of the rpms
we've built).

By comparison, our builds for EPEL-7 are seeing about 8,800 downloads a week.

Given this, we're thinking that we should stop building rpms for
Fedora and instead encourage people to use the rpms provided by the
Fedora Project themselves (which will tend to be more responsive to
changes in Fedora's packaging ecosystem... for instance, they have
Ansible rpms on Fedora 29 which use Python3, the default python for
that version of the distro).

If anyone uses our rpms in preference to the Fedora rpms, could you
let us know that you do so and why you use them over the ones provided
by Fedora? If we don't hear of a good reason to do so, we'll probably
stop building for Fedora in a release or two.

Thanks,
-Toshio

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQBcyYyTxwaBmpgatvU4NDge1c1CGyu%3DEJuTpY%2B-Tvoeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project]

2019-02-07 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general release of Ansible
2.7.7 and Ansible 2.6.13 are now available!

How do you get it?
--

$ pip install ansible==2.6.13 --user
or
$ pip install ansible==2.7.7 --user

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

* 2.7.7
https://releases.ansible.com/ansible/ansible-2.7.7.tar.gz
SHA256: 040cc936f959b947800ffaa5f940d2508aaa41f899efe56b47a7442c89689150
* 2.6.13
https://releases.ansible.com/ansible/ansible-2.6.13.tar.gz
SHA256: 96fbddc5b6a394d2a3259b23847611a61e8d24c5aca6f4325a9aabca54817f05

What's new in 2.7.7 and 2.6.13?
---

These releases are maintenance releases containing numerous bugfixes.
The full changelog is at:

* 2.7.7

https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst
* 2.6.13

https://github.com/ansible/ansible/blob/stable-2.6/changelogs/CHANGELOG-v2.6.rst

What's the schedule for future maintenance releases?

Future maintenance releases will occur approximately every 3 weeks.
So expect the next one around February 28th.

We've published a porting guide at
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.7.html
to help migrate your content to 2.7. If you discover any errors, or if
you see any regressions from playbooks which work on 2.7.6 and prior,
please open a GitHub issue, and be sure to mention you're using 2.7.7.

Thanks!

-Toshio Kuratomi

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaS7rLTRUSFnBAYUPf7Z0opf%3DLr2cPodcs_dQB3Vqoy8xA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.7.6 and 2.6.12

2019-01-17 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general releases of Ansible
2.7.6 and Ansible 2.6.12 are now available!




How do you get it?
--


$ pip install ansible==2.7.6 --user

or

$ pip install ansible==2.6.12 --user

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


https://releases.ansible.com/ansible/ansible-2.7.6.tar.gz
SHA256: 6d855ead966c1a24a7d583ddcea8dd9e1f6edab3207390b647149351e113eb38


https://releases.ansible.com/ansible/ansible-2.6.12.tar.gz
SHA256: c6fd83991df90de75330fe4cd00cb837446b4f946a699903cf4ab6e40eb24cd2


What's new in 2.7.6 and 2.6.12?
--


The 2.7.6 and 2.6.12 releases are maintenance releases containing
numerous bugfixes. The full changelogs are at:


* 
https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst

* 
https://github.com/ansible/ansible/blob/stable-2.6/changelogs/CHANGELOG-v2.6.rst



What's the schedule for future 2.7 and 2.6 maintenance releases?
--


Future 2.6 adn 2.7 maintenance releases will occur approximately every 3 weeks.




We've published porting guides to help migrate your content to 2.6 and 2.7:

* https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.7.html
* https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.6.html

If you discover any errors, or if you see any regressions from
playbooks which work on early releases, please open a Github issue,
and be sure to mention which Ansible release you're using.



Thanks!

-Toshio Kuratomi

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaR%3DNJqY8DE75YnCU-%3DVpvcs-az5xkGtd5H-mfpoPSnsiA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.5.14, 2.6.11, and 2.7.5 are available

2018-12-13 Thread Toshio Kuratomi

Hi all,

Ansible 2.5.14, 2.6.11, and 2.7.5 were released today. These releases
include a fix for a reported security vulnerability, CVE-2018-16876
https://bugzilla.redhat.com/show_bug.cgi?id=1657330 as well as other
general bugfixes.

CVE-2018-16876 prevented Ansible from respecting the no_log task
setting for ssh output when verbosity was high and Ansible had to
retry the ssh connection.

The new releases are available via the usual installation methods on
PyPI, https://releases.ansible.com/ansible/, and on GitHub. Detailed
installation instructions are available at
https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html.

The next releases for the 2.6 and 2.7 series are expected in January,
after the winter holiday season is over. 2.5 will only release for
security updates.

Changelog links for each release and tarball SHAs from releases.ansible.com:
- 2.7.5
URL: https://releases.ansible.com/ansible/ansible-2.7.5.tar.gz
Changelog:
https://github.com/ansible/ansible/blob/v2.7.5/changelogs/CHANGELOG-v2.7.rst
SHA256: aaf9e1974bd12840ca055ac156f37601c08d73d726a3a6b98a2fe759a57051bb
ansible-2.7.5.tar.gz

- 2.6.11
URL: https://releases.ansible.com/ansible/ansible-2.6.11.tar.gz
Changelog:
https://github.com/ansible/ansible/blob/v2.6.11/changelogs/CHANGELOG-v2.6.rst
SHA256: 2cc41e51a70a0e37d7db29e2f16af137bf548c3372fec4f7b48cc0575da55e32
ansible-2.6.11.tar.gz

- 2.5.14
URL: https://releases.ansible.com/ansible/ansible-2.5.14.tar.gz
Changelog:
https://github.com/ansible/ansible/blob/v2.5.14/changelogs/CHANGELOG-v2.5.rst
SHA256: 695ac8ebce0be57062924ff90f4b98cd61caa99cd21cdb10a964e3320524a069
ansible-2.5.14.tar.gz

-Toshio Kuratomi (@abadger1999)

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaRZseeAEfxFT8MegMEMuOsooSZWFWArO1XsTiGpuunr0w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] [WARNING]: The src option requires state to be 'link' or 'hard'. This will become an error in Ansible 2.10

2018-11-26 Thread Toshio Kuratomi

>From the name of your task, it looks like you mean to use copy:, not file:

-Toshio

On Mon, Nov 26, 2018, 6:19 PM Ronnie10  Hi All,
>
> I have the following ansible codes, however when I run molecule test, it
> gave me the error as my subject, anyway to fix that?
>
> - name: Copy  file to config folder
>   file:
> src: files/
> dest: "PATH/config/"
> mode: 0644
>
>
> Thank you.
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/119b5ce3-1ba4-4056-a568-15c00ed6775c%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQyBZdAsi1Dmc%3D5ga2GPgYKJC8GqU%2BBVAQYAKjFH-NNjw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible-2.7.2

2018-11-15 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general release of Ansible
2.7.2 is now available!

How do you get it?
--

$ pip install ansible==2.7.2 --user

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

https://releases.ansible.com/ansible/ansible-2.7.2.tar.gz
SHA256: a00d79531e4e0268321e431b1810286369ecf791dbebc1aecb28d453d4ea1ee0

What's new in 2.7.2?
--

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

https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst

What's the schedule for future 2.7 maintenance releases?
--

We aim to publish a 2.7.x maintenance release approximately every 3
weeks. For 2.7.3 we've already identified several fixes that we'd
like to get in sooner rather than later so, as a one-off, we are
shooting to release 2.7.3 2 weeks from now rather than 3 weeks from
now.

We've published a porting guide at
https://docs.ansible.com/ansible/2.7/porting_guides/porting_guide_2.7.html
to help migrate your content to 2.7. If you discover any errors, or if
you see any regressions from playbooks which work on 2.6.x and prior,
please open a Github issue, and be sure to mention you're using 2.7.2.

Thanks!

-Toshio Kuratomi

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSe%2B77KoSn2fHp1U%3Dua-rq-9vnwBNOQWLxQze8%2BAePVZw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] How to reopen issue in ansible (github)

2018-11-07 Thread Toshio Kuratomi

Open a new issue.  If you think it is related to the old issue, link to the
old issue in the new one.

Since that issue says that the issue was fixed, testing with the version
containing the fix could tell us if there was a regression versus a new and
unrelated problem.

On Wed, Nov 7, 2018, 4:29 AM ProfHase  Hi @all,
>
> could someone please tell me and/or reopen the following issue:
>
> https://github.com/ansible/ansible/issues/25046
>
> The issue is closed and is supposed to be fixed for 2.3 , it still exists
> in 2.6, though
>
> Thanks a lot
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/208ff96a-c51c-44b8-9446-a0f6f23c4e08%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQ%3D%3DpNQgpaqfdKEz5cVqDb1-HOZANq9NBQHfr-N-Pcrfw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible-2.7.1 is released

2018-10-25 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general release of Ansible
2.7.1 is now available!

How do you get it?
--

$ pip install ansible==2.7.1 --user

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

https://releases.ansible.com/ansible/ansible-2.7.1.tar.gz
SHA256: e7953472347fcc6dca10839111b576a9f790e00056344f2dcf448e6c452fe939

What's new in 2.7.1?
--

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

https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst#v2-7-1

What's the schedule for future 2.7 maintenance releases?
--

Future 2.7 maintenance releases will occur approximately every 3 weeks.

Thanks!

-Toshio Kuratomi (abadger1999)

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaRVyigMqeHjDgCgK65SJNLOA-igh3_YdaTTHHSPXshD8A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Ansible 2.7 yum module issues

2018-10-17 Thread Toshio Kuratomi

Are you able to grab the yum module from the stable-2. 7 bench to give it a
try?  There were a couple fixes to it after 2.7.0 and are merged for
2.7.1.  i know at least one had to do with config files but i don't recall
the symptoms so i can't be sure it's the same thing.

https://github.com/ansible/ansible/blob/stable-2.7/lib/ansible/modules/packaging/os/yum.py

-Toshio


On Wed, Oct 17, 2018, 2:36 PM 'Chris Bidwell - NOAA Federal' via Ansible
Project  wrote:

> Anyone notice weirdness with ansible 2.7?  I'm running 2.7.0 and the yum
> module doesn't seem to be working as it's supposed to.  Previous ran
> ansible 2.6.x with success.  Same module under 2.7.0:
> fatal: [172.23.10.2]: FAILED! => {"changed": false, "msg": "Error from
> repoquery: ['/usr/bin/repoquery', '--show-duplicates', '--plugins',
> '--quiet', '-c', None, '--disablerepo', '', '--enablerepo', '', '--qf',
> '%{epoch}:%{name}-%{version}-%{release}.%{arch}', 'glusterfs']: Error
> accessing file for config file:///home/tsg/--disablerepo\nError accessing
> file for config file:///home/tsg/--disablerepo\n"}
>
> I have no reference to file:///home/tsg/--disablerepo.  I don't know where
> it's pulling this from.
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/CAHKi8Ci4PkV8zETki%3Dm%3DTYv87%2Bb%3D7L2HhVpLJgBA-%2B7GbTUPWw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSKgjSjzV0AUwtZ%2B3A297JoN%3Dwsk2ET0nB1agTZXRyp9g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Re: how to use an pipe like < < in ansible ?

2018-10-10 Thread Toshio Kuratomi

Without an error message I'm not sure whether I'm looking at the same
thing but this looks like a portability problem with the shell script
you are attempting to use.

In /bin/sh (implemented by bash), I get the following error:

$ /bin/sh *[stable-2.7]  (10:54:10)
sh-4.4$ read HELLO_WORLD <<(/bin/expr 1 + 1) ; echo $HELLO_WORLD
sh: syntax error near unexpected token `('

Similarly /bin/bash:

$ /bin/bash   *[stable-2.7]  (10:54:31)
[badger@peru:16 stable-2.7]$ read HELLO_WORLD <<(/bin/expr 1 + 1) ;
echo $HELLO_WORLD
bash: syntax error near unexpected token `('

In /bin/zsh, I can get it to work, though:
$ /bin/zsh*[stable-2.7]  (10:54:36)
[pts/16@peru /srv/ansible/stable-2.7]$ read HELLO_WORLD <<(/bin/expr 1
+ 1) ; echo $HELLO_WORLD
2

So if you have zsh installed, you could write your ansible command like this:
$ ansible localhost -m shell -a 'executable=/bin/zsh read HELLO_WORLD
<<(/bin/expr 1 + 1) ; echo $HELLO_WORLD'
localhost | CHANGED | rc=0 >>
2

And the equivalent playbook:
---
- hosts: localhost
  gather_facts: False
  tasks:
  - shell: read HELLO_WORLD <<(/bin/expr 1 + 1) ; echo $HELLO_WORLD
args:
  executable: /bin/zsh

However, for things that involve multiple commands, it is usually more
maintainable to write the shell script into a file, test that the
shell script works, and then use the script module to execute it:

$ cat script.zsh  *[stable-2.7]  (11:07:34)
#!/bin/zsh
read HELLO_WORLD <<(/bin/expr 1 + 1)
echo $HELLO_WORLD

[pts/16@peru /srv/ansible/stable-2.7]$ cat mine.yml
*[stable-2.7]  (11:07:38)
---
- hosts: localhost
  gather_facts: False
  tasks:
  - script: script.zsh

-Toshio

On Wed, Oct 10, 2018 at 2:45 AM Henrik Schuetze  wrote:
>
> no. this doesnt work, because the shell command only support one "<"
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ansible-project/df773577-94d0-422f-a9e4-fa72b45e814e%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaRNLe94Fgt1zrZ_6PrwONJvHCHE_UUfW%2BUqgT%2BxpQRYMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] 2.7.0 Final has been released!

2018-10-04 Thread Toshio Kuratomi

Hi all- we're happy to announce that the general release of Ansible
2.7.0 is now available!

How do you get it?
--

$ pip install ansible --user

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

https://releases.ansible.com/ansible/ansible-2.7.0.tar.gz
SHA256: a1ab8e0f13e79a20661ad6546f45a142afeaeb664deb2c290e32362d8ae5b618

What's new in 2.7.0?
--

The 2.7.0 release contains numerous new features and bugfixes. The
full changelog is at:

https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst

What's the schedule for future 2.7 maintenance releases?
--

Future 2.7 maintenance releases will occur approximately every 3 weeks.

Thanks!

Toshio Kuratomi (@abadger)
Ansible Core Engineering / 2.7 release manager

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaRNC0XMrqOyz-uEipJFaXGHCP_Mmc6%2B49MUAV9CQ%2BBiwA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] unicode, json...

2018-09-01 Thread Toshio Kuratomi

It appears that nlb contains a string.  Perhaps because of the  initial space in
```
nlb: " {{ nlb.stdout |from_json }}"
```
?

On Fri, Aug 31, 2018 at 10:12 PM, Karl Auer  wrote:
> I have an AWS CLI command that returns this (I've truncated it):
>
> changed: [localhost] => {"changed": true, "cmd": ["aws", "elbv2",
> "create-load-balancer", "--name", "ADFS-ext-nlb", "--type", "network",
> "--subnet-mappings",
> "SubnetId=subnet-c1580ba5,AllocationId=eipalloc-09644c10a5aac6a39
> SubnetId=subnet-3cd85265,AllocationId=eipalloc-09c95f8e4f8e111b2  "],
> "delta": "0:00:02.343846", "end": "2018-09-01 14:13:21.199441", "rc": 0,
> "start": "2018-09-01 14:13:18.855595", "stderr": "", "stderr_lines": [],
> "stdout": "{\n\"LoadBalancers\": [\n{\n\"Scheme\":
> \"internet-facing\",\n\"State\": {\n\"Code\":
> \"active\"\n},\n\"DNSName\":
> \"ADFS-ext-nlb-722a4422c412e03e.elb.ap-southeast-2.amazonaws.com\",\n
>
> I have converted it into json like this:
>
> - set_fact:
>  nlb: " {{ nlb.stdout |from_json }}"
>
> And the output from that is this:
>
> TASK [nlb : set_fact]
> 
> ok: [localhost] => {"ansible_facts": {"nlb": " {u'LoadBalancers':
> [{u'IpAddressType': u'ipv4', u'Scheme': u'internet-facing',
> u'LoadBalancerArn':
> u'arn:aws:elasticloadbalancing:ap-southeast-2:375939078089:loadbalancer/net/ADFS-ext-nlb/722a4422c412e03e',
> u'VpcId': u'vpc-8bc156ef', u'State': {u'Code': u'active'}, u'DNSName':
> u'ADFS-ext-nlb-722a4422c412e03e.elb.ap-southeast-2.amazonaws.com',
> u'LoadBalancerName': u'ADFS-ext-nlb', u'CreatedTime':
> u'2018-09-01T03:10:47.036Z', u'AvailabilityZones': [{u'SubnetId':
> u'subnet-c1580ba5', u'ZoneName': u'ap-southeast-2b',
> u'LoadBalancerAddresses': [{u'IpAddress': u'52.64.194.159', u'AllocationId':
> u'eipalloc-09c95f8e4f8e111b2'}]}], u'Type': u'network',
> u'CanonicalHostedZoneId': u'ZCT6FZBF4DROD'}]} "}, "changed": false}
>
> I want to extract a LoadBalancerArn from that, but I can't seem to refer to
> the internal structure. I won't list here all the various syntactical
> variations I've tried! What I want is something like this:
>
> - set_fact:
>  lb_arn: "{{ nlb.LoadBalancers[0].LoadBalancerArn }}"
>
> No matter what I try I always get something like this:
>
> fatal: [localhost]: FAILED! => {"msg":
> "'ansible.utils.unsafe_proxy.AnsibleUnsafeText object' has no attribute
> 'LoadBalancers'"}
>
> Is this because of the unicode? Or am I missing something else?
>
> Regards, K.
>
> --
> Karl Auer
>
> Email  : ka...@2pisoftware.com
> Website: http://2pisoftware.com
>
> GPG/PGP : 958A 2647 6C44 D376 3D63 86A5 FFB2 20BC 0257 5816
> Previous: F0AB 6C70 A49D 1927 6E05 81E7 AD95 268F 2AB6 40EA
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/CA%2B%2BT08SRo77WjJ8cEHbqBDKG7EVbFRRtw5y8kUvfL086H_Nicg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaRkpz90ZUx3UDWa9H2mDrGDprf56ttjTMmUyG-4ofKtOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Re: issue with ansible dry-run mode (--check) on package installation tasks (yum and apt modules)

2018-05-10 Thread Toshio Kuratomi

The yum task succeeded. It's the subsequent fail that is failing.  You can
make any other module +fail react in the same way:

- file: path=/var/tmp/i_do_not_exist_yet state=directory
- stat:
  path: /var/tmp/i_do_not_exist_yet
  register: file

- fail:
msg: "File i_do_not_exist_yet doesn't exist!"
  when: file.stat.exists == False

As flowerysong says, --check means, do not make any changes to the system.
So you cannot run ansible in check-mode and then expect an assertion that a
change was made to succeed.  Similarly, you cannot expect that running a
second task which depends on the first task to have changed the system in
some way to succeed in check-mode because the change will not have been
made to the system.

-Toshio

On Thu, May 10, 2018, 10:56 PM js.a  wrote:

> @flowerysong
>
> The point is, a CI tool such as Travis, Tower... will report error on that
> task, but actually there is no error at all (normal running). In addition,
> package installing task is just 0,5% of the whole deployment project and
> thinking deeper, every task does changes on the systems. Many ansible other
> modules I have used do work in --check mode, except package manager which I
> am reporting here.
>
> ---
>
> Em quinta-feira, 10 de maio de 2018 02:06:38 UTC-3, flowerysong escreveu:
>>
>> On Thursday, May 10, 2018 at 12:11:02 AM UTC-4, js.a wrote:
>>>
>>> Hello guys.
>>>
>>> I'm here to bring an issue with Ansible dry-run (--check) mode. I have
>>> been facing a curious situation where package installation made using
>>> Playbooks and run in a dry-run mode is not working as expected. Using
>>> register+debug module it's possible to see that the package has been
>>> successfully installed, but when I try to use that installed package in
>>> later task, Ansible fails.
>>>
>>> *My Playbook:*
>>>
>>> ---
>>> - hosts: logging
>>>   become: yes
>>>
>>>   tasks:
>>> - name: Setting up EPEL
>>>   yum: name=epel-release state=present
>>>   register: inst
>>> - debug: var=inst
>>>
>>> - name: Checking installation
>>>   stat:
>>> path: /etc/yum.repos.d/epel.repo
>>>   register: file
>>>
>>> - fail:
>>> msg: "File epel.repo doesn't exist!"
>>>   when: file.stat.exists == False
>>>
>>> *Result:*
>>>
>>> [root@c7 projX]# ansible-playbook -i inventory epel.yml --check
>>>
>>> PLAY [logging]
>>> ***
>>>
>>> TASK [Gathering Facts]
>>> ***
>>> ok: [192.168.52.20]
>>>
>>> TASK [Setting up EPEL]
>>> ***
>>> changed: [192.168.52.20]
>>>
>>> TASK [debug]
>>> *
>>> ok: [192.168.52.20] => {
>>> "inst": {
>>> "changed": true,
>>> "changes": {
>>> "installed": [
>>> "epel-release"
>>> ]
>>> },
>>> "failed": false,
>>> "results": []
>>> }
>>> }
>>>
>>> TASK [Checking installation]
>>> *
>>> ok: [192.168.52.20]
>>>
>>> TASK [fail]
>>> **
>>> fatal: [192.168.52.20]: FAILED! => {"changed": false, "msg": *"File
>>> epel.repo doesn't exist!"*}
>>>
>>> PLAY RECAP
>>> ***
>>> 192.168.52.20  : ok=4changed=1unreachable=0
>>> failed=1
>>>
>>>
>>> ---
>>>
>>> If I take '--check' for dry-run out of the command it does work, but
>>> it's not the best approach for me once I'm planning to put this "checking
>>> task" in a CI software to "automate the automation".
>>>
>>> My question is: is there any specific reason for that case (package
>>> installation) not to work with --check parameter? I've done further tests
>>> using Ubuntu and the Ansible's apt module but the same problem comes up.
>>>
>>
>> The whole point of check mode is that it doesn't make changes to the
>> system. If you want things to change (e.g. packages to install), don't run
>> in check mode.
>>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/19f62a98-3ae0-4515-9da1-8058a7805dba%40googlegroups.com
> 
> .
> For more

Re: [ansible-project] ansible replace with_items prepends the letter 'u'

2018-05-04 Thread Toshio Kuratomi

Is it showing up in your sshd_config file or just in the display of what
each item was?

-Toshio

On Fri, May 4, 2018, 8:55 AM  wrote:

> I'm trying to use the replace module to update SSL ciphers and seem to be
> running into a Unicode issue.
>
> The code:
>
> ---
> - hosts: all
>   gather_facts: False
>   become: True
>   vars:
> text_for_EL6:
>   - { regexp: '^KexAlgorithms', line: 'KexAlgorithms
> diffie-hellman-group-exchange-sha256' }
>   - { regexp: '^MACs', line: 'MACs hmac-sha2-512,hmac-sha2-256' }
>   - { regexp: '^Ciphers', line: 'Ciphers
> aes256-ctr,aes192-ctr,aes128-ctr' }
> text_for_EL7:
>   - { regexp: '^KexAlgorithms', line: 'KexAlgorithms
> curve25519-sha...@libssh.org,ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group-exchange-sha256'
> }
>   - { regexp: '^Ciphers', line: 'Ciphers chacha20-poly1...@openssh.com
> ,aes256-...@openssh.com,aes128-...@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr'
> }
>   - { regexp: '^MACs', line: 'MACs hmac-sha2-512-...@openssh.com,
> hmac-sha2-256-...@openssh.com,umac-128-...@openssh.com
> ,hmac-sha2-512,hmac-sha2-256,umac-...@openssh.com' }
>
>   tasks:
>   - name: check and store ssh version
> shell: rpm -qa openssh
> register: ssh_version_result
>
>   - name: Set ciphers for EL6 - OpenSSL 5.3
> replace:
>   backup: yes
>   path: /etc/ssh/sshd_config
>   regexp: '{{ item.regexp }}'
>   replace: '{{ item.line }}'
> when: ssh_version_result.stdout.find('openssh-5') != -1
> with_items:
>   - "{{text_for_EL6}}"
> notify: restart sshd
>
>   - name: Set ciphers for EL7 - OpenSSL > 6.7
> replace:
>   backup: yes
>   path: /etc/ssh/sshd_config
>   regexp: '{{ item.regexp }}'
>   replace: '{{ item.line }}'
> when: ssh_version_result.stdout.find('openssh-7') != -1
> with_items:
>   - "{{text_for_EL7}}"
> notify: restart sshd
>
>   handlers:
>   - name: restart sshd
> service: name=sshd state=restarted
> ...
>
> The result:
>
> $ ansible-playbook update_sshd_ciphers.yml --limit my_server
> SUDO password:
>
> PLAY [all]
> 
>
> TASK [check ssh versions]
> *
>  [WARNING]: Consider using yum, dnf or zypper module rather than running
> rpm
>
> changed: [my_server]
>
> TASK [Set ciphers for EL6 - OpenSSL 5.3]
> **
> skipping: [my_server] => (item={u'regexp': u'^KexAlgorithms', u'line':
> u'KexAlgorithms diffie-hellman-group-exchange-sha256'})
> skipping: [my_server] => (item={u'regexp': u'^MACs', u'line': u'MACs
> hmac-sha2-512,hmac-sha2-256'})
> skipping: [my_server] => (item={u'regexp': u'^Ciphers', u'line':
> u'Ciphers aes256-ctr,aes192-ctr,aes128-ctr'})
>
> TASK [Set ciphers for EL7 - OpenSSL > 6.7]
> 
> ok: [my_server] => (item={u'regexp': u'^KexAlgorithms', u'line':
> u'KexAlgorithms curve25519-sha...@libssh.org
> ,ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group-exchange-sha256'})
> ok: [my_server] => (item={u'regexp': u'^Ciphers', u'line': u'Ciphers
> chacha20-poly1...@openssh.com,aes256-...@openssh.com,
> aes128-...@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr'})
> ok: [my_server] => (item={u'regexp': u'^MACs', u'line': u'MACs
> hmac-sha2-512-...@openssh.com,hmac-sha2-256-...@openssh.com,
> umac-128-...@openssh.com,hmac-sha2-512,hmac-sha2-256,umac-...@openssh.com
> '})
>
> PLAY RECAP
> 
> my_server  : ok=2changed=1unreachable=0
> failed=0
>
> I am not certain but I think the prepended 'u' is the problem.
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit
>

Re: [ansible-project] Ansible custom module_utils in Ansible 2.1 & 2.2

2018-04-18 Thread Toshio Kuratomi

On Tue, Apr 17, 2018, 11:35 PM Raja Shekar  wrote:
>
> Hi,
>
> I am working on Juniper.junos role. We are trying to correct our module_utils 
> import style to include ansiballz framework. Currently, for our role we 
> support Ansible >= 2.1. I understand that there was no custom module_utils 
> support in Ansible 2.1, 2.2 . I need help with a workaround that lets me use 
> ansiballz for Ansible > 2.2 and the import_juniper_junos_common function for 
> Ansible <= 2.2.
>
> Using ansible.module_utils fails in Ansible < 2.2  as it searches for  string 
> `from ansible.module_utils` in module code and changes the module_style & 
> module_substyle to 'new'. The custom module_utils support is not provided in 
> Ansible < 2.2.
>
> As a workaround, we decided to use imp library to import from 
> ansible.module_utils in Ansible > 2.2 ,else use import_juniper_junos_common 
> function.This workaround fails in Ansible > 2.2 as ansiballz doesn't 
> recognise the import statement and hence doesn't package module_utils code 
> into zip.
>
> Any pointers on how to make this work ??
>
> Ansible Core code snippet causing the error: Ansible snippet
>
>
> import_juniper_junos_common function
>
>
>
First, I should warn you that what you are attempting is very likely
to turn into a large time sink without a fully satisfactory outcome on
the other side.  You should probably reevaluate the scope of what you
are doing.  Ask yourself these questions:

* Why support ansible less than 2.4?  2.3 and earlier are unsupported
by upstream. Any bugs there (including security bugs) will never be
fixed.

* Why try to shoehorn this into the ansible.module_utils framework? It
will be much easier to work with such old versions and current
versions and potentially new versions if you make your common code
into a library that is installed by the users into the remote machine
(host it on pypi for users to pip install or make system packages for
them to use their favorite distro tools or come up with something in
your own role that drops the file into a known location so your module
can add it to sys.path).  You can also have your users install your
extensions into ansible's official module_utils directory on their
control machines.  Then ansible can find it when it constructs modules
to send over the wire.

* Working at such a low level runs the risk of breaking when we next
enhance how modules are processed, sent over the wire, and invoked
remotely.  A simpler solution that deviates less from the standard way
modules operate is less likely to break.

Those disclaimers out of the way, the first thing to figure out is
what your parameters actually are.  You talk about adding custom
module_utils, circumventing ansiballz, and using imp in your module to
import your custom module_utils however, these are three different
things.

Ansiballz is the way we locate module_utils and package them together
with the module to be sent over the wire for execution by python on
the remote machine.  It seems for your purposes you are trying to make
use of this to bundle your module_utils file with your modules
automatically. This had been available since 2.1.

Custom module_utils allows you to put a module_utils file into a
directory other than site-packages/ansible/module_utils and ansiballz
will find it when searching for the libraries it will package with the
module to transport over the wire.  This has been available since 2.3.

Loading of libraries in the modules is entirely separate from the
latter two.  You are free to add to sys.path inside of the module or
imp.load inside of the module but those won't affect what ansiballz
found on the controller side.

Taking a look at the code here:
https://github.com/Juniper/ansible-junos-stdlib/blob/master/library/juniper_junos_facts.py#L174
 (Let me know if that's not the code that you are using), I think that
you're sorta taking the route that I mentioned above about trying not
to use the module_utils facility since you want to support old
versions of Ansible.  Instead of hardcoding a path that your installer
establishes as I suggested, it looks like you've chosen to make that
path configurable via a module parameter.  That seems like it will
work fine.  It steps entirely outside of the AnsiballZ framework so
there won't be conflicts with it.

So it looks like the problem is you want to both use this code which
circumvents AnsiballZ and also *not* circumvent AnsiballZ.  That's not
going to work.  If you're going to work outside of the framework you
need to stay outside of the framework.  If you're going to work within
the framework, you need to stay within the framework.  AnsiballZ scans
module and  module_utils code for python imports (Not a specific
string, btw, but imports in the abstract syntax tree).  Any imports of
module_utils code that it finds are used to include those module_utils
into an archive with the module code and shipped to the remote machine
for execution.  There is no

[ansible-project] Subject: Ansible 2.4.4.0 Final released

2018-04-04 Thread Toshio Kuratomi

Hi all, For everyone who has not yet decided to upgrade to
ansible-2.5.0 we're happy to announce that ansible- 2.4.4.0 has been
released.

--
How do you get it?

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

https://releases.ansible.com/ansible/ansible-2.4.4.0.tar.gz
SHA256: 2b02756b9b6bc02d9028a4577ef332f8126c607528e18db825672b0301343358

You can also install it via pip by pinning the version:
$ pip install ansible==2.4.4.0

Or you can retrieve the release from the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.4.4.0-1

You can then source our testing script:

$ . hacking/env-setup

or you can build your own .tar.gz (output will be dist/ansible-2.4.4.0.tar.gz):

$ make sdist

--
This is the last regularly scheduled release in the 2.4.x series.
We'll make further 2.4.x releases if we discover critical or security
bugs that must be fixed while 2.4.x is still supported but the
majority of new bugfixes will be made to the 2.5.x release series.

Thanks to everyone who's participated in bug reporting and bug fixing
to make this release possible!

-Toshio

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaRFighjF09RXPYoVCiozW%3DDDtCwh_DNPpSbqep%3DRkWc%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.4.4 RC2 is ready for testing

2018-03-29 Thread Toshio Kuratomi

For those who are waiting a bit to upgrade to Ansible-2.5.x, we're
happy to announce that RC2 for 2.4.4 is now available for testing!

How do you get it?
--

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

https://releases.ansible.com/ansible/ansible-2.4.4.0-0.3.rc2.tar.gz
SHA256: 722018d4d7054b01270453a4f27b8087e7a486c944247e42cb5bc05b8aa1bdf6

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.4.4.0-0.3.rc2

You can then source our testing script:

$ . hacking/env-setup

or you can build your own .tar.gz (output will be dist/ansible-2.4.4.0.tar.gz):

$ make sdist

If you discover any errors, or if you see any regressions from
playbooks which work on 2.4.3 and prior, please open a Github issue
and be sure to mention you're testing against this release candidate.

I probably should have held off on release 2.4.4-rc1 until after 2.5.0
final had been released as this new pre-release contains many new,
little fixes which made it into 2.5.0. If you think you are still
going to run 2.4.x for a while, please test this out and report if you
find any showstopper bugs. Unless we hear of a blocker bug, 2.4.4
final will release next week. 2.4.4 will be the last regularly
scheduled release in the 2.4.x series (we'll only make more releases
in 2.4.x if critical bugs are discovered. Non-critical bugfixes will
be released in the 2.5.x or newer release serieses.)

Thanks for testing!

Toshio Kuratomi

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaT2A2sXfZ0w%3DQet%3DKFt1O75tu9%2ByDC4ehvmi7WbDk-X-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Error while running bigip_node module

2018-03-15 Thread Toshio Kuratomi

Setting ansible_python_interpreter=/path/to/python2.7 should do it for you
unless the scl python2.7 doesn't know where its own libraries are (haven't
used scl python so I don't know the answer to that off the top of my head)


You can set that on the command line using the --extra-vars option to test:
http://docs.ansible.com/ansible/devel/cli/ansible-playbook.html#cmdoption-
ansible-playbook-e
and via group_vars/host_vars to make it apply on every run:
http://docs.ansible.com/ansible/devel/user_guide/intro_inventory.html#host-variables

-Toshio

On Mar 15, 2018 4:21 AM, "eric landers"  wrote:

I'm trying to run the bigip_node playbook and am receiving the below error.
I've also upgraded to python 2.7 which is now running alongside of python
2.6. How do I make the f5 modules now point to python 2.7 instead of 2.6?

[admin@server1 f5]$ cat playbooks/labbigipnode.yaml
---

- name: Create a Node
  hosts: lab_ltm
  connection: local

  tasks:
  - name: Add a new node
bigip_node:
  server: "{{ inventory_hostname }}"
  user: "admin"
  password: "pass"
  state: present
  host: "10.2.1.1"
  name: "member1"
delegate_to: localhost
[admin@server1 f5]$

[admin@server1 ~]$ ansible --version
ansible 2.4.2.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/home/admin/.ansible/plugins/modules',
u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.6/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.6.6 (r266:84292, Aug  9 2016, 06:11:56) [GCC 4.4.7
20120313 (Red Hat 4.4.7-17)]

[admin@server1  ~]$ python --version
Python 2.6.6
[admin@server1  ~]$ scl enable python27 bash
[admin@server1 ~]$   python --version
Python 2.7.13



[admin@server1 f5]$ ansible-playbook -i inventory/hosts.ini
playbooks/labbigipnode.yaml

PLAY [Create a Node] **

*

TASK [Gathering Facts] **
***
ok: [dc1nnelabltm2.company.com.company.com]
ok: [dc1nnelabltm1.company.com.company.com]

TASK [Add a new node] **

An exception occurred during task execution. To see the full traceback, use
-vvv. The error was: SyntaxError: invalid syntax
fatal: [dc1nnelabltm1.company.com.company.com -> localhost]: FAILED! =>
{"changed": false, "module_stderr": "Traceback (most recent call last):\n
File \"/tmp/ansible_3X7cAp/ansible_module_bigip_node.py\", line 467, in
\nfrom ansible.module_utils.f5_utils import *\n  File
\"/tmp/ansible_3X7cAp/ansible_modlib.zip/ansible/module_utils/f5_utils.py\",
line 143, in \n  File
\"/usr/lib/python2.6/site-packages/f5/bigip/__init__.py\",
line 33, in \nfrom f5.bigip.cm import Cm\n  File
\"/usr/lib/python2.6/site-packages/f5/bigip/cm/__init__.py\", line 19, in
\nfrom f5.bigip.cm.autodeploy import Autodeploy\n  File
\"/usr/lib/python2.6/site-packages/f5/bigip/cm/autodeploy/__init__.py\",
line 20, in \nfrom f5.bigip.cm.autodeploy.software_images
import Software_Image_Downloads\n  File \"/usr/lib/python2.6/site-pack
ages/f5/bigip/cm/autodeploy/software_images.py\", line 23, in \n
from f5.bigip.resource import PathElement\n  File
\"/usr/lib/python2.6/site-packages/f5/bigip/resource.py\", line 725\n
no_meta_dict = {k: v for k, v in iteritems(self.__dict__)\n
   ^\nSyntaxError: invalid syntax\n", "module_stdout": "", "msg":
"MODULE FAILURE", "rc": 0}
An exception occurred during task execution. To see the full traceback, use
-vvv. The error was: SyntaxError: invalid syntax
fatal: [dc1nnelabltm2.company.com.company.com -> localhost]: FAILED! =>
{"changed": false, "module_stderr": "Traceback (most recent call last):\n
File \"/tmp/ansible_polkKA/ansible_module_bigip_node.py\", line 467, in
\nfrom ansible.module_utils.f5_utils import *\n  File
\"/tmp/ansible_polkKA/ansible_modlib.zip/ansible/module_utils/f5_utils.py\",
line 143, in \n  File
\"/usr/lib/python2.6/site-packages/f5/bigip/__init__.py\",
line 33, in \nfrom f5.bigip.cm import Cm\n  File
\"/usr/lib/python2.6/site-packages/f5/bigip/cm/__init__.py\", line 19, in
\nfrom f5.bigip.cm.autodeploy import Autodeploy\n  File
\"/usr/lib/python2.6/site-packages/f5/bigip/cm/autodeploy/__init__.py\",
line 20, in \nfrom f5.bigip.cm.autodeploy.software_images
import Software_Image_Downloads\n  File \"/usr/lib/python2.6/site-pack
ages/f5/bigip/cm/autodeploy/software_images.py\", line 23, in \n
from f5.bigip.resource import PathElement\n  File
\"/usr/lib/python2.6/site-packages/f5/bigip/resource.py\", line 725\n
no_meta_dict = {k: v for k, v in iteritems(self.__dict__)\n
   ^\nSyntaxError: invalid syntax\n", "module_stdout": "", "msg":
"MODULE FAILURE", "rc": 0}
to retry, use: --limit

Re: [ansible-project] Re: Permission denied while copy with sudo (Related to issue 2837)

2018-03-09 Thread Toshio Kuratomi

Your having a different problem than the person you replied to.  Your issue
is that you don't have permission on the directory that you are asking
ansible to create (/etc/ ).  The original poster was having problems
with an internal ansible temporary directory.

For your issue, you need the user you are logging into the remote machine
as to have permission to create that directory *or* you need to use
ansible's become facilities to become a user with sufficient permissions to
create the directory.

For instance, on my machines ansible will log into the remote machine as an
unprivilrged user and then use sudo with password to become root.  Using
your playing, I'd invoke ansible with a commandline like this:

ansible-playbook --become --become-user=root -K test.yml

On Mar 9, 2018 10:06 AM, "Vamsi krishna"  wrote:

> Hello @Toshio ,
>
> Thanks for your response, i tried and i changed in the ansible.cfg file to
> remote_tmp: /var/tmp and still same error
> Yaml file i am using
>  name: using
>  hosts: all
>  tasks:
>- name: creates directory
>  file:
>path: /etc/
>state: directory
>owner: root
>group: root
>mode: 0755
>
> Error i am getting
>
> "msg": "There was an issue creating /etc/ as requested: [Errno 13]
> Permission denied: b'/etc/'
>
>
> Any help.
>
> 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-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/ansible-project/c0a24201-6403-4207-836b-2b10d7ff558b%
> 40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQXniuo8555%2Bh1MFZyaR%2BrRquicX38dy%3D0Z6qtqYQgR6A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Re: Permission denied while copy with sudo (Related to issue 2837)

2018-03-08 Thread Toshio Kuratomi

There's a configuration option, remote_tmp.  Setting that to a system
directory (like /tmp or /var/tmp ) can fix this error.

On Mar 8, 2018 5:04 PM, "Vamsi krishna"  wrote:

> Hi vincent,
>
> mee to facing the same issue...
> changing the tmp directory means, what you mean??
>
> you mean to change that in our hosts
>
> can u explain litttle bit clear...
>
> On Friday, July 19, 2013 at 9:30:53 AM UTC-7, Vincent Hardion wrote:
>>
>> I have just pull the last version but it is the same behaviour.
>>
>> ~/projects/cfg-maxlab-ansible/etc/ansible% ansible-playbook --version
>> ansible-playbook 1.3 (devel f4b1e426ea) last updated 2013/07/19 18:08:52
>> (GMT +200)
>>
>> TASK: [ensure NTP point out to the ntp server] *
>> failed: [computerA.se] => {"failed": true, "item": ""}
>> msg: Could not replace file: /home/xxx/.ansible/tmp/ansible
>> -1374250532.29-44727094344629/source to /etc/ntp.conf: [Errno 13]
>> Permission denied: '/home/xxx/.ansible/tmp/ansibl
>> e-1374250532.29-44727094344629/source'
>>
>>
>> By changing the temp directory it works.
>>
>> Thank you Michael and Brian.
>>
>> Vincent
>>
>>
>> On Fri, Jul 19, 2013 at 5:54 PM, Michael DeHaan 
>> wrote:
>>
>>> But yes, Brian is correct.   The ansible remote temp path should
>>> probably be configured and forced to /tmp in this case.
>>>
>>>
>>>
>>>
>>> On Fri, Jul 19, 2013 at 11:54 AM, Michael DeHaan <
>>> mic...@ansibleworks.com> wrote:
>>>
 Just for clarification, have you tried the development branch as of
 about 20 minutes ago?

 Some code changes in that regard and want to make sure you're trying
 latest before I try to replicate things.

 --Michael




 On Fri, Jul 19, 2013 at 4:26 AM, Vincent Hardion 
 wrote:

> Thanks for your answer.
> Effectively with the version of ansible is better. So I tried first
> with 1.2 (rpm from epel) but it happens with release1.2.1 and even the
> development branch.
>
> I'm the owner of ~/.ansible. But now you talk about "unique" maybe one
> thing: the home directory is nfs mount. So when I launch ansible from
> computer A to computer B, ansible use the same "drive" space.
>
> This pull request can be more explicit : https://github.com/ansible/a
> nsible/pull/3587.
>
> Best regards,
> Vincent
>
> --
> 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-proje...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



 --
 Michael DeHaan 
 CTO, AnsibleWorks, Inc.
 http://www.ansibleworks.com/


>>>
>>>
>>> --
>>> Michael DeHaan 
>>> CTO, AnsibleWorks, Inc.
>>> http://www.ansibleworks.com/
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Ansible Project" group.
>>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>>> pic/ansible-project/yCN_yXa_GkM/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> ansible-proje...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>
>> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/4bae621f-b1d9-4ed7-87db-3dc76678b30f%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQNX9ii%2BVJBzZ7b0ehru%2Boxq%3Dd0btSPKYYZxjBYGLLaEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Re: /tmp/.ansible/tmp not write-able by all users

2018-03-02 Thread Toshio Kuratomi

If you specify /tmp/.ansible/tmp as the remote_tmp, then you become
responsible for ensuring that the correct users have permission to read,
write, and search that directory.  Ansible deals with permissions below
that directory only.

There was a bug in the 2.5 branch (I believe fixed in the latest rc) where
ansible was supposed to revert to the system temp directory when
remote_user was unprivileged and become_user was also unprivileged.  What
version of ansible are you using? (ansible --version output). That might
tell us if this is related to that bug.

-Toshio

On Mar 2, 2018 7:17 AM, "Mike Cavedon"  wrote:

Looks like /tmp/.ansible needs to be 777


On Friday, March 2, 2018 at 10:09:49 AM UTC-5, Mike Cavedon wrote:
>
> I changed remote_tmp to /tmp/.ansible/tmp for performance reasons. The
> directory is created as follows:
>
> [tmp]$ ls -ld .ansible
> drwx-- 3 ec2-user ec2-user 4096 Mar  2 09:47 .ansible
>
> When a different user attempts to write to the directory it fails:
>
> "Authentication or permission failure. In some cases, you may have been able 
> to authenticate and did not have permissions on the remote directory. 
> Consider changing the remote temp path in ansible.cfg to a path rooted in 
> \"/tmp\". Failed command was: ( umask 77 && mkdir -p \"` echo 
> /tmp/.ansible/tmp/ansible-tmp-1520002087.57-321143948
>
>
> Shouldn't /tmp/.ansible be created with 766 permission? Am I going to have to 
> chmod /tmp/.ansible in the playbook?
>
> --
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-project@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/ansible-project/129d8418-299a-47d4-a975-a4a98fc16d96%40googlegroups.
com

.

For more options, visit https://groups.google.com/d/optout.

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSZBMs_hNa0_S-4hwK%3DAvf%3DnOPaomop8%3DjWD624qHjMGQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.4.4 RC1 is ready for testing

2018-03-01 Thread Toshio Kuratomi

Hi all, we're happy to announce that RC1 for 2.4.4 is now available for testing.

How do you get it?
--

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

https://releases.ansible.com/ansible/ansible-2.4.4-0.2.rc1.tar.gz
SHA256: 97fd3fde530b8b8b0e15a89cc77cc58668ca41b17f5c055d93d83f47c391eabb

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.4.4-0.2.rc1

You can then source our testing script:

$ . hacking/env-setup

or you can build your own .tar.gz (output will be dist/ansible-2.4.4.tar.gz):

$ make sdist

I'm aiming to have 2.4.4 final come out the week after 2.5.0 final is
out. So do test this out if you're intending to stay on 2.4.x a while
longer but note that the final of 2.4.4 won't be released until after
2.5.0.

Thanks!

Toshio Kuratomi

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQJd3jb-bMj%3D%2B3-dJqJkh1qgc1X2L5HnMSPfViLYGY8qA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Release schedule for 2.4.4 and beyond

2018-02-19 Thread Toshio Kuratomi

Greetings all,

I just wanted to say a brief word about my intention as the 2.4.x
Ansible Release Manager forgetting 2.4.4 out the door and any further
2.4.x releases after that.

Release Schedule for 2.4.4
==

My plan is for 2.4.4 to be released shortly after 2.5.0 final is
released. To get us on the right track for that, I'll be releasing
2.4.4 beta1 when 2.5.0-rc1 is released. My plan is for just one beta
and then begin rc's for 2.4.4 as there are relatively fewer changes
hitting the 2.4 tree now. Here's the tentative release schedule:

February 21: 2.4.4-beta1
March 28: 2.4.4-rc1

2.4.4 final could potentially land as early as March 7th but I'll
definitely wait until 2.5.0 final is out before shipping 2.4.4 final.
There's enough code in common that it just makes sense to wait until
all of the bugs we're going to consider blockers for 2.5.0 are taken
care of before releasing 2.4.4 (in case any of them need backporting
to 2.4.4)

Beyond 2.4.4

So far, the 2.4.x release series has had a series of scheduled
releases. 2.4.1 and 2.4.2 were each scheduled for one month after the
previous releases. 2.4.3 was scheduled for two months after its
predecessor but slipped a few extra weeks. 2.4.4 will be the last of
these scheduled
releases. After it is released we'll continue to accumulate important
bugfixes in the stable-2.4 branch but will only be cutting a 2.4.5 if
there's any critical or security bugs that need to be addressed. If
that happens, I'll make one or more release candidate tarballs
followed by a new 2.4.x release that addresses the critical bug.

Thanks everyone, and looking forward to a smooth 2.4.4 release :-)

-Toshio

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaRmtxA52Ne4KbRgZ63XuszcCOmv8YsyjwER8ipm5tG-%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Can Ansible consider switching from Google Groups to a Discourse instance?

2018-02-18 Thread Toshio Kuratomi

I don't think this would happen. I have asked the core team about
switching from Google groups to a mailman 3 instance that has a forum-like
interface to the archives but there didn't seem to be any other interest in
that.

-Toshio

On Feb 18, 2018 12:34 PM, "David Reagan" wrote:

I did a search, and I think the last time switching from mailing lists to a
forum was discussed was in 2014 here: https://groups.google.com/d/
topic/ansible-project/3NkSXNxULFw/discussion

Can Ansible consider switching from Google Groups to a Discourse instance?

Elastic.co did so. It seemed like a successful move for them. Mozilla has
one.

So far, my experience using Discourse has always been far superior to
Google Groups or other mailing lists.

I believe Discourse offers the ability to interact with it the same way you
interact with Google Groups via email.

Some of the things I thing would benefit us all:

* Markdown formatting
* Marking a response as a solution
* Auto searching for similar topics.

What does everyone else think?

What are the pro's for Google Groups?

--
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-project@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/ansible-project/534281d5-6630-4823-aec0-4a3f7fff9529%40googlegroups.
com

.
For more options, visit https://groups.google.com/d/optout.

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaR4rQRmLVD%2Bu0t%2BhcAkkLtW%2BN6FcRu63xB%3D_Wm7azt9oA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.4.3 has been released

2018-01-31 Thread Toshio Kuratomi

On behalf of the entire Ansible open source community, we are very
happy to announce that Ansible 2.4.3 has been released!

This release includes many bugfixes to the 2.4 codebase.  For full
details, please see the Changelog:

https://github.com/ansible/ansible/blob/stable-2.4/CHANGELOG.md

As always, this update is available via PyPi and
https://releases.ansible.com/ansible/ansible-2.4.3.0.tar.gz
now, and packages for distros will be available as soon as possible.

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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaS00qEV8zpE9tJp5HrPYQJZ07_tNMytrhLe1kGxa%2BT0aA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible-2.4.3-rc3

2018-01-24 Thread Toshio Kuratomi

Hi all, we're happy to announce that RC3 for 2.4.3 is now available for testing.

How do you get it?
--

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

https://releases.ansible.com/ansible/ansible-2.4.3.0-0.6.rc3.tar.gz
SHA256: 48729ef5b3bdb9c65641c95be37b56555aeb8baceb1de3d7653c877bd6de1924

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.4.3.0-0.6.rc3

You can then source our testing script:

$ . hacking/env-setup

or you can build your own .tar.gz (output will be dist/ansible-2.4.3.0.tar.gz):

$ make sdist

If you discover any errors, or if you see any regressions from
playbooks which work on 2.4.2 and prior, please open a Github issue
and be sure to mention you're testing against this release candidate.

This release candidate fixes only a few more things than rc2 but we
deemed them blockers:

* A memory optimizations with include_role:
https://github.com/ansible/ansible/issues/31673
* A recursion issue with include_role:
https://github.com/ansible/ansible/issues/23609
* Misc changes to the Azure modules to account for new azure upstream API.
* A fix for timeout issues with python 3 in the ssh connection plugin:
https://github.com/ansible/ansible/issues/31673

Please test and report any bugs that we might want to list as blockers
as we're hoping that this will be the last release candidate before
2.4.3.0 final.

Thanks!

Toshio Kuratomi

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQO80eCaj-33GpUYUsGR0tvfQtUe6MwoSCCEukU4xzxdw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.4.3.0 rc2 ready for testing

2018-01-17 Thread Toshio Kuratomi

Hi all, we're happy to announce that RC2 for 2.4.3.0 is now available
for testing.

How do you get it?
--

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

https://releases.ansible.com/ansible/ansible-2.4.3.0-0.5.rc2.tar.gz
SHA256: 0890822fb3e7f99aa3746eb1fbe963aa2a7eed381fe1237b9d9a17b4fc22fc79

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.4.3.0-0.5.rc2

You can then source our testing script:

$ . hacking/env-setup

or you can build your own .tar.gz (output will be dist/ansible-2.4.3.0.tar.gz):

$ make sdist

The notable changes in this rc are some improvements for speed and
memory when using include_role and some butg fixes for the azure
modules.

If all goes well with testing of this, we should be releasing 2.4.3.0
final next week!

Thanks,

Toshio Kuratomi

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaRXOAW1rdi8R02P9oOeZ%2BbFi9qbof8aDAE_dUbNF1JtBA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.4.3 RC1 is ready for testing

2018-01-10 Thread Toshio Kuratomi

Hi all, we're happy to announce that RC1 for 2.4.3 is now available for testing.

How do you get it?
--

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

https://releases.ansible.com/ansible/ansible-2.4.3.0-0.4.rc1.tar.gz
SHA256: 95c339f05b1e5119b4f3f683932f080ea835cee86f05dcc8965e840d7372d38a

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.4.3.0-0.4.rc1

You can then source our testing script:

$ . hacking/env-setup

or you can build your own .tar.gz (output will be dist/ansible-2.4.3.0.tar.gz):

$ make sdist

If you discover any errors, or if you see any regressions from
playbooks which work on 2.4.2 and prior, please open a Github issue
and be sure to mention you're testing against this release candidate.

Thanks!

Toshio Kuratomi

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQ_8y-nucAaNDCw%3Df%2BucGOs416t0XwOLbJdyainLkc_Qw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] In an Ansible task, what is the proper way to run a script in the background?

2018-01-03 Thread Toshio Kuratomi

Or option three: use async:.
http://docs.ansible.com/ansible/latest/playbooks_async.html


If the script is something you want to run and exit after performing its
tall, I think async is the most idiomatic.  If the script is more like a
daemon, having nohup in the script feels right to me but I can't think of a
reason either would be better.
-Toshio

On Jan 3, 2018 11:56 AM, "ZillaYT"  wrote:

> Say I want to run a script in the background after my Ansible run
> finishes. Which of these two options is the correct way?
>
> *Option 1: Run a nohup on the Ansible task itself*
> - name:Run a script in the background
>   command: nohup myscript.sh 2>&1  &
>
> where myscript.sh does something (anything) but has no nohup calls.
>
>
> *Option 2: Put the nohup in the script itself?*
> - name: Run a script in the background
>   command: ./myscript.sh
>
> and myscript.sh has in it the nohup
>
> *myscript.sh*
> nodup do_something 2>&1 &
>
>
>
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/70316e05-1357-40d8-aab4-53092dd8edc1%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQ5yr8QSpjm6jtbe63fsQGOtkcUK_-K_UgQykEmUtTOLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] absolute import error for centos 5 environment

2017-12-20 Thread Toshio Kuratomi

You need a newer version of python or an older version of ansible.
Ansible-2.3 was the last release series to support python-2.4 on the
managed machines (it still required python-2.6 or greater on the controller
but you could manage machines with only python 2.4 installed ).

-Toshio

On Dec 20, 2017 5:48 AM, "Oğuz Yarımtepe"  wrote:

> Hi,
>
> While i am just testing ping adhoc command for my Centos5 environment
> below is the error i got
>
>
> $ ansible all -i tmp3.txt -m ping -u root -k
>
> TESTSRV | FAILED! => {
> "changed": false,
> "failed": true,
> "module_stderr": "",
> "module_stdout": "  File \"/tmp/ansible_nEiCUn/ansible_module_ping.py\",
> line 8\r\nfrom __future__ import absolute_import, division,
> print_function\r\nSyntaxError: future feature absolute_import is not
> defined\r\n",
> "msg": "MODULE FAILURE",
> "rc": 0
> }
>
> ✗ pip show ansible
> Name: ansible
> Version: 2.4.1.0
> Summary: Radically simple IT automation
> Home-page: https://ansible.com/
> Author: Ansible, Inc.
> Author-email: i...@ansible.com
> License: GPLv3+
> Location: /Users/foo/ansible-playbooks/venv/lib/python2.7/site-packages
> Requires: jinja2, PyYAML, setuptools, cryptography, paramiko
>
> at the TESTSRV
>
>  # cat /etc/redhat-release
> CentOS release 5.4 (Final)
>
> # python
> Python 2.4.3 (#1, Jan  9 2013, 06:47:03)
> [GCC 4.1.2 20080704 (Red Hat 4.1.2-54)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>
> Any idea what is missing at the remote side?
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/803d6d46-87c2-46d6-ba0b-db96e711fd43%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaR3tgmWOTtRKUiVAaMenQpG%3D_1dWxgN9JbCa-ZJQAJ%2B3Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Trying to duplicate a Bash script into ansible -- Not sure how to best handle alternatives with Slaves

2017-12-13 Thread Toshio Kuratomi

If you don't need idempotence (I assume you don't since the shell module
doesn't have idempotence either) I'd use the script module with your
existing bash script.

-toshio

On Dec 13, 2017 7:39 AM, "Justin Seiser"  wrote:

> I see there was a feature
>  request for this, but
> they do not note how they actually worked around it. In a nutshell, we
> download a groovy archive, unzip it, and create slaves for every file in
> the archive that is not the groovy executable, and doesnt end with .bat. We
> then do a update-alternatives for groovy.
>
>
>
> GROOVY_ALT_SLAVES=""
> for f in $(ls /opt/groovy-${GROOVY_VERSION}/bin | fgrep -v .bat |
> grep -v '^groovy$'); do
> GROOVY_ALT_SLAVES=" ${GROOVY_ALT_SLAVES}  --slave /usr/bin/${f}
> ${f} /opt/groovy-${GROOVY_VERSION}/bin/${f}"
> done
>
> update-alternatives --install /usr/bin/groovy groovy
> /opt/groovy-${GROOVY_VERSION}/bin/groovy 2000 ${GROOVY_ALT_SLAVES}
> update-alternatives --set groovy /opt/groovy-${GROOVY_VERSION}/
> bin/groovy
>
> I cant really wrap my head around the best way to dupe this, that isnt
> just running the shell module.  Once I resigned myself to using the shell
> module, I then read that doing something like
>
>
>  - shell: GROOVY_ALT_SLAVES=" ${GROOVY_ALT_SLAVES}  --slave /usr/bin/{{ item 
> }} {{ item }} /opt/groovy-{{ groovy_version }}/bin/{{ item }}"
> with_items: ['file1', 'file2']
>
>
>
>
> Wouldn't work, since each shell run is a separate connection, so Im not
> really building up a long string to then append to the update-alternatives
> command.  There is also the fact I have to manually specify a list of
> items, since I cant use glob because i need to match files that do not
> match a certain set of expressions.
>
>
> Im sure Im missing something obvious, but I haven't made any progress on
> this one and any help would be great.
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/155465dd-7461-486c-9351-5a386c6c5f15%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSiPiF-b9F0uXhoBfSL1rvv0pTnH_%3DhbZOh6V8kq6PPyQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] How to configure audible not to use MD5?

2017-12-05 Thread Toshio Kuratomi

I've just tested FIPS mode on both centos6 and centos7 and copy works
on both.  Here's the output from one of my tests:
ansible -m copy -a 'src=/etc/passwd dest=/tmp/test'  rhel7-test -v

rhel7-test | SUCCESS => {
"changed": true,
"checksum": "e71a984d8559a386e52c0ef954f368513c398eee",
"dest": "/tmp/test",
"diff": [],
"gid": 1000,
"group": "badger",
"invocation": {
"module_args": {
"attributes": null,
"backup": false,
"content": null,
"delimiter": null,
"dest": "/tmp/test",
"directory_mode": null,
"follow": false,
"force": true,
"group": null,
"local_follow": null,
"mode": null,
"original_basename": "passwd",
"owner": null,
"regexp": null,
"remote_src": null,
"selevel": null,
"serole": null,
"setype": null,
"seuser": null,
"src":
"/home/badger/.ansible/tmp/ansible-tmp-1512499612.07-236714811611664/source",
"unsafe_writes": null,
"validate": null
}
},
"md5sum": null,
"mode": "0664",
"owner": "badger",
"secontext": "unconfined_u:object_r:user_home_t:s0",
"size": 5664,
"src": 
"/home/badger/.ansible/tmp/ansible-tmp-1512499612.07-236714811611664/source",
"state": "file",
"uid": 1000
}

No error and the md5sum field is null.

So I will need the details I asked for to figure out how to reproduce
this and how to fix it.

Thanks,
-Toshio

On Tue, Dec 5, 2017 at 9:00 AM, Toshio Kuratomi <tkura...@redhat.com> wrote:
> Okay, that's a bug that needs to be fixed.  I need this information:
>
> * On what system?  It looks like the way it fails is now different
> than on the system that we first made this work with FIPS mode on.
>   * How do you get that system into FIPS mode?  (IIRC, we tested on
> RHEL5 or 6 and had to pass a kernel commandline parameter to enable
> FIPS mode)
> * What's the complete traceback?
>
> -Toshio
>
> On Tue, Dec 5, 2017 at 8:36 AM, Veena <mveen...@gmail.com> wrote:
>> The copy task fails and I get below error
>>
>> fips_md.c(147): OpenSSL internal error, assertion failed: Digest update
>> previous FIPS forbidden algorithm error ignored\n
>>
>> Thanks,
>> -Veena
>>
>> On Tuesday, December 5, 2017 at 8:59:12 PM UTC+5:30, Toshio Kuratomi wrote:
>>>
>>> Template and copy will work just fine in  FIPS mode.  The md5 return
>>> value will just be empty.  Try it :-)
>>>
>>> -Toshio
>>>
>>> On Tue, Dec 5, 2017 at 7:26 AM, Veena <mvee...@gmail.com> wrote:
>>> > Thanks for the reply Toshio.
>>> >
>>> > I have replaced copy with "synchronize". But there is no alternative for
>>> > "template". The use case is to run ansible tasks with FIPS enabled mode.
>>> >
>>> >
>>> > On Tuesday, December 5, 2017 at 8:52:06 PM UTC+5:30, Toshio Kuratomi
>>> > wrote:
>>> >>
>>> >> Just confirmed that template uses the copy module under the covers.
>>> >> That means if md5 is disabled on the remote machine, then it will not
>>> >> return an md5 hash.
>>> >>
>>> >> -Toshio
>>> >>
>>> >> On Tue, Dec 5, 2017 at 6:38 AM, Toshio Kuratomi <tkur...@redhat.com>
>>> >> wrote:
>>> >> > I'll check that template uses the same rules as the copy and start
>>> >> > modules
>>> >> > not in general if md5 is disallowed on a not do (for instance, fips
>>> >> > mode),
>>> >> > the module simply won't return an md5 hash.  Are you seeing an error?
>>> >> > What's your use case?
>>> >> >
>>> >> > -Toshio
>>> >> >
>>> >> >
>>> >> > On Dec 5, 2017 4:37 AM, "Veena" <mvee...@gmail.com> wrote:
>>> >> >
>>> >> > By default ansible uses MD5 for all the modules. I should run ansible
>>> >> > on
>>> >> > a
>>> >

Re: [ansible-project] How to configure audible not to use MD5?

2017-12-05 Thread Toshio Kuratomi

Okay, that's a bug that needs to be fixed.  I need this information:

* On what system?  It looks like the way it fails is now different
than on the system that we first made this work with FIPS mode on.
  * How do you get that system into FIPS mode?  (IIRC, we tested on
RHEL5 or 6 and had to pass a kernel commandline parameter to enable
FIPS mode)
* What's the complete traceback?

-Toshio

On Tue, Dec 5, 2017 at 8:36 AM, Veena <mveen...@gmail.com> wrote:
> The copy task fails and I get below error
>
> fips_md.c(147): OpenSSL internal error, assertion failed: Digest update
> previous FIPS forbidden algorithm error ignored\n
>
> Thanks,
> -Veena
>
> On Tuesday, December 5, 2017 at 8:59:12 PM UTC+5:30, Toshio Kuratomi wrote:
>>
>> Template and copy will work just fine in  FIPS mode.  The md5 return
>> value will just be empty.  Try it :-)
>>
>> -Toshio
>>
>> On Tue, Dec 5, 2017 at 7:26 AM, Veena <mvee...@gmail.com> wrote:
>> > Thanks for the reply Toshio.
>> >
>> > I have replaced copy with "synchronize". But there is no alternative for
>> > "template". The use case is to run ansible tasks with FIPS enabled mode.
>> >
>> >
>> > On Tuesday, December 5, 2017 at 8:52:06 PM UTC+5:30, Toshio Kuratomi
>> > wrote:
>> >>
>> >> Just confirmed that template uses the copy module under the covers.
>> >> That means if md5 is disabled on the remote machine, then it will not
>> >> return an md5 hash.
>> >>
>> >> -Toshio
>> >>
>> >> On Tue, Dec 5, 2017 at 6:38 AM, Toshio Kuratomi <tkur...@redhat.com>
>> >> wrote:
>> >> > I'll check that template uses the same rules as the copy and start
>> >> > modules
>> >> > not in general if md5 is disallowed on a not do (for instance, fips
>> >> > mode),
>> >> > the module simply won't return an md5 hash.  Are you seeing an error?
>> >> > What's your use case?
>> >> >
>> >> > -Toshio
>> >> >
>> >> >
>> >> > On Dec 5, 2017 4:37 AM, "Veena" <mvee...@gmail.com> wrote:
>> >> >
>> >> > By default ansible uses MD5 for all the modules. I should run ansible
>> >> > on
>> >> > a
>> >> > node where MD5 is not allowed. I could find a way for "copy" and
>> >> > "stat"
>> >> > by
>> >> > giving get_md5=no, but there's no alternative or workaround for
>> >> > "template"
>> >> > module. Please suggest a way to use template without md5 or in
>> >> > general
>> >> > how
>> >> > to make sensible not use md5.
>> >> >
>> >> > Thanks,
>> >> > -Veena
>> >> >
>> >> > --
>> >> > 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-proje...@googlegroups.com.
>> >> > To post to this group, send email to ansible...@googlegroups.com.
>> >> > To view this discussion on the web visit
>> >> >
>> >> >
>> >> > https://groups.google.com/d/msgid/ansible-project/5e57a754-5ec6-4de6-bf25-2cd6d958ee9b%40googlegroups.com.
>> >> > For more options, visit https://groups.google.com/d/optout.
>> >> >
>> >> >
>> >
>> > --
>> > 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-proje...@googlegroups.com.
>> > To post to this group, send email to ansible...@googlegroups.com.
>> > To view this discussion on the web visit
>> >
>> > https://groups.google.com/d/msgid/ansible-project/b62e7d06-bb24-451a-9b3a-0d0e107b6aac%40googlegroups.com.
>> >
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/3c30cb63-6d73-446f-938a-360ea7853bf5%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaTx2F9Yy2KnPao2SL5CSd3KMVVsUQ%2B5o%2B8gSGjeJr3Jtg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] How to configure audible not to use MD5?

2017-12-05 Thread Toshio Kuratomi

Template and copy will work just fine in  FIPS mode.  The md5 return
value will just be empty.  Try it :-)

-Toshio

On Tue, Dec 5, 2017 at 7:26 AM, Veena <mveen...@gmail.com> wrote:
> Thanks for the reply Toshio.
>
> I have replaced copy with "synchronize". But there is no alternative for
> "template". The use case is to run ansible tasks with FIPS enabled mode.
>
>
> On Tuesday, December 5, 2017 at 8:52:06 PM UTC+5:30, Toshio Kuratomi wrote:
>>
>> Just confirmed that template uses the copy module under the covers.
>> That means if md5 is disabled on the remote machine, then it will not
>> return an md5 hash.
>>
>> -Toshio
>>
>> On Tue, Dec 5, 2017 at 6:38 AM, Toshio Kuratomi <tkur...@redhat.com>
>> wrote:
>> > I'll check that template uses the same rules as the copy and start
>> > modules
>> > not in general if md5 is disallowed on a not do (for instance, fips
>> > mode),
>> > the module simply won't return an md5 hash.  Are you seeing an error?
>> > What's your use case?
>> >
>> > -Toshio
>> >
>> >
>> > On Dec 5, 2017 4:37 AM, "Veena" <mvee...@gmail.com> wrote:
>> >
>> > By default ansible uses MD5 for all the modules. I should run ansible on
>> > a
>> > node where MD5 is not allowed. I could find a way for "copy" and "stat"
>> > by
>> > giving get_md5=no, but there's no alternative or workaround for
>> > "template"
>> > module. Please suggest a way to use template without md5 or in general
>> > how
>> > to make sensible not use md5.
>> >
>> > Thanks,
>> > -Veena
>> >
>> > --
>> > 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-proje...@googlegroups.com.
>> > To post to this group, send email to ansible...@googlegroups.com.
>> > To view this discussion on the web visit
>> >
>> > https://groups.google.com/d/msgid/ansible-project/5e57a754-5ec6-4de6-bf25-2cd6d958ee9b%40googlegroups.com.
>> > For more options, visit https://groups.google.com/d/optout.
>> >
>> >
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/b62e7d06-bb24-451a-9b3a-0d0e107b6aac%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQaaeikYpwF5oJj0SzFPQUU0uG_kXXBgpCxKY75_MANRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] How to configure audible not to use MD5?

2017-12-05 Thread Toshio Kuratomi

Just confirmed that template uses the copy module under the covers.
That means if md5 is disabled on the remote machine, then it will not
return an md5 hash.

-Toshio

On Tue, Dec 5, 2017 at 6:38 AM, Toshio Kuratomi <tkura...@redhat.com> wrote:
> I'll check that template uses the same rules as the copy and start modules
> not in general if md5 is disallowed on a not do (for instance, fips mode),
> the module simply won't return an md5 hash.  Are you seeing an error?
> What's your use case?
>
> -Toshio
>
>
> On Dec 5, 2017 4:37 AM, "Veena" <mveen...@gmail.com> wrote:
>
> By default ansible uses MD5 for all the modules. I should run ansible on a
> node where MD5 is not allowed. I could find a way for "copy" and "stat" by
> giving get_md5=no, but there's no alternative or workaround for "template"
> module. Please suggest a way to use template without md5 or in general how
> to make sensible not use md5.
>
> Thanks,
> -Veena
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/5e57a754-5ec6-4de6-bf25-2cd6d958ee9b%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaRE3gekr75VMEg11V7COfHpoD4stBV6m4erXEpf0kgr6w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] How to configure audible not to use MD5?

2017-12-05 Thread Toshio Kuratomi

I'll check that template uses the same rules as the copy and start modules
not in general if md5 is disallowed on a not do (for instance, fips mode),
the module simply won't return an md5 hash. Are you seeing an error?
What's your use case?

-Toshio

On Dec 5, 2017 4:37 AM, "Veena" wrote:

By default ansible uses MD5 for all the modules. I should run ansible on a
node where MD5 is not allowed. I could find a way for "copy" and "stat" by
giving get_md5=no, but there's no alternative or workaround for "template"
module. Please suggest a way to use template without md5 or in general how
to make sensible not use md5.

Thanks,
-Veena

--
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-project@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/ansible-project/5e57a754-5ec6-4de6-bf25-2cd6d958ee9b%40googlegroups.
com

.
For more options, visit https://groups.google.com/d/optout.

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaThsybm83v_USVp%3D5e8B%2B8LAx4M_iqB3OYQ2eqdO8S6yg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Ansible Galaxy pip Dependencies

2017-12-02 Thread Toshio Kuratomi

Typically you make it the first task in your role.

-Toshio

On Dec 1, 2017 4:17 PM, "Andrew Vaughan" wrote:

Hello all,

I have a plugin that's included with a role I intend for Ansible Galaxy.

https://galaxy.ansible.com/andrewvaughan/ansible-prompt/

I need, in this case, to have a Python pip dependency installed in order
for the role to work correctly. I have not been able to find any
documentation or questions regarding the installation of Python
dependencies to support Ansible roles. Is this possible? If so, what is
the best practice for making it work?

I suppose I could always add pip install -r ~/.ansible/roles/
andrewvaughan.ansible-prompt/requirements.txt as an instruction in the
readme, but that *really* takes away from the ease-of-use factor that
Galaxy provides.

Thanks in advance,

Andrew

--
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-project@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/ansible-project/01d99259-23ee-4c12-8abf-61a76b1f3c49%40googlegroups.
com

.
For more options, visit https://groups.google.com/d/optout.

--
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-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQZv3ZUGP2koYP8qJ%3D35SLw6EsaJxp7_vLw_Dxo4UDtoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.4.2 has been released

2017-11-29 Thread Toshio Kuratomi

On behalf of the entire Ansible open source community, we are very
happy to announce that Ansible 2.4.2 has been released!

This release includes many bugfixes to the 2.4 codebase.  For full
details, please see the Changelog:

https://github.com/ansible/ansible/blob/stable-2.4/CHANGELOG.md

As always, this update is available via PyPi and
https://releases.ansible.com/ansible/ansible-2.4.2.0.tar.gz
now, and packages for distros will be available as soon as possible.

Thanks!

-Toshio

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaS%3DxZdUFK1E8_dm1tY36_5uCjV4E_F_9kFD-Pxfk_cG%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] register module help

2017-11-26 Thread Toshio Kuratomi

The debug module will help with displaying it and the assert module may be
what you want for checking (although there are many other ways to do the
latter as well)

-toshio

On Nov 26, 2017 7:11 PM, "Viju Venugopal"  wrote:

> – name: verify application/database processes are not running
> shell: if ps -eaf | egrep ‘apache|http’|grep -v grep > /dev/null ;then
> echo ‘process_running’;else echo ‘process_not_running’;fi
> ignore_errors: true
> register: app_process_check
>
> If i write something like above , How do i Check/Display what value
> “app_process_check” has got ?
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/a7cdb02d-46ca-4db4-a46f-9a6080060f10%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQkYGqAUtjwYR1Rq41FuZ71m2uou70eRtrA7nJ86-RKzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] ansible 1.9.4 to 2.4.1.0 migration issue

2017-11-26 Thread Toshio Kuratomi

Try nodes[hostname_mounts]["yumextra"]

-Toshio

On Nov 26, 2017 7:00 PM, "George V"  wrote:

Hi all,

I have been avoiding to upgrade Ansible 1.9.4 on Centos 6 for the past few
months, however since the upgrade project is again on my desk, I am
actively working through the warnings and errors e.g.  substituting
include: statements in tasks with import_tasks:, editing playbooks and
removing duplicate when: statements and so on.

There is one issue that I cannot resolve, it seems. I maintain a list of
vars for each server in the event that I need to rebuild the server ( NODES
file below ). It essentially is a list of settings for each server like
sshd extra options, interface and cacti settings and so on. The issue is
that in 2.4 I seem not to be able to run this playbook as I was able in
1.9.4. I see that jinja2 in when statement gets a warning.

Any ideas on how I would be able to run this playbook ? I am willing to
redo the nodes file if there is a better way to do this. Looks like jinja2
in when statements is not supported any longer ?
Thank you


Version details:

root [/etc/ansible/deployment]# rpm -q ansible
ansible-2.4.1.0-2.el6.noarch

root [/etc/ansible/deployment]# rpm -qa | egrep jinja
python-jinja2-26-2.6-3.el6.noarch
python-jinja2-2.7.2-1.el6.noarch # <---  This was needed for filters

root [/etc/ansible/deployment]# rpm -q centos-release
centos-release-6-9.el6.12.3.x86_64




###  VARS  file ###
hname: "'{{ inventory_hostname }}'"

hostname_hostname: "{{inventory_hostname}}"
hostname_shortname: "{{inventory_hostname.split('.')[0]}}"

# remove dash from host name as Ansible cannot handle it properly in vars
hostname_mounts: "{{hostname_shortname.replace('-','')}}"
hostname_short: "{{hostname_shortname.replace('-','')}}"


### NODES  file ###
nodes:
   umsrv3s1:  # <--- short hostname
  ifconfig:   # <--- interface info
 - { iface: 'eth0', IP: '91.X.Y.Z1',   netmask: '255.255.255.0',
gw: '91.X.Y.G1', enabled: '1'  }
  mounts:
 - {source: 'proc', target: '/proc', opts: 'defaults,hidepid=1',
fstype: 'proc'}
  cacti:
 - { enabled: '1', tree: 'Citi1',  template: 'ucd/net SNMP Host' }
  httpd:
 - { enable: false  }
  yumextra:   # <--- extra packages for this server only
 - { packages: [ ansible-inventory-puppetdb, ansible-cmdb,
VMware-vSphere-CLI, python-psphere, python-sphere, python-pyvmomi ] }
  sshdextra:  # <--- extra sshd options for this server
 - { name: 'MaxSessions', value: '6'}
 - { name: 'MaxStartups', value: '100:30:150'}
 # DisableForwarding added in 7.4
 - { name: 'DisableForwarding', value: 'yes'}

   umsrv3s2:
  ifconfig:
 - { iface: 'eth0', IP: '91.X.Y.Z2',   netmask: '255.255.255.0',
gw: '91.X.Y.G1', enabled: '1'  }
  mounts:
 - {source: 'proc', target: '/proc', opts: 'defaults,hidepid=1',
fstype: 'proc'}
  cacti:
 - { enabled: '1', tree: 'City1',  template: 'ucd/net SNMP Host' }
  yumextra:
 - { packages: [] }
  sshdextra: []
  httpd:
 - { enable: false  }
[]

### TASKS ###
- name: setfacts - set hostname vars
  set_fact:
hostname_short_nodash: "{{ inventory_hostname.split('.')[0].replace('-','')
}}"
hostname_short: "{{inventory_hostname.split('.')[0]}}"
  tags: [ setfacts ]

- name: yum - set_fact - get list of host-specific packeges to be installed
  set_fact:
__packages: "{{ item.packages }}"

*  with_items: nodes.{{hostname_mounts}}.yumextra  when:
nodes.{{hostname_mounts}}.yumextra is defined*
  tags: [ setfacts, yum ]

- name: yum - echo __packages
  debug: var=__packages
  when: nodes.{{hostname_mounts}}.yumextra is defined
  tags: [ setfacts, yum ]

- name: yum - set_fact - get list of host-specific packeges to be installed
  set_fact:
__packages: "{{ item.packages }}"
  with_items: nodes.{{hostname_mounts}}.yumextra
  when: nodes.{{hostname_mounts}}.yumextra is defined
  tags: [ setfacts, yum ]

- name: yum - echo __packages
  debug: var=__packages
  when: nodes.{{hostname_mounts}}.yumextra is defined
  tags: [ setfacts, yum ]


/usr/bin/ansible-playbook -l `hostname -f` -c local
/etc/ansible/deployment/deployment.yml
--vault-password-file .vault --tags=setfacts
[]

TASK [yum - set_fact - get list of host-specific packeges to be installed]

*
 [WARNING]: when statements should not include jinja2 templating delimiters
such as {{ }} or {% %}. Found: nodes.{{hostname_mounts}}.yumextra is defined

fatal: [umsrv10]: FAILED! => {"failed": true, "msg": "The task includes an
option with an undefined variable. The error was:
'ansible.utils.unsafe_proxy.AnsibleUnsafeText object' has no attribute
'packages'\n\nThe error appears to have been in
'/etc/ansible/deployment/tasks/setfacts.yml':
line 49, column 3, but may\nbe elsewhere in the file depending on the exact
syntax

Re: [ansible-project] rpmbuild of ansible tarball results in error: line 9: Illegal char '$' in: Version: $VERSION

2017-11-24 Thread Toshio Kuratomi

This looks like you aren't getting the tarballs from the official source:
https://releases.ansible.com/ansible/

Note that we also are building nightly rpms (repositories for centos and
fedora).  Look in https://releases.ansible.com/ansible/rpm

-Toshio

On Nov 23, 2017 4:40 PM, "Ki-Hyun Sung"  wrote:

> Hi  Johannes
>
> I get this error when building from the tarball (ansible version 2.4.0.0),
> also on Centos 7
>
> *error: line 10: Illegal char '"' in: Release:
> 100.git20171124"".el7.centos*
>
> Just wondering if you ran into a similar issue? Googling that error
> message presents me with just two search results!
> One of which is this forum.
>
> Basically I have installed epel-release, asciidoc and rpmbuild packages.
> Then extracted the tarball, cd into the root of it, and ran make rpm.
> That is when I hit that issue.
>
> I am also not familiar with rpm build, or Linux in general - any help
> would be much appreciated!
>
> -Darren
>
>
> On Sunday, April 10, 2016 at 4:16:31 AM UTC+10, Johannes Kastl wrote:
>>
>> On 09.04.16 19:55 Johannes Kastl wrote:
>>
>> > Is there no rpm of the version you would like to have?
>>
>> I built a version of ansible for CentOS_7 on the opensuse
>> buildservice, if you want to give it a try:
>>
>> http://download.opensuse.org/repositories/home:/ojkastl_buil
>> dservice:/CentOS_Zeug/CentOS_7/
>>
>> Johannes
>>
>> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/a0ea06e2-4d8b-4e8e-8e74-a5eb9ff21283%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSUPm7vW%2Bi6%3D1yj70X_AF%2BCfxC13PW8EtNJgFdZrZKivQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Ansible - copy between servers

2017-11-22 Thread Toshio Kuratomi

With one exception, ansible is all communication between the controller
(where you run the ansible-playbook command) and the managed machines.  So
using copy you'd need to first fetch the remote files to the controller and
then copy them out to the other machines.

The one exception is the synchronize module.  Using delegate_to you can
copy between two remote machines provided that you can live with certain
limitations (ssh key authentication where at least one of the remote
machines can ssh to the other one [I use ssh agent forwarding if I have to
do this].  Very primitive privilege escalation which lacks many of the
features you're used to (password less sudo works).  A summary of
synchronize might read, operates in a different way than other modules
which is sometimes exactly what you need but also an endless supply of bugs
and missing features.

If synchronize doesn't satisfy your use case, using ansible to set up rsync
between your servers and using ansible or Cron to start the rsync job might
be a way to go.

-Toshio

On Nov 21, 2017 11:43 PM, "Amir Saar"  wrote:

> I'm kinda newbie with Ansible. I have a hosts file that contains 4 hosts.
>
> I also have a 'copymap' dictionary that I built in order to copy data
> (folders) between the servers (the full 'copymap' dictionary is much bigger
> than the example below).
>
> copymap:
>   - {service: "zeppelin", src: '3.3.3.3', dest: '2.2.2.2'}
>   - {service: "local_data", src: '4.4.4.4', dest: '1.1.1.1'}
>
> I would like to copy the data between the servers, when the source is
> copymap.src and the destination is copymap.dest.
>
> I know how to iterate using 'with_items', but I'm not sure I understand
> how I can specify source and destination *servers*. Did anyone used the
> built-in 'copy' module to copy from *dynamic* remote to remote servers?
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/4506c159-1216-4efc-ab07-ae1a24900208%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSOpDkV4FLjw7nXf0p9%2BsB7Eo0eMO4qsMr7wXiXnpT4Xw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Yum module update_cache doesn't work for RHEL in ansible 2.4.0.0

2017-11-09 Thread Toshio Kuratomi

It does.  From your description, it sounds like the RHEL repository
has a packageset that's generating conflicts in your install.  the
update_cache is likely just making the error in the repository
visible.

CentOS and RHEL pull from different repositories and don't always have
the same set of packages at the same time (and you could also have
different packages installed on the two machines which complicates
things further).

A better test for diagnosing this would be whether using yum from the
commandline (or via ansible's command module) on the RHEL box does the
same thing or a different thing from the ansible command.

-Toshio

On Thu, Nov 9, 2017 at 10:15 AM, Kuldip Madnani  wrote:
> The example shown in Ansible website shows that update_cache is executed
> when ansible_distribution is Centos.
>
> - name: install system updates for centos systems yum: name=* state=latest
> update_cache=yes when: ansible_distribution == "CentOS"
>
> The exact same command works for us when we run it on Centos without the
> when condition, however it hangs up for hours in RHEL and finally outputs
> with a long error message depicting conflicts..
>
> Does update_cache work in RHEL?
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/9a8e1b30-9fe8-4c48-875f-b734b19019b2%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSajKN-Z%3DZmmuPXCVrb3pAxMJDjPkTq%2Bx2JOdT7PbAAZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Re: pytest arugment error

2017-11-09 Thread Toshio Kuratomi

You need to pip install the test requirements as well.

On Nov 6, 2017 4:15 AM, "Jae Kim"  wrote:

> I had executed
>>
>>
>
>>  . hacking/env-setup
>>
>>   And then I executed
>   pytest -r a --fulltrace --color yes ./mymoduletest/my_new_test_
> module.py
> = test session starts
> ==
> platform linux -- Python 3.4.5, pytest-3.2.3, py-1.4.34, pluggy-0.4.0
> rootdir: /root/work, inifile:
> collected 0 items
>
> = no tests ran in 0.01 seconds
> =
>
>But when I execute
>pytest -r a --cov=. --cov-report=html --fulltrace --color yes
> ./mymoduletest/my_new_test_module.py
>I get
>pytest: error: unregnoized arguements: --cov=. --cov-report=html
>infile: None
>rootdir: /root/work
>
>
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/e4959aba-0a7c-49d1-8995-4a4d1260a47e%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaQzTvTVEU_7UN1qc0aZGyiDoeQMp6Wfbogm0Q9f9%3DxmPA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Re: pytest error message

2017-11-05 Thread Toshio Kuratomi

That depends.  Did you install ansible into system site-packages?  Or did
you check it out from source?

On Nov 5, 2017 6:02 PM, "Jae Kim"  wrote:

>
>
> $PYTHONPATH is empty. Should this be filled in with something?
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/ff2442e7-0a6e-470c-b833-f17b58ab2c8f%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaRSOxFS3vxmPUvRY%2B12XKLGk4FMARW0XC0CfFsXxKQ1Sw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Re: pytest arugment error

2017-11-05 Thread Toshio Kuratomi

You need to follow the other steps in that page to install the test
dependencies, then.  Just running the single pytest step won't set up the
environment to run the tests.



On Nov 5, 2017 5:10 PM, "Jae Kim"  wrote:

>
> It is a single step.
> I was following instructions from http://docs.ansible.com/
> ansible/latest/dev_guide/developing_modules_general.html#unit-testing
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/72938c1a-820e-4d15-8e8b-6f6b0764ece6%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaRcJJ6yANDwRH9Lg640uuH6HUxY79zW%3DCGHYHTrPQr9sw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Re: InsecureRequestWarning: Unverified HTTPS

2017-11-04 Thread Toshio Kuratomi

This seems to be coming from urllib3.  I don't think we have much affect
over it.  Since it's a warning it doesn't affect the program's operation.
Note that there is a change in 2.4.2 (will be i nthe next tarball) and
devel which might remove this usage of urllib3 if you're using
python-2.7.9+ so you may stop getting that warning once you get that
upgrade.

-Toshio

On Nov 4, 2017 6:33 AM,  wrote:

any ideas? thanks

On Thursday, August 31, 2017 at 7:40:45 PM UTC-7, barfin...@gmail.com wrote:
>
>
> Despite setting  cert validation as ignore and false, I still get the
> warning message. Any ideas? thanks
>
> Windows OS: Windows10 64bit 1703
> Linux Controller: RHEL 7.4
>
>
> # group_vars/windows.yml
> ansible_user: Administrator
> ansible_password: 
> ansible_connection: winrm
> ansible_winrm_server_cert_validation: ignore
> validate_certs: false
>
>
> #  ansible-playbook -i hosts windows-desktops.yml
>
> PLAY [Installing Packages] **
> 
> **
>
> TASK [Gathering Facts] **
> 
> **
> /usr/lib/python2.7/site-packages/urllib3/connectionpool.py:858:
> InsecureRequestWarning: Unverified HTTPS request is being made. Adding
> certificate verification is strongly advised. See:
> https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
>   InsecureRequestWarning)
>
>
> --
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-project@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/ms
gid/ansible-project/a8abadde-8b9c-48d8-aa00-a0a45a7d706c%40googlegroups.com

.
For more options, visit https://groups.google.com/d/optout.

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSGhyL6CWMONJCokSBp6b6GiDjoWHqKmyay1uApRDB%3D7g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] How pass an array of dictionaries to my custom module elegantly?

2017-11-03 Thread Toshio Kuratomi

You could probably do:

 {"/usr/local": "/usr/my/local",
  "/local/perl": "/usr/my/perl"}

That will work as long as order does not matter (if the replacements do not
cause there to be more or less of the replacer substrings). If you can't
guarantee that, then the list is better, although you can do single element
dicts or two element lists inside:

  [{"/usr/local": "/usr/my/local"},
  {"/local/perl": "/usr/my/perl"}]

  [ ["/usr/local", "/usr/my/local"],
  ["/local/perl", "/usr/my/perl"]]


On Nov 2, 2017 11:55 AM, "ZillaYT"  wrote:

I'm not trying to re-invent the "replace" module that Ansible has.

I'm trying to write a (my FIRST) custom module to encapsulate the
repetitive Linux source build process, namely,
- run ./configure $CONF_OPTS
- run make
- run make $TARGETS

However, i have an outlying case where I have to modify Makefile (ugh) that
./configure produces (not my idea), so my steps are now

- run ./configure $CONF_OPTS
- modify Makefile
- run make
- run make $TARGETS

If I was writing above steps using generic Ansible modules, I'd of course
use the replace module, like so, correct? This will change all the
instances of "/usr/local" into "/usr/my/local" and "/usr/perl" into
"/usr/my/perl" in my Makefile

- name: Update Makefile (ugh)
  replace:
dest: "/path_to/Makefile"
regexp: "{{item.old_str}}"
replace: "{{item.new_str}}"
  with_items:
  - {old_str: "/usr/local", new_str: "/usr/my/local"}
  - {old_str: "/local/perl", new_str: "/usr/my/perl"}


I want my module call to look like this. Or is there a better way to
represent the "modify_regex" parameters?

- name: Run configure, make, and make targets
  config_make_targets:
path: /path_to_source
modify_file: "Makefile"
modify_regex: [
  {old_str: "/usr/local", new_str: "/usr/my/local"},
  {old_str: "/local/perl", new_str: "/usr/my/perl"}
]


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-project@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/ansible-project/33f9c3fa-9f38-46c5-8be6-57fce225d389%40googlegroups.
com

.
For more options, visit https://groups.google.com/d/optout.

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaTO3mixTPBRzJVb9q1A%2Bsk63TwVrMt1hVgSmGKt8vNJaA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] pytest arugment error

2017-11-02 Thread Toshio Kuratomi

Could you go through your shells' history and reporter precisely which
steps from that page you have performed?  It looks like you've missed a
step or two.

On Nov 2, 2017 5:58 AM, "Jae Kim"  wrote:

> Hi
>
>
>
> Following the command in this manual
>
> http://docs.ansible.com/ansible/latest/dev_guide/developing_
> modules_general.html
>
>
>
> When I run the following command
>
> pytest -r a --cov=. --cov-report=html --fulltrace --color yes
> test/units/modules/.../test/my_new_test_module.py
>
>
>
> the follow error message comes out.
>
>
>
> pytest: error: unrecognized arguments: --cov=. --cov-report=html
>
> --
> 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-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/4c635a56-5e29-4744-8979-431e68af5263%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAPrnkaSd7rwrba87BAW2s5WnETiLW1Wff15VyXTTqhs%2BnZ%2BTyA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] pytest error message

2017-11-02 Thread Toshio Kuratomi

How are you arranging for ansible to be in your PYTHONPATH?

-Toshio

On Nov 2, 2017 5:58 AM, "Jae Kim"  wrote:

> Hi
>
>
>
> When I run the following command
>
>
>
> pytest -r a -fulltrace --color yest my_new_test_module.py
>
>
>
> I get the following error message.
>
>
>
> = test session starts
> ==
> platform linux -- Python 3.4.5, pytest-3.2.3, py-1.4.34, pluggy-0.4.0
> rootdir: /root/work/mymoduletests, inifile:
> collected 0 items / 1 errors
>
> === short test summary info
> 
> ERROR my_new_test_module.py
>  ERRORS ==
> ==
>  ERROR collecting my_new_test_module.py
> 
> [31mImportError while importing test module '/root/work/mymoduletests/my_n
> ew_test_module.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> my_new_test_module.py:63: in 
> from ansible.module_utils.basic import AnsibleModule
> E   ImportError: No module named 'ansible' [0m
> !!! Interrupted: 1 errors during collection
> 
> === 1 error in 0.13 seconds
> 
>
>
>
>
>
> my_new_test_module.py is
>
>
>
> #!/usr/bin/python
>
> ANSIBLE_METADATA = {
> 'metadata_version': '1.1',
> 'status': ['preview'],
> 'supported_by': 'community'
> }
>
> DOCUMENTATION = '''
> ---
> module: my_sample_module
>
> short_description: This is my sample module
>
> version_added: "2.4"
>
> description:
> - "This is my longer description explaining my sample module"
>
> options:
> name:
> description:
> - This is the message to send to the sample module
> required: true
> new:
> description:
> - Control to demo if the result of this module is changed or
> not
> required: false
>
> extends_documentation_fragment:
> - azure
>
> author:
> - Your Name (@yourhandle)
> '''
>
> EXAMPLES = '''
> # Pass in a message
> - name: Test with a message
>   my_new_test_module:
> name: hello world
>
> # pass in a message and have changed true
> - name: Test with a message and changed output
>   my_new_test_module:
> name: hello world
> new: true
>
> # fail the module
> - name: Test failure of the module
>   my_new_test_module:
> name: fail me
> '''
>
> RETURN = '''
> original_message:
> description: The original name param that was passed in
> type: str
> message:
> description: The output message that the sample module generates
> '''
>
> from ansible.module_utils.basic import AnsibleModule
>
> def run_module():
> # define the available arguments/parameters that a user can pass to
> # the module
> module_args = dict(
> name=dict(type='str', required=True),
> new=dict(type='bool', required=False, default=False)
> )
>
> # seed the result dict in the object
> # we primarily care about changed and state
> # change is if this module effectively modified the target
> # state will include any data that you want your module to pass back
> # for consumption, for example, in a subsequent task
> result = dict(
> changed=False,
> original_message='',
> message=''
> )
>
> # the AnsibleModule object will be our abstraction working with Ansible
> # this includes instantiation, a couple of common attr would be the
> # args/params passed to the execution, as well as if the module
> # supports check mode
> module = AnsibleModule(
> argument_spec=module_args,
> supports_check_mode=True
> )
>
> # if the user is working with this module in only check mode we do not
> # want to make any changes to the environment, just return the current
> # state with no modifications
> if module.check_mode:
> return result
>
> # manipulate or modify the state as needed (this is going to be the
> # part where your module will do what it needs to do)
> result['original_message'] = module.params['name']
> result['message'] = 'goodbye'
>
> # use whatever logic you need to determine whether or not this module
> # made any modifications to your target
> if module.params['new']:
> result['changed'] = True
>
> # during the execution of the module, if there is an exception or a
> # conditional state that effectively causes a failure, run
> # AnsibleModule.fail_json() to pass in the message and the result
> if module.params['name'] == 'fail me':
> module.fail_json(msg='You requested this to fail', **result)
>
> # in the event of a successful module execution, you will want to
> # simple AnsibleModule.exit_json(), passing the key/value results
> module.exit_json(**result)
>
> def main():
> run_module()
>
> if __name__ == '__main__':
>

1 2 3 4 >

1 - 100 of 321 matches

Mail list logo