Red Hat Enterprise Linux's role-based security model enables us to provide discretionary access levels to users based on their roles and their responsibilities. We can also assign access based on service level to maintain service-level accounts for any purpose. If we need to back up a Red Hat Enterprise Linux box, we can assign a role to access that box only on the backup level. 

Red Hat Insights allows us to find vulnerabilities and conduct assessments from our central portal. It gives us insight into the compliance levels of different boxes and their licenses. Red Hat Insights helps us be proactive by giving us the details of recurring issues and vulnerabilities or zero-day threats. It automatically shows us what needs to be prioritized. It improves operations to have a single pane of glass for all your inventories and business. You can also implement automation and remedy most things from the cloud console. This is very helpful. 

Red Hat Enterprise Linux helps us achieve security standards certification. Most of our customers require compliance with regulations and internal security policy also. We have to be compliant with the profile for each standard based on Red Hat Enterprise Linux profiles or OSCAP integration. Satellite helps us remedy and manage compliance issues in daily operations.

Red Hat Enterprise Linux is the most reliable Linux flavor in terms of enterprise governance. I prefer it for its code stability, support, and integration. The lifecycle management features help us maintain compliance and keep the components updated.

The built-in security features simplify risk reduction. For example, Red Hat Enterprise Linux has built-in OSCAP profiles that we can select during implementation based on our industry and compliance needs. Using the OSCAP profile, we can minimize the effort needed to keep the software up to date. We also like the Red Hat Co-Pilot, which allows you to configure most things from the GUI.

We also have OpenShift, which enables elaborate, portable, and reliable ccontainerization. We use the System Roles feature when we have to disable root users and assign the system roles on the application level because some applications do not require root-level access or real group access. The System Role feature allows us to impose level controls and segmentation between the users. We can also automate security configurations to maintain consistency across systems over time.

I would like to use OSCAP profiles without the dependency on Red Hat Insights. If you install the OSCAP profiles from Red Hat Insights, I'm not sure if it is currently available in the cloud console. Most of the time, we manage compliance from Red Hat Satellite, but this feature could also be built into the console. Maybe it's not an issue price-wise most of the time, but it would be easier if we could use the same console and test-level capabilities.

I also want the co-pilot to provide more granular control and more features in the GUI, so we can have one configuration from the GUI itself. It would be helpful to have a feature similar to the one in Windows where we can manage all the net flows from one console in a single pane of glass and install it on-premises like an admin center. It would be great if Red Hat had some kind of admin center to manage all the Red Hat Enterprise Linux boxes without using an additional product like Satellite or something, we could use the co-pilot on all the systems to monitor the dashboard.

We started with Red Hat Enterprise Linux 6 in 2015. Now, we are on Red Hat Enterprise Linux 9, so it has been around eight or nine years.

Red Hat Enterprise Linux is a robust product. 

The scalability depends on the computing capacity and architecture. It varies based on whether we are replicating boxes or putting the Red Hat Enterprise Linux images into containers. The tool we use for orchestration is also a factor. 

I rate Red Hat support 10 out 10. We are mostly dealing with Level 1 or Level 2 support, and we always get a prompt response. Remote support is also available, which is nice. 

Positive

We used some open-source Linux flavors that are now obsolete and CentOS. Red Hat Enterprise Linux provides excellent support for migrating from CentOS to Red Hat Enterprise Linux at any level, so kudos to Red Hat for that. There is a great tool that enables us to migrate an existing application without any changes, so we can convert CentOS boxes.

There are one or two commercial Linux flavors that can compete with Red Hat, but their based on different architectures. Red Hat has a large portfolio, including OpenShift and SQL automation, offering deep integration between these tools. I don't think there is a competing product that offers a comparable product portfolio because Red Hat is under the umbrella of IBM now and also provides a multi-cloud solution. 

The initial deployment is straightforward. There's no problem. However, it also depends on what we want to achieve. Some of the options add a little complexity. It isn't very complicated, but it requires a different method. Overall, the general installation and configuration are effortless, and we don't have any issues. The initial installation can be done in 15-30 minutes, depending on the computing and storage capacity. 

We have one administrator experienced in Red Hat Enterprise Linux and enterprise Linux for maintence. We prefer a certified person who can understand the data complexities and advanced configuration, but a technician doesn't need to be a specialist to conduct the installation. 

The pricing depends upon the customer's bill of materials and what the customers are planning. Sometimes, a reseller and vendor partners provide a better price. I recommended buying the Red Hat Virtual Data Center instead of buying the Red Hat Enterprise Linux standalone licenses if anyone just wants to run a workload in the cloud environment. Virtual Data Center is the most cost-efficient.

The Red Hat Enterprise Linux license has a one-time cost, but there is an ongoing subscription for support with various levels. The license is perpetual, but we pay annually for support. Red Hat's support license is robust. You get three levels of professional support plus community support. Our banking, finance, and telecom clients rely on Red Hat Enterprise Linux entirely for their production workloads, so they need to minimize downtime. There is no comparison between professional and open source. We can provide support for some of our clients and set up redundancy, so that's something we can consider when we're looking at licensing or support costs. 

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.  

We have almost thirteen servers. There are SaaS applications installed on this server. We leverage Java and the functionality during installation. We install it on the platform and configure it there. Some are custom applications. Our database is also in the Red Hat Linux environment. 

The solution offers users easy access. It's very simple to have and use, from an admin perspective. 

The offering provides me with all I need to serve the operation in terms of usage and capabilities. 

The general user commands are good. They are helpful for starting and stopping applications and restarting and editing files. The maintenance of user-level processes is easy. 

We're not using it in a graphical environment, we're only using command line mode. There may be a lot of features, however, I don't use everything since I don't need to. 

There are millions of commands you can use, although we use only five or ten.

Likely the solution has helped our organization save on costs. I'm not sure by how much, as I don't have visibility into that aspect.

It's very easy to use across physical, virtual, and cloud infrastructure. Specifically, on the cloud side, I have noted it's quite easy. Also, on a virtual machine, you can create a cloud version of your infrastructure in a minute. 

For my work, the solution is not missing any features. We;re only using the command line and that is enough for us. 

Maybe they need to make it easier to apply patches from different resources. That said, at my level of usage, I never have to apply patches. 

I've used the solution for almost ten years. 

It's a stable product.

While I'm maintaining 30 servers, there are hundreds of servers in use. 

The scalability is good. We are able to increase capacity and functionality based on our demands. 

I'm not sure if the company has plans to increase usage in the future.

I don't directly deal with technical support. I might send a ticket to my side, and if they have to, they would be the ones to reach out to Red Hat. 

We used Oracle Linux before we moved over to Red Hat Linux. We likely switched due to costs and licensing. We also use Windows extensively. Since we used the same architecture, we didn't need to use any third-party applications.

As an admin, I was not involved in the setup process. 

If there is any maintenance needed, we get support from the Red Hat team.  If anything comes up on the operating side, our team will take care of it. 

I'm only using this solution as an admin and, therefore, have no visibility on costs. 

We did not evaluate other options before choosing this solution.

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. 

We are an Azure shop that runs middleware applications like Java and JBoss, running on the Azure back end. We have to redeploy everything via ARM templates. Anytime we do an upgrade of the application itself, it's a redeployment. We have custom images that we set up through Azure pipelines. We use Ansible for code changes and server changes.

The solution's stability is great, and patching it with Ansible is very easy.

The solution's licensing sometimes could be a little bit confusing for someone who's not a full-blown system admin and doesn't have a lot of experience with Red Hat Enterprise Linux. It took a while for me to understand the licensing.

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

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.

My primary use case is for web applications and database applications. I've come across quite a few use cases at different companies.

The most valuable feature is the package management. It helps a lot. I also like the support. 

Red Hat is a Linux-supportive and well-managed offering. It helps a lot in terms of when we're working in production, it gives us the confidence that our packages are legitimate and genuine and we always have support available. It helps a lot. Red Hat Enterprise Linux gives peace of mind compared to other unsupported Linux distributions. 

I also like Red Hat Satellite. 

I haven't used Insights yet but it seems interesting. 

The ability to patch Red Hat Enterprise Linux through Satellite is a huge contributor to mitigating all of the compliance requirements.

Red Hat Enterprise Linux has absolutely affected our security's uptime. None of the other distributions are nearly close to what you can get with Red Hat Enterprise Linux. Red Hat Enterprise Linux is something that helps a lot in ensuring that your secure application is up all the time and that you're not getting hit by vulnerabilities. It is an easier way for you to mitigate vulnerabilities when they're around.

The knowledge base is very useful. The only thing is that you need to have an account to get access. In terms of the content, the relevance, and being able to use the knowledge base to address things I've needed to deal with, it's awesome. For example, I was trying to add proxy configuration to the package manager once and if it wasn't for the knowledge base, I wouldn't have been able to do it.

I like it the way it is. 

It's getting easier for the community to use it free of charge. If you have an account, you get to use it. It would be better if the community could use it on their own for lab projects.

I have been using Red Hat Enterprise Linux since 2011. It's been 12 years. 

On the few occasions I needed to reach out to support, I was very satisfied.  

Positive

I have used Linux distributions but when it comes to the work I'm doing at my company, we always use Red Hat Enterprise Linux. 

The biggest differences between Red Hat Enterprise Linux and the other OS' are the support, Satellite, Insights, and the fact that Ansible was acquired by Red Hat so you can use all its automation and toolings. The entire ecosystem works very well together.

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.

We are a Linux shop, so a lot of our engineers are familiar with Linux. We try to push Red Hat Enterprise Linux instead of Windows. The reason for it in the beginning was licensing. Some of it was because of the way the contract was set up. It was cheaper, but we do use it now just for the ease of it. I do not know if it is because of Ansible, which we use for a lot of our day-to-day operations, that we tend to lean more toward Red Hat.

Red Hat Enterprise Linux has affected our system's uptime or security. I know Microsoft publishes zero-day vulnerabilities for Windows as fast as Red Hat, but we noticed that in terms of problems or alerts that we get for attacks or viruses, there is not anything on the Red Hat side. That is why we feel that it is more secure. It might be just the nature of Red Hat where all services and ports are off. It is not like Windows where everything is on, and you have to turn it on. I was having a conversation with one of the gentlemen who is also attending the Red Hat conference, and I got to know that there are built-in NIST features with Red Hat that we could turn on, so we do not have to try to figure out how to harden our system.

The testing of the updates or the packages of the kernel is valuable because I used to be a part of the Fedora project. I know it is all vetted out before it gets to production, but a majority of it is the support and the relationships I have with the Red Hat employees assigned to our account.

As they move over to newer versions, certain things change, which is expected as the technology matures or new things come out, but what really surprises me are the features that are there in the cloud, such as Red Hat Insights. They are not there on-prem. There are a lot of things on the cloud portal that I did not notice before, and I was surprised because we were unaware of them. Red Hat is doing a lot of investment in that sense.

The knowledge base offered by Red Hat Enterprise Linux is good. It is easy to parse through all of the knowledge base. I do not know if Windows does it because I have not looked at it, but in Red Hat's knowledge base, there are a lot of things. They fast-track a lot of things in their knowledge base, even when they are not yet official. Especially with the tie-in with Bugzilla, even though it is not a true KB, we can see and follow if other people in the world are hitting a certain problem or something similar to what we are experiencing. I like that.

It would be great to have an overview of how various Red Hat products work together. They can show how to tie all those pieces together and how to have the products that we work together for our day-to-day processes.

I started with the company around 2012, and they have been using it even before then. At that time, it was Red Hat Enterprise Linux 5, and now, we are up to Red Hat Enterprise Linux 9.

In 10 or 11 years of using Red Hat solutions, I have opened only one or two support tickets. It probably was something during a patch and during Satellite 5 to Satellite 6 migration. I would rate them a 10 out of 10.

Positive

In Linux, there are so many different flavors, but I am partial to Red Hat because I have been a part of the Fedora project. At our place, we have only two operating systems: Microsoft Windows and Red Hat Enterprise Linux. I know CentOS, but that is usually because the appliance from the vendor was set up using that. That is why we had a few instances of CentOS in the past, but nowadays, I do not see any other flavors of Linux.

For the majority of our use cases for Red Hat, we have on-prem deployments. There are some things that they are trying to spin up on AWS. I do not know if they are cloud-native apps or not, but I know our developers are now moving on to it.

I have been involved in the initial setup, upgrades, and migration of Red Hat Enterprise Linux. I did not have any problems while going from major OS versions. I always push new upgrades or homogeneous migrations, such as from version 6 to version 7 to version 8. There is probably an option to upgrade in place. Overall, with Red Hat OS, I have not seen many problems. A long time ago, when they went from Python 2 to Python 3, there were certain things we had to change in the script.

I know that Red Hat is moving to Wayland from X11, but I do not see any problems there. From Satellite 5 to 6, it was a bit hard in the beginning, but now, it is pretty self-explanatory. Overall, everything about which we had questions was very well documented.

In terms of our upgrade and/or migration plans to stay current, first, we look at the EOL and the roadmap of Red Hat because of security. We used to offer every single version before the said EOL happened, but now, we just do an n-minus-one. We try to maintain the newest and one level below version. SAP users are the biggest Red Hat Enterprise Linux users in our environment. They have a particular PAM and upgrade path that they have to do with Red Hat. We also wait to be certified to certain versions, but our main strategy is the newest and one major version down. We try to get everybody off the other versions.

Our provisioning is all done using VMware products. We have a vRealize automation, now called the Aria automation, to spin it up. Patching is done through Satellite. I do not do it, but when I watch them doing it, it seems it is just using remote SSH commands against the list of non-prod and prod servers. It is something simple. We do not seem to be doing anything complicated. I am wondering if there is a better way to do versioning control or patching and whatnot, but currently, it is very simple.

I am satisfied with the management experience not only in terms of patching but also the day zero to day one or day two stuff. We are interested in utilizing Ansible to eliminate human error and whatnot. During provisioning, we have Pearl scripts that we have to manually trigger. I know we can use Ansible for that, but it comes down to the cost of entry which is still very high. 

A lot of people are moving into the core count for licensing. We still have a few with one-to-one standard server licensing, but we are utilizing the virtualization host licensing. We license it based on the host, not based on VMs, which is cool. I was very happy that there was certain licensing with SAP to have access to SAP repos. Its cost was the same as the regular one, so I was happy about that.

The only pricing that bugs me right now is the Ansible pricing. We wanted to take a look at Ansible, but the biggest thing a year back with Ansible was that the management did not want to spend half a million on Ansible Tower. They wanted to see first if we would use it and not waste money. I do not know if things have changed now, but Ansible is probably still expensive. That is one of the routes that we want to go to. We will see if we can utilize Ansible Tower, so pricing-wise, that is the only thing that pops up. It is too expensive. The cost of entry seems quite high.

Overall, I do not see any issues with what we have spent on Red Hat. We also have learning subscriptions that we pay to Red Hat for the training, and I do not feel we have wasted any money.

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.

I use Red Hat Enterprise Linux for running applications and databases on them.

It has a smaller footprint, so it uses less storage. The product is optimized for resource utilization. Patching is very streamlined for the operating system compared to Windows. We prefer using Red Hat Enterprise Linux over Windows whenever we can. Patching is much easier, and it seems more mature. When we apply a patch, we're less likely to have problems after. It's more stable.

All resources should be available on the website.

I have been using the solution for about three years.

I rate the support a nine or nine and a half out of ten. I am not rating support a ten out of ten because if we were able to receive all of the resources that we could from the website, then we wouldn't need to reach out and contact support. It's a learning curve.

Positive

Previously, we used CentOS. We have also used Oracle Linux, which is based on Red Hat Enterprise Linux's kernel. Now, we're strictly trying to use Red Hat Enterprise Linux. We switched to Red Hat Enterprise Linux because it provides great support.

The products are pretty similar. A lot of the implementations, commands, and updates are very similar. Overall, we've had a more positive experience using Red Hat Enterprise Linux. We have a basic build routine when building new servers, updating, and installing add-ons. When we run those scripts, it seems like it's so much more streamlined with Red Hat Enterprise Linux. It could be because we're converting everything to Red Hat Enterprise Linux.

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 have Ansible deployed on our Red Hat Enterprise Linux servers. We use it to manage the security of our fleet of Ubuntu virtual machines.

Red Hat Enterprise Linux is way ahead of Ubuntu in terms of security and compliance. It is mainly the ecosystem of data science tools that our developers want that pushes us in that direction. As a security engineer, I have a lot more peace at night knowing that my Red Hat servers are doing a good job keeping our Ansible infrastructure safe because that has fingers into everything we do. It is pretty critical.

Red Hat Enterprise Linux has not affected our system's uptime in any particularly noticeable way.

Red Hat Enterprise Linux has not enabled us to achieve security standards certification because we do not have any yet. We will have them hopefully in the future.

There are some nice integrations with scanning for vulnerabilities. That is the feature I have enjoyed the most because I am a security person, and that is my bread and butter.

Ansible has certainly been a game-changer. It is a lot easier to keep a whole bunch of virtual machines consistent with each other and make a change consistently across all of them. We use them for data science activities. Our data scientists are constantly trying out new packages and downloading new tools. We have to enable them to have root access on their machines but also need to ensure that they are not doing anything stupid at the same time. There are competitors to Ansible, but we are a big Python shop, so it is a very comfortable environment for us.

The only issue we have had with it is around the SELinux configuration because the way Ansible installs, it sticks the platform passwords in a flat file. We want that locked down more strongly than what is there currently with SELinux. 

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

I would rate their support an eight out of ten.

Positive

Primarily, we have used Ubuntu. We have had some of our use cases on CentOS, and then, of course, our workstations are all Windows, but I wish they were not.

We chose Ansible, and that chose Red Hat Enterprise Linux for us.

We use Red Hat Enterprise Linux in the cloud. We have Azure because it is the corporate standard. We do not have any concerns about using Red Hat Enterprise Linux in the cloud. Obviously, everything in the cloud is more exposed than everything on-prem, but it has got good, sensible, and secure defaults built in, so there are no concerns there.

In terms of Red Hat Enterprise Linux upgrades, when we upgraded Ansible this fall, that pushed us from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8. It should be a little easier from now on. Now that we have made the big jump from the older Ansible to AAP, we will probably be upgrading the systems on a quarterly basis.

We probably have not yet seen an ROI. We purchased it a couple of years ago, but we have not had the time to put it to as much use as we wanted to put it to. The cost is low, so it would not take very long to reach a return on investment.

We have not made use of the Committed Spend.

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

We have a lot of Oracle databases, Tomcat, and Java microservices running on Red Hat Enterprise Linux.

A lot of our applications are like Java microservices. Deploying them on a Unix platform is so much easier. It's open-sourced and provides a lot of compatibility. It makes it easier for us to roll out applications. It is compatible with most Java microservices applications.

We like that Red Hat Enterprise Linux is a vendor-supported product. When we have problems, we just call Red Hat Enterprise Linux for support. The product employs a lot of automation tools to manage its OS. We love using Red Hat Satellite. We have close to 5000 servers. Managing individual servers would be a nightmare.

Red Hat Ansible Automation Platform and Red Hat Satellite help us automate our repetitive tasks. Every flavor of Linux distribution has its own specialties. The product offers a lot of integration within the Red Hat products suite. We use Red Hat products mostly, so it works for us.

The vendor keeps rolling out many packets, which complicates our job. We keep patching our servers. CVEs come out all the time. However, having a solid and secure OS will make our life much easier.

I have been using Red Hat Enterprise Linux since 2004.

I never had any problem with support. I didn't have any issues that I did not get a resolution for. Sometimes, it takes a little bit of time, but eventually, it gets resolved.

Positive

I was using AIX, which is also an IBM product. IBM bought Red Hat Enterprise Linux. AIX was more expensive and required IBM System p. Moving to Red Hat Enterprise Linux was much easier because it is a lot more compatible with the regular hardware like HP and Dell that we buy on the market.

I have seen an improvement in our deployment. When we have applications running on Windows, it takes longer to get them set up and provisioned, and the security is different compared to Red Hat.

The pricing could be better. The tool is getting expensive. Before, we could license only the hypervisor where Red Hat Enterprise Linux is running. Now, if a customer has a 12-node hypervisor, Red Hat Enterprise Linux forces customers to license all 12, even though they use only six.

We evaluated SUSE. At that time, SUSE did not have good support. We needed good support worldwide.

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.

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

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

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

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

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

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

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

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

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

I have used Red Hat Enterprise Linux since 2005.

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

Positive

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

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

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

We use it for databases and applications. In the new model, we keep databases separate from applications. Currently, about 90% of our operations are running in Red Hat 8. Some systems are still on Red Hat 7, but those will be migrated off by the beginning of next year.

It's been great since we have it. It's been reliable and fast. We keep all the security agents, and we've been taken care of right away, and that's the improvement in our company. It's with the new RHEL. There's always something new, something good that works for us. 

Moreover, we might need to move workloads from the cloud in the US to China in the future.

As we're migrating and doing the Elite upgrade, which is an in-place upgrade, we find it great. We use it for databases, and we're testing it for applications. Some applications don't work, but some are functioning well. So far, it's been a positive experience.

Since I'm more focused on migrating, Leapp is awesome. We are able to do something that will work the way it's working.  There are no issues or breaks.

RHEL's knowledge base is great. It's very good. Especially when you try to open a case, it gives you all the options you need, so you don't have to wait for the case to be opened. You can get all the information you need right there.

Moreover, I am in the process of testing Leapp and Red Hat Insights. And then create our images from there rather than create MIs.

At the new company, we've been using it for three years. At my previous company,  we used it for over five years. Personally, I have been using it for almost eight to ten years.

We often have to go through people who have the same labels as us and who have the same knowledge base articles as us, which takes time. But they do it first; it's searching the knowledge way that I search. That I can do. That takes the time before. They do the payment. They sent me exactly what I had already found. And then we can go to the next level. That is taking a little bit more time that we can be a little bit better. So, the initial step of the support process could be improved. 

90% of people who open those bases are administrators who already look on the Internet for all these knowledge bases. So by the time we get there, we're gonna get the knowledge base back. And that's not helpful. 

Positive

I used to use HPUX and Solaris. We switched to RHEL because HPUX started looking like it was going away, so we started moving to Red Hat. We thought it was our best option. We tested different flavors of RHEL.

When it comes to provisioning and patching, we have a satellite server. We use a lot of Ansible. We are getting used to Ansible and Satellite servers. 

The initial setup wasn't complex, but since we wanted to make it easier to use, it became harder to make it work the way we wanted. Not out of the box, so we can just build a server that is ready to be deployed right away without any more interventions.

We use RHEL with AWS because it's easier for us to maintain since we create our own AMIs and we update that as we need it. So we don't need to follow their schedule until we get it more secure and more reliable for us.

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