Red Hat Enterprise Linux (RHEL) Reviews

We are deploying Red Hat Enterprise Linux as our primary Linux OS, and we are using Ansible for some automation initiatives. Our use cases are around centralization.

We have a supported product. We are at the beginning of building a relationship with Red Hat similar to the one we have with Microsoft, Cisco, and others. It is to standardize the quality, supported version, and company. I am leading this project, and I believe Red Hat is the one.

We have built a hybrid environment. Most of it is on-prem, but we also have Azure, so we have both cloud and on-prem environments. Red Hat Enterprise Linux is helpful for patch and vulnerability management. There have been a lot of security initiatives around Windows and tightening it up, but our Linux environment was not standardized. Red Hat Enterprise Linux standardizes it. With the combination of Insights, it aligns with Windows and other security initiatives.

Red Hat Enterprise Linux has not yet enabled us to centralize development. It is too early for that. I am not very familiar with OpenShift, but with OpenShift, Kubernetes containers, and some of those capabilities, DevOps will become more integrated with Red Hat and its products in the future.

Red Hat Enterprise Linux’s built-in security features seem very good when it comes to risk reduction, business continuity, and maintaining compliance. One thing that helps is the catalog of preexisting playbooks provided by Red Hat around security. It helps you ramp up on security. It aligns it with what an IT person on the Windows side already knows to look for, such as firewalls, setting up permissions, etc. They have playbooks for Active Directory integration, security initiatives, and limiting the firewall. Building out some of the playbooks that Red Hat has in those areas was helpful in getting a good security posture for those systems.

Ansible is going to make the portability of applications and containers happen for us. The OS is important, but our ability to use Ansible and deploy via a cloud or automate via a cloud or on-prem would accomplish that.

Red Hat Insights is valuable. There is patch and vulnerability management. It is similar to what you would see with SCCM. I have a single pane of glass interface. I can approve the patches and vulnerabilities, and hopefully, between Satellite and Ansible, we can automate that process.

I am looking for training. I am a Windows guy who accidentally became a Linux guy. You volunteer a few times, and you are the guy. Right now, I am looking for training and ramping up to be able to support their products, so professional services are key. There are things like Lightspeed with IBM Watson. I do not know YAML very well, so it is going to be integral for me to create playbooks at the very beginning and be able to use the AI tools. If I say, "How do I open a port on this Cisco router?", the AI tools are going to give me the YAML code. In spite of not being a Linux guy or a great coder, I can use those tools to ramp up very quickly. Making Lightspeed a part of Red Hat deployment initiatives tremendously helps with customers' success. It gives them that extra tool. Right now, it is being sold separately as a subscription. If they could integrate that capability, people would not have to go use ChatGPT and other tools. They could use that as a part of it. It would just align things with Red Hat, so one area they can improve on is the approach to customer success for new deployments.

Red Hat Insights are instrumental in identifying vulnerabilities. I am still learning, but my understanding is that it is not directly connected to your environment to deploy a patch or vulnerability fix. It is going to give a YAML playbook to do that. It does not actually execute it. On the Windows side, I have an approval process on the server where I can say, "Deploy this patch." I thought of Insights along the same lines where I can just approve things, and then based on some backend configuration, it will implement them using Ansible, Satellite, and on-premises Ansible. It seems disconnected right now. It might not be, but to me, there seems to be a gap there. I love Insights, and I want to fully automate that approval process. This could be a point for improvement if it does not already do that.

Another area of improvement is Red Hat expressing a return on investment better. I do not know if they have determined a lot of that. I have always assumed that I could go with an open-source OS in a less expensive manner than Windows or something else. My impression is that there would be less cost, but I do not know that for certain. Red Hat building out some of that ROI on different products would be beneficial to their sales effort.

We are a brand new customer.

It is more stable than the wild west environment that I have been in. There is standardization. It is stable by standardizing.

So far, its scalability has been good. Once I get a good image built, I will get some workflows built into Ansible. I will have that process all the way down to the help desk. We will be entering variables and kicking out systems all day.

We have been using it minimally. We have about 15% Linux environment with lots of flavors. Red Hat Enterprise Linux is what we are centralizing on from now on, so we are going to do a conversion of all those. We have a new standard going forward. We have about 15% Linux systems, which would amount to about 150 systems throughout North America. It is a small footprint.

I have not had to call them much, so I do not have a good handle on support from Red Hat. Everybody gets at least a C or a five, but I am optimistic. It is going to be good. I would give them at least a seven out of ten.

Prior to Red Hat Enterprise Linux, it was CentOS and others. CentOS was free. It was whatever was available or the developers or applications guys were familiar with.

We switched to Red Hat Enterprise Linux for centralization, to be supported, and for patching and vulnerabilities.

Most of the things that I am deploying or replacing are on-prem and on Azure cloud. It is 50/50.

The deployment was very easy. They have a great and user-friendly installation process with 9.x and above. However, just being new to it and having a security hat on, I still struggle with what should and should not be installed on the base image. It is a learning curve for me, but using the interface has been great. I was able to join Active Directory and all those things.

CDW is handling our professional services and our training, which is a separate purchase. Its initial rollout is with CDW.

We have not yet seen an ROI.

It is expensive. Everything is. I was happy to get a three-year Red Hat Enterprise Linux contract for our initial rollout. 

It is less expensive than other solutions. It is a growing company.

It is called Microsoft ARC. It now facilitates patches for Linux, but it did not include certain things. For me, there was much more benefit outside of just patching by going with Red Hat Enterprise Linux and Ansible.

I am not yet certain about Red Hat Insights' vulnerability alerts and targeted guidance. We are at the beginning. We are just adding systems. I have not set those alerts up if they exist. I assume there are some. I am also going to evaluate how accurate the vulnerability and patching information is because we have other security products that are looking at the same things on the Windows side, and they have already identified many of the vulnerabilities. As a new customer, I want to make sure that if our other system says something is a vulnerability, Red Hat Insights also says that it is a vulnerability. I want to feel confident in the vulnerabilities that I am getting from Red Hat Insights. I want to make sure that other products are also scanning for the same thing. I suspect it is.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would recommend going for Red Hat Enterprise Linux. I cannot think of another OS that can match this.

I will start off with an optimistic ten, and I will rate Red Hat Enterprise Linux a ten out of ten.

We use Red Hat Enterprise Linux primarily for our entire group because most of our applications are based on Linux.

Red Hat Enterprise Linux has robust built-in security features.

It has an extensive knowledge base.

We used to patch our systems manually, and now we use Red Hat Satellite to manage the patching of our systems.

Red Hat Enterprise Linux provides a good way to manage our OS.

It has enhanced both our uptime and security. The system's stability has eliminated any noticeable security issues.

Red Hat Enterprise Linux has enabled us to achieve security standards certification, which has allowed us to maintain business operations without interruption.

Red Hat Enterprise Linux is a stable and supported platform with valuable built-in security features that help reduce risk and maintain compliance.

The cost of Red Hat Enterprise Linux is a bit high. 

Red Hat Enterprise Linux's support could be improved by offering human support in addition to their documentation. While their documentation is helpful, it can be frustrating to be referred to it instead of receiving direct assistance from a support representative.

I have been using Red Hat Enterprise Linux for two years.

Red Hat Enterprise Linux is stable overall.

Red Hat Enterprise Linux is scalable.

Red Hat's support is generally good, but their response time and overall competence could be improved. Occasionally, we are referred to their documents when requesting assistance, which can be frustrating.

Positive

Red Hat Enterprise Linux has a yearly subscription cost for the licensing that includes maintenance and support.

We evaluated Microsoft Windows Server, Ubuntu Server, and Red Hat Enterprise Linux before ultimately choosing Red Hat Enterprise Linux.

I would rate Red Hat Enterprise Linux nine out of ten.

I recommend Red Hat Enterprise Linux for its support and stability.

Our banking applications, primarily those focused on transactional data services, operate on Red Hat Enterprise Linux.

We run our workloads on Red Hat Enterprise Linux due to its compliance and long support cycle.

Red Hat Enterprise Linux has enabled us to centralize development by providing a standardized image that we customize for developer laptops, developer environments, virtual machines, and production machines.

Our containerization projects run on OpenShift, a virtualized platform based on Red Hat Enterprise Linux, where we deploy and manage our workloads and applications.

Red Hat Enterprise Linux is a high-performing operating system that effectively supports our business-critical operations, including high-latency, high-throughput applications essential for transaction services.

Red Hat Enterprise Linux has robust built-in security features that effectively reduce risk in our environment.

Red Hat Enterprise Linux significantly contributes to our business continuity and compliance efforts by inherently supporting various compliance standards, including PCI and others. This built-in compliance functionality is a major advantage, as it simplifies the process of meeting regulatory requirements and provides robust evidence for audits. Ultimately, Red Hat Enterprise Linux streamlines our compliance procedures and strengthens our overall security posture.

The Red Hat Enterprise Linux portfolio helps reduce our TCO.

Red Hat Enterprise Linux provides a strong foundation for compliance and offers extended support, which is particularly valuable for critical upgrades and assistance.

To enhance Red Hat Enterprise Linux, I would like to see more focus on improving performance and tools such as compilers.

I have been using Red Hat Enterprise Linux for almost ten years.

Red Hat Enterprise Linux offers high performance for our business-critical operations, especially for high-latency throughput applications that are critical for transaction services.

Red Hat Enterprise Linux is flexible, and we always get support from the team if something is not working.

The customer support and technical service from Red Hat is good. When we needed support, such as for Java 21, we received early access. However, it's rarely the case that we need support.

Positive

The most significant return on investment is the long-term support, as we don't need to worry about support over an extended period. It ensures the continuation of service.

Red Hat Enterprise Linux licensing is not cheap, but it is worth it, especially considering the compliance and support it provides.

I would rate Red Hat Enterprise Linux nine out of ten.

If you're considering a third-party Linux OS, try Red Hat Enterprise Linux. It offers a free subscription for developers, and if it suits your needs, you can easily transition to the production-ready Red Hat Enterprise Linux nine.

Most of our tech applications are based on Red Hat Enterprise Linux.

We chose Red Hat Enterprise Linux for most of our workloads and applications because it is an enterprise-grade operating system with regular security patches, reliable support, and a guarantee against hacking. Using a different OS would leave us vulnerable to security risks and complicate upgrades.

Currently, 70 percent of our Red Hat Enterprise Linux environment is deployed on-premises, while the remaining 30 percent resides in the cloud.

We utilize Ansible to automate the deployment of numerous Red Hat Enterprise Linux modules. This centralized approach, managed by a single Ansible engine, streamlines our development process.

Red Hat Enterprise Linux performs well for our business critical applications.

Red Hat Enterprise Linux's built-in security features satisfy our security requirements.

Red Hat mitigates risk by rapidly releasing patches for identified vulnerabilities, which is crucial for mission-critical applications.

It offers stability that enhances business continuity, simplifying upgrades, even for minor releases. Its compatibility with OpenSCAP, which provides profiles for various compliance benchmarks, streamlines compliance testing.

Red Hat Enterprise Linux provides regular security patches and proper support, allowing me to focus more on application management than worrying about the operating system.

It helped us avoid emergencies caused by security issues. The CVE reporting and knowledge base are valuable resources.

Red Hat Insights provides the tools for proactive environment management by identifying potential vulnerabilities, such as CVEs before they become a problem. This allows for advanced knowledge of system vulnerabilities and provides specific remediation guidance, which is more efficient than relying on regular scans.

Red Hat Enterprise Linux has helped reduce our total cost of ownership.

Red Hat Enterprise Linux is an enterprise-grade solution where we receive regular security patches and proper support.

Red Hat Enterprise Linux was not used for containerization due to its mutable nature, unlike CoreOS, a lightweight and immutable Red Hat Enterprise Linux variant designed explicitly for containerization and optimized for running authorization.

I am testing AI workloads, and I'm not sure if Red Hat Enterprise Linux is fully equipped. It might not accommodate AI workloads as effectively as needed.

Some Red Hat applications, such as Ansible for automation, are considerably more expensive than the average open-source solution.

I have been using Red Hat Enterprise Linux for 16 years.

Red Hat Enterprise Linux is stable, and I have not encountered issues compared to other applications.

Red Hat Enterprise Linux is scalable.

Red Hat's stability has meant I haven't needed their support for years, but when I did contact them previously, their response was quite fast. While their support for OpenShift is acceptable, I do have some concerns about it.

Positive

A stable OS allows me to focus more on applications, lowering the cost of managing the infrastructure.

Red Hat is stable, and we always opt for the lower-tier subscription, which is affordable. It doesn't have unexpected issues that require a premium subscription.

I would rate Red Hat Enterprise Linux nine out of ten.

It is important to assess the risk and use case before choosing a third-party Linux OS. For mission-critical applications, Red Hat Enterprise Linux provides insights and rich features like the patching cycle.

I work on SAP HANA, which is on Red Hat Enterprise Linux.

Red Hat Enterprise Linux has a good support portal that I rely on.

The system rules are helpful for segregation of duties, as they provide us with more feasible access to the system, allowing us to register it accordingly.

We immediately see the benefits of Red Hat Enterprise Linux.

From an administrative perspective, the cloud platform is the best because we don't have to wait long. It's a portal, so we can access whatever we want through it, whether the Azure portal or the AWS portal; we click, and it'll purchase it for us. Some deployments take 30 to 40 minutes. But in most cases, especially for small services, it's just a few seconds to three minutes. From a business perspective, the pay-as-you-go concept is where we only pay for what we use. So those are the two things I like most about the cloud version of Red Hat Enterprise Linux.

Using Red Hat Enterprise Linux on the cloud can become costly over the long term.

I have been using Red Hat Enterprise Linux for six years.

Red Hat Enterprise Linux on the cloud is stable with a 99.9 percent uptime. Regional redundancies are used to ensure data accessibility.

The initial deployment was a little challenging until I became familiar with the solution through the portal. We did encounter a handshaking issue with Azure that required submitting a ticket to Microsoft, but otherwise, the process went smoothly. A team of four were involved in the deployment.

The implementation was completed in-house.

I would rate Red Hat Enterprise Linux eight out of ten.

We have to apply patches weekly, monthly, or quarterly, depending on their purpose.

We had no concerns about using Red Hat Enterprise Linux in the cloud because both AWS and Azure supported it, and they provided support if needed.

Red Hat Enterprise Linux (RHEL) is just a piece of an operating system for my company, and what we need the most is STIG compliance because we have a lot of different customers.

Red Hat Enterprise Linux (RHEL) has helped my company since, with it, we have gotten more customers. Now, our company can say upfront that we use Red Hat and are STIG compliant while also being security-focused, which really helps open up the door to people who want to get their stuff done.

The most valuable feature of the solution is its good integration with Ansible.

Red Hat Enterprise Linux has not helped centralize development in our company, especially since we deal with unique use cases in our organization. My company still develops locally on CentOS, but once our company actually completes the product for our customer, it gets shipped somewhere else and we can't centralize things since we don't have that much time to spare owing to which we stay disconnected after the aforementioned process.

My company plans to use the product for containerization projects, especially since we are in the process of converting to Kubernetes.

Based on my assessment of the the built-in security features when it comes to areas like risk reduction, business continuity, and compliance, I would say that I am a big fan of the tool.

In terms of the portability of applications and containers built on Red Hat Enterprise Linux (RHEL) to keep our organization agile, it has been pretty good since all the containers have been very portable without having to deal with any environmental issues.

If I had to give a suggestion to a colleague who is looking at open-source cloud-based operating systems for Linux instead of Red Hat Enterprise Linux (RHEL), I would say that one should look at AlmaLinux since it is the closest thing one can get to Red Hat.

The product's deployment model is usually in a single data center, and it consists of one machine at a time. Red Hat Enterprise Linux (RHEL) does not use a public cloud.

The documentation is an area of concern where improvements are required. Sometimes, I go to look at stuff in the tool's documentation to see how to configure something, and it doesn't make any sense. The tool's documentation is written by someone who already knows how it works for those who need to learn how it works. Everything else in the documentation is really good, though. I would describe the documentation as a kind of a hit or miss.

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

It is a scalable solution.

I would like to expand the use of the product in the future, but our company's business model is contract-based and very slow, which makes it difficult to work with Red Hat Enterprise Linux (RHEL).

As per my evaluation of the technical support offered by the product, I would consider the support services offered to be at a 50-50 rate since everything really depends on who you get to talk to from the support team. Some of the people from the product's support team to whom we reached out didn't understand our use cases or our problems, so they couldn't help us at all. Some of the support staff members who understood what our company meant when it came to the issues associated with the product were able to help us in 30 seconds. My colleagues who contacted the product's support team were satisfied with the technical team's services. I rate the technical support a six out of ten.

Neutral

In my company, we used to use CentOS. Now that CentOS has reached the end of life phase, it doesn't meet our company's needs, so we transitioned to Red Hat Enterprise Linux (RHEL).

Previously in my company, we used to use CentOS. CentOS will reach the end of life phase in the upcoming month, which is the reason why my company had to choose another product like Red Hat Enterprise Linux (RHEL).

The solution is used on an on-premises model.

Deploying Red Hat Enterprise Linux (RHEL) was surprisingly easy. The installers were the same as the ones used for other solutions.

My company did not have a strategy to deploy the product since we just needed Red Hat to hurry up, put it on a box, and figure it out.

My company did not seek the help of a third party to help us with the product's deployment phase.

The biggest ROI I have experienced from the use of the solution revolves around the area of customer satisfaction. My company's customers who use the product have a lot less to be changed in the product and it has helped save a lot of development and redevelopment time for our organization.

The cost and setup are not areas that are transparent for me. The tool's licensing part has been a real pain because when our company sells a system to a customer, they take full control of it in their data center, and we are not allowed to access it, even though they bought it from us. The license transfer has always been really awkward because our company initially had the license until our customers tested it and accepted the product. I was hoping to find somebody to talk to about the license transfer part with Red Hat products, but I don't know where to find someone associated with the solution.

My company briefly evaluated a product named Debian, but after that, our company's customers specifically asked us to go for Red Hat Enterprise Linux (RHEL).

Considering that the licensing part associated with the product is a pain, I rate the tool a seven out of ten.

We first used it for application installation to run applications on Windows. We had it running on Windows. We then upgraded it. It was still on the IBM platform, but it was still x86. We have now updated it, and it is now running on IBM Linux Z.

We use it for Internet banking, core banking applications, and other peripheral applications.

It has helped with consolidation. When we first started to do clusters, we were using Oracle cluster and Red Hat cluster. The Red Hat cluster was more stable than the Oracle cluster, so we had to uninstall the Oracle cluster and just use the Red Hat feature to have floating IP addresses between two cluster nodes. Having it in a cluster was the single most useful application of Red Hat in the environment.

We use Red Hat Insights, Ansible, and Satellite. Red Hat Insights is helping us big time. A year ago, I was looking at bolstering my team to about five or so administrators. With Red Hat Insights and other tools, I am satisfied with just two administrators. They are there just to manage the system and not necessarily go down into the trenches.

It seems that Red Hat Insights provides vulnerability alerts and targeted guidance, but my team would know that better. I manage a team that does that.

Its stability is most valuable. Its administrative aspect is also good. It is relatively easy to administer. I am familiar with AIX. AIX is super easy. I did not have to struggle much to adapt to Red Hat.

They can make the extended file system dynamic. Currently, we have to bring down the server to add an Hdisk. We cannot extend the database on the fly. We have to have downtime. We want to ensure that we make the blackout periods as minimal as possible. Currently, there is a gap in the file system management. I want to be able to expand the file system in a simpler way and have the application or the database use that expansion without any downtime.

I have been using Red Hat Enterprise Linux since 2004. It has been 20 years.

There is no problem with stability. It is stable. We have a couple of Red Hat Enterprise Linux 4 still running. We also have Red Hat Enterprise Linux 6 systems. The hardware is functional, but the application was retired. We cannot get an update for it. It has been running since 2008.

Its scalability is fine. There is no problem with scalability. We can do it in real-time. Now with containers and other things, we can scale on the fly without much downtime. We can build a small system and scale it. We can start at a much lower level than several others.

It has improved tremendously. I remember when it used to be centralized. I have been to North Carolina to get training, but now they can come to us for the training. The whole support architecture has improved. We can reserve hours for calls when the need arises. If we do not use it, it is reallocated the next month to some other project. They are doing well. I am impressed.

Positive

We were using and still are using AIX, but most of the applications have been imported, so we are between AIX and Red Hat. We are also using Windows, but Red Hat has stood out. It is not yet there with AIX, but it is getting there.

We were using Ubuntu and a few other flavors, but they were not organized. They were still too open. The support and the training for Red Hat Enterprise Linux was spot on. It was exemplary. We could find support easily.

We have them in clusters, and we also have standalone ones. We have DR where we synchronize with DR. We synchronize at the file system level with DR, which eliminates some of the application limitations.

We are using it on-prem, but we have applications to be upgraded in another 18 months, which would be a hybrid cloud.

Its installation the first time was overwhelming. Once you get used to it, the team settles down, and you have knowledgeable people, it is a breeze.

We have an integrator, a reseller, and a consultant. Somebody would come in and help us connect the dots. I guess that is their reseller, and then the integrator helps us properly connect the dots.

Pedro is our accounts manager. He probably comes from Puerto Rico, and then there is Lincoln Walters from Jamaica. Together, they help us identify the resources we need for the things that we want to do.

The biggest ROI is in terms of the reduction of human resources required to manage and maintain it. The administrative duties have been vastly reduced. You can even have resources from Red Hat. They have something where you can block certain hours a month and you can just use them as needed. If you do not use them entirely, you can reallocate them. That means you can reallocate unused resources. There are savings on investment.

We are still learning about it, but our TCO has reduced because we do not have to have as much manpower, hardware, and processes to manage and operate.

Licensing is the most attractive part of it. With Red Hat Insights and Ansible, we now know that it was done with the intention of simplifying the licensing so that you get the support for what you have and not necessarily what you want to have.

Red Hat Enterprise Linux has not helped us to centralize development. We have not capitalized on that as yet. I am here at the Red Hat Summit to learn about Kubernetes and containers. It is all new to me, and at this point, I do not know from where to start. I am getting exposed to so many things, but I still need to understand from where to start. I need to know the foundations. In about 18 months, we will be going to containers. We have people developing Dockers, Kubernetes, and other things, but we need to find a way to integrate them. We will have containers running on OpenShift, but we need to know how to secure, store, and manage those containers.

I have participated in a few presentations, and I see that there are prescribed ways to ensure that you maintain compliance by upgrading. In one of the presentations, one of the presenters said to not expand or scale too quickly because some of the applications get left behind. That is something that I am taking away.

The portability of applications and containers built on Red Hat Enterprise Linux will be good for keeping our organization agile. It is flexible. They say, "Build once and run anywhere." That is the buzzword for me.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say that Linux is for beginners, whereas Red Hat Enterprise Linux comes with the bells and whistles and the stability for business. It is an enterprise-grade software.

Overall, I would rate Red Hat Enterprise Linux a nine out of ten. There is innovation and adaptability. Ten years ago, it was unheard of. It has grown, and it has been growing tremendously.

We are using Red Hat Enterprise Linux for running various things. We have a lot of virtual machines. The applications that are running on it are a bunch of shell scripts for processing orders, marketing campaigns, generating reports, or running some Java applications.

We have the customization capability. We can easily customize it, and we can also automate and deploy it. I have a command line interface. I am a command line junkie, and I am able to use that, config files, and Ansible to be able to easily figure out what I need to do to automate things. It feels like I know what it is doing and how to make it do what I want. I do not have to weave some magical arcane hack the way I have to do in Windows.

Red Hat Enterprise Linux has enabled us to centralize development in a lot of ways. We have it hooked in through our GitHub. We are trying to combine where we are storing things and then have a standard way of how we are deploying things and have some standard configurations. With every single server, we do not have to worry about how to set this up because we are doing the same thing the same way. We can just do it across the board, and then we only have to worry about the interesting parts.

Red Hat Enterprise Linux's built-in security features are great for risk reduction, business continuity, and maintaining compliance. There are published CVEs, and there is SELinux, which I do not use and I always turn it off. Firewalls and tooling around that make it easy to use. The automation on top of that makes it easy to configure. With a push of a button, it is done.

We do not have to worry too much about portability. We are coming from Oracle Linux. We were primarily an Oracle Linux shop, and because that is based on it, it just works. We have not had any issues.

The fact that it is Linux is valuable. Why I like it in general is that I know what it is doing. I can figure out what it is doing, and I can make it do what I want. I am not delving into arcane registry things.

I am still trying to figure out the features it has. There is so much that it can do. What it does really well is that it allows you to do things.

It was probably 2008 when I first started using it. The company was using Red Hat Enterprise Linux, and I was with the internal help desk supporting the Linux side.

Its stability is great. It is stable and rock-solid.

Its scalability is also great. It does not matter if the host is beefy or not. It is just going to run on it, and it is going to handle the work. Whether you have a couple of cores or 64 cores, it is just going to do it.

Their support is good. There is good responsiveness. They quickly get me to the person who knows the answer, but I have not used them much.

Positive

We were using Oracle Linux. We are switching because of some of the things. Oracle licensing has been a point of frustration. Their support is comparably difficult to work with, and the support documentation is a mess.

Red Hat is so much easier to navigate. It has been overall a much more pleasant experience to work with Red Hat.

We are using it on-prem, and then our cloud is a Kubernetes cluster on AWS, so it is basically on-prem.

Our deployment model is a manual kickstart with Ansible for configuration. My experience with deployment is good. I kickstart it and then hit it with Ansible, and it is done. It is very easy.

I did the deployment on my own.

We have not yet seen an ROI. It has not been in for long enough. There are no savings in terms of manhours because the actual day-to-day usage remains the same with Oracle Linux or Red Hat Enterprise Linux. However, getting some of the metrics with Red Hat Insights is going to be helpful as we get into a better patching cycle. I am anticipating an easier life.

We are expecting an overall decline in the costs because of the differences between the Red Hat licensing and Oracle licensing. We are expecting a net decrease in overall cost. For using it, other than the license, there is no cost.

The setup cost is non-existent. With licensing, there was a little snafu because I misread something. There was a slight learning curve because we use virtual data center licensing. We had to understand how it all maps. We had to understand how that mapping works when the hypervisors are Red Hat or VMware. There is a slight learning curve, but it worked out. It ends up being easy.

I did not evaluate other options mainly because I have had experience with it before. From my prior experience, I already knew what I wanted.

We are trying to use Red Hat Insights. I need to finish updating the playbooks to hook our host. We are in the midst of transitioning from Oracle Linux to Red Hat Enterprise Linux. I have not fully hooked everything in, but we will be using Red Hat Insights.

We just started using Red Hat Enterprise Linux for containerization projects. We have not yet seen any impact of Red Hat Enterprise Linux on containerization projects.

If a colleague is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, a lot of it would depend on their use case, what they are going to need for it, and whether they have an enterprise environment. There is a cost associated with it which can be a downside. I am an open-source lover. I do not like paying for stuff, but I get it. They need to look at the cost, and if the cost is prohibitive, they need to look at something that is compatible and as similar as possible.

Overall, I would rate Red Hat Enterprise Linux a nine out of ten. I generally do not give out a ten. There needs to be something spectacular for a ten, so that is my personal bias against the top of the scale.