Red Hat Enterprise Linux (RHEL) Reviews

I have been a sysadmin handling everything about Red Hat Enterprise Linux, primarily for on-premises environments. I have built projects based on Red Hat Enterprise Linux, including development and support projects in the companies. I have handled pretty much everything. Anything you can imagine, I have probably done with it.

In terms of security, it does a lot of things that most people still turn off. SELinux is turned on by default. They have pretty good firewall rules in their defaults. The audit rules always take tweaking, but, overall, it comes out of the box not too bad. I used to write scripts to harden them from there.

There are multiple ways to provision and patch. You have everything from local repositories to doing it by hand.

Their knowledge base is incredible. There is so much information out there. It has never taken me longer than 30 minutes to find an answer to anything, even very tough ones.

One company I worked for was a security company, and we did a lot of patching on everything. It was designed around security and email hosting, and uptime was pretty much whatever we wanted it to be. I have had a couple of times when the uptime was bad, but it was caused by a third-party solution. In fact, the Norton antivirus was definitely the worst. Red Hat had nothing to do with it.

Our main use cases for Red Hat Enterprise Linux (RHEL) at our company involve it being our primary operating system for most of our servers. We're about 80% Red Hat Linux, 20% Windows.

The feature of Red Hat Enterprise Linux (RHEL) I appreciate the most is the ability to build images from the Red Hat pipeline, which is very effective. 

We also have an on-prem image management system that works really well with Red Hat. These features of Red Hat Enterprise Linux (RHEL) benefit our company since they allow us to perform life cycle tasks faster.

Our upgrade or migration plans to stay current with Red Hat Enterprise Linux (RHEL) are that our operating strategy is to put all net new on 8.10, and we are going to stay on 8.10 until 9.10. We typically just stay on the long-term release.

In my current company, we use Red Hat Enterprise Linux (RHEL) for our mission-critical applications, such as Oracle and MS, and we have Oracle database workloads running on it. 

We use Ansible, which is hosted on Red Hat Linux, along with many other applications. From an overall standpoint, we use Red Hat. We are in the process of migrating to Red Hat from various other operating systems such as AIX, IBM workloads, to Red Hat. 

The simplicity of use is a pain point that Red Hat Enterprise Linux (RHEL) solves for us. Many other operating systems, from a security vulnerability standpoint, have very rare releases. Red Hat releases monthly patching schedules with vulnerability remediations happening every week. To be concurrent, Red Hat is a very good platform since you get a great deal of support and patches. The patching schedule and support we get from Red Hat Enterprise Linux (RHEL) is beyond any other Linux flavors available.

We have a monthly patching cycle for Red Hat and Red Hat releases patches pretty much every week. Many RHSA releases are available for Red Hat. We can do weekly patches. That said, due to downtime considerations, we have controlled it to a monthly schedule. From a security standpoint, our vulnerability scans are clean on the Red Hat side, while with Windows, it's painful to manage the vulnerabilities.

More applications are adopting a Red Hat way of operating. I personally observed many application teams port their applications to Red Hat due to these vulnerability considerations. Red Hat Enterprise Linux (RHEL) scales ahead of the game with the growing needs of my company. My company is a utility-based company where security is paramount. Every month, we get scan reports from various security and remediation tools. The Red Hat area is clean. Once you patch, even if there are missing patches, it still gets patched. The burden of patching is minimized with Red Hat. You just do an update and it gets patched to the latest version without worrying about outstanding vulnerabilities. When new vulnerabilities are released, Red Hat has been really supportive. If you open a ticket and ask them about a new vulnerability, they provide a timeline and a patch if it's critical.

Our main use cases for Red Hat Enterprise Linux (RHEL) currently involve general server workload, including numerous Oracle-based workloads.

The features of Red Hat Enterprise Linux (RHEL) that I appreciate the most include the most recent iterations such as no-downtime patching, live patching, and the ability to snapshot or snapshot LVM's; these features are more of a Linux capability, however, they have been really beneficial to us. 

High availability has been extremely beneficial for us to support. These features benefit our company by providing less downtime. We are not taking downtime to do patching on tier-one systems, and we spend less manpower and time to perform the types of automation and management that would normally take considerable time to accomplish hands-on, resulting in significant time savings.

Security requirements are always a consideration in choosing Red Hat Enterprise Linux (RHEL) in the cloud. Anytime we make any decision, security is definitely one of the foremost considerations we have taken place.

The biggest thing we look for is the ability to abide by STIG, as we do, and then apply our NIST policies as well as our defined HIPAA policies; Red Hat Enterprise Linux (RHEL) makes that a really easy process through the automation aspects.

We manage our Red Hat Enterprise Linux (RHEL) systems for provisioning and patching using a combination of VMware vRealize for actual deployment, and then we use Ansible Automation for the day-two configuration and lifecycle. Once software deployments and configurations are all Ansible automation, it couldn't work any better for us. As long as you have a coding background and understand YAML, Ansible works fantastically.

My main use case for Red Hat Enterprise Linux (RHEL) is application servers, and it's all of our VMs. Most, if not all, of our physicals, on the Linux side, are Red Hat. The only thing that we run that isn't Red Hat is our Kubernetes nodes.

The feature of Red Hat Enterprise Linux (RHEL) that I find most interesting is image mode, which has ramifications far beyond just upgrading the OS. Speed to market and zero day could really be accelerated leveraging it. 

Red Hat Enterprise Linux (RHEL) benefits my company at the end of the day by providing the foundation of Red Hat Linux, over 20 years and more. Coupled with the backing of a company such as IBM, you've got a company that can help solve pretty much any problem. 

It's the flexibility, almost the one-stop-shop nature, that Red Hat provides, that really creates an administrative-friendly environment.

The package manager is pretty solid now with DNF, which is the industry standard.

Red Hat Enterprise Linux (RHEL) helps solve quite a few pain points; I would say that in RHEL 8 to RHEL 9, when they went to AppStreams, it really helped simplify the repository structure and made package management significantly easier.

I wasn't part of the discussion about whether security requirements were a consideration in choosing Red Hat Enterprise Linux (RHEL) for our cloud operations, however, my guess is that it had to do with being able to do configuration management across on-prem and cloud in the same manner in both environments.

We manage our Red Hat Enterprise Linux (RHEL) systems through Red Hat Satellite, which we do not use to provision but only to patch, while provisioning is done through vRealize Automation. That's how we provision all of our VMs and custom builds, though there is additional infrastructure behind that.

Red Hat Enterprise Linux (RHEL) supports our hybrid cloud strategy as we are currently in the process of investigating different VM hypervisors, and as that investigation goes on, OpenShift is definitely at the forefront of the things we are looking at.

My main use cases for Red Hat Enterprise Linux (RHEL) involve running a lot of applications that run on Linux, as my company is more Linux-based than Windows, so we prefer Linux over Windows.

The feature of Red Hat Enterprise Linux (RHEL) that I appreciate the most is the logical volume feature as it's so easy to increase partitions and disk space. This logical volume feature benefits my company as sometimes we have a client whose data storage needs are unknown at the outset, allowing us to start small. As things increase, we can easily increase it without taking the server down, and we can do it seamlessly while the server is online.

One of the pain points that Red Hat Enterprise Linux (RHEL) helps me solve is security, as RHEL is more secure than Windows. I have migrated from RHEL 6 to RHEL 7 to RHEL 8 to RHEL 9, however, it's just been a manual install; while Red Hat has a tool to use for migrations, I've never used that and have just reloaded to the new version. The upgrade wasn't bad at all; it was actually a smooth upgrade.

When it comes to managing my Red Hat Enterprise Linux systems for provisioning and patching, I use Ansible Tower, and I'm very satisfied with that. It allows me to schedule jobs and go to sleep while looking at the email in the morning. That's a very effective and efficient product for me.

My upgrade or migration plans to stay current involve starting eventually, especially since I work in the government world, where we use their tools to harden the system. When those tools are available, we'll start looking to migrate to the next version of Red Hat. When those tools are ready, we'll start putting RHEL 10 into our development environment to start testing.

My main use cases involve using it to run our Ansible automation platform and various workloads, depending on what Development decides based on the project. We also use it for our Kubernetes clusters.

The features of Red Hat Enterprise Linux (RHEL) that I appreciate the most are focused on stability. It is a reliable system that I can depend on more than anything else. That stability benefits my company by providing more uptime and more satisfied gamers.

Red Hat Enterprise Linux (RHEL) helps us solve pain points related to stability and documentation. It is very easy to find solutions to problems or access official documentation, whereas with other Debian-based distributions, one often finds themselves searching through random forums.

Regarding built-in security features for risk reduction and compliance maintenance, some features are straightforward when following standards and installation profiles. However, the development side frequently mentions challenges with SELinux, as it is more difficult to understand and somewhat esoteric. Some features are very well-developed and easily understood, while others are more complex to implement.

Red Hat Enterprise Linux (RHEL) has helped to mitigate downtime and lower risks. While there is not much technical difference between RHEL and Oracle Linux, compared to other alternatives, it provides benefits.

We manage our systems for provisioning and patching using Ansible automation controller for patches and mirror repositories as needed.

My main use case for Red Hat Enterprise Linux (RHEL) is application hosting.

The feature of Red Hat Enterprise Linux (RHEL) that I appreciate the most is the stability. 

I used to use Ubuntu quite a bit, however, the stability of RHEL is the main thing that I enjoy about it. 

RHEL benefits my company by providing a stable platform and strong support behind it, which are the motivating factors of using it in general.

Red Hat Enterprise Linux (RHEL) helps me solve pain points such as support stability, so maintenance and operations are much easier. I manage my Red Hat Enterprise Linux (RHEL) systems for provisioning and patching using Ansible, Satellite, and Puppet, and I am satisfied with that management experience.

Red Hat Enterprise Linux (RHEL) supports my hybrid cloud strategy by looking into Openshift. Currently, we are independently deploying between the two environments because we do not yet have a platform to bridge those into a true hybrid.

Security requirements were not necessarily a consideration in choosing Red Hat Enterprise Linux (RHEL) in the cloud since we have our security team for all of our security compliance, so it is just our standard that we use.