What is your primary use case for Red Hat Enterprise Linux (RHEL)?

We use Red Hat Enterprise Linux primarily for our entire group because most of our applications are based on Linux.

Red Hat Enterprise Linux is used within our organization to orchestrate a multitenant, microservice-based architecture. This supports a distributed system of predominantly web-based applications and frontends. A typical deployment involves around 60 to 70 Amazon EC2 instances working in concert. The primary use cases involve running interconnected applications with requirements such as low latency and high availability, often achieved through redundant, multi-tenant, and load-balanced architectures. These applications may utilize read or write-optimized instances or be memory or processor-optimized, depending on their specific needs. Optimization is achieved through the processor, RAM, and connected protocols. The foundation for these applications is Red Hat Enterprise Linux.

We use Red Hat Enterprise Linux for model bases and websites. We chose Red Hat Enterprise Linux for its robust security and reliable support, which are critical for our government healthcare department and require 24/7 operation.

I use Red Hat Enterprise Linux to control my Docker systems and build and run containers on them. I also use it for a tokenization project I'm working on.

We use this operating system for our on-prem servers because it is more secure and reliable. We can install whatever application we want.

I work on SAP HANA, which is on Red Hat Enterprise Linux.

We are using the solution for automation. Mainly, we're doing a lot of automation with it. One of the projects, for example, is for ensuring payments processes on forms. We streamline and optimize the insurance claims process using OpenShift. This has enabled us to do faster claims processes and make resource utilization more efficient than it was. Everything can be done online. There are no papers involved.

As an organization, we use Red Hat Enterprise Linux for its stability and security. I have worked with it on the cloud as well as on-premises. We use it with AWS.

As a teacher, I have used Red Hat Enterprise Linux for server-side applications and containerization. My experience encompasses various system administration tasks, including managing servers, directories, data storage, files, and other related elements. While teaching my students about Red Hat, I share my knowledge of system administration tools. This prepares them for Linux work environments that use Red Hat, exposing them to these tools and their applications. This also strengthens my organization's position as a Red Hat Academy, enhancing our sector's expertise. Red Hat is a valuable tool for learning system administration due to its widespread use and versatility.

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

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

We use Red Hat Enterprise Linux primarily for data analysis servers for our scientific researchers. They log in remotely from around the world to access experiment data and run experiments using Python and commercial applications.

Most of our infrastructure is made up of Linux servers. All of the apps that we have published are running on a Linux system. That is the main functionality. I am responsible for Ansible for automation, and I am also responsible for our Satellite server, which is for patching and things like that. We use Red Hat Enterprise Linux a lot. We have 80% Red Hat Enterprise Linux and 20% Windows.

A lot of our Red Hat operating systems run middle-tier applications. We are mostly a JBoss shop, so they are homegrown applications. They are Java-based. We have several types of applications. We have identity, security, Oracle database, etc.

We use Red Hat Enterprise Linux for just about everything in my company. Our use cases stem from three-tier applications up through cloud deployments, Kubernetes, containers, etc. Prior to this, I worked in an enterprise as a Linux engineer.

We are mostly using it for application servers, infrastructure servers, and database servers.

We need to build a lockdown version of Red Hat Enterprise Linux to build our application on top.

We have a database that we maintain for root passwords, and sometimes I need to break the root password to reset it. We work a lot on logical volumes where I need to grow and shrink volumes on the fly. I did not have to shrink the logical volumes much, but I worked a lot on growing logical volumes on the fly to make them available for the database team. I have done network-related things. I configured network multipathing or IP multipathing where we can parallelly route the traffic to multiple ethernets. I work a lot on user-related issues as well. We are also using Ansible a lot for automation. I am writing some playbooks, so there are a lot of use cases.

I utilize Ansible to harden Red Hat devices across a multitude of disconnected environments.

We are deploying Red Hat Enterprise Linux as our primary Linux OS, and we are using Ansible for some automation initiatives. Our use cases are around centralization.

We primarily use it for enterprise software, databases, and some custom applications.

We are a brokerage firm. We use Red Hat Enterprise Linux for trading purposes. We develop our applications on it. By implementing Red Hat Enterprise Linux, we wanted a stable server and OS.

I use the product for the integration capabilities it provides between my company's servers and the servers from other companies since we operate in the banking sector. I use Red Hat Enterprise Linux (RHEL) for clusters or load balancing. The tool provides an open-source platform to use any program. Many programs can be installed over Red Hat Enterprise Linux (RHEL).

We use Red Hat Enterprise Linux to manage our database.

Red Hat Enterprise Linux serves as the foundation for our cluster infrastructure, allowing us to deploy applications and connect servers. We further enhance operational efficiency by deploying Kubernetes on top. We chose Red Hat Enterprise Linux for its stability and well-rounded features and its proven track record of decades of reliable operation.

I use Red Hat Enterprise Linux for my infrastructure and OpenShift primarily for its Kubernetes capabilities. I wanted to build infrastructure based on Red Hat for commercial distribution for data centers.

We use Red Hat Enterprise Linux as our core operating system for hundreds of our critical systems including our databases, complete middleware, and over 500 VMs.

We host Red Hat Enterprise Linux on our VMware Cloud and manage our customers' machines.

We use containers to create RPM packages for graphics drivers.

My primary use case for it is to run Jenkins servers.

We use Red Hat Enterprise Linux for our on-prem VM infrastructure. Recently, we got the OpenShift platform to help with containerization on-prem. Moreover, containerization is one way we're trying to get rid of any legacy. We don't patch. We try to have a fresh build with the newer version of the patch. We try to use those Red Glue deployment strategies and remove whatever we find in misconfiguration or vulnerability instances rather than fixing them. We redeploy it.

We have general use cases.

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

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

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.

We use it for databases and applications. In the new model, we keep databases separate from applications. Currently, about 90% of our operations are running in Red Hat 8. Some systems are still on Red Hat 7, but those will be migrated off by the beginning of next year.

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

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

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

We use Red Hat Enterprise Linux for off-the-shelf applications and Oracle databases.

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.

We host our applications and database servers on Red Hat Enterprise Linux. We mostly have an on-premises setup. We also have Red Hat Enterprise Linux running on a virtual machine.

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.

We predominantly use Red Hat CoreOS we use it to connect to different types of OpenShift clusters. Whenever I work with RHEL, it's always been with the CLI.

I use the solution for research purposes.

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

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

We use Red Hat Enterprise Linux for servers. We have deployed application servers and database servers on it. We run Oracle Database, WebLogic, Apache, and JBoss on it.

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.

We are running databases and applications on it. We are also using the Squid proxy server, NGINX, and Apache, so we are running multiple services on the servers. We are using Red Hat Enterprise Linux eight and nine. We also use Red Hat Satellite and Red Hat Ansible Tower. I've mostly worked with the telcos and banking sectors, and they mostly have on-prem setups. We do have a hybrid environment where we have multiple machines running on AWS. I am based in Saudi, where they are using another cloud called Din. They are running Red Hat Enterprise Linux on Din as well.

In our organization, we use the solution as our internet banking platform.

We use the solution in our company for normal application support and for databases.

We use the solution for deploying middleware applications and many different applications that we have, like the ones we can use in the marketplace with different users. We use other kinds of solutions in many of the applications we develop. But in general, we use Red Hat Enterprise Linux.

Internally, we use Red Hat Enterprise Linux for services and for applications that we run, especially Linux based-applications. We also have SAP solutions, which we sell to the customers as a total solution with Red Hat, SAP HANA, and also for our own cloud-based SAP HANA, which is under Red Hat's operating system.

RHEL is a phenomenal operating system for three primary reasons: * Support compared to the rest of the Linux ecosystem * Cohesive ecosystem * Application platform The combination of these three aspects has proven to me from an advising perspective that it is key in decision-making.

There are multiple use cases, and I am mostly focused on information security. Before we promote an ACS policy to production, we should be able to test that build and see how that policy behaves for that build. We use Podman to build some test images and get them to our development box. Then we use commands that we scan against those images. That has been one of the major use cases. In the future, we'll move our automation program from an on-premises Windows server to a Linux server. Over a period of time, we want to move those applications to the cloud and OpenShift. Currently, we have many legacy applications that are still being run on Windows Server, and we use the title job scheduler for that. Once we mature and gain more confidence, we want to containerize those applications and move them to OpenShift and Linux.

We use it to host applications, services, and backend databases. We aren't using it on the cloud. Most of my customers are DoD or some type of government agency. If it's not classified, it's siloed in some way. We don't get to use a lot of the functionality that makes Red Hat cool. It's all disconnected. In terms of version, currently, mostly everything is on versions 7 and 8. I've started pulling up some of the things from version 9, but that won't go into production for a while.

We are running our critical applications on it. We are using versions 7, 8, and 9, and we are running our workload on private clouds. We are currently testing Azure, but we don't have the production workload on it.

As a whole, our organization is using it on Bare Metal on-prem and the private cloud, and then also in more than one public cloud environment. We probably have all three cloud providers. We definitely have Azure and Google Cloud. The environment that I support has about 40 apps in one cloud or another, but the organization as a whole definitely has hundreds of apps in Google Cloud or Azure. They're predominantly in Azure. The Google Cloud adoption is pretty recent compared to our Azure utilization. I'm supporting a capital markets environment. A substantial portion of my environment is still Bare Metal at Colos. I'm sure on the application side, there's plenty of JBoss in our environment. There have been recent conversations around OpenShift on-prem that I'm working on, and our enterprise cloud teams are looking at or are using ARO in the cloud. In the next year, our use of the Ansible Platform will go from zero to full throttle as quickly as we can make that happen. We found the event-driven Ansible very interesting.

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 use the solution to develop OS for our internal use. I deliver it to our internal clients, so they can use it for whatever applications they may need to use it for.

We use Red Hat Ansible Automation Platform. We are using version 8.4, but we started with 8.3.

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.

Primarily, we use it for a couple of different servers. Some are doing data hosting, and some are doing network management-type functions. We use it on-premises. We do not use it on the cloud. Because of government work, we're not cloud-based.

I am an administrator for Red Hat Enterprise Linux. We use Red Hat Enterprise Linux in a hybrid environment running off of on-prem servers and also AWS. I use Red Hat Enterprise Linux for a variety of purposes. For example, we use it in cloud control systems at our factories. We also use it for test systems, data acquisition, databases, and web services.

We use Red Hat Enterprise Linux as an infrastructure support operating system across both x86 and s390 platforms. Specifically, we are running it on x86 Intel and Linux s390 mainframe on Zynq.

We run various application servers. We have application servers for Java and Python. We also run Postgres and different applications. We have Kubernetes, Docker, Docker Swarm, etc. We have a wide variety. We weren't trying to solve a particular problem by implementing Red Hat Enterprise Linux. We've used Red Hat Enterprise Linux for so long. We used to modify the Kernel in the early versions of Red Hat, but that's not needed anymore. We are currently using versions 7, 8, and 9.

I work in the financial industry in Brazil and my first job was to use Linux. We deploy Red Hat Enterprise Linux on-prem and in the cloud. Our cloud provider is AWS. We use Red Hat Enterprise Linux for web applications, including the JBoss data bridge. We also have some applications for prevention and risk. Red Hat Enterprise Linux is used for most of our applications in Brazil, so it is used for almost everything. We run our workloads and applications on AWS.

I work in the energy sector, so we use Red Hat Enterprise Linux for a variety of purposes. These include high-performance computing, running applications like SAP, geospatial applications, and Oracle. We rely on Red Hat Enterprise Linux for a wide range of applications, including those that require running Oracle databases.

We've implemented OpenShift on top of OpenStack. It's a Red Hat OpenStack environment, which is the virtualization layer, and then OpenShift is for the cloud technologies. It's currently on-prem on a private cloud. In the future, we might utilize a public cloud if the government approves that. Currently, the banking industry isn't allowed to go to the public cloud.

When I worked for an MSP, we had a lot of requirements for Linux servers. Any customer services that were deemed to be on Linux were on Red Hat 6 or 7. In fact, a good forty percent of our estate was on Red Hat 6 or 7.

I use Red Hat Enterprise Linux for deploying servers to install Oracle Databases.

Currently, we're running our web servers on Red Hat Enterprise Linux.

Our company uses the solution to provide DBA services and manage Linux databases for clients. The solution works well both on-premises and in the cloud. We deploy based on client preferences that include on-premises, hybrid cloud, and fully public or private cloud. Depending on use cases, we use different cloud providers such as AWS, Oracle, or Azure and they all have their own limitations. The solution is flexible and has great scripting so it can accommodate any conditions. For one client, we have version 7 installed and managed on a variety of physical servers for different environments including production. For another client, we have VMs. For other use cases, we have a setup of active sites in on-premises with standbys in the Azure cloud.

We use RHEL for network management and network services systems. 

We have DNS servers, data collectors, network management systems, subscriber management systems and network operations systems running on RHEL. 

I personally have dealt with systems as early as RHEL 4,5,6 and now running 7. RHEL is stable and secure so we never had OS-level performance issues or security incidents that can be attributed to the OS.

The main use case is general system administration, which includes configuring networking, configuring storage volumes, managing users, and running backup applications.

We have a very large system with ten application teams. We've got four DevOps squads that support those teams. We use this solution to containerize about 85% of our applications and software. OpenShift 4 maintains our applications and our databases, keeping our system up to date and it integrates with our CI/CD pipelines. We also use OCS for security compliance.

Our company uses one of the solution's varieties, mostly CentOS. We are restructuring and moving to the licensed version of RHEL and its derivatives. We use both RHEL 7 and 8 mostly in the cloud but also have a small data center where the solution is used on bare metal. Our team does a lot of AIML work where we set up instances to run simulations. We are moving a bit into Redshift because we do not have many staff members with containerization or Kubernetes experience.

Our organization uses the solution as a scientific workstation for forecasting, data collection, data presentation, and delivery of products in the form of bulletins or images to the general public. We have five to ten scientists who work on installations at any given time. We need a pretty powerful but flexible cluster system to operate and develop applications for general maintenance. We have over one hundred sites so we need something that is efficient. We use Smart Management to distribute packages and Ansible for some of our remote, repeatable management tasks.

We are part of the State Department and use the solution to achieve operational excellence and readiness for the cloud. We think about what the next 20 to 30 years of consular systems infrastructure might look like to build and design for the next 40 years. Not many other companies think beyond a decade. The solution was implemented in our environment in 2014. The initial mission is still the same but how we go about it is different. For now, the solution is more for application support and making sure we are following State mandates or executive orders. For example, one use case involved planning, designing the implementation, and executing a launch of online passport renewals. Our environment is moving toward tools that provide automation to remove human error. These are tactical operations and use cases. We currently use SaaS, OpenShift, and Ansible to a limited degree.

I worked with different organizations. So, the use case varies from organization to organization. Right now, some of the teams are using it for applications like BI, and then there are a few others that are using it for Websphere, middleware, etc. In terms of the version, most of them are on 7.9, but there are a few on 8.2 and 8.4 as well.

I work for an IBM business partner and we install Red Hat for our customers. They use Red Hat for databases, application servers, and some IBM applications that we also install. There are different uses.

We primarily use RHEL for LAMP stacks. Our deployment is currently on-premises, but if they change their licensing model on the cloud, we might start rolling it out in the GCP. It's used globally in VMware environments. We use it in APAC and AMEA, but the majority of the deployments are in the US. The major platforms that we run on it are PLM environment and digital asset management. Our shop is what we call out of the box and if it doesn't run on a container out of the box, then we don't run it on a container. So none of our stuff is running containers right now.

I use Red Hat to run applications like Apache, MySQL databases, etc. It is suitable for data storage and firewall. I can also measure performance with the SAR tools and do all I need with the Linux stack. I run several server farms, community applications, and more. Multiple teams use it. We have a hybrid setup, but we try to keep the use cases separate for each, so they're not transiting that much.

We are internet service providers in Bangladesh and resellers of this product to our customers to manage their network infrastructure.

I use it for almost everything. I run a company in South Texas and Mexico. We are a cloud service provider, and we have implementations for almost everything. We are using it for websites, virtualization, orchestration, and containers, and we are also using it a lot for telecommunications. We use almost all of its features. We have many versions. We have versions 8, 9, 9, 9.1, 9.2, etc.

I'm using Red Hat as an OI solution with some Oracle databases and an FTB server on top of it. I am not using containers in Red Hat. It's solely serving as an OS with direct applications installed on it. We have a few thousand users benefiting from Red Hat indirectly, but only 10 to 20 people work directly with it. I only use Red Hat in one location right now. Previously, I had it deployed in a cluster.

We're using it to support security applications. We also use it for various infrastructure aspects, such as hosting Satellite or Ansible Automation or Confluence. We have a mix of different apps running on it.

I am primarily doing developer enablement for users of Red Hat-based software stacks. Most of my experience for the last five years will be in the context of AWS and Azure. As my customers are primarily cloud-based, they are primarily using the Red Hat repositories hosted with Amazon and Azure. My customers are primarily DoD, so they are using EL7. We are trying to get them to move in the direction of EL8, but it is a slog.

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.

We have various use cases with about 12,000 instances across four data centers and three different clouds. In general, it's for the adoption of and standardization with other vendors, so that other vendors' software is known to work. We're doing lift-and-shift of existing hardware infrastructure that is onsite into the Cloud.

We use Red Hat for all sorts of use cases. This includes everything from running applications and databases, or the combination thereof, to building software for products that we use for embedded design. My company has several RHEL implementations deployed in the field, including versions 4, 5, 6, 7, and 8.

We use it for core infrastructure services, like package mirrors, configuration management hosts, and proxy requests going to the Internet or as reverse proxies in front of our applications. Our campus management software is delivered via RHEL and applications like Wikis learning platforms. Almost all machines are running on virtualization. Only a few bare-metal systems exist today. Currently, we are not engaged in any kind of public or hybrid cloud environment.

Our use case is mostly for application servers. We are not really using it for any of our file servers. We have a storage department who usually just deals with NAS and things like that. However, this solution is primarily for application servers.

Our primary use case is that we use it for transaction servers. We have it on-premises, mostly virtualized.

We are primarily using it for services, such as cloud infrastructure services, for our business. We are working with a Town Council in Bolivia. We provide the environment for deployed applications, and we are using it for the private cloud, Linux server, and applications developed within the company. Mostly, we use version 7.0. We also have three servers with version 8.5. We are working with everything on-premise. We have a cloud, but most of the cloud is accessible from inside the company. It is not accessible from outside of the company.

It is used for our production system. We are running multiple web servers and multiple databases on RHEL operating system platform. We are also running some of our OpenShift containers on it. We have a lot of applications that are running on RHEL versions 5, 6, 7, and 8 in our environment, but the maximum number of applications are running on RHEL 7 and 8.

We use a combination of Red Hat and Oracle Linux in different parts of the organization. We have a cluster, where RHEL is running. The instances are both virtualized and real, depending on which part of the cluster you're utilizing. They are set up as either RAC or single instance, depending on what we are trying to achieve in terms of performance. We have PeopleSoft systems that are all deployed on Red Hat. We also use it for deploying simple websites. PostgreSQL is running on the systems, along with a frontend that was created by the developers. We also use it for DNS fallback authentication. We have quite a few Windows systems, as well, and some of the applications that we used to run on Linux have now been migrated to Windows. We have a mixed environment, although, in the cluster, our deployment is primarily on-premises. There are some deployments into different cloud providers, depending on the service that we're looking for. However, when we head into the cloud, we tend to go to Product as a Service rather than Infrastructure as a Service or the like. This means that we're less concerned about the underlying operating system and we try to avoid interacting with it as much as possible. So, it is just virtualization in this case.

Our primary use case for RHEL is running our front-end web servers. When you visit our site, all of the front-end servers are Red Hat. The databases that are hosted are Oracle and they predominantly sit on Red Hat 7. We're trying to migrate those to version 8. We also use it for BI. We have a digital footprint in Azure and AWS, as well as on-premises. Things for us are very fluid. We're always changing and adapting to our environment, based on what the needs of our faculty and students are.

We are using it for application services.

It started mostly with websites and open source environments overall for development. Now, we are moving into business applications as we are migrating our ERP, which is a cp -r tree, to Linux. We are also migrating the database of SAP to SAP HANA on Red Hat Enterprise Linux. We use RHEL versions 7 and 8. There is a bit of version 6 still lying around, but we are working on eradicating that. It is mostly RHEL Standard subscriptions, but there are a few Premium subscriptions, depending on how critical the applications are.

We deploy front-end and back-end software applications on RHEL, and it's our app server. Most of our app servers and our production servers are on RHEL. They're running on RHEL, and that's why they are profiting from it. I2C is the issuer in the processing payment industry. Basically, we do the issuer processing for credit cards, and all the bank magic that happens when you swipe a credit card is handled by us. We're also using RHEL servers for processing debit card payments.

I use it for running RAID servers, Database clusters, and a lot of other open-source tools. I have also used it as a firewall. We have on-premises dedicated servers located in some data centers. We also have cloud servers on the public cloud. I am currently using the latest version, and I have also worked on previous versions as well as Template.

We use it for * some of our websites * one of our main applications for the City of Gothenburg * automation * the underlying operating system for our GitLab server.