Red Hat Enterprise Linux (RHEL) Reviews

I have been using Red Hat Enterprise Linux (RHEL) regularly in my current role since 2021, and I leverage RHEL for our daily Linux administrator administration tasks, orchestration tasks, patching, monitoring, and self-healing, while ensuring compliance with all security standards. From a product perspective, RHEL's robustness allows us to use Ansible, Jenkins, and ArgoCD to optimize our CI/CD processes, and we manage more than 50 clusters across five regions: Amer, Paris, Hong Kong, North Singapore, ensuring all deployments are secure. It is reliable and offers enterprise support, making it suitable for scaling workloads in both on-prem and cloud environments.

I have been using Red Hat Enterprise Linux (RHEL) on a daily basis as a foundation for my DevOps and Kubernetes infrastructure tasks, where it stands out as a primary tool for managing clusters. I regularly monitor system administration tasks such as patching, performing OS level troubleshooting on RHEL servers, and executing kernel updates on a monthly cycle, all while leveraging automation using Ansible. For monitoring, we utilize Prometheus, Grafana, and Kibana to visualize performance metrics, health checks, and set up alerts for CPU, memory, and disk usage on RHEL nodes. Regarding container orchestration on Kubernetes, we are responsible for deploying and maintaining workload shifts on OpenShift and Kubernetes clusters, which are built on RHEL nodes to ensure stability and scalability. Thus, RHEL is a core VM for both Kubernetes and OpenShift, with OpenShift being the main focus to ensure our infrastructure is stable and ready for daily use.

The best features I have seen in Red Hat Enterprise Linux (RHEL) include its scalability, enterprise-grade security, and stability. It incorporates features such as SELinux, kernel live patching, and RBAC systems, making it very reliable for production environment workloads, allowing for automated cycle processes akin to Kubernetes, which can manage itself over long-term stability, demonstrating good, consistent performance along with integrated Linux support via Ansible and OpenShift. Thus, RHEL is a trustworthy platform.

Compared to other operating systems, Red Hat Enterprise Linux (RHEL) is specifically designed for production environments. It integrates tightly with OpenShift, Ansible, and other tools that others cannot deeply support. RHEL seamlessly works in hybrid cloud and container platforms, and in comparison to Windows, RHEL provides greater flexibility for containerization and DevOps-related tools, making it a more reliable option.

In Societe Generale, Red Hat Enterprise Linux (RHEL) has helped us maintain a secure environment across our container platforms through SELinux and kernel patching, which has directly lowered the risk of downtime and improved trust in the system. Notably, the ability to automate server patching and manage cluster upgrades has eliminated the need for manual intervention, significantly reducing errors and saving several hours of work. As a result, our team can focus on more innovative topics rather than repetitive tasks, leading to improved deployment times and increased reliability by around 20 to 25%. Overall, RHEL has made scaling applications in hybrid cloud environments much smoother, positively impacting my organization by providing a stable and secure platform.

By using Red Hat Enterprise Linux (RHEL), our team saves approximately 10 hours per week on routine patching and monitoring housekeeping tasks, which allows us to focus more on innovation topics. The time saved has led to improved knowledge among the team on how to create pipelines and better support application teams, thereby positively influencing delivery timelines and productivity.

Red Hat Enterprise Linux (RHEL) is stable and secure, but I think one area for improvement is that licensing should be automatically updated, particularly in multiple environments. Additionally, a faster GUI experience would save time, which would enhance usability.

From the suggestions for improvements, I would advocate for simplifying license management and providing a more efficient web console that can run RHEL faster. Furthermore, built-in tools for monitoring and automation should be made easier to grasp, as we create many dashboards using Grafana, which are much needed.

I have been working in my current field for more than four years.

I have only used Red Hat Enterprise Linux (RHEL) and did not evaluate other options, as RHEL is very stable and designed according to its lifecycle. My consistent experience with RHEL underpins its foundation for OpenShift and Kubernetes clusters, supporting critical applications without unexpected failures, especially with Ansible handling our patching, which contributes to better stability.

From an organizational perspective, Red Hat Enterprise Linux (RHEL) pricing is justified for entry-level support, especially given the long lifecycle of kernel patching. Once deployed, RHEL demonstrates smooth operations that considerably reduce long-term operational costs. Utilizing RHEL with automation saves both time and money by preventing manual patching and minimizing downtime, allowing users to focus on more valuable tasks. Despite the initial setup effort, once implemented, RHEL significantly delivers savings in both money and time through automation, resulting in smoother daily operations.

Red Hat Enterprise Linux (RHEL) exhibits high scalability, as adding more CPU, memory, and storage to a single system is seamless within my organization, enabling applications to scale easily across on-premises clusters. I could rate its scalability between 8 to 10 on a scale, as it provides enterprise-grade stability and flexibility for workload scaling in various environments, whether they consist of a few servers or thousands. The primary area needing improvement is the speed of scaling operations.

My advice for others considering Red Hat Enterprise Linux (RHEL) is to take full advantage of its automation capabilities and how the system is set up. Utilizing tools such as Ansible can save considerable time across patching, upgrades, and other administrative tasks. I recommend focusing on RHEL's scaling capabilities compared to other operating systems and highlighting the efficiency of the monitoring tools available, such as Prometheus and Grafana. Thus, I believe RHEL is an excellent choice for facilitating organizational growth and enabling smooth scaling without issues. I rate this solution 9 out of 10.

On-premises

We have our in-house applications. We have several edge applications at our store locations. There is an in-house written app that we host on a basic Linux VM. Additionally, we have a few on-premises installations at headquarters. One of our major applications is being rewritten to be hosted on a Linux server, so that's in the process of migrating.

Red Hat Enterprise Linux (RHEL) helps me with configuration management. It has become a standard in many ways. There's substantial support and different applications that we run on it. The available options for configuration, maintainability, and stability are valuable, and it's not a rapidly changing base that we're working with.

My favorite feature of Red Hat Enterprise Linux (RHEL) isn't narrowed down to one specific aspect. As someone who grew up using command line interfaces, the ability to access a command line and have the system at my fingertips is beneficial. There are multiple options and different ways to approach tasks with Linux, allowing for creativity in the process.

The command line feature of Red Hat Enterprise Linux (RHEL) specifically helps me find ways to address problems. If there's a bottleneck, something slowing us down, or a manual process that we're spending significant time with, I can determine ways to either script around it or use an Ansible playbook. Having these different tools at our disposal is particularly useful.

While I don't have an immediate answer, there may be ways to lighten up the underlying system. There are many components I haven't investigated, making it difficult to pinpoint specific areas. It has always been reliable, and I haven't encountered many major issues. I've been content with Red Hat since I started using it.

We don't use SELinux because it gets in the way too much. It's a good product if you have the time to devote to it. A lot of management is involved in it. We typically set it to notify rather than completely disabling it, though vendors often request reduced security settings during application setup. Regarding areas for improvement, I can suggest streamlining SELinux, which currently feels heavy-handed in its approach to security. It's a system that requires deep immersion to understand. While there's probably justification for its current implementation, making the security component less intimidating for users would be beneficial. This is a recurring observation, as many users working on Red Hat systems or Linux systems tend to disable SELinux because it becomes an obstacle. With proper knowledge and usage, it could be beneficial, but it's similar to training a wild dog - it can be loyal, but without proper training, it becomes an impediment.

I have been using Red Hat Enterprise Linux (RHEL) professionally since around 2011, though I've been using some form of it since the late '90s.

We haven't experienced many problems with downtime. Our operating systems have been consistently stable regarding uptime. Any downtime issues have been related to upstream factors, networking, and power infrastructure.

In terms of stability and reliability, Red Hat Enterprise Linux (RHEL) is very stable. I rarely recall having issues where the OS wouldn't boot up. Any stability issues have typically been hardware, network-related, or facility-related rather than OS-related.

Red Hat Enterprise Linux (RHEL) scales with the growing needs of my company very effectively. We implement it in any place where we can find a suitable application.

The customer service and technical support for Red Hat Enterprise Linux (RHEL) are very good. I would rate it approximately eight or nine out of ten. It has been particularly good recently. Though there were past instances where support initially took a hands-off approach due to gray areas in their support scope, which was disappointing, they ultimately delivered when crucial support was needed.

Positive

We are largely a Windows shop. I'm probably the only Linux person on the staff. We have legacy systems, including HP-UX and Stratus VOS, with some RHEL outliers that are being phased out. While Red Hat will likely absorb some of that capacity, many people coming from a Microsoft environment are bringing Windows .NET applications. We're currently evaluating Azure as a hosting platform, which is already in place but not actively used yet.

I've been involved in Red Hat Enterprise Linux upgrades and migrations since Red Hat Enterprise Linux 5. We still maintain one Red Hat Enterprise Linux 5 server due to legacy applications. We have successfully removed all Red Hat Enterprise Linux 6 installations and currently maintain a large base of Red Hat Enterprise Linux 7 at our store locations, which we're migrating from. We've implemented both Red Hat Enterprise Linux 8 and Red Hat Enterprise Linux 9, completing the entire cycle. We've been through all the versions. We don't do in-place upgrades or anything like that. We just rehost the applications, which is probably pretty typical. This is largely a VM-based environment.

I use Satellite combined with the Ansible automation platform for provisioning and patching. I implement kick-starting via Satellite for most systems, with Ansible handling the final configuration. As Red Hat Enterprise Linux 10 approaches, I'm interested in exploring image options to streamline the process, particularly regarding CIS benchmark compliance.

We are going to move to Red Hat Enterprise Linux 10. We've been pretty good about getting up to the latest version once it's available. It took us a while with Red Hat Enterprise Linux 7, but we jumped to Red Hat Enterprise Linux 8 fairly quickly. I had my process down, so with Red Hat Enterprise Linux 9, I got right on to it and rewrote my configuration. I'm hoping to streamline that to get Red Hat Enterprise Linux 10 up and going once it comes out. I'll have a new service based on that. Our footprint is shrinking a little bit because a lot of our apps are being rewritten in a Windows .NET environment. It's not going to be as big as it used to be, but we're still going to have Red Hat.

The biggest return on investment when using Red Hat Enterprise Linux (RHEL) is time. Time is a crucial factor, and attempting this level of automation with Windows would be challenging. While automation is possible with Windows, it comes naturally with Linux. Being able to transform common manual tasks that previously took all day into processes that take an hour, half an hour, or even less, demonstrates clear value.

Management handles much of the pricing, setup costs, and licensing for Red Hat Enterprise Linux (RHEL), though I receive many of the invoices. While it isn't inexpensive, it has proven to be a worthwhile investment. The virtualized environment has provided good value. Each of our Satellite locations has its own physical license, which adds complexity, but Red Hat and our partners have worked with us to secure competitive pricing.

My rating for Red Hat Enterprise Linux (RHEL) is 10 out of 10.

On-premises

I have experience with Red Hat Enterprise Linux (RHEL), using both the cloud-based and on-premises versions, with a focus on the on-premises deployment. As an infrastructure support engineer and senior manager, my main use cases include providing infrastructure for all applications and businesses. This encompasses user account management, application handling, and operating system requirements for each virtual machine. We are building and delivering products using Red Hat Enterprise Linux (RHEL), and we also utilize Red Hat Ansible Automation Platform and Red Hat Satellite for patching the operating system and other Red Hat applications.

We use a ton of operating systems in our environment. We have Red Hat flavors, CentOS, Ubuntu, and multiple Debian versions. I have previously used AIX and Windows servers, with multiple versions of Windows as well. We maintain diversity in operating system usage.

Recently, we purchased Red Hat Enterprise Linux (RHEL) with support on a host-based license model. We previously used a per-host-wise license structure, but we opted for the highest license option, which provides unlimited virtual machines per host. The total investment was approximately 1.2 million dollars for around 1,100 hosts.

The purpose of this engagement was to gather survey information regarding Red Hat products and Red Hat Enterprise Linux (RHEL) operating system. I understand this will provide better insight into how Red Hat Enterprise Linux (RHEL) effectively targets customer inquiries.

The pros of Red Hat Enterprise Linux (RHEL) in comparison to other solutions I have used include that in most performance aspects, Red Hat Enterprise Linux (RHEL) is very robust and active in terms of performance, operating system strength, security, and lightweight efficiency.

The best features in Red Hat Enterprise Linux (RHEL) include its open-source nature in terms of the Linux background and kernel. The enhancements and features offer various options with timely updates and security measures. You have multiple choices on how to control security and fix bugs. You can modify and tweak the kernel according to your convenience. If you need to perform automation of your own choice, modifications can be made to perform as per your requirements. This can be done in Red Hat Enterprise Linux (RHEL) or any Linux-based operating system, but Windows has a ton of limitations. Even for bug fixes in Windows, you cannot announce fixes to others globally. Red Hat Enterprise Linux (RHEL) has an open-source community for this purpose, and CentOS has similar benefits. For patching solutions, Red Hat Enterprise Linux (RHEL) has its own patching solution such as Satellite. There is also live patching available, including kernel live patching, which is an excellent option for minimal application downtime.

The most important security features in Red Hat Enterprise Linux (RHEL) include the ability to control login access with multiple layers of security, such as two-factor authentication. Key-based authentication is one of the best options, and two-factor authentication is also beneficial. You can disable the root user, so normal users will not see or have access to system-secured commands unless they have sudo access. The kernel is much more secure, and most viruses do not affect the Linux kernel because all things are treated as files without extensions, which reduces virus impact in that area. Although any operating system can be vulnerable, Linux is less vulnerable than others.

I did not explore Red Hat Insights much and do not have substantial knowledge about this feature.

Deployment is very easy and straightforward. I did not find any issues with it. Even with automation, it is very easy.

I would suggest that Red Hat Enterprise Linux (RHEL) improve the graphical user interface-based experience in a much better way. If you compare with most preferences, many people are more habituated with Windows. If Red Hat Enterprise Linux (RHEL) can improve the graphical user interface experience and gaming scope, it would benefit users. Windows handles gaming much better, but Red Hat Enterprise Linux (RHEL) is more focused on the enterprise edition and server support. If Red Hat Enterprise Linux (RHEL) improves the graphical user interface experience, it would be better for users in terms of costing and user experience.

Another suggestion concerns Red Hat Ansible Automation Platform support. I believe Red Hat should provide much better engineers who have greater experience with their product. Although they have knowledge bases and training programs, I feel that Indian engineers at Red Hat are not as effective or experienced with their own product. I have faced some challenges with support level in this area.

Regarding the centralized patching system, Red Hat Satellite should support other operating systems beyond Red Hat Enterprise Linux (RHEL). I have observed that Red Hat Satellite has limitations and only supports Red Hat Enterprise Linux (RHEL). Most organizations use multiple flavors of operating systems. Excluding Windows and considering only Linux operating systems such as Ubuntu, Debian, CentOS, or SUSE Linux, Red Hat Satellite should support these with a rollback option. If Red Hat Satellite includes support for other operating systems with guaranteed rollback functionality, customers would accept it very readily and would not even consider the price.

I have been using Red Hat Enterprise Linux (RHEL) for almost 11 years.

Red Hat Enterprise Linux (RHEL) is much more stable in comparison to other operating systems. In terms of failures, sometimes no responses come and occasionally the system hangs up. However, the reasons for these issues are not particularly based on the operating system itself. Stability issues depend on memory and other applications running on the system. I cannot say that issues occur because of Red Hat Enterprise Linux (RHEL) or Red Hat applications. I have not observed much issue or lagging from the operating system or Red Hat application perspective. We receive more than 99.99% uptime from the operating system perspective for Red Hat Enterprise Linux (RHEL).

Expansion is fine with no issues. The only limitation is that the XFS file system cannot be reduced. Any troubleshooting and expansion tasks are adopted smoothly.

In our environment, most of what we run is critical. Red Hat has their own service level agreement, and we have our technical account manager ready. Whenever there is any urgency, we connect with our technical account manager who helps us resolve the issue within our expected timeframe. It depends on the urgency, but when we request assistance, they fulfill it. Our experience has been very good with Red Hat Enterprise Linux (RHEL) compared to other operating systems and original equipment manufacturers.

For any downtime, whether it is a priority one, priority two, or priority three case, their response time is one hour. They usually respond before that timeframe. I have faced some issues with Red Hat Ansible Automation Platform support and did not see that much effectiveness, but regarding the operating system itself, the service has been very good. As I mentioned earlier, for kernel modification and hardening, Red Hat has provided good support.

Positive

I deployed Red Hat Enterprise Linux (RHEL) myself, and a third party also conducted deployments for us. I have my own hands-on experience in production environments with both manual and automation processes. We deployed Red Hat Enterprise Linux (RHEL) using Terraform and other third-party tools. I used AWS Lambda and many other tools to deploy Red Hat Enterprise Linux (RHEL) systems.

We purchased Red Hat Enterprise Linux (RHEL) directly from Red Hat through their verified vendors. Red Hat does not sell directly but works through their own verified vendors for purchases.

When you use the image builder, the custom image will be standardized and signed off by the original equipment manufacturer, which is Red Hat. When it is certified and signed off by Red Hat Enterprise Linux (RHEL), enterprises and auditors will accept it. If we create any custom images on our own, they will be standardized, but the image release will not be certified from the original equipment manufacturer. This can lead to many questions from auditors. However, when Red Hat signs off on the image, it is a good positive point to present to the auditor as evidence. My overall rating for this solution is 8 out of 10.

Red Hat Enterprise Linux (RHEL) basically runs the bank's apps as my main use case.

I like the feature Satellite the most because it has services to manage my multiple Linux servers.

Satellite has no parallel in the Linux distro world, especially for an enterprise, enabling me to manage my servers, patch them, create content, get them binaries, updated security updates, and all that. It makes it easier for admins and reduces the need for a lot of manpower, especially with Ansible that enables me to do configuration management of 20,000 Linux servers.

Red Hat Enterprise Linux (RHEL) scales with the growing needs of my organization very well as we are expanding ourselves.

Red Hat Enterprise Linux (RHEL) has helped mitigate downtime and lower risk because the servers can run for more than 300 days of uptime. I do have to reboot them for patching, but otherwise, they are a very stable operating system that doesn't crash for no reason. If I experience kernel panics, it often involves EDRs or agents such as CrowdStrike, but otherwise, it's very stable with proactive features. We had issues with CrowdStrike; they identified the issue with their kernel drivers that used to crash my OS and provided a patch to address it, so they take care of us.

The implementation had challenges like whenever we bring out new products, there's always one issue: Red Hat Enterprise Linux (RHEL)'s documentation is not complete. I have to really have an enterprise account because I get access to their support, which sorts me out since every environment is unique. It's not a cookie cutter; I would deploy RHEL 8 in a way different compared to a retail store. So when it gets to those niche deployments, they don't have anything documented. I really have to get hold of the support, saying, "Hey, I'm trying to do this. It's not working," and then they will give me a solution, but I would expect that a document would have solved that issue without raising a ticket. That's my only complaint.

The area for improvement in Red Hat Enterprise Linux (RHEL) is documentation. I don't have any other suggestions. I think it's just the documentation that needs improvement. Otherwise, technically, I don't have anything to suggest.

I have been using Red Hat Enterprise Linux (RHEL) for ten years.

I have experienced downtime or security incidents as a result of the solution when proper practices are not followed, especially if I am using any third-party security. You have to manage kernel options; otherwise, the base OS itself is very stable.

Red Hat Enterprise Linux (RHEL) scales with the growing needs of my organization very well as we are expanding ourselves.

I would evaluate customer service and technical support based on my experience. I felt naive about being a small enterprise versus a big enterprise, but the response time of tickets is consistent. I haven't seen a difference; I thought I would have a slower response being on a small account, but the speed of our calls is the same.

Positive

I considered other solutions before choosing Red Hat Enterprise Linux (RHEL), but it was a default choice for us. I see that they have expanded; earlier, it was just a bare-metal OS and not an ecosystem, but now they are in OpenShift, providing Kubernetes and everything.

I wasn't using another solution to address my needs prior to adopting it.

The upgrade or migration is straightforward if I have applications that depend less on what the OS is, but in our case, it was not that simple. We had a business requirement, so we had to shut down the older one, provision a new one, and move everything.

I have seen ROI from using Red Hat Enterprise Linux (RHEL) in terms of uptime itself.

My experience with pricing, setup, and cost of the solution is that it's a service based on how many cores, not sockets.

My deployment model for Red Hat Enterprise Linux (RHEL) is on-premises, but I am just starting off with cloud.

For security requirements in the cloud, I don't do SELinux; I just depend on my ACLs because my servers are not internet-facing. We trust Red Hat Enterprise Linux (RHEL) with the binaries, with nothing on the base OS such as firewalls or SELinux.

I use AWS and Azure as my cloud providers.

I manage my Red Hat Enterprise Linux (RHEL) systems for security, updates, and patches with Red Hat Satellite, which makes it very easy.

I have been involved in upgrades from RHEL 6 to 7 and from 7 to 8.

My assessment of Red Hat Enterprise Linux (RHEL)'s FIPS and security compliance features is that it's the best in the industry. They have FIPS, which I think is more for federal clients, and although I haven't used it, I know they offer it by default on their Linux.

My upgrade and migration plans are to always try to stay on the current version all the time, unless there's a legacy application. Any apps I manage are always on the latest Red Hat release, and we keep migrating them as Red Hat provides the first-ever release out, which is a requirement for our Satellite to support the latest version.

The area for improvement in Red Hat Enterprise Linux (RHEL) is documentation.

I would assess the knowledge base offered by Red Hat Enterprise Linux (RHEL) as paywalled, so if you don't pay for it, you wouldn't be able to access their system. The KB is pretty good, but you need to have a Red Hat account.

My advice to a company considering this solution is to go for it. It is supported by enterprise support from Red Hat, which I don't think any other enterprise can offer. While I know Canonical does it for Ubuntu, SUSE is another good option; however, the adoption is not there, and you don't have a lot of sysadmins. Red Hat Enterprise Linux (RHEL) is a bible due to the abundance of resources in the market. I would rate this solution a 10.

I am a system administrator using Red Hat Enterprise Linux (RHEL) for handling applications and databases. The machines I manage handle applications and databases, along with some JBoss.

Ever since IBM has come into the picture, Red Hat and Ansible have been developed very well. The reporting and workflows have become very good.

Among all Linux flavors in the market, Red Hat Enterprise Linux (RHEL) has a very high-level support developer team, which is important for our critical systems. We need a solid platform that provides one spot for vulnerability fixes, unlike Ubuntu, CentOS, etc. They only provide low levels of support. 

The management is fine. We're doing regular patches with Satellite. We're happy with it. It is manageable.

We can manage a hybrid cloud environment. Red Hat doesn't come fully into our picture with our environment since we're using the Amazon environment and VMware for virtual machines. Red Hat is just an OS, and it is easy to set it anywhere with no issues. 

They should be more generous in providing documentation in a friendlier way. The Red Hat Enterprise Linux (RHEL) documentation is good, yet not as good as other products such as IBM. Oracle, on the other hand, is the worst; they are very limited in sharing their documentation with engineers.

The Asian support could use improvement.

I have total experience in Unix/Linux of 25 years, which includes five years of Solaris, IBM HP-UX, IBM AIX, and HP-UX, along with Sun Solaris, while the other 15 years is with Linux.

We never faced any issues with stability, and we never faced any limitations.

We never faced any issues with scalability, and we never faced any limitations. For our company,  it is more than enough. I'd rate scalability nine or ten out of ten.

Red Hat support is good, actually. It depends on the region. I have dealt with several regions including Asia, Middle East, and Europe. The majority of European support is excellent. I would give it nine to ten out of ten. In the Middle East, it is between seven to eight out of ten, while in Asia, very rarely do we get nine or eight out of ten. I'd rate it five out of ten there.

Positive

We have moved to another technology since we are no longer working with Dell EMC or Networker. With Veeam, we are currently working for that vendor. We are using Veeam exclusively nowadays.

We're working with 80% Linux, 10% Unbuntu, 10% Oracle.

The initial setup was very simple. 

Management is fine, since we have the Red Hat Satellite, which allows us to do regular up-to-date patches. We are happy with the Red Hat Satellite. It is manageable.

I am handling the storage, backup, and operating systems of Linux flavors personally.

This question of ROI would be unfair for me to answer. We are not using the full range of Red Hat Enterprise Linux (RHEL) products and are depending on other things. However, Ansible is doing very well with the new version, and in terms of workflow, it is easy to manage. Ansible has been performing very well, especially after IBM acquired Red Hat. IBM has enhanced Red Hat and Ansible very well, as they are famous for reporting and managing workflows.

The pricing is very simple. Compared to something like IBM, Red Hat is the cheapest.

Without something to compare it with other than Red Hat Enterprise Linux (RHEL), I cannot do a direct comparison. However, compared to Unix products such as Oracle Linux or IBM, Red Hat Enterprise Linux (RHEL) is less expensive.

Regarding Linux Image Builder and system roles, I have tried both, however, cannot recall which one I downloaded. The last time I built it was more than five months ago. 

I rate Red Hat Enterprise Linux (RHEL) nine out of ten.

Hybrid Cloud

My main use cases for Red Hat Enterprise Linux (RHEL) include maintaining a stack of servers where we perform monitoring, provisioning, certificate provisioning, and checking patch status across the servers.

The most valuable feature within my systems is Satellite. The features that I appreciate most on a daily or on-demand basis are those provided by Satellite. This feature benefits my organization by providing provisioning for every instance, as we have approximately 100 instances under Red Hat and another 20 under Ubuntu. Currently, we use a single user interface to control them all.

Red Hat Enterprise Linux (RHEL) could be improved by providing end-to-end support for customers because we are seeing that it is more distributed. For all the Red Hat services, we use Satellite, but other services are on the cloud, and some things are hybrid cloud. This means we have multiple platforms to monitor each time. Another area for improvement is the false positives. We have the Red Hat alarm system, and it is good, but it just fires and reports, sending an email every night for us to check our duties. This is really unpleasant for us.

I have been using Red Hat Enterprise Linux (RHEL) for four years.

I have experienced downtime, crashes, or performance issues seldomly. It is good and can solve 80% of problems. Sometimes I seek consultants for help to rebuild the model or to see what the root cause is. Sometimes this problem occurs many times, requiring someone to show up and thoroughly investigate it.

Red Hat Enterprise Linux (RHEL) scales with the growing needs of my organization as it is stable, and I see that with Android development. However, I think it has only increased our usage by 3%. I think it is stable and we will not decommission it, but we still compare the benefits of cloud solutions and the Red Hat solution. I have expanded usage on Red Hat because Ubuntu is an open licensing and very unmanageable, so we are trying to reallocate resources to Red Hat.

I evaluate customer service and technical support as great. My own company has a consultant who is very timely in dedicating support to our services. We can call at any time to seek urgent consultant services. Overall, it is good. We find that rebooting or rebuilding is tough for us. We want to make sure that the service is ready to use, but for some unfortunate situations that happen, we seek 24-hour support to solve the problem as soon as possible. Every second that passes represents a loss for us.

Positive

Prior to adopting Red Hat Enterprise Linux (RHEL), we were using Ubuntu, and now it depends on what this product and what this pipeline built initially. If they used Ubuntu at the beginning of the startup, we just use it. We make sure they are up, make sure they are stable, and do not care about anything else. If they use Red Hat, we just keep running with it.

I would describe my experience with deploying Red Hat Enterprise Linux (RHEL) as manageable. It is not out of control. For every server instance, we get notified, and I get an alarm at a very early time, so we can manage to replicate it. This instance has some broken files, which is helpful for the developer to debug and understand it.

When I was deploying Red Hat Enterprise Linux (RHEL), the deployment, particularly the hotfixes, is a real challenge. We have some big instances with the front-end code and back-end code in one service. We have to do this really quickly to deploy hotfixes and implement new features. We need to make sure that the code is consistent across all the services at that time. We can do the Ansible playbook, which is a very good template that we can reuse to replicate the problem.

I have been involved in Red Hat Enterprise Linux (RHEL) upgrades or migrations, as for version upgrades, I have been involved. We still have some Red Hat Linux consultants who support us in doing the migration. I think it is helpful. The seamlessness of the process with the consultant depends on the service difficulty because sometimes everything is hard to ensure that it is correct. It depends on the project size.

I do not touch the pricing and the cost of the solution, but I think compared to some cloud costs, it is good because our team is relying on that. We just make sure that the service is up.

The other solutions I considered before selecting Red Hat Enterprise Linux (RHEL) are that in our company, we have two choices: one is Red Hat and one is Ubuntu.

My security requirements and considerations in choosing Red Hat Enterprise Linux (RHEL) include that this is our manager, and we want to have some endpoints tracking any attack and detecting the status of anything broken. My assessment of Red Hat Enterprise Linux (RHEL)'s built-in security and compliance features is that right now, I think it is simply risk reduction. I am just maintaining it. For maintaining compliance, I can say that the first priority is to keep it safe. The second priority is to keep it up. We make sure they are okay, available to use, and available to maintain. For any other new features, we do not require that. We just make sure of these two things. Beyond this point, we are seeking some cloud help.

My upgrade and migration plans to stay current with Red Hat Enterprise Linux (RHEL) are that we need to upgrade it every year, or just when you have a vulnerability, you need to come up with it and upgrade it. From my perspective, we are not doing really timely upgrading because we do not want to disturb the current pipelines.

For the knowledge base offered by Red Hat, such as the Confluence page, it is helpful. For Red Hat Enterprise Linux (RHEL), the knowledge base is helpful. I try to look up and check many of those pages, and they give me detailed ideas on how to implement the system. Sometimes the problem is really unique, and I can get help or try to get support to formalize some questions and help us understand the solutions. I still need to seek a senior consultant's help on migration. Some documentation is outdated.

My advice to other organizations considering Red Hat Enterprise Linux (RHEL) is that if you use Java, you should use it. If you have many massive servers to maintain, a Red Hat solution with the pipeline and Satellite is beneficial. If you have some old legacy systems, you do not have to set up new labor on monitoring. I give this product an overall rating of 8 out of 10.

My main use cases for Red Hat Enterprise Linux (RHEL) are for the core banking systems. It is a much more stable OS than other competitor operating systems, especially with Databases.
Most banks in Iraq use Linux, whether it is free like CentOS for a UAT environment or enterprise like Red Hat.

The Red Hat Satellite makes my life much easier when it comes to managing my Red Hat Enterprise Linux (RHEL) systems for provisioning and patching. Before few years ago, each server had to have internet access to make updates or deployments. After joining the Satellite, it's just one push, and all the patching is done. And all the datacentres prohibit having external access. So we can create a local repository at our Red Hat Satellite and then push it to other servers, with the option of choosing a specific version to push for all servers.

Furthermore, the IDM, which is FreeIPA, is great. I appreciate how it makes the management much easier for me, even when managing more than 500 users same time. Like when someone leaves the company or someone joins, it's easier for me to onboard or respond to other things. It makes my system more secure by monitoring all the user's activity, which is another important point since no one can have direct access to the server without being authenticated and authorised by the IDM.

The Red Hat Satellite makes my life much easier when it comes to managing my Red Hat Enterprise Linux (RHEL) systems for provisioning and patching. At first, we had to access each server to make updates or deployments. After joining the Satellite, it's just one push, and all the patching is done. All this distribution also helps us as we use it on-prem, and all the data centers prohibit external access. So we can create a local registry at our Red Hat Satellite and then push it to other servers without issues regarding version changes.

I am a big fan of Red Hat Enterprise Linux (RHEL) built-in security features, which simplify risk reduction and maintaining compliance, and I would just say we achieve 99% success. I remember a few years ago when there was a zero-day attack. Red Hat was the fastest company to respond. We found out about it at six o'clock PM, and the next day at eight AM, they had some fixes and pushed updates. So we could respond directly and implement the fixes. Any security breach with Red Hat, I do not want to speak about others, since we face worse responses from other companies.

My upgrade or migration plans to stay current involve understanding the concept of OpenShift, which has not yet become very popular in Iraq. I try to keep pushing the client to understand the concept of containers and other things. It will take some time, however, it's a good feature to move ahead with OpenShift containerization. Even with the Central Bank regulation, we have to remain on-prem, thus OpenShift supports this point and offers a flexible solution. Red Hat Enterprise Linux (RHEL) has helped me mitigate downtime and lower risks by about 80%.

I am a big fan of Red Hat Enterprise Linux (RHEL) built-in security features, which simplify risk reduction and maintaining compliance, and I would just say we achieve 90% success. I remember a few years ago when there was a zero-day attack. Red Hat was the fastest company to respond. They had some fixes and pushed updates in few hours from discovering the security breach. So we could respond directly and implement the fixes. I don't like to mention the other competitors, since we face worse responses from other companies.

My upgrade or migration plans to stay current involve understanding the concept of OpenShift, which has not yet become very popular in Iraq. I try to keep pushing the client to understand the concept of containers and other things. It will take some time, however, it's a good feature to move ahead with OpenShift containerization. Even with the Central Bank of Iraq regulation, we have to remain on-prem, thus OpenShift supports this point and offers a flexible solution. Red Hat Enterprise Linux (RHEL) has helped me mitigate downtime and lower risks by about 80%.

I can't pinpoint something specific to improve Red Hat Enterprise Linux (RHEL). I feel they are doing good. I haven't thought much about what they could enhance to become even better for me.

Currently, I manage an issue not related to the OS. It's more about how to purchase vouchers or training from them. Unfortunately, any MasterCard or Visa card issued by a bank inside Iraq is blocked by Red Hat without a clear reason.

While other vendors like Cisco, Microsoft, IBM, VMware, Veeam, Nutanix, etc., we can purchase learning and vouchers directly without any issue. Only Red Hat it's blocked, so to solve this, I have to travel to Dubai and buy it outside the country. This is a significant issue for me and all Red Haters in Iraq, and that's why I also develop myself with non-official content and stopped pursuing their certification since I must travel each time I need it.

I have been using Red Hat Enterprise Linux (RHEL) for about six years.

Regarding stability and reliability, I didn't face any issues with that. It's 99%. Any issue I face with it is due to some mistake from a colleague or something pushed the wrong script, yet I haven't faced a sudden crash.

Red Hat Enterprise Linux (RHEL) scales to my company's growing needs very effectively; I didn't face any issues with scalability. Before working in my current company (Red Hat partner), I was a work at a payment gateway company. And we made a successful story by scaling out our datacenter and migrating the version from 6 to 8 without any major issues. Also, we did clustering with Enterprise Linux and other things, and all scalability was good, just requires specific knowledge. That said, it's manageable.

In my six years working with Red Hat, I only remember opening cases three times since the technical documentation on the Red Hat site is so comprehensive that if you carefully check it, you often won't need further assistance.

The support itself is satisfactory, and they solved my issues. They understood my concerns about the side effects of some changes, however, and they were perfect in their response.

Positive

I did consider other solutions before or while using Red Hat Enterprise Linux (RHEL), including Ubuntu, CentOS, and Debian. I am a big fan of Red Hat. This is why I will always choose them. When you love something that much, you just stick with it. That's why I will consistently recommend it to clients as a Red Hat partner.

For the first time, it was a little bit complicated. However, once you know how it works, it's very easy.

My experience with the pricing, setup costs, and licensing for Red Hat Enterprise Linux (RHEL) it's a little bit higher. I suggest that if they could make the price more affordable, it would be great. Some clients are just startups and when opening a budget with Red Hat, it doesn't cover what they need. Perhaps they could create a specific version for startup companies or offer discounts for first-time users.

On a scale of one to ten, I rate Red Hat Enterprise Linux (RHEL) a ten out of ten.

On-premises

Other

My main use cases for Red Hat Enterprise Linux (RHEL) are mainly all of our business applications, as they all run on RHEL.

Red Hat Enterprise Linux (RHEL) helps me solve pain points related to reliability, stability, and security, mainly. 

Feature-wise, what I appreciate the most about Red Hat Enterprise Linux (RHEL) is security; it's much more secure, and I don't have to patch it that much. For us, security is a very key aspect of our operations, especially since we are even more security-conscious due to what happened with us in the past, so having Red Hat Enterprise Linux (RHEL) in our environment makes us much more confident. When we deploy new applications, it's RHEL by default; we don't even consider another operating system right now since it keeps our environment secure and our business stable.

Security requirements are always a consideration in choosing Red Hat Enterprise Linux (RHEL) for the cloud since it is much more secure than other operating systems and has a proven track record of being compliant and secure for many years.

When it comes to managing my Red Hat Enterprise Linux (RHEL) systems for provisioning and patching, it's about 50% manual and 50% automated, and we are currently starting a project with Ansible to fully automate it end-to-end. Right now, it's all semi-automated, and we want to make it fully automated.

For us, Red Hat Enterprise Linux (RHEL) supports our hybrid cloud strategy mainly through seamless migrations from on-premise to cloud, which has been really helpful. Frankly, we don't use the knowledge base offered by Red Hat Enterprise Linux (RHEL) that much; our team prefers to get help from Red Hat support directly.

One of the suggestions I have for improving Red Hat Enterprise Linux (RHEL) is finding better solutions around domain authentication, as we are facing several issues with our current methods.

I have been using Red Hat Enterprise Linux (RHEL) for 20 years.

The stability and reliability of Red Hat Enterprise Linux (RHEL) has been excellent for us; aside from a couple of upgrade challenges, we generally don't face any issues during a normal business day.

Red Hat Enterprise Linux (RHEL) scales with my company's growing needs, as we are increasing our footprint in both on-premise and cloud, with all new deployments on Linux without any scaling issues.

In terms of customer service and technical support for Red Hat Enterprise Linux (RHEL), it has been good in general, although we have recently faced some challenges around domain authentication where support is lacking. 

At this point, I would rate customer service and technical support a solid eight out of ten due to recent issues; I would have given a nine otherwise.

Positive

We deploy Red Hat Enterprise Linux (RHEL) both in the cloud and on-premise.

The deployment has been great. I've never had any issues either patching or upgrading it. We are right now on Red Hat 9. I saw that Red Hat 10 has been announced. Our team has been able to manage the entire life cycle from starting at Red Hat 4 until now. It has not been a problem at all.

I am involved in Red Hat Enterprise Linux (RHEL) upgrades all the time; we are currently in the process of upgrading from Red Hat 8 to 9 for all of our environments. Upgrading Red Hat Enterprise Linux (RHEL) has its challenges; we had a couple of hiccups in a couple of cases. Overall, about 95% of the use cases have been issue-free, with just 5% of cases occasionally encountering problems.

The biggest return on investment for me when using Red Hat Enterprise Linux (RHEL) comes from security, as we experience fewer incidents, more stability, and less business impact, without outages resulting in revenue loss.

My experience with the pricing, setup cost, and licensing of Red Hat Enterprise Linux (RHEL) has been good; the licensing isn't very expensive compared to other products we're using.

While using Red Hat Enterprise Linux (RHEL), we still consider other solutions as we do have other operating systems, however, for business-critical applications, we usually prioritize RHEL.

On a scale of one to ten, I would rate Red Hat Enterprise Linux (RHEL) a nine.

Hybrid Cloud