3 ms·
That's interesting, to me he's the Ansible role guy. He has hundreds of roles, and I've used dozens for F500 clients on RHEL. Him moving away from it means RedH
by theossuary 3y ago
That's interesting, to me he's the Ansible role guy. He has hundreds of roles, and I've used dozens for F500 clients on RHEL. Him moving away from it means RedHat in all likelyhood will have to pickup the slack and start creating hundreds of supported Ansible roles for RHEL OSes. Wonder if they'll release the source, or require the subscription level with Ansible/Tower to get access to them heh
- bravetraveler 3y agoI trust Jeff is making decent choices in his modules to support the distributions he's offering (including very similar derivatives) By doing this, there's certainty that a lot of what's written will work just fine on RHEL. It's a huge Python library with the express purpose of abstracting away annoying OS quirks CentOS Stream <-> RHEL is basically point releases. You're generally well past this stage by using Ansible. At most you want to care about the OS family, treating the derivatives as part -- Debian, Red Hat, etc. Focusing mostly on binary/config file path quirks There may be certain traits about RHEL users that will bring some issues eg: more likely actually using SELinux, have forgotten to tend to their subscriptions, or are aiming for more strict compliance