Red Hat Enterprise Linux (RHEL) Reviews

I use Red Hat Enterprise Linux to manage pre-configured web servers, troubleshooting issues such as "524 errors" and missing configurations in EMV files. Furthermore, I constructed an on-premises Kubernetes cluster on Red Hat Enterprise Linux 9 and configured it for ELK.

The Red Hat Enterprise Linux knowledge base is excellent. When I encountered an error, they were able to quickly identify the issue and guide me through the necessary steps to resolve it.

The Red Hat Enterprise Linux Web Console functioned properly throughout the lab courses.

Red Hat Enterprise Linux is excellent for commercial use and enterprise tools. It's best to use Red Hat for enterprises because it provides robust support available twenty-four by seven, which I have experienced.

To start working with Red Hat Linux was straightforward and user-friendly. I didn't encounter any complexities.

The most valuable feature of Red Hat Enterprise Linux is its comprehensive ecosystem. The detailed documentation eliminates the need to consult external resources, and the knowledgeable support team provides expert assistance with both technical issues and site navigation.

Improvement is needed for supporting Kubernetes clusters because it is less supported by Red Hat according to my experience. There are also some gaps in documentation which affect configuring Kubernetes clusters.

I have been using Red Hat Enterprise Linux for four to six months.

I have not faced any downtime or stability issues with Red Hat Enterprise Linux.

I have not encountered any scalability issues with Red Hat Enterprise Linux.

The technical support is excellent. They promptly addressed my concerns regarding permission issues when I contacted them.

Positive

I used CentOS for non-enterprise purposes but switched to Red Hat for enterprise applications due to its superior support and stability. However, Ubuntu is generally preferred for Kubernetes deployments.

Red Hat Enterprise Linux is nine out of ten.

Red Hat Enterprise Linux does not require maintenance.

Our mid-size organization has between 20 and 50 employees, including our DevOps team, who use Red Hat Enterprise Linux.

I recommend Red Hat Enterprise Linux due to its support and strategy.

In our environment, we primarily use Red Hat Enterprise Linux (RHEL) for managing customer environments and our own. The customer environments are mostly Apache web servers. Some customers have databases, like Postgres, running on Red Hat Enterprise Linux. Others run native Docker on it to manage application dependencies. 

We run containerization projects in the OpenShift environment based on Red Hat Enterprise Linux OS because that's more suitable for containerized workloads. You can do some machines on Red Hat Enterprise Linux, but not all of them. Your worker nodes need to be Red Hat CoreOS, but your master nodes can be Red Hat Enterprise Linux.

I was more experienced with other Linux distributions and Docker. It's open source, so you can fetch Docker and run it, but they don't have support if you have questions or if something isn't working as expected. Podman is similar to Docker. I don't primarily use Red Hat Enterprise Linux for containerization, but I set something up in Podman on Red Hat Enterprise Linux. It isn't used that much. Tinkering and development are the main reasons you would use Podman on a single centralized Red Hat Enterprise Linux machine. If you want to orchestrate on a larger scale, you use OpenShift.

Red Hat Enterprise Linux has made significant contributions to our business continuity and compliance efforts. If a critical vulnerability is spotted in the wild, Red Hat fixes it most of the time. It's usually within a day if it's a zero-day vulnerability. Log4J was a bit more difficult because it was not a single package, but it was mostly shipped with other products. It's hard to analyze which application is vulnerable and whatnot. The solution lets us centralize development. We use Ansible to orchestrate the tooling deployment or to fetch a lot of information. 

Red Hat always clearly describes the vulnerability on its security pages as a CVE score. You can fix errors by patching or mitigating them. If the patch hasn't been released, you can mitigate it to prevent the vulnerability from being exploited. Red Hat Enterprise Linux helps us guide the data and ensure it is correctly placed. I was monitoring it daily, but it was a bit too frequently. Now, we get vulnerability notifications weekly or monthly about a vulnerability or exploit that's been discovered. I also look on Reddit directly to see if there's a fix or a mitigation we can implement.

Sometimes, when upgrading or migrating systems, there are differences in the repositories of the versions that aren't one-to-one replaceable. For example, there are significant differences in the repositories from version 7 to 8. We needed to upgrade Red Hat Enterprise Linux from version 7 to 8 because it had reached the end of its life. A Postgres database was running on it that used a Red Hat Enterprise Linux 7 package, allowing some database or reporting features. When I upgraded to Red Hat Enterprise Linux 8, it was not in the repository. I needed to install it with some workaround. Of course, it was installed with some minor incompatible dependencies. 

I have mixed feelings about the built-in security features. SELinux must be configured correctly for the port and directory, or applications won't run, so we primarily disable it. Sometimes, we enable it and tinker with legacy systems deployed long before I joined the company. However, chances are it will break something if you enable it. 

We have been using RHEL for three years.

Red Hat Enterprise Linux has performed very well for our business-critical applications, with minimal downtime.

We don't need to dynamically scale our application because of our workloads, as we mostly use Red Hat Enterprise Linux for our internal tools. We don't have much demand to scale out.  Containerization lets you quickly scale out your application with some bots if your hardware supports it, and you have enough resources. 

In VMs, we didn't need to dynamically hot plug some service to compensate for the load. It would be vertical scaling by adding more resources. Sometimes, we need to do that for databases that consume a lot of memory, CPU, power, etc.

I rate Red Hat support eight out of 10. It depends on the priority of the requests. We had to launch several P1 requests because something wasn't working in our OpenShift environment, and we were stuck. The support response was quick.

However, we were annoyed that most of the support was based in India. Sometimes, they don't know what the problem is and need to escalate it to an expert in the US or or Germany. It prolongs the ticket resolution, but once it gets to the expert, they fix the problem instantly because they know more. 

Positive

We previously used other Linux distributions with Docker. We prefer Red Hat Enterprise Linux because of its enterprise support capabilities, which open-source distributions like Debian or Ubuntu lack.

I'm unsure what the standard Red Hat Enterprise Linux license costs for one machine. We pay for premium support that guarantees a response in two hours. 

I rate Red Hat Enterprise Linux eight out of 10. If applications and package installations work correctly, I would give it an 8.5. It's a pleasing OS to work with, especially Red Hat Enterprise Linux 8 and 9, which are more polished than Red Hat Enterprise Linux 7. I briefly interacted with Red Hat Enterprise Linux 6, I'm 27, so I know I'm very young, but I know colleagues who worked with Red Hat Enterprise Linux 4, 5, and 3. 

Other open-source Linux distributions might work if they have high levels of community involvement so the community can identify and fix vulnerabilities quickly. Alma and Rocky Linux are all upstream from Red Hat Enterprise Linux. If you want to go with an open-source distribution, I will point you to Alma and Rocky because they are the one-to-one replacements from CentOS. You don't need a subscription. 

We are a big company with many customers, so we prefer a stable platform with support. You can't open a ticket for open-source distributions like Debian or Ubuntu if you have a problem, ticket. With Red Hat, you can open a ticket if you discover a bug. That's included in your support subscription. You also get regular patches, so we can show our customers we are compliant, etcetera. It's a no-brainer to use an enterprise distribution with support instead of something open source where you don't have a support subscription.

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.

We use Red Hat Enterprise Linux as our server operating system to install and configure various applications. Its uses include system troubleshooting, DNS configuration, and many other tasks, especially in a mixed environment with Ubuntu.

Patching Red Hat Enterprise Linux in our environment is a straightforward process that utilizes Red Hat Satellite. We identify necessary patches for production servers in the content view and notify customers two days in advance via email. Before patching, we verify the Nagios servers for identification purposes. We then execute a pre-configured Ansible playbook to efficiently patch our 300 servers. This playbook was already established, and our only interaction with it is to run it.

The web console is handy, especially for tasks like command line operations. Its secure environment allows for the safe execution of queries.

Red Hat Enterprise Linux is most valued for its reliability, as evidenced by my daily use.

The documentation needs improvement. Providing more detailed explanations would make it easier to work on projects.

I have been using Red Hat Enterprise Linux for my entire career, which spans over eight years.

Red Hat Enterprise Linux is stable. There has been no significant issue regarding lagging or downtime.

Red Hat is highly scalable and essential in the industry. I would rate scalability nine out of ten.

The customer support from Red Hat is good. They are always there to help when needed.

Positive

I have used Ubuntu, and Kali Linux alongside Red Hat.

I have been involved with migrations to Red Hat Enterprise Linux, which are not complex. For example, migrating to Red Hat Enterprise Linux 7 or 8 is easy, requiring only the installation of necessary dependencies and the creation of a file to sync files to the new system.

I typically work as part of a team rather than implementing integrations on my own.

Red Hat Enterprise Linux is quite expensive, particularly its technical support, which can cost $500 per hour.

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

Realizing the benefits of Red Hat Enterprise Linux took time, as post-deployment troubleshooting was often necessary. This included tasks like opening ports and verifying functionality, which were sometimes prerequisites for the system to operate. These requirements varied depending on the specific application used and its security needs.

We perform maintenance on Red Hat Enterprise Linux every weekend, including backups. Incremental backups are done daily, while full backups are completed every weekend.

Red Hat Enterprise Linux's role-based security model enables us to provide discretionary access levels to users based on their roles and their responsibilities. We can also assign access based on service level to maintain service-level accounts for any purpose. If we need to back up a Red Hat Enterprise Linux box, we can assign a role to access that box only on the backup level. 

Red Hat Insights allows us to find vulnerabilities and conduct assessments from our central portal. It gives us insight into the compliance levels of different boxes and their licenses. Red Hat Insights helps us be proactive by giving us the details of recurring issues and vulnerabilities or zero-day threats. It automatically shows us what needs to be prioritized. It improves operations to have a single pane of glass for all your inventories and business. You can also implement automation and remedy most things from the cloud console. This is very helpful. 

Red Hat Enterprise Linux helps us achieve security standards certification. Most of our customers require compliance with regulations and internal security policy also. We have to be compliant with the profile for each standard based on Red Hat Enterprise Linux profiles or OSCAP integration. Satellite helps us remedy and manage compliance issues in daily operations.

Red Hat Enterprise Linux is the most reliable Linux flavor in terms of enterprise governance. I prefer it for its code stability, support, and integration. The lifecycle management features help us maintain compliance and keep the components updated.

The built-in security features simplify risk reduction. For example, Red Hat Enterprise Linux has built-in OSCAP profiles that we can select during implementation based on our industry and compliance needs. Using the OSCAP profile, we can minimize the effort needed to keep the software up to date. We also like the Red Hat Co-Pilot, which allows you to configure most things from the GUI.

We also have OpenShift, which enables elaborate, portable, and reliable ccontainerization. We use the System Roles feature when we have to disable root users and assign the system roles on the application level because some applications do not require root-level access or real group access. The System Role feature allows us to impose level controls and segmentation between the users. We can also automate security configurations to maintain consistency across systems over time.

I would like to use OSCAP profiles without the dependency on Red Hat Insights. If you install the OSCAP profiles from Red Hat Insights, I'm not sure if it is currently available in the cloud console. Most of the time, we manage compliance from Red Hat Satellite, but this feature could also be built into the console. Maybe it's not an issue price-wise most of the time, but it would be easier if we could use the same console and test-level capabilities.

I also want the co-pilot to provide more granular control and more features in the GUI, so we can have one configuration from the GUI itself. It would be helpful to have a feature similar to the one in Windows where we can manage all the net flows from one console in a single pane of glass and install it on-premises like an admin center. It would be great if Red Hat had some kind of admin center to manage all the Red Hat Enterprise Linux boxes without using an additional product like Satellite or something, we could use the co-pilot on all the systems to monitor the dashboard.

We started with Red Hat Enterprise Linux 6 in 2015. Now, we are on Red Hat Enterprise Linux 9, so it has been around eight or nine years.

Red Hat Enterprise Linux is a robust product. 

The scalability depends on the computing capacity and architecture. It varies based on whether we are replicating boxes or putting the Red Hat Enterprise Linux images into containers. The tool we use for orchestration is also a factor. 

I rate Red Hat support 10 out 10. We are mostly dealing with Level 1 or Level 2 support, and we always get a prompt response. Remote support is also available, which is nice. 

Positive

We used some open-source Linux flavors that are now obsolete and CentOS. Red Hat Enterprise Linux provides excellent support for migrating from CentOS to Red Hat Enterprise Linux at any level, so kudos to Red Hat for that. There is a great tool that enables us to migrate an existing application without any changes, so we can convert CentOS boxes.

There are one or two commercial Linux flavors that can compete with Red Hat, but their based on different architectures. Red Hat has a large portfolio, including OpenShift and SQL automation, offering deep integration between these tools. I don't think there is a competing product that offers a comparable product portfolio because Red Hat is under the umbrella of IBM now and also provides a multi-cloud solution. 

The initial deployment is straightforward. There's no problem. However, it also depends on what we want to achieve. Some of the options add a little complexity. It isn't very complicated, but it requires a different method. Overall, the general installation and configuration are effortless, and we don't have any issues. The initial installation can be done in 15-30 minutes, depending on the computing and storage capacity. 

We have one administrator experienced in Red Hat Enterprise Linux and enterprise Linux for maintence. We prefer a certified person who can understand the data complexities and advanced configuration, but a technician doesn't need to be a specialist to conduct the installation. 

The pricing depends upon the customer's bill of materials and what the customers are planning. Sometimes, a reseller and vendor partners provide a better price. I recommended buying the Red Hat Virtual Data Center instead of buying the Red Hat Enterprise Linux standalone licenses if anyone just wants to run a workload in the cloud environment. Virtual Data Center is the most cost-efficient.

The Red Hat Enterprise Linux license has a one-time cost, but there is an ongoing subscription for support with various levels. The license is perpetual, but we pay annually for support. Red Hat's support license is robust. You get three levels of professional support plus community support. Our banking, finance, and telecom clients rely on Red Hat Enterprise Linux entirely for their production workloads, so they need to minimize downtime. There is no comparison between professional and open source. We can provide support for some of our clients and set up redundancy, so that's something we can consider when we're looking at licensing or support costs. 

I rate Red Hat Enterprise Linux 10 out of 10. Red Hat Enterprise Linux is an affordable product and a great value. It is constantly evolving and adding capabilities. We can orchestrate a multi-cloud environment for Nutanix under Red Hat Enterprise Linux. It's an excellent product for virtualization.  

We are using the solution for automation. Mainly, we're doing a lot of automation with it. One of the projects, for example, is for ensuring payments processes on forms. We streamline and optimize the insurance claims process using OpenShift. This has enabled us to do faster claims processes and make resource utilization more efficient than it was. Everything can be done online. There are no papers involved. 

It is mainly just cutting out redundant tasks. The focus was mainly driven by driving costs down and efficient resource utilization. We wanted a solution that could make deployment easy and ensure scalability.

The biggest benefit has been the automation. It affected our delivery schedule. Instead of doing something in two weeks, we do it faster. We've cut down our production time. And people are able to focus on other tasks since they're automating a lot of things. Even with our clients, when they have issues, we have created a system where they can send out a ticket. And from that ticket, we can diagnose, and it's easier to solve the issue at hand. 

In terms of cost per head, we've seen a drastic drawdown from that. It is mainly optimizing a lot of our systems and resources.

The high availability is great. It's available most of the time - even when we're doing upgrades, provisioning, configuration, and patching. It made things easier for us. 

The automation is great. I'm a big fan of offering convenience to people and making systems easier for people to understand and use. 

There are good features, such as proactive monitoring as well. It offers predictive analytics, which helps you identify issues before they impact operations. We can foresee several problems. On top of that, this is how we can combat those problems. These types of features are really valuable when considering a company's strategy and when it comes to the impact of operations. 

We are able to move workloads between different clouds or our data center using Red Hat Enterprise Linux.

The knowledge base on offer is quite extensive. We started learning from a third-party provider since we've had a lot of use cases. Maybe you are installing something, or maybe during virtualization, you have to do something, and you need more information. The Red Hat OpenShift community is quite huge. Even a resource such as YouTube has people releasing videos on common problems. Even outside of Red Hat itself, the Red Hat community is very good. The information is extensive. The knowledge base is there. There's a lot of information sharing. People do not try to gatekeep information. 

When it comes to provisioning and patching, so far, we have not had a lot of issues. We currently are using a subscription model. In terms of getting security patches and updates, they support us quite well. There's a 24-hour support base and they're quite good. 

I've tried the Leapp and Red Hat Insights features. It helps with proactive monitoring. It did analyze the system configurations and compares those against databases of known problems and fixes. Basically, there's a pool of data that has common issues and it analyzes how you've configured your system and then compares them. It can come back to you and say, "Hey, this is your problem. Why don't you try the solution?" It's like a good AI tool. It gives us a lot of help. It's quick. Thanks to this feature, we sometimes find that we don't really need to open a ticket for support.

We realized the benefits of using RHEL in months. We were told when we were doing the onboarding, we'd see benefits in six months. For us, it took a little over eight months. That was due to some of our internal processes that we had to do, some sign-offs, et cetera. Still, it took us less than a year. Over time, we are down 20% to 30%.

In the beginning, we didn't start on the cloud. Only now are we fully transitioning to going off-site. There are still some clients who are a little resistant to going to the cloud. It's nice to be hybrid, to accommodate both. We've done a lot of virtualization and server consolidation. So far, everything is running smoothly. 

When moving workloads between different clouds or data centers, it's not that simple. There are a lot of things that you need to consider, including prerequisites and things like hardware, network, operating systems, et cetera. Once you get the hang of it, it becomes easier. However, in the beginning, it was very, very challenging. Coming from a development background, I found it easier to use command lines.

I've hit some snags doing updates or changing things for clients. 

It would be nice if they improved vulnerability management. They could add more security tools and tools for provisioning. 

I've used the solution for two years. 

The stability is good. We don't really have any downtime. I'd rate stability nine out of ten. 

We've had no issues with scalability. It's quite user-friendly. 

During the implementation, we did have to open a support ticket. They assisted us effectively.

Positive

I've never tried other solutions. I know of other solutions, such as Ubuntu. However, my interactions with that solution have been minimal. 

The initial setup was a little bit complex. The instructions, however, were very clear, and our deployment strategy was clear. Still, for the technicians doing it, it was complex.

The setup took about a week and a half.  

I've been involved with two upgrades so far. They were challenging. There were a lot of teams involved. There needed to be a lot of migration planning. We had to use the Link Utility and we did a lot of testing first. We spent a long time verifying the applications and checking dependencies. It was quite a learning curve.

There is some maintenance needed in the form of system updates. 

We did get a lot of help from RHEL. We had senior engineers guide us through the setup.

We've seen an ROI of around 30%.

When we went through IBM, it was quite expensive. Now, we are going through AWS, which is less pricey. 

We started off as a partner to IBM, and IBM opened up the opportunity for us to build certifications for Red Hat through the certification program. Then we became support specialists, taking on RHEL projects. We are in the process of becoming a reseller. 

I'd rate the solution eight out of ten. We're doing a lot of big data infrastructure and they are giving us good stability and performance.

We have a database that we maintain for root passwords, and sometimes I need to break the root password to reset it. We work a lot on logical volumes where I need to grow and shrink volumes on the fly. I did not have to shrink the logical volumes much, but I worked a lot on growing logical volumes on the fly to make them available for the database team. I have done network-related things. I configured network multipathing or IP multipathing where we can parallelly route the traffic to multiple ethernets.

I work a lot on user-related issues as well. We are also using Ansible a lot for automation. I am writing some playbooks, so there are a lot of use cases.

Red Hat Enterprise Linux helps us a lot. We host a lot of our applications on the Red Hat platform. We are using Red Hat Enterprise Linux for both on-prem and VM platforms. Most of them are VMs, but we do have some old legacy systems where we have Linux running on some Dell architecture. Our goal is to get rid of them this year and implement everything on virtualization because virtualization is growing a lot.

Red Hat Enterprise Linux has enabled us to centralize development. We are using it in the production and lower environments. We are using a common platform for our deployments. We have a centralized environment.

In terms of portability of applications and containers built on Red Hat Enterprise Linux for keeping our organization agile, it is flexible. Agile methodologies are very popular nowadays, and they help with coordination between dev and production teams. It is fulfilling the gaps between these teams. It is helpful.

I see so many features in Red Hat Enterprise Linux that I do not see in other Linux operating systems, such as Ubuntu. That is why Red Hat is very popular. All my experience is mostly on the Red Hat side. In terms of features, I like breaking root passwords, and I like the XFS file system over ext4.

I have not used it on the cloud side. I have not heard much about how Red Hat is doing on the cloud side. In the market, AWS and Azure are very popular, and they have captured most of the market. If Red Hat can improve on the cloud side, they can retain their customer base. Their customers do not need to go out for other cloud resources, and they can use the Red Hat cloud.

We are using it on-prem and in the virtual environment on VMware. We are using a cloud, but it is not a Red Hat cloud. We are using AWS in our organization. We have some EC2 instances deployed with Red Hat Enterprise Linux images, but I cannot say it is a Red Hat cloud. It is an AWS cloud, and we have instances. We are depending on a third-party cloud. If Red Hat provides that kind of service to our company, we can retain Red Hat. We do not need to go for a public cloud.

I have been using Red Hat Enterprise Linux for almost 12 years. I started with Red Hat Enterprise Linux 5.

It is a stable platform, but our company still wants to stick to the older version. They do not want to change the application base. They do not want to take risks. Unfortunately, Red Hat is not able to help to provide the patches for older versions. They suggest upgrading, but management is not doing that, so the Red Hat Enterprise Linux side is good, but our management side is bad.

Its scalability is good. We plan to use it more. We are growing. As our infrastructure grows, we are buying more licenses.

Their customer service is excellent. I like it. I am in touch with Ed who is one of the support engineers with Red Hat. He is helping me. 

I am also in touch with a few other people at Red Hat. If I run into any issues, I can simply email them, and I get a quick response from them. Based on the support I am receiving, I would rate them a ten out of ten.

Positive

We did not use any similar solution previously.

We are using it on-prem and in the virtual environment on VMware. Our cloud provider is AWS.

We are using the CI/CD model for Red Hat Enterprise Linux. We are using blue/green deployments as well for our containerized applications, and we have some canary deployments.

My initial deployment experience with Red Hat Enterprise Linux was not great. It was not as easy as the current version. It was difficult during those days. We had to load the GUI and then change to CLI. It is better now. Red Hat has made some improvements in the newer versions. The current version 9 looks better than any other previous version.

I did not use any integrator or consultant. I downloaded an ISO image from Red Hat. I downloaded and installed it myself, and it worked very well. I did not run into any issues with the installation process.

Over the last few years, we have been within budget. We do not have any constraints about Red Hat. We are a big organization. We use a lot of products from different vendors. We are working on cost optimization for some of the vendors but not Red Hat, so Red Hat is still good. We are still happy with it.

The biggest return on investment is the customer base. We are in the telecom industry. We try to get as many customers as we can. Red Hat is not the only product that we are using, but it is a major product that we are using in our company.

We are good as of now. We do not have any concerns about licensing. Its price is still good for us.

We are not using Red Hat Enterprise Linux for containerization projects. We are using Kubernetes and Dockers for that.

When it comes to patching, our goal for 2024 is to make all the systems compliant. Especially at the infrastructure and application levels, I am actively working on the compliance tasks, and our goal is to fix all vulnerabilities. I am working with someone at Red Hat on some issues because I am not able to find the exact patch for certain vulnerabilities.

For now, we are happy with Red Hat Enterprise Linux. We are happy with what we are getting.

Overall, I would rate Red Hat Enterprise Linux an eight out of ten. The reason for reducing two points is that I have not explored other operating systems very well.

My company currently uses Red Hat Virtualization to host all our virtual machines, and then we install Red Hat Enterprise Linux (RHEL) for almost everything we do. My company only has 30 or 40 Windows Servers, while we have over 2,000 Red Hat Enterprise Linux (RHEL) machines. In my company, we use Red Hat Enterprise Linux (RHEL) for everything from provisioning systems to Speedtest Servers to whatever we need in the company.

I would like to say Red Hat Enterprise Linux (RHEL) is much more efficient than Windows, and my employees love the Linux command line. All in all, Linux is what my company has been using since the beginning, so it is imprinted in everyone working in the technology section of our organization.

All Red Hat Enterprise Linux (RHEL) features have been valuable.

Red Hat Enterprise Linux (RHEL) is a Linux system, and in our company, we could probably use different Linux systems. My company mainly uses Red Hat Enterprise Linux (RHEL) because of the kind of security and the patching delivered, including the backporting of patches, instead of actually having to do version upgrades. The product's valuable features include stability and security.

In my company, the solution has helped centralize development in most parts.

The use of the product for containerization projects is an area that my company has been dealing with lately. In our company, we are installing a lot of OpenShift clusters now and moving that way, but if they run on Red Hat Enterprise Linux (RHEL) or bare-bones or bare-metal OpenShift, the shift needs to be made.

In terms of the impact my company has experienced after making Red Hat Enterprise Linux (RHEL) a part of our containerization projects, I would say that a different team is handling the development parts for our company. Our company would be happy if the products we use were Red Hat Enterprise Linux (RHEL) or OpenShift. My company is very interested in Red Hat Enterprise Linux (RHEL), even if it will take many years for us to be completely over containers.

As per my assessment of the tool's built-in security features when it comes to areas like risk reduction, business continuity, and compliance, all of the aforementioned functionalities are the main reasons my company stayed with Red Hat Enterprise Linux (RHEL). My company prefers Red Hat Enterprise Linux (RHEL) because of its stability, patch management, and other features that make us feel more secure.

In terms of the portability of applications and containers built on Red Hat Enterprise Linux (RHEL) to keep our organization agile, I would say that my company has done a lot of automation, which helps us keep everything as flexible as we want. One of my team members told me that the product is super when it comes to everything related to automation. The tool allows you to be kind of flexible.

At the moment, I don't use Red Hat Insights even though we have looked at it in our company. In our company, we have put up Red Hat Insights, and we have it on the machines, but it's not that deep in use yet. I believe that Red Hat Insights will be more and more important since the security team wants to use it to get a better overview.

If I have to speak to a colleague who is looking at open-source cloud-based operating systems for Linux, I would say that everyone needs to make a choice when it is not something concerning our company since we are standardized with Red Hat Enterprise Linux (RHEL) or Red Hat products in our company. My colleagues will have to use Red Hat products if they work in my company.

Speaking of whether the Red Hat portfolio has affected our total cost of ownership across our enterprise landscape, I would say that we have been using virtualization in Red Hat Enterprise Linux (RHEL) for many years, and it has been a very good and cost-effective tool for our company. The product may reach the end of the life phase soon, so we have to migrate to some other solution, though we know that the prices may go up whenever we do it. Up until now, the tool has been very good.

My company deploys Red Hat Enterprise Linux (RHEL) from Red Hat Satellite. Red Hat CloudForm is a self-service portal we use in our company but now it is an IBM product. I don't remember the name as it is long and boring. Red Hat CloudForm is a self-service portal that is connected to Red Hat Satellite to provision the machines.

My manager role is the reason why I am not that deep into the technical part anymore. In my company, the IT team is happy with Red Hat Enterprise Linux (RHEL) since they don't have to use Windows.

Personally, I started using Red Hat Enterprise Linux (RHEL) around ten years ago. In my company, I have been using the tool for twenty years.

It is a stable solution.

The solution scales up perfectly fine, especially since everything is automated since we have a very small team of 10 people in our company managing everything, including 2,000 servers.

The product's support team was good whenever my company needed support services. Our company also uses some professional services from time to time, especially since Red Hat has a deep knowledge of the tool. If our company faces a problem, we have a very good connection with the tool's team in Norway, and they always help us, even if it's time-critical. The tool's support team manages to get us the consultants our company needs. I rate the technical support a ten out of ten.

Positive

My company has been using Red Hat Enterprise Linux (RHEL) from the beginning.

When I started in the company almost ten years ago, deployment of Red Hat Enterprise Linux (RHEL) was done with an ISO image, which you mount it up, and you put in the IP addresses and do a lot of manual things. It is a different story today since you just enter how many courses you want and how much disk you want, and the deployment is done in two minutes.

The solution is deployed on an on-premises model, and we don't have a lot in the cloud at the moment in our company. As an ISP, the services we deliver are kind of time-sensitive or latency-sensitive, so as long as we have a data center, it doesn't make that much sense to put stuff in the cloud just because it is the best.

In terms of the prices and license of the product, I feel the solution has been good so far, especially since it has been quite easy to understand compared to a lot of other tools. I have been working with IBM and other vendors, where I have seen how other tools might have a bit more difficult pricing or licensing models compared to Red Hat Enterprise Linux (RHEL). In terms of pricing, Red Hat Enterprise Linux (RHEL) has been quite okay in general.

Red Hat Enterprise Linux (RHEL) was present ten years ago before I joined my current company, so I don't know if any other products were evaluated against it before my joining.

We have a few applications that we have started developing in the cloud now managed by a different team, but I don't think they use Red Hat Enterprise Linux (RHEL) specifically.

I rate the tool a ten out of ten.