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

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

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

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

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

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

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

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

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

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

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

It is a scalable solution.

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

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

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

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

The solution is used on an on-premises model.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

It is a stable solution.

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

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

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

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

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

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

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

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

I would recommend Red Hat Enterprise Linux (RHEL)to a colleague who is looking at open-source cloud-based operating systems for Linux since it offers Red Hat Satellite, so everything is just so encapsulated and there in the tool.

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

I rate the tool a ten out of ten.

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

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

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

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

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

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

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

It is a stable solution.

It is a scalable solution.

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

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

The product's deployment phase was simple.

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

The solution is deployed on an on-premises model.

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

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

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

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

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

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

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

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

I don't use Red Hat Insights.

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

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

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

I rate the tool a ten out of ten.

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

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

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

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

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

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

In terms of the portability of applications and containers built on Red Hat Enterprise Linux (RHEL) to keep our organization agile, I would say that we have an applications team that would do it in our company. I just make sure that our company's VMs have OS and network connectivity since there is a different team that takes care of the applications.

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

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

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

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

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

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

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

The solution is deployed on an on-premises model.

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

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

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

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

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

I use the solution in my company for regular servers with databases, load balancers, Apache, and so on.

The benefits of using the product revolve around the fact that it has made it easier to automate everything on it, which includes automating servers and so on.

The most valuable feature of the solution is that it is an upcoming, more stable product, like Oracle OS. The tool has everything that IBM Red Hat Redbooks has.

In terms of how I would assess the portability of applications and containers built on Red Hat Enterprise Linux (RHEL) for keeping our organization agile and flexible, I would say that since my company is a service provider, we get the containers from the customers, which we don't use for our own selves, but we use Red Hat Universal Base Images (UBI) 9 for some things like to to get our own containers and so on.

My company has not tried to use Red Hat Enterprise Linux (RHEL) 9 since we are still using Red Hat Enterprise Linux (RHEL) 8. In the future, I am expecting to see Podman 5.0 released for RHEL 9.

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

It is a nice and stable solution. Some problems may occur with the product if you don't patch it after a year or two.

There are no problems with the scalability of the product, as it works fine.

Previously, my company used to use a simple version of RHEL and other tools depending on the needs of our company's customers.

Regarding my experience related to the deployment process, I would say that everything is automated now. You just fill out the survey, and then you just deploy the tool. The product's deployment phase is easy.

The solution is deployed on an on-premises model.

The team members can deploy the solution in my company.

If the customer wants to pay for the support and so on, then we can go for Red Hat Enterprise Linux (RHEL). Otherwise, one can go for any other open-source platform. With Red Hat Enterprise Linux (RHEL), you get the latest on everything. If you are running Oracle Linux, it gets hard to find some patches. It is easy to find new things like Podman or Red Hat Subscription-Manager, especially if you want to run something on Oracle OS, then you need to compile the patches yourself.

The product has helped centralize development in our company. In our company, we are mostly automating all the server installations on Red Hat template by filling in IP addresses with Postman.

We don't use the built-in features of Red Hat Enterprise Linux (RHEL) for risk reduction, business continuity, and maintaining compliance since they are only available in Red Hat Enterprise Linux (RHEL) 9.

To a colleague who is looking at open-source cloud-based operating systems for Linux other than Red Hat Enterprise Linux (RHEL), I would say that previously people preferred CentOS until Red Hat stripped it apart. At the moment, it is like, if you want an RHEL-based tool, it is either Rocky Linux or Oracle OS because I think Fedora is too lenient, while CentOS is somewhere in the middle.

I would be spending the same amount of time on some other solution if I was not using Red Hat Enterprise Linux (RHEL) since everything is automated now, and in such a case, it will just be another image you use on some other product.

My company uses Ansible as a part of the deployment model.

The product is easy to use, and you can get support whenever you want. The solution also the latest packages, which include Red Hat Subscription-Manager, Podman, Linux, and other such functionalities.

I rate the tool a nine out of ten.

A lot of our Red Hat operating systems run middle-tier applications. We are mostly a JBoss shop, so they are homegrown applications. They are Java-based. We have several types of applications. We have identity, security, Oracle database, etc.

Red Hat Enterprise Linux helps with standardization. A lot of middle-tier applications hosted in the data center or in the cloud are unified in one standard operating system, which is Red Hat Enterprise Linux. On the data center side, we only have Red Hat Enterprise Linux. We have one unified operating system.

For our containerization projects, we are looking into OpenShift. Our Ansible Automation Platform executioner uses container-based Red Hat Enterprise Linux. We use Podman. We have moved to the Red Hat Podman container. It is a lot easier. We can scale up easily and manage it. It reduces the security risk. We do not have to worry about patching. We can just image a new container that is up to date. That is great.

We had a situation where we had to create an image for Red Hat Enterprise Linux 9, and there were built-in playbooks for hardening the system. We were able to run that and create the image. It made the work much easier than it used to be in the past.

Red Hat Insights provides vulnerability alerts and targeted guidance. It has that capability. It has a lot of features built in that not only help with security but also with misconfigurations. If a system is misconfigured, it detects that. It gives you the solution for the problem it captured. It is a great tool, but we have been focusing on the security perspective. We have not been focusing on operating system configurations. I have not yet looked at the new version, but in my opinion, it would be better if Red Hat puts a lot of focus on Insights and take it to the next level where the company could use it for its OS compliance.

We have all types of different versions running in our environment except the obsolete ones. We are moving towards versions 8 and 9. We have had version 7, and it has been very stable until now. It is ending this year around June 30, so we are in the process of moving to version 8, and we have just released an image for version 9. So far, version 8 has also been very stable.

It is a Linux-based operating system. It integrates with our automation base. We have Red Hat Satellite and Red Hat Ansible. All the engineers who are a part of our infrastructure or operation on the Unix side are Red Hat Enterprise Linux certified, so it is a lot easier for us to manage and integrate with the tools that we have. It makes much more sense from the middleware perspective and management too.

The bootup time for Red Hat Enterprise Linux running on physical hardware in the data center can be improved. We have seen cloud-based Red Hat Enterprise Linux, and it is instantaneous. You wait for a few seconds, and the operating system is up and running. It is a lot faster, whereas it takes a very long time when running Red Hat Enterprise Linux on physical hardware.

We used Red Hat Insights, but we are more focused on compliance, patching of operating systems, and things like that. In the past, when we looked at Red Hat Insights, it was its own platform, and then it migrated to Satellite. Companies are struggling to be compliant from the security side. Everyone is focused on how to patch the systems, what the environment looks like, whether they are under 90-day CVE, how their environment is compliant, and where they can see it as a dashboard. I wish Red Hat Insights was focused on that. From the Red Hat perspective, I am not seeing any sessions. I do not see anyone talking about that, which is a huge deal for us. I would like Red Hat Insights to go to the next level where it is focused on patching and compliance.

I do not have any other areas of improvement. It has been stable for us. There is a lot we do in terms of automation and integration. I know Red Hat 8 now has Podman for containers. Cockpit has a UI, so that is good now. That helps with certain things.

We have been using Red Hat Enterprise Linux for close to 20 years.

We have not run into something that caused a huge problem to our environment. If something is happening, such as it is running an Oracle database and that system has kernel panic or something like that, it is usually the database or application software running on the operating system. It is not the operating system itself.

We have not run into any major infrastructure incident costing us because of the operating system. They have it integrated with all other products such as OpenShift, OpenStack, etc.

We have three data centers at different geographical locations. Two are in the state of Georgia and one is in Las Vegas. In all three data centers that we manage, the compute-based are all Red Hat-based.

We have a Red Hat TAM, and that helps a lot in terms of the problems and things that we run into. He is the interface with Red Hat. He escalates our service tickets and things like that. That is a huge help from our perspective.

The support that we get directly from putting tickets in has always been great. Red Hat Enterprise Linux is probably the best and most stable product that Red Hat has especially in regards to getting support and getting things fixed. They are on top of that. It has been a great experience. I would rate them a ten out of ten.

We used to run Sun Solaris. We were a Sun Solaris shop in the beginning. This was 15 or 20 years ago. We moved because of the Intel-based hardware, licensing, and cost reduction. Moving away from Sun SPARC hardware to Red Hat was a lot of saving. It saved a lot for the company. We can now run Linux-based systems on Intel commodity hardware using Dell.

Its usage is growing. Our team is working with other business units within the enterprise to get them onboarded to the Red Hat-based operating system. We have multiple entities that are running CentOS and Ubuntu. We have to have a standard operating system, and that is Red Hat. Our portfolio is increasing. We are growing and migrating a lot of nonstandard ones to Red Hat.

We have an enterprise technology group that utilizes Oracle Linux. We have worked with OEM. Our team is managing that too.

We are using Red Hat Enterprise Linux on-prem. We also have a cloud environment, but other teams are using it on the cloud. The cloud provider is AWS. The database team also uses Red Hat Enterprise Linux in AWS.

We use Red Hat Satellite and Ansible for Red Hat Enterprise Linux deployment across all three data centers.

My first deployment experience was almost 30 years ago. I started with Red Hat Enterprise Linux 4 or something like that back in 1993 or 1994. There has been a tremendous change in the way you install it and utilize it now. It is night and day. It has come a long way.

We implement it on our own.

Our costs are reduced. We can allocate that OpEx and focus on some other project. We do not have to struggle and say that this is how much we are going to pay licensing just on the operating system cost. We now have a model that works for us.

We are a huge VMware shop. Our licensing cost works well with Red Hat. We license based on the data center. The way our license works is that we can run as many Red Hat VMs as we want and pay for a single license. On the VMware side, we gain a lot, and it makes much more sense.

We did not evaluate other operating systems and compared them with Red Hat Enterprise Linux. We just went from Solaris to Red Hat.

We are an agile environment. We practice agile methodology. Anything we manage and deploy has to go through a sprint phase. We do not have a fully containerized environment. In the future, once we adopt OpenShift, it is going to increase our productivity because of how we manage things through agile. It is going to help us a lot.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say that it all comes down to the company and how a company foresees security. Anything we support and manage has to have a support base. If something gets impacted from the security side, we know that we have Red Hat support, and it is reliable. We can get the patch we want. If you install an application that needs a bug fix, you can reach out to Red Hat and open a ticket. If you want to have a stable environment, then I would highly recommend getting the support and running Red Hat.

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

I use the solution in my company mainly for the operation system of the core business applications.

My company has experienced benefits from the use of the product, especially considering the agility that the tool offers in terms of the time to market in different areas of business and because of its compatibility with most of the applications in the market.

The most valuable features of the solution are the stability and scalability.

I run Red Hat Enterprise Linux (RHEL) on a hybrid cloud deployment, and it has impacted our company's operations, but I would say that it has been quite simple to implement, especially considering the security, which has been a considerable piece of the infrastructure.

Red Hat Enterprise Linux (RHEL) has helped centralize development in our company. The applications run with Red Hat Enterprise Linux (RHEL), and it became the standard for the operating system for the applications.

My company uses Red Hat Enterprise Linux (RHEL) for containerization projects with OpenShift. This use of Red Hat Enterprise Linux (RHEL) has had an important impact on containerization, as it is a simple process. Owing to the simplicity, we always involve the solution's experts and get faster solutions.

The built-in features of Red Hat Enterprise Linux (RHEL) for risk reduction, business continuity, and maintaining compliance are very important because our company is always aware of all these security issues that constantly happen.

Though the product has many features, the tool's virtualization area has certain shortcomings that require improvement. The product should also offer more containers and probably some financial services.

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

It is a very stable solution.

It is a quite easily scalable solution.

The technical support for the solution is very good. I rate the technical support a nine out of ten.

Before Red Hat Enterprise Linux (RHEL), my company used to use Windows. My company started to use Red Hat Enterprise Linux (RHEL) after we found that it offers more stability, sophistication, and security and serves as a standard for many products.

The product's initial deployment phase was easy and quick.

My company did follow some strategy to deploy the product, and we also had the support from the vendor.

The solution is deployed on the cloud and on-premises models.

My company sought the help of a system integrator during the implementation phase of the solution.

In terms of ROI, I see that the tool offers stability, performance, agility, and resilience.

If I describe my experience with the product's price, I would say that we have to live with it for now.

My company evaluated other Linux products, such as SUSE Linux Enterprise Server (SLES), against Red Hat Enterprise Linux (RHEL).

I would recommend Red Hat Enterprise Linux (RHEL) to a colleague who is looking at open-source cloud-based operating systems for Linux since it is a tool with more market experience and offers more documentation and support from the vendor, which is not easy to acquire when it comes to open-source software.

Red Hat's portfolio has affected the total cost of ownership across our enterprise landscape by around 10 to 20 percent.

My company has the product in two data centers, but the production happens only in one. Mostly, my company uses the cloud services offered by Azure.

I rate the tool a nine or ten out of ten.

I use the solution in my company to deploy our custom apps or to set up servers for DevOps operations, like running containers and those kind of tasks.

The benefits associated with the product for my company stem from the enterprise support the solution offers. Based on the fact that our company has technical exchange meetings with the product's staff members, I can say that I have never seen something like that happening in a hands-on engagement with our company, so that is just great. Being able to talk to the solution team about our company's issues and problems related to the tool all the time is something that really helps a lot.

I can't say anything specific about the product's valuable features, but I would say that whenever I have questions, I feel the tool's documentation is on point since I can always find anything I need easily.

There are some points in the solution's documentation where a few areas seem generic. The aforementioned area consists of the same scenario when it comes to some of the other products, so it is not just applicable for Red Hat Enterprise Linux (RHEL) alone, but also for some of the other supported products. I have never had a problem with Red Hat Enterprise Linux (RHEL), as it is really easy to use.

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

It is a stable solution.

It is a scalable solution.

I believe that there are definitely some plans to increase the use of the solution in our company in the future.

I believe that there are definitely some plans to increase the use of the solution in our company in the future, especially if we start to get more customers and there is a need to ramp up automated testing since we would need more systems.

The solution's technical support is really good and responsive. I rate the technical support a ten out of ten.

I believe that my company used to use a few products before starting off with Red Hat Enterprise Linux (RHEL), but I believe that it was before I joined the organization.

The solution is deployed on the cloud and on-premises models.

In terms of the ROI, my experience using the solution revolves around the product's community. The fact that I can just go out and even in an ecosystem in general with tools like Fedora, CentOS, and other stuff, I can always find what I want with the help of the community where there are people with similar experiences, especially if it is not available in the documentation part. I feel Red Hat Enterprise Linux (RHEL) is community-focused, and I really appreciate that as a developer.

Running Red Hat Enterprise Linux (RHEL) on the foundation of a hybrid cloud deployment has impacted our company's operations and I can say that it has been easy because there is not much to do between the two environments, as it is consistent, and that just reduces a bunch of headaches.

Red Hat Enterprise Linux (RHEL) has helped me centralize development. The operating system that we are developing is based on Red Hat Enterprise Linux (RHEL). In our company, we are able to use everything in the solution with the help of documentation, support shared knowledge resources, and all of that. Just using the tool to support our company's infrastructure is really great, and now we don't have to branch out and use other technologies. The tool is a platform that supports many different things.

I use Red Hat Enterprise Linux (RHEL) for containerization projects in my company as it is easy to use.

When it comes to the built-in features of Red Hat Enterprise Linux (RHEL) for risk reduction, business continuity, and maintaining compliance, I can't really say anything much about it because the product is used in our company for a specific use case and we put ourselves on top, so we don't really use the aforementioned components for the policies.

In terms of how I would assess the portability of applications and containers built on Red Hat Enterprise Linux (RHEL) for keeping our organization agile and flexible, I would say that the offering of minimal images and all such stuff really helps cut it down and make deployments faster. In our company, we are really excited to use Red Hat Enterprise Linux (RHEL) to check the containerization of our apps, so being able to do such things for our products helps keep everything moving quickly. In general, my company is excited that Red Hat Enterprise Linux (RHEL) is moving towards the area to check the containerization of apps.

I would recommend Red Hat Enterprise Linux (RHEL) to a colleague who is looking at open-source cloud-based operating systems for Linux.

In terms of the deployment model used in my company for Red Hat Enterprise Linux (RHEL), I would say that the tool is basically deployed on-premises for closed environments and in the cloud because some of our company's customers prefer to deploy the product on the cloud. Mostly, my company uses the cloud services offered by AWS, while some of our company's customers use the services from Azure.

I like Red Hat Enterprise Linux (RHEL) considering the support that it offers to our company along with good documentation.

I rate the tool a ten out of ten.

When we are looking for Linux servers or developers need Linux, we have standardized around Red Hat Enterprise Linux. We do not use Ubuntu or any random flavors of the day. If it is a Linux deployment, it is Red Hat.

It helps with standardization. If someone comes to us and requests a Linux server, we have one product offering. We have a couple of different flavors of it, but people know what they are getting from us. The consistency, reproducibility, and standardization of it have been fantastic.

We are using Red Hat Enterprise Linux on-prem and on the cloud. We have it in Azure, VMware, and on-prem. We have it on bare metal. It is all over the place. Our operations are simpler, more efficient, and easier to handle. Our Linux team now supports one OS rather than a whole bunch of flavors that everyone has brought in. It has just made things more efficient and simplified.

Red Hat Enterprise Linux has enabled us to centralize development. Those developers are now developing on Red Hat Enterprise Linux. Previously, we had people who were developing on Ubuntu and trying to push Ubuntu to production, but we did not necessarily support it. Red Hat Enterprise Linux gave us a clear path to production. Our developers also get an easier experience. They know which OS to use and what they are using from day to day. There is less confusion for developers.

We are using Red Hat Enterprise Linux for containerization projects. It has helped with simplification. We do not have to create too many of our own custom container definitions and do our own thing. We use minimal images and whatever is provided is supported under our subscription. It simplifies things and puts guidelines around things.

Red Hat Enterprise Linux's built-in security features are good when it comes to risk reduction, business continuity, and maintaining compliance. We use Red Hat Satellite to manage our Linux. That makes it all very simple. There is a feature called OpenSCAP. We use it for security scanning. All the features that they provide on top of the base OS make it very easy to manage.

The portability of applications and containers built on Red Hat Enterprise Linux is great for keeping our organization agile. We know we can rely on that middle layer. We can start with the container and then build on top of that. Having a solid and standard foundation makes it all easy to do.

The enterprise aspect of it is valuable. There is security patching, security scanning, and compliance. There are all kinds of features around managing and keeping it up-to-date and secure. Everything is in a box for us from Red Hat which makes it very easy to manage them.

It is constantly improving. It is important to continue to improve. That is another reason I like it. They are using newer kernels, which gives us access to newer hardware. They are already doing that. I cannot pretend to tell them what to do better. They can just keep on doing what they are doing.

Personally, I have been using it for about 12 years. I have only been with my company for about four months, but I know they also have been using it for years.

It is stable.

It is scalable. They define scalability. I am a basic user. I just deploy more VMs if I need to. It is easy to do. Its scalability is great.

They are great. I would rate them a ten out of ten. A big selling point is that when you submit a support ticket, you know you are reaching out to experts. That is great, and that is one of the primary reasons we went with Red Hat.

In my company, they were using AWX for automation, and we moved them to AAP. For Linux, I was a part of a project to migrate some of the other operating systems over to Red Hat Enterprise Linux. I am on the tail end of the move or standardization to Red Hat Enterprise Linux.

There were a lot of Ubuntu operating systems in the environment, but they had challenges standardizing around it. There were different versions. There was also CentOS, but it was old CentOS. They are naturally moving that to Red Hat Enterprise Linux.

The support and the standardization around it were the main reasons for going for Red Hat Enterprise Linux. CentOS is more of a community thing now, whereas we can call Red Hat and they help us with everything. The support and the enterprise features we needed pointed at Red Hat Enterprise Linux rather than CentOS. It is a better choice for production.

We deploy them from AAP and then we deploy them into VMware. We deploy them into Azure, which is our main provider. We do that all orchestrated through Ansible and Satellite.

We have outsourced support. TCS is a general contractor, but for Red Hat deployments, we generally go with Red Hat Consulting. We just finished a consulting engagement with them for that. I know they have used them in the past prior to me being here. We generally just use Red Hat Consulting.

We have standardization. I know what I am walking into every day. I know there is support behind it. There is the support of Red Hat and the community behind it. I feel confident using Red Hat Enterprise Linux. I might use other Linux operating systems at home, but a lot of the time, there is no documentation for them. There might be three guys in a forum from ten years ago who may have talked about my problem. With Red Hat Enterprise Linux, when I am going to work, I know what I am walking into. I can feel safe and assured using something industry standard that works, and I can get help with it very easily. It makes life a lot easier.

Our total cost of ownership across our enterprise landscape has gone up because we were using a lot of mixed and free open-source solutions. However, there was an extra cost of operations and extra cost of hiring for specialized skills and things like that. With the Red Hat portfolio, I feel that we spend more on subscriptions, and we save in terms of efficiency and operations. I feel that we spent some money to save money on the backend, and I hope that is how it ended up.

I do node counts for the Red Hat Enterprise Linux system. I am gathering data for our decision-makers about how many nodes we need and how many things we need. Once or twice a year, they ask us to true up and find out how many nodes we are using and what the actual consumption is. I then report that, and then the account team usually works on the money part of it. I just work on the count.

We use Red Hat Insights a little bit. I am more of an Ansible guy, and we use Red Hat Insights for our licensing and a few other things. We have not been using Red Hat Insights as much as we wanted to. I know that on the Linux side, they are using it a lot for license count, monitoring, and other things.

I feel we are underutilizing Red Hat Insights. Our account executive has shown how it works and where it is, but we have not committed to it yet. That is coming soon. As we gain more Red Hat products and standardize more, we will have to rely on a single pane like that, so we will be using it more. I know that Red Hat Insights provides vulnerability alerts and targeted guidance, but we are not utilizing it right now.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say to go for whatever they find to be the best. My standard for an enterprise solution is Red Hat Enterprise Linux. It works very well, but they have to make sure that it fits their use case. Fortunately, Red Hat Enterprise Linux fits most use cases. They might end up there, but if there are licensing or cost restrictions, there are other free options, such as CentOS. The ecosystem of Red Hat Enterprise Linux is healthy, so I would recommend it, but if they want to use something else, they need to come up with all the standards around that.

I would rate Red Hat Enterprise Linux a ten out of ten. It is my preferred enterprise operating system. Everywhere I go, they are using it. It has been great. There are no complaints.