I am finally after 2+ years working on learning to work with and write Ansible.
I have a server I built that I intend to install Ansible on but with an RPM hopefully from a repo; it will be my Ansible Control Node. I also have 4 other VMs that I am going to treat as my Ansible Managed Nodes.
The problem is if I attempt to perform a dnf install ansible* I do not see ansible-core or a package simply called “ansible.”
Is ALMA Linux not supporting Ansible in any way? Seems like a silly question but I am not finding what I would expect to be run-of-the-mill packages available.
@jlehtone do you use Ansible at all? I am wondering if I should add the epel-release. I had to dig a little deeper than I would hope but found instructions to install epel-release and then install ansible, both using yum|dnf.
Yes, I do, but I run most of it from CentOS 7 machines. (The managed systems have been CentOS 5, 6, 7, 8, and Alma 8, 9.)
I did use EPEL-version for a while, but then found CentOS SIG repos, which like module streams do not rebase. So now I do have done:
dnf install centos-release-ansible-29 # to get repo
dnf install ansible # to get program
However, the Ansible 2.9 is old now, and if RHEL 8.6 will have ansible-core and EPEL add more tools for it, then it makes sense to do now:
dnf install epel-release # to get repo
dnf install ansible # to get program
(If one is running from Alma, ect. With CentOS 7 I have to consider more carefully whether it makes sense – there will be some porting of playbooks, I presume.)
I’ve written most of the roles and playbooks that I use myself as that did support learning the tool.
Red Hat offers “system roles” now and documents them within RHEL docs, so those are a good option too.
Things are very different now than what they were a month ago. Now RHEL 8 and 9 (and hence AlmaLinux 8 and 9) do provide ansible-core – no more need to resort to third-party repositories.
Besides, pip modules you install mainly for personal use of a regular account, and then you have to update them in addition to updating managed packages. (But obviously you can have an Ansible play that does both …)
Upside is one can install specific versions, which include bugfixes and perhaps features.
And if you want to use Ansible in an environment, it’s nice to have it installed on one regular account, e.g. an ansible account…
Nevertheless, OP got what he wanted