Red Hat Enterprise Linux (RHEL) Reviews

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 are using the full setup in Linux and use the enterprise edition. We're migrating a lot of things over. 

We like that it's open-source and fully secure. We've fully migrated to Linux, and we were able to move everything over from the Red Hat database.

Compared to earlier tools, we get more options, and it's very user-friendly. The patching, for example, is easier. It can also support many things. It took us about six months to realize the solution's full benefits.  

The solution is very user-friendly. 

The Red Hat Enterprise Linux scripting is very good. It is easy for us to access those parts in the Linux portion. 

The security is very good. It helps us to maintain overall security.

I have a Linux certification, however, they do have good documentation in order for users to get information about the product.

The management experience for patching is very good. We can do the patching through the portal. We can use it based on our own timing. If there isn't something in production, we can do the patching. The patching experience is very nice compared to what we had to deal with previously. For example, with Windows, the patching would happen whenever. We can control it via the portal, and it is very user-friendly now.

We only use the command line. We do not use the GUI. The graphical user interface is useful. However, we prefer to use the command line as we can do many more things. 

Red Hat Enterprise Linux has positively affected our uptime. It's very fast. If you have to do patching, and need to reboot, it doesn't take too much time to do that. It might only take one to two minutes. 

For the most part, everything looks fine. Everything is going smoothly. 

Right now, we need to get memory and CPU via the console. If it was available in the console so that we could adjust these two things, that would be ideal. 

I've used the solution for the last four years. 

The stability of the solution is fine. I'd rate it nine out of ten for stability. It's user-friendly and the downtime is low. It won't impact business.

The solution is not deployed across multiple locations. We have around 300 end users.

It is scalable. We can immigrate to servers and it won't impact the business. 

We know there are some issues, and if we come across some vulnerabilities, we'll work with support. If we get an error, we'll go to them and discuss the issues. We take advice from them on how to work through problems. 

Sometimes, we'll get some errors and we'll send them an email. Sometimes it takes too much time for them to respond. The support time could be better.

Neutral

We did previously use a different solution. 

I was not involved in the installation. I have not worked on the OS level and I'm not involved in the migration to the cloud.

We have eight to nine people on our team that may handle some maintenance tasks. If there are any issues, we can patch and fix them. We go through the portal to handle patching and maintenance. We'll check the system pre and post patching.

I'm not aware of the exact pricing of the solution. 

We did not evaluate other options. We've fully moved to Linux and used Red Hat Enterprise Linux to do this. 

I'm an end-user. 

We will be moving to the cloud only. I'm not directly involved in that. The main thing will be that soon everything will be in the cloud only. Currently, I work with the on-premises version only. It's on a VM right now. 

This is a good solution if you are handling migrations or your internal environment. It's user-friendly and you can connect with technical support easily. It's also very secure. 

I'd rate the solution nine out of ten. 

I work as a consultant for a bank. They were using another type of Linux and facing some scripting issues. We are using Ansible for infrastructure, but they depend on different languages. In this fintech use case, the bank performs transactions between two banks. The transactions were getting stuck, but they detected that the money had been transferred. 

The money comes from the bank. They transport it from the cloud and deliver it to the channels like Visa, MasterCard, etc. The national bank is also involved at that stage, so there is a pause. When we are using auto-scaling, it requires a small amount of time, so your application will have an error. This is a millisecond process. That is the duration. We were looking for issues like bank fraud. You need to conduct an analysis and restart the service. The data is on Red Hat Linux, and we use EKS for containerization. 

We have a hybrid solution combining AWS with an on-premise environment. Moving data to the cloud requires a stable connection because we have multiple systems on-premises and on the cloud. This platform helped us communicate among multiple clouds and our private cloud network. 

Using Red Hat Enterprise Linux enables us to subscribe to other Red Hat services from our portal. We can connect to Satellite with single sign-on logins. We can use the Spring CLI call and the Docker hub. We have a direct subscription.  

Red Hat Enterprise Linux has helped us avoid cloud vendor lock-in. We could easily migrate between cloud services from AWS to Azure if we wanted to. Everything is an SCL, so we could deploy the same thing on another cloud. It's highly useful. We can make a script and move the entire infrastructure. 

The Red Hat Linux comes with Anaconda, a fascinating tool that is useful if I need to connect multiple systems. I also like role-based access. 

Red Hat Enterprise Linux is a little expensive for some customers who don't have the budget. It depends on the client. They can save money by not purchasing some of the added packages and services.  If the client has a budget of $10 million, we can go for the whole bundle. 

I have used Red Hat Enterprise Linux for four or five years.

Red Hat Enterprise Linux is stable.

Red Hat Enterprise Linux is scalable, but it depends on the deployment. 

I rate Red Hat support 10 out of 10. I'm a big fan. 

Positive

I have used Ubuntu, which has its own cloud service. Red Hat Enterprise Linux is a better option if the client has a budget. Red Hat Enterprise Linux can be certified and meet compliance requirements. 

Deploying Red Hat Enterprise Linux is straightforward, but the complexity and time required depend on whether we are deploying on a virtual machine or a desktop. If we have the correct documentation, the total process can be completed in three to five days.

I have used the Image Builder Tool, but in the latest deployment, I pulled down the repository from the Docker hub. We use our own XML file and create the repository. It's a two or three-day design process for Red Hat Linux. We need one data resource for that process and a second engineer on the support side if we want to set up more servers from their on-site services.

It's affordable, but everything costs money. At the same time, everything adds value for our clients.  For example, I was working on a machine-learning project, and they needed more team resources, and all the projects used computing power. By running multiple clusters, the client exceeded the rate for that data. We buy services from AWS, the Azure Marketplace, or directly from Red Hat. 

I rate Red Hat Enterprise Linux nine out of 10. I recommend buying the services in a package if you can afford it. If the client doesn't have the budget, we can find alternatives. It depends on the client's needs. 

We use Red Hat Enterprise Linux as our core operating system for hundreds of our critical systems including our databases, complete middleware, and over 500 VMs.

The portability of applications and containers built on Red Hat Enterprise Linux is exceptionally high due to the utilization of Java as the middleware and Oracle as the database. This enables seamless portability across various platforms, regardless of the specific infrastructure employed. As long as Oracle continues to provide support for a particular platform, the applications and containers can operate effectively on that platform. Therefore, the decision regarding the deployment platform rests solely with the company's preference.

The consolidation into a single operating system has brought about significant improvements. Previously, companies often had to manage three or four different operating systems, which was not only costly but also inefficient. With a unified operating system, we can now streamline operations and reduce the number of teams required for maintenance.

Red Hat Enterprise Linux facilitates our compliance with security standard certifications. We receive daily reports and recommendations specifically for applying security patches and related measures.

Red Hat Enterprise Linux is the most used Unix platform in the cloud. We can build with confidence knowing that it is available across physical, virtual, and cloud infrastructures.

The integration with Oracle is the most valuable feature.

The patching process with Red Hat is disruptive and not very cost-effective. This is why I would like to switch to Oracle Linux, which allows for security patching on a running system. This is a significant advantage of Oracle Linux over Red Hat. With Red Hat, we have to shut down all of our machines at least four times a year for large patches. Oracle acquired the technology for applying these online patches from MIT, and this technology is integrated into Oracle Linux. This allows for systems to be patched without disrupting the work of employees and their organization, which is a major improvement over Red Hat's patching process.

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

Red Hat Enterprise Linux is a stable operating system. In most cases, the issues we have encountered have been related to hardware, not the operating system itself.

Scaling Red Hat Enterprise Linux is easy. We have clusters and simply need to add machines to those clusters to scale.

We have more applications being added all the time.

Previously, we used HP for our database site before transitioning to Red Hat Enterprise Linux. As we were already utilizing Red Hat Enterprise Linux for our applications, it proved to be a more optimal choice for our database site as well.

The implementation was completed in-house.

We have to pay for the support and features.

The distinguishing feature between open-source competitors and Red Hat Enterprise Linux is the comprehensive support that Red Hat Enterprise Linux provides. Red Hat Enterprise Linux no longer faces competition from HP and Digital in terms of support services, as these companies have ceased offering their solutions. IBM remains the sole competitor, but they recently acquired Red Hat, essentially consolidating the support landscape.

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

Numerous open-source Linux operating systems are available, but Red Hat Enterprise Linux provides robust support and a stable platform for large organizations that would benefit from the support.

Organizations should base their decision on which operating system to use for their specific requirements. For Windows or Oracle systems, the corresponding OS should be chosen for support reasons. For Unix systems, Red Hat Enterprise Linux provides the best support.

When I first used Linux 1.0 over ten years ago, I was surprised at how well it worked. I never expected it to become so successful that it would surpass all the major Unix systems, but that is exactly what happened. Today, Linux is used for a wide variety of applications, regardless of the platform. This is due to its exceptional scalability and the low cost of hardware.

I work in infrastructure. We have various use cases for Red Hat Enterprise Linux. We use it for the compute feature, which runs on some applications on the front end and databases on the back end.

LVM is a valuable feature. It enables us to dynamically increase the file systems or logical volumes. My journey with this feature started 10 to 12 years ago. 

LVM is the reason why I started using the solution initially. Nowadays, there are a lot of applications. We can use clustering, security, and optimize security.

The product's availability is on the main cloud hyperscalers, like GCP, IBM Cloud, Azure, and AWS. The product should be made available on Oracle Cloud. 

I would like to see Ansible as a default in future releases.

I have been using the solution for 13 to 14 years.

Although some questions are not business-critical and high priority, they are still urgent. The support identifies such questions as P3 or P4 incidents. Although there's no business impact, we depend on the support team for answers.

Neutral

We have used SUSE Linux. We have also used open-source tools like Ubuntu, Fedora, and CentOS. We switched to Red Hat Enterprise Linux due to its vast exposure to security vulnerabilities. Its support model, subscription model, and its support for HANA are valuable.

We use the product on-premise, on IBM Cloud, and on Azure. The subscription model of the solution enables us to use hybrid environments. We can enjoy the benefits of the hybrid environment with the bring-your-own-subscription model.

We have plans for upgrades. We have a legacy Red Hat Enterprise Linux. One of the customers has version 5. We are trying to build an upgrade plan for it. We would like to know whether we can directly land on version 9 or if we should go step by step to each version.

The solution's built-in security features are exciting. I like that the solution covers the recent vulnerabilities in the CVEs. The solution should continue to do that.

Overall, I rate the product an eight out of ten.

We use Red Hat Enterprise Linux to run quite a few pieces of software. It's mostly for jPOS, but we also run some Apache solutions and some security applications.

Red Hat Enterprise Linux has streamlined a lot of the support issues. When we've had problems, Red Hat has been proactive about solving the problem with us. Support is always an issue with open-source platforms. By providing this support, Red Hat makes it much easier to adopt Linux.  

I love Red Hat Enterprise Linux's built-in security. You can see who is trying to do what and who isn't allowed. You get an alert for that. We also use a product from Symantec on the Linux system for real-time threat detection, but I think we probably don't need that. Red Hat already has these capabilities, but the security team needs something they can centrally manage. They need to know whether the system is protected and the agent is running. 

We use it on VMware, and we have a multi-site deployment, so it's very easy to patch and keep the servers up. We use Ansible automation for patching, which has really helped with the service uptime.

I like the speed of the OS data and the ease of Ansible automation. I don't need to spend much time managing everything. The provisioning and patching using Ansible is seamless. Ansible automation gives you almost a cloud-like capability on-premise. Most of my group doesn't have cloud skills. I learned it on my own and got my Kubernetes certification. I'm familiar with the automation infrastructure, how to build the execution environment and implement the private automation hub. Others still need training.

I've used Red Hat Enterprise Linux Image Builder for testing and development, but I haven't put it into production. We have a VMware template, and we've been doing training on VMware, but we are not there yet. I think they might move from VMware to another product. They are looking at other options, such as OpenShift, but we don't have training for OpenShift yet. They should try to have a salesman come and get OpenShift training for customers. If they make training free for the customers, more would switch to OpenShift from VMware.

I use Linux on Satellite with Ansible infrastructure. It would be great if there were a universal interface to control Red Hat Enterprise Linux's policy from Satellite. It could be a dashboard showing which policies were enabled on what system and allow you to apply them from the dashboard. 

I think Red Hat training could be cheaper. A company can move fast technologically with enough training. They will be stagnant without training and remain unable to fully leverage the technology. I have been encouraging the group to get a subscription to the training course for five years, but we haven't been able to take advantage of it because of the cost. They should make it cheaper for clients and offer big discounts at scale. 

When people lacked training for the technology we use, we migrated away from it. I worry that if we don't have enough training available to the client, they will eventually migrate away from Red Hat. More affordable training on key technologies like Satellite and Ansible automation will help us retain customers on those products. Downstream it will help them migrate to the latest and greatest Red Hat Enterprise Linux, as well. 

I have used Red Hat Enterprise Linux since 2005.

I rate Red Hat support 10 out of 10. I've been very impressed with the knowledge base and the support from Red Hat. When I create a ticket, they respond and resolve the issue quickly or they point us to the correct resources. For example, we had an NFS issue with ISO, so they helped us with the mounting options. We also had an issue with IBM AIX and Red Hat integration. Red Hat referred us to the IBM support stack, and we were able to get IBM to help us out.

Positive

Initially, I used Solaris because I liked it the best, but Red Hat Enterprise Linux has improved so much that it has overtaken Solaris. Red Hat Enterprise Linux is easier to use and has better documentation. I also like having the ability to use Satellite and Ansible automation to manage Red Hat Enterprise Linux. 

The deployment is straightforward because we use Ansible automation to spin up a new system and install applications directly from the Ansible workflow. We were planning to have Red Hat Enterprise Linux 8 online last year, but Red Hat Enterprise Linux 9 came out, so we decided to wait for a bit, and we're almost ready to upgrade to Red Hat Enterprise Linux 9.  The application folks still haven't had enough time and money to migrate everything over, and we need a project manager. 

I rate Red Hat Enterprise Linux 10 out of 10. It comes with all of these nice tools like the Satellite automation web console. 

We use Red Hat Enterprise Linux for our on-prem VM infrastructure. Recently, we got the OpenShift platform to help with containerization on-prem.

Moreover, containerization is one way we're trying to get rid of any legacy. We don't patch. We try to have a fresh build with the newer version of the patch. We try to use those Red Glue deployment strategies and remove whatever we find in misconfiguration or vulnerability instances rather than fixing them. We redeploy it.

In terms of improvement within the Linux environment, especially for a non-IT company like ours, where we have a limited number of Linux administrators and specialists in Linux hardening and security, Red Hat Enterprise Linux plays a significant role. 

It eases the burden by restricting the use of open-source Linux and preventing the development community from obtaining their own images. This is crucial for maintaining a secure supply chain and ensuring the lockdown of live Linux packages.

However, when it comes to security compliance, I have not been exposed to the Red Hat Enterprise Linux security; we got the advanced cluster security from OpenShift, which has some vulnerability tracking within the cluster. Within Red Hat Enterprise Linux, I have not experienced the security console yet.

Red Hat Enterprise Linux has affected our systems and our security. It helps us achieve security standards. It's one of the hardening requirements so, it helps with that compliance requirement.

With standardization across the environment, we don't have to generate multiple artifacts for compliance, and having a single Linux platform management like Red Hat Enterprise Linux helps to satisfy auditors a little faster.

From a security perspective, the overall hardening of Red Hat Enterprise Linux is good. It has been effective in enhancing security.

Image management and hardening are essential, so we don't have to procure open-source Linux images that developers can get themselves. It adds a layer of security with signed images.

The knowledge base is pretty good.

From a cloud perspective, I'm looking for more integrations with native cloud services. For example, the ability to use native Azure Key Vault instead of Ansible Key Vault or Red Hat Key Vault. 

Additionally, integrating image services from Red Hat into native image repositories such as Azure, Google, or third-party image repositories like JFrog is crucial. The key focus is on integration. 

Red Hat should not become Microsoft and lock down functionalities within Red Hat. 

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

We have premium support, so it is pretty good.

Positive

We are a mix of some other cloud virtualization technologies. The overall cloud information will define how we look down the road.

With Linux management, the pros are that it makes management a little easier. Overall, it is just a single view of the images we deploy in the organization. 

The cons are that the integrations are a little tricky sometimes, and then we have to make exceptions to our policies. Better integration, more native service using more credentialless authentication, and authorization like using service principles or managing these over-store credentials would make it better.

Currently, the emphasis is on on-premises solutions.

Overall, I would rate the solution a seven out of ten because it needs more integrations.

We primarily use it for OS purposes. 

It's very good for support compared to other operating systems. For decades, it's been providing good support and service. Even during implementation, there's a dedicated team to answer any queries. We are a very big company running critical applications and having that support is very important.

The patching tool is good. We're also introducing the possibility of automation.

The built-in security features are okay when it comes to simplifying risk reduction. It makes life easier, especially in regards to the lifecycle and what we need to install, et cetera. The features and tools help us to maintain security overall. 

It is easy to maintain compliance.

The portability of applications and containers is good. Now we are just starting with the containers and anything related to Kubernetes. 

Red Hat is always providing security on time. Any vulnerabilities are immediately dealt with to fill the gap and deal with the issue.

It's a good tool. I'm very confident with this product.

The system role features for automation security configurations, et cetera, for Ansible, we started using it. We are new in terms of automation. We'll start to use it heavily in the near future. Ansible is another great tool from Red Hat.

It enables us to maintain consistency across systems over time. My role is to maintain stability, even during upgrades and patches. So far, it's been a positive experience. We use the entire ecosystem around Red Hat.

We use Red Hat Insights. From a security perspective, we may stop using it. With Insight, if you have Red Hat Satellite, it gives you an in-depth view of everything. The only thing missing is the insights related to performance. We may not continue with it. We'll see if we'll push it and have everything on the cloud. 

In the area we are using it, we are satisfied.

Maybe in OpenShift, which is our next step, there can be more improvements with integration with Kubernetes. We're not experts there yet. 

Maybe it could have a better user experience and less coding. Reducing the effort for the end user or administrator would be ideal to make daily operation and maintenance easier. 

If they can make the integration with Ansible easier, that would be ideal.

They should offer more in terms of learning materials to make learning easier. 

They need to make things more affordable or accessible. 

The solution is stable. We barely have any issues with a server setup. So far, it's manageable. The biggest challenge is the criticality of releasing patches. When we have any critical alerts we action them. We tend to try to wait for the release of a stable version. 

How many people use the solution depends on the application. We likely have thousands of users. We do have some products that maybe only have a few or a few hundred. 

We've had no challenges with scaling. It can support any type of load within the data center. 

Support is excellent. 

Positive

We did use a different OS. I have used Unix in the past. I started with Unix 30 years ago. I've also used SUSE. Red Hat offered more service and support. 

I was involved in the deployment. Our team managed the process. It's pretty straightforward. We handle implementation, tuning, and patching. 

How long it takes to implement the product depends. We're trying to mitigate the time by automating with Ansible. We want to handle one VM or server in five or fewer minutes, however, it can take days. At this point, we can provision servers in a few minutes. It's becoming faster. 

We have a team of ten to run the infrastructure on the OS level. 

I'm not an expert on ROI. We are paying to use the solution, however, the utilization we get and the support both offer good value. 

The pricing model isn't something I deal with directly. The pricing is fair, especially compared to virtualization like VMware. We do use VMware and are thinking about moving sandboxes and testing over to Red Hat. This may end up being a big cost savings with our CAPEX and OPEX. 

From the price level, the cost is almost the same for us, if we look at Red Hat versus SUSE, however, we get a higher level of support with Red Hat. 

Red Hat was always our first choice. 

We're a Red Hat customer. 

I'd rate the solution nine out of ten. 

We are currently using Red Hat Enterprise Linux's versions 6, 7, and 8. We run the OS both on-prem and in the cloud.

We use Red Hat Enterprise Linux for web applications, containers, Kubernetes, and simple scripting servers. The scripting servers are used to run scripts on run drops and so on. However, the biggest use cases are containers and web app workloads.

The cloud providers are AWS and Alibaba.

Red Hat helps our organization avoid cloud vendor lock-in because we can run Kubernetes and a few different workloads directly on Red Hat across different cloud providers. Since Red Hat is an operating system, we can migrate our workloads to any cloud provider that supports Red Hat.

Avoiding vendor lock-in and being able to move workflows between cloud providers has saved us hundreds of thousands of dollars per year.

Red Hat Enterprise Linux is easy to recover, especially from a backup. I believe this is because of its resilience. If I use an instance, I can go to my backups and restore it without much trouble. I was going to compare it to Windows for a moment, where there might be some additional steps required to clean things up after recovery. However, I haven't had many issues where I needed to do any cleanup afterward.

It is easy to move workloads between the cloud and our data center using Red Hat Enterprise Linux. The ease of migration depends on the cloud provider and what they allow us to do. However, for the most part, replication-based migration between cloud providers or on-premises works well. 

Linux is good for hardening the operating system. Logical volumes allow us to dynamically expand volumes, which is valuable from an operational perspective. This is especially true in cloud environments, where we pay for every kilobyte of storage. By using logical volumes, we can expand the disk on demand without downtime, which can help us keep costs down.

The price has room for improvement.

I have been using Red Hat Enterprise Linux for three years, but I have known about the OS since version four.

Red Hat Enterprise Linux is definitely resilient and easy to recover, especially when compared to Windows. I enjoyed working with Red Hat Enterprise Linux more than Microsoft Windows, especially because of its resilience.

Red Hat Enterprise Linux's scalability is easy to manage. We can simply spin up more instances as needed, and then turn them off when we no longer need them. This means that Red Hat Enterprise Linux's scalability is not as much of an issue with the cloud provider.

We have around 2,500 instances of Red Hat Enterprise Linux in our environment.

Red Hat support is generally good, but it can sometimes take a little longer than we would like to get a response, especially when the issue is through a web-based chat.

Positive

The on-premises deployments are subscription based, and the cloud instances are from the providers which are AWS and Alibaba.

We can always ask for Red Hat Enterprise Linux to be less expensive but when we compare it to other options, there are savings in the long run.

Red Hat Enterprise Linux was our first choice because of its enterprise support. That was the key factor. We do also run other Linux distributions, but Red Hat Enterprise Linux is our primary choice because of the enterprise support. 

The big difference between Red Hat Enterprise Linux and other Linux-based operating systems is the support. There isn't much difference other than the syntax, where the command is "at, get" versus Red Hat using YUM or DNF for installation. So outside of that, the support is the main difference.

I give Red Hat Enterprise Linux a nine out of ten. No solution is perfect, but Red Hat Enterprise Linux is very close.

Our engineering team probably used the image-building tool. I am on the operations side, so I do not see that part of the process. I take the images that are already built and deploy them.

I think it's just a workflow issue. We need to improve our own workflows to be able to manage them better. Red Hat support is already good when we encounter something we're unfamiliar with. So, we need to get Enterprise CoreOS from Red Hat for those cases. I think as we encounter more of our own workloads, we'll need to improve our workflows even further.

I am a Federal Contractor. Red Hat Enterprise Linux is one of the FedRAMP-approved operating systems, so the government is comfortable with using it. That is why we use it, even though it is a bit outdated. Most of our software runs on Red Hat Enterprise Linux because we work in Identity Access Management. For example, Oracle Identity Stack runs on Linux, so we have to use Red Hat Enterprise Linux. We follow very strict security protocols, and we use Ansible to enforce them. Red Hat Enterprise Linux is the easiest way for us to do this.

Red Hat Enterprise Linux is a trustworthy and highly scalable operating system. The federal government needs an operating system that they can rely on, with enterprise support and long-term service. As well as being stable and well-known within the community.

I have not yet experienced a disaster recovery scenario, but resiliency is important, and risk is very reliable. The auto logs are very clear. Additionally, with those support communities, it is straightforward enough to understand what we are looking for and to eventually resolve the issue.

I actually like the in-place upgrade that Red Hat Enterprise Linux offers. It has made our upgrade process from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 much easier than we originally thought. 

I know that many people prefer in-house support, but I personally prefer Red Hat's support. It is easy to get in contact with their support team.

Even though it is not directly related, the fact that Red Hat Enterprise Linux and Ansible are closely related makes it easier for us to move forward.

The package management, repository, and satellite repository are easy to use.

I am a bit biased because my client is air-gapped. This means that we cannot connect to the internet, so all of our operations are disconnected. I would like to see better support for disconnected operations. For example, the in-place upgrade from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8 initially relies on a lot of online resources. This makes sense, but it would be nice for a consumer or integrator like me to be able to say, "Hey, we need an offline solution so we can upgrade our government clients on-premises." Red Hat does provide instructions on how to create a repository, but the instructions are not very clear. This leaves us scrambling to figure out why we are missing a repository in our satellite image. Red Hat should provide a way to mirror repositories or at least provide a solution for us to bubble up packages throughout the entire process.

I have been using Red Hat Enterprise Linux for four years. We started with Red Hat Enterprise Linux 6, and we upgraded to Red Hat Enterprise Linux 7 in an airgap environment. We are currently in the process of upgrading to Red Hat Enterprise Linux 8.

Red Hat Enterprise Linux is stable.

Red Hat Enterprise Linux is scalable. It is deployed in a 10,000-plus enterprise company.

The support team is always direct and easy to find. Their answers are so helpful that I have not yet had to call them. I also appreciate how they approach troubleshooting. They don't assume that you're doing anything wrong. Instead, they try to educate you on how to fix the problem. In my experience, the support team has always been very positive.

Positive

I have experience with most Linux operating systems, including distributions like Apache, Debian, CentOS, Fedora, and others. From my perspective, Red Hat Enterprise Linux is not necessarily the top standout product, but I know that it is a product that I can rely on. It is the standard image that enterprise users in the community will use. We can rely to a degree on the standardization of how packets are used to support it. However, it does not stand out to us as much as the other products. Nevertheless, I know that it will have a positive partnership with us. Red Hat Enterprise Linux is a more suitable operating system for enterprise environments in terms of stability and reliability.

We are currently in the process of reviewing our initial solution for upgrading from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8. The in-place upgrade for the airgap environment is an area where we are still struggling to understand the documentation. However, Red Hat has been very supportive and has offered us pathways to move forward. We do not have much to say at this time, as we are still in the middle of the process.

When we upgraded Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7, it took us around six months due to external factors not related to Red Hat Enterprise Linux.

Our client has a direct subscription to Red Hat.

I give Red Hat Enterprise Linux an eight out of ten. I am not a firm believer that everything is perfect right out of the gate. Everything can be improved. I am a little biased. I wish there was better support for offline environments. I understand that I am in the minority in this case, as everyone is connected to the internet now. However, as a federal contractor and integrator, we have requirements that we must meet. It is not fun having to download binaries offline and then figure out how to set up our own repository. These are not straightforward tasks like Red Hat telling me what to do. We just wish it was easier to do things like patch management. Perhaps there could be more support for air gap environments. These are not environments where we can temporarily connect to the internet. They have never seen the internet.

Depending on our customer's environment, sometimes they have GovCloud, but we still use Red Hat Enterprise Linux images there. Sometimes the customer can't use that so we use the offering from CentOS. But we still try to match it with CentOS.

The reason why some clients don't use Red Hat Enterprise Linux on the cloud is not because of security concerns. I think it's more about cost and their current contract situation. They need a low-cost, open source alternative, and our recommendation would be CentOS. However, many clients are not ready to pay for the enterprise edition of Red Hat Enterprise Linux, so they may choose to scale back their plans.

I have not used the Red Hat Enterprise Linux knowledge base strictly. I have only used the Red Hat Enterprise Linux support.

Clients who use Red Hat Enterprise Linux on the cloud, typically use AWS GovCloud. As a government integrator, we strive to design our solutions in a way that does not lock our clients into any specific cloud provider. This is why we chose Linux, as it can be run on any cloud platform. This flexibility is important to our clients from a price contract perspective. For example, Amazon provides Kubernetes services, among other things. We try to figure out open source solutions or at least architecturally determine them and provide them to our clients. For example, we can tell them that they can move all of their GovCloud data to Azure or Google Cloud. Government agencies really like Amazon right now because it is FedRAMP. However, for other classes that are not government or commercial, we try to introduce them to the CentOS perspective so that they can get a taste of the upstream.

We do not use the image builder tool provided by Red Hat. Instead, we use the one provided by Amazon. We take a base image, coordinate it with Ansible, and provide it to any environments that have used the cloud. For on-premises solutions, we strictly use manual processes.

I don't have a perspective on the golden image, which is at least with our client. The parts that we use are always evolving, so we don't really maintain the golden image. We do have a relative backup of what we deployed to, but we don't necessarily have a strict golden image.

Migrating workloads between the cloud and the data center using Red Hat Enterprise Linux is not entirely applicable to us. We did migrate from on-premises to the cloud at one point, but migrating from Red Hat Enterprise Linux on-premises to Red Hat Enterprise Linux in the cloud was not a concern for us. We knew it would be stable and fine. The main concern was migrating our customer data from our enterprise to the cloud.

If someone is looking for an open source cloud-based operating system for Linux instead of Red Hat Enterprise Linux, I would like to eventually drive them over to Red Hat Enterprise Linux, but I would recommend starting with CentOS. CentOS is a good gateway OS because it is very similar to Red Hat Enterprise Linux, and the knowledge transfer between the two is very straightforward. This makes it a good choice for users who are new to Linux, or who are looking for an OS that is compatible with Red Hat Enterprise Linux.