Red Hat Enterprise Linux for SAP with HA and Update Services

I use Red Hat Enterprise Linux (RHEL) , and we have a couple of customers using OpenShift, the Kubernetes  platform based on Red Hat, and also Red Hat Virtualization. My first contact with the Linux platform was with Red Hat.

The best features of Red Hat Enterprise Linux (RHEL)  are its stability and the RPM, Red Hat Package Manager, which is perfect. They also deliver Satellite, a platform for updates. It is a very robust, excellent platform.

For me, and for every Linux distribution, the most important security feature in Red Hat Enterprise Linux  (RHEL) is SELinux. Security is often misunderstood by others. SELinux is very important because it provides security for the kernel. Many people disable SELinux, but it is the most important and most misunderstood feature. People do not understand it. The updates and SELinux are very important to me. SELinux is very good, but it is complex, and I have seen many administrators disable it because instead of helping them, it causes trouble. For example, securing my NGINX  configuration is a pain. It is a very good security option, but I would say it is excellent only if one is an expert.

Red Hat Enterprise Linux  (RHEL) documentation is very good and very complete. Regardless of my opinion about the IBM acquisition, the documentation is excellent.

IBM committed two major mistakes with Red Hat. The first was destroying the CentOS  project, which was a fork of Red Hat. The second was limiting the use of free options and restricting hardware to support Red Hat on just some limited hardware. One can use the system for free, but the statement is not entirely true because it is limited to a couple of virtual processors and I do not remember if it was 24 or 16 GB of RAM. If one goes beyond that configuration, one has to pay, and IBM is IBM. Many companies were in trouble because from one day to the next, IBM said they would no longer support CentOS  and told them to move to another distribution. People had to migrate, and for that reason, there are Rocky Linux , AlmaLinux , and other Linux distributions that are trying to rise and taking advantage of that situation. Red Hat Enterprise Linux (RHEL) is just for corporate companies with money to waste on licensing.

Red Hat Enterprise Linux (RHEL) is very expensive. In the case of our customers, the couple of customers with OpenShift, they have enough money to license Red Hat. They bundle Red Hat with virtualization and OpenShift packages. However, it is not suitable for an SMB company. It is not payable or affordable. For me, it is very expensive.

I use Red Hat Enterprise Linux (RHEL) a lot, though I do not remember the exact frequency.

I have worked with Red Hat support, and it is very good because they have very good engineers. In Latin America, during my time, the support in Spanish was mostly provided by engineers from Argentina. In Colombia, I have worked with a couple of engineers from Colombia, and they were very good. I have not worked with support in English for Red Hat, only in Spanish with those engineers.

My first Red Hat Enterprise Linux (RHEL) certification, Red Hat Certified Engineer, was for version 6, which was approximately 12 to 15 years ago.

I have tried Red Hat Enterprise Linux (RHEL) Image Builder and System Roles, and it is pretty good.

I would rate the support at an eight out of ten. My overall rating for this product is ten out of ten.

The main use cases for Red Hat Enterprise Linux (RHEL)  at the bank involve internal applications, as we do a lot of internal applications not exposed to clients.

From my perspective, the best features of Red Hat Enterprise Linux (RHEL)  lie in its ease of use, especially compared to AIX, which has a lot of functionalities requiring extensive learning. It was easy for me to shift from AIX to Red Hat Enterprise Linux  (RHEL).

Red Hat Enterprise Linux  (RHEL) helps manage our hybrid cloud environment, but being a bank, we are highly regulated internally, so there is limited direct involvement with the cloud environment in Royal Bank cloud, which is Azure .

One area I see for improvement in Red Hat Enterprise Linux (RHEL) is in the documentation. I encountered some scarcity when looking for information regarding structure, commands, and administrative tasks.

I have dealt with Red Hat Enterprise Linux (RHEL) for around 10 years, even when it was not part of IBM.

My opinion of Red Hat Enterprise Linux (RHEL)'s scalability is that it was very easy.

I would rate Red Hat's customer service or technical support as a 10, as my experience with all IBM products, including Red Hat Enterprise Linux (RHEL), has been very satisfactory all the time.

The initial setup of Red Hat Enterprise Linux (RHEL) is straightforward compared to AIX, which is more convoluted.

I have experience with platforms like Linux, and I am also working deeply with MongoDB and Node.js, tools that I use constantly every single day.

I am familiar with Red Hat Enterprise Linux (RHEL), and here in RBC, we are a big IBM shop, currently using JBoss and Red Hat Enterprise Linux (RHEL) as part of our environment.

Red Hat Enterprise Linux (RHEL) is used for both cloud-based solutions and on-premises.

From a business value perspective, the business folks do not notice much difference between Red Hat Enterprise Linux (RHEL) and other distributions, as long as their application functions well, they are satisfied.

We utilize two cloud providers for Red Hat Enterprise Linux (RHEL) solutions, mainly Azure  and also Amazon. I cannot answer how Red Hat Enterprise Linux (RHEL) was purchased, but I know we have it on both Amazon and Azure.

I would rate Red Hat Enterprise Linux (RHEL) a nine, as I find it satisfactory in various aspects.

Red Hat Enterprise Linux (RHEL)  is used primarily to build AWS  servers. A specific example of how RHEL  is used to build AWS  servers involves purchasing licenses from third-party vendors like REL and also from AWS. Once an AMI is obtained from the Marketplace, the AMI is customized by injecting all organization standards.

After internal tools have been built on the AMI, that AMI is used to build AWS servers.

Red Hat Enterprise Linux  (RHEL) has positively impacted the organization by helping track everything, such as how many users have access to the server, which is easy to monitor. RHEL also offers better options for downloading repositories easily, and the ability to stripe the EBS volumes has allowed for pulling more IOPS and throughput.

The impact on the team and organization has been significant, as it has helped improve application performance and backup performance. Since AWS backend is used for backups, RHEL striping has proven very useful.

By using RHEL striping, throughput and IOPS have increased, which reduced the backup completion time from fifteen to sixteen hours to just fifteen to sixteen minutes. The main reason is the backend and the striping implemented for EC2  instances.

Red Hat Enterprise Linux  (RHEL) offers several valuable features, including being secure and standard, and making whatever commands are executed easier to manage. When security and standardization are considered, no other person can access those RHEL servers.

Another good aspect is that whatever is downloaded comes from the repository, and every command is tracked, including the person who entered the command. Tracking on RHEL AMIs and OS standardization is very effective.

Red Hat Enterprise Linux (RHEL) helps mitigate downtime and lower risks by using the Pacemaker role for high availability. The primary and secondary systems are managed by the Pacemaker role, which helps reduce downtime for applications.

Red Hat Enterprise Linux (RHEL) could be improved by including a better app stream module experience or simply phasing out modules in favor of straightforward version repos. Red Hat could also integrate more common tools directly or integrate EPEL more seamlessly. Additionally, enabling AI-based operational tuning for kernel parameters, file system parameters, and network stack optimization could enhance the experience.

Regarding needed improvements, simplifying the subscription and licensing would help reduce complexity in subscription management. Clear visibility of consumption and unused subscriptions and compliance is also important.

Seven years of experience have been accumulated in the current field.

Red Hat Enterprise Linux (RHEL) is stable.

Red Hat Enterprise Linux (RHEL) offers great scalability and supports very large memory.

The customer support received is good.

Red Hat Enterprise Linux (RHEL) has been the only solution used, and no switch from any other solution has occurred.

In comparing the business value of RHEL to other Linux distributions, no other Linux distributions have been used; only Red Hat Enterprise Linux (RHEL) has been utilized.

Red Hat Enterprise Linux (RHEL) systems are managed with a dedicated cloud support team that handles provisioning and monthly patching. Additionally, focus is placed on security hardening and optimizing it with cloud-init, instance tuning, and subscription activation.

Image Builder has been used, but the AMIs are not built personally. A dedicated support team handles the building of the AMIs.

A return on investment has been seen, as it has saved a tremendous amount of time.

Red Hat Enterprise Linux (RHEL) helps save time; for example, the Pacemaker role facilitates faster task completion, and it optimizes backup processes.

Regarding pricing, setup cost, and licensing, the pricing is good; however, licensing is a bit confusing.

My advice for others looking into using Red Hat Enterprise Linux (RHEL) is to be aware that subscriptions can be challenging to manage. When a server reboots, the subscription goes to open, which can lead to others consuming the subscription, creating a challenge regarding the subscription and licensing part.

Security requirements were a significant consideration in choosing RHEL in the cloud because it is not open source and is highly secure.

Red Hat Enterprise Linux (RHEL) is assessed as having a better knowledge base offered through its tuning capabilities. By better tuning, the documentation is referred to, which helps in day-to-day work.

Red Hat Enterprise Linux (RHEL) entitlement management can be confusing, as converting systems between subscription modes is not straightforward.

I would rate this review a nine out of ten.

My main use cases for Red Hat Enterprise Linux (RHEL) are primarily our websites and applications that run on top of Red Hat Enterprise Linux (RHEL) operating system platform.

What I appreciate most about Red Hat Enterprise Linux (RHEL) is the SELinux policy that has been introduced; I believe that is truly good security, although it was difficult initially to become accustomed to it. In the modern world, you don't want every user to have accessible permissions. It gives you a granular level of control over each and every file and directory, just as ACLs used to provide in the past. By using SELinux policy, you can actually secure these accesses and establish a strong security posture.

The main business problem that Red Hat Enterprise Linux (RHEL) helped us solve is automation of tasks and scalability of the business. Red Hat Enterprise Linux (RHEL) has helped reduce downtime because in modern infrastructure, you do not face out of memory issues. Red Hat Enterprise Linux (RHEL) has affected the downtime by reducing it to a minimal level; the reboots are very speedy.

I think the support for Red Hat Enterprise Linux (RHEL) can be much better; when it comes to something such as SUSE Linux, I feel those providers are doing a much better job in terms of support than what Red Hat provides. One area where Red Hat Enterprise Linux (RHEL) stability could be improved is with Ksplice; Ksplice is used for online patching. The problem I have seen with it is that it applies patches at the user level, but not at the kernel level. That was a problem in terms of our security architecture because it doesn't recognize that the patch has been installed. I evaluate the customer service or tech support for Red Hat Enterprise Linux (RHEL) as needing improvement; addressing the tickets takes a little longer and there has been a lack of consistency. Not every engineer who handles a case handles it correctly. Everybody has a different way of handling the tickets. So, the support needs to be a little bit more streamlined.

I have been using Red Hat Enterprise Linux (RHEL) for the past three years.

My assessment of Red Hat Enterprise Linux (RHEL)'s stability and reliability once it is deployed in production and maintained is that it's straightforward, but there's a huge functionality and learning curve. We started using it and actually understood the reason why Red Hat has implemented it and the level of granularity in terms of security posture that it provides. We understood that it's doing a really good job.

I assess the stability, availability, and reliability of Red Hat Enterprise Linux (RHEL) as pretty stable and very reliable.

Red Hat Enterprise Linux (RHEL) has crashed or failed here and there, but there were some settings that needed to be changed. We make sure that we match those parameters.

Red Hat Enterprise Linux (RHEL) scales to my needs pretty much up-to-date.

The support from a competitor I've used is Oracle. My experience with Oracle support is that Oracle on-premises support, what it provides with Oracle Enterprise Linux, performs very well, and many of our customers believe that something from Oracle is more secure. When they compare Oracle with Red Hat, it has a much better support system and a much more secure posture than what we get.

I evaluate the customer service or tech support for Red Hat Enterprise Linux (RHEL) as needing improvement; addressing the tickets takes a little longer and there has been a lack of consistency. Not every engineer who handles a case handles it correctly. Everybody has a different way of handling the tickets. So, the support needs to be a little bit more streamlined.

My experience with the deployment of Red Hat Enterprise Linux (RHEL) has been smooth because back then we were on-premises and all our information used to be on-premises, rather than run them completely as we do now.

I have evaluated a couple of operating systems including Ubuntu, Oracle Linux, SUSE, and then came to Red Hat Enterprise Linux (RHEL) because Red Hat is considered the pioneer.

I have considered replacing Red Hat Enterprise Linux (RHEL) with another solution; specifically Oracle Linux.

If I were to switch, I would consider factors such as security and support.

We are currently considering using the Ansible Automation Platform for configuration and patching; we are using a manual approach and a little bit of Ansible here and there, but not fully deployed an Ansible Automation Platform or command line approach. But today I had the experience in the lab with the Ansible Automation Platform. That looks truly promising. I hope to get a chance to do a proof of concept and show my company that this is the product we can use in the future.

I have used the in-place upgrades to migrate machines to a newer release of Red Hat Enterprise Linux (RHEL); I used LEAP which has been designed to upgrade Linux 7 to Linux 8, and it was smooth. I think that was truly good work, especially because it supports you in situations where you do patching.

The upgrade process for Red Hat Enterprise Linux (RHEL) is straightforward and we didn't have any problems.

We are planning on upgrading from Red Hat Enterprise Linux (RHEL) 6 and 7 to 8, though we do have some legacy applications that would not support it. However, other systems which are web servers or Apache, we are trying to upgrade them.

I haven't found any limitations in Red Hat Enterprise Linux (RHEL)'s security.

My assessment of the documentation offered by Red Hat Enterprise Linux (RHEL) is that Red Hat's documentation is top notch. You cannot compare that with SUSE.

My specific goals that led me to choose Red Hat Enterprise Linux (RHEL) include the security posture.

Current, I am using the standard lifecycle support add-on for Red Hat Enterprise Linux (RHEL); I think we are still sticking with the standard and haven't upgraded yet.

The advice I would give to a team considering Red Hat Enterprise Linux (RHEL) is that one of the new features that it has is promising, and everybody promises great things with new features. My overall rating for Red Hat Enterprise Linux (RHEL) is nine out of ten.