Re: ansible1.9 package

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/03/2017 06:09 AM, Peter Rex wrote:
Security flaws mean nothing to the application I use Ansible for, but stability does. Control servers are in private networks, and they configure equipment guarded by murderous thugs, so no problem there.

The control servers don't get updated that often, but when they do, it's not good if things stop working, because, you know, the equipment they configure is owned by people who employ murderous thugs to guard it. Kind of a problem.

We originally looked at Ansible and thought, OK, Red Hat, nothing more stable than that. Ansible, flagship product. It seemed like a good bet, but turned out not to be, that Red Hat wasn't likely to deprecate a major version of a software package during the lifetime of one of its operating systems, in this case EL6. Given how much of a moving target Ansible has turned out to be, I definitely should have subscribed to epel-announce, to, you know, minimize the chance of getting murdered, but here we are.

Make sure that the murderous thugs do not find out that you confused the stability of RHEL ( which is a commercial product backed by an enterprise which asks for money and delivers services ... and rather long term stable APIs for most of the software they offer  ) with the one of EPEL which is a community-driven-best-effort-based product

    wolfy ( Who's not afraid of murderous thugs because he's protected by a murderous 3mo old cat -- it murdered several toys already)


Anyhow, thanks for the feedback.


On Thu, Nov 2, 2017 at 2:48 PM, Kevin Fenzi <kevin@xxxxxxxxx> wrote:
On 11/02/2017 11:03 AM, Peter Rex wrote:
> Thanks for the info, Ricardo. Hadn't found the retirement notice. Security,
> I guess. I can't resist saying, though, that I regret using Ansible and my
> assumption that one of the Es in EPEL stood for Enterprise. Oh well, live
> and learn.

Sorry things didn't work out as you would have liked.

ansible1.9 was always intended as a short term 'bridge' to help give
folks more time to migrate to 2.0. When upstream stopped supporting it,
we retired it in EPEL as well. ansible is very very fast moving and
complex and there's no way we could backport even security fixes to an
out of date 1.9 version. Sorry.

You can of course still use 1.9 if you wish, just realize that it
doesn't get any bugfixes or security updates.

_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux