The primary software utilized across our business units is S4HANA, which runs on our SAP server hosted on Red Hat Enterprise Linux. Consequently, most Red Hat systems in our environment support SAP-related services. We operate approximately 105 Red Hat Enterprise servers dedicated to running these SAP services.

Red Hat Enterprise Linux was implemented due to its robust infrastructure, which allows us to efficiently manage our enterprise servers on a large scale using tools like Red Hat Satellite, Insight, and Ansible. This centralized management simplifies the orchestration and control of our extensive RHEL environment. Red Hat Identity Manager also ensures secure authentication and authorization for our remote systems. Beyond infrastructure, Red Hat's robust support is invaluable, providing timely solutions to complex issues. The operating system's strong security posture, including rapid patch deployment for vulnerabilities, further solidifies our decision to implement RHEL.

Red Hat Enterprise Linux simplifies risk reduction by integrating Red Hat Insights. This provides a comprehensive security posture assessment of our Red Hat systems, offering easy-to-understand best practice recommendations and applicable actionable remediation steps.

The knowledge base offered by Red Hat Enterprise Linux is detailed and contains numerous articles that can help resolve our issues.

Red Hat Satellite simplifies our patch process by helping us meet audit and compliance needs. We've set up a lifecycle environment within Satellite to test patches on development and quality systems before deploying them to the operating system. This allows us to roll out patches based on the environment, ensuring thorough testing before reaching production. Additionally, we leverage Ansible automation to streamline provisioning and manage patches effectively. While automation is ongoing, we have successfully implemented Ansible and Red Hat Satellite for provisioning, and we continue to identify areas for further automation within our environment.

Red Hat Insights provides best practice recommendations based on regular system assessments. Like other security tools like Microsoft Azure Defender, it can access a system to offer security improvement suggestions. I have a Red Hat Insights certification and find the tool valuable. It generates actionable recommendations that can be easily implemented through automated processes like FastScript, making it an efficient way to leverage data insights for enhanced system security.

Since implementing Red Hat Enterprise Linux, we have experienced high performance, improved security, excellent support service, and easier system management.

Red Hat Enterprise Linux has enhanced our security posture through timely security patch releases and best practice recommendations, which collectively have increased the protection of our data systems.

Red Hat Enterprise Linux allows me to manage all my Cloud and on-premise systems from one console.

The most valuable aspect of Red Hat Enterprise Linux is its ease of management. A robust suite of tools, including the user-friendly GUI and the powerful Red Hat Cockpit web portal, simplifies system administration. Cockpit provides a centralized platform for managing hosts, while Red Hat Satellite or automation servers excel at overseeing large fleets of radar systems.

Red Hat Enterprise Linux training and certification opportunities for engineers and administrators could be improved. While I have benefited from free training offered by other companies like Microsoft, I have not had similar opportunities with Red Hat. Despite holding a Red Hat certification, I incurred significant costs to achieve it. The training required for these certifications is expensive, and it would be advantageous if Red Hat provided more affordable training courses.

I have been using Red Hat Enterprise Linux for seven months.

Red Hat Enterprise Linux is highly stable.

Red Hat Enterprise Linux is scalable.

The support is good.

Positive

I have used Ubuntu Linux, Windows Server, and other solutions. Compared to these alternatives, Red Hat Enterprise Linux stands out as superior in terms of ease of management, security, and support.

The initial deployment is straightforward. Deploying it manually takes about fifteen to twenty minutes from start to finish using it manually.

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

We have 15,000 users all across Africa that use our systems.

Red Hat Enterprise Linux requires periodic maintenance to apply security patches and updates.

I recommend Red Hat Enterprise Linux and conducting a proof of concept to ensure it aligns with our requirements.

I use Red Hat in data routines for web, database, and container servers. Right now, I'm using three primary use cases.

Red Hat offers compliance consulting services. If we purchase hardware from companies like HP, Dell, or IBM, which also partner with Red Hat, they often guarantee compliance for their hardware. This compliance can extend to security regulations imposed by certain countries or governments, such as those based on NIST or CSSP standards. Red Hat's focus on compliance seems to center primarily around these hardware-related aspects and associated security requirements.

Red Hat's knowledge base requires an active subscription for full access, but developers can utilize a free, annually renewable option. With an activated developer subscription, users gain access to forums, documentation, the latest news, vulnerability reports, and other resources related to Red Hat Enterprise Linux and its associated packages. The knowledge base is now well-documented, and the active community quickly responds to forum inquiries, often within a few hours.

Leap is a feature designed by Red Hat to migrate its operating systems between versions. Introduced to address the end-of-life issue for distributions like CentOS seven, eight, and RHEL seven, eight, Leap allows users to upgrade from RHEL seven to eight, RHEL eight to nine, CentOS seven to eight, and CentOS eight to nine. However, Leap is specifically designed for Red Hat and works optimally only on Red Hat seven, eight, and nine. It does not function as intended on CentOS, Fedora, Oracle Linux, or other community distributions. Red Hat Insights is a complementary tool that provides valuable information to subscription holders about their licensed servers, including package installations, subscription validation, detected bugs, and vulnerabilities. It also offers alerts about new vulnerabilities and patches and facilitates license management and environment oversight.

I've used Convert2RHEL, a tool that simplifies transitioning from CentOS-based distributions like Leap to Red Hat Enterprise Linux. It supports converting only CentOS to RHEL by replacing binaries and installing Red Hat logos. Underlying Ansible scripts entirely handle this process. While I've had success with it, occasional minor issues arise but are easily resolved.

I have experienced minimal downtime while using RHEL. Some of our RHEL systems have operated uninterrupted for over 600 days. The only necessary reboots occur when applying kernel updates. Overall, RHEL has demonstrated reliable and resilient uptime and security.

Due to its built-in compliance features, RHEL is instrumental in achieving certifications for security standards. The system incorporates policies that align with regulations for governance and public institutions. When installing Red Hat Enterprise Linux in the cloud or on-premises, users must implement security policies that activate specific plugins and APIs to maintain compliance. Given its comprehensive coverage of contemporary compliance standards, Red Hat is the most valuable distribution.

Release updates are the most valued feature because Red Hat's rigorously tested release update pipeline sets it apart from other distributions. While many options are available, none match Red Hat's commitment to thorough package testing. Packages are initially delivered to Fedora, Red Hat's community distribution, for testing and validation. Proven packages then transition to CentOS, and after six months, the most stable and reliable packages are incorporated into the new Red Hat release. This well-defined pipeline ensures that Red Hat packages are stable and long-lasting. However, not all packages released in Fedora make it to Red Hat; some experimental or community-driven packages may not meet enterprise standards. Fedora serves as a testing ground, while Red Hat focuses on delivering a stable operational system.

Red Hat, known for its secure distribution, sometimes delays critical security patches for certain packages compared to other Linux communities like AlmaLinux or Rocky Linux. For instance, AlmaLinux addressed recent vulnerabilities in the SSH package within days, while Red Hat took over a week to release a patch. While Red Hat's rigorous testing ensures high-quality patches, the delay in releasing them can pose security risks.

Red Hat Enterprise Linux is a highly regarded but expensive distribution known for its top-notch software. This high cost often precludes smaller companies from adopting it. There is potential to make Red Hat Enterprise Linux more accessible to a wider range of businesses by lowering the price.

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

I previously encountered instability with an assistant. While using a non-Red Hat graphical interface, KDE, I experienced a system crash following a kernel update. This desktop environment proved incompatible with the new kernel. Conversely, servers utilizing only the command line never suffered crashes or downtime. I've observed the opposite trend in my Red Hat infrastructure, demonstrating exceptional resilience. For instance, during a complete data center outage two or three years ago, Red Hat systems recovered within minutes, while Ubuntu servers required significant maintenance. This suggests that Red Hat offers greater stability and reliability in our environment.

Specific features such as path movement and load balancing must be enabled when running routes within a cluster. Pre-installed software simplifies the process for system administrators to implement smart clusters and scale servers. Among various distributions, Red Hat is considered the most proficient in these areas, excelling in scalability and cluster server management.

The deployment was challenging, not because of Red Enterprise Linux itself but because the application runs within this distribution. Certain legacy software required manual installation on this new system, which complicated the migration process. However, the operating system itself is straightforward and plug-and-play. The difficulties arose from configuring the necessary applications within the distribution. I've had no issues working with or migrating to this distribution.

Red Hat Enterprise Linux is only affordable for large organizations.

If I had to choose alternatives to RHEL, I would consider Oracle Linux and AlmaLinux. Oracle Linux is an enterprise distribution based on Red Hat, offering binary compatibility, meaning applications built for Red Hat Linux will run identically on Oracle Linux. It is an enterprise-grade product without the associated costs, as the distribution itself is free, with charges only for optional support. While I believe AlmaLinux is more resilient and reliable than RockyLinux, my preferred alternatives would be Oracle Linux first, followed by AlmaLinux.

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

Cockpit is a technology offering a web-based console for server management. This web console can also perform any action achievable through the command line interface. However, I do not recommend it due to the inherent security risks of running a web server, especially when managing another web server. This introduces additional vulnerabilities and necessitates increased patching efforts. My preference is to maintain a minimalist system that runs only essential services. While Cockpit might be suitable for junior system administrators in the RHEL environment, as a senior administrator, I exclusively utilize the CLI, both on-premises via SSH and in cloud environments. I would only consider implementing Cockpit if we have junior staff and are willing to implement robust security measures such as firewalls, access control lists, and other protective strategies.

I used Red Hat Enterprise Linux to construct systems according to the application team's requirements. I build and support these systems through the development, testing, pre-production, and production phases, fulfilling both developer and operational roles. To ensure the systems can handle the application's demands and meet our cybersecurity standards, I implement all security measures outlined by our cybersecurity team.

The extensive knowledge base offers a full path from beginner to advanced levels. We can access everything needed to study, pass exams, and apply knowledge immediately. The information is presented clearly, without any abstract concepts.

Red Hat offers built-in security features that simplify risk management. Unlike Oracle Linux, which overlooks critical security features like C Linux, Red Hat actively develops and maintains robust security measures. As a result, Red Hat prioritizes system security, consistently providing updates to fortify its machines against potential threats.

Red Hat helps us maintain compliance by enabling us to create and modify firewall rules as needed, allowing for strong security measures that can be adjusted.

The security reports generated every three months are valuable for provisioning and patching as they identify vulnerabilities requiring remediation. I find all the necessary information to address these vulnerabilities and implement patches through the Red Hat Enterprise portal and community resources.

When I started using Red Hat Enterprise Linux five years ago, I noticed the benefits incrementally over time.

Red Hat's greatest asset is its extensive community, which provides valuable support and advice when issues arise. Due to the robust nature of this community, I have never required direct assistance from Red Hat Enterprise.

Red Hat offers customizable tools, such as Assemble, that enhance flexibility within enterprise products. Assemble is a platform capable of managing multiple systems from a single console.

While Red Hat offers essential starting and security documentation, I would like to see it officially recognize the more detailed and customized documents available in the community and make them accessible on its website.

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

Red Hat Enterprise Linux is the most stable system I have ever worked with.

Red Hat Enterprise Linux is scalable.

I changed jobs five months ago, and my new company uses Oracle Linux instead of Red Hat, so Oracle provides support rather than Red Hat.

I find Red Hat Enterprise Linux more flexible, with a larger community and numerous security advisors.

We found it less complex to build a new system on the newer version of Red Hat Enterprise Linux and migrate data rather than upgrading the existing system from, for example, version seven to eight. A simple upgrade risks data loss.

One person can do the upgrades and migrations.

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

The system requires immediate maintenance due to necessary security patches, unresolved vulnerabilities, and a constant influx of operational tasks from other teams. These daily demands include critical adjustments such as modifying service ports and implementing local firewall rules.

I recommend new users visit the official Red Hat Enterprise Linux website to review the guides, explore the community, and research information related to their Red Hat Enterprise Linux tasks. 

We use Red Hat Enterprise Linux to maintain our systems, manage our user logs, and monitor our storage.

The fact that Red Hat Enterprise Linux is stable has led to more enterprises wanting to use it. All the updates are current from a security point of view. So, the fact that we are one-managed or subscription-managed through Red Hat Enterprise Linux keeps us secure.

Red Hat Enterprise Linux's built-in security features simplify risk reduction and help maintain compliance, which gives us peace of mind.

The knowledge base of Red Hat Enterprise Linux depends on the end user. However, the information is always there, and the most reliable information is from the Red Hat system.

We have a dedicated server for provisioning and patching, and I am satisfied with how it works.

Red Hat Enterprise Linux's Image Builder and System Roles improve our productivity by increasing efficiency.

The Web Console is helpful because we use it to monitor and record users if we choose to, as well as check our system to make sure everything is up to date and we are current with the latest patches.

Red Hat Enterprise Linux helps us be more compliant.

Red Hat Enterprise Linux's ease of use in a controlled system, especially when dealing with constant repository updates, is valuable.

From a monitoring standpoint, we have Splunk, which is more versatile in monitoring data files, and Nagios, which can monitor multiple instances via Windows or Linux servers and different boxes. If Red Hat Enterprise Linux can improve its monitoring capabilities, that would be helpful.

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

Red Hat Enterprise Linux is stable.

I have not submitted any support tickets because we can find all the answers we need from the RHEL community for minor issues.

Positive

Red Hat has been the industry standard for most companies, but sometimes, organizations will run a Windows server and Active Directory alongside it.

The critical difference between Red Hat and Windows lies in their user interfaces. While both share a similar underlying structure, Windows offers a graphical interface for easy interaction, while Red Hat relies on command-line prompts. This makes Red Hat a more secure environment.

Red Hat Enterprise Linux helps improve efficiency, reducing vulnerability and, ultimately, a higher return on investment by minimizing IT costs and downtime.

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

We have between 100 and 200 end users. Red Hat Enterprise Linux is deployed in a standard, dev, quality, staging, and production environment.

Maintenance is minimal for Red Hat Enterprise Linux. We only deal with updates and patches.

We use Red Hat Enterprise Linux to run Oracle Databases for CC&B and JDM. All the RHEL stuff is on-prem. The CC&B team manages the customer care and billing stuff, but we take care of the operating systems, and the application users manage the applications. We have 200 to 300 users on RHEL. 

We are missing random devices for patching and everything, and we don't have the Linux data license for that. If we had that, life would be much easier. Right now, we patch using Yum updates and we manually do configuration changes from our end.

Red Hat Enterprise Linux improves our security. On our end, we only use the console to reboot the server and apply security. We patch it completely if we have any security updates. Every quarter, we run a report using quality and whatever it was pulling. That's what we are patching. 

Red Hat Enterprise Linux makes patching and scripting much easier, and it provides all the features I need for patching and VM updates. It's easy to apply Red Hat Enterprise Linux's built-in security features when it comes to simplifying risk reduction or maintaining compliance.

For phone support, we had to buy a license for all our servers, and it was a bit pricey for us. 

I have used RHEL for 21 years.

Red Hat Enterprise Linux is highly stable. We've never had any problems or crashes. It's very smooth from our end.

It's easy to scale Red Hat Enterprise Linux. Right now, we're discussing what will happen a year from now, when we plan to increase our usage. 

I rate Red Hat customer service eight out of 10. Their knowledge base is fantastic. You can easily find whatever you need. Their support responds immediately, whereas we struggled with support from Oracle. 

We were using Oracle Linux, and I don't see much difference except the support. We were not getting good support from Oracle because it took too long whenever we opened a ticket. Oracle was also too expensive, and patching is much easier with Red Hat Enterprise Linux. We were not looking for more features. Oracle Linux has a lot more packages than we need.

Setting up Red Hat Enterprise Linux was straightforward. You need at least two system admins to do so. Migrations and upgrades are also easy. Our main products are CC&B and JDM, with an Oracle database on the back end. We were highly satisfied with Red Hat Enterprise Linux for migrating all of those. We also have other solutions like SQL Server, which is on the Windows operating system.

Performance-wise, this Linux is better because you can ignore some packages if you don't need them. 

Oracle Linux is free, but we were having many other issues with it.

I rate Red Hat Enterprise Linux nine out of 10. Red Hat Enterprise Linux is very easy to install and manage. 

I use Red Hat Enterprise Linux as an operating system for government contracts. 

I like the flexibility Red Hat Enterprise Linux offers in terms of permissions. The patch management is much shorter and easier. Red Hat Enterprise Linux helps us move workloads between different clouds and data centers. It's pretty smooth and transparent. 

We use AMIs — machine images — for provisioning. The image builder is nice. It's a vertical Amazon machine image. They have each machine image, so you don't need to install anything. You can just copy the machine image. 

There's an operating system called EdgeOS, which is an edge operating system used by edge computing nodes in the cloud. If Red Hat Enterprise Linux had a version incorporating EdgeOS-type functions, that would be great. Otherwise, you have to learn a little bit of EdgeOS to work with those nodes.

We have used Red Hat Enterprise Linux for several years.

I rate Red Hat Enterprise Linux nine out of 10 for stability. 

I rate Red Hat Enterprise Linux nine out of 10 for scalability. 

I rate Red Hat support nine out of 10. 

Positive

Red Hat offers better support and stability. There are several others, including Windows, and Red Hat Enterprise Linux is a pretty stable standard operating system. 

I rate Red Hat Enterprise Linux nine out of 10 for ease of deployment and migration. Deploying an AMI is straightforward. We hardly had to do anything. It's pretty much automatic and uninterruptible. 

I wasn't involved in the licensing, but Red Hat Enterprise Linux's price should be reasonable if the government and others get it. 

I rate Red Hat Enterprise Linux 10 out of 10. It's the top of the line.

The main use case is generating golden images. All the deployments of operating systems and virtual machines on the servers are based on the golden image. The developers and providers can run all the applications on top of those.

Whenever we need to remediate any vulnerabilities, patches are available. These patches are not only for current exploits but also for back-porting for bug fixes and security fixes. These patches are available from the most recent versions to the specific version that we are using.

Red Hat Enterprise Linux has enabled us to centralize development. We have a golden image of the operating system. That golden image sets the standard for all the security policies that we are applying to it. For example, the partition scheme and the best practices that we apply to the golden image are the starting point for all the developers to start working with all the applications and also executing appliances or applications from providers.

We are using Red Hat Enterprise Linux with Podman for containerization projects. Red Hat offers what is called UBI or Universal Base Image. That image is already configured to be secure and have good performance. To start working with containers, we just have to pull UBI as a base for our images and start working on those. It has impacted our containerization project because instead of using Docker, we can use Podman. There is a common container image that is used by the majority of the customers, but I forgot the name of that one. Instead of using that, which is like a very minimal image, we are using UBI because it is already secure. It has the majority of the benefits of our Red Hat Enterprise Linux image but in a container image.

There is portability of applications and containers built on Red Hat Enterprise Linux for keeping our organization agile. That is a very good option to have because you do not have to worry about the underlying system. You just have to worry about your application and have the application running on top of your image based on UBI. It is going to be so easy to have the application running either on a machine with Podman or have the same application running just on top of OpenShift. It is so easy to move a container-based application that can be executed on top of Red Hat Enterprise Linux with Podman or on top of OpenShift. 

Security, packages, and updates are valuable. There is also the possibility to do unattended installations. This way you can define how you want the installation to behave and be configured whenever you do the deployment.

One of the best features is having a tool called OSCAP, which is a tool that is going to allow us to apply security profiles to the golden image. This way, all the security features or policies can be applied in real time. This way, we can follow all the policies that are defined by our security teams.

There are not a lot of areas to improve because the majority of the time, Red Hat is constantly improving it. The only area would be in regards to being capable of running on other architectures like ARM. They are about to release a new version that is available to be executed on ARM architecture.

We have been using Red Hat Enterprise Linux for about a year.

It is very stable.

It is scalable. We have plans to increase its usage.

It used to be better. It is still good as long as you can get in touch with a level 3 support engineer. If you have a trained engineer who helps you with what you need and who understands how to ask for specific details of what you need, you should be good. But, unfortunately, if you start with a simple detail of what you are experiencing and what kind of help you need, you will receive the same response. For example, you are pointed to a knowledge base article, and that is it. The support engineer is supposed to help you with your issue or request, but unfortunately, that is not happening anymore. It used to, but I understand.

We are looking for a support engineer to go all the way. The only way for you to contact support is via the support case system or page. After that, you interact through the ticket or email. You do not have a chance to have a call. If we have escalated a case, it is usually better if you have a person for a proper understanding and proper advice on what you have to do and how to resolve the issue. It could be that you need a new product, subscription, or service, but you do not know that.

Neutral

When I got into the company, they were already using Red Hat Enterprise Linux, but back in the day, I used to have HP-UX. That was a very ancient system. It was Unix-based. It was a proprietary solution. HP-UX was a platform licensed based on the old Unix code that was tightly integrated into hardware built only by Hewlett-Packard. You could not run HP-UX in any other place. You could only run it on hardware created by Hewlett-Packard. The intention with that was to run only on the Itanium architecture, whereas Red Hat Enterprise Linux can run on x86 architecture. It is also open-source.

We have it on-premises. It is in different locations. We are following a strategy to publish the images of the operating system. This way, multiple teams can grab the images and have their own procedures to deploy within each separate environment. We have multiple teams working on developments and they need a base image to start working on all the development stuff. Because they are all independent teams, they have access to a single source of image. This way, they can start working on further customizations and whatever they need.

We implement it in-house.

The ROI is in terms of the time that I have to invest in doing customizations, applying security policies, and fixing the supply to the system, wherever I need those.

The reason for going for Red Hat Enterprise Linux is to improve the time to market. It is so easy to just generate a new image. We can configure it with all the security features and all the libraries and packages we need. We can also configure it with the ones requested by developers. We can do all of that. It is so much easier than what we can do with Windows, for example.

It is very straightforward. We do not have to think much about having to get all the subscriptions related to the Red Hat Enterprise Linux fleet that we have because all the subscriptions came in pairs of CPUs or even for an entire bare-metal server. That way you can partition your bare-metal server into multiple virtual machines, and then you are covered. As long as your bare-metal server is covered, you can roll out any number of virtual machines on top of it. It is very easy to get subscriptions for your bare-metal server, and you can utilize whatever you want.

We evaluated operating systems or Linux distributions created by the community or run by the community only. We evaluated them mainly because of costs.

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 they would not have the same team supporting all the operations and all the critical features and patches that they receive with Red Hat Enterprise Linux. They can go with one of the clones, but unfortunately, at the end of the day, the clones are going to deviate from Red Hat Enterprise Linux. With Red Hat Enterprise Linux, you can also create support cases to receive back-ported bug fixes and security fixes, and you get very cool features such as Insights, Satellite, or system roles provided along with Ansible. 

We are currently not using Red Hat Insights but that is an awesome tool.

Overall, I would rate Red Hat Enterprise Linux a ten out of ten. It is an enterprise Linux distribution. It was one of the first distributions to focus on the enterprise. There are others, but Red Hat is the main contributor to the Linux ecosystem. Because of that, it is so stable. It has proper support. It also provides the Linux ecosystem with new features and enhancements.

The use case in my very early years was for dedicated servers for doing web applications.

We almost exclusively use Red Hat. The benefits boil down to the support. There is no problem getting support. Whenever we have an issue that we cannot solve, which does not happen often, we have somebody who is there either virtually or physically.

We use Red Hat Enterprise Linux on-prem and on the cloud in a hybrid environment. We probably also have edge devices. I am not completely sure about that one. Having it in a hybrid cloud deployment has been no different than having it on-prem. Running it on-prem is just as good as running it on the cloud for us. It simply works.

I appreciate the dashboards that are available online. There has been a lot of feedback on the CVEs. The most recent one that came was probably related to Zutil. Red Hat made an announcement very quickly saying that if you are using only Red Hat features, you do not have to worry about it. It does not run on their operating system. Unless you are custom compiling, it does not work on their system. I greatly appreciate little things like that because they save us a lot of time. If Red Hat is simply saying that it is not a part of their repo, I do not have to look for it.

We use Red Hat Insights but not company-wide. It is one of those things that simply saves you time. I do not want to have myself or anyone on my team go out and check various things. That is the whole purpose of using Red Hat Satellite. The whole purpose of all different dashboards and these websites is to use what you have. Let it report out what you have and not continue to write scripts just to check things.

Their support is valuable. Whenever I had a problem, I could get on a phone call with somebody. I did not have to go to some random forum or send an email and wait forever. I could call somebody.

It does have a workstation option, but you rarely hear anything about it. I would love to see the workstation replace Windows. That is a stretch goal, but it is possible.

I have been using Red Hat Enterprise Linux since version 4. It has been a while.

It is stable as long as you do not do something stupid.

Red Hat specifically works hard to make it difficult to not be able to scale it into anything. The only thing that I do not see it being capable of, officially at least, are the IoT devices. Technically, it is possible to get it on those devices, but that is not something Red Hat is focusing on right now. From a scalability standpoint, it comes down to what makes a reasonable profit and what is a good return on investment while choosing how to scale and where to scale. Red Hat is doing it right so far.

Prior to a few months ago, the support that we got from a TAM point of view was next to none. Now that I understand the scenario a little bit more, it was not because Red Hat was not doing its job or did not want to do more support. It was because of how the contracts aligned, and more importantly, who in our organization was handling those contracts. We had a recent change in our organization in terms of who is running what and who is handling what. When that change happened, the doors really burst open. Now that we have a different person he is working with, we are getting incredible support from our TAM. He is in communication with us on a very regular basis. While I have been here at Red Hat Summit, we have gone out to have meetings twice. I cannot speak highly enough. I would rate their support a ten out of ten.

Positive

My current organization has pretty much always used Red Hat, specifically Red Hat Enterprise Linux. There are all sorts of flavors of Unix in our environment. Almost all of them are there because they are managed network devices.

We wanted to stay close to Red Hat Enterprise Linux simply because of the mentality of the business. We have got some people who have been around for 20 years. Things such as switching from YUM update to APT update are easy. People can usually change from one to another pretty quickly, but some of the other commands that you are used to running in Red Hat Enterprise Linux are slightly different for different versions of Unix. It did not make sense.

I have used a lot of different variants through the years. I could be running Raspberry Pi, or I could be using Ubuntu to do a job but not for the production environment. I do not waste my time anymore. I know what works and where support is.

Our setup is a bit of a hybrid. We are streamlining a lot of things and trying to redesign how we are doing things. In terms of the cloud, we are 100% TerraForm. We are building out infrastructure as a code and TerraForm pipelines. On-prem, we have a Jenkins job that runs some TerraForm, which then runs some Ansible and then some Puppet. There is some cleaning up needed there.

Currently, we use all three major cloud providers: Azure, Google Cloud, and AWS. Each has its purpose.

The initial experience of deploying it at the current company was terrible, but it was not a Red Hat issue. It was an internalized issue that took a little bit of time to work out. After that, it was not a problem.

We implement it on our own.

I have not run into a single person who knows about Red Hat Enterprise Linux and is not being helpful. You can get talking with somebody at Red Hat Summit about what you are doing on Red Hat Enterprise Linux, and they will be like, "I did that a couple of days ago. Did you run into this problem too?" There is a community. I am sure there are communities for other variants, but my return on investment is simply community and support. I cannot speak highly enough of these two.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say, "Good Luck!" We looked at a lot of different options to potentially leave Red Hat simply because of the cost. We tried out CentOS. We tried out Rocky. There were even talks about trying out Ubuntu, but there was the hassle of changing all of our mentality and code to work with different systems. It just did not make sense. CentOS worked almost side by side with Red Hat, but certain things that we have specialized with Red Hat were not working on CentOS for some reason.

We chose not to use CentOS because we had a misunderstanding of what AppStream was in terms of end-of-life for CentOS. Rocky was ruled out pretty quickly simply because of a lack of understanding in terms of:

• Where does Rocky come from?
• How reliable is it?
• Where is the support?
  

Red Hat's support model trumps a lot of those other ideas. I tell people that even if they are working in a home lab environment, get a developer license and get a developer account with Red Hat. Use Red Hat because more and more businesses I work with simply use Red Hat. It is great to have Fedora on your laptop as a workstation. It is great to have CentOS as a workstation. That is because those are still a part of Red Hat. You can transition and use Red Hat for a company. I have not been a fan of Ubuntu and some of the other variants because of how easy it is for people to make changes to operating systems that are not fully backed or tested. In my opinion, you do not want to put production on it.

Red Hat Enterprise Linux has not enabled us to centralize development. We are moving towards centralized development, but there are still so many different teams, so centralized development is not yet there.

We are partially using Red Hat Enterprise Linux for containerization projects. Within the next year, I hope to bring OpenShift in and replace AKS. I do not have a use case for the portability of applications and containers built on Red Hat Enterprise Linux. Based on what I have seen here at Red Hat Summit, I have a lot of ideas spinning around in my head to make it happen, but I do not yet have anything around containerization.

Red Hat Insights provides vulnerability alerts and targeted guidance, but we are currently not using that side of it. It helps in my limited sandbox environment, but of course, my sandbox is built up and torn down like crazy. It is valuable, but we do not have a great use case yet.

I would rate Red Hat Enterprise Linux a ten out of ten. I have been working with Unix systems for a while now. The first Unix system I touched was in 1992. There were so many variants that were striving to become well-known. You would hear all of these weird names. There were all of these weird animals and all of these different logos through the years. Even before 1992, there were a lot. As things progressed, you quickly saw different ones die out. I do not remember when I truly got onboarded with Red Hat. I know I started with version 4. It is one of those companies when you are looking for a name that sticks around and about which you do not have to question if they are going to be around for a while. You do not have to question that with Red Hat. You do not have to question that with Red Hat Enterprise Linux, whereas a lot of other variants do not even exist anymore, or they exist, but they have not been maintained longer than some people have been alive.

We run web apps. We run databases. We run a high-compute platform on Red Hat Enterprise Linux variants.

All of our customers run Red Hat Enterprise Linux. We run Red Hat Enterprise Linux for mesh nodes. For anything Linux, if we can use Red Hat Enterprise Linux because it is supported, we put it on Red Hat Enterprise Linux. Probably 60% to 80% of our infrastructure is Red Hat.

Having a stable Linux platform means I am not spending my time rebuilding Linux systems, constantly patching, and doing things like that. It helps to have an approved and supported platform. I know they have tested everything and when I patch my system, it is not going to blow up. It just does not happen. The other thing is that we have had catastrophic failures, and they have helped us out of these catastrophic failures. The support for Red Hat Enterprise Linux has always been good, and the community around Red Hat Enterprise Linux has been fantastic.

We were also CentOS users, so we have committed to AppStream as well. Being a part of the community has been a huge benefit for us. Community adoption means it is easy for people to find information. It helps new people get on boarded into Linux.

We mostly have an on-prem environment. VMware is a significant chunk. We do have some Red Hat clusters. We do have clustered applications, both physical and virtual, running on the cluster. We do have some cloud. We have our own internal cloud with VMware running behind the scenes. Having a consistent image means things always look the same. It is boring, but it is cookie-cutter. That is what we like. We like everything to come out the same. We have consistency and the ability to patch across our entire environment. We are also a Satellite user, so we are able to patch everything and maintain everything in a single pane of glass. It means I can have fewer admins administering many more machines. If you have a reduction in failure and an improvement in automation, things just work.

We have created what we call creator nodes. We have built a platform on Red Hat with Podman so that they can connect with Visual Studio code and do development or Ansible development. We now have our mainframe people developing automation with Linux with all of the plugins right there. It is a consistent environment for them, and that has been awesome. That has been fantastic. We have a few hiccups with Podman. They are working on the permissions to be able to have multiple people run Podman. They are working on the UID and GID problem that we had earlier. Right now, we are running Docker, but I am planning on moving to Podman once they fix that. We have also automated the build process for those nodes. If we need to scale up, we build a couple more VMs, and we are done.

We use Red Hat Enterprise Linux for containerization projects. We are containerizing applications. We are pulling the Windows container that we have and converting it to the Red Hat Enterprise Linux container. At the Red Hat Summit, the keynote about image RHEL with systemd blew my mind. It is a change from what we have been doing, but it should make a lot of things more reachable for us. It is cool because now my container image looks like my VM image. You cannot make it simpler for people to develop in a container. It looks the same. There is no difference. That is going to drive heavy adoption with us because if there is no difference, people are not going to have that fear of something new. It has 100% impacted our projects in a positive way. We have started to migrate all of our workloads to OpenShift now that we have got it in the door. It makes a lot of sense. I can redeploy. I can patch. I can do all this with code. I do not have to maintain a VM and a container. It makes life simple.

We have seen a drop in TCO because we ended up buying more than building. When you build something, there is the hidden cost of support, training, and the precarious position you get in if you deploy something you do not fully understand. We were there. We had five instances and a bunch of complexity. We reduced that down to one. We were able to simplify our complex nature. That is what Red Hat has allowed us to do. We have been able to roll out and we have been consistent. I have got machines out there that have been running for two or three years with no problems. They just patch them in the background. It just works.

I love systemd. They have made some significant improvements with the firewalld console. I do not use it that much, but I know it makes Linux reachable for people who are not normally Linux admins.

I just love the command line configuration. It makes that easy for me. Another thing is that when you combine that with Ansible, your life is simple. You can do a lot of your jobs without having to touch the system. That is my ideal.

I appreciate everything they have done. The systems are just bulletproof. We do not have problems with it. Support for file system differences and migrations has been solid.

There have been a few things that I have run into. They have significantly improved DNF and YUM, but there can be better communication around what is going on. A lot of it is related to communication. They are building solid products, and quite often, people do not find out about them until two or three years have passed. We still have not discovered everything in Red Hat Enterprise Linux 9. A lot of it is because we have not had the time, but it would be helpful to have a little bit more communication around it. Maybe that is on us to make sure that we stay updated with the community.

I have been using it since Red Hat Enterprise Linux 2.5. It has been around 20 years. I love Red Hat Enterprise Linux.

I would rate it a nine out of ten for stability. It is stable. It is fairly bulletproof. There are a lot more things that they are adding to make it better.

I have had no problems scaling up or scaling horizontally. I have had some very large Red Hat Enterprise Linux nodes with 254 gigs of memory and a big chunky Oracle database system. We have had no problems with them. We have not had any problems with running with multiple memory cluster nodes. We have had 100 gigs network, and we had no problems. We had a high-end SAN and a high-end network, and we had no issues.

They have good integrations, and they have not had too many problems with external SAN providers. They have been fairly consistent with keeping up with everybody else and keeping their drivers good.

They are probably one of the better ones in the industry. I can get a real answer, and I do not feel like people are breathing down my neck and saying, "I am going to close your ticket. I have not heard from you in 15 minutes." It has been a very positive experience. They have always helped us out when we have completely gone sideways.

They are very patient with the level of experience that a lot of people have. We have a significant number of junior admins who put in tickets that probably should not have been put in. They have been very patient. Overall, it has been a good and positive experience.

Positive

Before Red Hat Enterprise Linux, I was strictly using Solaris and AIX. I never used Ubuntu. It was just straight, big-frame Unix before I went to Linux. I did not change too many platforms.

We use Ansible to deploy Red Hat Enterprise Linux machines on VMware. That is 80% to 90% of our workload. For everything else, I have done PXE boot and kickstarts.

We are using a hybrid cloud. Our cloud providers are Azure and AWS. We work with both. The deployment on Azure and AWS was simple. We built Elasticsearch inside of Azure. It was a click-button deployment. We use TerraForm to deploy most of it, and then we have Ansible to do the rest.

I wanted to try to do more infrastructure as code, but it is hard to get traditional admins into that mindset, so it is always a mix. I deploy these servers for them with TerraForm, and then I pretend I never did, and they can do whatever with them. It then goes back into traditional life cycle management. Sometimes they delete them, and sometimes they forget about them. Satellite has helped us keep track of where everything is. It has helped us track our life cycles. It has been helpful for us.

We have used Red Hat consultants multiple times. They helped us set a few things up and clean up our pipelines. We have been very happy with our Red Hat consultants and our last deployment of OpenShift AAP. We loved their consultants. They were fantastic.

The biggest ROI that we have seen by using Red Hat Enterprise Linux is accessibility to information for frontline support people, midline support people, and developers. There is a ton of information, and there is a ton of community support.

For us, Red Hat Enterprise Linux is a consistent platform because if we are on a customer's Rocky machine, we already know Red Hat Enterprise Linux. We can deal with that. It is a skill set that is very broad across multiple platforms. That means we can apply what we have learned and what we have been trained in. While working with the Red Hat Enterprise Linux team, we have learned best practices, and we can apply those across the board. That partnership has helped us better our internal practices whether it is Red Hat Enterprise Linux or not. That is a positive. Satellite has also been a real positive for us because we can now manage all of our systems from a single pane of glass. That is what my frontline people have been asking for. They wanted one place to patch the systems, and now they can.

Our experience was incredibly positive because we started working with OpenShift before we were fully licensed. They knew we were going in that direction. The same thing happened with Red Hat Enterprise Linux. They knew we would buy tons of Red Hat Enterprise Linux, so they were a little bit more relaxed. We wanted a thousand licenses, and we could pick those up. We true up. Our license experience has been positive with the exception of having to deal with all of the broken-up accounts, which is as much our fault as anybody's.

My biggest complaint is that we have eight or ten different contracts. It is hard to keep track of what is on what and where we are getting the most value-add out of our benefits.

They are helping us solve that problem. We have reached out to our account executives. They will help us solve that problem. That is a huge step because that has been a problem for 15 years. It will help us consolidate and understand what we are spending across the board instead of seeing what we are spending in chunks.

OpenShift has come close to paying for itself in the first year and a half. That is an easy business case to make if you have the direct ability to show cost savings. We are getting cost savings, and we have the ability to show those cost savings. These are the two major benefits we have seen with AAP and Red Hat Enterprise Linux bits. That has been a positive for us. Red Hat Enterprise Linux AI and some of the other things they are starting to do are probably going to enable a lot of our developers to start taking advantage of them. Red Hat Enterprise Linux AI changes the belief that AI is out of reach for a normal developer.

We considered the idea of building this entire platform on Rocky as a free solution. It just was not cost-effective. There are hidden costs of patching and maintaining. They require care and feeding. We wanted cattle, not pets. We had a bunch of pets. Red Hat Enterprise Linux enabled us to get into that cattle methodology and mindset. Our mesh nodes are built on Red Hat Enterprise Linux 9. If my mesh node goes sideways, I do not care. I just delete the VM, redeploy it, and run my playbook. In 15 minutes, I am back up and running again. Why would I troubleshoot it? It takes time. I do not care about troubleshooting. It enables us to rinse and repeat a lot of our processes.

People turn off too many of the tools way too often. We have a lot of room for improvement as an organization to embrace SELinux. We are still working on that. That has a significant amount of value. We want to embrace the GPG sign code in AAP. I do not want anything but approved containers and code running on our platform and our customer's platform. They have enabled us to be incredibly secure, and we are yet to fully take advantage of those offerings. It is a goal, and we are going to get there.

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 Red Hat Enterprise Linux-based variants are the best in my opinion. If I have a choice, I will always go for CentOS, Fedora, Rocky, or something else that is Red Hat Enterprise Linux-based. If they were not going to go with Red Hat, I would probably tell them to go with CentOS but stay behind a little bit because they do not want to be at the bleeding edge of CentOS. That relationship kind of changed when they took it to AppStream instead of a more supportive platform.

I would rate Red Hat Enterprise Linux a nine out of ten. They keep doing well, and they keep getting better. As long as they stay on the same path, I do not see us not using Red Hat Enterprise Linux in the future. It has been consistent. Why would we change?