We run web apps. We run databases. We run a high-compute platform on Red Hat Enterprise Linux variants.

All of our customers run Red Hat Enterprise Linux. We run Red Hat Enterprise Linux for mesh nodes. For anything Linux, if we can use Red Hat Enterprise Linux because it is supported, we put it on Red Hat Enterprise Linux. Probably 60% to 80% of our infrastructure is Red Hat.

Having a stable Linux platform means I am not spending my time rebuilding Linux systems, constantly patching, and doing things like that. It helps to have an approved and supported platform. I know they have tested everything and when I patch my system, it is not going to blow up. It just does not happen. The other thing is that we have had catastrophic failures, and they have helped us out of these catastrophic failures. The support for Red Hat Enterprise Linux has always been good, and the community around Red Hat Enterprise Linux has been fantastic.

We were also CentOS users, so we have committed to AppStream as well. Being a part of the community has been a huge benefit for us. Community adoption means it is easy for people to find information. It helps new people get on boarded into Linux.

We mostly have an on-prem environment. VMware is a significant chunk. We do have some Red Hat clusters. We do have clustered applications, both physical and virtual, running on the cluster. We do have some cloud. We have our own internal cloud with VMware running behind the scenes. Having a consistent image means things always look the same. It is boring, but it is cookie-cutter. That is what we like. We like everything to come out the same. We have consistency and the ability to patch across our entire environment. We are also a Satellite user, so we are able to patch everything and maintain everything in a single pane of glass. It means I can have fewer admins administering many more machines. If you have a reduction in failure and an improvement in automation, things just work.

We have created what we call creator nodes. We have built a platform on Red Hat with Podman so that they can connect with Visual Studio code and do development or Ansible development. We now have our mainframe people developing automation with Linux with all of the plugins right there. It is a consistent environment for them, and that has been awesome. That has been fantastic. We have a few hiccups with Podman. They are working on the permissions to be able to have multiple people run Podman. They are working on the UID and GID problem that we had earlier. Right now, we are running Docker, but I am planning on moving to Podman once they fix that. We have also automated the build process for those nodes. If we need to scale up, we build a couple more VMs, and we are done.

We use Red Hat Enterprise Linux for containerization projects. We are containerizing applications. We are pulling the Windows container that we have and converting it to the Red Hat Enterprise Linux container. At the Red Hat Summit, the keynote about image RHEL with systemd blew my mind. It is a change from what we have been doing, but it should make a lot of things more reachable for us. It is cool because now my container image looks like my VM image. You cannot make it simpler for people to develop in a container. It looks the same. There is no difference. That is going to drive heavy adoption with us because if there is no difference, people are not going to have that fear of something new. It has 100% impacted our projects in a positive way. We have started to migrate all of our workloads to OpenShift now that we have got it in the door. It makes a lot of sense. I can redeploy. I can patch. I can do all this with code. I do not have to maintain a VM and a container. It makes life simple.

We have seen a drop in TCO because we ended up buying more than building. When you build something, there is the hidden cost of support, training, and the precarious position you get in if you deploy something you do not fully understand. We were there. We had five instances and a bunch of complexity. We reduced that down to one. We were able to simplify our complex nature. That is what Red Hat has allowed us to do. We have been able to roll out and we have been consistent. I have got machines out there that have been running for two or three years with no problems. They just patch them in the background. It just works.

I love systemd. They have made some significant improvements with the firewalld console. I do not use it that much, but I know it makes Linux reachable for people who are not normally Linux admins.

I just love the command line configuration. It makes that easy for me. Another thing is that when you combine that with Ansible, your life is simple. You can do a lot of your jobs without having to touch the system. That is my ideal.

I appreciate everything they have done. The systems are just bulletproof. We do not have problems with it. Support for file system differences and migrations has been solid.

There have been a few things that I have run into. They have significantly improved DNF and YUM, but there can be better communication around what is going on. A lot of it is related to communication. They are building solid products, and quite often, people do not find out about them until two or three years have passed. We still have not discovered everything in Red Hat Enterprise Linux 9. A lot of it is because we have not had the time, but it would be helpful to have a little bit more communication around it. Maybe that is on us to make sure that we stay updated with the community.

I have been using it since Red Hat Enterprise Linux 2.5. It has been around 20 years. I love Red Hat Enterprise Linux.

I would rate it a nine out of ten for stability. It is stable. It is fairly bulletproof. There are a lot more things that they are adding to make it better.

I have had no problems scaling up or scaling horizontally. I have had some very large Red Hat Enterprise Linux nodes with 254 gigs of memory and a big chunky Oracle database system. We have had no problems with them. We have not had any problems with running with multiple memory cluster nodes. We have had 100 gigs network, and we had no problems. We had a high-end SAN and a high-end network, and we had no issues.

They have good integrations, and they have not had too many problems with external SAN providers. They have been fairly consistent with keeping up with everybody else and keeping their drivers good.

They are probably one of the better ones in the industry. I can get a real answer, and I do not feel like people are breathing down my neck and saying, "I am going to close your ticket. I have not heard from you in 15 minutes." It has been a very positive experience. They have always helped us out when we have completely gone sideways.

They are very patient with the level of experience that a lot of people have. We have a significant number of junior admins who put in tickets that probably should not have been put in. They have been very patient. Overall, it has been a good and positive experience.

Before Red Hat Enterprise Linux, I was strictly using Solaris and AIX. I never used Ubuntu. It was just straight, big-frame Unix before I went to Linux. I did not change too many platforms.

We use Ansible to deploy Red Hat Enterprise Linux machines on VMware. That is 80% to 90% of our workload. For everything else, I have done PXE boot and kickstarts.

We are using a hybrid cloud. Our cloud providers are Azure and AWS. We work with both. The deployment on Azure and AWS was simple. We built Elasticsearch inside of Azure. It was a click-button deployment. We use TerraForm to deploy most of it, and then we have Ansible to do the rest.

I wanted to try to do more infrastructure as code, but it is hard to get traditional admins into that mindset, so it is always a mix. I deploy these servers for them with TerraForm, and then I pretend I never did, and they can do whatever with them. It then goes back into traditional life cycle management. Sometimes they delete them, and sometimes they forget about them. Satellite has helped us keep track of where everything is. It has helped us track our life cycles. It has been helpful for us.

We have used Red Hat consultants multiple times. They helped us set a few things up and clean up our pipelines. We have been very happy with our Red Hat consultants and our last deployment of OpenShift AAP. We loved their consultants. They were fantastic.

The biggest ROI that we have seen by using Red Hat Enterprise Linux is accessibility to information for frontline support people, midline support people, and developers. There is a ton of information, and there is a ton of community support.

For us, Red Hat Enterprise Linux is a consistent platform because if we are on a customer's Rocky machine, we already know Red Hat Enterprise Linux. We can deal with that. It is a skill set that is very broad across multiple platforms. That means we can apply what we have learned and what we have been trained in. While working with the Red Hat Enterprise Linux team, we have learned best practices, and we can apply those across the board. That partnership has helped us better our internal practices whether it is Red Hat Enterprise Linux or not. That is a positive. Satellite has also been a real positive for us because we can now manage all of our systems from a single pane of glass. That is what my frontline people have been asking for. They wanted one place to patch the systems, and now they can.

Our experience was incredibly positive because we started working with OpenShift before we were fully licensed. They knew we were going in that direction. The same thing happened with Red Hat Enterprise Linux. They knew we would buy tons of Red Hat Enterprise Linux, so they were a little bit more relaxed. We wanted a thousand licenses, and we could pick those up. We true up. Our license experience has been positive with the exception of having to deal with all of the broken-up accounts, which is as much our fault as anybody's.

My biggest complaint is that we have eight or ten different contracts. It is hard to keep track of what is on what and where we are getting the most value-add out of our benefits.

They are helping us solve that problem. We have reached out to our account executives. They will help us solve that problem. That is a huge step because that has been a problem for 15 years. It will help us consolidate and understand what we are spending across the board instead of seeing what we are spending in chunks.

OpenShift has come close to paying for itself in the first year and a half. That is an easy business case to make if you have the direct ability to show cost savings. We are getting cost savings, and we have the ability to show those cost savings. These are the two major benefits we have seen with AAP and Red Hat Enterprise Linux bits. That has been a positive for us. Red Hat Enterprise Linux AI and some of the other things they are starting to do are probably going to enable a lot of our developers to start taking advantage of them. Red Hat Enterprise Linux AI changes the belief that AI is out of reach for a normal developer.

We considered the idea of building this entire platform on Rocky as a free solution. It just was not cost-effective. There are hidden costs of patching and maintaining. They require care and feeding. We wanted cattle, not pets. We had a bunch of pets. Red Hat Enterprise Linux enabled us to get into that cattle methodology and mindset. Our mesh nodes are built on Red Hat Enterprise Linux 9. If my mesh node goes sideways, I do not care. I just delete the VM, redeploy it, and run my playbook. In 15 minutes, I am back up and running again. Why would I troubleshoot it? It takes time. I do not care about troubleshooting. It enables us to rinse and repeat a lot of our processes.

People turn off too many of the tools way too often. We have a lot of room for improvement as an organization to embrace SELinux. We are still working on that. That has a significant amount of value. We want to embrace the GPG sign code in AAP. I do not want anything but approved containers and code running on our platform and our customer's platform. They have enabled us to be incredibly secure, and we are yet to fully take advantage of those offerings. It is a goal, and we are going to get there.

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 Red Hat Enterprise Linux-based variants are the best in my opinion. If I have a choice, I will always go for CentOS, Fedora, Rocky, or something else that is Red Hat Enterprise Linux-based. If they were not going to go with Red Hat, I would probably tell them to go with CentOS but stay behind a little bit because they do not want to be at the bleeding edge of CentOS. That relationship kind of changed when they took it to AppStream instead of a more supportive platform.

I would rate Red Hat Enterprise Linux a nine out of ten. They keep doing well, and they keep getting better. As long as they stay on the same path, I do not see us not using Red Hat Enterprise Linux in the future. It has been consistent. Why would we change?

We are using Red Hat Enterprise Linux for running various things. We have a lot of virtual machines. The applications that are running on it are a bunch of shell scripts for processing orders, marketing campaigns, generating reports, or running some Java applications.

We have the customization capability. We can easily customize it, and we can also automate and deploy it. I have a command line interface. I am a command line junkie, and I am able to use that, config files, and Ansible to be able to easily figure out what I need to do to automate things. It feels like I know what it is doing and how to make it do what I want. I do not have to weave some magical arcane hack the way I have to do in Windows.

Red Hat Enterprise Linux has enabled us to centralize development in a lot of ways. We have it hooked in through our GitHub. We are trying to combine where we are storing things and then have a standard way of how we are deploying things and have some standard configurations. With every single server, we do not have to worry about how to set this up because we are doing the same thing the same way. We can just do it across the board, and then we only have to worry about the interesting parts.

Red Hat Enterprise Linux's built-in security features are great for risk reduction, business continuity, and maintaining compliance. There are published CVEs, and there is SELinux, which I do not use and I always turn it off. Firewalls and tooling around that make it easy to use. The automation on top of that makes it easy to configure. With a push of a button, it is done.

We do not have to worry too much about portability. We are coming from Oracle Linux. We were primarily an Oracle Linux shop, and because that is based on it, it just works. We have not had any issues.

The fact that it is Linux is valuable. Why I like it in general is that I know what it is doing. I can figure out what it is doing, and I can make it do what I want. I am not delving into arcane registry things.

I am still trying to figure out the features it has. There is so much that it can do. What it does really well is that it allows you to do things.

It was probably 2008 when I first started using it. The company was using Red Hat Enterprise Linux, and I was with the internal help desk supporting the Linux side.

Its stability is great. It is stable and rock-solid.

Its scalability is also great. It does not matter if the host is beefy or not. It is just going to run on it, and it is going to handle the work. Whether you have a couple of cores or 64 cores, it is just going to do it.

Their support is good. There is good responsiveness. They quickly get me to the person who knows the answer, but I have not used them much.

We were using Oracle Linux. We are switching because of some of the things. Oracle licensing has been a point of frustration. Their support is comparably difficult to work with, and the support documentation is a mess.

Red Hat is so much easier to navigate. It has been overall a much more pleasant experience to work with Red Hat.

We are using it on-prem, and then our cloud is a Kubernetes cluster on AWS, so it is basically on-prem.

Our deployment model is a manual kickstart with Ansible for configuration. My experience with deployment is good. I kickstart it and then hit it with Ansible, and it is done. It is very easy.

I did the deployment on my own.

We have not yet seen an ROI. It has not been in for long enough. There are no savings in terms of manhours because the actual day-to-day usage remains the same with Oracle Linux or Red Hat Enterprise Linux. However, getting some of the metrics with Red Hat Insights is going to be helpful as we get into a better patching cycle. I am anticipating an easier life.

We are expecting an overall decline in the costs because of the differences between the Red Hat licensing and Oracle licensing. We are expecting a net decrease in overall cost. For using it, other than the license, there is no cost.

The setup cost is non-existent. With licensing, there was a little snafu because I misread something. There was a slight learning curve because we use virtual data center licensing. We had to understand how it all maps. We had to understand how that mapping works when the hypervisors are Red Hat or VMware. There is a slight learning curve, but it worked out. It ends up being easy.

I did not evaluate other options mainly because I have had experience with it before. From my prior experience, I already knew what I wanted.

We are trying to use Red Hat Insights. I need to finish updating the playbooks to hook our host. We are in the midst of transitioning from Oracle Linux to Red Hat Enterprise Linux. I have not fully hooked everything in, but we will be using Red Hat Insights.

We just started using Red Hat Enterprise Linux for containerization projects. We have not yet seen any impact of Red Hat Enterprise Linux on containerization projects.

If a colleague is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, a lot of it would depend on their use case, what they are going to need for it, and whether they have an enterprise environment. There is a cost associated with it which can be a downside. I am an open-source lover. I do not like paying for stuff, but I get it. They need to look at the cost, and if the cost is prohibitive, they need to look at something that is compatible and as similar as possible.

Overall, I would rate Red Hat Enterprise Linux a nine out of ten. I generally do not give out a ten. There needs to be something spectacular for a ten, so that is my personal bias against the top of the scale.

We have Red Hat Enterprise Linux for our staging and development environments. We are using Red Hat Enterprise Linux for our production servers. It is the only Linux operating system that we are using in our company. I do not think we will change it. We will stay with it.

We started with CentOS, so it is quite similar. We have various features, and it is stable. The updates and upgrades are stable. This is the most important thing for my company. We are a gambling company. Reliability and performance are the most important for us. We like to press the update button and have an updated operating system after one, two, three, or five minutes. The most important thing about Red Hat Enterprise Linux is that it is a stable operating system.

We are using Red Hat Enterprise Linux for containerization projects. Red Hat Enterprise Linux and Docker daemons have been running for years without any problems. It is very stable. We are happy with it.

Every time we did an update or upgrade for the operating system or some dependencies, it worked well. It was very fast and stable. We are not afraid to press the button. We are happy with it.

The portability of applications and containers built on Red Hat Enterprise Linux keeps our organization agile. We are running some Docker applications. They are not our production applications. We are running some containers. It is very quite easy.

We use Red Hat Insights, and we are happy with Red Hat Insights in urgent situations due to security issues, noncompliant settings, or unpatched systems.

Red Hat Insights provides us with vulnerability alerts and targeted guidance. We have not had any problems.

It is a very stable operating system. We are not afraid to upgrade it.

If I want GUI, its GUI is better than other open-source operating systems. I prefer it for package management for sure. I am happy with it.

At the moment, I am happy with it. I cannot think of any areas for improvement. We have everything. The biggest challenge that we had was the migration from CentOS to Red Hat Enterprise Linux, but after some tests, it was easy.

We have been using Red Hat Enterprise Linux for almost two years.

It is stable.

It is scalable. We plan to increase its usage.

We are partners of Red Hat. We have support, so we are good.

We were using CentOS. The architect in my company chose Red Hat Enterprise Linux because we were already partners with Red Hat.

We are mostly on-prem. We are trying to migrate our applications to the cloud. We are using Azure Cloud.

The main data center that we have is in Ireland, but we are serving a lot of countries. We have small data centers for some countries. We have 2,000 VMs in Ireland, and we also have VMs in other countries. We have almost five data centers. We use Red Hat Enterprise Linux in all of them.

Migration from CentOS to Red Hat Enterprise Linux was a big challenge, but Red Hat had software to migrate and convert all CentOS VMs to Red Hat Enterprise Linux. It was an adventure in the beginning, but after some tests, it was easy. We migrated and converted almost 2,000 VMs in two to three months, and we had only ten cases where the migration failed, but it was our fault. We were happy.

For migration to Red Hat Enterprise Linux, we created a template and made the changes that we wanted. We ran some Ansible Playbooks, and we created the VMs.

We used a consultant from Red Hat the first time.

We did not evaluate other solutions.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would advise going for Red Hat Enterprise Linux because of support. There would be someone who already knows about your issue and can help you in a couple of hours. There is no need to spend time fixing the issue by yourself. Imagine running Ubuntu and having a production issue. You need someone to guide you.

Red Hat Enterprise Linux has not enabled us to centralize development. Our company is based on the .NET language. Our developers do not care about our infrastructure. They develop their applications, and we deploy them in OpenShift. We are using Red Hat Enterprise Linux for other services, such as MongoDB, Postgres, and our logging infrastructure. We use it for Elasticsearch, Graylog, and Docker services. Our applications do not run on Red Hat Enterprise Linux systems. They are running on CoreOS for OpenShift.

I would rate Red Hat Enterprise Linux a ten out of ten. It is stable. We are not afraid to upgrade it. We are happy to use it. This operating system is for us.

We mainly use RPM-based systems to give our developers virtual machines.

The most valuable features of using RHEL for us are the standard way to run Linux and tools like NetworkManager. They make things easier for us.

I prefer a product that offers everything in a yearly subscription, like VMware, and I think RHEL should consider offering it as well.

I have been using RHEL for 15 years.

The scalability of the solution is good.

We use RHEL deployed in different zones, only on-premise, not in the cloud. Deploying RHEL depends on the end user, but migrations aren't usually a problem due to site forwards. The hardest part is dealing with end-user applications on the machines. We use Ansible for scripting, especially with Oracle. Sometimes, meeting the end of life for RHEL versions is tough, and we have had to buy extended support for RHE because some applications reached the end of life within a year. I appreciate the extended support option, though I prefer not to use it.

RHEL's pricing and licensing are quite expensive. For a big company, paying these fees might be manageable, but as a government organization, spending tax money on such expensive solutions is challenging, even though we do have the funds.

I see benefits in using RHEL because it offers stability and long-term support. Although we use both RHEL and Ubuntu, I have noticed that updates in Ubuntu can change things unexpectedly within a main release, which I don't like. That is why I focus on RHEL for its consistent and reliable updates.

RHEL's built-in security features are very good for risk reduction, business continuity, and maintaining compliance. We apply security guidelines in Linux using RHEL, which provides all the necessary baselines. We can choose and apply what we need directly to our RHEL systems.

I would say that open-source cloud-based operating systems like Debian are stable and have been around for a long time. There is a whole community supporting it, making it a strong alternative to RHEL with fewer licensing costs.

Overall, I would rate RHEL as a nine out of ten.

We primarily use RHEL for data analysis servers supporting our scientific researchers, who access the systems remotely.

The reliability and long support lifespan of RHEL are crucial for us. It lasts for ten years, meaning we don't need frequent changes. Updates are quick, simple, and reliable, automatically backing out if issues arise, saving us from patching headaches.

I'm eager to see how the AI features in RHEL can enhance our capabilities. We hope it will improve tasks we have found challenging in the past, like documentation searches. We are particularly interested in automation and easily finding information.

I have been using RHEL for 15 years.

RHEL is scalable. We have scaled our data analysis clusters with it quite well.

I would rate the customer support as a nine out of ten.

Deploying RHEL for the first time was simple. It was a long time ago, and we had documentation from previous admins which made it straightforward. We did the deployment on our own.

We have seen ROI with RHEL. Our biggest investment is in professional development through Red Hat Summit, online training, and a Red Hat Learning subscription, which we have used for courses.

Our experience with RHEL pricing and setup costs has been good. We will be purchasing an extended license for another year.

We have used RHEL since I joined my company about 15 years ago. We have looked at other options like Fedora and Ubuntu for more up-to-date libraries, but we keep coming back to RHEL for its reliability and long-term support.

Using RHEL for containers has simplified our processes. While we, as system managers, aren't heavily involved in development, we provide RHEL containers for our developers. Overall, it has improved support for container management within our organization.

We rely on Linux for our web and file servers to ensure file integrity and service verification. Additionally, we use the host firewall regularly on all our hosts for enhanced security.

We started agile development and containers help us by making it easier for developers to teardown and recreate environments. This allows for more frequent updates, improving our workflow.

Our Red Hat portfolio reduced our cost of ownership by using RHEL Workstation instead of full server licenses where possible, saving money. We use full RHEL only on our enterprise production servers.

I would advise a colleague to check out Red Hat for its long-term support and reliability compared to other open-source Linux-based operating systems.

Overall, I would rate RHEL as a nine out of ten.

Red Hat Enterprise Linux (RHEL) is just a piece of an operating system for my company, and what we need the most is STIG compliance because we have a lot of different customers.

Red Hat Enterprise Linux (RHEL) has helped my company since, with it, we have gotten more customers. Now, our company can say upfront that we use Red Hat and are STIG compliant while also being security-focused, which really helps open up the door to people who want to get their stuff done.

The most valuable feature of the solution is its good integration with Ansible.

Red Hat Enterprise Linux has not helped centralize development in our company, especially since we deal with unique use cases in our organization. My company still develops locally on CentOS, but once our company actually completes the product for our customer, it gets shipped somewhere else and we can't centralize things since we don't have that much time to spare owing to which we stay disconnected after the aforementioned process.

My company plans to use the product for containerization projects, especially since we are in the process of converting to Kubernetes.

Based on my assessment of the the built-in security features when it comes to areas like risk reduction, business continuity, and compliance, I would say that I am a big fan of the tool.

In terms of the portability of applications and containers built on Red Hat Enterprise Linux (RHEL) to keep our organization agile, it has been pretty good since all the containers have been very portable without having to deal with any environmental issues.

If I had to give a suggestion to a colleague who is looking at open-source cloud-based operating systems for Linux instead of Red Hat Enterprise Linux (RHEL), I would say that one should look at AlmaLinux since it is the closest thing one can get to Red Hat.

The product's deployment model is usually in a single data center, and it consists of one machine at a time. Red Hat Enterprise Linux (RHEL) does not use a public cloud.

The documentation is an area of concern where improvements are required. Sometimes, I go to look at stuff in the tool's documentation to see how to configure something, and it doesn't make any sense. The tool's documentation is written by someone who already knows how it works for those who need to learn how it works. Everything else in the documentation is really good, though. I would describe the documentation as a kind of a hit or miss.

I have been using Red Hat Enterprise Linux (RHEL) for about six months.

It is a scalable solution.

I would like to expand the use of the product in the future, but our company's business model is contract-based and very slow, which makes it difficult to work with Red Hat Enterprise Linux (RHEL).

As per my evaluation of the technical support offered by the product, I would consider the support services offered to be at a 50-50 rate since everything really depends on who you get to talk to from the support team. Some of the people from the product's support team to whom we reached out didn't understand our use cases or our problems, so they couldn't help us at all. Some of the support staff members who understood what our company meant when it came to the issues associated with the product were able to help us in 30 seconds. My colleagues who contacted the product's support team were satisfied with the technical team's services. I rate the technical support a six out of ten.

In my company, we used to use CentOS. Now that CentOS has reached the end of life phase, it doesn't meet our company's needs, so we transitioned to Red Hat Enterprise Linux (RHEL).

Previously in my company, we used to use CentOS. CentOS will reach the end of life phase in the upcoming month, which is the reason why my company had to choose another product like Red Hat Enterprise Linux (RHEL).

The solution is used on an on-premises model.

Deploying Red Hat Enterprise Linux (RHEL) was surprisingly easy. The installers were the same as the ones used for other solutions.

My company did not have a strategy to deploy the product since we just needed Red Hat to hurry up, put it on a box, and figure it out.

My company did not seek the help of a third party to help us with the product's deployment phase.

The biggest ROI I have experienced from the use of the solution revolves around the area of customer satisfaction. My company's customers who use the product have a lot less to be changed in the product and it has helped save a lot of development and redevelopment time for our organization.

The cost and setup are not areas that are transparent for me. The tool's licensing part has been a real pain because when our company sells a system to a customer, they take full control of it in their data center, and we are not allowed to access it, even though they bought it from us. The license transfer has always been really awkward because our company initially had the license until our customers tested it and accepted the product. I was hoping to find somebody to talk to about the license transfer part with Red Hat products, but I don't know where to find someone associated with the solution.

My company briefly evaluated a product named Debian, but after that, our company's customers specifically asked us to go for Red Hat Enterprise Linux (RHEL).

Considering that the licensing part associated with the product is a pain, I rate the tool a seven out of ten.

Most of our infrastructure is made up of Linux servers. All of the apps that we have published are running on a Linux system. That is the main functionality.

I am responsible for Ansible for automation, and I am also responsible for our Satellite server, which is for patching and things like that. We use Red Hat Enterprise Linux a lot. We have 80% Red Hat Enterprise Linux and 20% Windows.

The benefits have been in terms of the speed and how the operating system does not interfere with apps that are running on it. That is the best aspect, at least from a business point of view. Databases run smoother, and so do the applications we have. There is no latency or issues like that.

We have a small number of servers up in the cloud in AWS, and then most of our servers are on-prem. We have a data server. Red Hat Enterprise Linux has made the deployment of servers smoother. We can do that pretty much with the click of a button, especially using AWS's platform.

For security and compliance, we have to be in sync with our security team. We cannot leave anything open. In Ansible, we have set up an actual configuration management playbook where it keeps all of our systems security compliant. It is really cool. Right now, we only have it working on our Dev and QA environments. We have not moved past that because we still have Chef. We are trying to get off of Chef completely. As of now, we are a hybrid. We have Chef and Ansible. Eventually, we will be completely Red Hat Ansible.

When it comes to keeping our organization agile, it is easy to decommission servers. Most of it is on VM, so we can just delete and then rebuild. If we accidentally delete a server, we can always bring it back because of backups and things like that. That is possible because of VMs. We do not have OpenShift, so I cannot say that Red Hat is the one that is keeping us agile.

The feature that I am enjoying right now is the actual LEAP program that they created for the actual in-place upgrades. I am upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8. We are in the process of that, so that is the best functionality right now. It never had that ability in the past. That addition has been an amazing aspect.

I am not too sure how it could be better. I have not yet used Red Hat Enterprise Linux 9, so I cannot say if there have been any changes or improvements. Honestly, I cannot see it getting any better. I like the way the operating system works now, and I do not really see any bad functionality with it.

The only thing I would say is getting rid of some aspects. That is the one part that a lot of admins probably get annoyed with. For example, we are now going to DNF from using YUM. At some point, YUM will be taken away completely, but right now, you can use both. There are those minor tweaks, and you just have to roll with the punches. Maybe it is just a better version of what was there prior. DNF is probably used at a simpler level, and it probably does not take up as much configuration and space as YUM. I am not sure exactly why they make those changes, but that is probably the only thing that is kind of annoying.

In my current company, we recently switched from CentOS to Red Hat Enterprise Linux. We are also working with CentOS. It has been around three years with this company, but I have been using Red Hat Enterprise Linux a lot longer. I am a Linux admin and I have been using it since 2006 or 2007.

It is definitely stable. We never have any issues. Everyone wants to blame the patching or some change in the OS, but it is never that. It is always the other side.

It has a lot of scalability. We have plans to increase its usage. We are in the process of getting off Oracle Linux, which is, again, another version of theirs, but we are going to be converting those over to Red Hat. All of our databases are going to be running on Red Hat.

It is awesome. I just upgraded my Satellite server. I moved from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 and then also upgraded to Satellite 6.14, which is almost the most recent version. I did that in the last month. Their support was awesome. I worked through what was said in the documentation on how to do the upgrade. I created my own spreadsheet for the upgrade and what I needed to do. I worked with their support. I had a meeting with them to check if it would work and if anything needs to be added or taken away. They worked with us that way. Their support is awesome.

We had CentOS. It is still based on Red Hat.

We are just now starting to use Podman. We were using Docker, and we are now moving over to Podman, which is the Red Hat Enterprise Linux-specific version of containers. It has been an easy transition. We do not necessarily work with Podman. Application owners are the ones who want us to install it, and then they utilize it the way they want to.

We have three data centers. We have a data center in the East in Pittsburgh, and then we have one in Arizona. We also have it in the cloud in AWS. Even there, there are two, so we have four data centers.

We do have a few Red Hat Enterprise Linux systems on the cloud. We are not sure if we are going into the cloud completely, but we do have some servers in the cloud. Our cloud provider is AWS. Our main app resides in the cloud. All the data, most of the data servers, and other applications are on prem.

I was involved in the deployment of Red Hat Enterprise Linux. We were the ones who converted it. It was very simple. Red Hat's technical person gave us the conversion script and tools. We just utilized that conversion script to switch from CentOS.

We did not use a consultant or an integrator. Red Hat gave us the tools, and we did it.

I do not know what the impact is financially because I am not in that department. For compliance, it has been helpful. Especially the banks have to be compliant in terms of being patched and things like that. Red Hat has been beneficial.

The biggest return on investment has been the ease. I have been a Linux admin for many years. I have used Solaris, AIX, CentOS, etc. I have always liked Red Hat Enterprise Linux better. It is just a better OS.

I do not know the overall cost, but I know that Red Hat is cheaper than Windows.

We did not evaluate any other solution. We were going to Red Hat Enterprise Linux.

We just switched from open source, which was CentOS, to Red Hat. My advice is to stick with Red Hat only because with open source, you do not get the updates at the same time. The updates come later for vulnerabilities and things like that. I would not recommend open source for an organization. If you are at home, you can go ahead and easily use CentOS. It is free, so why not use it? For an organization, Red Hat Enterprise Linux is better.

Currently, we are not using Red Hat Insights the way they are meant to be used. We are planning to do so at some point in the future. Currently, we only use it as a tool to make sure that it keeps track of all of our servers, whether we delete or add servers. Red Hat Insights keeps track of that and lets us know what version it is and things like that, but we do not utilize Red Hat Insights the way they are meant to be. Red Hat Insights provides vulnerability alerts and targeted guidance, but we use Nexpose for vulnerability scanning.

Red Hat Enterprise Linux has not yet enabled us to centralize development. That is because of the way the company is structured. Everything is fragmented. We have a separate networking team. We have a separate Linux team and we have a separate software team. Getting something done and centralized is pretty much impossible at this point. Any small tweaks are like pulling teeth at this point. I do not know if that is going to change. Hopefully, it will. We are planning on moving to OpenShift. I am hoping that it will make everything more centralized and it will bring the company to a less fragmented spot.

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

I use the solution to manage Atlassian applications. In our company, we initially deployed Atlassian applications on Red Hat Enterprise Linux (RHEL). For most of the products my company uses, we create Red Hat Enterprise Linux (RHEL)-based servers because we have Red Hat Satellite, so we just bring them up and make them supportive for us.

The most valuable benefit of the product for my organization revolves around standardization, which is why we have all the same types of machines and operating systems. It makes it very easy and familiar across the board. The tool is also very reliable.

My company does have a hybrid cloud environment. Running Red Hat Enterprise Linux (RHEL) as the foundation for the hybrid cloud deployment strangely impacted our operations. I think that when my company moved off from the tool's on-premises version for certain applications, we had to leave Red Hat Enterprise Linux (RHEL). Everything in my company is based on whatever AWS provides, specifically when Linux is on AWS, and I guess it negatively affected my company.

Red Hat Enterprise Linux (RHEL) has helped my company centralize developments because we know what we are going to use in the product, and so we don't have to make any decisions. Owing to the aforementioned area, I would say it offers a good standard.

In terms of the tool's built-in security features when it comes to risk reduction, business continuity, and maintaining compliance, I would say it is very easy to patch, which helps our company to keep it up to date and avoid all downfalls.

Speaking about the portability of applications and containers built on Red Hat Enterprise Linux (RHEL) to keep our organization agile, I would say that we don't tend to move that much with applications. The tool has helped to weave a path for an upgrade while creating a new application server, after which one can transfer it over. Considering the aforementioned details, the tool is portable. In short, whenever I try to use the product's portability feature, it does work.

The most valuable feature of the solution is that the upgrade in the patching area is really easy.

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

It is a stable solution.

It is a scalable solution since it is easy to make changes in the tool.

If the product is deployed on an on-premises model, it will be deployed on Red Hat Enterprise Linux (RHEL) system.

I haven't had a reason to use the support services of the product for a long time. I rate the technical support a ten out of ten.

In the past, my company used CentOS for a while. There were some other products which were also used in my company. My company started to use Red Hat Enterprise Linux (RHEL) as it provided standardization, and we required something nice and uniform in nature.

The product was already up and running when I joined the organization.

The solution is deployed on an on-premises model. If my company opts to have the product deployed on cloud, then we would opt for the cloud services offered by AWS.

I am sure my company did not seek help from many integrators, resellers, or consultants to deploy the product.

The biggest ROI I experienced using the product stemmed from the fact that it was really fast to deploy right from the beginning when we were building our company's new systems. The product works fine.

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 offers Red Hat Satellite, so everything is just so encapsulated and there in the tool.

I can't speak of whether the Red Hat portfolio has affected our total cost of ownership across our enterprise landscape since I don't know the cost.

I rate the tool a ten out of ten.

The use of the solution keeps varying, considering that we have web apps and a lot of homegrown stuff as we build a lot of our own apps. My company also uses Red Hat Enterprise Linux (RHEL) for the operating systems for a lot of our other applications that we use for authentication purposes and so on.

I can't really talk much about how the product has benefited the organization since it is not in my wheelhouse, and I mostly deal with the area of configuration management and the automation of configuring it. In my company, we have a Unix team I work with, and when they want to automate processes, then they come to me and I help direct them.

The solution's most valuable feature revolves around its simplicity, especially when maintaining it, which is an easy process.

I have not seen anything in Red Hat Enterprise Linux (RHEL) that causes any queries or doubts in my mind, so I am not really sure if I see any need for improvements in the product at this point, especially when I have good communication with the sales teams and support. I have also recommended the changes I want to see in Ansible, an area where my company sees progress. There is nothing my company is disappointed about regarding Red Hat Enterprise Linux (RHEL).

I would like to see a better way to organize the jobs within Ansible, specifically with the automation platform. Right now, in Red Hat Ansible Automation Platform, everything is just flat as there are no directory structures or folders and no ways to designate specific jobs for specific things as everything is in one big pile.

With Red Hat Enterprise Linux (RHEL), my company has not seen anything requiring improvements. My company is really happy with Red Hat Enterprise Linux (RHEL). My company is still in the migration process right now since, from all of our seven boxes, we are moving on to the eight and Red Hat Enterprise Linux (RHEL) 9. The aforementioned process has been really smooth and slick. My company likes the speed and simplicity of the OS.

I have been using Red Hat Enterprise Linux (RHEL) for twelve years. My company has been using the product since before I joined.

It is a stable solution.

It is a scalable solution.

I went to have dinner with my sales team the previous night, and we just had a chat, after which I got to know some professional services offered by some people willing to come and help our company with the solution if required. Based on the aforementioned area, I can rate support as ten out of ten.

My company has experience with AIX, Solaris, and Windows. My company switched over to Red Hat Enterprise Linux (RHEL) because people wanted it, specifically the app developers. My company uses Red Hat Enterprise Linux (RHEL) based on supply and demand factors. You just build what is needed for the infrastructure side or when you are in the operations.

The product's deployment phase was simple.

There is a different group in my company that has built up a strategy to deploy the product, so I don't have to do anything in its deployment phase. To request a new system is just a matter of filling out the ticket and submitting it easily, after which the box is built, which is great.

The solution is deployed on an on-premises model.

The deployment phase for the tool was carried out with the help of our company's in-house team. The product was deployed with the help of vRealize Orchestrator Appliance.

In terms of the ROI associated with the product, I would say that with a lot of stuff I do in the company, I also get involved with the patching side, especially the patching of servers. I can patch 1,500 Red Hat Enterprise Linux (RHEL) boxes in the time it takes me to patch ten boxes from Windows. Patching in Windows is bad. Being able to patch Red Hat Enterprise Linux (RHEL) is simple since I think the most I have ever seen it takes is around 35 minutes to patch a box. When our company started to move towards a more containerized approach, we saw that being able to have your container or your OS can open a whole new world. Being able to spin up systems and have multiple systems that are already pre-patched, I don't have to have downtime for the enterprise.

There were a couple of operating systems, including CentOS, which my company looked at before choosing Red Hat Enterprise Linux (RHEL) as it offered a strong support model. The consistency offered by the Red Hat Enterprise Linux (RHEL) was also one of the other reasons why my company chose it over other tools.

Though my company does not currently have a hybrid cloud environment with the tool, we are working on it since regulatory compliances in the banking sector require us to stay compliant. My company is not in a place where we can just jump into cloud infrastructure, but we do hope to do so in the future. Presently, the product is on an on-premises model.

As I am not required to deal with the developers in our company, I don't know if the product has helped centralize developments.

My company uses Red Hat Enterprise Linux (RHEL) for containerization projects. The product has made dealing with containerization projects easy for my company since we get to use a lot of Kubernetes and Docker platforms that snap right into Red Hat Enterprise Linux (RHEL) and works.

Considering the built-in security features offered by the tool for risk reduction, business continuity, and maintaining compliance, I prefer Red Hat Enterprise Linux (RHEL) over a lot of other products. Our company is like an Active Directory shop, so we are doing a lot of tying to it, which is a little bit disappointing, but it is just business. I like the security end of Red Hat Enterprise Linux (RHEL). I also like the way the file handling takes place along with its management part, so I have no issues with the tool.

Speaking about the portability of applications and containers built on Red Hat Enterprise Linux (RHEL) to keep our organization agile, I would say that it is something that will happen in the future as my company is a slow adopter. I am not really sure why it has been slow. My company does have a new organization that is really focusing on opening up new avenues so that we can actually be more agile and have the ability to move to things like OpenShift and having our containers offer more high availability while not having any downtime.

I don't use Red Hat Insights.

If I have to speak to a colleague who is looking at open-source cloud-based operating systems for Linux, I would say that CentOS or Fedora are good options since both products have had an association with Red Hat Enterprise Linux (RHEL) for a long time. I personally like and prefer CentOS.

I would not be able to comment on whether the Red Hat portfolio has affected our total cost of ownership across our enterprise landscape because we just spin them up and keep building them. My company was primarily an AIX house, using Solaris and a lot of Windows boxes from Windows. Right now, my company has gotten rid of the AIX and Solaris systems, and now we are down to about a 50-50 split when it comes to Windows and Red Hat Enterprise Linux (RHEL). There have been times when we have had more Red Hat Enterprise Linux (RHEL) boxes in our company over the ones from Windows. I can see that in the near future, my company is going to be more of a Red Hat Enterprise Linux (RHEL) shop than an organization that has boxes from Windows.

In terms of the deployment model, I would say that my company has three data centers, mostly where VMware is used.

I rate the tool a ten out of ten.

I use the solution in the company to build a lot of our software environments, so we keep different baselines on it. Right now, I'm working on setting up and installing Ansible manually, so I haven't used Red Hat Ansible Automation Platform yet, a reason why I have been still using my Red Hat Enterprise Linux (RHEL) server.

In terms of features, I found it great when I talked with Linux subject matter experts about Ansible. They further mentioned that it was native to Red Hat, which is why it wasn't going to bring over more packages or modules. The packages or modules in the tool are already there but are just not enabled because they weren't being used before I asked about them. It is super easy to enable the tool's packages or modules when I want to start messing with it.

Red Hat Enterprise Linux (RHEL) has helped me centralize development because it has a standard, which is why my company can't really have the option to mess with its different technologies. Our company's customers don't want to use Ubuntu or any other such operating systems, which is why my company has to use Red Hat Enterprise Linux (RHEL). I guess the tool is easily centralized because that is its standard, and that is the only option one has unless someone wants Windows, but again, developers don't want Windows, and so there are no other options.

Our organization has a team to take care of the containerization part. I am mostly on the infrastructure side, but my company has started to ask me for Podman Desktop and all these different container platforms, and I haven't used any of them yet.

If I dissect the built-in security features of Red Hat Enterprise Linux (RHEL) for risk reduction, business continuity, and compliance, I would say that we use VMware for risk reduction so that we have a high availability. On the top of my head, I think the Linux team probably knows more about reducing risks. Our security team has all these STIGs they want us to apply, so I don't know how much manipulation they actually have to do.

If I dissect the built-in security features of Red Hat Enterprise Linux (RHEL) for risk reduction, business continuity, and compliance, I would say that we use VMware for risk reduction so that we have a high availability. On the top of my head, I think the Linux team probably knows more about reducing risks. Our security team has all these STIGs they want us to apply, so I don't know how much manipulation they actually have to do. For business continuity, my company uses VMware, considering the ease of making snapshots of our environments, but I believe we could probably do the same with different operating systems. In our company, we just take lots of snapshots, and then if we have another VMware instance, we could just build it right back. The only compliance I know about was associated with our company's customer and their STIG requirements, but I don't know how Red Hat Enterprise Linux (RHEL) helps with it, especially considering that in our company, we have to manipulate it and how we want to do it.

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 we have an applications team that would do it in our company. I just make sure that our company's VMs have OS and network connectivity since there is a different team that takes care of the applications.

Right now, since my company is in an air-gapped on-prem network, it is really tough to go through all the RPMs that we have to have based on different STIGs. Whenever in our company, we have to install the tool, we see that something or the other is missing, and so of the hundreds of things mentioned in the list, we have to find whether we need a particular RPM or if we need to take this one out, and that is always a trouble for the team managing Linux in our company.

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

When I spoke to one of the speakers the other day, who was a software development manager, I was told how much one could trust Red Hat Enterprise Linux (RHEL). I believe that Red Hat Enterprise Linux (RHEL) is considered a standard for a reason.

I believe that if you have enough license to support the product in your environment, then you can scale the product depending on how big your license is, and it is a super easy process where one can roll out a whole bunch of VMs and VMware.

As my signature block comes with Lockheed Martin, I think the tool's support team has been pretty attentive. If I go to a wide-scale service and once Red Hat Enterprise Linux (RHEL) sees what kind of a customer I am, I get to go to their specialized sectors, and the support has been pretty fast. I have had no issues with the product's support team. I don't use the product's support services very often. I have mainly dealt with Red Hat's support team for Ansible. I rate the technical support a seven out of ten. When I was asking the tool's support team questions when I was off the internet, I just kind of felt weird about it. For any service I ask for from the support team, I have to manipulate it depending on what we need for our company.

I have not previously used any other product, and I have worked for the government for the past twelve years using Red Hat Enterprise Linux (RHEL).

The deployment of the product has been super easy, but when we do it through VMware, I just make a VM, and then load an ISO image, after which the deployment is done. The tool's deployment is super easy, and I am pretty much a novice when it comes to Linux.

The solution is deployed on an on-premises model.

My company did not seek the help of a third party to depot the product. The deployment was carried out by our company's employees, who have been around for decades.

The government buys the product for our company and provides us with the license for the solution.

For a colleague who is looking at open-source cloud-based operating systems for Linux, I would say that Red Hat Enterprise Linux (RHEL) is a cool product for small businesses outside of the government. I work for the government, where Red Hat Enterprise Linux (RHEL) is the standard, so if my colleagues are in the government, I would tell them they have no other options.

I am not sure about the product's deployment model since it is kind of ad hoc in nature. If a developer needs another VM, our company just provisions it through VMware, so we don't have a large-scale deployment model across different availability zones. We have our program, after which we wrap it all up and then ship it out to the customer.

As I have not compared Red Hat Enterprise Linux (RHEL) to any other operating systems in the market, I rate the tool a nine out of ten.