I would advise following the best practices recommended by Red Hat. It will minimize the downtime of the application or system. Partner with the vendor and get that support. Know the business case and build a strong relationship with the vendor. Trust them and tell them your use case, and they will come up with the best solution possible.

I am not a big authority on Red Hat or other Linux or Unix products. Only recently, I have been exposed to the concept called hardening and penetration testing. I do not know whether Red Hat provides a hardened version of the OS. My basic distribution is Gentoo which provides a hardened version of Linux. On the client side, the organizations we work with have different departments, such as the security department and the compliance department. For security, they work with various options that are available. For penetration testing, we engage a penetration testing consultancy company once a year.

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

I give Red Hat Enterprise Linux an eight out of ten.

I think open source software is generally cheaper than Red Hat. However, I don't think that cheaper software is always better. And I don't think that Red Hat is necessarily better than open source just because it costs more. It really depends on our specific needs. If we're comparing Red Hat to an open source equivalent, I would say that Red Hat would probably be a better fit for us. This is because Red Hat offers support, a back-end, and a team of experts who can help us if we need it. With open-source software, we're often on our own and have to figure issues out on our own. With Red Hat, we have the peace of mind of knowing that we can get help if we need it.

We have Red Hat Enterprise Linux deployed across multiple contracts and multiple data centers. It was not on the cloud; it was all on-premises. However, we were able to deploy it across multiple data centers, multiple customers, and multiple departments. This flexibility was a major advantage.

We used Red Hat Enterprise Linux to patch and update the system, including drivers, the OS itself, and security updates. We also monitored disk space usage and swap usage, but this was not too time-consuming. We had a team of three or four people to rotate tasks, so no one person was stuck on the same thing all the time.

Red Hat Enterprise Linux is a good product. It has a good ecosystem and support. It is lightweight and does what we need it to do. It is a good alternative to Windows for lightweight containers or servers. It is also good for specific roles.

The operating system is a great way to learn about Linux. While some people will always choose Windows, it is not always the best answer. Red Hat Enterprise Linux is more stable and less resource-intensive than Windows, and it is also more trustworthy. This makes it a good choice for environments where reliability and security are important.

One of the new features in RHEL version 8 is AppStream. We're still doing our RHEL 8 deployments and although we've started using AppStream, we haven't gotten very deep into it. Its use is on a very limited scope. RHEL 8 is about halfway through its lifecycle and we're still trying to see how it works.

When it comes to the deployment of cloud-based workloads, this solution helps to automate activities. We are just starting our cloud journey and as such, we currently don't have any cloud-based workloads. However, we plan to, and my understanding is that it will be much easier using Red Hat Gold images for Azure, AWS, etc.

My advice to anybody who is implementing this solution is to automate as much as possible. Overall, I think that this is a good product. I'm a pretty big proponent of Red Hat and in fact, as we speak, I'm wearing a Red Hat RHEL 8 shirt. 

I would rate this solution a nine out of ten.

I've been trying to find a reason to use containers, but I just can't. I know our company uses it a lot, and they love it. They love the ability to shift things around and bring down servers when they want, and all of that, but for my own use cases, I haven't had a reason.

Overall, I'd rate Red Hat Enterprise Linux a ten out of ten. Everything is great.

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

We have a requirement to have a Linux operating system.

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

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

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

If you want to integrate with OpenShift or build an OpenShift cluster with the master Red Hat Enterprise Linux and worker Red Hat Enterprise Linux, you can do that, but you need to plan your upgrade or maintenance activities. It would be better if you choose CoreOS for both. CoreOS would be a better choice in terms of maintenance activities or upgrade activities in the future. If you cannot afford that, you can go with the Red Hat Enterprise Linux operating system, but you need to do two upgrades. You first need to upgrade the control plane and then you need to separately update your worker nodes. That is the only thing you need to keep in mind.

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

RHEL provides features that help speed deployment. I am currently learning how to take advantage of those features.

As far as deployment goes, I build a golden image VM and just deploy the images themselves. I don't really use any RHEL tools specifically for the deployment portion.

The solution is constantly expanding and moving into new areas, like jumping into the cloud.

I need more experience with their self-monitoring tools. That is the one area where I feel like I am lacking. I am still using a lot of the stuff that I learned in the Unix realm. I haven't really matured into using the specifics that are being supplied. I am a member of the accelerators team and have been exposed to some of these tools through their lectures. I am starting to play with them a little bit, but I have not fully gone into that arena. So, there is improvement needed on my access to RHEL.

I would rate the solution as 10 out of 10.

I rate Red Hat Enterprise Linux nine out of 10. 

Red Hat Enterprise Linux has built-in features, but we do not use them. It is one of the things about which I need to talk to our account manager. There are so many different ways to skin a cat. My department has so much money, so they bought everything, but a lot of the security features, such as SELinux, are disabled for us. We handle the firewall rules, access lists, and other things at another location rather than on the actual VM itself. It does not hurt to do it at multiple places, but operations-wise, it would be a nightmare, so we try not to do it. I know there are a lot of cool new things built in Red Hat, and that is something we should circle back and take a look at.

I have seen Red Hat Insights. I clicked on it one time when our account manager was showing us something. They have so many features in the cloud that we do not know we can use. Maybe it is wrong to assume, but the reason I do not look at Red Hat Insights is that a part of our patching is already included. We are not that strict about what we patch in terms of the versions. It is useful, but Red Hat emails us anyway. They tell about the severity of an issue. We do not look at Red Hat Insights. We see those emails and we see CVEs. If a package is installed and applicable to our VMs, we just use Satellite and patch that particular vulnerability. 

I have also tried the web console once. It looked interesting, but we do not have much use for it because a lot of our customers or application owners are server admins. About 99% of our Red Hat installs are all minimal installs. We do not have a GUI. There is just a terminal screen. Even though they could console in and do whatnot, it is all done via SSH.

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

For its use case, I would rate Red Hat Enterprise Linux a ten out of ten.

Overall, I would rate it nine out of ten.

I give Red Hat Enterprise Linux a ten out of ten. Red Hat Enterprise Linux is the best thing I have.

We always install a minimized Red Hat Enterprise Linux system for our customers. If they require more features, we provide them as requested.

Red Hat Enterprise Linux is the most perfect OS I have ever worked with. It is nice knowing when we have to use the OS and when we don't.

All Linux solutions are open source, but Red Hat Enterprise Linux is a commercial product that includes support and frequent updates. Red Hat Enterprise Linux can be downloaded for free, but it is not recommended to use it without a subscription, as it will not receive security updates or bug fixes. Red Hat reinvests a portion of the subscription revenue back into open-source projects, making it possible for other organizations to use these technologies for free.

Maintenance requirements depend on our needs. If we only want to have a server and install updates every night, no additional maintenance is required. Red Hat Enterprise Linux does not require any special support. However, if we want to ensure that the system time is always correct, that all updates are installed within a month, and that the system reboots after updates are installed, we will need to perform some additional maintenance tasks. These tasks can be automated to ensure that our system is always running smoothly. We currently have three people for the maintenance. We currently have 900 systems.

I recommend evaluating multiple Linux solutions and conducting a proof of concept because, although Red Hat Enterprise Linux is a great operating system, it may not be the best choice for every organization. I do not recommend using Red Hat Enterprise Linux on a new laptop because the versions included in Red Hat Enterprise Linux are typically two to four years old. This is because Red Hat Enterprise Linux is designed to be a stable OS, and newer versions may not have been fully tested and may have issues. If we have a server or software that is certified for Red Hat, then I would always recommend using Red Hat Enterprise Linux.

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.

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

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

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

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

We have approximately 14 servers running Red Hat 6 but we used Red Hat 6 all the way to Red Hat 8.

The AppStream feature is something that we have tried but on a very limited scale. We have had mixed results with it, although it looks promising. At this point, I can't say whether it is a good feature or not.

My advice for anybody considering Red Hat depends on the role of the person that is making the decision. If they're an end-user or their organization is using office productivity software, then they're probably not going to want to use it for the backend. This is because there are not a lot of users that are using Red Hat as their office productivity operating system.

If on the other hand, you're somebody that's looking for servers that just need what they call five nines or high availability, Red Hat is your solution for that. That's what I would say to anybody, any technical person that I've talked to, if you can afford it, definitely get Red Hat for your web development. Your web servers should be either Apache, or NGINX, which is their web server stuff.

Red Hat should also be used to host an Oracle database. We found that that works really well and is very competitive with Microsoft's SQL server. It's about the same cost; the Red Hat product is actually a little cheaper than Microsoft's SQL product.

Considering the cost, ease of deployment, and ease of use, Red Hat is the better product for your main infrastructure. For things that just have to be up and running, Red Hat is the product that you want to use.

I can't be strong enough in my opinion that Red Hat does what it does very well for the mundane tasks of infrastructure. For instance, when it comes to web servers, no other OS does a better job than Red Hat for web servers or databases. Similarly, it does a very good job for proxies. For things that just need to run and have very little human interaction, Red Hat's your solution. If you're looking for something that's for an office, such as for accounting, then Red Hat is not the solution to choose.

I would rate this solution an eight out of ten.

I would advise paying for the enterprise-level support at least for the first year.
For sure, it is expensive, but it would be helpful. With experience, you can downgrade to the second level.

We have had some issues with container compression that broke everything. So, I don't recommend using it if you don't know how to fix everything.

The biggest lesson that I've learned from using this solution is to read before starting the implementation.

I would rate it a 9 out of 10 because there is nothing perfect.

We're exploring more automation features. Three years is still relatively new for an operating system for our department. As we explore more automation-rich features and tools and subsets of tools, we'll be able to utilize the solution better. Red Hat Enterprise Linux may be very good at it, but our knowledge and experience are still growing. We need to take a deeper dive into implementing automation.

We use Red Hat Enterprise Linux with Microsoft Azure. We did not have concerns about using Red Hat Enterprise Linux in the cloud because we had spoken to other customers of Azure that had been running Red Hat Enterprise Linux. We can install Red Hat Enterprise Linux on our own, or we can use the custom-built Red Hat Enterprise Linux images available through Azure. It makes the deployment of a server much quicker and more efficient.

We have been migrating some workloads and applications from on-premise to Azure. However, we do not constantly move workloads back and forth between Azure. It's more of a one-way migration. We're trying to be less on-premise and more in the cloud. There's definitely a learning curve for the migration. There were some hiccups with learning how to do the migrations. We've done a handful of migrations so far, and each time, we learn from our previous experiences and mistakes. We use our lessons learned and have a better experience each time that we do a migration. It's getting smoother each time.

The knowledge base offered by the product is really good. There are a lot of resources available on the website. We have a direct contact for support, which we utilize on a regular basis. We have enterprise licenses, so we pay for support. We get support whenever we need it. I have been involved in Red Hat Enterprise Linux upgrades. It's pretty straightforward. We just convert from different Linux operating systems to Red Hat Enterprise Linux. My technical team has used Red Hat Insights, Image Builder, and Convert2RHEL.

We keep pretty close to the most current versions of Red Hat Enterprise Linux. There are many different versions of the product. Version 9 is the most current. We're trying to stay up with at least one or two versions close to the most current version to stay updated. We don't want to get to a version that would be at the end of its life.

The solution has helped us streamline and optimize our infrastructure for any applications or databases we run on a Linux operating system. They help us save on our physical resources because they're less demanding. Therefore, we don't have to spend as much money on a server that has a lot of CPU and a lot of memory. We can fit many more VMs on a single physical virtualization host because it's optimized. The support is great, and we can find quite a bit of information either directly through the Red Hat website or through the Red Hat community. We're able to do research on our own and find most of the information that we need. If we can't, support will assist us.

Overall, I rate the tool a ten out of ten.

We use AWS and Microsoft Azure as our cloud providers. We don't use the off-the-shelf product that we get from the cloud. We build around it because we have a standard template. When we deploy our solution in the cloud, all the security features we need are already within the OS, as opposed to using the cloud OS and applying all the changes we need. It's easier to get our template to the cloud and use it.

The licensing for the cloud environment is totally different than the on-premise one. We use the Virtual Datacenter license on-premises. I don't see any difference because Red Hat Enterprise Linux still supports it, whether on-premise or on the cloud.

Red Hat Enterprise Linux knows its product. Whenever I have an issue, an engineer gets assigned to me. I can always escalate if needed. We're not using every host that we license. We ensure that we can fail over smoothly on every single hypervisor. It's fair to license them. We're not using it, but we're still paying for it. I do not like it, but it is a business cost.

We migrate workloads to the cloud. I never upgrade an OS. I usually replace the old OS with a new OS and migrate the application. I use the OS versions 7, 8, and 9. The migration is pretty straightforward. AWS and Azure have a tool that we can use to integrate with our environment. It's a lift and shift. We grab the VM from our on-premise hypervisors and move it to the cloud.

We use Red Hat Ansible Automation Platform mostly for patching and upgrading to the next revisions. We don't upgrade from one OS to another. We build on a new OS and get all the applications running there. Once the application is running, we move all the workload from the old OS to the new OS. There's no impact on the existing system.

I don't do the day-to-day patching because we have a managed service. However, it does create interruption. When we do a patch, we have to reboot, especially when there's a kernel update. It causes an outage. I have used Red Hat Insights. It gives us insight into what's happening on every single Red Hat VM that we have. It tells us if it's behind or has some performance bottlenecks. It gives us visibility on the health of the whole OS.

People who are looking into the product must get a good account manager. We must have a good account manager who we can always contact and who gives us all the updates that we need. They keep us in the loop on what is happening in the Red Hat world. We are satisfied with the product.

Overall, I rate the tool a ten out of ten.

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

We have ten people that are using the solution in our organization.

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

My company is a private cloud company. Mostly, we have our own private services, providing private cloud services to the customers. But we also provide public clouds like Azure and some Amazon clouds.

Regarding resiliency, it is a good standardized OS with stability. But sometimes, it is a little slow in reaction to problems that might appear. For example, we had this big Java Log4j bug where their reaction was very slow compared to other distributions. Of course, they found the solution when they had it, but it was quite a slow reaction. In general, it's a very stable OS.

Regarding how easy or difficult it is for you to move workloads between the cloud and your data center using Red Hat Enterprise Linux, I don't have any solution for that. I have to migrate it manually right now.

Regarding the cost-saving capability of the solution, I would say that it is possible to save on costs because of the automation we use through Red Hat Satellite for maintenance and how we have managed automation, time to spend on the service, maintenance, test, problems, etc. So, you can say that it's been a cost-saving procedure.

I rate the overall product a seven and a half out of ten.

I rate Red Hat Enterprise Linux nine out of ten. My advice to prospective users is to try RHEL out and see if your application works. In the long run, the benefits will outweigh the time and effort spent migrating. The important thing is to ensure you run programs in parallel so you can accurately evaluate the benefits and make a case for switching.

I have used Satellite and Ansible in other environments. Satellite integrates very well. It's built by Red Hat, so it integrates thoroughly and it allows a single point of download for all patches and any software deployments you have. You can automate server builds, if you do it right, and make things a lot easier.

Ansible can tie into Satellite and RHEL fairly easily. It allows you to build multiple types of deployments for multiple solutions, and allows a playbook-type deal. You develop a playbook and send it out and it builds a server for the user. Done.

It would speed up deployment and make it easier to manage. If you had a developer who needed to throw up a box real quick to check something, he could run a playbook, throw up a server and rather quickly do what he needed to do. Then dismiss the server and all resource reviews return back to the YUM. If it was hardware, it would be a little bit different, but if we run a virtualization environment, they return all resources back to the host. So it made matching servers and deployment a lot simpler and less work on the operations environment.

The best advice I could give is if you're going from a Windows environment to an RHEL environment, there's a learning curve that is going to be a factor during implementation management and basic administration. Your company would probably need to hire new people just to support an RHEL environment. Between SUSE and RHEL, the number of people who know SUSE very well in the US is not as high as it is in Europe. RHEL has become more of a global OS than SUSE, though they're both comparable. I would advise looking at what you need it to do and then make sure you have the infrastructure, people, and manpower to support it.

There's a huge number of resources out there. You have sites geared specifically for RHEL administration. I believe IT Central Station has some resources on its site as well. There are Usenet groups and different forums. TechRepublic has a large number of resources as well. There are numerous resources out there to ease the learning curve.

There are a lot of things I've learned over the years using RHEL. Running it as a virtual design environment where you can run multiple servers on a single hardware piece makes it a lot more cost-effective and you don't have the resource depletion as you would have with Windows. Unfortunately, Windows is a resource hog. RHEL can be set up to run very minimally, with virtually no overhead other than the applications you're using to service users. 

I would rate it a nine out of ten.

I rate Red Hat Enterprise Linux nine out of 10. 

We haven't used the image builder tool or insights, but it's something that we might explore in the coming months. 

I'd rate it a ten out of ten. It's very customizable and very supportive. It never seems to crash. There could be better integration with apps, but from an OS perspective, it's excellent.

Overall, I'd rate Red Hat Enterprise Linux a nine out of ten.

Red Hat Enterprise Linux's built-in security features, in terms of simplifying risk reduction and maintaining compliance both maintaining compliance and security, are essential aspects. Compliance requirements vary across different industries, such as banking, with each industry having its specific rules. However, security is a common concern that applies universally. Therefore, we need to address both areas.

Red Hat Enterprise Linux provides various logs and event triggers that assist in monitoring the operating system's security. Since the operating system sits as the layer between the hardware and the application, it plays a crucial role in safeguarding against security breaches and penetration attacks. A secure application relies on robust application security, followed by a well-protected OS. By ensuring the OS's security, we can establish a strong foundation for the entire ecosystem. If the OS is secure, we can confidently state that the application is at least 80% secure.

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

To anyone interested in using Red Hat for the first time, I would definitely advise starting with the GUI because now, the GUI option is quite good, and you can do all the things. After that, you can slowly start moving to CMD. For learning, there are a lot of resources available online, such as YouTube and LinkedIn Learning, whereas Red Hat Academy is quite expensive.

The biggest lesson I have learned from using this solution is that when you're using the command line, you need to be extra careful. That's because when using the command line, a single slash can make a huge difference. That's what I learned at the start of my career.

I started with Red Hat Version 5. Now they have version 9, which I haven't used, but if I just consider the evolution from version 5 to 8, 8.2, or 8.4, there has been a huge difference because, at that time, people were scared of using Linux, but now, things are different. There has been a revolution in terms of OS. A lot of things are being changed, but in terms of the things that we do, for us, it is the same because we are doing system administration. As a system admin, there is nothing different for us. We are doing the same things again and again because the applications require the addition of storage.

There is also a change in terms of security features. If I compare the old versions with the new versions, in old versions, adding any exception in the host firewall was a real task, but now, things have either become smooth, or we have gotten used to it. Overall, for me, things have become easier. They are getting more and more secure, but with the vulnerabilities and the assessments that have been done, we need to keep updating. Now, everything has caught up with the latest security required in the market.

In our environment, we're using virtual servers. There are no physical ones. We are shifting to containers in my current organization. Most of the applications we are using are containerized, and it has been easy for us to manage those applications. However, we also require some in-built applications, and for that, a change in people's mindset is required. It's not about the OS; it's about the people who do the development. It is becoming a bit hard for them because they were using a different platform previously, and now, they need to move to the Linux platform. It is a little bit different for them.

Overall, I would rate it an eight out of ten. When comparing it with AIX, AIX is a bit easier in terms of use and it also has the Smitty tool.

I rate Red Hat Enterprise Linux nine out of 10. I've been pretty happy with RHEL over the years. That's 20 years of Unix right there. I tell anybody coming into Linux or Unix to learn the program. Scripting is your best friend, and you can't understand automation if you don't understand basic scripting. 

If you've never seen Unix or RHEL before, go to a class and learn how to do it in a lab so you don't have to screw up your job. Once you're comfortable with that,  start learning containers because I firmly believe containers will replace how we do most of what we do today.

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

Red Hat Enterprise Linux is deployed across multiple locations in our organization with 95 percent of our employees that use it.

To ensure optimal performance and security, we must prioritize installing operating system updates as they become available.

Taking the Red Hat administration course beforehand will significantly ease the user experience when using Red Hat Enterprise Linux.

I'm a customer and end-user.

I'd rate the solution eight out of ten. 

Overall, I would rate the solution an eight out of ten. 

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

Red Hat Enterprise Linux is deployed in multiple environments, including pre-production, user acceptance testing, and system integration testing. Our Red Hat team, the development team, and another team utilize Red Hat Enterprise Linux within our organization.

Each processor architecture has a distinct version of the software.

The Red Hat exams are not solely based on security but also on performance. It is a challenging skill to grasp, but once learned, Red Hat Enterprise Linux will be flawless.

I highly recommend Red Hat Enterprise Linux, particularly for production environments, due to its stability and enhanced security features.

The most valuable lesson I have learned using Red Hat Enterprise Linux is that the entire Red Hat ecosystem is perfect. All the open-source projects can work together, especially for DevOps or when implementing valid automation or containerized applications. If we need to deploy a centralized application, we will use OpenShift. And if we want to perform tasks on OpenShift, we will use Ansible as an automation platform. If we want to upgrade or manage our environment hosts in batches, we will use Red Hat Satellite. If we have applications and want to create an environment for them, we will use Red Hat JBoss. If we want to run high-availability clusters or high-performance computing clusters, we will turn to Red Hat High Availability Clustering. Working within the Red Hat ecosystem is perfect.

It has a strong security posture. I did a SELinux contract for my current company. Compared with open-source alternatives, Red Hat Enterprise Linux provides better support services and reliability. Also, we are rolling out a new Ansible platform for insights. It gathers information about how many jobs we have, how long they take to complete, etc.

We need to manage vulnerabilities for a massive base of clients' systems. We don't use open-source apps for it like Red Hat. We have a third-party tool as we straddle different compliances. However, Red Hat is great about security announcements. I can call them anytime for an update as well. But it is challenging to work with the vendor for scanning machines. It does not know how to work with Red Hat packaging version numbers.

I rate the solution a nine out of ten.

In terms of the portability of applications and containers built on Red Hat Enterprise Linux, I don't know how much that applies to us. In our case, someone develops an application in a Podman container, and we ingest that and run it, but we're not doing much more than that. So, all of the Java-based applications that we run, are run within a couple of different containers, and that's about it.

I personally use Red Hat Insights in my home lab. We can't dial out for that for a lot of customer-based work, but I personally use it. It hasn't helped avoid any emergencies because it's super low risk for what I'm using it for, but I can see the benefit of it. In a more enterprise setup, such as health care where I used to work, things probably would have been interconnected, and we would have been using Insights, but we're not using it currently.

Overall, I'd rate Red Hat Enterprise Linux a 10 out of 10. 

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.

It is important to ensure there is a level of training for implementation. You need to understand compliance for your organization to determine whether vendors can provide appropriate tools. 

Do not be afraid to ask questions once the solution is implemented in your environment to ensure you are where you need to be. 

Stay on top of version or patch releases to prevent bugs or security vulnerabilities to your ISSO or agency. 

I rate the solution a seven out of ten. 

I rate the solution an eight out of ten. 

I rate Red Hat Enterprise Linux 10 out of 10. Red Hat Enterprise Linux is an affordable product and a great value. It is constantly evolving and adding capabilities. We can orchestrate a multi-cloud environment for Nutanix under Red Hat Enterprise Linux. It's an excellent product for virtualization.  

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

For those who are looking at other open source cloud-based operating systems for Linux, I would recommend Red Hat Enterprise Linux. It is well-documented and has a large pool of information available. We can also use CentOS content with Red Hat Enterprise Linux. The pool of information for Red Hat Enterprise Linux is far greater than some other open-source solutions.

The environment in which we deployed the solution is enterprise-level.

We run some applications on the cloud, but they are not business-critical applications. We run all business-critical applications on-premises. We are not dependent on the cloud for business-critical applications. We are not locked with the vendor.

We use Qualys to scan the underlying node. We expect any critical vulnerabilities to be patched as early as possible. We have an enterprise policy wherein any business-critical vulnerabilities seen on business-critical applications or nodes need to be fixed within 30 days. If some running application is exposed to the internet, we want that to be prioritized. If vendors can prioritize a 30-day life cycle for critical vulnerabilities, that would really help many other organizations.

Red Hat Enterprise Linux is the only option we are currently looking at. We don't want to go with Windows. We already have this ecosystem where we use OpenShift, and it's already integrated with ACS. So we would not like to go with any other different OS. Red Hat Enterprise Linux will integrate easily with the entire ecosystem.

Overall, I rate Red Hat Enterprise Linux an eight out of ten.

I would rate this solution as nine out of ten.

My advice is if you're actually testing, you don't need to go with this solution. If you're an advanced Linux user or server administrator, you will definitely require Red Hat because many of the latest solutions require dependency-based repositories. It will be very easy if you're active with this operating system.

This has a set of repositories built into the database. We don't need to go anywhere to set up all of the databases and repositories. Everything is embedded into the solution.

If you're looking for HPC and NVIDIA clusters, most of the supercomputers need to have the solution, so it's better to have it equipped with that.

Look at the security features of the solution and compare them with other options. Open source is great, but at the end of the day, you need someone supporting the product. Another option is to just listen to groups that write on the internet, but you have to decide if you trust that along with their adversaries. 

Government offices have to worry about adversaries from other countries because the code they use is unclear. The idea of open source is to be able to evaluate the code but it is not clear if anyone actually reviews it. 

I rate the solution a ten out of ten. 

My biggest advice would be to read the documentation and reach out to Red Hat, or even just search the internet, so that you understand what you're getting into and what you're implementing.

I can't think of very much that needs to be improved with RHEL. The model that they have for maintaining patching, and their cadence on Zero-day attacks is fantastic, and their support is really good. I don't see any issues.

My company uses the normal security features provided by the product. Presently, I am taking some courses related to security. My company uses solutions for security purposes, like CrowdStrike Falcon Protection.

I use the documentation provided by the product. I also joined the academy operated by Red Hat Enterprise Linux (RHEL) to learn about courses related to OpenShift and virtualization. The documentation is very easy to understand, and it is also good for learning purposes.

I joined the product's academy courses when Red Hat opened a new branch in Egypt. I have got certificates for learning about OpenShift and virtualization. I am planning to learn OpenStack.

For provisioning and patching, I use Foremen, which is an open-source product implemented by Red Hat Satellite. Foremen is very good and easy to use for patching and security updates.

Leapp or Red Hat Insights are not features that are enabled by default. I don't usually use the aforementioned in the product.

I use Red Hat Store for image-building purposes. Some other programs are installed after the images get installed with the help of the product.

Speaking about whether I use the web console or Convert2RHEL, I would say that I use the terminal console provided by the product, and it is also very easy for me to use.

The product has affected my company's security and uptime since Linux offers a firewall that provides complete security, which is very good.

I hope to use the product in a hybrid environment.

I need to prepare for security standard certifications from Red Hat Enterprise Linux (RHEL) since it can help me understand the features and the security that I need to get from the product for my company, making it something very important for my organization.

Red Hat Enterprise Linux (RHEL) is a big part of my company since we use a lot of servers with its open-source services. Red Hat Enterprise Linux (RHEL) serves as the base of the servers in our company.

Sometimes, I take care of the maintenance of the product, but it is not something that is required all the time. The maintenance process is pretty normal.

As a part of our company's migration or upgrade plans to stay updated, I will be upgrading from RHEL 8 to RHEL 9.

The product does what it is meant for, especially if MariaDB is installed over the tool.

I rate the solution a nine out of ten.

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 would rate Red Hat Enterprise Linux a nine out of ten.

The amount of people required for Red Hat Enterprise Linux maintenance depends on the type and size of each project.

Red Hat already provides tools to maintain up-to-date migration plans. These tools can not only identify which components require upgrade but also preserve any already installed elements. Additionally, Red Hat offers a web-based solution for managing upgrade processes if required. However, we can choose alternative options: implementing the solution ourselves or employing open-source software for upgrades. I see no significant challenges with utilizing Red Hat tools for the upgrade process.

I recommend evaluating all the available solutions that offer the tools that Red Hat Enterprise Linux offers and comparing their functionality and cost to avoid issues after purchase.

Overall, I would rate the solution an eight out of ten. 

We test Red Hat Enterprise Linux 9, the latest version. We do backtesting for versions 7 and 8 as well. The product is very secure. It took me a while to wrap my head around the whole Subscription Manager system and understand how that worked. Even at a base level, it provides a much higher level of security and the ability to take remediation steps if things go wrong. You can shut the whole system down and bring it back from the ground up.

From the keynote, it looks like steps are already being taken to make the solution more accessible to any regular user. 

The product does a really fantastic job of reducing the overall risk to the user. If a user is doing something they’re not supposed to be doing, it's very easy for the system administrator to walk them out of doing it. As for maintaining compliance, if a user is only meant to have specific packs and is only meant to perform specific tasks, it's very, very easy to lock it into only being able to do that one specific thing.

Most people in IT enjoy a little learning. Everything I've done so far with Red Hat has been installing, setting up the account, getting everything registered, and then worrying about testing to validate. It is difficult to start with, but the more you learn about it, the easier it gets. The more I use it, the more capabilities I find within the system.

Overall, I rate the product a nine out of ten.

Overall, I'd rate it a nine out of 10. There's always room for a little bit of improvement.

I give Red Hat Enterprise Linux a nine out of ten because there is always room to grow.

Someone looking at an open source, cloud-based Linux OS instead of Red Hat Enterprise Linux should consider what is being used in their customer base. If they are putting something up there as a proof of concept, then dabbling in open source is fine. However, if they have customers relying on them and they want minimal downtime, then they need Red Hat Enterprise Linux.

The knowledge base can be a bit cryptic at times. We can go in there and read the same information that's in the documentation, but sometimes it's not clear enough. So I'll often go to a half dozen other websites that tend to give us examples and other helpful information. The knowledge base is a good place to start, but it's not the end-all-be-all.

I use Ansible Builder to build my containers. However, I do not use Red Hat Enterprise Linux’s image builder tool.

We do not use Red Hat Insights yet, but we're planning to use it in the near future. As soon as we get more servers in our environment, our firm’s directors might decide to start using Red Hat Insights. Right now, we are just using Automation Analytics. The solution’s resiliency is pretty solid.

We implemented the solution because we wanted automation. We cannot install Ansible Automation Platform in operating systems other than Red Hat Enterprise Linux.

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

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

I make the applications compatible with the cloud so we can migrate the data.

The knowledge base offered by Red Hat Enterprise Linux is good, but I don't use it much because the infrastructure team manages issues with the OS. I only check the documentation when an application is not working as expected. 

It is very stable, and you can easily run a lot of production workload on RHEL. Red Hat products are well established. They have been around for many years. Red Hat is dealing with multiple products and applications and is constantly doing research to develop new products according to industry trends. With RHEL, you can get an end-to-end solution with their multiple products, which is something not available through other vendors. 

Red Hat's open-source approach was a factor when choosing RHEL. We are utilizing a lot of open-source solutions in our Test and Dev environment before going into production. We are able to get a lot of information in the open-source community, and we also have local community support in our region.

Its newer versions enable us to deploy current applications and emerging workloads across bare-metal, virtualized, hybrid cloud, and multi-cloud environments, but the older versions are not supporting these features. They have included more features in the newer versions to integrate and merge with other applications that are on-premises, in the cloud, or in a hybrid cloud setup. In the older versions, we faced some issues in moving some of the applications from on-premises to the cloud, but in the newer versions, it is very easy to move or merge to the cloud. The applications that we have deployed across these environments are very reliable, except for the bare-metal. They are not much reliable if we are using a bare-metal solution on-prem. For virtualization, we are not using the native RHEL virtualization. We have VMware for virtualization, and it is okay in terms of directly deploying some of the applications to the public cloud. It is quite reliable.

It doesn't simplify adoption for non-Linux users. For non-Linux users, it is somewhat difficult to manage this solution or have this solution. However, as compared to other Unix platforms, RHEL is okay.

We are not using RHEL to run multiple versions of the same application or database on a specific operating system. In a specific operating system, we are running an application according to our end-user features requirements. We go through a lot of documentation and do multiple PoCs for deploying an application on the RHEL platform. We have a lot of user acceptance test procedures for each application in terms of how we have to do benchmarking and what are our requirements. So, we are managing with an individual operating system and not using the whole centralized solution.

We use automation tools to move to the cloud. When we are planning to move to the cloud, we do multiple cloud assessments for which we have third-party tools as well as in-built RHEL tools. Each vendor has a different way of migration and automation for moving the on-prem workload to the cloud workload. Each vendor gives you different tools, and we follow the best practices given by them while moving the on-premises workload to the cloud.

I would rate RHEL an eight out of 10.

We are not working in a hybrid environment. I work with the Dutch government, and the regular cloud solutions are not sufficient because of data safety.

Moving workloads between the cloud and our data center using Red Hat Enterprise Linux is not really an issue. The network connectivity is good. The data storage is fast enough. Cloud vendor lock-in is always a debatable discussion. Whatever we do, we always get vendor lock-in. We just choose what works for us at the moment.

The cost savings are mainly in time. We don't have to figure out everything if there's a priority-one issue. We can raise a ticket with the vendor and ask them to help us. It saves us costs. The savings are mostly in time because the product is not cheap. If you compare it to a free Linux OS, the total cost savings will be about the same. Our level of stress and effort is far lower. It's the real saving.

When my Red Hat Knowledgebase account works, it works fine. However, there are some issues at my company. I cannot log in sometimes. It's not Red Hat’s fault.

Look at what your priorities are. Do you want to switch fast, run the latest stuff, and be agile? Then, use open-source tools and contribute to that community. If you work for a big enterprise and mainly want stability, choose Red Hat Enterprise Linux.

I’m very happy with the solution. If someone is a technical person, they must get some training and an in-depth technical course on Red Hat Enterprise Linux. It will help them a lot. Although it is Linux, it is very different from other open-source Linux packages.

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

The solution is self-explanatory. Most applications run on Red Hat Linux and related products.

I rate Red Hat Enterprise Linux a nine out of ten overall. I don't think RHEL is exactly perfect, but it's a trusted, easy and well-supported solution. They are constantly improving and trying to make it easier. 

We have plans to increase usage. Every new application that supports running on Solaris or Linux is going to be deployed on RHEL these days. I hope it will be our major operating system in the data center. So, in the foreseeable future, there would only be two operating systems: RHEL and Microsoft Windows.

I would rate this solution as nine out of 10.

They are a great company overall. It is hard to say where they could improve. They have user groups. They put out a lot of messaging and information. The solution is easy to learn and get to know their products and what they do. From a personal standpoint, I have everything that I need.

If I wanted to run multiple versions of Node.js, there are ways to do that without using AppStream. More recently, I have been working with different versions of Node.js, having it in different versions on one machine. It works well. Just the fact that I have the capability is great.

Among the other distributions of Linux out there, I would rate it as 10 out of 10. If I have to compare this solution against everything else out there, this solution is at the top of the list.

I'm an end-user of the solution. I had admin-level access to the product.

Red Hat Enterprise Linux does not enable us to achieve security standard certification.

I'd rate the solution ten out of ten. 

Red Hat has not personally enabled me to achieve security standard certifications in the projects I've worked on but I could see how it would help. 

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

We do a lot of patching and upgrading with Ansible and we keep the host up to date all the time.

I've had a very positive experience with Red Hat Enterprise Linux. My only point of comparison is Ubuntu, which I use for personal projects. 

Red Hat Enterprise Linux is a solid enterprise product with a greater emphasis on security. However, Ubuntu Server is easier to use in many ways compared to Red Hat Enterprise Linux. This may just be a matter of familiarity, but I find it easier to get current versions of Ruby with Ubuntu than with Red Hat Enterprise Linux. 

This is based on my somewhat limited use, but it's my impression nonetheless. That's what keeps it from being a ten out of ten.

We use the on-premise, cloud, and hybrid versions. We have deployed it on AWS, Microsoft Azure, and Google Cloud. Most of our infrastructure is in the Azure cloud. I work in the server infrastructure team, and other data collectors work on AWS and GCP. We haven't used the tool's features like the image builder. 

The product supports our hybrid cloud strategy. We have been migrating using tools from Microsoft Azure. Its knowledge base is good. Sometimes, finding an article is difficult. However, once I reach them, it contains good information. 

We used Azure's tools for migration to the cloud. It is straightforward. We have no problems deploying the servers. Our main strategy focused on data centers.

We use the Leapp tool to manage the upgrades. It works smoothly on our Oracle databases. Leapp is straightforward to use. 

We use Red Hat Insights quite a bit. I have not explored all the features yet. We use it to look for events our monitoring hasn't picked up. It also helps us with tips and hints for fine-tuning applications like SAP and Oracle. We go by these recommendations and follow them to put the applications in place. I have downloaded the Playbooks for remediation. 

I use system rules for SAP tuning in Oracle. I do not use the image builder since we already have a process to do the server builds. I use the web console once in a while. 

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

We're a Red Hat customer. 

I'd rate the solution nine out of ten. 

For customers looking for alternatives to Red Hat Enterprise Linux, my advice would be to choose something that aligns with your requirements and that you are happy with. Don't just pick something because it's cheap. You gotta look at the long term. Also, know what is needed for your project. For example, if you have issues, can you get those issues resolved in a timely manner? If you run into an issue, you're stuck, and they can't help you out, this means your project will be delayed. You will need to weigh that out.

It is important to make sure your patches are up to date. Any part of regular maintenance should not be skipped. 

I recommend the solution because it is stable and easy to manage. I rate the solution an eight out of ten. 

The portability of applications and containers built on RHEL can be quite complex at times because some applications, data containers, and other aspects are not compatible with Linux, as compared to the Windows Azure solution. Some applications that are built by Microsoft or Oracle might not run on the Linux version because of compatibility. But the majority of applications are integrated and compatible with Red Hat Enterprise Linux. It is quite flexible for integrating third-party applications, that's not an issue. But you need some configuration-level changes and will require additional setup for those applications.

We have our own application development and some of the development teams are working on the Linux-based open-source system and some are working on Windows. But we need people with certain skill sets who can comfortably work on Linux because it requires different methods for working with the computer, as opposed to Windows which is a graphical user interface operating system. That is the main challenge, finding Linux-based resources to do work.

If you have requirements related to an open-source platform or open-source applications like Java or Python, Red Hat would be a great choice as it is an open-source platform as well. It has the features and the community and those are the most important things.

Some of my customers use OpenShift, many of my customers use Ansible, and a lot of them use a local Docker and Podman. The ones that actually run within Red Hat integrate just fine. The ones that Red Hat runs on top of, those are a little more difficult to speak to. Running Docker inside of RHEL is easy. It is much better on EL8 than it is on EL7.

I like it enough that I use it as my own operating system for my personal web and mail server. So, I would rate it as eight or nine out of 10. The primary hits against it are that if you want to do anything bleeding edge, the pursuit of stability works counter to that.

You cannot compare it with anything that is in the market because there is nothing that does the same. Amazon is doing something similar, but it is still a different service. Everything that they give us surprises us and changes the way we are doing things.

It hasn't simplified adoption for non-Linux users because we have mostly deployed servers, and they are not visible to the users. Users are just using the applications, and they don't know what is going on in the background. They don't know if they are using Linux or something else. They are using Windows on the client, but on servers, they don't know what is running.

We aren't using bare metal for servers. Everything is virtualized and working just fine. We have VMware, OpenShift, etc. Everything is deployed on our own cloud, and everything is on our server.

We use the dashboard of OpenShift to monitor the whole infrastructure, but we also have two solutions that are not by Red Hat. One is Zabbix, and the other one is Pandora. Both of them are open source. The dashboard of OpenShift doesn't significantly affect the performance of existing applications, but it is helpful because it can send triggers. It has triggers to send alerts and things like that. It is not really resource-consuming. It is really good.

I would rate Red Hat Enterprise Linux (RHEL) a 10 out of 10.

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. 

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

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

I recommend using Red Hat Enterprise Linux over an open-source OS because it offers better support.

Red Hat Enterprise Linux requires minimal maintenance.

Red Hat Enterprise Linux is a reliable solution and I recommend it to others.

To those looking into implementing Red Hat Enterprise Linux, I would advise making use of Red Hat's community. 

Red Hat Enterprise Linux has had some impact in terms of security, but we have other security measures and procedures. We have not used SELinux and other embedded security features of Red Hat Enterprise Linux.

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

You have to deploy it and evaluate it. You can see that there's a lot of difference compared to other operating systems. It also depends on where exactly you're going. There are mainframes and other different places where you can deploy it. Even on the mainframe, it makes a lot of difference.

With Red Hat, there are a couple of things you need to consider while building your infrastructure. You need to have good hardware, and you need to have a compatibility matrix to be able to have a stable environment. It has to be tested in a proper way, rather than deploying it on any box.

In terms of the golden images created by the image builder tool, we have vendors who come with their solutions. They come with the containers, and they deploy them. Most of them are using GitHub, and we just provide the infrastructure. From a technical perspective, there's a solutions department that's into APIs. They handle everything, and we just provide the infrastructure.

Overall, I'd rate it an eight out of ten. 

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

When evaluating operating system options, keep in mind that Red Hat offers the best support.

Times have changed from when I first started using it. Back then it was just a matter of putting a CD in and installing it. One of the companies I worked for did a lot of homegrown stuff and I used their tools that were like Kickstart. Now it is all automation with infrastructure-as-code. The complexity of deployment is about the same. Some of what we're doing to deploy stuff is outside of Red Hat and it's a matter of finding what tools are available.

We're in the process of deploying something right now where we have different versions of Python. That's the only use case we have with multiple versions on the same server. I don't expect any issues, but it's still early in that deployment.

We have three people dedicated to maintaining the infrastructure environment that we work in. That includes managing Linux servers, the applications that go with them, and dealing with day-to-day tasks like patching. It's the typical life cycle maintenance functions: break/fix, dealing with hardware issues, deploying new applications, and maintaining a VMware environment.

The reason we're using it is because it's stable and we know we can get support. I know there are other versions of Linux, ones that I've used, but I've never experienced the kind of support with those versions that Red Hat has provided. Red Hat is a stable Linux solution provider.

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 would rate Red Hat Enterprise Linux a nine out of ten.

Most of my clients have particularly sensitive information. We tend to run on-premises rather than the cloud because of security issues for those highly sensitive databases. We disconnect those databases from the internet so they are ultimately secure. That is something that you cannot do in the cloud.

Red Hat Enterprise Linux doesn't have any particular standout security features, which the other Linux tools don't have. I've also used the Oracle version of Linux, which seems very similar to Red Hat Enterprise Linux. Both seem to be as secure as the other. If I have to give a score in relation to stability, Oracle's version of Linux might be slightly more stable than Red Hat Enterprise Linux.

All the customers I've worked for have been using those operating systems for a long time. For instance, one of our customers has been using Red Hat Enterprise Linux since it was first available over 20 years ago. A return from that is difficult. They were using Unix rather than Linux. The applications they ran were ported from those environments, and migrating them to Red Hat Enterprise Linux was relatively painless. We did those migrations back in 1995 to 1997.

We tend to use the environment for running databases. So, we have very few real users directly connecting to the system. The people who connect to the system do so by applications.

We haven't needed any maintenance for a long time. My last company was a large organization, and we had the internal expertise to provide support. Some net contributors have fixed bugs themselves and contributed those bug fixes back into the Linux open-source community. It was a huge organization, and its IT department was as big as some software consultancies.

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

We probably purchased the solution from a cloud provider. We are using versions 5 to 9 currently.

The solution’s built-in security features are pretty good, but it's not something that I would take as a major selling point. The portability is good because we have a stable baseline for applications and containers. Red Hat Enterprise Linux’s security posture is pretty good. I don’t know if it's the strongest selling point, but it's up there.

In some ways, Red Hat Enterprise Linux enables us to centralize development. However, that's not mostly what we focus on. The primary output from Red Hat Insights is targeted guidance. Targeted guidance has not affected our uptime much.

It makes sense to go with a stable distribution compared to others. Overall, I rate the product an eight out of ten.

It's easy to install and secure. You can customize it and manage various aspects. It's a good operating system for servers with security. It can run on machines without a powerful CPU or a lot of memory. It's stable.

Overall, I'd rate Red Hat Enterprise Linux a nine out of ten.

It is easy to troubleshoot with RHEL. I would rate this solution an eight out of ten. If you are in the government space and you're looking to modernize your systems but you're not quite sure about the cloud, using OpenShift to containerize is a good first step. It will give you that cloud-agnostic capability so that you're more readily able to move to the cloud when you're ready.

I would rate this solution an eight out of ten. 

I rate Red Hat Enterprise Linux nine out of ten. I would recommend it, but I need to qualify that by pointing out that I don't have enough experience with other Linux flavors to say that it's better than the others. I've mostly used RHEL because it's so ubiquitous.

Red Hat Enterprise Linux’s built-in security features for simplifying risk reduction and maintaining compliance are pretty good. My only exposure is just packet management, but packet management gives me everything that I need.

Red Hat Enterprise Linux has enabled us to achieve security standards certification. We have to stay on top of things because we work with the Ontario District School Board. There's a big emphasis on keeping everything secure, and the solution has helped us to do that.

Right now, our company is migrating to 8.8, and I think we will stay on 8 for a few years. We're doing everything through the images, and we keep everything updated with Ansible. I don't think we have any plans to use any of the automation tools other than Ansible.

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

We use RHEL 7 and RHEL 8 on on-premises. RHEL 8 is on the AWS. There is a security policy like CIS when deploying the solution. You can embed it on the image. I am not sure if there is HIPAA compliance yet. 

Migration from RHEL 8 to RHEL 9 is easy. Upgrade depends on the application that is running on each instance. You need to check if it is compatible with the kernel. We need to plan things before migrating to the latest version. We need to stay current to ensure compliance. We plan to move from RHEL 7 to RHEL 9 and use RHEL 8 and RHEL 9. 

We use Red Hat insights but do not utilize them. It helps with the remediation. I use Image Builder to build AWS and GCP images. I haven't deployed them. 

I rate the product a nine out of ten. 

As a consultant, I handle sizing, design, and optimization for new infrastructures and I would recommend Red Hat Enterprise Linux to anybody considering it.  

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

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

The ease of moving workloads between the cloud and our data center depends on the application architecture. If the application has a monolithic infrastructure, it may be easier to move to the cloud. However, if the application is already running mostly in the data center, it may be more difficult because we would need to recreate all of the infrastructure and topology from scratch. This is because there are so many parts to consider when migrating a microservices-based application to the cloud.

For someone who wants to use an open source Linux operating system, I would recommend Rocky Linux. However, they should be aware that open source solutions do not come with the same level of support as Red Hat Enterprise Linux.

Four network team members are required to maintain Red Hat Enterprise Linux.

The Red Hat knowledge base is good and well-documented.

Red Hat Enterprise Linux is the only Linux solution that is supported for enterprise-level organizations. I recommend this solution for large organizations that want professional support for their Linux systems.

I would recommend it based on the use case and the budget. If it meets your needs and budget, Red Hat Enterprise Linux is the best option.

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

The solution's key element is its cohesive ecosystem between hybrid and cloud environments. It helps clients such as giant banks create a single space for managing workloads in different hyper scalers. This way, it helps in cost management and visibility. It creates a single platform to manage work. It helps in saving costs, especially with subscription plans. It provides them with a consistent cost structure. Also, being an open-source solution has benefits that fit within the ecosystem.

I rate it an eight out of ten, primarily for the support and licensing terms. It helps some of our enterprise clients navigate open-source licensing and export control complexities.

There are areas of improvement, such as the cycle of updates and the ecosystem as a whole. Also, the elements like Ansible are priced separately. For automation, there is an opportunity to combine everything. Even though they are different products, they shouldn't be charged separately from the ecosystem perspective.

We purchased the solution from Red Hat. We use Packer by HashiCorp to build our templates. I am a junior developer. I have been employed with my company for about five months. I don't know the initial issues that led to us choosing Red Hat Enterprise Linux as our Linux solution. I speak from a developer’s perspective because I deal with Ansible.

The product has really good built-in security. The product provides good support, which helps us manage downtime and get the service back up and running, thus producing more money.

Overall, I rate the product a ten out of ten.

Our customers use the solution on multiple cloud providers, mostly AWS and Azure. Our customers buy a yearly subscription for some equipment, and for short-lived instances, they do on-demand pricing within the cloud provider to buy the ones they offer.

I believe Red Hat Enterprise Linux has helped our organization avoid cloud vendor lock-in. We've been able to pretty reliably and easily lift, shift and redesign our application from on-prem to the cloud. It might not necessarily be a huge benefit for us. However, it is definitely a perk, especially in an environment where we have to go through a certain purchasing cycle and background reviews for everything. It does end up helping us.

As much as I've used Red Hat Image Builder, I really like it. Though, I've only had to build a handful of images out of it. We can't use something like Fedora, where you've got a nightly update. Red Hat Enterprise Linux is tested and reliable. Having something they can work on, develop, and use daily is helpful to our customers.

The sosreports and soscleaner developed in recent years are a huge improvement. My customers tend to be pretty fixed in their ways and what they use, so they continue to work and use things for longer than they should, but that's the beauty of Red Hat Enterprise Linux. It is supported, and we still have the necessary reach back.

Red Hat Enterprise Linux is pretty solid. It's been tested. It has its upstream counterparts that ensure that most of the bugs get worked out, and what makes it down into the final testing is strong and resilient. We've been working on moving workloads between the cloud and data center with the customers. Instead of lift and shifts, we try to redevelop their applications instead of spending $10,000 to give 32 cores in the cloud because they had 32 cores in the system.

We have a fantastic team that works with us and supports us. The team goes out of its way to help find cost savings for both us and our customers.

Overall, I rate the product a nine out of ten.

I give Red Hat Enterprise Linux an eight out of ten.

Cloud vendor lock-in is inevitable when we adopt the cloud. This is because once we adopt a cloud service, such as DynamoDB or AWS, we become dependent on that provider for support and maintenance. It is very difficult to work with multiple clouds 100 percent of the time, as this can lead to problems with failover and other issues in multiple cloud environments because the risk is high.

The Red Hat Enterprise Linux ecosystem is more attractive because we are not just buying an operating system. We are buying an ecosystem that helps, supports, and secures our platform. I believe this is the better option.

Applying patches in the new versions of Red Hat Enterprise Linux is more time-consuming than in Oracle Linux because Oracle Linux does not require legacy environments to be patched or changed through applications.

For someone looking for an open source cloud-based Linux OS instead of Red Hat Enterprise Linux, I recommend AWS Linux. It is a very stable version of Linux and does not require a subscription.

Overall, I rate Red Hat Enterprise Linux as a five out of 10. 

I don't see Red Hat Enterprise Linux's built-in security features as effectively simplifying risk reduction and compliance. We use AIX, but still, we face a lot of vulnerabilities from Red Hat that need frequent patching, often monthly. This frequent need for updates, along with the rapid changes in Red Hat Enterprise Linux releases, can be frustrating and lead to instability. In the banking industry, where we take vulnerabilities seriously, these frequent releases and lack of stability can be problematic. 

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

By implementing the solution, my organization is trying to solve the agility issue. Using Red Hat Enterprise Linux, we are not tied to Windows patches. Windows patches break sometimes, and then the application goes down, which is a big issue. With Red Hat Enterprise Linux, we have that reliability and robustness.

I am very impressed with the solution's resiliency.

Regarding how easy or difficult it is for us to move workloads between the cloud and our data center using Red Hat Enterprise Linux, I have found it to be very easy.

Regarding portability, it is easy. I was speaking to someone over there who benefits from containers. I mentioned it to my manager, and we are going to have a discussion about it.

In terms of my assessment of the solution's built-in security features when it comes to simplifying your risk reduction and maintaining compliance, I feel it is good. We haven't ever had an issue ever with the solution.

As nothing is perfect, I rate the overall solution a nine out of ten.

I rate Red Hat Enterprise Linux a nine out of ten. If you don't know anything about Red Hat Enterprise Linux, you should read up on it. It will do everything you want. Red Hat Enterprise Linux is excellent.

I rate the solution a ten out of ten. 

I would advise looking at some of the other operating systems out there and determining what your needs are in terms of if you're going to be using Linux, or if you're going to be using Microsoft. For Linux, it's definitely preferred, but just do your research and do your homework. I can't say enough good things about it.

I would rate it a nine out of ten.

I rate Red Hat Enterprise Linux nine out of ten. It's an excellent solution. Go for Red Hat If you want stability at a reasonable cost. It's the best.

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

I'm a customer and end-user. 

We do not use Red Hat Insights just yet due to some restrictions around sending sensitive information off-premises. We're quite limited in terms of using that feature at the moment.

I'd rate the solution nine out of ten. 

To someone who is looking at open source cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say that if they are looking for an enterprise OS on a cloud environment and they want to have some stability and security, Red Hat is the perfect match for that.

Overall, I'd rate Red Hat Enterprise Linux a nine out of ten.

As an operating system, I would rate Red Hat Enterprise Linux a ten out of ten.

Make sure that you have well-trained engineers who are familiar with RHEL. If you are looking for a solution that runs in a mission-critical environment, you always want a supported solution. If you're looking for Linux, I don't think that there's a better-supported solution than RHEL.

In our particular scenario, our underlying infrastructure is either VMware virtualized or bare metal, although the latter was mostly in the past. Rolling out to a virtualized solution or rolling out to bare metal with RHEL—with the exception of the bits that are unique to those platforms—the operating system installation and the like are going to be very similar.

Overall, RHEL is a very solid solution.

I would rate Red Hat Enterprise Linux an eight out of ten due to the complexity of its network boost management issue.

We have Red Hat Enterprise Linux deployed in one location.

Red Hat Enterprise Linux is used in our environment to run the application for all of our customers, and only around ten people have access to it.

Red Hat Enterprise Linux requires maintenance for applying new patches, releases, and debugging. 

At this time, we do not use Red Hat Smart Management.

The benefit of using multiple Red Hat products is that they integrate well, so I don't have to worry about fitting different Lego pieces together. They just work. I prefer Red Hat over most other solutions since I'm most familiar with it at this point and it offers consistency.

I'd rate the solution nine out of ten.

RHEL provides features that help to speed deployment, although we don't use their tools. We use tools from a third party.

My advice for anybody who is looking into implementing RHEL is to make sure that it is going to work for you. Ensure that it supports all of the products that you need it to support once you've actually assessed all of those things. It is a quality product, there's no doubt about that. Once you have made that assessment, I would say, "Great, go for it."

In summary, this is one of the products that works well and does what we need.

I would rate this solution a nine out of ten.

From a licensing perspective, Red Hat Enterprise Linux is flexible. We leverage our licenses based on the VMware cluster. 

Accessing the knowledge base from the public perspective is challenging. You can get much more from the documentation if you are a supported organization. If Red Hat Enterprise Linux continues to keep the documentation open-source, it will benefit us. 

We leverage Ansible to help with the upgrades. It makes upgrades easier. We rely on a reseller for Ansible AWS upgrades. 

We are shifting our Red Hat Enterprise Linux servers from version 7 to version 8. 

I rate the product a seven out of ten. 

Overall, I would rate the solution a nine out of ten because most of the information I need I could find on the Red Hat website.

The number one advice would be to keep the division between testing and production.

There's one system that you need to set up for testing purposes only, and this testing system can be obtained free of license. There's an evaluation license that can be easily applied. When developing the application on the Red Hat 7 system, stay using the evaluation version until the requirements are fully met, only then should you migrate them to a paid supported version.

The biggest lesson that you learn by using this solution is, you easily reach a point where a single person or a single team can no longer respond to the complexities and challenges of the security or the different versions of the applications. At that moment you need to rely on a serious fused team, that team that is backing the effort.

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

We cannot use Red Hat Enterprise Linux on the cloud because I work as a contractor for the government, and all our development is in a classified area where we can't touch the internet at all.

In the last quarter, Red Hat Enterprise Linux products like Satellite Server and OpenShift stood out because of their ease of administration. I do system administration. When my customers need something, assisting them with these products is easier than giving a long configuration of YAML.

I like Red Hat Enterprise Linux's built-in security features. We use their SCAP features when we do our kickstart and build it.

We were using Docker, and the Docker swarm was trying to get all the containment. We're now switching to Podman and getting our developers to learn that more so we can give them the ability to kick off containers.

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

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

Regarding the problems we are trying to solve by implementing the solution, I would say that it is our operating system of choice. I think the support is good since we have Red Hat Enterprise Linux subscriptions. We get support for all the operating systems from them. It's great and stable.

Regarding the solution's resiliency, it is good. We've been running, and we have over 99 percent uptime all the time. We also do monthly patching and everything, so it works. Kernel upgrades also work as expected. So it has been pretty good.

Regarding how easy or difficult it is for you to move workloads between the cloud and your data center using Red Hat Enterprise Linux, we don't use relative migrating solutions. It's considered a separate environment, but we use the same base image. 

I consider the solution to be the main OS because going with an open source solution like Red Hat Enterprise Linux, you have better support.

The support is great. We also have integrations with other products, especially with whatever Red Hat releases. We have all those integrations available and we can easily take advantage of it.

I rate the overall solution between seven and eight out of ten.

The product’s resiliency is pretty good. It responds fast to security updates compared to some other closed-source vendors. 

We moved from other priority operating systems to Red Hat Enterprise Linux because it saves us costs on the commodity hardware. Overall, I rate the solution an eight or nine out of ten.

I would always advise doing a proof of concept where the client gives out his requirements and you run a proof of concept based on those requirements to make them confident of purchasing the solution. It is always better if a proof of concept is done. This way, everybody knows what they're getting into.

Its built-in security features are definitely helpful, but at the end of the day, you have to go further than using the built-in ones. You have to do a few other things yourself. The built-in features are helpful for compliance, but we, and most enterprise organizations, always want to go further than using built-in features because some built-in features could be more open to risks. We use the best built-in features, but we always want to go further and integrate other features into the RHEL system.

I have used Red Hat Insights only once, and I have not worked much with it, but my colleagues handling monitoring used it. It was helpful for the unpatched system. They checked Red Hat Insights and saw the systems that need patching. We got an email saying that it is a security requirement and that we need to patch them because it may affect the security of the systems. Coincidentally, after doing the patching, we read blogs about security hacks out there for some of the older systems that were not patched early enough.

Red Hat Insights provide us with vulnerability alerts, but I am not sure about targeted guidance. Vulnerability alerts have impacted the uptime, which is something that we take very seriously. Uptime was one of the major reasons we wanted to work with Insights because we didn't want any attacks that would cause downtime.

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

The only inconsistency we've noticed so far is with the server, which might be the only aspect we could potentially raise concerns about. Overall, I would rate it eight out of ten.

Overall, I would rate the solution an eight out of ten. 

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

If you're evaluating this solution, I'd recommend having your own architects discuss your architecture with the local Red Hat personnel in your state. Red Hat Enterprise Linux is a good product, and it could be even better if you know how to integrate it based on the preferences of your organization. So, my advice would be to have your guys discuss your IT architecture with the local Red Hat people and then decide how to specifically integrate your IT infrastructure with the Red Hat software.

Overall, I'd rate Red Hat Enterprise Linux a seven out of ten.

We purchased the solution via a cloud provider. We use AWS, Google, and Azure. The resiliency of the product is the same as other products. 

The solution helped us reduce costs. We use SLES and Windows alongside Red Hat Enterprise Linux. Application support and vendor support for Red Hat Enterprise Linux are better than other products. 

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

We are a bunch of techies here. RHEL is not managed by end users. We don't really mind the GUIs, because the first thing that we do is stop using them. We are using Ansible, which is now part of RHEL, and that can automate the living heck out of everything. For now, we are not using the Power approach, but we may in the future. We are doing a business case for that, as it would be an easy sell for some communities and the use cases are not techie-to-techies.

There is a cloud, but we have very little infrastructure as a service in the cloud right now. 

It delivers to the targeted audiences. Could Red Hat Enterprise Linux be used in all types of other scenarios? Most likely. They have an embedded version for microcontrollers, i.e., things that you put into your jewelry or light switches. However, this is not what they're aiming for.

I would rate RHEL as a nine and a half (out of 10), but I will round that up to 10.

Try the product out. If you decide to purchase a subscription, don't be afraid to submit a ticket or a support case to Red Hat, because that's why you pay for a subscription. It took us a  long time before we started to open support cases, because we thought, "Ah, we can fix this ourselves." But now we use the support system quite often and it works quite well.

One of the things I've learned from using RHEL is that there are applications that work so much better on Linux than they do on Windows.

The product supports our hybrid cloud strategy well. 

We move workloads between different clouds and data sandboxes. 

Red Hat Enterprise Linux's knowledge base is quite extensive. It is free, which helps us to advocate the product. I would like it to continue and rate it positive. 

The Red Hat Enterprise Linux web console was helpful and offered visibility through dashboards. It helped us see what was going on with our system. 

I rate it a nine out of ten. 

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.

RHEL’s built-in security features for simplifying risk reduction and maintaining compliance are good. If you keep SELinux on, it is all good. If you have a system with SELinux off for a long time, it could get you in trouble. The system will make many changes, like restoring files could break your application later. In case you resolve the problems simultaneously, it is fine. 

The troubleshooting feature of Red Hat is excellent. It can solve many issues on the machine right away. In addition, if you have an external scene, then Red Hat Insights is on. I sometimes go to this feature to see its status and what is happening. 

I don't do this on a daily basis and only check it every two weeks, but it's nice to have. I mainly oversee the high-level view of all the systems. This way, I know if the clients' machines need a patch system. 

There are some missing modules for SELinux in Ansible, like the playbook. It becomes a genuine hurdle to manipulate SELinux at the moment. I have to go to the machine, take a file to the repository, and deploy it.

I rate the solution a nine out of ten.

Overall, I'd rate Red Hat Enterprise Linux a nine out of ten.

Overall, I would rate the product an eight out of ten. The product is good, and the documentation is really comprehensive. The support is satisfactory as well. Based solely on the product itself, without considering support, we find it stable and capable of supporting various architectures. The documentation is particularly good and stands out. It provides valuable resources, including bug fixes, to people with developer accounts, which are free. Having all that information available is very helpful and resourceful, especially when troubleshooting Linux-related issues.

The documentation is very good, making it easier to troubleshoot any peculiar Linux-related problems.

Compare the documentation and the answers that are published by Red Hat. Review these aspects and that should help you decide.

I strongly recommend RHEL as it fits well in on-premises or cloud development, whether for a small or a large company, and it's a professional product. It's very integrated with container technology, including with Podman and Docker, although we recommend Podman for containers. RHEL fits well in a lot of situations and container environments. It's a good product.

Red Hat Enterprise Linunx's knowledge base is good, and you can find answers there. 

I rate the product a nine out of ten. 

Overall, I would rate it nine out of ten.

We use Red Hat Enterprise Linux with AWS. We started our practice with AWS, and most customers use it instead of GCP or Azure. We use the product in a hybrid environment, mostly when shifting the containers or existing workloads from legacy systems. 

Most of the customers use Red Hat Enterprise Linux because it is the only approved OS. The tool's knowledge base is good but is limited to subscriptions. 

The upgrade migration is straightforward. For the initial projects, we used to execute CLI scripts. We plan to upgrade the system if everything works well in the lower environment. 

I have used the image builder feature. I rate the overall product a nine out of ten. 

I'd rate the solution an eight out of ten. 

I'd advise new users to learn from someone who has done everything before. It's much easier than trying to learn by yourself from scratch. They should also have their own environment for testing. 

It's normally an issue of balancing the cost of support and the features that you are looking to achieve. If security is number one to any organization, Red Hat is a no-brainer. If support is a key issue, Red Hat again is a no-brainer. If you're facing any security or support issues, I'd recommend going with a distribution that has some sort of licensing tied to it.

I'd rate Red Hat Enterprise Linux an eight out of ten.

Our upgrade and migration plans are focused on a balance between stability and staying current with the latest and most secure versions of Red Hat. 

While there is a desire to be on the cutting edge, we must consider what is currently in use by our clinicians and staff who rely on our hospital systems. We aim to strike a balance between these factors and leverage a sandbox environment to test the latest versions before deploying them in our production environment. 

We have been thoroughly impressed with Red Hat Insights and are currently in the process of exploring Leapp, which has shown great results in our evaluations. The web console has been invaluable for us, particularly when collaborating with application custodians who may not be familiar with the command line interface. 

We use Ansible for managing our Red Hat Enterprise Linux systems for provisioning and patching, which has improved visibility and reduced issues compared to third-party solutions. Overall, I would rate Red Hat Enterprise Linux as a nine out of ten.

A lot of improvement is required to get security compliance, especially with the privacy of the data, managing it, and storing it. I'm sure Red Hat Enterprise Linux will be able to improve in the future.

Red Hat Enterprise Linux's effect on our system's uptime or security has been really positive. Especially with the customer's feedback coming out, I would definitely like to continue its usage.

It has enabled us to achieve 50% security standards certification. It doesn't fall into that domain, but the overall security policies do help integrate with it.

We use Red Hat Enterprise Linux in a hybrid-cloud environment. It has not yet supported our hybrid cloud strategy. It's still a work in progress, but I'm sure they will be able to do it in the future.

The knowledge base offered by Red Hat Enterprise Linux is really helpful, especially in connecting different cross-functional communities.

Our in-house monitoring services team with the network operating center manages our Red Hat Enterprise Linux systems regarding provisioning and patching. It has quite a good integration with Red Hat.

We have tried Red Hat Insights, and it's really helpful for the market competitive intelligence portal we have in-house and how it interacts with external parties.

We have tried Red Hat Enterprise Linux system roles, and it is helpful for on-time delivery.

We have tried the Red Hat Enterprise Linux web console. It has helped us 50%, and it still needs to be reviewed in more detail.

Overall, I rate Red Hat Enterprise Linux an eight out of ten.

Whenever we see a compliance issue and need a patch, it's been relatively easy to get Red Hat Enterprise Linux to update it.

We have a mix of Windows and Linux. Around 80 percent of our systems are Red Hat, but we also have Windows. So it depends on the application.

Most applications are compatible with Red Hat Enterprise Linux. It's easier to tune on a Red Hat system than on another OS. We could pin applications to a core with Red Hat Enterprise Linux. In terms of tuning, Red Hat Enterprise Linux performs better in the long run.

Overall, I rate Red Hat Enterprise Linux an eight out of ten.

I am running my workloads on-premises and on the cloud. I mainly use AWS.

Resiliency-wise, the solution is very good. It's good because we don't have a problem with our environment at this moment. When we don't have a problem, we don't need to explain what is to be improved in the solution. It is reliable and doesn't break or bring us any problems.

Regarding how easy or difficult it is for me to move workloads between the cloud and my data center using the solution, we don't have problems. In general, it's easy.

We are talking about moving applications from on-premise to the cloud. We need to see if that represents any cost savings. We would need to go through a migration process, and that would be an extra cost.We would need to see if that is beneficial.

I rate the overall solution a nine out of ten.

I would advise others to read up on the solution first. Try Fedora first before you get into Red Hat. There are some similarities and a lot of what you know about Linux transfers over. 

I would rate this solution a nine out of ten. 

For security purposes, we use the SSH key algorithm, MD5, and SHA256. We have set up a firewall in our network, and all servers are password-based. We also block some common ports that are open when we install the OS. We also have monitoring tools to ensure uptime.

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

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

From what I've seen of Red Hat Enterprise Linux, it's well-documented. There are comprehensive notes and documentation available. I've been using it recently, and I've found that all the information I need is readily available. If we can't find what we're looking for, our support organization is there to help.

We have a virtual environment and deploy the solution from a satellite.

Currently, we require two people for the maintenance of Red Hat Enterprise Linux.

It's the default posture of a lot of the third-party vendors that you should just disable and leave them off. With containerization being prevalent everywhere, portability is across the board. Red Hat Enterprise Linux adopted Podman as opposed to Docker. Podman is a good tool, and I like it. Red Hat Enterprise Linux is the standard on which many others have based their platforms.

Using SELinux is largely misunderstood. If used properly, it provides a great platform for us. Red Hat is a big corporation, and we have people we can reach out and talk to. The same goes for SUSE. For Ubuntu, I have always gone straight to NVIDIA for support. I personally don't know of any great differentiators between all the products. I know Red Hat. It's been around longer, and I've had a long history that makes me comfortable. 

I wouldn’t recommend one over the other. It would come down to the use case. If someone wants Kubernetes on-prem, I would probably guide them toward OpenShift. I do have customers that don't run OpenShift on-prem. I often find that the customers already have a preference because they already have a license. So it's never really a decision that falls on me.

Red Hat Enterprise Linux uses firewalls, so configuring a firewall is easy. I have deployed the solution in multiple places. Overall, I rate the product an eight out of ten.

Overall, I would rate the solution an eight out of ten because there is always room for improvement when it comes to technology.

I have worked on a few Linux platforms, but Red Hat is a different experience. Due to its stability, it makes an excellent choice. It’s so-called invincible security makes sure that your data remains safe. The excellent customer service support agents are ready to get your problem resolved almost within an hour of opening a case (as long as you have the premium license for your servers). Taking all this into consideration, I would say this solution is a nine out of 10.

I have been working on Red-hat for two years and I must say I enjoy working with it. No day is like another, since there will always be something which will enhance your learning curve.

I would say if you are managing high-end servers running complex programs, Red Hat would never do you wrong. It has a lot of built-in tools if you choose the maximalist installation. If you are running a low-end server, you can even go with the minimalist installation which would only cramp a few megabytes of your processor power.

We are a big data shop that has around 700-800 nodes.

Red Hat Enterprise Linux Leapp was very helpful. It is very easy to use. 

Our servers run for 500 days, and we reboot them every 600 days. 

I search through Red Hat Enterprise Linux's knowledge base daily. 

We use Red Hat Enterprise Linux 8.6 since the third-party tool is compatible with it. 

We use satellites for the operating system and Ansible to do the configuration. 

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

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

I am using versions 7, 8, and 9. By implementing the solution, we wanted a unified server with a baseline platform that everybody uses. We wanted to have just one server that is enterprise ready.

We do not really have compliances in the same way as an American company has. It's nice to have IT security personnel. You get SELinux from the start. However, we get a lot of support cases because of it. The developers face problems with it. So, we get the security, but we also get lots of support cases. Usually, I end up in the middle of that because I work with support.

We run containers on OpenShift. We run only one platform, so portability isn't a concern. We only have Red Hat Enterprise Linux and OpenShift. We don't really need portability since we are government agencies. Nothing else other than on-prem is allowed for us.

The knowledge base offered by Red Hat Enterprise Linux is extensive. It is a bit hard to find information. However, when you find it, it's good. The packages are a bit old. We have a bit of an issue because of that. But other than that, it's a great operating system.

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

I did not have issues finding configurations and changing settings as needed. I haven't had any issues like bugs or downtime while using Red Hat Enterprise Linux. Overall, it was a good experience. Overall, I rate the solution an eight out of ten.

The biggest lesson I have learned with RHEL is don't complicate your design. You can always find an easier way to do things. Sometimes you'll think, "Oh, we can do this," and you start thinking about very complicated processes. It's better to think and start simple.

With RHEL, we have patching in place, automation in place, and we already know the support. We are very satisfied. We have done a lot of work on it and now it's easy to deploy VMs immediately. We are not looking to implement any other version of Linux.

Since I started with version RH 7, I believe the GUI is quite close to any other GUI operating system. There have always been a variety of tools and features that attract a non-Linux user.  As already mentioned, RHEL has been a pioneer in open-source technologies; it continued to evolve with changing market needs, that has been a big success for them.

I would definitely advise choosing RHEL if you need stability, scalability, and reliability of the OS platform. I would be a big advocate for the use of Red Hat to any new person who wants to deploy his production workloads, on-prem or on cloud on a Linux environment.

I would rate it a nine out of ten. It's near perfect. 

I would advise making sure you get a good support contract and you have a very good salesperson to work with.

In terms of RHEL's effect on our organization's management and efficiency, it can always be improved, but we probably are a three out of five on efficiency. As we move into OpenShift and get a lot more automation working, we will move slowly to the five, but that's not the fault of Red Hat. That's the fault of our organization having limited resources, and Red Hat is helping to provide the tools to get us to the next level.

Given that we started running everything on Microsoft, Red Hat is a lot more flexible in giving us the ability to span out specifically as we move into containers. It's going to give us the ability to stand up a lot more resiliency. When we're getting a heavy load, we can expand. Even currently, we have the ability to expand slightly but moving into containers will give us even more capability. We've chosen Red Hat as our platform. Red Hat has done well enough for us, and that's the platform that we're moving to with containers.

At this point, I would rate it an eight out of ten because there's always room for improvement. I don't feel that there's a perfect OS. I would even rate Windows as a seven. There's definitely room for improvement, and with Red Hat being one of the larger targets out there for hackers and people, there are always issues coming up.

I recommend RHEL because although there's not much difference between it and CentOS, it does provide full support. If you have any issues you know where to turn and they can be solved. 

I rate RHEL nine out of 10. 

I would rate this solution a nine out of ten. 

I would recommend this solution to others. It is easy to use, manage and handle with very little downtime. 

I would rate this solution an eight out of ten. 

Well worth a look if you want supported enterprise Linux.

I rate this solution eight out of 10. 

I would recommend this solution to others. I would advise others to do their research before deploying it and make sure that they are up to speed with the OS and what it can do. It is fairly easy to use as long as you know what you're doing.

I would rate Red Hat Enterprise Linux (RHEL) an eight out of ten.

I would like to see user training sessions that last about one to two hours on new features and releases. 

We have a separate team that creates dashboards for us. I rate the product a seven out of ten. 

I would tell potential customers that they should go for the latest releases. If they want to buy it, they should get a developer account from RHEL first and use that dev account before buying it. They might have some hands-on experience before spending too much money on Red Hat.

On a scale from one to ten, I would give Red Hat Enterprise Linux (RHEL) an eight.

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

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

We have around 20 Red Hat Enterprise Linux users in our organization.

For somebody familiar with the Linux platform, it is not difficult to troubleshoot when using this solution.

I would rate this solution a seven out of ten. 

My advice: Kickstart is your friend.

I would definitely recommend this solution. It is my most preferred solution. I like using terminals, and with Red Hat, I get to work on terminals and shell commands. It has good security. 

I would rate Red Hat Linux (RHEL) an eight out of ten. I find it excellent, but no system can be 100% perfect.

Red Hat is similar to CentOS, except that CentOS doesn't offer to support certain solutions, such as Oracle.