Ansible on CentOS 10 Reviews

My main use case for Ansible on CentOS 10 is automating server configuration, software installation, and routine system administration. I use Ansible playbooks to install and configure JINX, manage firewall rules, create user accounts, and ensure consistent settings across multiple CentOS 10 servers. This has been very helpful in reducing manual work, minimizing configuration errors, and making server deployment faster and more repeatable.

I typically use Ansible playbooks to automate server setup and configuration across CentOS 10 environments. My workflow involves defining the required settings in YAML and organizing tasks into reusable roles, storing the playbooks in GIT, and testing changes in a staging server before applying them to production.

Another significant benefit is that Ansible makes server management more repeatable and easier to scale. This workflow saves me time, reduces configuration drift, and makes troubleshooting and server maintenance more efficient.

Ansible on CentOS 10 has positively impacted my organization by automating repetitive server administration tasks, reducing manual configuration errors, and making deployments more consistent.

For example, automating the JINX installation and configuration across multiple CentOS servers reduced the time spent on repetitive setup tasks from approximately 30 minutes per server to about 5 to 10 minutes of automated execution and verification. It also reduced configuration inconsistency because the same tested playbook was used across environments.

One of the best features Ansible on CentOS 10 offers is agentless automation. I particularly appreciate playbooks, which is one of my favorite features, along with configuration management and reusable roles.

Agentless automation and playbooks stand out for me because they enable me to manage remote servers over SSH without requiring an Ansible agent on each machine. Playbooks use simple YAML files to automate tasks such as installing packages, configuring JINX, and managing services seamlessly.

The error handling and reporting in Ansible on CentOS 10 help identify failed tasks and troubleshoot deployment issues more easily.

Ansible on CentOS 10 has strong security capabilities for infrastructure automation, including SSH-based access, privilege escalation controls, and Ansible Vault for encrypting sensitive data, which I believe is excellent for AI-assisted automation.

Ansible on CentOS 10 integrates well with AWS services, particularly EC2 for server provisioning and configuration.

One of the main areas that Ansible on CentOS 10 could improve is providing clearer error messages, faster execution across larger environments, and simpler debugging for complex playbooks.

For example, when I was deploying JINX across multiple CentOS 10 servers, a package installation failed because of a repository or dependency issue. Ansible reported a task failure without immediately making the root cause obvious. This required additional troubleshooting and delayed the deployment.

Improved integration with monitoring systems would make automation easier to maintain and more reliable.

I have been using Ansible on CentOS 10 for five years.

Ansible on CentOS 10 is generally reliable for infrastructure automation because playbooks follow explicitly defined tasks and desired configuration. Ansible on CentOS 10 is very stable, with minimal downtime issues and is always reliable.

Ansible on CentOS 10 is very scalable and handles my organization's growth well.

The customer support is very proactive and responsive. I would rate the customer support eight out of ten.

I have not switched from any previous tool.

Deploying Ansible on CentOS 10 was relatively straightforward. The main tasks involved installing Ansible, configuring SSH access to managed servers, defining an inventory, and creating basic playbooks.

The configuration process was relatively straightforward. I configured the inventory file to identify managed CentOS 10 servers, set up SSH key-based authentication, and organized automation tasks into reusable YAML playbooks and roles.

I have seen a return on investment mainly through time savings and reduced manual configuration errors. For example, automating server setup reduced the estimated time per server from approximately 30 minutes to 5 to 10 minutes, saving approximately 60 to 80 percent of setup time.

Ansible Core is open-source and does not require a separate software license. The metering and billing experience with Ansible on CentOS 10 is straightforward because Ansible Core is open-source and does not charge per task or managed server. This helps keep automation costs predictable. My experience with the Ansible cost has been positive, transparent, and very manageable.

I considered several alternatives before choosing Ansible, including SaltStack and Bash scripts.

On a scale of one to five, I would rate Ansible on CentOS 10 a four out of five. I chose a four because it provides powerful automation, consistent configuration management, and reusable playbooks that reduce manual work. I did not give it a perfect score because of two or three minor improvements needed, such as clearer error messages, faster execution across larger server environments, and improved integration with monitoring systems. My experience has been very positive. Ansible on CentOS 10 is particularly valuable for teams managing multiple servers because it improves consistency, reduces manual effort, and makes infrastructure easier to maintain.

Public Cloud

Amazon Web Services (AWS)

My primary use for Ansible on CentOS 10 is to prioritize product testing, and thanks to Ansible on CentOS 10, I can automate deployments on multiple CentOS and Red Hat machines.

A concrete example of automation I have carried out with this tool is performing upgrades of different products on different environments, which allowed us to have the same configuration on all environments thanks to Ansible on CentOS 10, while minimizing the impact of human error on the configurations.

Ansible on CentOS 10 is a very powerful product for deploying configurations, product installations, or actions on different machines at the same time, and Ansible Tower complements it by adding the ability to create sequential action flows via Ansible on CentOS 10.

The best features that this tool offers me include Infrastructure as Code as the first, environment stability through controlled configurations which allows me to have identical (ISO) environments as the second, and the ability to very quickly deploy the same configurations on 1, 10, or 100 machines as the third, which is very useful for saving time.

Infrastructure as Code with this tool has changed the way my team works by allowing us to have a sort of pseudo documentation in the code. Thanks to the code that is in Ansible on CentOS 10 in Git, it allows us to quickly understand and have a standard structure thanks to Ansible Galaxy. Even if a new team member joins our team, they are not lost thanks to the standard structure from Ansible Galaxy.

The positive impact this tool has had on my organization is that when there are bugs in an environment, it is very easy to reproduce the bug in a test environment because the configuration is the same. This has been a huge time saver to have identical (ISO) configurations between environments and thus to have the same behaviors and to reproduce bugs and to understand and debug them.

In my opinion, Ansible on CentOS 10 could be improved in the simulation part. In Ansible on CentOS 10, it is possible to test a playbook without actually executing it. However, from time to time when it simulates, if a file does not exist, even though it is a simulation, it fails with an error, which is unfortunate because the simulation should take into account this kind of non-existence since we are in a simulation.

I have been using this tool for about a year and a half.

I have noticed 100% reliability with this tool, as I have never really had any issues with it. The only behavioral issues I have encountered are when we do not fully understand a plugin, and sometimes it is more a knowledge issue than a product stability issue. Ansible on CentOS 10 is very stable and works very well, and the expected results are often around 98%.

The scalability of this tool meets my needs when the number of machines or environments increases. Its strong point is scalability; the more hosts you have, the faster you go.

I rate the customer support for Ansible on CentOS 10 by saying that I have never needed to contact support as I go on Stack Overflow and I look into Ansible on CentOS 10's own documentation, finding it really powerful and extraordinary.

I did use another solution before, specifically Puppet, Salt, and Chef, and I find that the most straightforward one for configuration, speed, and everything is Ansible on CentOS 10.

What led me to choose Ansible on CentOS 10 over Salt, Puppet, or Chef is its ease of installation, its fast compatibility with the SSH protocol, its simplicity in setting up and creating playbooks, the standardization of structures via Ansible Galaxy, and the fast integration if I purchase Red Hat's Ansible Tower.

Ansible on CentOS 10 is deployed in my organization fully on premise.

I have seen a return on investment with this tool. For the debugging part, when we have identical (ISO) behaviors, it is easy to reproduce a production behavior in a test environment, leading to time savings. Infrastructure as Code allows us to have good documentation of behaviors and operations, so documentation on SharePoint or Confluence is much smaller, which is another time saving aspect. Installing a product or a patch or anything via Ansible on CentOS 10 allows us to install it on 1, 10, 20, 100 machines, and the more machines we have, the more time we save.

Regarding pricing, implementation costs, and licenses for this tool, Ansible on CentOS 10 is free, so we implemented it. The only cost is the working time of the team members and myself.

Before choosing Ansible on CentOS 10, I did not evaluate other similar solutions, as it was my experience with previous products that led us to use Ansible on CentOS 10.

My advice to others considering using Ansible on CentOS 10 is to first create a standard and put an initial setup in place, meaning to agree on the sudoers part and to properly secure the SSH part. Then create a standard for the structure of files and folders. I also advise creating a kind of reference bible so that everyone is on the same wavelength when they develop.

I would suggest an improvement for interview processes to allow more response time because when there is a pause in the conversation for a few seconds, it feels as if moving to the next question occurs, so being more patient before moving to the next question would be beneficial.

I rate this product an 8 out of 10.

The main use case for Ansible on CentOS 10 is configuration management, as I have a fleet of servers, including web servers, backend Python servers, and Node.js servers, all configured using Ansible.

I have used Ansible for configuration management on various front-end servers and back-end servers, specifically for one SaaS product that we were building, an email-related product with a frontend in Node.js, a couple of Java back-end servers, an Elasticsearch cluster for metric data, and a monitoring layer using Prometheus and Grafana. All these servers were managed with Ansible for configuration management using dynamic inventory, with a staging setup of four or five servers and a production environment with 12 to 14 servers, as well as a smaller deployment on DigitalOcean with six servers.

I used roles in Ansible on CentOS 10, which helped me significantly by allowing me to carve out roles assigned to subsets of servers with similar use cases, along with templates such as Jinja for dynamically updating configurations on those servers. This approach improved my efficiency with Ansible in configuration management.

The impact of Ansible on CentOS 10 on my organization has been significant, with quick deployments as a configuration management tool aiding me considerably. I tried Puppet prior to Ansible, but its agent-based nature posed problems that Ansible avoids, allowing for quick turnaround times, reduced costs, and an easy learning curve with minimal setup requirements.

Regarding deployment, Ansible on CentOS 10 has helped me achieve faster deployment, especially when moving a setup of 14 to 15 bare-metal servers and VMs to DigitalOcean, which reduced my deployment costs to almost one-third of what I was spending on bare-metal servers. The quicker turnaround time in writing the Ansible playbook for this deployment allowed me to swiftly prototype my product on DigitalOcean.

One of the best features Ansible on CentOS 10 offers is dynamic inventory, and I particularly appreciate that Ansible is an agentless system. It operates over SSH, so I can include a server in one of the host inventory files and deploy it without needing pre-installed agents, whether in data center or cloud environments. Additionally, it is idempotent, meaning it only applies changes when necessary, saving CPU resources, and the templating and roles are excellent features I have used quite often in deployments.

I think the most important feature I use often is the module library in Ansible on CentOS 10, which has a very rich module library that has helped me significantly. I have not built any custom modules, but I frequently utilize roles for deploying sets of packages such as web servers, allowing minimized repetition when deploying across different environments.

The self-sufficient built-in modules are extremely beneficial. One of the latest use cases for Ansible was setting up base infrastructure on my Proxmox base servers using the module library, providing an excellent experience for both virtualized and physical servers.

Regarding how Ansible on CentOS 10 can be improved, I think further integration with other tools would be beneficial. While Ansible already integrates with Vault, integrating other HashiCorp tools would enhance its capabilities and allow for better interaction with other open-source tools.

I have used Ansible on CentOS 10 for close to three to four years.

Ansible on CentOS 10 is very stable for me. Earlier versions worked great, and the latest version continues to meet my needs effectively.

I have used Ansible on CentOS 10 effectively across 15 bare-metal machines, 50 virtual machines, and even larger setups with up to 100 servers, allowing me to scale operations across thousands of nodes in a private cloud setup.

I have not used customer support for Ansible on CentOS 10, but I believe it is good based on the resources available. I have resolved many issues through online blogs and community support instead of needing direct assistance.

I had used Puppet before switching to Ansible on CentOS 10, finding Puppet's agent-based system cumbersome due to the necessity for agent deployment, synchronization, and requiring a Puppet server, whereas Ansible allows straightforward deployment without needing a dedicated server.

I definitely see a good return on investment with Ansible on CentOS 10, as it saves substantial time during deployments with minimal setup costs thanks to its agentless nature, only requiring Python and SSH for server connections.

Regarding pricing, setup cost, and licensing for Ansible on CentOS 10, I utilize the open-source offering of Ansible, and there are no licensing fees associated with CentOS 10, making the cost minimal for me.

Before choosing Ansible on CentOS 10, I evaluated other options, primarily Puppet and Ansible, and while I have experimented with Nix, it is limited to NixOS and not applicable to CentOS, making Ansible the clear first choice during my transition from Puppet.

I would rate Ansible on CentOS 10 a nine out of ten, as there is always room for improvement.

I rate it a nine because Ansible is a full-fledged configuration management tool, but I take off one point specifically for the need for larger integration, as existing metrics related to deployment times could be beneficial in increasing efficiency.

In my organization, Ansible on CentOS 10 is deployed across private cloud, public cloud, and on-premises servers, proving to be fairly reliable from my experience.

I have used Ansible on DigitalOcean and Google Cloud for public cloud deployments, but I have not used it much on AWS since I primarily employed Puppet there.

My advice for others considering Ansible on CentOS 10 is to proceed with it. It is one of the best configuration management tools available, whether deploying on CentOS 10 or other Linux distributions.

Hybrid Cloud

Other

My main use case for Ansible on CentOS 10 involves patching and database building, managing the start with respect to OS patching, and handling those activities after kernel updates.

For these activities using Ansible on CentOS 10, I connect to the machine and perform a YUM update on that machine. If there is any update, including a kernel update, it will automatically update, and I block certain updates like Java updates from going through YUM update. Those kinds of updates I handle through another automation tool called Chef, where those are created using tags and versions. All other configurations with respect to CentOS are managed through Ansible code.

I have nothing else to add about my use case with Ansible on CentOS 10 that may be unique to my organization.

Ansible on CentOS 10 has positively impacted my organization by reducing the time to production significantly compared to other automation agents like Chef or Puppet, where an agent is involved and other elements like groups and roles are required. With Ansible, those elements also exist and are very easy to manage.

When I say the time to production is lower, I estimate that it is almost 50 to 60 percent faster compared to my previous process.

The best features Ansible on CentOS 10 offers include being very user-friendly. I can read the code and write the code myself without using any kind of loops or high-level languages like Java. I simply use the YAML language, which is very basic and everyone can easily understand. Additionally, with respect to CentOS, there are no agents involved. I just need an SSH connection to connect with a system, which is very basic, and Ansible works with Python in the backend, so I don't need any other additional software as Python is automatically installed on every machine.

I do not have anything else to add about the features of Ansible on CentOS 10 that I find especially helpful or unique.

There are many ways Ansible on CentOS 10 can be improved, but most of them are already in the open-source platform and in development, so for now, my use cases with respect to this organization are sufficient.

I would add that some features in the code itself are very much appreciated, such as being able to write the code and identify where the issues with the code are.

On a scale of 1 to 10, I would rate Ansible on CentOS 10 a nine.

I choose a nine because Ansible on CentOS 10 is very useful for me and my team.

Ansible on CentOS 10 is deployed in my organization in an on-premises and hybrid cloud setup.

I use both Azure and AWS as the cloud providers in my hybrid cloud setup.

My advice to others looking into using Ansible on CentOS 10 is to proceed with confidence. It is very simple, and you can use it.

Hybrid Cloud

Other

I use Ansible on CentOS 10 for automation, configuration management, and drift management.

I automated the patching procedure with event-driven Ansible for automated event resolution from ServiceNow tickets.

I implemented vulnerability management and drift management where the system checks for any vulnerabilities or configuration drift. If any services are stopped, the system automatically brings the server to the desired state.

I have achieved a 75% reduction in incidents with the implementation of Ansible on CentOS 10, which derives operational expenditure savings from my earlier automation tool. I purchased Ansible on CentOS 10 through Red Hat as a bundle offering that includes the automation platform, operating system, license, and support. This one-stop solution helps me with time management, operational expenditure, and capital expenditure optimization.

Event Driven Automation (EDA) is the most valuable feature.

Anisble on CentOS 10 reduces human hours by automating repetitive jobs with no manual intervention, which reduces ServiceNow ticket incidents and saves manpower hours.

It reduces human costs and operational expenditure. I use Red Hat Automation everywhere for patching on both Windows and Linux servers, as well as OpenShift configuration, all through Ansible, which is very helpful.

I have achieved a 75% reduction in human-touch incidents. Everything on Linux and Windows is now automated.

Ansible on CentOS 10 can manage infrastructure as code, but from a deployment or infrastructure perspective, it lacks features similar to Terraform. I would like features that automatically start services if they are down or unavailable and make maintenance easier.

I need improved infrastructure-as-code configuration for Red Hat satellite environments with a more user-friendly interface. This would allow people who do not know how to write code to easily generate code through an Ansible or AI platform, validate the code through AI, and deploy it directly after human approval.

Documentation is definitely required. Whenever I write code, there should be automatically generated documentation in markdown format that creates a knowledge base. The system should create an automatic repository for all available playbooks so that AI agents can search the library and documentation. If the solution is not found, only then should the AI agent create an Ansible playbook. If the solution is found, it should automatically deploy from the repository.

I would also benefit from having AI-generated code validated by AI agents with proper human oversight and guardrails to ensure Ansible code quality and governance.

I do not use Ansible on CentOS 10 on CentOS itself, but rather on some CentOS flavors and mostly on Red Hat. I have been using it for around the last 10 years.

I have experienced stability issues.

Scalability is good. I am running Ansible on CentOS 10 on EKS, and it performs well.

Customer service is good.

I previously used TCS Ignio tool but switched to Ansible on CentOS 10 because Ignio had higher costs and was more difficult to manage. Ansible on CentOS 10 is easier to manage.

I have achieved a 75% reduction in total incidents, which is deriving operational expenditure savings from my earlier automation tool. I purchased Ansible on CentOS 10 through Red Hat as a bundle basis offer that includes automation, the operating system, the license, and support. The support is much more reliable and provides a one-stop solution, which helps with time management, operational expenditure, and capital expenditure planning.

I purchased Ansible on CentOS 10 through Red Hat. At an enterprise level, the cost is acceptable.

I evaluated Terraform as an alternative solution.

There are some features that I have requested that are still missing. If those features are added, Ansible on CentOS 10 would definitely achieve a 10 out of 10 rating. Apart from that, I cannot find any other challenges with Ansible on CentOS 10. It is very easy to understand, easy to write, and easy to manage.

Anisble on CentOS 10 is secure. The governance part is also important. When AI agents or other systems write Ansible playbooks, there should be a human loop for review or guardrails to check Ansible code quality.

I cannot commit to increased value until those features are approved and present. However, if Ansible on CentOS 10 behaves as I expect with those features implemented, it will be more valuable.

My advice to others would be to first learn how Ansible on CentOS 10 works, understand its features, and learn how the infrastructure Ansible baseline foundation looks. Make your infrastructure scalable by using idempotency in roles. Create roles as collections and use custom collections, which will make management much easier.

Hybrid Cloud

Amazon Web Services (AWS)

My main use case for Ansible on CentOS 10 is automating configuration management. I use it for managing configuration on our EC2 tools and server provisioning. I also use Ansible to consistently install different packages on our servers, configure services, manage users, and apply system settings across all our multiple servers. When we need to set up several CentOS servers for an application environment, I use Ansible playbooks to install the required packages and configure the services. Instead of doing everything manually, this automation makes the setup fast and helps to keep the server consistent.

One of the main reasons why I chose Ansible on CentOS 10 is because it is one of the best tools for configuration management. Manual configuration becomes time-consuming and is prone to error. It was harder to keep multiple CentOS servers consistent if we were using a manual process. Ansible on CentOS 10 gave us a simple way to define every configuration in our playbooks and it repeats the same process without any problem. Instead of logging into ten, fifteen, or twenty servers to install packages and update configuration files, I can just run one Ansible playbook and apply those changes across all our servers. This also helps us to troubleshoot because we know that servers were being configured from the same automation process, making troubleshooting very easy since everything is automated.

Ansible on CentOS 10 has provided significant benefits to my organization. It gives us a repeatable and auditable way to manage our changes. When there is a need to audit what somebody has done, it is easier for us to do that. For example, if we need to update a configuration or deploy a security patch across our multiple CentOS servers, we can update the playbooks and apply the same changes consistently. Instead of relying on manual steps that take time, this reduces configuration drift and makes it easier to maintain the environment over time, giving us a very consistent environment where all our environments have the same configuration.

Ansible on CentOS 10 has impacted my organization in a very positive way. It reduces manual work, reduces human error, and improves consistency across our CentOS environment. We can automate repetitive tasks, provision servers fast, and apply configuration or security changes consistently, ensuring that all the systems are the same.

The time savings are significant. Tasks that could take hours of manual configuration across multiple servers can be handled within a single playbook. For example, when we were initially spending two hours on configuration, we now complete all playbooks in about ten minutes. A server configuration or package update that previously required logging into each server individually can now be applied consistently across the environment in one execution. We also saw fewer configuration inconsistencies and manual errors because the same automation was used each time we ran all this configuration.

One of the features that I like most is playbook-based automation and configuration management. The agentless architecture makes it easier because we can manage multiple CentOS servers through SSH without installing a separate agent on each machine. For instance, when we needed to install a package, update a configuration file, and restart the service, everything happened in a definite way. We defined it once in an Ansible playbook and applied it consistently.

The idempotent behavior of Ansible on CentOS 10 is also important because Ansible will generally only make changes when the system actually needs them. If the changes have already been applied, nothing will be done again, which helps us to reduce unnecessary modifications.

The agentless approach makes things simpler because we do not have to install anything or maintain anything or troubleshoot any agents on every CentOS server. We can just use SSH and start managing servers immediately. When we needed to bring several new servers into our environment, we could add the IPs or hostnames to the Ansible inventory and run everything on our existing playbooks. Compared to other agent-based tools, there was less time spent, less overhead, and fewer components to manage.

Although Ansible on CentOS 10 is a very robust tool, there are still things I would like to see improved. The documentation and troubleshooting guidelines could be more detailed so that anybody who looks into it will be able to understand what to do, especially for more complex CentOS environments. More detailed examples around advanced configuration, security hardening, and integration with new DevOps tools would also be helpful.

I would also like to see more strong visibility into playbook execution, especially when managing large environments. Better error messages and easier debugging would help engineers identify which tasks fail and why.

From my own experience, high availability is important because we use Ansible on CentOS 10 for server configuration.

I have been using Ansible on CentOS 10 for about four years.

Ansible on CentOS 10 is stable. From my own experience, I find it to be stable for configuration management and server provisioning. The agentless setup and repeatable playbooks make it reliable as long as the playbooks are properly tested.

Ansible on CentOS 10 scales very well. One Ansible control node can manage many CentOS servers through inventories and playbooks. Instead of configuring servers one by one, we can apply the same configuration across our growing environment as we expand.

The customer support from my experience is very responsive. The customer support is very good overall. The documentation and the community resources are also helpful. When we run into issues, we could usually find troubleshooting guidelines quickly. For complex issues, having enterprise Red Hat support provides an additional level of assistance.

By the time I got into the organization, everything had already been set up. I do not know if they used a previous solution before I joined. When I arrived at the organization, we rely on Ansible on CentOS 10.

Because Ansible on CentOS 10 is agentless, we do not have to waste money installing agents on other servers. We have seen a positive return mainly through time saving and reduced manual effort. Rather than reducing headcount, we have seen about a thirty to thirty-five percent reduction in dollar amount. For example, a configuration change that might take an engineer several hours to apply manually across our multiple CentOS servers can be handled through one playbook, which saves time. This makes deployment very fast, reduces repetitive work, and also lowers the risk of configuration drift in our environment.

The licensing and setup cost is relatively straightforward. The setup cost is relatively low because Ansible on CentOS 10 is agentless. We do not have to install an agent and it does not require installing software on every server. We only install it on the control node. The licensing is also straightforward, although enterprise support or subscription costs can apply depending on what Ansible on CentOS 10 is offering. For example, we could install Ansible on our management environment and start managing multiple CentOS servers using SSH without having to purchase or deploy any agent on each of them. This kept the initial setup simple and reduced administrative costs.

Everything has been configured before I got into the organization, but from what I saw in the documentation, my organization actually evaluated Puppet and Chef as well. I would say my organization chose Ansible on CentOS 10 because it was simple to set up, it is agentless, and it fits well with our AWS environment. It also makes our workload easier and creates repeatable playbooks to manage multiple servers consistently due to the automation.

Ansible on CentOS 10 is reliable for automation and configuration management. It is a very robust tool for automation and configuration management, especially across multiple servers. The agentless approach makes it easy to deploy and manage. I give it an eight out of ten rating.

From the governance and security standpoint, Ansible on CentOS 10 is very robust. It gives us good control over who can run the automation and what changes are defined in playbooks and how those changes are applied. For example, we can use version control playbooks, role-based access, or approval processes so configuration or security changes are reviewed before being deployed.

Ansible on CentOS 10 is very reliable from my experience over the years. It is very reliable since Ansible on CentOS 10 is primarily an automation tool. For its automation output, I would rate it as highly reliable when the playbooks are properly written and tested. When we use playbooks in my organization to install packages or configure services across our multiple CentOS servers, we get consistent results across the environment. We still test changes in our lower environment first, especially for production systems, just to make sure we catch anything early.

Any organization that wants to manage their servers and wants to have consistency in their environment should start with a small environment and build fewer playbooks first. They should also make sure that they use version control and test changes before they start applying them to their production environment. They should take advantage of Ansible on CentOS 10 roles and inventories as the environment grows because that makes it easier to manage multiple CentOS servers and makes the environment very consistent in general.

Public Cloud

Amazon Web Services (AWS)

My main use case for Ansible on CentOS 10 is patch application, where we need to push patches across our infrastructure. Whenever we want to execute ad hoc queries or commands and retrieve command output for multiple servers, including hundreds of servers, that is one of our primary use cases. We also execute configuration changes for particular files across multiple servers simultaneously, which is another critical use case. There are many use cases we are utilizing Ansible for across our organization.

One specific task I regularly automate with Ansible on CentOS 10 is adding NFS mount points from VAST data storage, as we work in the AI infrastructure field. We create NFS mount points from VAST data that are shared across multiple AI infrastructure environments, including DGX or HGX boxes. This is one of our main use cases recently, where we attach particular mount points across all the servers, numbering over 100 servers. This would typically be a manual activity, and Ansible has transformed how we handle this task. The particular mount point is shared across all 100 plus servers and added into /etc/fstab, which Ansible takes care of automatically.

Regarding my use cases for Ansible on CentOS 10, ad-hoc queries have greatly helped us because AI infrastructure is booming and many people are not completely aware of the entire AI infrastructure server ecosystem. This is where ad-hoc tasks become invaluable. When Nvidia develops their complete products, there are features we do not completely understand. Whenever there is a new issue, they ask us to execute new commands on all servers and provide results.

To execute a single command on all servers, we do not need to manually log in to all systems to execute commands and collect outputs. Instead, we use ad-hoc queries to customize what we want, including grepping particular answers, and receive only the expected output. This ad-hoc customization through Ansible really helps in our current day-to-day activities.

Ansible on CentOS 10 has positively impacted my organization significantly. Instead of onboarding multiple people for day-to-day operations, we have a junior team and mid-level team with very few resources. We initially thought that with increasing servers we would need to add more people, but Ansible has reduced that need as major operational tasks are now scheduled via Ansible. This has saved us considerable time, and the number of people we need to hire has also reduced. This is definitely a great advantage for our organization, as it has saved substantial costs.

I estimate that we have saved almost $10,000 per annum in operational costs.

The best features Ansible on CentOS 10 offers include being very easy to use because of the JSON format. Even non-programmers or engineers who do not know coding can easily learn and create playbooks. The second advantage is that it is agentless, requiring only SSH, which eliminates the need for manual effort to install and monitor agents. This avoids unnecessary troubleshooting and potential issues caused by agents, which is a major advantage I consider.

The agentless feature of Ansible on CentOS 10 has helped my team save time and avoid specific issues compared to other tools that require agents. This has reduced configuration time for multiple servers significantly because we do not need to access servers for agent configuration, nor do we need to monitor it. Troubleshooting is also minimized since unnecessary issues, such as agents consuming CPU and memory resources, are avoided. I have faced situations where some agents caused 100% CPU and memory consumption. To avoid these issues, it is better to adopt the agentless configuration that Ansible on CentOS 10 provides.

Regarding improvements for Ansible on CentOS 10, there are several modules we want to integrate, particularly those that are Red Hat-linked since both CentOS and Red Hat are similar. However, the integration for modules specifically meant for other operating systems that are not CentOS or Red Hat needs improvement.

Community support needs some improvements since not all of the data is available. This would be really helpful for organizations like ours that have newly implemented this, especially on CentOS 10. The documentation needs to be improved as well.

I have been using Ansible on CentOS 10 for almost four years, but I have used Ansible for around ten years.

Ansible on CentOS 10 is completely stable.

Ansible on CentOS 10 is very scalable. As we add thousands of servers, our Ansible setup can easily increase by enhancing resources for Ansible servers. We have not faced any issues regarding scalability so far.

Regarding customer support, I can say it is good but not great. The response time needs to be improved, but other than that, everything is perfectly fine.

I would rate the customer support on a scale of one to ten as a seven.

Previously, we used Terraform, but we switched to Ansible because it is more user-friendly, allowing everyone to learn it easily compared to Terraform, which had some difficulties.

The return on investment for Ansible on CentOS 10 is great. Compared to other applications or tools we have purchased recently, we have definitely seen a strong return on investment. Initially, we planned to hire a few experts exclusively for Ansible, needing at least $10,000 for two or three expert resources. However, existing team members learned it easily and completed implementation without needing additional resources. This saved significant costs.

Additionally, we negotiated costs related to licensing, saving us more money and time, allowing us to focus on new developments. There is definitely a good return on investment.

I have not been fully involved in pricing, setup cost, and licensing, but I do have some understanding of it.

Before choosing Ansible on CentOS 10, we did evaluate other options, specifically Terraform.

On a scale of one to ten, I would rate Ansible on CentOS 10 as a nine.

I chose nine out of ten for my rating mainly because of the user-friendliness. This user-friendliness is excellent, allowing anybody to use it. It is crucial that even those new to the organization can use it. Therefore, Ansible on CentOS 10 is excellent and very user-friendly.

Regarding Ansible on CentOS 10's AI capabilities, I think the governance and security are solid as we have not faced any issues so far. There are no known loopholes or bugs, but perhaps with longer usage, we might discover if there are any security vulnerabilities.

In terms of accuracy and reliability of output, I can say it is ninety percent accurate, but it still needs to meet one hundred percent accuracy.

My advice to others looking into using Ansible on CentOS 10 is to procure it. This definitely improves the quality for engineers working in infrastructure. You can automate a lot, which reduces manual effort and eases employee pressure. From a management perspective, costs also decrease in the long run. In both ways—employee and management—it is beneficial, so I definitely recommend purchasing and using it.

On-premises

My main use case for Ansible on CentOS 10 is automating OS administration tasks and scripting routines that I previously handled manually. I have automated all of these tasks with Ansible on CentOS 10.

A specific example of a task I have automated with Ansible on CentOS 10 is user administration, using the Ansible module for user administration.

Ansible on CentOS 10 has positively impacted my organization by optimizing my workflow. I have used it for administrative tasks, and it has smoothed my workflow and eased my administrative responsibilities.

It has optimized my workflow by providing significant time savings. Jobs that we previously delegated to various junior administrators are now handled by automated processes through Ansible. This addresses various user management tasks, such as revoking user access, creating accounts, and reinforcing security policies.

The best features Ansible on CentOS 10 offers are automation and platform independence, particularly when moving between Linux distributions.

Platform independence helps me in my work because it allows me to work on various distributions, as they are all flavors of Linux. Whether it is a Red Hat flavor or a CentOS flavor, I have the privilege of working with both. I can write code on CentOS 10 that works in RHEL as well, so this independence is significant for me. It also works with Ubuntu with some minor changes.

Regarding my use cases with Ansible on CentOS 10, I would like to see multiple modules added for network devices, which remains a challenge for most Ansible automation efforts. I would like to see support for multiple vendors in the networking category, including Cisco, Netgear, and Juniper. Windows automation is still limited with Ansible, and I would like to see the portfolio expanded in this area.

Regarding additional features of Ansible on CentOS 10, I would like to see how it evolves and whether it can include tools for monitoring such as Prometheus and Grafana for visualized performance monitoring. I would also appreciate integration with cloud platforms like AWS, integrated with AI in that Linux distribution.

Ansible on CentOS 10 can be improved by expanding the portfolio to include Prometheus or Grafana, with visualization-enabled graphical monitoring tools. Additionally, integrating products such as AWS or other cloud platforms along with AI features would be beneficial.

While documentation is generally adequate, there is always room for improvement. It could be made easier to read and enhanced with animations and examples of working scenarios, which I found to be missing in some areas.

I gave Ansible on CentOS 10 a rating of seven because I would like to see improvements and latest features incorporated. These are still missing from the Ansible portfolio, and it needs to be more user-friendly and expansive.

Regarding Ansible on CentOS 10's AI capabilities, I have not yet experimented with them, but I would like to see practical, working models that include support for the latest LLMs, along with the ability to change which LLMs we want to use, as we are currently limited to built-in options.

I have used Ansible on CentOS 10 for two years.

In my experience, Ansible on CentOS 10 is quite stable. I would like to see additional improvements, but it is not unstable.

Regarding customer support, we did not need to call for assistance.

Before Ansible on CentOS 10, I used Python and Bash scripting for task automation. Ansible on CentOS 10 has made that process significantly easier and has completely replaced those previous methods.

I have seen a return on investment with Ansible on CentOS 10 through time savings and a lower total cost of ownership.

My experience with pricing, setup cost, and licensing was positive.

I typically used RHEL and the Red Hat Ansible Automation Platform, which incorporates advanced AI-driven automation. This capability also extends to CentOS, so it works well.

I rate Ansible on CentOS 10 a seven.

I have not utilized AI with CentOS but have used it with RHEL 10's built-in features. Security-wise, it is good, but it is still something to be explored on the CentOS platform.

We deploy Ansible on CentOS 10 in my organization on-premises, typically in a test environment.

My advice for others looking into Ansible on CentOS 10 is to consider it for migrations between CentOS and RHEL, as it excels in that area. It includes a Convert to RHEL workflow, and you can use the Gen-AI assistant to build error-free playbooks, which is a valuable feature.

On-premises

My main use case for Ansible on CentOS 10 is to perform infrastructure automation.

A specific example of the kind of infrastructure automation I use Ansible on CentOS 10 for is provisioning nodes, patching, and many configuration management tasks, including the automation of SSSD.

I would like to add that the main advantage of Ansible on CentOS 10 is that it is easy to understand and easy to write playbooks. I can use Ansible Tower to build solutions and roles for provisioning nodes. It is very easy to identify idempotency.

Ansible on CentOS 10 has positively impacted my organization. It is very beneficial for our organization where we have many servers running CentOS 10, and we use Ansible to perform automation for patching and to push all configuration tasks using Ansible, including server configuration.

Since using Ansible on CentOS 10, I have seen it save significant time on many configuration tasks, obtaining information about servers, and provisioning nodes. Earlier, I did this manually using images or templates, but now using Ansible, I simply run a playbook and it creates a server, saving considerable time and providing a good solution.

Some valuable features that Ansible on CentOS 10 offers include its agentless architecture and its dependence on SSH. Without SSH, I am not able to use Ansible, so this is an important consideration.

I would like to add that it is a valuable capability to have Ansible for infrastructure automation. Through playbooks, I can add many idempotent tasks, and it is easy to execute tasks and obtain results. I can perform automation across many servers.

Ansible on CentOS 10 can be improved. Currently, I use it in an agentless manner, which works well.

I have been using Ansible on CentOS 10 for two years.

Ansible on CentOS 10 is very stable.

The scalability of Ansible on CentOS 10 is very good. I can perform many tasks, including increasing and decreasing file systems, and everything I use Ansible on CentOS 10 for works well.

Before using Ansible on CentOS 10, I managed these tasks manually and also used Puppet.

Before Ansible on CentOS 10, I used Puppet, and I have migrated to Ansible on CentOS 10 because it is a superior solution.

I have seen a return on investment. Ansible on CentOS 10 has saved considerable time, money, and resources.

My experience with pricing, setup cost, and licensing is that I spend more on Red Hat and CentOS regarding those areas.

On a scale of 1 to 10, I would rate Ansible on CentOS 10 a 10.

I rate it a 10 because I use both Puppet and Ansible, and I find Ansible more comfortable than Puppet. With Puppet, I need to write manifests and work with many modules. With Ansible on CentOS 10, it is easy to write playbooks and maintain idempotent roles with a good architecture that is easy to understand. That is the reason I am giving it a 10.

Regarding Ansible on CentOS 10's governance and security, I believe it is very secure because I use SSH. SSH itself is a secure shell, so it is a good solution, and I do not have to worry much about security.

I deploy Ansible on CentOS 10 in both on-premise and private cloud environments.

The private cloud provider I use is Microsoft Azure.

My advice to others looking into using Ansible on CentOS 10 is that I recommend it because Ansible on CentOS 10 is agentless, and it is easy to write Ansible playbooks. It is a good solution on CentOS 10, which is a very secure operating system supporting many technologies including microservices, Docker, and Kubernetes.

My main use case for Ansible on CentOS 10 is automating the platform, managing applications, and deployment, mostly on the infrastructure side of things.

For example, we have multiple servers that we want to patch. Traditionally, we would log into each server and patch each one individually.

Through Ansible on CentOS 10, we can execute a single command that automatically patches all server groups.

Ansible on CentOS 10 has impacted my organization positively by making infrastructure management very easy. In a traditional approach, we would need to log into each server to patch, upgrade, or install applications.

Now, through a single command, these tasks are installed across all servers.

I have seen specific outcomes such as time savings. Patching used to be an entire weekend activity before, and now it takes less than an hour to complete.

Ansible on CentOS 10 makes automating infrastructure very easy. Ansible has been around for a long time, making it a very stable product that is widely known. It is open source, so there is not a lot of cost associated with it.

Any complicated configuration can be easily done, especially those with SSH. The fact that it is agentless means you do not need to install any software or daemons on the managed nodes, which is a major reason we use Ansible on CentOS 10.

I rely on all of these features, though this server patching is not something we do every day. It happens whenever there is a major patch or update that needs to be installed.

The major features most important for us are the declarative syntax, which makes it very easy to define the ideal system state we want, and the agentless architecture. Ansible on CentOS 10 handles achieving that state on its own. These two features are the standout features for us.

Ansible on CentOS 10 is already a very stable product. One potential improvement could be allowing Windows systems to be used as a control node, though this is not very relevant to our use case.

It is very easy to install, especially on CentOS. Ansible on CentOS 10 now allows us to query cloud providers to fetch currently running instances and inventory, so it is already at a very good level.

I have been using Ansible on CentOS 10 for more than two years.

Ansible on CentOS 10 is stable.

Ansible on CentOS 10 is very scalable. You can scale it to thousands of instances if you want.

Previously, we were doing server management manually.

I have definitely seen a return on investment. As I mentioned before, it has saved a lot of time.

IT-side activities, especially patching servers or installing applications, used to take a lot of time, possibly an entire weekend. Now, we can schedule these tasks and leave them to run without spending significant time on them.

My experience with pricing, setup cost, and licensing is that it is very affordable, and I do not have any issues with that.

Before choosing Ansible on CentOS 10, we considered Terraform, but it does not provide the same functionality that Ansible on CentOS 10 does, so we see completely different use cases.

I rate Ansible on CentOS 10 a perfect ten out of ten because it performs the job that it needs to do.

I give it a ten because it is easy to work with and manage, especially because it is agentless and has a declarative syntax. You can ensure that a playbook can run multiple times with the same system state. Ansible on CentOS 10 does the job that we need it to do and is open source at a cost-effective rate, which gives it a ten out of ten.

My advice to others looking into using Ansible on CentOS 10 is that if your use case involves IT asset management, server management, infrastructure management, application management, or installing applications at scale, Ansible on CentOS 10 is the product for you. It can simplify these processes and save you a lot of money and time.

Public Cloud

Microsoft Azure