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.

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.

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.

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.