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.

Red Hat Enterprise Linux is used within our organization to orchestrate a multitenant, microservice-based architecture. This supports a distributed system of predominantly web-based applications and frontends. A typical deployment involves around 60 to 70 Amazon EC2 instances working in concert.

The primary use cases involve running interconnected applications with requirements such as low latency and high availability, often achieved through redundant, multi-tenant, and load-balanced architectures. These applications may utilize read or write-optimized instances or be memory or processor-optimized, depending on their specific needs. Optimization is achieved through the processor, RAM, and connected protocols. The foundation for these applications is Red Hat Enterprise Linux.

Red Hat Enterprise Linux facilitates seamless workload migration between diverse cloud environments and data centers. In DevOps, workload portability between cloud and data centers is crucial, so we prioritize operating systems supported by multiple cloud providers and available locally. Key considerations include stability, security hardening capabilities, and the ability to obtain government or compliance organization approvals, which are incredibly stringent in sectors like banking and securities exchange. Red Hat Enterprise Linux meets these requirements by providing a secure, reliable, and consistently delivered operating system that facilitates approvals and ensures seamless workload mobility.

Regarding Red Hat Enterprise Linux provisioning and patching, both processes are generally straightforward. Patching can be completed within a few hours. Once the automation pipelines are properly configured, tested, and operational, provisioning can be fully automated. This applies to any operating system, not just Red Hat. Setting up a correct pipeline ensures smooth provisioning regardless of the OS.

Implementing Red Hat Enterprise Linux has resulted in significant resource savings due to its efficient usage of minimal resources. Compared to other operating systems, Red Hat Enterprise Linux requires less RAM and CPU allocation, which translates to cost savings. Additionally, its stability and minimal downtime contribute to operational efficiency.

The solution is used for on-premises data centers. Multiple private data centers run workloads on VMware Cloud solutions, and Red Hat Enterprise Linux is deployed on critical systems. We use KVM virtualization technology to host various virtual machines on Red Hat Enterprise Linux that run workloads and applications.

Red Hat Enterprise Linux improved our compliance by working with third-party security providers, like CIS Enterprise Internet Security. It's a nonprofit organization that provides many security solutions and benchmarking for each operating system. CIS and Red Hat jointly developed a CIS-approved operating system. They work with various public cloud providers like App Engine, Google, and AWS to provide comprehensive CIS-approved images in Red Hat Enterprise Linux. 

The US federal government has already certified the OS for FIPS compliance. FIPS is the organization that designs cryptography algorithms for federal agencies, and they approved Red Hat Enterprise Linux. 

It takes some time to realize the benefits. Some customers cannot see a direct benefit because the licensing is a bit complex. In a huge enterprise environment, you could see an immediate effect, but a smaller or medium-sized organization may take a while to yield a return on investment.

A lot of our Red Hat operating systems run middle-tier applications. We are mostly a JBoss shop, so they are homegrown applications. They are Java-based. We have several types of applications. We have identity, security, Oracle database, etc.

Red Hat Enterprise Linux helps with standardization. A lot of middle-tier applications hosted in the data center or in the cloud are unified in one standard operating system, which is Red Hat Enterprise Linux. On the data center side, we only have Red Hat Enterprise Linux. We have one unified operating system.

For our containerization projects, we are looking into OpenShift. Our Ansible Automation Platform executioner uses container-based Red Hat Enterprise Linux. We use Podman. We have moved to the Red Hat Podman container. It is a lot easier. We can scale up easily and manage it. It reduces the security risk. We do not have to worry about patching. We can just image a new container that is up to date. That is great.

We had a situation where we had to create an image for Red Hat Enterprise Linux 9, and there were built-in playbooks for hardening the system. We were able to run that and create the image. It made the work much easier than it used to be in the past.

Red Hat Insights provides vulnerability alerts and targeted guidance. It has that capability. It has a lot of features built in that not only help with security but also with misconfigurations. If a system is misconfigured, it detects that. It gives you the solution for the problem it captured. It is a great tool, but we have been focusing on the security perspective. We have not been focusing on operating system configurations. I have not yet looked at the new version, but in my opinion, it would be better if Red Hat puts a lot of focus on Insights and take it to the next level where the company could use it for its OS compliance.

We deployed Red Hat Enterprise Linux on-prem and in the cloud as a fallback.

We are a private cloud provider and we host Linux ourselves because they are tough to manage.

We offer our customers the option to host their Red Hat Enterprise Linux on Azure or on our private cloud.

Red Hat Enterprise Linux's built-in security features help simplify risk reduction. Red Hat offers a subscription service that provides critical security updates within 24 hours. The service also includes an excellent database of known security vulnerabilities. If a CVE identifier is known for a vulnerability, it can be entered into the web interface. The web interface will then indicate whether Red Hat Enterprise Linux is affected by the vulnerability and what steps need to be taken to fix it. The fix will be included in the next security update. This is a valuable security feature that helps organizations to stay up-to-date on security patches and mitigate risk.

The portability of applications and containers built on Red Hat Enterprise Linux is beneficial for keeping our organization agile. Red Hat Enterprise Linux 8 and 9 include Podman, a newer software similar to Docker. Podman was built to address the problems that Docker had with creating and running containers, and it also includes the support of Red Hat. There is a good synergy between Red Hat and Podman.

Red Hat Enterprise Linux has helped improve our organization. We provide a service to our clients, which they pay for each month. This service includes our support. Red Hat Enterprise Linux is a stable operating system, so we do not have to provide much support. When we do need to provide support, it is usually for an application, not for the operating system.

I can build with confidence and ensure availability across physical and virtual cloud infrastructures using Red Hat Enterprise Linux. I have been using Red Hat Enterprise Linux on-premises since 2008 without any problems. It is easy to automate. Virtualization is always present, so I work with virtual machines. Red Hat Enterprise Linux is very easy to deploy on a virtual machine. We can create a virtual machine, and if we are working with VMware, we can create a template to use for new systems. There is no need for a classic installation.

We use Red Hat for all sorts of use cases. This includes everything from running applications and databases, or the combination thereof, to building software for products that we use for embedded design.

My company has several RHEL implementations deployed in the field, including versions 4, 5, 6, 7, and 8.

RHEL allows us to run multiple versions of the same application with no problem. We have specific databases and specific versions of them running for the support team, even though some of them are not in support. It has lots of features for things like containerization.

We use a fair bit of Red Hat including other products such as Red Hat Satellite, Red Hat Insights, Red Hat Ansible, and Ansible Tower. We have also attempted to look at an OpenShift PoC. Red Hat seems to be doing a great job integrating their products. For instance, Satellite 7 will finally have all of the Puppet functionality Ansiblized. Overall, they're doing a great job integrating their stack to help make it better.

Having this integrated solution approach provides us with greater operational excellence because we can see what somebody is building. We have the environment captured and have visibility about what went into it for repeatability, reproducibility, scalability, and lots of other benefits.

We mainly use Red Hat Enterprise Linux for general applications. We have Red Hat Enterprise Linux for identity management. We use it for NTP services. Most of the bank services that run on Linux run on Red Hat Enterprise Linux. Our core applications include bank cards solutions.

It is a stable operating system, and that is why we use it. We have many team members who understand how to use Red Hat Enterprise Linux, so it's much easier to use this version of Linux to deploy services.

There is ease of use. A lot of resources are available online if the team wants to understand something. There is also the ability to use various automation tools to run multiple tasks.

For risk reduction and compliance, we have CIS benchmarks. There are various configuration files that we are able to update and change. Using the benchmarks available from CIS, I can have a template and automate that across multiple machines using automation features such as Ansible. When examining permissions for file systems, enabling login, and enabling file integrity, these are the items we would use for security.

I typically use Red Hat Enterprise Linux (RHEL) in my federal government contracts. Federal government customers are the only ones that use Red Hat Enterprise Linux.

Most government agencies use Red Hat Enterprise Linux because they have a requirement for commercial support. That is the only reason why Red Hat Enterprise Linux gets used over any other Linux distribution.

The only reason our clients use Red Hat Enterprise Linux is because Red Hat offers commercial support. 

Red Hat Enterprise Linux is a solid product. They have decent support, although not the best. They have a good knowledge base and a well-developed ecosystem.