Red Hat Subscriptions

The main use cases were certifying our product with this OS platform, installing our product on this platform, and identifying the challenges we face, such as memory leak issues or OS-level issues, such as some libraries not being supportive, permission-related issues, or glitches due to different folder structures because the paths vary from Windows. Developers mostly keep Windows in mind as they have Windows laptops for the development environment.

Most of the time, we only certify our product with this OS. We perform most of the operations related to that only, leaving very little chance to explore features. However, as I read the news and newsletter from the Red Hat side, there are a good number of features, such as server editions, that can be really helpful.

System roles are helpful because we can achieve security through them. This is a good feature, as we can restrict permissions and policies with their help. 

When interacting with terminals, most of the errors can be a bit complicated for humans to read. If they used more user-friendly error messages, it would help people understand quickly. 

There are also a few changes needed at the library level. Some libraries supported by others, such as Oracle, are not supported by Red Hat Enterprise Linux (RHEL) . Especially in terms of Java, as now Java is with Oracle, if the Red Hat Enterprise Linux (RHEL)  system could align with those libraries, it would be helpful for end-users, eliminating the need to figure out which library is causing issues.

I have been working with Linux solutions for four to five years.

It is stable.

We create a ticket when we contact Red Hat support, but most of the time, we are able to find solutions through the community. The support is good from both Oracle and Red Hat. I would rate their support an eight out of ten.

I have tried Oracle Linux  and SUSE Linux, and we've explored different versions. It depends on the customer's requirement and whatever platform the customer is comfortable with; we have to certify our product with that.

There are multiple factors that led to our decision to move to Linux: pricing is one of the biggest factors, then security because Linux is more secure than Windows. Performance is another reason since malware programs do not run directly on Linux. Additionally, the command prompt is always faster than GUI mode.

When it comes to learning, it's all about perception because most people carry their perceptions from their college days. If someone is new or a fresher joining the industry, they have their own perceptions in mind. They often feel comfortable with Windows because most colleges provide Windows machines, but once they get hands-on experience with Linux systems, they start preferring Linux over Windows.

I haven't seen many complications with the initial setup of Red Hat Enterprise Linux  (RHEL) because whenever we provide a build or our product, we have a readme file with all the steps included. It's usually not that difficult. It's a couple of hours of work, and if any difficulties arise, it doesn't take long because we have a good community online to find solutions.

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

My use of Red Hat Enterprise Linux (RHEL) is for on-premise vertical solutions, but everything is on-premise. The main use cases for Red Hat Enterprise Linux (RHEL) include enterprise applications, such as databases and enterprise web applications, or security applications like WebSphere.

I find the most valuable aspect of Red Hat Enterprise Linux (RHEL) is its stability in working with other enterprise devices, such as firewalls and centralized storage. Enterprise applications and devices communicate well with RHEL, and it provides appropriate drivers for those enterprise devices. However, apart from that, I see almost the same performance with other open-source distributions like Ubuntu or Debian.

When assessing the knowledge base offered by Red Hat Enterprise Linux (RHEL), I find their documentation online to be excellent. I would rate the experience I have had with the documentation or knowledge base of Red Hat Enterprise Linux (RHEL) as excellent, giving it a ten out of ten. It is very good and useful for other Linux distributions as well.

The most important security feature in Red Hat Enterprise Linux (RHEL) is similar to that of other distributions, such as user creation and minimum privileges during the operating system's operation. In enterprise environments, I don't notice anything special in terms of security compared to others; it interacts very well with enterprise devices like firewalls and storage solutions.

RHEL has its own firewall, which is SE Linux, and I consider that to be a remarkable security feature. I have not tried Red Hat Insights; I don't know how to use that feature of Red Hat. Regarding the Image Builder or System Roles in Red Hat Enterprise Linux (RHEL), I haven't used them; I only use the ISO image directly for installation.

The solution has high pricing.

My overall usage of Red Hat Enterprise Linux (RHEL) has been uninterrupted. In total, it has been three years.

In terms of Red Hat support, I haven't used it, as everything I need to solve is in the documentation, which is very good.

Positive

I have previously used other solutions like Debian or Ubuntu.

I switched to Red Hat Enterprise Linux (RHEL) based on the direct requirements of the customer, not by my own decision.

The initial setup of Red Hat Enterprise Linux (RHEL) is straightforward; I find it very easy to set up.

My experience with the pricing, setup costs, and licensing of Red Hat Enterprise Linux (RHEL) indicates that this was the main topic that made me step away from RHEL. Personally, I don't see good benefits from their support and paid licensing compared to completely free and well-documented Linux distributions, as I find RHEL excessively expensive. Normally, the customer asks for a three-year licensing agreement for Red Hat Enterprise Linux (RHEL).

Overall, I would rate Red Hat Enterprise Linux (RHEL) as a nine technically, however, considering the cost, I would rate it a six, since it is very expensive. Combining technical and financial aspects, I give it a seven out of ten.

I was working on Azure  cloud migrations using Azure  Discovery tool and AWS  Endeavor tool. 

I worked with Red Hat Enterprise Linux (RHEL)  Azure discovery migration tool. I have worked on-premises for 16 years and on the cloud for four years.

I like that there is no downtime during operations. We work to mitigate downtime, but it typically ranges from two to three hours for upgrades and up to four hours for migration work.

Red Hat Enterprise Linux (RHEL)  now uses satellite servers, though we are not getting many materials or awareness about that aspect. Containers have also been implemented in Red Hat Enterprise Linux , but we need more materials and documentation for these features, based on my work experience. 

I have used Red Hat Enterprise Linux  in hybrid environments including physical, virtual, and cloud deployments.

Red Hat Enterprise Linux  is now integrated with RAN engineering, supporting telecom applications. Features such as Ansible  and container applications come built-in since RHEL 8.

I find information through seminar websites and seminar links. With satellite servers, I receive links through which I share and gain knowledge, including online resources, PDF materials, and Udemy courses.

For telecom products and technical platforms that support RAN engineering, we expect more features to be added to satellite, as it is currently quite complicated.

I have been working with Red Hat Enterprise Linux  (RHEL) for 16 to 17 years. The upgrades and materials have been consistently good.

Initial container deployment is difficult because the application matters more than the Red Hat Enterprise Linux (RHEL) server.

I would rate the scalability at eight out of ten.

Technical support from Red Hat Enterprise Linux (RHEL) has been very good.

Positive

The implementation took approximately six months because it was a RAN application.

Using the framework, I can upgrade directly from 7.9 to 8.1. I have completed upgrades for approximately 2,000 servers using Leap.

I perform server migrations, including physical to physical and physical to virtual transfers. I work on application upgrades and Red Hat Enterprise Linux (RHEL) server upgrades. 

I rate this product 8 out of 10. I expect more Ansible  features and container features in future releases.

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

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

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

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

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

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

The Asian support could use improvement.

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

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

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

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

Positive

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

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

The initial setup was very simple. 

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

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

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

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

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

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

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

I'm supporting a client in North America, specifically in Canada, where they are using Red Hat Enterprise Linux (RHEL)  servers in their retail business. They utilize it for back office software service, specifically a software called BOSS (Back Office Software Service). We are using Red Hat Enterprise Linux (RHEL)  on almost 1,200 servers, but this year, we have started migrating to Rocky from Red Hat Enterprise Linux  (RHEL).

Vulnerability management and patch releases are done on time. There are no delays, and we are not leaving our environment vulnerable, which minimizes risks.

Red Hat Enterprise Linux (RHEL) has helped us mitigate downtime and lower risk. With our current patching process using Kpatch, we frequently do not reboot the servers. We only reboot once a year during application downtime to upgrade to the next kernel level, while all security patches are applied live.

Some of the best features I noticed with Red Hat Enterprise Linux  (RHEL) include the LVM and the patching mechanism through the Satellite system. We do patching whenever there is a security vulnerability, and we are able to do it with the support of Red Hat Enterprise Linux (RHEL). For me these two big features, LVM and patching, are essential. 

If I can resolve an issue myself, that would be ideal, as it means I wouldn’t need to raise a case at all. The KB articles should contain all the necessary information for reference.

It would be great if they're able to reduce the price. It will be easier to convince customers to use Red Hat Enterprise Linux (RHEL) instead of open-source solutions. 

I have almost five years of experience with Red Hat Enterprise Linux (RHEL).

Scalability is fine; I don't have any challenges there. However, we are not using many of those features because our application is not ready to utilize them.

We use their knowledge base to find the solution.

I would rate the technical support with Red Hat Enterprise Linux (RHEL) a nine out of ten. 

Positive

The customer is moving to Rocky. It is not our decision; we still insist on Red Hat Enterprise Linux (RHEL) due to its security and additional features. The customer is moving away primarily for cost-cutting on licensing. 

Compared to other Linux distributions such as openSUSE, SUSE, or Rocky, I believe Red Hat Enterprise Linux (RHEL) offers better features. In Rocky, we don't have a live patching mechanism.

Deployments or migrations are quite easy for us since we have been working with Red Hat Enterprise Linux (RHEL) for the last five or six years. It feels like a piece of cake. Whether it's a minor or major version update or a migration, we don’t face any significant challenges. The process is smooth.

Initially, it took us two days to spin up a VM with all the requirements when on-prem. Now, the code is in GitLab . We have set up a code to build the servers, so after submitting a request in ServiceNow , it can be ready the next day. It is all automated.

It was on-prem, but last year, all of the servers were migrated to GCP.

There isn't much difference whether it's on-prem or on cloud, because the patching mechanism we follow through the Satellite system remains the same. From an admin's perspective, there isn't much difference between cloud and on-prem support.

As we lift and shift, our application is not cloud-ready or digital-ready, so we are still working in legacy mode. Therefore, we need to recode the entire application stack to make it compatible with cloud features.

If Red Hat Enterprise Linux (RHEL) can reduce its pricing, then it would be easier to convince others that there is not much difference between open-source solutions while still receiving several features for a licensing cost.

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