Hello everyone,
We're happy to announce the release of the Ansible 8.1.0 package!
Ansible 8.1.0 includes ansible-core 2.15.1 as well as a curated set of
Ansible collections that provide a vast number of modules and plugins.
How to get it
Hello everyone,
We're happy to announce the release of the Ansible 8.1.0 package!
Ansible 8.1.0 includes ansible-core 2.15.1 as well as a curated set of
Ansible collections that provide a vast number of modules and plugins.
Please: stop claiming this. ansible-core is a required dependency, not
contained within the ansible packages. Pip install builds the
dependency, but it can be built and installed quite independently of
the "ansible" distribution.
Nico Kadel-Garcia
Hello Nico,
<snipped>
Please: stop claiming this. ansible-core is a required dependency, not
contained within the ansible packages. Pip install builds the
dependency, but it can be built and installed quite independently of
the "ansible" distribution.
Thank you for pointing this out. I truly appreciate it.
I will edit the wording of the release announcements to match to what
happens, under the hood, technically. How does this sound?
Ansible 8.1.0 requires latest version of ansible-core 2.15 and
includes a curated set of
Ansible collections that provides a vast number of modules and plugins.
<snipped>
Looking forward to hearing from you.
Cheers,
Anwesha
That sounds *fabulous*. Thank you very much. The ansible documentation
is a bit vague on the distinction as well.
If you're revising the release or installation notes, perhaps you
could mention the python version requirement? The current ansib-core
2.15 or later requires python 3.11 or later. And some supported
systems, like RHEL 7, don't have such recent python as a supported
option. It's why I would recommend using RHEL 8 or 9 for ansible
servers.
Hi Anwesha,
before we start modifying the announcement, can we please first have it
in a public GH repo - say
https://github.com/ansible-community/ansible-build-data/tree/main/docs
- and then discuss these changes in a PR so it's clear to everyone
involved what exactly the diff is?
Cheers,
Felix
Hi Anwesha,
before we start modifying the announcement, can we please first have it
in a public GH repo - say
https://github.com/ansible-community/ansible-build-data/tree/main/docs
- and then discuss these changes in a PR so it's clear to everyone
involved what exactly the diff is?Cheers,
Felix
Felix, the provenance of the "ansible" package is really a bundle of
"ansible galaxy collections", It's not from a single project. It's
built from more than 100 distinct modules, most of which have their
own git repo. Take a look at this to see the build tool used to
generate that tarball.:
https://github.com/ansible-community/ansible-build-data/blob/main/8/ansible-8.1.0.deps
And yes, this is very confusing, especially because ansible-core comes
from the mismatched git repo name:
https://github.com/ansible/ansible
Can we just fix the one thing right now?
Nico Kadel-Garicia
Hi Nico,
Felix, the provenance of the "ansible" package is really a bundle of
"ansible galaxy collections", It's not from a single project. It's
built from more than 100 distinct modules, most of which have their
own git repo. Take a look at this to see the build tool used to
generate that tarball.:
I'm fully aware of how the ansible PyPI package is built.
Can we just fix the one thing right now?
We have two things here: we have the ansible PyPI package, and we have
Ansible as the 'thing' that users use.
The new suggestion is perfect from a technical point of view, when
talking about the ansible PyPI package. But it is NOT perfect when
looking at Ansible, as described by the Ansible docsite
(https://docs.ansible.com/ansible/latest/) and the Ansible changelog
(https://github.com/ansible-community/ansible-build-data/blob/main/8/CHANGELOG-v8.rst).
I'm against changing something so that one aspect of it is better, but
another gets worse, without this being properly discussed first.
Cheers,
Felix