I used Red Hat Enterprise Linux to construct systems according to the application team's requirements. I build and support these systems through the development, testing, pre-production, and production phases, fulfilling both developer and operational roles. To ensure the systems can handle the application's demands and meet our cybersecurity standards, I implement all security measures outlined by our cybersecurity team.

The extensive knowledge base offers a full path from beginner to advanced levels. We can access everything needed to study, pass exams, and apply knowledge immediately. The information is presented clearly, without any abstract concepts.

Red Hat offers built-in security features that simplify risk management. Unlike Oracle Linux, which overlooks critical security features like C Linux, Red Hat actively develops and maintains robust security measures. As a result, Red Hat prioritizes system security, consistently providing updates to fortify its machines against potential threats.

Red Hat helps us maintain compliance by enabling us to create and modify firewall rules as needed, allowing for strong security measures that can be adjusted.

The security reports generated every three months are valuable for provisioning and patching as they identify vulnerabilities requiring remediation. I find all the necessary information to address these vulnerabilities and implement patches through the Red Hat Enterprise portal and community resources.

When I started using Red Hat Enterprise Linux five years ago, I noticed the benefits incrementally over time.

Red Hat's greatest asset is its extensive community, which provides valuable support and advice when issues arise. Due to the robust nature of this community, I have never required direct assistance from Red Hat Enterprise.

Red Hat offers customizable tools, such as Assemble, that enhance flexibility within enterprise products. Assemble is a platform capable of managing multiple systems from a single console.

While Red Hat offers essential starting and security documentation, I would like to see it officially recognize the more detailed and customized documents available in the community and make them accessible on its website.

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

Red Hat Enterprise Linux is the most stable system I have ever worked with.

Red Hat Enterprise Linux is scalable.

I changed jobs five months ago, and my new company uses Oracle Linux instead of Red Hat, so Oracle provides support rather than Red Hat.

I find Red Hat Enterprise Linux more flexible, with a larger community and numerous security advisors.

We found it less complex to build a new system on the newer version of Red Hat Enterprise Linux and migrate data rather than upgrading the existing system from, for example, version seven to eight. A simple upgrade risks data loss.

One person can do the upgrades and migrations.

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

The system requires immediate maintenance due to necessary security patches, unresolved vulnerabilities, and a constant influx of operational tasks from other teams. These daily demands include critical adjustments such as modifying service ports and implementing local firewall rules.

I recommend new users visit the official Red Hat Enterprise Linux website to review the guides, explore the community, and research information related to their Red Hat Enterprise Linux tasks.

We use Red Hat Enterprise Linux to maintain our systems, manage our user logs, and monitor our storage.

The fact that Red Hat Enterprise Linux is stable has led to more enterprises wanting to use it. All the updates are current from a security point of view. So, the fact that we are one-managed or subscription-managed through Red Hat Enterprise Linux keeps us secure.

Red Hat Enterprise Linux's built-in security features simplify risk reduction and help maintain compliance, which gives us peace of mind.

The knowledge base of Red Hat Enterprise Linux depends on the end user. However, the information is always there, and the most reliable information is from the Red Hat system.

We have a dedicated server for provisioning and patching, and I am satisfied with how it works.

Red Hat Enterprise Linux's Image Builder and System Roles improve our productivity by increasing efficiency.

The Web Console is helpful because we use it to monitor and record users if we choose to, as well as check our system to make sure everything is up to date and we are current with the latest patches.

Red Hat Enterprise Linux helps us be more compliant.

Red Hat Enterprise Linux's ease of use in a controlled system, especially when dealing with constant repository updates, is valuable.

From a monitoring standpoint, we have Splunk, which is more versatile in monitoring data files, and Nagios, which can monitor multiple instances via Windows or Linux servers and different boxes. If Red Hat Enterprise Linux can improve its monitoring capabilities, that would be helpful.

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

Red Hat Enterprise Linux is stable.

I have not submitted any support tickets because we can find all the answers we need from the RHEL community for minor issues.

Red Hat has been the industry standard for most companies, but sometimes, organizations will run a Windows server and Active Directory alongside it.

The critical difference between Red Hat and Windows lies in their user interfaces. While both share a similar underlying structure, Windows offers a graphical interface for easy interaction, while Red Hat relies on command-line prompts. This makes Red Hat a more secure environment.

Red Hat Enterprise Linux helps improve efficiency, reducing vulnerability and, ultimately, a higher return on investment by minimizing IT costs and downtime.

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

We have between 100 and 200 end users. Red Hat Enterprise Linux is deployed in a standard, dev, quality, staging, and production environment.

Maintenance is minimal for Red Hat Enterprise Linux. We only deal with updates and patches.

We use Red Hat Enterprise Linux to run Oracle Databases for CC&B and JDM. All the RHEL stuff is on-prem. The CC&B team manages the customer care and billing stuff, but we take care of the operating systems, and the application users manage the applications. We have 200 to 300 users on RHEL.

We are missing random devices for patching and everything, and we don't have the Linux data license for that. If we had that, life would be much easier. Right now, we patch using Yum updates and we manually do configuration changes from our end.

Red Hat Enterprise Linux improves our security. On our end, we only use the console to reboot the server and apply security. We patch it completely if we have any security updates. Every quarter, we run a report using quality and whatever it was pulling. That's what we are patching.

Red Hat Enterprise Linux makes patching and scripting much easier, and it provides all the features I need for patching and VM updates. It's easy to apply Red Hat Enterprise Linux's built-in security features when it comes to simplifying risk reduction or maintaining compliance.

For phone support, we had to buy a license for all our servers, and it was a bit pricey for us.

I have used RHEL for 21 years.

Red Hat Enterprise Linux is highly stable. We've never had any problems or crashes. It's very smooth from our end.

It's easy to scale Red Hat Enterprise Linux. Right now, we're discussing what will happen a year from now, when we plan to increase our usage.

I rate Red Hat customer service eight out of 10. Their knowledge base is fantastic. You can easily find whatever you need. Their support responds immediately, whereas we struggled with support from Oracle.

We were using Oracle Linux, and I don't see much difference except the support. We were not getting good support from Oracle because it took too long whenever we opened a ticket. Oracle was also too expensive, and patching is much easier with Red Hat Enterprise Linux. We were not looking for more features. Oracle Linux has a lot more packages than we need.

Setting up Red Hat Enterprise Linux was straightforward. You need at least two system admins to do so. Migrations and upgrades are also easy. Our main products are CC&B and JDM, with an Oracle database on the back end. We were highly satisfied with Red Hat Enterprise Linux for migrating all of those. We also have other solutions like SQL Server, which is on the Windows operating system.

Performance-wise, this Linux is better because you can ignore some packages if you don't need them.

Oracle Linux is free, but we were having many other issues with it.

I rate Red Hat Enterprise Linux nine out of 10. Red Hat Enterprise Linux is very easy to install and manage.

I use Red Hat Enterprise Linux as an operating system for government contracts.

I like the flexibility Red Hat Enterprise Linux offers in terms of permissions. The patch management is much shorter and easier. Red Hat Enterprise Linux helps us move workloads between different clouds and data centers. It's pretty smooth and transparent.

We use AMIs — machine images — for provisioning. The image builder is nice. It's a vertical Amazon machine image. They have each machine image, so you don't need to install anything. You can just copy the machine image.

There's an operating system called EdgeOS, which is an edge operating system used by edge computing nodes in the cloud. If Red Hat Enterprise Linux had a version incorporating EdgeOS-type functions, that would be great. Otherwise, you have to learn a little bit of EdgeOS to work with those nodes.

We have used Red Hat Enterprise Linux for several years.

I rate Red Hat Enterprise Linux nine out of 10 for stability.

I rate Red Hat Enterprise Linux nine out of 10 for scalability.

I rate Red Hat support nine out of 10.

Red Hat offers better support and stability. There are several others, including Windows, and Red Hat Enterprise Linux is a pretty stable standard operating system.

I rate Red Hat Enterprise Linux nine out of 10 for ease of deployment and migration. Deploying an AMI is straightforward. We hardly had to do anything. It's pretty much automatic and uninterruptible.

I wasn't involved in the licensing, but Red Hat Enterprise Linux's price should be reasonable if the government and others get it.

I rate Red Hat Enterprise Linux 10 out of 10. It's the top of the line.

The main use case is generating golden images. All the deployments of operating systems and virtual machines on the servers are based on the golden image. The developers and providers can run all the applications on top of those.

Whenever we need to remediate any vulnerabilities, patches are available. These patches are not only for current exploits but also for back-porting for bug fixes and security fixes. These patches are available from the most recent versions to the specific version that we are using.

Red Hat Enterprise Linux has enabled us to centralize development. We have a golden image of the operating system. That golden image sets the standard for all the security policies that we are applying to it. For example, the partition scheme and the best practices that we apply to the golden image are the starting point for all the developers to start working with all the applications and also executing appliances or applications from providers.

We are using Red Hat Enterprise Linux with Podman for containerization projects. Red Hat offers what is called UBI or Universal Base Image. That image is already configured to be secure and have good performance. To start working with containers, we just have to pull UBI as a base for our images and start working on those. It has impacted our containerization project because instead of using Docker, we can use Podman. There is a common container image that is used by the majority of the customers, but I forgot the name of that one. Instead of using that, which is like a very minimal image, we are using UBI because it is already secure. It has the majority of the benefits of our Red Hat Enterprise Linux image but in a container image.

There is portability of applications and containers built on Red Hat Enterprise Linux for keeping our organization agile. That is a very good option to have because you do not have to worry about the underlying system. You just have to worry about your application and have the application running on top of your image based on UBI. It is going to be so easy to have the application running either on a machine with Podman or have the same application running just on top of OpenShift. It is so easy to move a container-based application that can be executed on top of Red Hat Enterprise Linux with Podman or on top of OpenShift.

Security, packages, and updates are valuable. There is also the possibility to do unattended installations. This way you can define how you want the installation to behave and be configured whenever you do the deployment.

One of the best features is having a tool called OSCAP, which is a tool that is going to allow us to apply security profiles to the golden image. This way, all the security features or policies can be applied in real time. This way, we can follow all the policies that are defined by our security teams.

There are not a lot of areas to improve because the majority of the time, Red Hat is constantly improving it. The only area would be in regards to being capable of running on other architectures like ARM. They are about to release a new version that is available to be executed on ARM architecture.

We have been using Red Hat Enterprise Linux for about a year.

It is very stable.

It is scalable. We have plans to increase its usage.

It used to be better. It is still good as long as you can get in touch with a level 3 support engineer. If you have a trained engineer who helps you with what you need and who understands how to ask for specific details of what you need, you should be good. But, unfortunately, if you start with a simple detail of what you are experiencing and what kind of help you need, you will receive the same response. For example, you are pointed to a knowledge base article, and that is it. The support engineer is supposed to help you with your issue or request, but unfortunately, that is not happening anymore. It used to, but I understand.

We are looking for a support engineer to go all the way. The only way for you to contact support is via the support case system or page. After that, you interact through the ticket or email. You do not have a chance to have a call. If we have escalated a case, it is usually better if you have a person for a proper understanding and proper advice on what you have to do and how to resolve the issue. It could be that you need a new product, subscription, or service, but you do not know that.

When I got into the company, they were already using Red Hat Enterprise Linux, but back in the day, I used to have HP-UX. That was a very ancient system. It was Unix-based. It was a proprietary solution. HP-UX was a platform licensed based on the old Unix code that was tightly integrated into hardware built only by Hewlett-Packard. You could not run HP-UX in any other place. You could only run it on hardware created by Hewlett-Packard. The intention with that was to run only on the Itanium architecture, whereas Red Hat Enterprise Linux can run on x86 architecture. It is also open-source.

We have it on-premises. It is in different locations. We are following a strategy to publish the images of the operating system. This way, multiple teams can grab the images and have their own procedures to deploy within each separate environment. We have multiple teams working on developments and they need a base image to start working on all the development stuff. Because they are all independent teams, they have access to a single source of image. This way, they can start working on further customizations and whatever they need.

We implement it in-house.

The ROI is in terms of the time that I have to invest in doing customizations, applying security policies, and fixing the supply to the system, wherever I need those.

The reason for going for Red Hat Enterprise Linux is to improve the time to market. It is so easy to just generate a new image. We can configure it with all the security features and all the libraries and packages we need. We can also configure it with the ones requested by developers. We can do all of that. It is so much easier than what we can do with Windows, for example.

It is very straightforward. We do not have to think much about having to get all the subscriptions related to the Red Hat Enterprise Linux fleet that we have because all the subscriptions came in pairs of CPUs or even for an entire bare-metal server. That way you can partition your bare-metal server into multiple virtual machines, and then you are covered. As long as your bare-metal server is covered, you can roll out any number of virtual machines on top of it. It is very easy to get subscriptions for your bare-metal server, and you can utilize whatever you want.

We evaluated operating systems or Linux distributions created by the community or run by the community only. We evaluated them mainly because of costs.

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 they would not have the same team supporting all the operations and all the critical features and patches that they receive with Red Hat Enterprise Linux. They can go with one of the clones, but unfortunately, at the end of the day, the clones are going to deviate from Red Hat Enterprise Linux. With Red Hat Enterprise Linux, you can also create support cases to receive back-ported bug fixes and security fixes, and you get very cool features such as Insights, Satellite, or system roles provided along with Ansible.

We are currently not using Red Hat Insights but that is an awesome tool.

Overall, I would rate Red Hat Enterprise Linux a ten out of ten. It is an enterprise Linux distribution. It was one of the first distributions to focus on the enterprise. There are others, but Red Hat is the main contributor to the Linux ecosystem. Because of that, it is so stable. It has proper support. It also provides the Linux ecosystem with new features and enhancements.

The use case in my very early years was for dedicated servers for doing web applications.

We almost exclusively use Red Hat. The benefits boil down to the support. There is no problem getting support. Whenever we have an issue that we cannot solve, which does not happen often, we have somebody who is there either virtually or physically.

We use Red Hat Enterprise Linux on-prem and on the cloud in a hybrid environment. We probably also have edge devices. I am not completely sure about that one. Having it in a hybrid cloud deployment has been no different than having it on-prem. Running it on-prem is just as good as running it on the cloud for us. It simply works.

I appreciate the dashboards that are available online. There has been a lot of feedback on the CVEs. The most recent one that came was probably related to Zutil. Red Hat made an announcement very quickly saying that if you are using only Red Hat features, you do not have to worry about it. It does not run on their operating system. Unless you are custom compiling, it does not work on their system. I greatly appreciate little things like that because they save us a lot of time. If Red Hat is simply saying that it is not a part of their repo, I do not have to look for it.

We use Red Hat Insights but not company-wide. It is one of those things that simply saves you time. I do not want to have myself or anyone on my team go out and check various things. That is the whole purpose of using Red Hat Satellite. The whole purpose of all different dashboards and these websites is to use what you have. Let it report out what you have and not continue to write scripts just to check things.

Their support is valuable. Whenever I had a problem, I could get on a phone call with somebody. I did not have to go to some random forum or send an email and wait forever. I could call somebody.

It does have a workstation option, but you rarely hear anything about it. I would love to see the workstation replace Windows. That is a stretch goal, but it is possible.

I have been using Red Hat Enterprise Linux since version 4. It has been a while.

It is stable as long as you do not do something stupid.

Red Hat specifically works hard to make it difficult to not be able to scale it into anything. The only thing that I do not see it being capable of, officially at least, are the IoT devices. Technically, it is possible to get it on those devices, but that is not something Red Hat is focusing on right now. From a scalability standpoint, it comes down to what makes a reasonable profit and what is a good return on investment while choosing how to scale and where to scale. Red Hat is doing it right so far.

Prior to a few months ago, the support that we got from a TAM point of view was next to none. Now that I understand the scenario a little bit more, it was not because Red Hat was not doing its job or did not want to do more support. It was because of how the contracts aligned, and more importantly, who in our organization was handling those contracts. We had a recent change in our organization in terms of who is running what and who is handling what. When that change happened, the doors really burst open. Now that we have a different person he is working with, we are getting incredible support from our TAM. He is in communication with us on a very regular basis. While I have been here at Red Hat Summit, we have gone out to have meetings twice. I cannot speak highly enough. I would rate their support a ten out of ten.

My current organization has pretty much always used Red Hat, specifically Red Hat Enterprise Linux. There are all sorts of flavors of Unix in our environment. Almost all of them are there because they are managed network devices.

We wanted to stay close to Red Hat Enterprise Linux simply because of the mentality of the business. We have got some people who have been around for 20 years. Things such as switching from YUM update to APT update are easy. People can usually change from one to another pretty quickly, but some of the other commands that you are used to running in Red Hat Enterprise Linux are slightly different for different versions of Unix. It did not make sense.

I have used a lot of different variants through the years. I could be running Raspberry Pi, or I could be using Ubuntu to do a job but not for the production environment. I do not waste my time anymore. I know what works and where support is.

Our setup is a bit of a hybrid. We are streamlining a lot of things and trying to redesign how we are doing things. In terms of the cloud, we are 100% TerraForm. We are building out infrastructure as a code and TerraForm pipelines. On-prem, we have a Jenkins job that runs some TerraForm, which then runs some Ansible and then some Puppet. There is some cleaning up needed there.

Currently, we use all three major cloud providers: Azure, Google Cloud, and AWS. Each has its purpose.

The initial experience of deploying it at the current company was terrible, but it was not a Red Hat issue. It was an internalized issue that took a little bit of time to work out. After that, it was not a problem.

We implement it on our own.

I have not run into a single person who knows about Red Hat Enterprise Linux and is not being helpful. You can get talking with somebody at Red Hat Summit about what you are doing on Red Hat Enterprise Linux, and they will be like, "I did that a couple of days ago. Did you run into this problem too?" There is a community. I am sure there are communities for other variants, but my return on investment is simply community and support. I cannot speak highly enough of these two.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say, "Good Luck!" We looked at a lot of different options to potentially leave Red Hat simply because of the cost. We tried out CentOS. We tried out Rocky. There were even talks about trying out Ubuntu, but there was the hassle of changing all of our mentality and code to work with different systems. It just did not make sense. CentOS worked almost side by side with Red Hat, but certain things that we have specialized with Red Hat were not working on CentOS for some reason.

We chose not to use CentOS because we had a misunderstanding of what AppStream was in terms of end-of-life for CentOS. Rocky was ruled out pretty quickly simply because of a lack of understanding in terms of:

• Where does Rocky come from?
• How reliable is it?
• Where is the support?
  

Red Hat's support model trumps a lot of those other ideas. I tell people that even if they are working in a home lab environment, get a developer license and get a developer account with Red Hat. Use Red Hat because more and more businesses I work with simply use Red Hat. It is great to have Fedora on your laptop as a workstation. It is great to have CentOS as a workstation. That is because those are still a part of Red Hat. You can transition and use Red Hat for a company. I have not been a fan of Ubuntu and some of the other variants because of how easy it is for people to make changes to operating systems that are not fully backed or tested. In my opinion, you do not want to put production on it.

Red Hat Enterprise Linux has not enabled us to centralize development. We are moving towards centralized development, but there are still so many different teams, so centralized development is not yet there.

We are partially using Red Hat Enterprise Linux for containerization projects. Within the next year, I hope to bring OpenShift in and replace AKS. I do not have a use case for the portability of applications and containers built on Red Hat Enterprise Linux. Based on what I have seen here at Red Hat Summit, I have a lot of ideas spinning around in my head to make it happen, but I do not yet have anything around containerization.

Red Hat Insights provides vulnerability alerts and targeted guidance, but we are currently not using that side of it. It helps in my limited sandbox environment, but of course, my sandbox is built up and torn down like crazy. It is valuable, but we do not have a great use case yet.

I would rate Red Hat Enterprise Linux a ten out of ten. I have been working with Unix systems for a while now. The first Unix system I touched was in 1992. There were so many variants that were striving to become well-known. You would hear all of these weird names. There were all of these weird animals and all of these different logos through the years. Even before 1992, there were a lot. As things progressed, you quickly saw different ones die out. I do not remember when I truly got onboarded with Red Hat. I know I started with version 4. It is one of those companies when you are looking for a name that sticks around and about which you do not have to question if they are going to be around for a while. You do not have to question that with Red Hat. You do not have to question that with Red Hat Enterprise Linux, whereas a lot of other variants do not even exist anymore, or they exist, but they have not been maintained longer than some people have been alive.