Systems Engineer at a financial services firm with 1,001-5,000 employees
Real User
The solution's enterprise-level security provides peace of mind, ensures compliance, and allows us to focus on other tasks
Pros and Cons
  • "One of Red Hat Enterprise Linux’s valuable features is its enterprise-level security. We are guaranteed that it's secure, and that's important for us because we need to comply with security regulations. Security always remains a top priority."
  • "The knowledge base provided by Red Hat exists, but I find it difficult to navigate. The information seems scattered and hard to find."

What is our primary use case?

One of our use cases is for our in-house applications that the development team builds. We also use it for typical tasks like running Jenkins, GitLab, and other development tools to make them accessible for the developers who write code and do software development.

What is most valuable?

One of Red Hat Enterprise Linux’s valuable features is its enterprise-level security. We are guaranteed that it's secure, and that's important for us because we need to comply with security regulations. Security always remains a top priority.

We just run Red Hat Enterprise Linux’s built-in security features day in and day out. We know it's secure, and then we just move on to other tasks. It's like a routine where we don't have to think too much because we know it's already integrated into the whole enterprise. It's the next step, and it gives us more time to focus on other tasks.

What needs improvement?

We are trying to figure out how to enable encryption or just encryption. The last thing we want is to use locks, which are a hassle for encryption. We don't have the personnel to unlock the system every time it gets rebooted. I know there's a way, like on Windows, where they have TPM. I'm not sure how Red Hat Enterprise Linux’s TPM works. That's one of the issues we face—how to utilize TPM effectively.

I think in the future, if the company requires us to encrypt everything, it would be a time-consuming process. I'm not sure how long that would take or if it will happen. I just want to understand how Red Hat Enterprise Linux and TPM work or if there's an existing solution that works similarly where I don't necessarily have to be present every time my system reboots and enter a password. At least for Windows, we know that it works, but I'm not familiar with the equivalent functionality in Red Hat Enterprise Linux.

In future releases, I would prefer a Red Hat Enterprise Linux image that fits on a DVD. The Red Hat Enterprise Linux image keeps getting larger and larger. One of the biggest requirements for my company is that it has to fit on a DVD. Now, with Red Hat Enterprise Linux 9 approaching close to ten gigabytes, it won't fit on a DVD anymore. The last thing we want to resort to is using Blu-ray. I prefer not to use Blu-ray. So we need to keep the image size on a DVD smaller. That's one of the main issues. And we can't use USB sticks either, even though they're a new option. Everything needs to be burned on a DVD. So having a Red Hat Enterprise Linux image that fits on a DVD would be beneficial for any future versions or releases.

For how long have I used the solution?

I have been using this solution for eight years now. Right now, we're migrating. I'm trying to upgrade from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7. And that process is painstaking. It's taking a lot of time. I know we want to get that done before October because I think that's when the security support for Red Hat Enterprise Linux 6 expires. We need to move everything to Red Hat Enterprise Linux 7.

We have a lot of legacy systems, and it's very time-consuming trying to figure out what will work and which version of Red Hat Enterprise Linux will support all our applications. So it's just a lengthy process to go through.

Buyer's Guide
Red Hat Enterprise Linux (RHEL)
May 2024
Learn what your peers think about Red Hat Enterprise Linux (RHEL). Get advice and tips from experienced pros sharing their opinions. Updated: May 2024.
772,679 professionals have used our research since 2012.

What do I think about the stability of the solution?

In terms of stability, there have been some issues, particularly on the workstation side. The workstation tends to freeze up occasionally, requiring a system restart. The server side, on the other hand, works well as intended. Although Red Hat Enterprise Linux is primarily designed for servers, our developers use it as a workstation, and that can sometimes cause issues after a couple of days of continuous use.

They may need to restart their systems when something freezes or stops working. So it's one of those things we encounter.

How are customer service and support?

I don't really use it extensively. I have some knowledge and experience with it, but I don't heavily rely on Red Hat support. Whenever I encounter a problem, I usually turn to Google for solutions.

The knowledge base provided by Red Hat exists, but I find it difficult to navigate. The information seems scattered and hard to find. I tend to prefer searching on Google since I can get immediate answers there compared to the knowledge base, which can be challenging to navigate. It seems like the knowledge base could use some improvement.

Which solution did I use previously and why did I switch?

One of the main advantages is the level of support. Red Hat Enterprise Linux provides nearly ten years of support, including two years of extended support, whereas other operating systems typically have one or two major versions released within five years. It can be challenging to allocate the budget for frequent updates over such a short period. So I think that's the main appeal of Red Hat Enterprise Linux—its ten-year support with an additional two years.

How was the initial setup?

Since I've been working with Red Hat Enterprise Linux for a long time, it feels easy for me. However, for someone completely new to it, especially coming from a Windows background, it might seem more complicated. But for me, it's second nature and not that difficult. So the initial setup depends on the level of familiarity with the system.

For a brand-new system, it might take around ten minutes.

Which other solutions did I evaluate?

I have worked with CentOS, Fedora, and Ubuntu. So I have experience with different flavors of Linux, from the Ubuntu side to Fedora. From a developer's point of view, the main difference, if I compare it to Ubuntu, is that they always get the latest packages, which helps them a lot. 

On the other hand, with Red Hat Enterprise Linux, I understand that it's set up to prioritize security. But sometimes, from a development perspective, it's challenging for them to obtain the latest packages. As an assessment, I have to go out there, fetch the package or compile the new package for the new version, and then bring it into Red Hat Enterprise Linux so that developers can use it. I think that's the issue. It's a balancing act between trying to get the latest package versions and ensuring stability and security. It's a problem that I think everyone struggles with.

What other advice do I have?

Overall, I would rate the solution an eight out of ten because there is always room for improvement when it comes to technology.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Software Engineer at a security firm with 10,001+ employees
Real User
GUI for network adapters, and built-in tools such as Mozilla browser, are key for us
Pros and Cons
  • "The GUI for network adapters and built-in tools provided by RHEL, such as the Mozilla browser, have been valuable. Since they come built-in, it saves the time of having to install them, and you have everything necessary with the installation itself."
  • "Until now, RHEL has been the most stable OS I have ever seen. Nothing seems to break, with frequent updates. I have been running it 24/7 for the past 18 months and it runs flawlessly."
  • "I really think that the upgrade policies between the major versions, like from from RHEL 5 to RHEL 6, should be much easier, similar to what is in place for upgrading from RHEL 6 to RHEL 6.8."

What is most valuable?

The GUI for network adapters and built-in tools provided by RHEL, such as the Mozilla browser, have been valuable. Since they come built-in, it saves the time of having to install them, and you have everything necessary with the installation itself.

There are several tools which Red Hat provides as add-ons such as ReaR (Relax and Recover) which can be used for disaster recovery.

What needs improvement?

Improvements are necessary to stay in the market and face the competition. I really think that the upgrade policies between the major versions, like from from RHEL 5 to RHEL 6, should be much easier, similar to what is in place for upgrading from RHEL 6 to RHEL 6.8.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

Until now, RHEL has been the most stable OS I have ever seen. Nothing seems to break, with frequent updates. I have been running it 24/7 for the past 18 months and it runs flawlessly.

What do I think about the scalability of the solution?

No issues so far. You can always scale the hard disk as much as you want, add NFS, CIFS disks and still the enterprise solution would run seamlessly.

How are customer service and technical support?

I would rate technical support at eight out of ten. Though they have some excellent engineers available, the case mostly goes through level-3 support staff and then it moves forward. This can sometimes be a time consuming process and lethal for a company.

Which solution did I use previously and why did I switch?

No, we did not use a previous solution. We knew about Red Hat from our inception. It was a pretty well-known enterprise platform.

How was the initial setup?

The setup of RHEL is straightforward, there is nothing complex about it. Everything is well documented on their website.

What's my experience with pricing, setup cost, and licensing?

The pricing is a bit on the expensive side, mainly because of the support they provide. However, it is quite affordable if you are an organization. If, as a small company or individual, this is an expensive option, I would recommend CentOS, which is an exact replica of RHEL, minus the customer support.

What other advice do I have?

I have worked on a few Linux platforms, but Red Hat is a different experience. Due to its stability, it makes an excellent choice. It’s so-called invincible security makes sure that your data remains safe. The excellent customer service support agents are ready to get your problem resolved almost within an hour of opening a case (as long as you have the premium license for your servers). Taking all this into consideration, I would say this solution is a nine out of 10.

I have been working on Red-hat for two years and I must say I enjoy working with it. No day is like another, since there will always be something which will enhance your learning curve.

I would say if you are managing high-end servers running complex programs, Red Hat would never do you wrong. It has a lot of built-in tools if you choose the maximalist installation. If you are running a low-end server, you can even go with the minimalist installation which would only cramp a few megabytes of your processor power.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Red Hat Enterprise Linux (RHEL)
May 2024
Learn what your peers think about Red Hat Enterprise Linux (RHEL). Get advice and tips from experienced pros sharing their opinions. Updated: May 2024.
772,679 professionals have used our research since 2012.
IT Systems Engineer & Architect at a government with 1,001-5,000 employees
Real User
Extremely reliable and improves support for container management within our organization
Pros and Cons
  • "The reliability and long support lifespan of RHEL are crucial for us. It lasts for ten years, meaning we don't need frequent changes."
  • "We hope it will improve tasks we have found challenging in the past, like documentation searches."

What is our primary use case?

We primarily use RHEL for data analysis servers supporting our scientific researchers, who access the systems remotely.

What is most valuable?

The reliability and long support lifespan of RHEL are crucial for us. It lasts for ten years, meaning we don't need frequent changes. Updates are quick, simple, and reliable, automatically backing out if issues arise, saving us from patching headaches.

What needs improvement?

I'm eager to see how the AI features in RHEL can enhance our capabilities. We hope it will improve tasks we have found challenging in the past, like documentation searches. We are particularly interested in automation and easily finding information.

For how long have I used the solution?

I have been using RHEL for 15 years.

What do I think about the scalability of the solution?

RHEL is scalable. We have scaled our data analysis clusters with it quite well.

How are customer service and support?

I would rate the customer support as a nine out of ten.

How would you rate customer service and support?

Positive

How was the initial setup?

Deploying RHEL for the first time was simple. It was a long time ago, and we had documentation from previous admins which made it straightforward. We did the deployment on our own.

What was our ROI?

We have seen ROI with RHEL. Our biggest investment is in professional development through Red Hat Summit, online training, and a Red Hat Learning subscription, which we have used for courses.

What's my experience with pricing, setup cost, and licensing?

Our experience with RHEL pricing and setup costs has been good. We will be purchasing an extended license for another year.

Which other solutions did I evaluate?

We have used RHEL since I joined my company about 15 years ago. We have looked at other options like Fedora and Ubuntu for more up-to-date libraries, but we keep coming back to RHEL for its reliability and long-term support.

What other advice do I have?

Using RHEL for containers has simplified our processes. While we, as system managers, aren't heavily involved in development, we provide RHEL containers for our developers. Overall, it has improved support for container management within our organization.

We rely on Linux for our web and file servers to ensure file integrity and service verification. Additionally, we use the host firewall regularly on all our hosts for enhanced security.

We started agile development and containers help us by making it easier for developers to teardown and recreate environments. This allows for more frequent updates, improving our workflow.

Our Red Hat portfolio reduced our cost of ownership by using RHEL Workstation instead of full server licenses where possible, saving money. We use full RHEL only on our enterprise production servers.

I would advise a colleague to check out Red Hat for its long-term support and reliability compared to other open-source Linux-based operating systems.

Overall, I would rate RHEL as a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Data Platform Engineer at a manufacturing company with 10,001+ employees
Real User
Comes with good tech support and security patching feature
Pros and Cons
  • "Red Hat Enterprise Linux is the underlying licensing system that our third-party tool uses. It offers convenience. We can open a case when we want to escalate anything."
  • "I don't like the UI changes that come with different versions."

What is most valuable?

Red Hat Enterprise Linux is the underlying licensing system that our third-party tool uses. It offers convenience. We can open a case when we want to escalate anything. 

The tool's insights included with licensing is good. Security patching is also a good feature for us.

What needs improvement?

I don't like the UI changes that come with different versions. 

How are customer service and support?

The tool's support is good. Sometimes, support comes from India. I try to wait and ensure remote support is from the US so that it fits the timeline. 

How would you rate customer service and support?

Positive

How was the initial setup?

The product's deployment is straightforward. 

What other advice do I have?

We are a big data shop that has around 700-800 nodes.

Red Hat Enterprise Linux Leapp was very helpful. It is very easy to use. 

Our servers run for 500 days, and we reboot them every 600 days. 

I search through Red Hat Enterprise Linux's knowledge base daily. 

We use Red Hat Enterprise Linux 8.6 since the third-party tool is compatible with it. 

We use satellites for the operating system and Ansible to do the configuration. 

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

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Application Developer at a financial services firm with 10,001+ employees
Real User
Top 20
Offers adaptability to modern technologies, training and good support
Pros and Cons
  • "Red Hat Enterprise Linux is certainly more secure than AIX, which is what we had. It's also better than Solaris. It has improved from that perspective. We can handle the vulnerabilities better. It's more secure."
  • "The adoption was slightly slow because the knowledge in the market is slightly less available. It's hard to find resources to actually support the product."

What is our primary use case?

All of our application services, application databases, and web services run on Red Hat Enterprise Linux. Everything is on there.  

How has it helped my organization?

Red Hat Enterprise Linux is certainly more secure than AIX, which is what we had. It's also better than Solaris. It has improved from that perspective. We can handle the vulnerabilities better. It's more secure.

Other than that, some of the products that we are using, we are migrating out of very costly license items. For example, we're using Fusion because we wanted to migrate, and then we started using Vision Manager. We did a POC a few years ago. We started using PAM because we wanted an engine in our workflow management system from that perspective. 

We are still exploring a lot of items, but it's been a decent journey. It has helped to set up modern technologies.

What is most valuable?

We use a lot of Red Hat products. We use Red Hat PAM, Red Hat Session Manager, and the operating system. 

We use the operating system the most because all our servers are on it.

The support is good. Red Hat provides use with a degree of training.

What needs improvement?

The adoption was slightly slow because the knowledge in the market is slightly less available. It's hard to find resources to actually support the product.

Some kind of training that can upskill the resource into this technology could certainly help.

For how long have I used the solution?

I started using Red Hat Enterprise Linux version 6 in 2019. We have our own data center.

Which solution did I use previously and why did I switch?

We used different solutions. We moved from AIX 7.1 to RHEL 6. Then we moved to 7. Now we're going to 8.

We chose Red Hat Enterprise Linux because we wanted to adopt newer technologies and we wanted to secure our systems. Red Hat Enterprise Linux was a good available option. 

How was the initial setup?

It's on-prem right now. The deployment was straightforward. 

I manage the infrastructure team so all of these things are under my purview. 

We did hit some hiccups, but then RHEL's emergency support was available, and we were able to resolve it. 

What about the implementation team?

We have an engineering team that analyzes different products. During the analysis phase, we look for all vulnerabilities.

Once it passes all of those things, it becomes available in our internal protocol. We have different names where it becomes available in our source space to get deployed.

Migrations and upgrades have been straightforward. For example, OpenSSL has different versions that are not supported on RHEL 7, which we have right now. There is a version that comes built-in. 

We faced some issues, but we worked it out with Red Hat. They gave us a patch. 

We're moving to RHEL 8 now. We moved to RHEL 7 last year; we're going to RHEL 8 now. Next year, in 2024, we plan to move to RHEL 8.

What was our ROI?

We saw a return on investment. It is helping the business. 

What's my experience with pricing, setup cost, and licensing?

The pricing is competitive. It's not low, but it is in the market. 

What other advice do I have?

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

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
System Admin for OpenShift at a government with 1,001-5,000 employees
Real User
A stable solution that has an extensive knowledge base
Pros and Cons
  • "The enterprise support of the product is valuable to us."
  • "There's too much information on the support page sometimes."

What is our primary use case?

We use the product as our server's operating system.

What is most valuable?

The enterprise support of the product is valuable to us. When stuff gets difficult, it's nice to have somebody to ask about it.

What needs improvement?

The solution should be updated more with the releases of programming languages. They’re lagging a bit too much. We have a lot of developers complaining about having releases that are too old. For example, if they want Python 3.11, Red Hat Enterprise Linux supports only 3.9. So the product is lagging behind a bit more than our developers would like. 

It would be nice if all the features that are available on the cloud, like Image Builder and Insight, would be available on-prem.

For how long have I used the solution?

I have been using the solution for five years.

What do I think about the stability of the solution?

The product is very, very stable and tested. It is like everybody tested everything for five years, and every problem was fixed.

What do I think about the scalability of the solution?

We have never had a problem with the solution’s scalability. We have around 6000 Red Hat Enterprise Linux servers in versions 7, 8, and 9.

How are customer service and support?

Red Hat Enterprise Linux is a lot better compared to all other products. I rate the support an eight or a nine out of ten. There's too much information on the support page sometimes. If we log in to the support pages and try to find information, it's hard to get what we're searching for.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We had a lot of different Linux distributions. The pros of Red Hat Enterprise Linux are that it's the same platform for everybody, and it works for everybody. If you need something very special, you might get issues in Red Hat Enterprise Linux, but you can work around it. 

The biggest issue with Red Hat Enterprise Linux is mostly the old packages. It is a con if you have something that you know is a bug that hasn't really been released in Red Hat Enterprise Linux but has been released in the other products.

How was the initial setup?

We do a template, and then we just use it. It's quite great.

What about the implementation team?

We take 30 minutes to deploy the solution. It depends on the size of the machine.

What other advice do I have?

I am using versions 7, 8, and 9. By implementing the solution, we wanted a unified server with a baseline platform that everybody uses. We wanted to have just one server that is enterprise ready.

We do not really have compliances in the same way as an American company has. It's nice to have IT security personnel. You get SELinux from the start. However, we get a lot of support cases because of it. The developers face problems with it. So, we get the security, but we also get lots of support cases. Usually, I end up in the middle of that because I work with support.

We run containers on OpenShift. We run only one platform, so portability isn't a concern. We only have Red Hat Enterprise Linux and OpenShift. We don't really need portability since we are government agencies. Nothing else other than on-prem is allowed for us.

The knowledge base offered by Red Hat Enterprise Linux is extensive. It is a bit hard to find information. However, when you find it, it's good. The packages are a bit old. We have a bit of an issue because of that. But other than that, it's a great operating system.

Overall, I rate the product an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Cyber Security Engineer at a financial services firm with 10,001+ employees
Real User
A highly stable solution that is super easy to use
Pros and Cons
  • "The product is super easy to use."
  • "The default settings are confusing."

What is our primary use case?

I use the solution to build web applications.

How has it helped my organization?

The tool provides more support, resources, and documentation than other products.

What is most valuable?

The product is super easy to use.

What needs improvement?

The default settings are confusing. I often change these settings to avoid problems.

For how long have I used the solution?

I have been using the solution for a couple of years.

What do I think about the stability of the solution?

The stability of the product is very good.

What other advice do I have?

I did not have issues finding configurations and changing settings as needed. I haven't had any issues like bugs or downtime while using Red Hat Enterprise Linux. Overall, it was a good experience. Overall, I rate the solution an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Sr. Designer Data at a comms service provider with 11-50 employees
Real User
Playbooks help automate and speed up deployment, including post-deployment configuration
Pros and Cons
  • "The most valuable feature is the Identity Management. You pay almost the same subscription cost for normal RHEL and you get the central Identity Management. You would need to pay much more if you were using other applications or products like Active Directory from Microsoft."
  • "An area for improvement in RHEL has to do with security policies. I know they are doing something about this in RHEL 9, but I haven't worked with that version yet. When it comes to security policies in RHEL 8, it is a bit behind. It would be better if we could just enforce a certain security policy such as CIS Level 1. That was not available, out-of-the-box, in RHEL 8."

What is our primary use case?

It's the operating system for different applications we have that are related to telecommunications such as VoIP, DNS, and many others including identity management.

We are using it based on virtualization, including VMware, Red Hat Virtualization, and we have some OpenShift Virtualization.

How has it helped my organization?

RHEL has improved things a lot when it comes to automation. Creating a virtual machine was not an issue, but when it comes to the post-configuration of the workload, the solution has made life way easier. For instance, we created an automation chain that creates a virtual machine from scratch right through until the post-configuration is done. We managed to group different applications in this one chain.

In terms of speeding deployment, we have playbooks that are supported by Red Hat, where we can automate deployment and configuration. That helps a lot, making things much faster. It has accelerated our deployment of cloud-based workloads because of the availability of the modules that help us to create playbooks for post-configuration. It's not only creating a VM but, after that, we still have to do the post-configuration manually; rather that's all automated now. Where post-configuration used to take one or two days, it now takes a couple of hours.

In addition, so far the applications are consistent, regardless of the infrastructure. That's especially true when you automate it. Even if you have an issue, the consistency of deployment helps a lot.

In addition to Red Hat Virtualization and Red Hat OpenShift, we use Red Hat Satellite. We decided to base our entire stack on Red Hat because most of the vendors we use want us to have our applications on the Red Hat operating system. With our whole stack on Red Hat, it makes communication easier because we aren't ping-ponged between different vendors. In addition, there is a good knowledge base for different Red Hat products. The integrated approach among Red Hat products has helped us in that when it comes to identity management, for instance, because we don't need to wonder if Microsoft will support this or not. It has also helped to automate patching as well.

What is most valuable?

The most valuable feature is the Identity Management. You pay almost the same subscription cost for normal RHEL and you get the central Identity Management. You would need to pay much more if you were using other applications or products like Active Directory from Microsoft.

It also enables you to deploy current applications and emerging workloads across bare-metal and private cloud, which are the only environments we have. The applications are very reliable, across these environments, with RHEL.

In addition, we use the solution for monitoring using the features like PCP and that is helpful indeed.

What needs improvement?

An area for improvement in RHEL has to do with security policies. I know they are doing something about this in RHEL 9, but I haven't worked with that version yet. When it comes to security policies in RHEL 8, it is a bit behind. It would be better if we could just enforce a certain security policy such as CIS Level 1. That was not available, out-of-the-box, in RHEL 8.

For how long have I used the solution?

We have been using Red Hat Enterprise Linux (RHEL) since mid-2010.

What do I think about the stability of the solution?

If it works the first time, usually it will work forever. It's only when you patch that you need to do some regression testing to make sure that it's working.

What do I think about the scalability of the solution?

We haven't had any issues with scalability at the OS level for years.

How are customer service and support?

I'm very satisfied with the technical support for RHEL. They are helpful and knowledgeable. I don't have any complaints.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I used to have Ubuntu, but I didn't like it. The beauty of RHEL is that you can easily find support, unlike Ubuntu. While Ubuntu has free subscriptions, unlike RHEL, you cannot get support for Ubuntu easily.

With Ubuntu, when I had an issue, I would have to go to Stack Overflow and check the internet. With RHEL, I like that I can go to IRC and post my question and they answer me.

How was the initial setup?

We are using Satellite, which is considered to be a subscription manager, in a way. In the beginning, it was complicated. Now, they have created something called Simple Content Access  (SCA). We buy a subscription for audit purposes and for legality to have a legitimate copy. On the other hand, Satellite itself issues subscriptions once you have a new OS system. That has made things way easier.

What about the implementation team?

We used professional services back in 2009 or 2010. But once we found that every vendor was looking for Red Hat Enterprise Linux, we added that skill in our department and now we are doing everything ourselves.

What's my experience with pricing, setup cost, and licensing?

Because it's a very stable solution, if you have the knowledge in-house, go for a regular subscription. Otherwise, buy the Premium Support.

Which other solutions did I evaluate?

We had some AppStream versions for different OSs, such as CentOS, but we decided to go for RHEL because it would make life easier in terms of lifecycle management. If we had RHEL and CentOS, it would make patching more complicated.

What other advice do I have?

The biggest lesson I have learned with RHEL is don't complicate your design. You can always find an easier way to do things. Sometimes you'll think, "Oh, we can do this," and you start thinking about very complicated processes. It's better to think and start simple.

With RHEL, we have patching in place, automation in place, and we already know the support. We are very satisfied. We have done a lot of work on it and now it's easy to deploy VMs immediately. We are not looking to implement any other version of Linux.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Buyer's Guide
Download our free Red Hat Enterprise Linux (RHEL) Report and get advice and tips from experienced pros sharing their opinions.
Updated: May 2024
Buyer's Guide
Download our free Red Hat Enterprise Linux (RHEL) Report and get advice and tips from experienced pros sharing their opinions.