Red Hat Enterprise Linux (RHEL) Reviews

All our infrastructure uses Red Hat Enterprise Linux. Every service we run is all Red Hat Enterprise Linux. Even containerization is on it.

It has improved our organization. It has standardized processes. Everyone uses it. 

The upgrades are straightforward which helps when you want to move a major version of an upgrade. It's done in a standard way.

Everything we do is all Red Hat Enterprise Linux. Red Hat Enterprise Linux's security has been good because I have never seen any application going down due to security reasons. 

Red Hat Enterprise Linux enables us to achieve security standard certification. For example, we have a very tightly SCC-regulated company so there are many rules that we are to follow and we are able to achieve this using Red Hat Enterprise Linux.

I have been using it for six years. 

We are all on-prem, but we also have some footprints in AWS but those images are also on Red Hat Enterprise Linux.

Red Hat Enterprise Linux has supported our hybrid cloud strategy. We have a few things running on AWS. We have a few things on OpenShift. We are able to get all the basic images. It is easy to start and deploy anywhere.

One thing I like is the updates because when we patch it and upgrade it, we save a lot of time doing those upgrades and migrations.

Moreover, upgrades or migration to Red Hat Enterprise Linux have been straightforward in some ways. For example, we are currently migrating to Red Hat Enterprise Linux 8 and we have all our servers running on RHEL 7. We have scripts that are very easy to migrate.

For our implementation strategy, we go environment by environment. We start with our development environment. Once we are done with it, we test it. We have some automation test suites, test them, and we go to the upper environment.  

We worked directly with Red Hat for the deployment. We are already working on Red Hat Enterprise Linux 8 migration. Every year, whenever there is a major version release, we migrate to the major version.  

We see a return on investment in terms of saving time. One thing I like is the updates because when we patch it and upgrade it, we save a lot of time doing those upgrades and migrations.

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

My use cases are mainly limited to databases. I'm also involved in other ETL tools; I worked on migrations from older vendors, like Windows, and transitioning to RedHat Linux.

The most valuable features are security, performance tuning, storage management, and OS-level automation. If you wanted to automate while adapting with different vendor scripts or your own development because it's Linux, it's not like an operating system itself. It is always going to perform how you expect it to. IAQt's not like other operating systems. It is based on Linux. 

These are the main features. Storage management is another valuable feature that is very critical in an operating system. It works along hardware and software.

The most valuable features are security, performance tuning, storage management, and OS-level automation. If you wanted to automate while adapting with different vendor scripts or your own development because it's Linux, it's not like an operating system itself. It is always going to perform how you expect it to. IAQt's not like other operating systems. It is based on Linux.

Compared to other OS', Red Hat Enterprise Linux is the best from my 20-plus years of experience. It is well-suited for production environments. In 2003 and 2006 I worked with one of the vendors in another country. We were able to run a database instance on Red Hat Enterprise Linux for two years without restarting it. The database was located in a remote location, and the team could not be on-site to provide support. We installed it ourselves and it worked for two years. We restarted the database instance. We didn't need to touch it internally. It works like a charm.

If it works, it works. You don't need to attach anything at all. You just monitor them remotely. Nobody was there on-site. That's the beauty of it. Red Hat Enterprise Linux is great. I love it.

The GUI has room for improvement. It needs to be managed by many administrators. It has basic command lines. They could improve it with better automation. We'd like to be able to create a script, and then have the ability to deploy it where we don't need to write everything manually. That part can be useful for automating. 

We'd like it so that a coder wouldn't need to go through it, read it, go to GUI, and then generate a script. If they want to modify it, they could modify it. If Red Hat Enterprise Linux is going to build something, the REST API can be helpful instead of writing their own, starting from scratch. That would make it easier.

For future releases, there could be more integration. Regarding security, we used a different tool for scanning, but having a tool within Red Hat could enhance it. 

Support is essential for open-source software. If they improve aspects like prevention against hacking, it would be beneficial. 

Before, with a surge in hacking incidents, companies lost data, and once lost, it remains lost forever. You never know when it might be used. Improving security, especially in terms of prevention, is crucial. I would like to see ongoing improvement in this aspect.

I've worked with different companies. In my over 20 years of experience, in the last five or six companies I've worked for, all of them have been using Red Hat. They use it mostly for databases. 

I'm in the database sector, primarily working as a senior technical architect. End-to-end, we always find that Red Hat is best suited for Linux, especially for Oracle and other NoSQL databases. It's reliable, first and foremost, and it offers stability and performance. Performance tuning is crucial, and once it's set up, you can rely on it. 

With the cloud, it's moving into containerization, and most of them support the cloud. 

The customer service and support are really good. 

Positive

I have worked with many different operating systems in the past, including Windows, Linux, and RedHat Linux.

We switched to Red Hat Enterprise Linux because it is a reliable and well-supported enterprise operating system. It is easy to manage, use, and upgrade.

We have seen a return on investment. 

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

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

We use Red Hat Enterprise Linux to run our GS and PSP applications.

Red Hat Enterprise Linux helps us avoid cloud vendor lock-in.

Red Hat Enterprise Linux helped us save on costs. 

The support and the stability are Red Hat Enterprise Linux's most valuable areas.

Upgrading between versions needs to be easier. For example, if we have Red Hat Seven running now and a Java exploit is found on Red Hat Seven, we need to be able to upgrade to Red Hat Nine online without any downtime in the environment. This is because it is not possible to reinstall the environment from Red Hat Seven to Red Hat Nine in production without causing downtime to the applications. Red Hat needs to have tools that ensure that we can upgrade from Red Hat Seven to Nine online without any issues.

I have been using Red Hat Enterprise Linux for almost seven years.

Red Hat Enterprise Linux is extremely stable.

Red Hat Enterprise Linux is scalable. We have around 1,790 end users.

The technical support is quick to respond.

We previously used Proxmox and switched to Red Hat Enterprise Linux because of the price.

The initial setup is straightforward because it is well-documented. The deployment time depends on the application. A small application can take around 20 minutes.

The implementation was completed in-house.

The cost is based on each organization's budget and infrastructure.

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

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

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

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

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

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

It is for binding servers. It is for web servers, such as Apache and NGINX, and KVM virtualization.

We have servers running all time. We have not had any issues with Red Hat Enterprise Linux. We have had issues with Microsoft products over time. Because of the updates, we had downtime, but that is not the case with Red Hat Enterprise Linux.

It has been very productive for our organization. We have an online client buying or purchasing products from our website, which is available 24 hours.

Red Hat Enterprise Linux is good when it comes to building with confidence and ensuring availability across the infrastructure. I would rate it a ten out of ten in terms of stability and reliability. In the case of our web server, I have had availability issues with Microsoft, whereas, with Red Hat Enterprise Linux, we have not had many such issues. There has been only 1% downtime, whereas, with Microsoft, we have had a lot more downtime.

We have support. If we have any issues with the distro, we can call their support team. We have reliable packages from Red Hat.

Network management can be easier. It is getting more complex. They can also give more customization for the CLI.

I have been working with Red Hat Enterprise Linux for six years.

It is very stable. We have three websites running on Red Hat Enterprise Linux.

It works fine. We have had servers running for ten years. We have been just updating them, and we have not had any issues or downtime.

It is scalable. We can upgrade it, and the upgrades do not impact the product.

We have a team of five people who are using this solution.

We have premium support. It is excellent. We have not interacted a lot with their support. We have almost five engineers working in the team, so we did not have to contact them a lot. We did have any major issues with the hardware or software. 

Neutral

I also use CentOS for educational purposes. Support and regular updates are advantages of Red Hat Enterprise Linux over others. 

For directory servers, we always use Microsoft because it is easy to manage and easy to control. Implementing and managing domain controllers on Microsoft is easy, and we can apply policies by groups (GPO).

Its deployment is very easy. It does not take long. Its maintenance is also easy. We can expand the storage for the operating system or the web server.

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

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

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

I provide consultation to clients for their mission-critical applications. Its primary use case is running containers and microservices on Springboard.

My customers use versions 7.2 or 7.3. I have used versions 8.2 and 8.4. I have tried version 9, but I use version 8.4 specifically because it supports HighPoint RAID for storing the data, whereas the client applications run on the much lower version.

There are benefits in terms of price, security, and stability to reduce the risk of applications going down or something like that. A vast majority of systems are on Red Hat Enterprise Linux than on other distributions, which is another benefit.

Red Hat Enterprise Linux helps to achieve security standards certification. They use it in the PCI DSS segment, so it enables the applications to be compliant with all these security aspects.

Red Hat Enterprise Linux is very stable. It has been in the market for many years, and it is used by large organizations.

Their documentation and knowledge base are valuable. As an individual developer, whenever I have problems, it is easy to find the information. Their knowledge base is seamlessly integrated with the software. Whenever I have a question, it directly takes me to the knowledge base. It is well documented.

It supports scripting very well. Everything is scripted. A snapshot is taken in the VM, and the script is applied. It lends itself to better security and governance processes.

Its installation on a RAID or cluster system is something difficult. There are specific teams working on that. The GRUB configuration is also a little different from the other Linux distributions. 

In terms of additional features, as technology keeps evolving, the product will also have to evolve. For example, Microsoft Windows has come a long way. In Windows 11, there are so many features that are fundamentally the same as the oldest version, but there are other aspects or processes that have improved. macOS has also evolved over time. Similarly, in the Red Hat Enterprise Linux that I used in 2003 and the one that I am using now, some things are the same and some things have changed. Red Hat can continue to engage clients, understand the use cases, and update them.

I have been using Red Hat Enterprise Linux since 2002 or 2003. Red Hat has a vast variety of products. I have only been using Red Hat's operating system. I have not used Red Hat's other products.

It is very stable.

It is scalable, but I do not have experience in building hundreds of systems on a VM.

I have not used their technical support at all. I only use their documentation portal for self-support. Our production support team interacts with Red Hat's support team.

As a developer, I use both SUSE as well as Red Hat Enterprise Linux. My personal preference is Gentoo, but no one runs Gentoo on a production system. Gentoo is better in terms of customization. You can choose what you want.

I am not directly involved in its deployment, but I am planning to build an application. At that time, I will be deploying it myself. In the organization where I work as a consultant, there is a segregation of roles. There is a production support team, there is a development team, and there is a DevOps team. I am a part of the development team.

Its initial setup is straightforward. It is not complex. It also depends on the architecture, high availability, etc.

In terms of deployment, earlier, it was on-prem, but now, it is on the cloud. My client runs about 150 VMs on the cloud in the production, staging, and QA environments. Most of the things have been consolidated into VMs. The migration is complete. It was not that complex.

I have not measured that, but it should pay back for itself easily. The ROI should be reasonable. The cost over a period of time should be minuscule. As compared to other OSs, it is better to go with a big, known, and trusted vendor.

As a developer, I pay around 10,000 Yen, which is around $100 per annum for support. SUSE and Red Hat are typically the same without standard support. The pricing is not a big deal. Enterprise customers will pay for the support. Enterprises have the money for one or two products like this that are reliable and supported.

As a consultant, I advise customers to go for support. You mitigate risks by having support. For your personal usage, you can manage without support, but when it comes to the enterprise level, you need to delegate things to people, and it should be through the proper channel. You need a proper point of contact.

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

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

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

The users utilize Red Hat Enterprise Linux for building, installing, and automating platforms. Additionally, we employ it as an installer for OpenShift clusters. Furthermore, there is a product called Red Hat High Availability Clustering and also JBoss. Occasionally, we also use it to build an Oracle RAC database.  

Red Hat Enterprise Linux simplifies risk reduction and compliance maintenance by utilizing bash scripts or Ansible to automate and streamline our tasks. Red Hat also offers a tool called Convert2RHEL, which simplifies the process of maintaining our products from Oracle, CentOS, and other vendors to Red Hat. This feature is truly remarkable.

The portability of applications and containers built on Red Hat Enterprise Linux is perfect for keeping our organization agile, especially when considering rootless containers or utilizing BotMan containers for enhanced security and performance. 

The Red Hat ecosystem enables the seamless integration of our products such as Ansible, Red Hat Virtualization, Red Hat Satellite, and OpenShift platform to fulfill tasks, thereby enhancing the efficiency of our organization.

Red Hat Enterprise Linux helps us reduce the time we spend on tedious tasks, and the large Red Hat community provides an easy way for us to maintain or fix errors and bugs. We were able to realize the benefits quickly.

Red Hat Enterprise Linux enables us to achieve security standard certification. I am a certified Red Hat System Administrator and Red Hat Engineer. The content of the certificate includes topics such as C Linux. This helps to make our organization more secure and stable and has an impact on our personnel sourcing.

Red Hat Enterprise Linux assists us in building with confidence and ensures availability across physical, virtual, and cloud infrastructure. While there is a higher level of risk associated with using a public cloud for any product, private or virtualized environments offer greater security.

Red Hat Insights helps us prevent emergencies caused by security issues, noncompliant settings, and unpatched systems by enabling us to be more proactive in detecting and avoiding errors before they occur.

Red Hat Insights provides us with vulnerability alerts and targeted guidance, especially when we register our host directly with Red Hat. It works perfectly because it utilizes machine learning, allowing us to monitor our logs and prevent unnecessary downtime.

Errata is the most valuable feature, which is supported by Red Hat. Errata is a list of corrected errors appended to a document in Red Hat, used for provisioning or batching our hosts. Moreover, its stability and security are noteworthy.

Ever since Red Hat acquired CentOS, the connection between the new CentOS Upstream and Red Hat Enterprise Linux has become unstable and requires improvement.

Red Hat Enterprise Linux's ability to run containerized applications is not optimized and has room for improvement.

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

Red Hat Enterprise Linux is extremely stable.

Red Hat Enterprise Linux can scale horizontally because it is in a virtualized environment. Vertical scaling depends on the deployment of the solution.

We have plans to increase our utilization of the solution.

The Red Hat technical support is excellent; critical issues are resolved promptly.

Positive

We also utilize other Linux operating systems depending on the use case. SUSE Linux Enterprise is more optimized for SAP products. When working with an Oracle database, it is preferable to use Oracle Linux.

The initial deployment was straightforward. The deployment time depends on two factors: the first factor is the infrastructure specs, and the second factor is what we are deploying with the operating system. For a minimal server, deployment takes five minutes. For a server with a graphical user interface, it can take up to 20 minutes.

The implementations are all completed in-house.

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

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

Each processor architecture has a distinct version of the software.

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

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

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

We're using the product to test operating system stability and verify that it runs on the hardware that Trenton Systems produces. If it passes testing, it becomes a validated operating system that we can sell for the server. We plan to offer Red Hat in the coming months to anyone purchasing systems from our company.

The solution’s security feature is the most valuable feature for my company. We offer OS to military or government agencies. For these sectors, security becomes one of the highest priorities, especially the ability to wipe everything out if anything becomes compromised. Red Hat does a great job at that.

The product should be made more accessible to someone who isn't experienced with Linux.

I have been using the solution for four to five months.

The solution is very stable. Compared to many other OSs we test for our company, Red Hat Enterprise Linux has not crashed out on me or given me any problems. Anytime something goes wrong, after some research, I find that it's going wrong because I'm doing it wrong, not because the OS is fighting me in any way.

I haven't used support where I'm emailing or speaking to someone directly, but I've used a lot of the online support just by looking at different user guides, health guides, and things like that. Everything is really well documented. 

Sometimes there are posts about similar issues but with different remediation based on different circumstances. You might have the answer open in a tab, but you've got nine tabs open to find the right answer.

Positive

I have used Ubuntu, CentOS, openSUSE, and Mint. Red Hat Enterprise Linux definitely has an edge in security and the ability to control what the user at the end stage is doing. However, it is difficult to learn.

The licensing makes perfect sense for the number of features you get with the operating system.

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

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

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

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

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

It's pretty much everything that we have. We don't have a lot of Windows in our environment.

I've been using it a lot for several years. In the past, I ran a small web hosting company, and we used it for web servers, mail servers, FTP servers, and other things like that. After that, I was in casinos, and those were mostly Windows, but here, it's a lot of Linux, and it's all Red Hat. In my team, we just build it and make sure it keeps running, and the application teams do what they do.

We use Red Hat Enterprise Linux on-premises. We support the in-house server-based things, and we have another team that supports all the cloud-based things, so I don't have a lot of visibility into the cloud.

In terms of the version, we're trying to phase out version 7. We just brought in version 8. Our Satellite is a little bit behind. By the time that gets caught up, our version 8 should be a little bit more solid, and then they can start testing version 9.

I haven't been on this team for a very long time. I've only been on this team for a couple of years, and it was already in place. In the past, we used it to get the stability and the support that we needed because, for a web hosting company, it was either IIS or Apache, and that was back in the NT days, so obviously, we went with Apache. I find it a better server operating system, so that's what we use.

I don't use it in a hybrid cloud environment, but my organization does. I like its built-in security features when it comes to simplifying risk reduction and maintaining compliance. All the firewall features and iptables have been fine for me. SELinux has been great for me. With the hosting that we used to do, SELinux was great because we had to share files with customers. It made it easy to make sure that files stayed secure and only changed by whoever needed to touch them.

I just use it. I'm strictly into command lines, and they just do what I need them to do, and I know how to use them. Everything is just stable and works well. 

It works fine for me, and it does what I need already. It does everything I needed to do, and it has for so many years. The only change that stumped me was the networking in version 9. I preferred the ifconfig way of doing things, but the system changes of it have grown on me. I preferred the ifconfig way because of familiarity. I knew how to manipulate things. I knew how to get things running and stay running and script ways to keep them running and notify me if the thing went wrong. My only gripe has been the networking change and the inability to use ifconfig anymore. I talked to some people, and they did point out that it's good if you're moving from one environment to another environment—like a laptop, but for servers, I don't need that. I just put my config file where I can find it and make the changes that I need.

I've been in this organization for a couple of years, but I've been using Red Hat since version 3. It has been a long time.

The stability has been pretty great. There are some things that we're still working on, but once we solve them, I know they'll remain solved.

Scalability has been great too because when we need more, we just add more, and we're good.

They've been great. I've worked with them a lot lately. They've been a ten out of ten. They're always there for us, and they answer us quickly.

Positive

I've personally used everything from Slackware to OpenBSD, FreeBSD, Red Hat, Fedora, and Ubuntu. I've used everything.

I like the way that everything is predictable with Red Hat Enterprise Linux. You know what you're getting. You know where everything is, and you know that you can find support if you need it. When we're upgrading or if we're adding something, I always know where I could find what I need to find.

I would think that we have seen an ROI. Our licensing has been very fair, but I don't have a lot of visibility into that.

I like my developer account. The free sixteen licenses that they give with the developer account are great because that gives me the ability to keep using it at home instead of trying CentOS or something like that. Once CentOS went away or changed, I had the ability to just make a developer account and spin up my entire lab in Red Hat, which made it better anyway because that's what we use at work, and now I have a one-to-one instead of a clone-to-one.

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

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

Red Hat Enterprise Linux is connected to our internal private cloud that is air-gapped.

We use Red Hat Enterprise Linux as the operating system on our network management and data management servers. It is our server operating system of choice for any type of hardware that needs to be reliable and stable.

Red Hat Enterprise Linux solved our need for automation and running containers. It is the most stable open source operating system available. When compared to other OSes, it is reliable and works well. This is important for my line of work, where I need to be able to reliably transfer files across thousands of miles. I need to do this quickly, and I have found that other OS solutions, such as Windows Server and Ubuntu Linux Server, are not as reliable or as quick. I have found myself constantly having to troubleshoot problems with these other OSes, and there is often not a lot of documentation available to help me.

The Red Hat Enterprise Linux knowledge base is awesome. Everything is documented, so I could easily find the information I needed to troubleshoot my misconfiguration issue. The knowledge base even provides suggestions for likely causes, which was helpful because most of the time, when something isn't working right on a Red Hat Enterprise Linux system, it's a configuration issue.

Security is one of the benefits of Red Hat Enterprise Linux. It is secure from the start, and it does not take long to configure it to meet government security standards. It also performs well during the staging process, and it does not break or cause services to be lost. In contrast, other operating systems often lock accounts, break, and cause services to be lost.

Simplifying risk reduction and maintaining compliance is straightforward and uncomplicated. There is plenty of documentation to help us, so if we get lost, we can refer to it to find our way.

The portability of applications and containers built on Red Hat Enterprise Linux makes it easier for our company to stay agile. We have found that our applications and programs run just fine on Red Hat Enterprise Linux, which provides a lot of supportability.

Red Hat Enterprise Linux's most valuable feature is that it comes with all the tools we need to set up and maintain an enterprise-grade system. Even if we install the minimal version of Red Hat Enterprise Linux, we will still have everything we need to get up and running quickly and easily. And if we ever need to restore our system from a backup, Red Hat Enterprise Linux makes it easy to do so, whether we are restoring from a scratch build or a backup that is a few weeks old.

A feature that I would like to see in the image builder is the ability to open the image in live mode and access a command line interface. This would allow me to immediately apply the necessary security settings required by the STIG. By doing so, I can deploy the image with the confidence that vulnerabilities present in the live network cloud service are closed before deployment, rather than applying the settings afterward as suggested in the example by Red Hat.

Ideally, I would prefer to deploy an operating system that already has all the necessary configurations in place. This would involve accessing a command line interface, adjusting configuration files as needed, setting up banners, and establishing user accounts. After making these changes, I would create an image and deploy it. I've noticed that the current image builder is primarily designed for commercial use, but as a DoD user, I have different requirements. Therefore, having an emulator or virtual terminal that allows me to interact with the kernel and make live changes, which can then be saved to create a customized ISO, would be an excellent feature to have. It would be great if Red Hat Enterprise Linux had a similar capability. Interestingly, Ubuntu Linux does offer this functionality with its "Custom Ubuntu Basic ISO Creator" (CUBIC).

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

Red Hat Enterprise Linux is stable.

Red Hat Enterprise Linux is a scalable operating system. Red Hat Enterprise Linux offers a wide range of options and features, and we are only just beginning to explore its full potential.

The initial setup is straightforward. I installed Red Hat Enterprise Linux using the stick method. I had to create nine different partitions, all of which were encrypted. This is where things got a little complicated. We need to decide whether to create a LUKS partition or partition and build our image on top of a LUKS partition. Initially, I was individually encrypting each partition using the "encrypt" option. However, this is not ideal because we cannot grow or shrink an LVM partition that is on an encrypted partition. Once the partition is created, it is set in stone. So, I needed to figure out how to encrypt just the partition and then create an LVM partition on top of the encrypted partition, such as SDA3. This was a bit of a challenge, and there is not a lot of documentation on how to do this. The documentation that is available is a bit confusing, and I got lost a few times. Once I figured it out, it was not too bad. The entire deployment process takes about 20 minutes.

We have seen a return on investment in all areas with Red Hat Enterprise Linux, including productivity. We use it in our daily operations in almost all of our systems. In one form or another, Red Hat Enterprise Linux is running on our systems. If we are not running Red Hat Enterprise Linux, our systems are unstable.

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

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

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

Red Hat Enterprise Linux specifically was a hard requirement for certain software that we wanted to utilize. In fact, purchasing Red Hat’s enterprise version was necessary to run AP. That was the primary objective.

Apart from that, the robust networking capabilities offered by Red Hat Enterprise Linux were highly valuable. They have numerous partnerships and dedicated efforts in low-latency technologies, which are particularly beneficial for trading firms. They possess extensive expertise in external tuning and similar aspects.

Overall, the reliability stands out the most for me. While the package selection might be somewhat restricted, it is highly integrated and cohesive.

I'm really excited about some of the developments happening in the workstations and the Fedora Silverblue space. There are advancements like rpm-ostree and the OCI container format, which enable deploying RHEL in new ways.

As we have numerous developer workstations, being able to deploy them in an image-based format is highly desirable. This would allow us to use the "toolbox" concept, where developers can choose any desired operating system within the toolbox. Some of our developers also work with Ubuntu and Oracle Linux. Having a consistent developer platform with full pseudo permissions and zero permissions within that container or toolbox would be beneficial.

Additionally, having an image that includes all the necessary software and provisioning it so that subsequent updates provide the updated image, would significantly enhance the developer experience. It would be great if teams could make modifications and changes to the image, like rebasing. I think it would be an awesome feature.

Let me provide an example of why this would be valuable for Red Hat Enterprise Linux Workstation. We recently switched from one security software application to another similar application on our workstations. We had to manually remove the unwanted software and install the new one. It was manageable for servers or edge devices, but for remote devices that are not always on the network or VPN, it became a cumbersome task to reach out to each device and remove and install the software. If we could update an image with the old software removed and the new software installed, and then allow users to update their image, it would simplify the process for everyone. Currently, it's possible with Red Hat Enterprise Linux for Edge, but it would be fantastic if this capability could be extended to Red Hat Enterprise Linux Workstation as well. That's what would be really cool.

The company has been using Red Hat Enterprise Linux for a significant period of time. As for myself, it's been around five years or so. I have also contributed to GNOME. About ten years ago, I was one of 12 individuals who wrote documentation for GNOME 3.

I don't think we are leveraging Red Hat Enterprise Linux on the cloud. Since we are primarily involved in trading, our infrastructure is predominantly on-premises, accounting for about 80%. We have our own data centers. While we do have some cloud workloads and our cloud presence is growing, it isn't a major focus in my role. I serve as the lead engineer for 700 developer workstations that run Linux. For parts that use Red Hat Enterprise Linux on the cloud, we are split between different cloud providers, AWS, Azure, and Google Cloud.

For the most part, we are using Red Hat Enterprise Linux 8, which we support alongside Ceph and a bit of AAP. Apart from that, there is still a significant amount of CentOS 7 in use as people are gradually transitioning away from it.

The stability is good. I would rate it a nine out of ten.

The scalability is impressive. I would rate it a nine out of ten.

The customer service and support were pretty good. We encountered an issue, and we involved some people for assistance. In retrospect, we should have engaged higher-level support sooner for that specific issue. Support can be challenging when you're dealing with Linux problems, especially in our environment where we have a lot of skilled engineers; it feels like we're already operating beyond the normal troubleshooting space. So having access to escalated help when we need it is valuable. The support fixed our problem.

Positive

The initial setup was complex because we were using a newer version of Red Hat Enterprise Linux for the server team's workloads. Normally, we go with Red Hat Enterprise Linux for hardware, but this time we got a better deal from a different vendor whose IPMI Redfish interface wasn't as advanced as Red Hat Enterprise Linux's. This caused some issues specifically related to deploying the newer version. However, once we managed to overcome most of those challenges, the use of Ansible for OS deployment became more straightforward.

For the OS component, we worked directly with Red Hat. However, we utilized a company called Bits, based in Elk Grove, Illinois, to handle the hardware provisioning and setup.

We've seen an ROI. For instance, we were able to run a storage workload on one cluster that had an immense capacity. I calculated it to be the equivalent of either 16,000 iPads or 64,000 iPads. It was a significant amount. This capability is beneficial for us as we deal with a lot of trading data. We can perform analytics and machine learning workloads on it, which aids in compliance and enables traders to make more informed trades. It's a win-win situation.

The compliance aspect ensures that we stay out of trouble, and the machine learning capabilities help traders make better trades, which ultimately contributes to our success. I'm glad that they make money. It's wonderful.

Red Hat is making efforts to simplify the SKU system, which is a positive development. It's beneficial to have the flexibility to allocate a certain budget to explore different licenses within the Red Hat ecosystem. We can try out products and decide if they meet our needs. If they don't, we can decommission the corresponding SKU. I have noticed that we have some Red Hat entitlements that we are not currently utilizing, so having granularity in the SKU structure would be an advantage.

For our specific use cases, certain products like SAP, AAP, and OpenShift require Red Hat Enterprise Linux. That played a significant role in our decision.

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

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

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