A lot of our Red Hat operating systems run middle-tier applications. We are mostly a JBoss shop, so they are homegrown applications. They are Java-based. We have several types of applications. We have identity, security, Oracle database, etc.

Red Hat Enterprise Linux helps with standardization. A lot of middle-tier applications hosted in the data center or in the cloud are unified in one standard operating system, which is Red Hat Enterprise Linux. On the data center side, we only have Red Hat Enterprise Linux. We have one unified operating system.

For our containerization projects, we are looking into OpenShift. Our Ansible Automation Platform executioner uses container-based Red Hat Enterprise Linux. We use Podman. We have moved to the Red Hat Podman container. It is a lot easier. We can scale up easily and manage it. It reduces the security risk. We do not have to worry about patching. We can just image a new container that is up to date. That is great.

We had a situation where we had to create an image for Red Hat Enterprise Linux 9, and there were built-in playbooks for hardening the system. We were able to run that and create the image. It made the work much easier than it used to be in the past.

Red Hat Insights provides vulnerability alerts and targeted guidance. It has that capability. It has a lot of features built in that not only help with security but also with misconfigurations. If a system is misconfigured, it detects that. It gives you the solution for the problem it captured. It is a great tool, but we have been focusing on the security perspective. We have not been focusing on operating system configurations. I have not yet looked at the new version, but in my opinion, it would be better if Red Hat puts a lot of focus on Insights and take it to the next level where the company could use it for its OS compliance.

We have all types of different versions running in our environment except the obsolete ones. We are moving towards versions 8 and 9. We have had version 7, and it has been very stable until now. It is ending this year around June 30, so we are in the process of moving to version 8, and we have just released an image for version 9. So far, version 8 has also been very stable.

It is a Linux-based operating system. It integrates with our automation base. We have Red Hat Satellite and Red Hat Ansible. All the engineers who are a part of our infrastructure or operation on the Unix side are Red Hat Enterprise Linux certified, so it is a lot easier for us to manage and integrate with the tools that we have. It makes much more sense from the middleware perspective and management too.

The bootup time for Red Hat Enterprise Linux running on physical hardware in the data center can be improved. We have seen cloud-based Red Hat Enterprise Linux, and it is instantaneous. You wait for a few seconds, and the operating system is up and running. It is a lot faster, whereas it takes a very long time when running Red Hat Enterprise Linux on physical hardware.

We used Red Hat Insights, but we are more focused on compliance, patching of operating systems, and things like that. In the past, when we looked at Red Hat Insights, it was its own platform, and then it migrated to Satellite. Companies are struggling to be compliant from the security side. Everyone is focused on how to patch the systems, what the environment looks like, whether they are under 90-day CVE, how their environment is compliant, and where they can see it as a dashboard. I wish Red Hat Insights was focused on that. From the Red Hat perspective, I am not seeing any sessions. I do not see anyone talking about that, which is a huge deal for us. I would like Red Hat Insights to go to the next level where it is focused on patching and compliance.

I do not have any other areas of improvement. It has been stable for us. There is a lot we do in terms of automation and integration. I know Red Hat 8 now has Podman for containers. Cockpit has a UI, so that is good now. That helps with certain things.

We have been using Red Hat Enterprise Linux for close to 20 years.

We have not run into something that caused a huge problem to our environment. If something is happening, such as it is running an Oracle database and that system has kernel panic or something like that, it is usually the database or application software running on the operating system. It is not the operating system itself.

We have not run into any major infrastructure incident costing us because of the operating system. They have it integrated with all other products such as OpenShift, OpenStack, etc.

We have three data centers at different geographical locations. Two are in the state of Georgia and one is in Las Vegas. In all three data centers that we manage, the compute-based are all Red Hat-based. 

We have a Red Hat TAM, and that helps a lot in terms of the problems and things that we run into. He is the interface with Red Hat. He escalates our service tickets and things like that. That is a huge help from our perspective.

The support that we get directly from putting tickets in has always been great. Red Hat Enterprise Linux is probably the best and most stable product that Red Hat has especially in regards to getting support and getting things fixed. They are on top of that. It has been a great experience. I would rate them a ten out of ten.

Positive

We used to run Sun Solaris. We were a Sun Solaris shop in the beginning. This was 15 or 20 years ago. We moved because of the Intel-based hardware, licensing, and cost reduction. Moving away from Sun SPARC hardware to Red Hat was a lot of saving. It saved a lot for the company. We can now run Linux-based systems on Intel commodity hardware using Dell.

Its usage is growing. Our team is working with other business units within the enterprise to get them onboarded to the Red Hat-based operating system. We have multiple entities that are running CentOS and Ubuntu. We have to have a standard operating system, and that is Red Hat. Our portfolio is increasing. We are growing and migrating a lot of nonstandard ones to Red Hat.

We have an enterprise technology group that utilizes Oracle Linux. We have worked with OEM. Our team is managing that too.

We are using Red Hat Enterprise Linux on-prem. We also have a cloud environment, but other teams are using it on the cloud. The cloud provider is AWS. The database team also uses Red Hat Enterprise Linux in AWS.

We use Red Hat Satellite and Ansible for Red Hat Enterprise Linux deployment across all three data centers.

My first deployment experience was almost 30 years ago. I started with Red Hat Enterprise Linux 4 or something like that back in 1993 or 1994. There has been a tremendous change in the way you install it and utilize it now. It is night and day. It has come a long way.

We implement it on our own.

Our costs are reduced. We can allocate that OpEx and focus on some other project. We do not have to struggle and say that this is how much we are going to pay licensing just on the operating system cost. We now have a model that works for us.

We are a huge VMware shop. Our licensing cost works well with Red Hat. We license based on the data center. The way our license works is that we can run as many Red Hat VMs as we want and pay for a single license. On the VMware side, we gain a lot, and it makes much more sense.

We did not evaluate other operating systems and compared them with Red Hat Enterprise Linux. We just went from Solaris to Red Hat.

We are an agile environment. We practice agile methodology. Anything we manage and deploy has to go through a sprint phase. We do not have a fully containerized environment. In the future, once we adopt OpenShift, it is going to increase our productivity because of how we manage things through agile. It is going to help us a lot.

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 it all comes down to the company and how a company foresees security. Anything we support and manage has to have a support base. If something gets impacted from the security side, we know that we have Red Hat support, and it is reliable. We can get the patch we want. If you install an application that needs a bug fix, you can reach out to Red Hat and open a ticket. If you want to have a stable environment, then I would highly recommend getting the support and running Red Hat.

Overall, I would rate Red Hat Enterprise Linux a ten out of ten.

I use the solution in my company mainly for the operation system of the core business applications.

My company has experienced benefits from the use of the product, especially considering the agility that the tool offers in terms of the time to market in different areas of business and because of its compatibility with most of the applications in the market.

The most valuable features of the solution are the stability and scalability.

I run Red Hat Enterprise Linux (RHEL) on a hybrid cloud deployment, and it has impacted our company's operations, but I would say that it has been quite simple to implement, especially considering the security, which has been a considerable piece of the infrastructure.

Red Hat Enterprise Linux (RHEL) has helped centralize development in our company. The applications run with Red Hat Enterprise Linux (RHEL), and it became the standard for the operating system for the applications.

My company uses Red Hat Enterprise Linux (RHEL) for containerization projects with OpenShift. This use of Red Hat Enterprise Linux (RHEL) has had an important impact on containerization, as it is a simple process. Owing to the simplicity, we always involve the solution's experts and get faster solutions.

The built-in features of Red Hat Enterprise Linux (RHEL) for risk reduction, business continuity, and maintaining compliance are very important because our company is always aware of all these security issues that constantly happen.

Though the product has many features, the tool's virtualization area has certain shortcomings that require improvement. The product should also offer more containers and probably some financial services.

I have been using Red Hat Enterprise Linux (RHEL) for five years.

It is a very stable solution.

It is a quite easily scalable solution.

The technical support for the solution is very good. I rate the technical support a nine out of ten.

Positive

Before Red Hat Enterprise Linux (RHEL), my company used to use Windows. My company started to use Red Hat Enterprise Linux (RHEL) after we found that it offers more stability, sophistication, and security and serves as a standard for many products.

The product's initial deployment phase was easy and quick.

My company did follow some strategy to deploy the product, and we also had the support from the vendor.

The solution is deployed on the cloud and on-premises models.

My company sought the help of a system integrator during the implementation phase of the solution.

In terms of ROI, I see that the tool offers stability, performance, agility, and resilience.

If I describe my experience with the product's price, I would say that we have to live with it for now.

My company evaluated other Linux products, such as SUSE Linux Enterprise Server (SLES), against Red Hat Enterprise Linux (RHEL).

I would recommend Red Hat Enterprise Linux (RHEL) to a colleague who is looking at open-source cloud-based operating systems for Linux since it is a tool with more market experience and offers more documentation and support from the vendor, which is not easy to acquire when it comes to open-source software.

Red Hat's portfolio has affected the total cost of ownership across our enterprise landscape by around 10 to 20 percent.

My company has the product in two data centers, but the production happens only in one. Mostly, my company uses the cloud services offered by Azure.

I rate the tool a nine or ten out of ten.

I use the solution in my company to deploy our custom apps or to set up servers for DevOps operations, like running containers and those kind of tasks.

The benefits associated with the product for my company stem from the enterprise support the solution offers. Based on the fact that our company has technical exchange meetings with the product's staff members, I can say that I have never seen something like that happening in a hands-on engagement with our company, so that is just great. Being able to talk to the solution team about our company's issues and problems related to the tool all the time is something that really helps a lot.

I can't say anything specific about the product's valuable features, but I would say that whenever I have questions, I feel the tool's documentation is on point since I can always find anything I need easily.

There are some points in the solution's documentation where a few areas seem generic. The aforementioned area consists of the same scenario when it comes to some of the other products, so it is not just applicable for Red Hat Enterprise Linux (RHEL) alone, but also for some of the other supported products. I have never had a problem with Red Hat Enterprise Linux (RHEL), as it is really easy to use.

I have been using Red Hat Enterprise Linux (RHEL) for five years.

It is a stable solution.

It is a scalable solution.

I believe that there are definitely some plans to increase the use of the solution in our company in the future.

I believe that there are definitely some plans to increase the use of the solution in our company in the future, especially if we start to get more customers and there is a need to ramp up automated testing since we would need more systems.

The solution's technical support is really good and responsive. I rate the technical support a ten out of ten.

Positive

I believe that my company used to use a few products before starting off with Red Hat Enterprise Linux (RHEL), but I believe that it was before I joined the organization.

The solution is deployed on the cloud and on-premises models.

In terms of the ROI, my experience using the solution revolves around the product's community. The fact that I can just go out and even in an ecosystem in general with tools like Fedora, CentOS, and other stuff, I can always find what I want with the help of the community where there are people with similar experiences, especially if it is not available in the documentation part. I feel Red Hat Enterprise Linux (RHEL) is community-focused, and I really appreciate that as a developer.

Running Red Hat Enterprise Linux (RHEL) on the foundation of a hybrid cloud deployment has impacted our company's operations and I can say that it has been easy because there is not much to do between the two environments, as it is consistent, and that just reduces a bunch of headaches.

Red Hat Enterprise Linux (RHEL) has helped me centralize development. The operating system that we are developing is based on Red Hat Enterprise Linux (RHEL). In our company, we are able to use everything in the solution with the help of documentation, support shared knowledge resources, and all of that. Just using the tool to support our company's infrastructure is really great, and now we don't have to branch out and use other technologies. The tool is a platform that supports many different things.

I use Red Hat Enterprise Linux (RHEL) for containerization projects in my company as it is easy to use.

When it comes to the built-in features of Red Hat Enterprise Linux (RHEL) for risk reduction, business continuity, and maintaining compliance, I can't really say anything much about it because the product is used in our company for a specific use case and we put ourselves on top, so we don't really use the aforementioned components for the policies.

In terms of how I would assess the portability of applications and containers built on Red Hat Enterprise Linux (RHEL) for keeping our organization agile and flexible, I would say that the offering of minimal images and all such stuff really helps cut it down and make deployments faster. In our company, we are really excited to use Red Hat Enterprise Linux (RHEL) to check the containerization of our apps, so being able to do such things for our products helps keep everything moving quickly. In general, my company is excited that Red Hat Enterprise Linux (RHEL) is moving towards the area to check the containerization of apps.

I would recommend Red Hat Enterprise Linux (RHEL) to a colleague who is looking at open-source cloud-based operating systems for Linux.

In terms of the deployment model used in my company for Red Hat Enterprise Linux (RHEL), I would say that the tool is basically deployed on-premises for closed environments and in the cloud because some of our company's customers prefer to deploy the product on the cloud. Mostly, my company uses the cloud services offered by AWS, while some of our company's customers use the services from Azure.

I like Red Hat Enterprise Linux (RHEL) considering the support that it offers to our company along with good documentation.

I rate the tool a ten out of ten.

When we are looking for Linux servers or developers need Linux, we have standardized around Red Hat Enterprise Linux. We do not use Ubuntu or any random flavors of the day. If it is a Linux deployment, it is Red Hat.

It helps with standardization. If someone comes to us and requests a Linux server, we have one product offering. We have a couple of different flavors of it, but people know what they are getting from us. The consistency, reproducibility, and standardization of it have been fantastic.

We are using Red Hat Enterprise Linux on-prem and on the cloud. We have it in Azure, VMware, and on-prem. We have it on bare metal. It is all over the place. Our operations are simpler, more efficient, and easier to handle. Our Linux team now supports one OS rather than a whole bunch of flavors that everyone has brought in. It has just made things more efficient and simplified.

Red Hat Enterprise Linux has enabled us to centralize development. Those developers are now developing on Red Hat Enterprise Linux. Previously, we had people who were developing on Ubuntu and trying to push Ubuntu to production, but we did not necessarily support it. Red Hat Enterprise Linux gave us a clear path to production. Our developers also get an easier experience. They know which OS to use and what they are using from day to day. There is less confusion for developers.

We are using Red Hat Enterprise Linux for containerization projects. It has helped with simplification. We do not have to create too many of our own custom container definitions and do our own thing. We use minimal images and whatever is provided is supported under our subscription. It simplifies things and puts guidelines around things.

Red Hat Enterprise Linux's built-in security features are good when it comes to risk reduction, business continuity, and maintaining compliance. We use Red Hat Satellite to manage our Linux. That makes it all very simple. There is a feature called OpenSCAP. We use it for security scanning. All the features that they provide on top of the base OS make it very easy to manage.

The portability of applications and containers built on Red Hat Enterprise Linux is great for keeping our organization agile. We know we can rely on that middle layer. We can start with the container and then build on top of that. Having a solid and standard foundation makes it all easy to do.

The enterprise aspect of it is valuable. There is security patching, security scanning, and compliance. There are all kinds of features around managing and keeping it up-to-date and secure. Everything is in a box for us from Red Hat which makes it very easy to manage them.

It is constantly improving. It is important to continue to improve. That is another reason I like it. They are using newer kernels, which gives us access to newer hardware. They are already doing that. I cannot pretend to tell them what to do better. They can just keep on doing what they are doing.

Personally, I have been using it for about 12 years. I have only been with my company for about four months, but I know they also have been using it for years.

It is stable.

It is scalable. They define scalability. I am a basic user. I just deploy more VMs if I need to. It is easy to do. Its scalability is great.

They are great. I would rate them a ten out of ten. A big selling point is that when you submit a support ticket, you know you are reaching out to experts. That is great, and that is one of the primary reasons we went with Red Hat.

Positive

In my company, they were using AWX for automation, and we moved them to AAP. For Linux, I was a part of a project to migrate some of the other operating systems over to Red Hat Enterprise Linux. I am on the tail end of the move or standardization to Red Hat Enterprise Linux.

There were a lot of Ubuntu operating systems in the environment, but they had challenges standardizing around it. There were different versions. There was also CentOS, but it was old CentOS. They are naturally moving that to Red Hat Enterprise Linux.

The support and the standardization around it were the main reasons for going for Red Hat Enterprise Linux. CentOS is more of a community thing now, whereas we can call Red Hat and they help us with everything. The support and the enterprise features we needed pointed at Red Hat Enterprise Linux rather than CentOS. It is a better choice for production.

We deploy them from AAP and then we deploy them into VMware. We deploy them into Azure, which is our main provider. We do that all orchestrated through Ansible and Satellite.

We have outsourced support. TCS is a general contractor, but for Red Hat deployments, we generally go with Red Hat Consulting. We just finished a consulting engagement with them for that. I know they have used them in the past prior to me being here. We generally just use Red Hat Consulting.

We have standardization. I know what I am walking into every day. I know there is support behind it. There is the support of Red Hat and the community behind it. I feel confident using Red Hat Enterprise Linux. I might use other Linux operating systems at home, but a lot of the time, there is no documentation for them. There might be three guys in a forum from ten years ago who may have talked about my problem. With Red Hat Enterprise Linux, when I am going to work, I know what I am walking into. I can feel safe and assured using something industry standard that works, and I can get help with it very easily. It makes life a lot easier.

Our total cost of ownership across our enterprise landscape has gone up because we were using a lot of mixed and free open-source solutions. However, there was an extra cost of operations and extra cost of hiring for specialized skills and things like that. With the Red Hat portfolio, I feel that we spend more on subscriptions, and we save in terms of efficiency and operations. I feel that we spent some money to save money on the backend, and I hope that is how it ended up.

I do node counts for the Red Hat Enterprise Linux system. I am gathering data for our decision-makers about how many nodes we need and how many things we need. Once or twice a year, they ask us to true up and find out how many nodes we are using and what the actual consumption is. I then report that, and then the account team usually works on the money part of it. I just work on the count.

We use Red Hat Insights a little bit. I am more of an Ansible guy, and we use Red Hat Insights for our licensing and a few other things. We have not been using Red Hat Insights as much as we wanted to. I know that on the Linux side, they are using it a lot for license count, monitoring, and other things.

I feel we are underutilizing Red Hat Insights. Our account executive has shown how it works and where it is, but we have not committed to it yet. That is coming soon. As we gain more Red Hat products and standardize more, we will have to rely on a single pane like that, so we will be using it more. I know that Red Hat Insights provides vulnerability alerts and targeted guidance, but we are not utilizing it right now.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say to go for whatever they find to be the best. My standard for an enterprise solution is Red Hat Enterprise Linux. It works very well, but they have to make sure that it fits their use case. Fortunately, Red Hat Enterprise Linux fits most use cases. They might end up there, but if there are licensing or cost restrictions, there are other free options, such as CentOS. The ecosystem of Red Hat Enterprise Linux is healthy, so I would recommend it, but if they want to use something else, they need to come up with all the standards around that.

I would rate Red Hat Enterprise Linux a ten out of ten. It is my preferred enterprise operating system. Everywhere I go, they are using it. It has been great. There are no complaints.

We use Red Hat Enterprise Linux for just about everything in my company. Our use cases stem from three-tier applications up through cloud deployments, Kubernetes, containers, etc. Prior to this, I worked in an enterprise as a Linux engineer.

Being able to onboard faster is definitely an advantage to other Linux systems. In the enterprise, we had an onshore and offshore model. Our offshore model was hard to get onboarded into Linux, even if they said they had Linux experience. There is a big difference between managing one or two systems in your basement to managing a fleet of Linux systems, and that does not always translate over. Having a Linux system that has a cockpit with it where you can give someone a GUI, even though the engineers do not really use it, helps onboard new people into the enterprise, into their jobs, and into their roles a lot faster.

We have a lot of really smart people. They are constantly figuring out ways to do things better and faster with Red Hat Enterprise Linux. The openness of it and the ability to create whatever we want to create or have to create to make our actual job easier has given our operations people more time to focus on the things they need to focus on, and not the nitty-gritty of the operating system. Tuning becomes super easy. It is scriptable. It is easy to automate. That gives them all the time back in their day to be able to go solve cool problems and not infrastructure problems.

Red Hat Enterprise Linux has enabled us to centralize development. All of our developers get their own developer environment, and that is all based on containers and some version of Red Hat Enterprise Linux. It depends on what they are at and what they are doing. So, we build and give it to them. They are up and running, and they just go. We have some legacy guys who are still helping our customers with older versions. Those people exist. I talked to someone earlier who still has a Red Hat Enterprise Linux 4 deployment out there.

When it comes to security and compliance, I like firewalld to do things at the host level and to complement what we are doing out in the enterprise with next-gen firewalls and things like that. I have had SELinux enabled on my systems and in my enterprises since it was available. It was a little bit of a learning curve, but it has helped to keep our systems as secure as possible. It complements well with what security groups are doing for the rest of the enterprise.

The portability of applications and containers built on Red Hat Enterprise Linux is great for keeping our organization agile. It is fantastic. We can run them on-prem. We can run them in the cloud. We can move them wherever we need them at the time. If something has to go to the edge for any reason, such as a bandwidth issue or an on-prem issue in the data center, we can push those workloads out. We could push all those containers to where they need to run and when we need to run them. It is super easy to do.

I have not used Red Hat Insights for long, but when I was a Red Hat Insights user, it was the first place I stopped to see what was going on and be able to quickly address and fix issues that Red Hat Insights found.

Red Hat Insights provided us with vulnerability alerts and targeted guidance. In terms of their effect on our uptime, we were able to plan our maintenance windows around what we were seeing in Red Hat Insights. We had the visibility and the ability to go in and plan things out. We could plan what needs to be done and then make that change and say, "This is what we are doing. Here is the playbook for it. We are going to run this in tonight's maintenance window." That prevented us from having to take machines down during the day because we found something critical at that time.

The features of Red Hat Enterprise Linux that are most valuable to me, both in the enterprise and now as a partner, are the enterprise features. We are able to have a Linux system that is open-source and that allows us to do domain trust IBM and all that fun stuff. We have a good solid enterprise Linux.

It is not broken. Linux is Linux. It has been since Torvalds created the kernel back in version one of the kernel. We have added more features. More things have come to Linux and kernel. All the AI stuff is a bunch of buzzwords. In the keynote today at the Red Hat summit, Chris Wright talked about lightspeed coming to Red Hat Enterprise Linux. What do we need that for? What are we doing with AI? Just the stability of it is fine. If anything cool comes out, I will be the first to check it out. It is a stable platform. It is a workhorse, and that is how we use it.

However, there should be training materials for new enterprises that do not cost an arm and a leg. Red Hat training is phenomenal, but it is expensive. There has to be a better way to onboard new engineers into Linux to really and truly compete with Microsoft. Microsoft is just easy. Everyone uses it. You have to use it in school, and you have to use it everywhere. From an onboarding perspective, we can improve and have an affordable training solution for someone who might not want to be an RHCE or an RHCA but still needs to do their job. It is not Linux's fault. It is what it is. It is a workhorse. It does its thing, but we can do better to enable customers to utilize Linux better.

I have been using it since Red Hat Enterprise Linux 4. It has been about 20 years.

It is super stable. When Red Hat comes out with lightspeed or integrates SELinux, there are no huge rollbacks. Once it makes it downstream in Red Hat Enterprise Linux, you know that is going to work. Everything has bugs, and we get that, but we know it is going to work. We know that nothing terrible is going to happen to our production environment, so stability is fantastic.

We can roll out more machines if we need more machines. We pull machines back if we do not need them anymore. One of the things that is lacking is that currently, there is no way to have ephemeral Linux instances for compliance month or your audit month. If you have to bring up a hundred machines, you have to pay for that upfront. That might be changing now, but in terms of scalability, that is a detriment to how smaller organizations can operate. Not everyone can absorb that cost. It is very scalable, but the pricing is a little prohibitive for scalability.

Their support is awesome. Their TAMs are awesome. The technical support that you get is awesome. There is the ability to attach yourself to bigger customers. When you are a small enterprise and you have an issue, you sometimes filter to the bottom of that list because there are other way-bigger customers who are way louder than some of the smaller ones. Being able to talk to your team and ask how to get a problem fixed is phenomenal. They are able to look at the backend and go, "Oh, there is a large telco that is having the same problem. I am going to add you to that one." From a customer service standpoint and tech support specifically, engineering has been fantastic.

The ability to talk to the people out in the community who work for Red Hat and maintain all of that, from the open-source side and the closed-source side, is amazing. A lot of people do not realize that they can jump on Slack or other platforms, and they can talk to the guys who are responsible for it and figure out what is going on. Sometimes, they ask to open a case, and other times, they say that they know and they are fixing it. Having that accessibility is amazing. You cannot call Microsoft and ask them to let you talk to the engineer who made X, Y, or Z.

Positive

I have been using Red Hat for 25 years.

We are using Red Hat Enterprise Linux everywhere. We are using it on-prem. We call it the fourth cloud, so we have our own cloud like every enterprise does. They might realize that or not. We are using it everywhere. We have it at the edge, in the cloud, on-prem, and hybrid. It is the whole nine yards.

Our deployment strategy is to make it work and get it out there fast. We use all three cloud providers: GCP, Azure, and AWS.

Its deployment is super easy. Once you know what you need, rolling out Red Hat Enterprise Linux is super simple. You just go and repeat until you need to change something and then you change it.

We are using OpenShift to deploy Linux containers for a virtualization competitor migration. We are using it to migrate workloads from that vendor to Red Hat Enterprise Linux, so we have Linux running in containers to do their virtualization. We are running Red Hat Enterprise Linux containers as well for some workloads, but for the bootable container aspects of it, we essentially have a VM. This is how we use it there, and then everything else is pure containerization. It is not Red Hat Enterprise Linux-specific.

We take care of the deployment for customers. 

When I was in the enterprise, we did not take external help. We did all of that in-house.

We have seen an ROI but not specifically with Red Hat Enterprise Linux. Red Hat Enterprise Linux is the workhorse. Everything else that supports Red Hat Enterprise Linux is where you get your ROI. When you take Ansible, you start automating all of your configurations. You take Insights, and you are getting those playbooks to remediate security issues and all that fun stuff. That is where you get a return on your investment. That is where you see your engineering dollars go down and they can focus on other aspects of the business. That is not specific to Red Hat Enterprise Linux. It is the whole ecosystem.

I have had sales folks who have been transparent with the pricing, and then I have had other ones who were not as great. Most of those ones that were not as great are not working for Red Hat anymore.

From a pricing perspective, there is supportability. What you get with that support is the ability to open a case before you do something. You can tell them that you are going to be upgrading your Satellite system or all Red Hat Enterprise Linux systems and that you need a case open. They open a case, and then when the day comes, they are there. They are ready, and they know what is going on. The price point for that is phenomenal because you are paying for support. From a pricing perspective, it is on point. It is definitely a value-add, and it is extremely transparent from a customer standpoint.

I have evaluated other solutions. Manageability is the main difference. I have successfully ripped out other solutions in enterprises that I went to and replaced them with Red Hat. They had large fleets and no centralized management. When you come to Red Hat Enterprise Linux, you have the Red Hat Satellite server. You have Red Hat Insights. You have all of those things that help you manage large fleets and a large number of Linux machines. When you evaluate other solutions, they have some centralized management now, but that was not common previously. It is kind of a hodgepodge. They are stitched together with all these other solutions, but it does not make sense. In one case, they jammed Linux into their management platform used to manage databases, and it did not work. How do you manage a thousand machines on some busted piece of management software?

If a colleague is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, they should go for something based on the use case. They have to look at what they are trying to do and what they want to do. They can get away with Fedora, for instance, but the question for me always comes down to supportability. Do they want to be able to call someone and say, "This is broken. Help. Hurry," or do they have the skills in-house to do that? Most companies do not have those skills. They have one or two very good engineers, but they cannot fix everything at the same time. If they want portability, then they should not look somewhere else. They should go to Red Hat Enterprise Linux because they have the Red Hat name behind it.

I would rate Red Hat Enterprise Linux an eight out of ten. There is always room for improvement in a product. Tens are unicorns. No one gets a ten. Maybe if Jesus made an operating system, he would get a ten.

We are mostly using it for application servers, infrastructure servers, and database servers.

Red Hat Enterprise Linux lends itself to a lot of automation. We are able to manage many more servers with less staff and by using other Red Hat products such as Ansible. Those are the things that I like.

We are using Red Hat Enterprise Linux for containerization projects. Their Podman product has made it easier. It comes with a lot of security. It is a drop-in product or replacement for Docker. I have used Docker before and switching to Podman was very easy. I just saw the demo for the Podman desktop, and I am looking forward to using that. It will hopefully help me streamline container usage and container deployment in Kubernetes or OpenShift.

It inherently has a lot of functions built in for risk reduction, business continuity, and maintaining compliance. For example, it has SELinux, certain firewalls, logging, and all those things. It has all the built-in features required to meet the needs. We can plug in other third-party tools to have it gather information, or we can send logs to centralized locations to track activity and do audits and things like that.

I use Red Hat Insights for different things. I do not use it much to look at security risks. I know that it has those features, but I use a different tool like a Satellite server to take care of patching and things like that. Red Hat Insights provides us with vulnerability alerts and targeted guidance, but it has not affected our uptime much. It is good to see that information. I can see those vulnerabilities, and I can see action steps or remediation steps that I can take. All my servers are patched on a cycle, so as the cycle goes through, each server gets patched based on its own cycle. It does not really affect the uptime.

I like the stability that comes with Red Hat. That has always been the feature that I like. They do not always have the newest features, but they prioritize stability, which is important in the production environment.

Red Hat should keep doing what they have always done. They should continue to be a leader in the open-source space. They should keep innovating and keep creating great products. They can allow more access to their training and their products' testing. There are ways to do it now. You might have to get a certain type of account to test their products. It might be easier if you can just download the product and test it out.

In a production environment, I have been using Red Hat Enterprise Linux for about five years. I have used Red Hat Enterprise Linux clones such as Fedora and CentOS for about 15 years or maybe longer.

It is absolutely stable. It is 100% stable.

It is good. It scales well. With the tools that Red Hat provides, it does not matter if you have 10 servers, 100 servers, or 1,000 servers. They make it simpler with Ansible. Ansible is your friend.

They are top-tier. Support is probably their number one selling point. As long as you give the Red Hat engineers what they need, they are very good at providing new solutions. I would rate them a ten out of ten.

Positive

I have used Red Hat clones in other positions. I might as well just say it is Red Hat because it is a clone, so I have been using Red Hat all along if we look at different products.

I have worked with CentOS, Rocky Linux, etc. The main difference is that Red Hat's support is top-tier. There is also stability. With the ecosystem that they have built, there are a lot of tools to help me manage. They have Ansible and other great tools to help manage the product. You cannot say the same about Windows. They might have a different way of doing things.

We have deployed Red Hat Enterprise Linux on-premises. We have a hybrid cloud environment, but we run other types of servers there. They are mostly Windows, and they are run on Azure cloud. We do not run Red Hat Enterprise Linux in a hybrid cloud environment, but there is always an opportunity to do that in the future.

The Red Hat servers that we have are on-prem. We use VMware and the tools that they provide to deploy Red Hat.

Its initial deployment was done a long time ago. It is a straightforward process to install it as long as you are not trying to do anything complicated.

We do not have a deployment strategy. We install it based on the requirements. If it is a web server or database server, there are different things that you need to do, but it is pretty straightforward. It is a good process.

We took help for deploying Red Hat and purchasing the license and maybe the hardware. We probably used CDW and Advizex. They are probably based in Pittsburgh.

Time savings is the biggest return on investment. I can do more in less or a shorter amount of time. The time savings depend on what you are working on, but you can potentially have about 75% time savings.

I have very little experience with pricing and getting quotes. The whole VMware thing happened, and everybody is looking at different alternatives. At this point, any competitor is probably a good choice based on the cost.

Everyone should evaluate what their needs are, test out different products, and pick the product that is best for their needs. I know that the Red Hat Enterprise Linux is a very good solid product. One thing I would say is that their support is top-tier, so from that aspect, I would recommend Red Hat.

At this time, I am trying to develop a platform that facilitates developer workflows. We may adopt more of a GitHub mindset and use Red Hat tools, such as OpenShift and Ansible.

We are currently not using containers as much as we would like to. We are working on setting standards. That is going to come down the road. Our workloads right now are mostly virtual machines and monolithic applications built on VMs. We will use them more. We will make more microservices and use pods to contain the applications. We will use more Red Hat tools.

Overall, I would rate Red Hat Enterprise Linux a nine out of ten. There are many things to take into account. From a production perspective, it is a ten out of ten. From the innovation and latest features perspective, it is probably a seven. That is not necessarily a bad thing because that is their unique point. They prioritize stability, but if you want something with your features, you can use Fedora.

We are doing image building. Our team focuses on the image of the platform and presenting it in a secure way for everybody to consume.

My organization had already been using it before I started, so I am not sure what benefits they got from Red Hat Enterprise Linux. They were already a Red Hat shop when I started.

We do not utilize Red Hat Insights as much as we would like, but we know that it is there. It provides the data, and we can act on that data, but we do not use Red Hat Insights the way we should. However, it does tell us when things are critical and need to be patched. If something is on there and it is critical, we can at least see that it is patched. The alerts and targeted guidance from Red Hat Insights have not affected our uptime so far.

It is open source. Most of the features are already there for you. They make solutions for challenges that we do not even think about sometimes, but we may consume them later.

I have not put in many feature requests. They have mainly been around small things such as monitoring with Ceph. I cannot remember the name, but monitoring was needed for a specific function. It was a pretty important function, but there was no monitoring set up. It took some extra effort. That was the only feature I asked for. I asked them if they could set up a monitor to make sure that the system was healthy or working correctly.

I have been using Red Hat Enterprise Linux for about five years. 

Its stability is fine. I have not seen too many issues with stability.

Its scalability is great. We can scale up or down.

I do not have any issues with the customer service or tech support. It is good. I would rate them a ten out of ten because they can usually resolve anything.

Positive

The deployment of Red Hat Enterprise Linux is pretty simple. There are not so many issues.

We are using it on the cloud and on-prem. We are trying to get to Azure. We are not using it in a hybrid cloud environment. I know we are setting up OpenShift in Azure and on-prem.

We have been using TerraForm to create images and Ansible to make sure everything is fine. We have some things on Azure, but we are trying to make it easier for people to consume Azure. We are trying to get that automation together so that it is a lot easier if anybody wants to spin anything up in Azure. They have a container to use that is secure. All of our business tools are on it.

We just use Red Hat. We do not use any integrator or consultant.

Our team does not use a lot of containerization, but we probably will be doing that soon with VMware changes. We are trying to get more of the monolithic stuff down to containerized workloads. We will hopefully see some return on investment after we get our VMware stuff out and get more things containerized. We are working with the OpenShift team, and we will be able to see some ROI.

That has been mostly handled by Red Hat. As we are a Red Hat shop, we have a lot of people around that already.

We do not use the security features of Red Hat Enterprise Linux. There are so many scanners out there. We do not use what is on Red Hat Enterprise Linux, but we do set it up. They are at least available to consume. We do not use them because we have so many security compliance tools. As a bank, we have to use those for auditing and other things like that.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say to get something that is close to Red Hat. Red Hat is killing a lot of the downstream stuff. All my Linux is Rocky Linux because it is based on Red Hat Enterprise Linux. I would suggest getting something that is close to Red Hat Enterprise Linux so that if they or their company does not want to go for Red Hat, they would still have the same tooling and the same infrastructure.

I would rate Red Hat Enterprise Linux a ten out of ten. I have not seen a lot of issues with Red Hat Enterprise Linux. I am overall satisfied with it.

We need to build a lockdown version of Red Hat Enterprise Linux to build our application on top.

It gives us a stable and secure platform on top of which we can build our applications.

We use Red Hat Enterprise Linux for containerization projects. It allows us to do better application isolation using containers. If I want to take a program that runs on my system and put it in its own network namespace, I can put it in a container. I can put a physical interface in with it and run them together in that container.

It definitely makes it easy to go back and look at all the Open CVEs and things like that.

It works well for us in terms of the portability of applications and containers for keeping our organization agile. We are able to do the kind of things we need to do. We are able to modify the system to do whatever we need to do to get where we want to go.

Things like packaging and the stability you get from things being downstream are valuable. A lot of times, upgrades are more security-based and not feature-based, so things do not break API-wise as we go forward a lot of times.

I feel like it is going all over the place now. Sometimes it is hard to figure out what is going on. I would like more guidance.

We definitely spend a lot of time developing on top of things, but I am not sure what on the Red Hat Enterprise Linux side can be better.

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

It is very stable.

It is very scalable. I would rate it a ten out of ten for scalability.

It has been great when we needed it. We have not needed a lot of it, but we have had no problems when we needed it. 

Positive

We did not use a similar solution previously. We have only been using Red Hat Enterprise Linux.

We use it on-premises. We use the ISO installer. We install it via CD ROM on-site.

I was not involved in its initial deployment.

It is the guarantee that we are getting the updates that we could backport into the system and we have a stable system to build on.

We have been using Red Hat Enterprise Linux since I have been with the company. They might have evaluated other solutions before I joined.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would ask, "Why?" We plan to stick with Red Hat as far as we see in the future, and we have no plans to change.

Red Hat Enterprise Linux has not helped us to centralize development. It is not something we are looking to use it for.

We use Red Hat Insights very little. We work mostly in an offline environment. It is hard to use Red Hat Insights in an offline environment.

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

My company currently uses Red Hat Virtualization to host all our virtual machines, and then we install Red Hat Enterprise Linux (RHEL) for almost everything we do. My company only has 30 or 40 Windows Servers, while we have over 2,000 Red Hat Enterprise Linux (RHEL) machines. In my company, we use Red Hat Enterprise Linux (RHEL) for everything from provisioning systems to Speedtest Servers to whatever we need in the company.

I would like to say Red Hat Enterprise Linux (RHEL) is much more efficient than Windows, and my employees love the Linux command line. All in all, Linux is what my company has been using since the beginning, so it is imprinted in everyone working in the technology section of our organization.

All Red Hat Enterprise Linux (RHEL) features have been valuable.

Red Hat Enterprise Linux (RHEL) is a Linux system, and in our company, we could probably use different Linux systems. My company mainly uses Red Hat Enterprise Linux (RHEL) because of the kind of security and the patching delivered, including the backporting of patches, instead of actually having to do version upgrades. The product's valuable features include stability and security.

In my company, the solution has helped centralize development in most parts.

The use of the product for containerization projects is an area that my company has been dealing with lately. In our company, we are installing a lot of OpenShift clusters now and moving that way, but if they run on Red Hat Enterprise Linux (RHEL) or bare-bones or bare-metal OpenShift, the shift needs to be made.

In terms of the impact my company has experienced after making Red Hat Enterprise Linux (RHEL) a part of our containerization projects, I would say that a different team is handling the development parts for our company. Our company would be happy if the products we use were Red Hat Enterprise Linux (RHEL) or OpenShift. My company is very interested in Red Hat Enterprise Linux (RHEL), even if it will take many years for us to be completely over containers.

As per my assessment of the tool's built-in security features when it comes to areas like risk reduction, business continuity, and compliance, all of the aforementioned functionalities are the main reasons my company stayed with Red Hat Enterprise Linux (RHEL). My company prefers Red Hat Enterprise Linux (RHEL) because of its stability, patch management, and other features that make us feel more secure.

In terms of the portability of applications and containers built on Red Hat Enterprise Linux (RHEL) to keep our organization agile, I would say that my company has done a lot of automation, which helps us keep everything as flexible as we want. One of my team members told me that the product is super when it comes to everything related to automation. The tool allows you to be kind of flexible.

At the moment, I don't use Red Hat Insights even though we have looked at it in our company. In our company, we have put up Red Hat Insights, and we have it on the machines, but it's not that deep in use yet. I believe that Red Hat Insights will be more and more important since the security team wants to use it to get a better overview.

If I have to speak to a colleague who is looking at open-source cloud-based operating systems for Linux, I would say that everyone needs to make a choice when it is not something concerning our company since we are standardized with Red Hat Enterprise Linux (RHEL) or Red Hat products in our company. My colleagues will have to use Red Hat products if they work in my company.

Speaking of whether the Red Hat portfolio has affected our total cost of ownership across our enterprise landscape, I would say that we have been using virtualization in Red Hat Enterprise Linux (RHEL) for many years, and it has been a very good and cost-effective tool for our company. The product may reach the end of the life phase soon, so we have to migrate to some other solution, though we know that the prices may go up whenever we do it. Up until now, the tool has been very good.

My company deploys Red Hat Enterprise Linux (RHEL) from Red Hat Satellite. Red Hat CloudForm is a self-service portal we use in our company but now it is an IBM product. I don't remember the name as it is long and boring. Red Hat CloudForm is a self-service portal that is connected to Red Hat Satellite to provision the machines.

My manager role is the reason why I am not that deep into the technical part anymore. In my company, the IT team is happy with Red Hat Enterprise Linux (RHEL) since they don't have to use Windows.

Personally, I started using Red Hat Enterprise Linux (RHEL) around ten years ago. In my company, I have been using the tool for twenty years.

It is a stable solution.

The solution scales up perfectly fine, especially since everything is automated since we have a very small team of 10 people in our company managing everything, including 2,000 servers.

The product's support team was good whenever my company needed support services. Our company also uses some professional services from time to time, especially since Red Hat has a deep knowledge of the tool. If our company faces a problem, we have a very good connection with the tool's team in Norway, and they always help us, even if it's time-critical. The tool's support team manages to get us the consultants our company needs. I rate the technical support a ten out of ten.

Positive

My company has been using Red Hat Enterprise Linux (RHEL) from the beginning.

When I started in the company almost ten years ago, deployment of Red Hat Enterprise Linux (RHEL) was done with an ISO image, which you mount it up, and you put in the IP addresses and do a lot of manual things. It is a different story today since you just enter how many courses you want and how much disk you want, and the deployment is done in two minutes.

The solution is deployed on an on-premises model, and we don't have a lot in the cloud at the moment in our company. As an ISP, the services we deliver are kind of time-sensitive or latency-sensitive, so as long as we have a data center, it doesn't make that much sense to put stuff in the cloud just because it is the best.

In terms of the prices and license of the product, I feel the solution has been good so far, especially since it has been quite easy to understand compared to a lot of other tools. I have been working with IBM and other vendors, where I have seen how other tools might have a bit more difficult pricing or licensing models compared to Red Hat Enterprise Linux (RHEL). In terms of pricing, Red Hat Enterprise Linux (RHEL) has been quite okay in general.

Red Hat Enterprise Linux (RHEL) was present ten years ago before I joined my current company, so I don't know if any other products were evaluated against it before my joining.

We have a few applications that we have started developing in the cloud now managed by a different team, but I don't think they use Red Hat Enterprise Linux (RHEL) specifically.

I rate the tool a ten out of ten.

We have extensive contracts with Red Hat. We have it for the operating system. I manage the cloud deployment for GCP, and we have got Red Hat Satellite running in GCP. All of our VMs run on Red Hat Enterprise Linux in the cloud. On-prem, we are running Red Hat Enterprise Linux on our OpenShift cluster, and we have a supercomputer that has got 753 nodes with 50,000 cores running on Red Hat Enterprise Linux. We use a lot of the other products too.

There is consistency across the deployment. Generally, when you are looking to hire people, if you hire people who know Red Hat Enterprise Linux, they have a certain level of understanding that goes along with using the operating system.

It is easy to secure. It has a lot of built-in security features, and it is very stable, which is a big deal.

It makes it easier to have one team that deals with both on-prem and cloud because there is a uniform operating system and tooling. You do not have to have a set of admins where one knows one thing and the other one knows another.

Red Hat Enterprise Linux has enabled us to centralize development. We are using the same platform everywhere. It is the same tooling, and everyone is working in the same system.

We are using Red Hat Enterprise Linux for containerization projects. We are building out OpenShift on-prem right now on bare metal. We are running the hub cluster from GCP to spin up the bare metal cluster on-prem. We will hopefully be moving more and more things towards containerized workflows. We are running OpenShift, so it all runs on top of Red Hat Enterprise Linux.

For security, SELinux is built in. It is out of the box. It is built towards building a secure system. We are in the process of working on compliance and getting this 800-171 certified. That is in process. They have regular security updates and lots of tools for rolling out updates. In that sense, there is a continuous upgrade path that is well-worn and fairly easy to maintain.

In terms of portability of applications and containers built on Red Hat Enterprise Linux for keeping our organization agile, when it is in a container, it does not matter if you are running a UBI container or some other sort of container. If you have an environment that will run a container, you can throw a container in it, and it will run, so the portability does not belong to the OS at that point. It belongs to the containerization system.

It is consistent. It is geared toward security. I am used to it. I know only Red Hat Enterprise Linux. I do not know Ubuntu or any of the other flavors of Linux.

It is good. I do not have anything to improve for Red Hat Enterprise Linux, but CentOS could be open-source again.

I have been using Red Hat Enterprise Linux since 2014. I have been using Red Hat since 1.2. It was probably 1998.

It is very stable.

We have a cluster with 50,000 cores. It is pretty scalable.

Their customer service is good. We have a TAM. Our TAM is great. Without a TAM, it is hard to get new tickets through.

I have used many solutions. I have used many that predate Linux. For Linux, I have run Slackware, but that is just for fun. Professionally, it has all been Red Hat Enterprise Linux. 

Our deployment experience is good. For the things in the cloud, I use Satellite. I build images and deploy from images to the cloud. It is a mutable deployment chain rather than a standard upgrade path.

We deploy it in-house.

The vendor management takes care of that. 

We have an enterprise agreement. From our department's standpoint, everything gets rolled into the enterprise agreement, which is great because we never see it.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say, "Why would you look at something other than that?" I have built things on Fedora and Red Hat Enterprise Linux. I was out of the industry for a while, and I came back, and I focused on Red Hat Enterprise Linux because it pays better. There are more standardized jobs in the area if you know Red Hat Enterprise Linux. The certification that you get from Red Hat means something quite specific.

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