As the DevOps engineer, my main use case for Red Hat Enterprise Linux (RHEL) today is as our OS. All our runners run on that, as well as Red Hat Enterprise Linux (RHEL) UBI containers, which is what we deliver to our customers. Red Hat Enterprise Linux (RHEL) runs our infrastructure and is what we deliver to the customers as well.

We use Red Hat Enterprise Linux (RHEL) all on-premises on Dell servers.

I have not tried doing AI workloads with any Red Hat AI product specifically, but we are running our AI model server with VLLM on Red Hat systems. We are using it on Red Hat Enterprise Linux (RHEL), but not with any Red Hat AI.

Red Hat Enterprise Linux (RHEL) helps us solve pain points by giving us security and trust. When we tell our customers we are using Red Hat Enterprise Linux (RHEL) images, it helps them trust us that we are using the security and we have all these controls. Red Hat Enterprise Linux (RHEL) gives us trust and security.

I value the management features of Red Hat Enterprise Linux (RHEL) the most, such as Red Hat Satellite, which allows us to tell and monitor our whole fleet about the status of every system and keep it up to date. The management interfaces are really effective.

For navigating our security risks in Red Hat Enterprise Linux (RHEL), it would probably be mostly Satellite. With Satellite, you can determine which of your systems are out of date. Containers might also show outdated packages. Satellite helps you find systems that have not been updated or systems with old packages.

Red Hat Enterprise Linux (RHEL) helps mitigate downtime and lower risks. Since Red Hat Enterprise Linux (RHEL) has all these Ansible and Kickstart and Satellite features, we have a good process of redeploying systems. If something did go down or break, we have all the automation to be able to bring it back up, and we have all that as code. This has been helpful.

I am not certain how Red Hat Enterprise Linux (RHEL) can be improved. We are still on Red Hat 8 mostly, and so I am not really certain about what features have already been released.

From a Red Hat 8 perspective, I think perhaps better container support for running them as services would be beneficial. Maybe Kubernetes support, such as something built-in for if you just want to use the system for running containers and keep them online as services would be valuable.

I have been using Red Hat Enterprise Linux (RHEL) for the whole time, since 2021, which is approximately five years.

I have not experienced any downtime, crashes, or performance issues with Red Hat Enterprise Linux (RHEL). We have had servers that are very stable for many years.

Red Hat Enterprise Linux (RHEL) has definitely scaled with the growing needs of my company. As we have grown as a company, we have expanded how many servers we have. It has been pretty smooth with Satellite managing it all. You can keep track of everything, so it has been good.

I would rate customer service and technical support of Red Hat Enterprise Linux (RHEL) an eight. It is really helpful to be able to open up tickets and get a technical person that can walk you through getting the logs and getting the information. In an ideal ten out of ten, it would be instantaneous support or much faster response times, but we do have a good response time and good support.

I am not certain if my company was using another solution to address our needs prior to using Red Hat Enterprise Linux (RHEL). There may have been some CentOS or Ubuntu used way back, but I am not certain.

I think we have seen a return on investment with Red Hat Enterprise Linux (RHEL) from a technical point of view. The investment comes from when we can deliver our software to customers and they can start immediately using it versus if we are delivering a different OS that someone might not be certain is secure. They trust in Red Hat Enterprise Linux (RHEL) and that we are using that. This allows us to keep delivering at a good pace and getting the software into our customers' hands.

My experience with pricing, setup cost, and licensing has been really good. I am not at the level to buy it, but I think we have a company-wide Red Hat license. We can have as many Red Hat Enterprise Linux (RHEL) machines as we want, including all the packages and the containers. It has been positive and good.

We have also looked at Ubuntu while using Red Hat Enterprise Linux (RHEL). Their management platform is Landscape, and it just does not seem as reliable for us. We have had much more issues with Ubuntu from deploying it and hardening it. It does not really seem to work the same for us as Red Hat.

The business value of Red Hat Enterprise Linux (RHEL) compares favorably to the other Linux distributions we have evaluated, such as Ubuntu. Red Hat definitely has more value. We invest much more time in that because we have so many more Red Hat Enterprise Linux (RHEL) systems, and it has been a much smoother experience. If any project tries to come to us wanting Ubuntu, we try to steer them away and see if Red Hat will work first, because it seems to work better and is more comfortable.

I have tried Red Hat Enterprise Linux (RHEL) Image Builder, but only as testing. We are not using that in production, but I have used it and created a few images.

The testing with the Image Builder went really well. There were some limitations with what versions of Red Hat the Image Builder supported versus what we were currently using, so I could not really continue testing, but it worked for the walk-through I was following.

I do not know anything in particular in Red Hat Enterprise Linux (RHEL) that has helped me with my AI workloads overall yet. We are still just getting into the space, so I do not know if there is really anything about Red Hat specifically, because we are just running open source tools on Red Hat. However, it is still making us secure from a foundation with a secure OS.

We are not really doing a full zero-trust setup with Red Hat Enterprise Linux (RHEL), not yet. Having all our devices, such as all our Red Hat devices registered in Satellite, helps you keep tracking them. This is moving towards it, having a management system for everything, but nothing really other than that.

We have not done a major version upgrade with Red Hat Enterprise Linux (RHEL) and Ansible Automation Platform, such as moving from Red Hat 8 to Red Hat 9. Whenever we have done that, we just reloaded the system. We use Ansible Automation a lot, but never for a full upgrade.

My experience with the Ansible Automation Platform has been really good. We transitioned to it heavily. Before, we were just using each developer who were running the playbooks themselves. Now we can put them in the platform. The access is really good, so we can have students who can only run certain playbooks or not edit them, which is helpful. Full-timers can set up something that works and then the students can run it as they need. This has been really helpful for us for automating things.

From an OS level, when we are deploying Red Hat Enterprise Linux (RHEL), we can pick the DISA STIG profiles, and that gives us a good starting point for all our systems to be hardened a certain amount. Then we use the Ansible Automation Platform running Ansible playbooks that can finish the job and finish the rest of the STIG controls. This makes them compliant. We can also run Ansible playbooks that can verify all our systems are at that certain level. Red Hat Enterprise Linux (RHEL) does a major part, and we use Red Hat for pretty much everything for our compliance.

The knowledge base offered by Red Hat Enterprise Linux (RHEL) is really good. Many times I am searching for questions and it will pop up as one of the first few results showing how to solve it. A few weeks ago it helped me solve an issue for a customer. The knowledge base has been really helpful.

The deployment process with Red Hat Enterprise Linux (RHEL) has been pretty straightforward. We use the Kickstart process, and then Ansible to finish the deployment. My overall review rating for Red Hat Enterprise Linux (RHEL) is nine out of ten.

My main use cases for Red Hat Enterprise Linux (RHEL) include virtualization, day-to-day computing, general use cases, desktop use cases, and server use cases, treating RHEL primarily as a server system.

RHEL helps us solve tremendous pain points because we are a cloud service provider, and we do a lot of virtualization and networking. As a cloud provider, we basically rely on virtualization, networking, storage, and a lot of other things, so RHEL is a core platform for us that enables us to combine all these components together and provide a comprehensive solution.

Since we are a cloud service provider, we rely on RHEL's virtualization feature and sell these virtual machines to customers, making a significant profit from it.

RHEL supports our hybrid cloud strategy as we offer private and public clouds to customers and can burst into other public clouds. RHEL as an operating system provides in-built support that helps us burst into hybrid and other cloud ecosystems with our expertise.

The features I appreciate most in RHEL include virtualization, networking, and storage, and there is not a single feature that stands out for me because I appreciate pretty much everything RHEL offers.

RHEL acts as an enabler for running AI workloads, offering in-built security, particularly with features such as Podman that help secure the environment. With RHEL AI, there are many integrations, including Instacloud, providing significant security benefits.

RHEL plays a core role in our implementation of the Zero Trust model, operating many OpenStack clouds and utilizing systems for regulated industries such as financial services and government sectors. The good ecosystem of RHEL supports authentication, authorization, and zero trust, enhanced by features from OpenShift as well.

RHEL should cover more hardware, particularly since we face challenges with some hardware components, such as Intel VROC as a RAID controller, which RHEL has compatibility issues with. I acknowledge that it is difficult for RHEL engineers to cover all hardware, but collaboration with manufacturers such as Intel or Lenovo might alleviate some drawbacks.

I have been using Red Hat Enterprise Linux (RHEL) since my university days, and it has been almost eight years.

I have not experienced any downtime or performance issues with RHEL; it is a very stable operating system.

We have been able to scale well with RHEL; we run a lot of distributed storage, and scaling up is just a matter of adding resources without limitations, as the platform supports scalability indefinitely.

The customer service and technical support from Red Hat are perfect; they know what to do when we reach out, even when it is on behalf of customers.

We have also worked with SUSE and Ubuntu Pro, but our customers often prefer RHEL for general-purpose server workloads, while they go to SUSE for SAP workloads, indicating that RHEL has a strong customer preference for its compatibility and support.

My experience deploying RHEL has been straightforward; the deployment methods are easy, utilizing PXE boot and cloud-init within our OpenStack environment, which makes maintenance and deployment very efficient.

From our perspective as a cloud service provider, the biggest return on investment with RHEL comes from the margins we make after selling licenses to customers. We operate clouds with RHEL as the core, and we see a good amount of margin through virtualization services provided to customers.

The pricing, setup cost, and licensing of RHEL work out for us as a cloud service provider, so we are satisfied with them.

We sell other products such as OpenShift that do similar work to RHEL.

When it comes to navigating security risks with RHEL, we rely on SELinux as the main security feature, and we are also looking at Lightspeed, which provides a nice command line assistant. We also utilize PQC for core cryptography in RHEL as well as its TLS functionality, and container sandboxing is another major feature we leverage.

I tried the Image Builder in RHEL, and my experience with it was quite good. The image mode is beneficial because it allows us to create many portable images, which I find really good for our needs. I use the Image Builder in the cloud for internal purposes as well as for our customers.

I have used Satellite. Satellite helps manage and maintain my hybrid cloud environment, although not to a very good extent because we operate a single environment that we consider an on-premises or private cloud. Some customers use it to manage a fleet of systems across various instances, but for me, it is more focused on on-premises.

We have tried out RHEL AI, using Instacloud and other tools as well as OpenShift, which is outside of RHEL. We are not using the Ansible Automation Platform for major version upgrades, but we do use Leapp upgrades because the Leapp tool is necessary for our upgrades, although it requires manual oversight to ensure there are no compatibility issues.

We use both open-source Ansible and the Ansible Automation Platform, and it has been good for managing our fleet of servers as we run virtualization. The Ansible Automation Platform is particularly useful for managing many CVE patchings.

I believe RHEL effectively mitigates downtime, and I do not see any significant problems regarding this issue. The knowledge base offered by RHEL is pretty good; the documentation is top-notch and very helpful, and the support portal, including the AI features, is also excellent.

We have been able to scale well with RHEL; we run a lot of distributed storage, and scaling up is just a matter of adding resources without limitations, as the platform supports scalability indefinitely. Overall, I would rate RHEL as a top-notch, superior product, and it is a very stable operating system.

I would recommend RHEL to other companies, emphasizing that stability is key, especially for running enterprise-grade workloads or server workloads because everything is tested and reliable, which minimizes the risk of breaking things during upgrades. I would rate this review as 9 out of 10.

We use Red Hat Enterprise Linux (RHEL) for applications. Our use case involves its very easy deployment and usability, along with substantial support from the community and open source resources. We are looking forward to using much more OpenShift applications and Red Hat Open as well. Red Hat Enterprise Linux (RHEL) helps me solve pain points related to scalability, enabling us to deploy several servers in one.

The AI and automation features such as Ansible and Ansible Tower stand out to me. We build streams in our automation features, using playbooks in Ansible for patching the application servers in a timely manner. We are also using automations for fault detections and fixing configurations, as well as building pipelines to deploy new features such as Windows 2019.

The open source environment has positively impacted our organization due to the package feature with the satellite, allowing us to download open source codes, which has been very flexible, resulting in enormous savings. Red Hat Enterprise Linux (RHEL) has mitigated downtimes and lowered risks in our organization, especially with the latest features.

I would like to see smoother integration with the AI components that would use other Red Hat products such as OpenShift and Ansible in Red Hat Enterprise Linux (RHEL). I think the support should be more concerned about the new standards of technology. Customer support could be a little bit better, but it is definitely very good overall.

I have been working for 26 years in the application management team.

Red Hat Enterprise Linux (RHEL) is definitely stable, and we are very happy about it.

Red Hat Enterprise Linux (RHEL)'s scalability is very well configured and very straightforward.

Although my team is not responsible for patching and maintaining Red Hat Enterprise Linux (RHEL) systems, I hear from my colleagues that they are very satisfied with the features, stating that it is easy to maintain the Linux environment and flexible. I have a Red Hat account and look on the internet for knowledge bases.

Since I am not responsible for managing the Red Hat Enterprise Linux (RHEL) hardware in our environment, I cannot give a detailed explanation of how I access the knowledge base. However, I research on the internet and with my account, I try to go into labs and find the appropriate knowledge base.

We used a different solution primarily for automation, which was the main reason for our switch.

We have saved costs, but I cannot provide specific metrics at this time.

Since we are a big bank, the pricing, setup cost, and licensing were through an end-user master agreement, which made us really happy because it was beneficial for both sides.

We had some options, but we were very enthusiastic about Red Hat Enterprise Linux (RHEL), so we chose it.

We navigate our security risks using features such as identity management, which we fall in love with more every day because it is really key to organizing security. The most important security feature for Red Hat Enterprise Linux (RHEL) that stands out to me includes the accessible accounts groups.

Red Hat Enterprise Linux (RHEL) is part of an open-source community, so I advise others to develop their own solutions within the environment and community while still being supported and free of enhancements. I would rate this product a 9 out of 10.

My main use cases revolve around managing my application, so I want to ensure there is an operating system on which I can keep it. Linux is one of the best options where I can keep my application, either containerized or running as a JBoss application or whatever else is needed. Therefore, I started with Red Hat Enterprise Linux (RHEL) 6 and have progressed to RHEL 7, RHEL 8, and RHEL 9 as of today. One of my main use cases is to ensure I run my application on an operating system, and RHEL provides the best security patches and quick fixes, and it supports a lot.

RHEL helps solve my pain points by providing patching. Security is one of the big pain points for me, especially as I work for a financial company, making it important that security is a critical thing, and RHEL solves that.

The features of RHEL that I appreciate the most include its various packages, which allow me to ensure that I can customize whatever I need and keep it in the operating system. I can discard the rest of the things that are not needed. It provides various ways, and whatever the package manager it provides and the connection to Satellite, it is a seamless process. I do not need to spend much time on that.

I think RHEL could improve by considering backward compatibility when making changes from version to version. For example, we were using OpenLDAP in RHEL 7, but when we went to RHEL 8, it was not available. I had to bring in some new systems because OpenLDAP is not a feature in RHEL 8, requiring a lot of re-engineering because of whatever new tools arise that are not backward compatible.

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

We have experienced some downtime, performance issues, or crashes with RHEL, but these are not critical impacts. Our system is designed to minimize issues. We have seen out-of-memory errors, which we monitor through kernel logs such as dmesg. We were able to tune the system effectively. Issues arise, but they are solvable. It depends on the requirements, such as what application is running on it. Fine-tuning the operating system is essential to maintain reliability, especially for containerized applications. The base image requires fine-tuning, and similarly, RHEL does.

RHEL scales well with the growing needs of my company. We used to have three hundred virtual machines, and now we have over seven thousand five hundred virtual machines in our environment across RHEL 8, RHEL 9, and RHEL 7.

I would rate customer service and technical support eight out of ten. It depends on the issue I raise. Good support is provided for Sev 1 issues, but for those of lesser severity, the response decreases. This rating also relates to the type of subscription I believe we have; with a premium subscription, we tend to receive a good response.

I do not remember using another solution prior to RHEL at my company. It has been a long time, and I do not think we were using anything else before.

The deployment process of RHEL is pretty straightforward. We have multiple strategies, including SaltStack, and we used to have Puppet; now, we utilize Ansible. We have control and manage the deployment, or we go to VMware, create the machine, and install the operating system. Everything is automated, and we have transitioned from SaltStack to Ansible, making it straightforward.

I have not done a major version upgrade with RHEL and Ansible Automation Platform, but my team has. Recently, we migrated from RHEL 7 to RHEL 8 using Ansible.

That experience was pretty straightforward. We tested it end-to-end, and then we just migrated.

From my perspective, the biggest return on investment when using RHEL is security. As a financial company, I cannot opt for an open-source operating system. I invest effort and money in RHEL 8, expecting the system to be secure and reliable when serving my clients. RHEL is definitely helpful in that regard.

I do not deal much with the pricing, setup costs, or licensing of RHEL. Most recently, I was involved in those conversations, and it seemed pretty reasonable. I do not think it is a significant issue for us.

I have not evaluated other solutions while using RHEL. We recently migrated to OpenShift. If the application is containerized, we are moving to OpenShift, so it is not that we are actually looking for any RHEL alternatives.

My thoughts on Red Hat Satellite are that it provides an easy way to pull the patches, and it has all the versions, allowing me to create the repo and just pull from Satellite to get the packages I need.

We use Amazon Web Services as our cloud provider.

I do use Red Hat Satellite.

RHEL helps solve my pain points by providing patching. Security is one of the big pain points for me, especially as I work for a financial company, making it important that security is a critical thing, and RHEL solves that.

To navigate my security risks, I use a security tool such as Wiz running on the system, which identifies if there are any CVEs associated with the systems. Whatever the CVE it had, I can get the latest. We always go back to the CVE report and see if Red Hat provided that patch or not. If it is there, we just do monthly patching.

I am not certain what role RHEL plays in my company's implementation of the zero trust model.

My company's process for managing regulatory compliance involves tying up with different companies for auditing. They ask for screenshots, versions, patching details, version numbers, and a lot of details. We take all the screenshots, document them, and send them. RHEL plays a key role in this process; without an operating system, it would not make sense to provide the audit team any compliance information.

Whether RHEL helps mitigate downtime and lower risk depends on how I configure it. I make sure I have high availability. I have high availability running on my systems and migrate the traffic as needed, especially to keep my application up and running and reliable. Keeping high availability is essential, and RHEL supports me with the versions or at least the keepalived or whatever packages it provides; we use them.

I am not completely certain which RHEL capabilities helped to mitigate downtime and lower risk at my company. An example would help me correlate. Satellite provides patches, and it helps with downtime. My system depends on Satellite. Ultimately, my packages depend upon Satellite, and it does assist us with high availability and downtime.

The knowledge base offered by RHEL is straightforward. It has been there for a while, and every version we go through its documentation, especially while doing upgrades. The support team is always there and helpful if needed. I can raise a Red Hat case if required, just a Sev 4 or Sev 5 ticket. I might get a response in a day or two, depending on the severity or the bug's nature. While documentation helps mostly, we reach out for additional support as necessary.

I would rate Red Hat Enterprise Linux (RHEL) nine out of ten overall. My advice to other companies considering RHEL is to definitely look at the support that Red Hat provides, especially regarding security patching, version upgrades, and how Red Hat listens to our needs. When I have an issue, I expect that while they cannot resolve it the same day, they will address it in the months to come. I always have faith that I will receive assistance; it just takes time. My suggestion to other customers is to trust Red Hat; they always listen to their users and take care of issues.

My main use cases for Red Hat Enterprise Linux (RHEL) are primarily for IT services, as well as supporting Army programs. We use the OpenSCAP project in Red Hat Enterprise Linux (RHEL) because we have a lot of security compliance requirements that we must address with STIG compliance.

Increased security posture through running minimal base images for critical services. Scalability through automated OS deployments.

Red Hat Enterprise Linux (RHEL) helps us solve the challenges that you potentially have with the Windows operating system being a much larger attack surface with services running which often are not needed. RHEL is a security-focused operating system.

I appreciate Red Hat Enterprise Linux (RHEL)'s feature of supporting minimal installs because for a lot of our use cases, we do not need a full operating system with office productivity tools, which makes it much easier to provide just the minimal installation.

The compliance tools in Red Hat Enterprise Linux (RHEL) help our company because they are a mandated requirement, allowing us to use those tools to remediate the system and provide quantifiable percentages and scores to show that we are compliant.

Red Hat Enterprise Linux (RHEL) plays a huge role in my organizations implementation of the zero-trust model, as we always end up with requirements that force us to use Windows. Traditionally, we use Active Directory for identity management, and Red Hat Enterprise Linux (RHEL) has been a staple for all of our server infrastructure. For anything that needs to have a long uptime or anything that provides a service, we always gravitate to Red Hat Enterprise Linux (RHEL) as opposed to Windows, which is primarily for office productivity-type purposes.

My organization's process for managing regulatory compliance involves working with the cyber team to provide a checklist and show that we are compliant with all the controls or at least document why we are not or tailor them out. Red Hat Enterprise Linux (RHEL) has helped us with that because out of the box, it is in pretty good shape, so there is only minimal work we have to do on top of it.

The biggest struggle we have with Red Hat Enterprise Linux (RHEL) is the cost and the fact that a lot of our user base wants to gravitate to the free upstream offerings. I believe more competitive pricing would be my primary feedback.

My insights on the pricing model for Red Hat Enterprise Linux (RHEL) go back to the annual recurring cost. At the end of the day, anything Red Hat can do to lower that to make it more competitive would help push people to a more stable enterprise product and not be so tempted to use the upstream free alternatives.

I have been using Red Hat Enterprise Linux (RHEL) since RHEL 5 or around 15yrs.

Red Hat Enterprise Linux (RHEL) has helped us with the mitigation of downtime and lowering risks because it is a stable operating system, and we are able to keep the uptime on our servers, with everything working great. We could not be happier with it.

Red Hat Enterprise Linux (RHEL) is very scalable. We have systems where we have 2,000 users logging into it, and we have environments that are both online and on closed, restricted networks, so it is a very easy-to-scale product with everything where it needs to be.

I would rate the customer service and technical support for Red Hat Enterprise Linux (RHEL) as a nine. Everything is solid there, and I am happy with it. There is always room for improvement.

Every company starts off with Windows, and that is where we were at. There was a lot of use of CentOS for a while, but I definitely got involved with Red Hat Enterprise Linux (RHEL) pretty much early in my career and have been with it through the evolution of the product.

The deployment process of Red Hat Enterprise Linux (RHEL) is straightforward. We are able to do it at scale, having used Kickstarts for doing bare-metal installs and virtual machines, and now with containers using Ansible to roll things out. The automation built-in makes it very easy.

We have used Ansible extensively and use it a lot. We also use the Automation Platform in Red Hat Enterprise Linux (RHEL), which is part of our build pipelines and what IT does for patching.

From my point of view, the biggest return on investment when using Red Hat Enterprise Linux (RHEL) is definitely the relationship that we have with our account management team. I would say that is something we do not have with a lot of other vendors, so that is probably one of the big advantages we get with this product versus others.

My insights on the pricing model for Red Hat Enterprise Linux (RHEL) go back to the annual recurring cost. At the end of the day, anything Red Hat can do to lower that to make it more competitive would help push people to a more stable enterprise product and not be so tempted to use the upstream free alternatives.

Ubuntu is still used a lot but I've found their distributions while more upstream, boated, and move likely to be impacted by CVE.

We have not used any AI workloads with Red Hat Enterprise Linux (RHEL). We are just beginning in the world of AI, and I saw the keynotes that looked promising. We have provided some OpenAI chatbot-type solutions, so I need to look at pricing for that and see how we can potentially shift some of the things that we have done on Red Hat Enterprise Linux (RHEL) to more of an enterprise offering such as Red Hat AI.

My thoughts on the efficiency of Red Hat Enterprise Linux (RHEL) are that it is a great product. We could not live without it, and I do not see it going away anytime soon, so I believe it is a staple of the offerings.

The knowledge base offered by Red Hat Enterprise Linux (RHEL) is solid, and it is what we always go to first before we open tickets. Red Hat is doing a great job of keeping that up to date and current, making it definitely a good resource.

I would rate this review a nine overall.

We use Red Hat Enterprise Linux (RHEL) to install our Linux versions. We are using a product called Appian, which is a low-code/no-code platform BPN. On top of that, we will be installing our products in Citibank, which means at the client location. We will run that installation and everything in Red Hat Enterprise Linux (RHEL), and we will be bringing that instance where end users develop their use cases on that. Apart from that, we have four to five products called Boardwalk and Apptio which are running on the on-premises Red Hat Enterprise Linux (RHEL)-based versions.

Before choosing Red Hat Enterprise Linux (RHEL), I previously worked with Kubernetes, but for the past four years, I have been working on OpenShift administration and as an application developer.

Red Hat OpenShift has the best GUI for a friendly user experience, and regarding security, it is number one compared to open-source tools like orchestrating Kubernetes. Red Hat OpenShift also provides excellent customer support where responses come immediately when we get stuck with anything. Security constraints are an added feature because they restrict non-root users for all applications, making it immutable and not overwritable by any malfunctions, which represents the best practices in Red Hat Enterprise Linux (RHEL).

I am currently working with the Red Hat Insights feature, which is a customized one for us in the banking sector. Although I may not have all the features, the best things we have for enabling security come into the picture, including RBAC, security services, and firewalls.

System Roles are organization-dependent and will change from organization to organization, not only in Red Hat. Those are the default system roles, but the organization can create roles on top of that. If they have an enterprise license, they may ask to create some system roles which are defined for the organization with privileged access.

In my hybrid cloud strategy for my clients, they will select any data center and install the bare metal racks there. On top of the racks, they will install the physical servers, which involve CPU utilization, and they will apply the security policies to the cluster, making it the best for deploying resources.

I feel there are no pain points that Red Hat Enterprise Linux (RHEL) helps me solve, and I do not have any complaints.

Red Hat Enterprise Linux (RHEL) saves time because it provides the best GUI, making it easier to perform changes without relying solely on CLI.

From my perspective, the best features of Red Hat Enterprise Linux (RHEL) include security patches which are the best, and the OS is very good compared to Ubuntu or other alternatives. Red Hat Enterprise Linux (RHEL) offers UBI images or UBI versions that are very eco-friendly for use by the end users of those Linux machines that are deploying their services or applications, making it user-friendly for them. Whenever we get stuck, the support from Red Hat is very responsive, and we receive the best support from them.

I decided to switch to Red Hat because our products have the capability and we need to have the flavor based on Red Hat Enterprise Linux (RHEL). With Red Hat Enterprise Linux (RHEL), the security and compliance are the best part, and building applications on that platform will give security constraints. The dependency can be installed, and whatever packages we get from Red Hat are the best things to have compared to Ubuntu.

I have worked in both hybrid and purely on-premises environments, specifically on-premises bare metal.

The business value of Red Hat Enterprise Linux (RHEL) compared to other Linux distributions I have used is that a separate team is always engaged with our organization. Whenever we face issues, there will be a ServiceNow or an INC raised, and they respond immediately along with dedicated people available for support.

I would prefer better handling as sometimes the PVCs may get stuck, and there are numerous things like release notes that may affect some applications depending on the binaries, which they can manage and improve.

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

I have not seen any performance issues with Red Hat Enterprise Linux (RHEL). Performance issues may arise if any node goes down or a cluster drain occurs. When a new release happens, every organization receives notification via email that applications should be built per Red Hat Enterprise Linux (RHEL) guidelines to avoid any performance issues, which depend on how the applications are built on the platform.

I find Red Hat Enterprise Linux (RHEL) scalable, and there are no limitations because scalability depends on the replica set, allowing flexibility from 100 to 10 or whatever you need.

I would assess the knowledge base offered by Red Hat as four out of five because whatever issues we encounter, we immediately go to that customer portal and get those things and raise a ticket for them.

I rate the tech support for Red Hat Enterprise Linux (RHEL) as nine out of ten.

I previously worked with Ubuntu, but currently we are using Red Hat Enterprise Linux (RHEL) flavors only.

The initial setup with Red Hat Enterprise Linux (RHEL) is straightforward, and there are no significant complexities in the deployment process. Red Hat provides the necessary binaries or TAR files, allowing you to bring it into your Red Hat Enterprise Linux (RHEL) system and run it with command line access directly from the local machine to the OpenShift cluster, demonstrating how user-friendly it is.

The ability to mitigate downtime and lower risks depends on how I build my applications. If you create them on a good platform, they generally behave well. If a new release occurs, only then would it cause disturbances, but that usually does not happen.

For user benefit, end users do not know what platform it is sitting on. They experience the best latency with low latency, allowing them to utilize the products and resources running, making everything compatible, which is the best for them. Therefore, this is essential to design at an architectural level.

I have not faced any missing features, so I cannot comment on those.

I can provide advice if they need to migrate from on-premise to OpenShift based on my experience in working as an architect in that area.

I will recommend Red Hat because in OpenShift clusters, it is user-friendly with a GUI that offers excellent visualization alongside Kubernetes. There is no need to create additional dashboards. Red Hat Enterprise Linux (RHEL) is a best security product managed globally by the Red Hat team, and all binaries are available for download. The support portal allows for quick issue resolution, with responses available in a fraction of hours depending on the ticket's urgency.

My overall review rating for Red Hat Enterprise Linux (RHEL) is nine out of ten.

My main use cases for Red Hat Enterprise Linux (RHEL) include everything from apps to web servers to HPC.

Red Hat Enterprise Linux (RHEL) helps me solve pain points primarily because the ecosystem has already been approved for use with our customers. That's probably the main thing. It's a single, trusted source to get everything from. That's really our main thing.

Red Hat Enterprise Linux (RHEL) has helped to mitigate downtime and lower risk using Satellite because I rarely have any outages on my RHEL boxes. They're pretty solid.

Satellite helps reduce and mitigate risk through the quality of the packages that get put out and the dependencies that are already validated.

I've never really thought about how Red Hat Enterprise Linux (RHEL) could be improved, but the only thing I wish they had that I've asked Red Hat for so far is something resembling managed service accounts. Since we have to integrate with a lot of Active Directory, that would be beneficial.

I have been using Red Hat Enterprise Linux (RHEL) since RHEL 4.

I would assess the stability and reliability of Red Hat Enterprise Linux (RHEL) as excellent because I've not had anything serious that couldn't be figured out.

Regarding scalability, I've never had a problem there. We run HPC on it, and it's pretty rock solid.

I don't really have an answer for the customer service and the technical support of Red Hat Enterprise Linux (RHEL) because we have to handle most things in-house.

Before adopting Red Hat Enterprise Linux (RHEL), my company was using a lot of Solaris, other flavors of Unix, and other options, but I think we've pretty much standardized on RHEL.

I think the deployment process for Red Hat Enterprise Linux (RHEL) is straightforward.

If you're doing a network install, it's easy. It's easier than the Windows side.

I'm brand new to Ansible Automation Platform. We're just rolling it out.

From my point of view, the biggest return on investment when using Red Hat Enterprise Linux (RHEL) is the fact that it's well-curated and it's a one-stop shop for most everything you need.

My experience with the pricing, the setup cost, and the licensing of Red Hat Enterprise Linux (RHEL) has been pretty good. I have no complaints.

Though there have been talks of going to other distros while using Red Hat Enterprise Linux (RHEL), that's a big ask to switch everybody over.

The features I prefer most about Red Hat Enterprise Linux (RHEL) relate to my broader appreciation for Linux given all the history behind it and open source for all that it represents.

For navigating security risks, I use Red Hat Enterprise Linux (RHEL) Satellite for patch management and deployment. We don't use Insights. That's probably the main one we use.

Regarding the role Red Hat Enterprise Linux (RHEL) plays in my company's implementation of the zero-trust model, it's pretty new to us, so I can't really answer that yet. We're still in the learning process.

In terms of managing regulatory compliance, we do use Nessus and other tools for auditing in our applications. That's probably about it.

You can usually find a good answer on the knowledge base offered by Red Hat Enterprise Linux (RHEL).

I've always been happy with Red Hat ecosystem, using it since before RHEL, and I just appreciate the flavor of it. I've tried other Linux distros and I just keep coming back because I'm so familiar with it. It's so helpful, and it's hard to beat. I would rate Red Hat Enterprise Linux (RHEL) a nine out of ten.

My main use cases for Red Hat Enterprise Linux (RHEL) involve a custom Linux security module, and I use RHEL as my upstream and repackage it as my own distro.

To navigate my security risks, I use features in Red Hat Enterprise Linux (RHEL) such as Satellite, Ansible, IPA, or IDM, and I also perform STIGging with a lot of my requirements coming from the government telling me to ensure I have all these things done. Red Hat Enterprise Linux (RHEL) makes it easy to do that, with the biggest thing being their documentation because I can find any question I type into Google and find a Red Hat link, log in, and see it.

I use Red Hat Enterprise Linux (RHEL) on-premise.

Red Hat Enterprise Linux (RHEL) helps me solve pain points because it's open source, so it's easy to modify, and there's the support that I need, especially since I work with the public sector a lot where they want support provided, updates, and patches on CVEs almost immediately after a zero-day is released, and that's the big thing that Red Hat Enterprise Linux (RHEL) helps me with.

What I appreciate most about Red Hat Enterprise Linux (RHEL) is that they're open source, and I take what they have and repackage it. I appreciate RPMs, Mock, and a lot of the tooling that's in that community, in the Fedora world, but Red Hat Enterprise Linux (RHEL) makes it easy to get to and work with.

The knowledge base offered by Red Hat Enterprise Linux (RHEL) is something I love, and it's very helpful. That is probably the most useful part of Red Hat Enterprise Linux (RHEL).

Red Hat Enterprise Linux (RHEL) can be improved by getting more upstream packages from Fedora because they don't have enough packages, and it's problematic that I have to maintain a separate repo from what comes from Fedora. I don't understand why Red Hat Enterprise Linux (RHEL) doesn't package it as the base, as Red Hat Enterprise Linux (RHEL) only has a subset of packages from upstream.

The desktop environment is another area that needs significant improvement because it is barely usable and meets just the bare minimum of what's needed. There are people from Red Hat giving presentations on Windows, Macs, and other distros, which to me would be embarrassing. If I was the CEO of Red Hat and my employees aren't using our own product, that should be a major red flag. Why would you present to customers of all people? Red Hat Enterprise Linux (RHEL) is great as a server operating system distribution and the support is the number one thing that makes Red Hat Enterprise Linux (RHEL) stand out, but it really falls short as a client workstation.

I have not experienced any downtime, crashes, or performance issues with Red Hat Enterprise Linux (RHEL). I've had servers run for three years straight without crashing, so Red Hat Enterprise Linux (RHEL) is very reliable.

In terms of scalability, I get a lot of complaints from customers, and when I start getting a lot of machines running, I start to see problems in production, which my customers experience as well, so then I'm supporting it. I don't know how much to blame Red Hat Enterprise Linux (RHEL) for that, but it does seem to become a headache once it gets larger.

I evaluate customer service and technical support from Red Hat Enterprise Linux (RHEL) as pretty good.

Prior to adopting Red Hat Enterprise Linux (RHEL), I was using another solution, specifically Solaris as my upstream. I think when Red Hat Enterprise Linux (RHEL) 6 dropped, I switched from Solaris to Linux, and it was Red Hat Enterprise Linux (RHEL) as the solution because of the support.

The deployment process of Red Hat Enterprise Linux (RHEL) has been straightforward and easy for me.

I am probably not considering switching to another product while using Red Hat Enterprise Linux (RHEL).

I have tried neither Red Hat Enterprise Linux (RHEL) Image Builder nor system roles, and I'm not a big fan of them because they're not part of my use case. They are useful in a sense for reproducibility if I'm going to create a golden image and deploy it, but that's not really my use case.

Red Hat Enterprise Linux (RHEL) has helped me to mitigate downtime and lower risks.

Red Hat Enterprise Linux (RHEL) is great on the server side and not as strong on the client side, with the workstation and desktop environment needing a lot of work. As far as adopting it, if you're willing to pay for all the licensing, then go for it because you'll get the support you want. On a scale from one to ten, I would rate Red Hat Enterprise Linux (RHEL) overall as a seven or eight.

My main use case for Red Hat Enterprise Linux (RHEL) is using it as an operating system for all of our Linux VMs, converting all of them from 42 different operating systems and versions over to Red Hat.

One pain point that Red Hat Enterprise Linux (RHEL) helps me solve is patch management, as we previously used a giant Ansible playbook that would run updates across our infrastructure with so many conditionals in it, but now we can simplify it down to essentially just one. It was previously one playbook, but it simplifies the workload to approximately half of what it was.

The features of Red Hat Enterprise Linux (RHEL) that I like the most include the cohesion among all of our VMs, so I do not have to remember that if I am SSHing into this server, it is apt update, and this one it is DNF update, and that one it is yum update; it is all going to be the same, DNF or yum update for all of them.

For navigating security risks in Red Hat Enterprise Linux (RHEL), Satellite is a big feature for us, as in the last couple of weeks, we just had two critical security vulnerabilities come out for Linux, and we use Satellite to find all of the vulnerable servers and then Ansible to patch them as soon as Red Hat releases a kernel update.

I have used System Roles quite heavily, so I want to use Image Builder, but I have not used it yet. All of our Ansible playbooks and roles focus on using System Roles first so that future iterations and updates to Red Hat Enterprise Linux (RHEL) 10 or Red Hat Enterprise Linux (RHEL) 11 will work going forward.

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

Regarding the stability and reliability of Red Hat Enterprise Linux (RHEL), I have experienced no downtime, crashes, or performance issues; it has been flawless. We have had no issues with it, and the only waiting period we experienced was for the two recent security issues because someone jumped the gun and published the exploits too early, but that is nothing Red Hat Enterprise Linux (RHEL) can control.

In terms of scalability, Red Hat Enterprise Linux (RHEL) scales wonderfully; we have about 400 VMs, and as I mentioned, we are converting all of our existing VMs over, whether that is a straight conversion using convert to Red Hat Enterprise Linux (RHEL) scripts or a rebuild. I have had both five Red Hat Enterprise Linux (RHEL) VMs and also had 200 Red Hat Enterprise Linux (RHEL) VMs, and honestly, it has been no different; when running reports, it just takes maybe a minute longer to grab everything.

My experience with customer service and technical support has been phenomenal; I have submitted multiple cases for various issues, and technical support has also been fantastic to work with. The longest I had to wait for a solution was about two days, and what they suggested fixed the issue for us long-term.

The factors that led me to consider a change to Red Hat Enterprise Linux (RHEL) included running an audit across all of our Linux servers and discovering that there were 42 different versions of operating system or operating system versions; we could maintain that with a bunch of Ansible playbooks, but we did not want to. Another product released by SUSE is similar to Satellite in that it provides an upstream RPM provider, but it did not work very well; it was adequate, but Satellite is by far the best. Standardizing everything has been a huge advantage for us.

I would describe the deployment process of Red Hat Enterprise Linux (RHEL) as straightforward, as I can go into Satellite and spin up a new VM; I have a fully functional VM within 10 to 15 minutes. This is provisioning VMs from nothing essentially, as we are not cloning a template. We initially tried cloning templates, and it only took minutes to have a new VM up and running.

We have not considered any other solutions in the time that we have been using Red Hat Enterprise Linux (RHEL), as we just purchased Red Hat Enterprise Linux (RHEL) three years ago. However, around that time, we contemplated Ubuntu's enterprise-level agreement, which includes support and extended release for updates; these were the two contenders we really compared, and Red Hat Enterprise Linux (RHEL) beat them by a significant margin.

While I have not used Red Hat Enterprise Linux (RHEL) in a traditional sense with AI workloads, we have a Red Hat Enterprise Linux (RHEL) VM that one of our Ames Technology Hub members logs into and runs AI workloads, though I do not know what they are using, and I doubt they are using Red Hat Enterprise Linux (RHEL) AI.

In our company implementation of the zero-trust model, Red Hat Enterprise Linux (RHEL) plays a role by using SE Linux and firewall D to configure everything and set it all up, although we have a different tool for managing Windows and micro-segmentation, and we have not implemented that on Linux since Linux is such a small portion of our company's business.

I have not done a major version upgrade with Ansible Automation Platform because we do not have it yet, but I have done major version upgrades from seven to eight and eight to nine with Satellite using the Leapp package provider. I have not done any nine to 10 upgrades because no applications really support it.

The transition from previous versions to Red Hat Enterprise Linux (RHEL) was smooth; we tried converting all of our existing VMs over to Red Hat, and that was hit or miss on whether it would work. This is through no fault of Red Hat's, as Oracle Linux does not migrate over to Red Hat smoothly, but the major version upgrades have been flawless and have worked every single time.

Our company's process for managing regulatory compliance does not involve Red Hat Enterprise Linux (RHEL) playing a role, as we are not a publicly traded company, and we also do not house any PII or credit card information, so we are not under any regulatory compliance. However, our auditing team checks what users have root access to these servers or super user privileges, and at the moment, we just run an active directory audit since they are all joined to our active directory. In the future, I am hoping to set up Red Hat Identity Manager to manage SSH keys and user access into Linux servers.

Overall, I have loved the experience with Red Hat Enterprise Linux (RHEL), as I have used Ansible for six years of the seven years I have been doing this professionally. We just hired a new Linux admin, and one of the first questions I asked was about their experience with Ansible. They had worked with it, so I asked about their experience in writing playbooks or roles, and they have written them extensively. I would rate this product a 9.5 out of 10.