Red Hat Lightspeed Reviews

Our primary use case is that we use it for transaction servers.

We have it on-premises, mostly virtualized.

RHEL helps speed up our deployments. We don't use things like Kickstart and Satellite for deployments, because we usually just clone systems. But the ability to script customizations during deployments is particularly useful for us. It enables us to tailor each machine the way it needs to be.

We use RHEL to run multiple versions of the same application or database on a specific operating system and its features for managing them, things like Satellite and Insights, make management of multiple versions of an application server much simpler.

We use Red Hat Insights to monitor the systems and it is a godsend. It's like having an extra person on staff. Insights is a constantly updated database of CVEs and configuration best practices. It checks everything in the environment to make sure that it is patched, up-to-date, configured properly, and using industry best practices. When you look at the Insights control panel, you know either that everything is good or, if you have an issue, you know exactly where to look and how to fix it. Nine times out of ten, it even gives you an automation script to fix it automatically.

Other than Satellite, we also use Red Hat Ansible, but not Ansible Tower. They integrate very well with RHEL. They're tooled for integrating with it and they do that well. That integrated approach makes my life much easier. The primary function we use Satellite for is patching. Having something that's built to manage application environments and make sure that everything is patched correctly to use Ansible, plugs into everything else, including Satellite. You can use it to manage RHEL, Satellite, and other things, such as Windows and networking equipment. The tightest integration is with Red Hat.

RHEL enables us to deploy applications and emerging workloads across bare-metal and virtualized environments and I find those workloads to be extremely reliable. The reliability is so good that I rarely find myself calling Red Hat support any longer. Support is the first benefit of using RHEL, but the second thing is that the platform is so stable that the need to use support is negligible.

There is potential for improvement when it comes to ease of use. It has become easier to use over the years but could be better still. Linux, in general, has never been a simple solution. It's usually a more complex solution than something like Windows. If there is a downside, it's that it is more complex than some of the other solutions.

I've been using Red Hat Enterprise Linux (RHEL) for about 10 years.

One of its most valuable features is its stability and reliability.

We have applications that we've scaled quite significantly, with over a dozen servers running the same application, load-balanced, and RHEL scales quite well.

We have an installation of about 200 servers and about another 800 servers in our SaaS environment. We're looking to grow the environment where it makes sense. I like to take the approach of considering the appropriate tool for the job. We are primarily a Windows shop, but often the right tool for the job is Red Hat. That's where we would grow our environment, where it's appropriate and the right tool for the job.

Our engagements with RHEL support are usually good. It's been a while since I've had to contact them, but they're good even when it's a significant issue that takes time. They don't even have any problems moving issues around through time zones and having support work on them around the world.

The initial setup of RHEL is very straightforward. It's all menu-driven and most of the time there are only a few answers that need to be given during the setup procedure to get a system up and fully running in a few minutes.

We can get a system up and running in about 15 or 20 minutes if we need to. We can do a custom build and use the full build process, or sometimes we do virtual cloning and then just run scripts to individualize the machines.

RHEL's single subscription and install repository for all types of systems may be a bit of a stumbling point. It seems that the descriptions of the subscriptions change every year or two and it gets a little complicated. And the naming conventions they use in the subscriptions can be a little complicated.

As for maintenance and administration of RHEL, there are just two people in our organization who handle that, me and another engineer.

The prices are comparable, and good for what is being provided.

RHEL is certainly more difficult to use than Windows, but it requires fewer hardware resources than Windows and, in my experience, it has also been more robust.

The fact that RHEL is an open-source solution isn't a concern, directly. Where it might be a factor would be when we're looking at using a tool for a particular need and we're looking for the best platform for it. That's the biggest factor.

Make sure that you have well-trained engineers who are familiar with RHEL. If you are looking for a solution that runs in a mission-critical environment, you always want a supported solution. If you're looking for Linux, I don't think that there's a better-supported solution than RHEL.

In our particular scenario, our underlying infrastructure is either VMware virtualized or bare metal, although the latter was mostly in the past. Rolling out to a virtualized solution or rolling out to bare metal with RHEL—with the exception of the bits that are unique to those platforms—the operating system installation and the like are going to be very similar.

Overall, RHEL is a very solid solution.

The primary use of Red Hat Insights is to analyze the whole data set of the service to determine what is highly critical.

The most valuable feature of Red Hat Insights is that it is dynamic.

It is determined by the data. 

The use case is to determine how to obtain crucial factor information. 

And then, depending on the technical circumstances, you proceed, for example, to upgrade or alter configurations to implement modifications for security the use case is not the technical view.

It is the capacity for looking at critical factors.

The improvements, in my opinion, have to be done in the infrastructure of the Red Hat Satellite, it is very complex.

I have worked with IT infrastructure for fifteen years. IT operations and IT infrastructure.

I started in this position as an Operating System, and coordinator of the Operating System team for two years. Only doing this

Technical support is good, they are both helpful and quick.

Red Hat Insight is the cloud view of Red Hat Satellite.

It is difficult to rate this product, I am still new to it.

It's a very good product.

I would rate Red Hat Insights a nine out of ten.