We are currently in the midst of a POC phase with a standalone cluster. This cluster consists of both coordinator and worker nodes, with a metadata store for storing various metadata. The entire setup is deployed on Red Hat Enterprise Linux 8, and we have established a connection to the OpenShift UI.

While using it, we encountered far fewer complexities, and the entire process is much smoother and streamlined. For patching purposes, we simply need to communicate with our system administrator. They take care of the patching process, so we don't have to get involved and we can easily connect to the artifact repository and download the necessary artifacts to install in our system.

We have a set of JSON files containing YAML configurations where all the required image details are documented and this setup makes it very straightforward for us.As for the Web Console, if you're talking about the user interface for tasks like creating ports, deploying applications, managing secrets, and other functions, I haven't encountered any significant issues.

The process is generally straightforward and quick, taking just a few minutes. OpenShift offers two types of interfaces: one where you can edit YAML files for more advanced customization, and the other where you can use forms for faster deployment, though with fewer features.

Continuous improvement is essential to enhance user experiences and address evolving needs.

I have been working with it for approximately six months.

Our experience with its customer support is very good. Whenever we encounter any issues, we receive prompt and comprehensive assistance. There's no need to wait or take any additional steps to get the help we require, which is highly appreciated. I would rate it nine out of ten.

In the past, our work primarily involved Hadoop, and we also dealt with Solid Cloud for security and other purposes, but we found that this setup was slow and not open source. On the other hand, the DLP solution we're currently using is not only cost-effective but also significantly faster.

I also used a Linux browser, specifically the KCL browser which required me to go through the process of installing packages and various components, while in the current setup, everything is seamlessly connected. We simply use the OC command with a private key to connect to OpenShift. There are no extra or additional steps required, making the whole process exceptionally fast and efficient. It's quite remarkable and makes the workflow truly hassle-free.

The initial setup was easy.

The deployment process is straightforward. I simply had to deploy the images using OC commands, and the process of connecting to OpenShift was remarkably fast and smooth.

Overall, I would rate it nine out of ten.

We use Red Hat Enterprise Linux to run quite a few pieces of software. It's mostly for jPOS, but we also run some Apache solutions and some security applications.

Red Hat Enterprise Linux has streamlined a lot of the support issues. When we've had problems, Red Hat has been proactive about solving the problem with us. Support is always an issue with open-source platforms. By providing this support, Red Hat makes it much easier to adopt Linux.

I love Red Hat Enterprise Linux's built-in security. You can see who is trying to do what and who isn't allowed. You get an alert for that. We also use a product from Symantec on the Linux system for real-time threat detection, but I think we probably don't need that. Red Hat already has these capabilities, but the security team needs something they can centrally manage. They need to know whether the system is protected and the agent is running.

We use it on VMware, and we have a multi-site deployment, so it's very easy to patch and keep the servers up. We use Ansible automation for patching, which has really helped with the service uptime.

I like the speed of the OS data and the ease of Ansible automation. I don't need to spend much time managing everything. The provisioning and patching using Ansible is seamless. Ansible automation gives you almost a cloud-like capability on-premise. Most of my group doesn't have cloud skills. I learned it on my own and got my Kubernetes certification. I'm familiar with the automation infrastructure, how to build the execution environment and implement the private automation hub. Others still need training.

I've used Red Hat Enterprise Linux Image Builder for testing and development, but I haven't put it into production. We have a VMware template, and we've been doing training on VMware, but we are not there yet. I think they might move from VMware to another product. They are looking at other options, such as OpenShift, but we don't have training for OpenShift yet. They should try to have a salesman come and get OpenShift training for customers. If they make training free for the customers, more would switch to OpenShift from VMware.

I use Linux on Satellite with Ansible infrastructure. It would be great if there were a universal interface to control Red Hat Enterprise Linux's policy from Satellite. It could be a dashboard showing which policies were enabled on what system and allow you to apply them from the dashboard.

I think Red Hat training could be cheaper. A company can move fast technologically with enough training. They will be stagnant without training and remain unable to fully leverage the technology. I have been encouraging the group to get a subscription to the training course for five years, but we haven't been able to take advantage of it because of the cost. They should make it cheaper for clients and offer big discounts at scale.

When people lacked training for the technology we use, we migrated away from it. I worry that if we don't have enough training available to the client, they will eventually migrate away from Red Hat. More affordable training on key technologies like Satellite and Ansible automation will help us retain customers on those products. Downstream it will help them migrate to the latest and greatest Red Hat Enterprise Linux, as well.

I have used Red Hat Enterprise Linux since 2005.

I rate Red Hat support 10 out of 10. I've been very impressed with the knowledge base and the support from Red Hat. When I create a ticket, they respond and resolve the issue quickly or they point us to the correct resources. For example, we had an NFS issue with ISO, so they helped us with the mounting options. We also had an issue with IBM AIX and Red Hat integration. Red Hat referred us to the IBM support stack, and we were able to get IBM to help us out.

Initially, I used Solaris because I liked it the best, but Red Hat Enterprise Linux has improved so much that it has overtaken Solaris. Red Hat Enterprise Linux is easier to use and has better documentation. I also like having the ability to use Satellite and Ansible automation to manage Red Hat Enterprise Linux.

The deployment is straightforward because we use Ansible automation to spin up a new system and install applications directly from the Ansible workflow. We were planning to have Red Hat Enterprise Linux 8 online last year, but Red Hat Enterprise Linux 9 came out, so we decided to wait for a bit, and we're almost ready to upgrade to Red Hat Enterprise Linux 9. The application folks still haven't had enough time and money to migrate everything over, and we need a project manager.

I rate Red Hat Enterprise Linux 10 out of 10. It comes with all of these nice tools like the Satellite automation web console.

We use Red Hate Enterprise Linux in our infrastructure, which consists of VM and Linux. We use it to create clusters.

I would like to see the GNOME system monitor feature, which shows CPU usage and other aspects. It will help to save time.

I have been working with Red Hate Enterprise Linux for eight years.

We have a separate team that handles any issues. We inform them whenever we encounter issues.

I would like to see user training sessions that last about one to two hours on new features and releases.

We have a separate team that creates dashboards for us. I rate the product a seven out of ten.

Our use case for Red Hat Enterprise Linux is for production applications.

We are a Managed Service Provider. Red Hat Enterprise Linux enables us not to be worried about vulnerabilities, security, and patching.

The most valuable features are the subscriptions and upgrades.

We need to have more flexibility on the developed versions. Not everybody is ready to subscribe to enterprise versions. They would like to test the tool without subscriptions.

We chose Red Hat Enterprise Linux because of its security.

We use Red Hat Enterprise Linux with AWS. We started our practice with AWS, and most customers use it instead of GCP or Azure. We use the product in a hybrid environment, mostly when shifting the containers or existing workloads from legacy systems.

Most of the customers use Red Hat Enterprise Linux because it is the only approved OS. The tool's knowledge base is good but is limited to subscriptions.

The upgrade migration is straightforward. For the initial projects, we used to execute CLI scripts. We plan to upgrade the system if everything works well in the lower environment.

I have used the image builder feature. I rate the overall product a nine out of ten.

We use Red Hat Enterprise Linux for VMs and physical servers.

The containerized platform will help us use ROSA.

The tool's most valuable feature is OpenShift. We plan to move all our applications to microservices. The container platform is integrated into one.

I opened a few cases, and the tool's support responded quickly.

Deployment is simple if you have been using the solution for a long time. However, it can be complex if you are new to it.

We use RHEL 7 and RHEL 8 on on-premises. RHEL 8 is on the AWS. There is a security policy like CIS when deploying the solution. You can embed it on the image. I am not sure if there is HIPAA compliance yet.

Migration from RHEL 8 to RHEL 9 is easy. Upgrade depends on the application that is running on each instance. You need to check if it is compatible with the kernel. We need to plan things before migrating to the latest version. We need to stay current to ensure compliance. We plan to move from RHEL 7 to RHEL 9 and use RHEL 8 and RHEL 9.

We use Red Hat insights but do not utilize them. It helps with the remediation. I use Image Builder to build AWS and GCP images. I haven't deployed them.

I rate the product a nine out of ten.

We have over a thousand VMs or physical machines running on Red Hat Enterprise Linux. We have various applications, and we also run the OpenShift Container Platform on-prem, so we have a lot of containers. They are migrating a lot of apps from the mainframe over to Spring Boot type of app. It fits well in the container.

Red Hat Enterprise Linux gave us stability. There is somebody to call when we have issues.

Red Hat Enterprise Linux has affected our system's uptime or security.

Red Hat Enterprise Linux has not yet enabled us to achieve security standards certification because we do not go after any of those. There are some products that we will have to do once we get there, but so far, we have not had to certify anything.

Red Hat Insights gives a lot of insights into known issues that we do not think about unless we call support. It tells us to proactively fix something.

I have used Image Builder and System Roles mainly for Red Hat Enterprise Linux for Edge. It builds out the OS tree build for us, which is very helpful. I do not like to do that myself.

I use the Red Hat console every now and then, but I do not use it heavily. I am old school.

The security updates and the support that comes along with it for applications are valuable.

Red Hat Insights was a nice feature to discover. I did not know about Ansible until probably eight years ago. I learned that language, and that was a void or something that was missing for over 25 years.

I like the SCAP Workbench interface that I can use to build some security around. I use Ansible to go out and do configuration management checks as well. Overall, I feel it is very easy to get the data I need.

We finally started doing Red Hat Enterprise Linux for Edge. That one definitely is an improvement. One piece that is missing is that we are required to use moby-engine, but currently, Red Hat Enterprise Linux for Edge forces Podman, so we have to work around it.

I have been using Red Hat Enterprise Linux for a decade in my current organization, but overall, I have been using Red Hat for over 25 years.

Early on, support was closer to a six, but now, it is a nine out of ten.

I have used them all back from the early nineties. I have used CentOS and others. The reasons for companies switching from those to Red Hat Enterprise Linux are that most of it is open source, and they get more product features. There is a market. If other companies are doing it, they tend to switch over. Containerization is a major reason as well.

I was involved in the OpenShift deployments. We are also directly involved in every version of Red Hat Enterprise Linux. We are involved in the proof of concept. Its deployment is straightforward.

We used Red Hat with the OpenShift deployments to make sure we were doing it right, and then a lot of other things, such as Red Hat Enterprise Linux 8 or Red Hat Enterprise Linux 9, we just did ourselves.

In terms of our upgrade and/or migration plans to stay current, we are upgrading everything to Red Hat Enterprise Linux 8, and we are going to Red Hat Enterprise Linux 9 already. We are making that a product feature. We are using Red Hat Enterprise Linux for Edge for our remote deployments.

In terms of provisioning and patching, we deploy the base image, and then we use Ansible for the configuration behind it. For Red Hat Enterprise Linux for Edge, we use the OS builders to build out that same image. I use Kickstart to build the base image before the configuration.

I do not track that in the company, but I am sure we have seen an ROI.

It seems to be fair. It is not overpriced. I went to the simple model, and that makes it easier for us to deploy.

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

We had a lot of IBM AIX servers. We migrated a lot of them to Red Hat Enterprise Linux. We have a lot of VMs, and we have a few physical servers. Currently, we are moving all the Red Hat VMs to the cloud. There are 1,600 to 1,700 Red Hat VMs that we are currently running.

The main benefit is that it can be easily recovered and easily restored. It is on the VM. We can easily restore every image that we back up on the VM. If something happens, we can easily fix it. Support and maintenance are easy. The most common issues that happen with Red Hat Enterprise Linux are password restore issues. We can go and restore the passwords through the single-user mode. This feature is well-developed and good.

We are using Ansible for the most automations. We can push everything through Ansible. We are moving towards automation to make sure our system can be easily maintained, and we can recover, restore, and do the things that we want. We have 1,600 to 1,700 servers. We have Ansible Tower, and we have a few satellite servers and a lot of capsules to support Red Hat servers.

If anything is supported by Red Hat Enterprise Linux and the feature is available in Red Hat Satellite, we are able to install it on Red Hat Enterprise Linux. We are using Red Hat Satellite to install all the patches and all the packages, so if a feature is available, we can easily install it if it is supported.

Red Hat Enterprise Linux has built-in security features for simplifying risk reduction and maintaining compliance. We are working with most of the security environments. Security is our main concern. We have zero tolerance when it comes to security. We are able to apply security rules and regulations within the Red Hat environment.

We are using Red Hat Enterprise Linux 7, and we normally look at how it can easily support the system. With Red Hat Enterprise Linux 7, we have a high-security system. We have a lot of features there. That is the main thing, but currently, we are moving from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8.

Red Hat Enterprise Linux Leapp and Red Hat Insights have been useful. RHEL Web Console is also helpful.

We have access to the Red Hat knowledge base. We have frequent meetings with Red Hat. Red Hat partners provided us with all the information and any kind of training.

We are using the features that are available with Red Hat Enterprise Linux and Ansible. As such, there are no specific features that we are looking for.

We have frequent meetings with them. We have had some issues on the application side and the OS side for which we opened cases and discussed those concerns and questions in the meetings offered by Red Hat.

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

Upgrades and migrations are ongoing processes to stay current. We are a big company. We always have migration going on. We always have the build process. Red Hat's presence keeps increasing in our environment. We are going to have about 2,500 Red Hat Enterprise Linux VMs in the next year.

If there are any concerns, we have a meeting with Red Hat, and they provide the required support. When we have any concerns or questions, they answer them. It is easy. I would rate their support a nine out of ten.

We have probably seen an ROI. Red Hat is getting better every day.

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