How has it helped my organization?
We are a Linux shop, so a lot of our engineers are familiar with Linux. We try to push Red Hat Enterprise Linux instead of Windows. The reason for it in the beginning was licensing. Some of it was because of the way the contract was set up. It was cheaper, but we do use it now just for the ease of it. I do not know if it is because of Ansible, which we use for a lot of our day-to-day operations, that we tend to lean more toward Red Hat.
Red Hat Enterprise Linux has affected our system's uptime or security. I know Microsoft publishes zero-day vulnerabilities for Windows as fast as Red Hat, but we noticed that in terms of problems or alerts that we get for attacks or viruses, there is not anything on the Red Hat side. That is why we feel that it is more secure. It might be just the nature of Red Hat where all services and ports are off. It is not like Windows where everything is on, and you have to turn it on. I was having a conversation with one of the gentlemen who is also attending the Red Hat conference, and I got to know that there are built-in NIST features with Red Hat that we could turn on, so we do not have to try to figure out how to harden our system.
What is most valuable?
The testing of the updates or the packages of the kernel is valuable because I used to be a part of the Fedora project. I know it is all vetted out before it gets to production, but a majority of it is the support and the relationships I have with the Red Hat employees assigned to our account.
As they move over to newer versions, certain things change, which is expected as the technology matures or new things come out, but what really surprises me are the features that are there in the cloud, such as Red Hat Insights. They are not there on-prem. There are a lot of things on the cloud portal that I did not notice before, and I was surprised because we were unaware of them. Red Hat is doing a lot of investment in that sense.
The knowledge base offered by Red Hat Enterprise Linux is good. It is easy to parse through all of the knowledge base. I do not know if Windows does it because I have not looked at it, but in Red Hat's knowledge base, there are a lot of things. They fast-track a lot of things in their knowledge base, even when they are not yet official. Especially with the tie-in with Bugzilla, even though it is not a true KB, we can see and follow if other people in the world are hitting a certain problem or something similar to what we are experiencing. I like that.
What needs improvement?
It would be great to have an overview of how various Red Hat products work together. They can show how to tie all those pieces together and how to have the products that we work together for our day-to-day processes.
For how long have I used the solution?
I started with the company around 2012, and they have been using it even before then. At that time, it was Red Hat Enterprise Linux 5, and now, we are up to Red Hat Enterprise Linux 9.
How are customer service and support?
In 10 or 11 years of using Red Hat solutions, I have opened only one or two support tickets. It probably was something during a patch and during Satellite 5 to Satellite 6 migration. I would rate them a 10 out of 10.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
In Linux, there are so many different flavors, but I am partial to Red Hat because I have been a part of the Fedora project. At our place, we have only two operating systems: Microsoft Windows and Red Hat Enterprise Linux. I know CentOS, but that is usually because the appliance from the vendor was set up using that. That is why we had a few instances of CentOS in the past, but nowadays, I do not see any other flavors of Linux.
How was the initial setup?
For the majority of our use cases for Red Hat, we have on-prem deployments. There are some things that they are trying to spin up on AWS. I do not know if they are cloud-native apps or not, but I know our developers are now moving on to it.
I have been involved in the initial setup, upgrades, and migration of Red Hat Enterprise Linux. I did not have any problems while going from major OS versions. I always push new upgrades or homogeneous migrations, such as from version 6 to version 7 to version 8. There is probably an option to upgrade in place. Overall, with Red Hat OS, I have not seen many problems. A long time ago, when they went from Python 2 to Python 3, there were certain things we had to change in the script.
I know that Red Hat is moving to Wayland from X11, but I do not see any problems there. From Satellite 5 to 6, it was a bit hard in the beginning, but now, it is pretty self-explanatory. Overall, everything about which we had questions was very well documented.
In terms of our upgrade and/or migration plans to stay current, first, we look at the EOL and the roadmap of Red Hat because of security. We used to offer every single version before the said EOL happened, but now, we just do an n-minus-one. We try to maintain the newest and one level below version. SAP users are the biggest Red Hat Enterprise Linux users in our environment. They have a particular PAM and upgrade path that they have to do with Red Hat. We also wait to be certified to certain versions, but our main strategy is the newest and one major version down. We try to get everybody off the other versions.
Our provisioning is all done using VMware products. We have a vRealize automation, now called the Aria automation, to spin it up. Patching is done through Satellite. I do not do it, but when I watch them doing it, it seems it is just using remote SSH commands against the list of non-prod and prod servers. It is something simple. We do not seem to be doing anything complicated. I am wondering if there is a better way to do versioning control or patching and whatnot, but currently, it is very simple.
I am satisfied with the management experience not only in terms of patching but also the day zero to day one or day two stuff. We are interested in utilizing Ansible to eliminate human error and whatnot. During provisioning, we have Pearl scripts that we have to manually trigger. I know we can use Ansible for that, but it comes down to the cost of entry which is still very high.
What's my experience with pricing, setup cost, and licensing?
A lot of people are moving into the core count for licensing. We still have a few with one-to-one standard server licensing, but we are utilizing the virtualization host licensing. We license it based on the host, not based on VMs, which is cool. I was very happy that there was certain licensing with SAP to have access to SAP repos. Its cost was the same as the regular one, so I was happy about that.
The only pricing that bugs me right now is the Ansible pricing. We wanted to take a look at Ansible, but the biggest thing a year back with Ansible was that the management did not want to spend half a million on Ansible Tower. They wanted to see first if we would use it and not waste money. I do not know if things have changed now, but Ansible is probably still expensive. That is one of the routes that we want to go to. We will see if we can utilize Ansible Tower, so pricing-wise, that is the only thing that pops up. It is too expensive. The cost of entry seems quite high.
Overall, I do not see any issues with what we have spent on Red Hat. We also have learning subscriptions that we pay to Red Hat for the training, and I do not feel we have wasted any money.
What other advice do I have?
Red Hat Enterprise Linux has built-in features, but we do not use them. It is one of the things about which I need to talk to our account manager. There are so many different ways to skin a cat. My department has so much money, so they bought everything, but a lot of the security features, such as SELinux, are disabled for us. We handle the firewall rules, access lists, and other things at another location rather than on the actual VM itself. It does not hurt to do it at multiple places, but operations-wise, it would be a nightmare, so we try not to do it. I know there are a lot of cool new things built in Red Hat, and that is something we should circle back and take a look at.
I have seen Red Hat Insights. I clicked on it one time when our account manager was showing us something. They have so many features in the cloud that we do not know we can use. Maybe it is wrong to assume, but the reason I do not look at Red Hat Insights is that a part of our patching is already included. We are not that strict about what we patch in terms of the versions. It is useful, but Red Hat emails us anyway. They tell about the severity of an issue. We do not look at Red Hat Insights. We see those emails and we see CVEs. If a package is installed and applicable to our VMs, we just use Satellite and patch that particular vulnerability.
I have also tried the web console once. It looked interesting, but we do not have much use for it because a lot of our customers or application owners are server admins. About 99% of our Red Hat installs are all minimal installs. We do not have a GUI. There is just a terminal screen. Even though they could console in and do whatnot, it is all done via SSH.
Overall, I would rate Red Hat Enterprise Linux a 10 out of 10.
Disclosure: I am a real user, and this review is based on my own experience and opinions.