Red Hat Enterprise Linux specifically was a hard requirement for certain software that we wanted to utilize. In fact, purchasing Red Hat’s enterprise version was necessary to run AP. That was the primary objective.

Apart from that, the robust networking capabilities offered by Red Hat Enterprise Linux were highly valuable. They have numerous partnerships and dedicated efforts in low-latency technologies, which are particularly beneficial for trading firms. They possess extensive expertise in external tuning and similar aspects.

Overall, the reliability stands out the most for me. While the package selection might be somewhat restricted, it is highly integrated and cohesive.

I'm really excited about some of the developments happening in the workstations and the Fedora Silverblue space. There are advancements like rpm-ostree and the OCI container format, which enable deploying RHEL in new ways.

As we have numerous developer workstations, being able to deploy them in an image-based format is highly desirable. This would allow us to use the "toolbox" concept, where developers can choose any desired operating system within the toolbox. Some of our developers also work with Ubuntu and Oracle Linux. Having a consistent developer platform with full pseudo permissions and zero permissions within that container or toolbox would be beneficial.

Additionally, having an image that includes all the necessary software and provisioning it so that subsequent updates provide the updated image, would significantly enhance the developer experience. It would be great if teams could make modifications and changes to the image, like rebasing. I think it would be an awesome feature.

Let me provide an example of why this would be valuable for Red Hat Enterprise Linux Workstation. We recently switched from one security software application to another similar application on our workstations. We had to manually remove the unwanted software and install the new one. It was manageable for servers or edge devices, but for remote devices that are not always on the network or VPN, it became a cumbersome task to reach out to each device and remove and install the software. If we could update an image with the old software removed and the new software installed, and then allow users to update their image, it would simplify the process for everyone. Currently, it's possible with Red Hat Enterprise Linux for Edge, but it would be fantastic if this capability could be extended to Red Hat Enterprise Linux Workstation as well. That's what would be really cool.

The company has been using Red Hat Enterprise Linux for a significant period of time. As for myself, it's been around five years or so. I have also contributed to GNOME. About ten years ago, I was one of 12 individuals who wrote documentation for GNOME 3.

I don't think we are leveraging Red Hat Enterprise Linux on the cloud. Since we are primarily involved in trading, our infrastructure is predominantly on-premises, accounting for about 80%. We have our own data centers. While we do have some cloud workloads and our cloud presence is growing, it isn't a major focus in my role. I serve as the lead engineer for 700 developer workstations that run Linux. For parts that use Red Hat Enterprise Linux on the cloud, we are split between different cloud providers, AWS, Azure, and Google Cloud.

For the most part, we are using Red Hat Enterprise Linux 8, which we support alongside Ceph and a bit of AAP. Apart from that, there is still a significant amount of CentOS 7 in use as people are gradually transitioning away from it.

The stability is good. I would rate it a nine out of ten.

The scalability is impressive. I would rate it a nine out of ten.

The customer service and support were pretty good. We encountered an issue, and we involved some people for assistance. In retrospect, we should have engaged higher-level support sooner for that specific issue. Support can be challenging when you're dealing with Linux problems, especially in our environment where we have a lot of skilled engineers; it feels like we're already operating beyond the normal troubleshooting space. So having access to escalated help when we need it is valuable. The support fixed our problem.

Positive

The initial setup was complex because we were using a newer version of Red Hat Enterprise Linux for the server team's workloads. Normally, we go with Red Hat Enterprise Linux for hardware, but this time we got a better deal from a different vendor whose IPMI Redfish interface wasn't as advanced as Red Hat Enterprise Linux's. This caused some issues specifically related to deploying the newer version. However, once we managed to overcome most of those challenges, the use of Ansible for OS deployment became more straightforward.

For the OS component, we worked directly with Red Hat. However, we utilized a company called Bits, based in Elk Grove, Illinois, to handle the hardware provisioning and setup.

We've seen an ROI. For instance, we were able to run a storage workload on one cluster that had an immense capacity. I calculated it to be the equivalent of either 16,000 iPads or 64,000 iPads. It was a significant amount. This capability is beneficial for us as we deal with a lot of trading data. We can perform analytics and machine learning workloads on it, which aids in compliance and enables traders to make more informed trades. It's a win-win situation.

The compliance aspect ensures that we stay out of trouble, and the machine learning capabilities help traders make better trades, which ultimately contributes to our success. I'm glad that they make money. It's wonderful.

Red Hat is making efforts to simplify the SKU system, which is a positive development. It's beneficial to have the flexibility to allocate a certain budget to explore different licenses within the Red Hat ecosystem. We can try out products and decide if they meet our needs. If they don't, we can decommission the corresponding SKU. I have noticed that we have some Red Hat entitlements that we are not currently utilizing, so having granularity in the SKU structure would be an advantage.

For our specific use cases, certain products like SAP, AAP, and OpenShift require Red Hat Enterprise Linux. That played a significant role in our decision.

Red Hat Enterprise Linux’s built-in security features, in terms of simplifying risk reduction and maintaining compliance, are an area where I've observed some of the developments with Satellite and Red Hat Insights. But since we have different operating systems, such as Windows, Mac, Linux, and a mix of server and desktop environments, I'm not sure if Satellite or Insights can integrate seamlessly with all these platforms. Currently, we use a different product to assess our CVE vulnerabilities across hosts, including phones and other devices. I do find the discussions about software supply chain security intriguing. Focusing on that aspect seems really promising.

The portability of applications and containers, specifically for those already built on Red Hat Enterprise Linux, seems pretty good. Red Hat offers UBI images that are freely available without the need for licensing. Red Hat Enterprise Linux and container platforms provide a solid setup for portability.

Overall, I would rate the solution a ten out of ten.

We use Red Hat Enterprise Linux as an infrastructure support operating system across both x86 and s390 platforms. Specifically, we are running it on x86 Intel and Linux s390 mainframe on Zynq.

Red Hat Enterprise Linux is a stable operating system. We recently upgraded the majority of our systems from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8. We were able to automate most of the upgrade process and did not encounter any major issues. As a result, we were able to bring our systems up to date quickly and easily. This is a major advantage of using Red Hat Enterprise Linux.

From an automation standpoint, we have been able to automate some of our patching workflows. This has definitely saved us time and money.

From a security and compliance standpoint, it is easy to maintain compliance. This is mostly accomplished by patching Red Hat Enterprise Linux on a frequent basis. The availability of security patches is also quick, which allows us to keep up with our client requirements quickly. Red Hat usually does a good job of making fixes available in a timely fashion, so we can remediate high-priority issues when they arise.

From a containerization standpoint, Docker and Podman now give us the ability to move workloads and structures around with little effort. It is very flexible and consistent, and the results also provide us with a stepping stone as we move towards an orchestration platform like OpenShift. Our ability to run Podman on servers and then migrate those Podman deployments to OpenShift is very beneficial.

The most valuable features are ease of support and the ability to run a read-only course on the operating system.

Red Hat Enterprise Linux is easy to maintain. We currently use Red Hat Enterprise Linux 7 with Docker for containerization. With Red Hat Enterprise Linux 8, we are moving to Podman, which is a native container runtime that is part of the operating system. 

I suggest that Red Hat move to a continuous delivery model instead of major releases. I know that this is a trend for many middleware products. We do not have a major release network. We only have monthly or quarterly roll-on releases on our continuous delivery model, which reduces the impact of a major version. This would probably be the easiest change to make.

The technical support has room for improvement.

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

Red Hat Enterprise Linux is stable.

Since we run a number of hypervisors for all of our real systems, I believe that a lot of the scalability comes from a level higher than the operating system. However, Red Hat Enterprise Linux can accommodate these tools.

Red Hat support could be improved, and they should have a better relationship with IBM and VMware. This is because a lot of what we do involves working with IBM, both from a hardware standpoint and from a hypervisor standpoint. We have a long history with IBM, and we are now starting to work more with Red Hat on OpenShift private cloud solutions and other tooling. However, Red Hat and IBM are not on the same page. They are still very different companies, and they don't always know what the other one is doing. This can lead to contradictory information, inaccurate information, and frustration for customers. I think there is a relationship between Red Hat and IBM that could be improved. If Red Hat and IBM could work together more effectively, it would put customers at ease and make them more confident that they could get the work done. It would also help IBM and Red Hat to better understand each other's products and services, which would lead to better customer support.

For example, we recently had an incident that started as a severity two on the scaling. A number of our account representatives called and emailed us, saying, "Hey, we wanted to let you know that you have an open case. We need some help with this." The incident was not a production outage, but it was preventing us from doing something, so there was an indirect production impact. After about ninety minutes of back-and-forth communication, we were told, "Okay, go ahead and bump it up to severity one. That should get traction." We did not hear from anyone for four hours. This does not happen every time, but in this case, it needed to be dealt with well before four hours. It made things more difficult than they needed to be. Sometimes the support is an eight out of ten, and sometimes it is a four.

The end result was still good because they acknowledged what happened and got everyone together to resolve it but it was not done in an efficient way.

Neutral

The initial setup of Red Hat Enterprise Linux is very straightforward. It is not much different from any other Linux operating system. Most of the things we need to consider when deploying Linux are relatively standard. Therefore, Red Hat Enterprise Linux is easy to deploy and maintain. If we know how to administer Linux operationally, then Red Hat Enterprise Linux should be easy to deploy.

I do not know enough to give a comprehensive answer, but other operating systems are in use at my company because they have more favorable licensing terms. This is a major factor in why we do not use Red Hat Enterprise Linux everywhere.

We evaluated SUSE Linux Enterprise and a few others. Depending on the computing platform, it is sometimes better and sometimes not. For some of our environments that are running on s390, SUSE Linux Enterprise gives us a better price point. However, for some of our other environments, such as x86 on VMware, it is more valuable. It is a better financial move for us in those cases. Therefore, the value of SUSE Linux Enterprise changes depending on the computing architecture.

I give Red Hat Enterprise Linux a ten out of ten.

We have a requirement to have a Linux operating system.

I'm not sure how our developers are building their images. I believe they use some desk start products.

We use SUSE Linux Enterprise for Linux on the mainframe. In a particular enclave, we have some government contracts where we use Red Hat Enterprise Linux for a number of reasons, including licensing for hosts. These hosts are hosted with OpenShift. We use Red Hat Enterprise Linux for all our Bastion hosts and OLS for our other hosts.

The Red Hat knowledge base is generally an eight or nine out of ten, but it can be difficult to get the information we need. The initial level of support is a six or seven, but it improves as we escalate the issue.

We use the product to use the virtual servers.

Compared to Windows, the solution is much simpler. The product is easy to use.

The solution should provide demos so that users can learn to use it and improve their environments.

I have been using the solution for three to four years.

I have no complaints about the stability. It is good.

I have no complaints about the scalability.

We use the on-premises solution because we work for the government. We cannot use the cloud version because we have to maintain confidentiality. We are using versions six, seven, and eight. We also use Windows in our organization. Overall, I rate the solution a ten out of ten.