Ansible on CentOS 10 Hardened
Automation has simplified patching and consistently cuts production time by over half
What is our primary use case?
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.
How has it helped 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.
What is most valuable?
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.
What needs improvement?
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.
What other advice do I have?
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.
Automation has reduced configuration drift and now delivers faster, error-free remediation
What is our primary use case?
My main use case for Ansible on CentOS 10 includes configuration drift detection and remediation, configuration management with idempotency, and patching and vulnerability remediation.
I typically implement drift detection or vulnerability remediation with Ansible on CentOS 10 using Ansible playbooks that have playbooks and roles, running daily scheduled jobs through Ansible AWX. If there is any drift detected, such as in the `/etc/ssh/sshd_config` file, it will automatically remediate on the particular server.
I also use Ansible on CentOS 10 for hardening.
How has it helped my organization?
Ansible on CentOS 10 has positively impacted my organization by enabling configuration management, drift detection, patching, and vulnerability remediation. It has reduced the time to implement and secure Linux servers, as well as to implement vulnerability remediation, patching, and configuration management as required.
I have seen specific outcomes such as time saved and no errors once implemented.
What is most valuable?
Ansible on CentOS 10 offers valuable features including that CentOS ships with foundational runtime software, specifically Python 3.9.12 and GCC 14.12. Since Ansible is built on Python, this native inclusion means that the operating system natively fulfills all environment requirements for running configuration management tasks.
The main feature of Ansible on CentOS 10 is idempotency when using the Ansible built-in modules, which is excellent.
What needs improvement?
I do not find any improvement areas for Ansible on CentOS 10. I have not found anything that could be improved or added to make Ansible on CentOS 10 even better to date.
For how long have I used the solution?
I have been using Ansible on CentOS 10 for hardly one year because CentOS is a recently released distribution.
What do I think about the stability of the solution?
Ansible on CentOS 10 is stable.
What do I think about the scalability of the solution?
Ansible on CentOS 10's scalability is good, allowing me to scale to a large number of servers.
How are customer service and support?
I never needed any customer support for Ansible. I resolved issues from internet resources.
Which solution did I use previously and why did I switch?
Before using Ansible on CentOS 10, I was using BMC TrueSight Server Automation, and I switched due to the high licensing cost and longer time taken for deploying patches.
What was our ROI?
I have seen a return on investment with time saved and money saved, as the licensing part is one aspect I can optimize since Ansible AWX is open source. With fewer employees, I can manage depending upon the number of configuration items.
Which other solutions did I evaluate?
Before choosing Ansible on CentOS 10, I evaluated other options and found Ansible to be the best one.
What other advice do I have?
On a scale of one to ten, I rate Ansible on CentOS 10 a ten. I chose ten as my rating because I did not find any issues with Ansible on CentOS 10.
Regarding Ansible on CentOS 10's AI capabilities, I think for governance and security, if you implement the hardening part and patch the servers regularly while remediating vulnerabilities once identified, then it is suitable. Otherwise, you should choose Red Hat Enterprise Linux servers for enterprise-grade support and vendor patches.
Ansible on CentOS 10 is deployed in my organization in the public cloud. I use mostly Azure, GCP, and AWS as my cloud providers.
My advice for others looking into using Ansible on CentOS 10 is that it is the best choice.
Automation has transformed patching and AI infrastructure tasks while reducing operational effort
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Ansible on CentOS 10 for almost four years, but I have used Ansible for around ten years.
What do I think about the stability of the solution?
Ansible on CentOS 10 is completely stable.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
I have not been fully involved in pricing, setup cost, and licensing, but I do have some understanding of it.
Which other solutions did I evaluate?
Before choosing Ansible on CentOS 10, we did evaluate other options, specifically Terraform.
What other advice do I have?
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.
Automation has transformed incident resolution and now drives consistent, hands‑off operations
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
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.
What do I think about the stability of the solution?
I have experienced stability issues.
What do I think about the scalability of the solution?
Scalability is good. I am running Ansible on CentOS 10 on EKS, and it performs well.
How are customer service and support?
Customer service is good.
Which solution did I use previously and why did I switch?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
I purchased Ansible on CentOS 10 through Red Hat. At an enterprise level, the cost is acceptable.
Which other solutions did I evaluate?
I evaluated Terraform as an alternative solution.
What other advice do I have?
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.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Automation has transformed routine patching and user administration into a one-admin workflow
What is our primary use case?
My main use case for Ansible on CentOS 10 is automation. I automate any given task and anything I want to automate.
A specific example of something I've automated using Ansible on CentOS 10 includes tasks related to my own workflows, specifically for my own services.
When it comes to one of those tasks that Ansible helps with regularly, I focus on patching and updating, specifically updating. The video tasks involve scheduling based on some date, and Ansible has made them easier in that aspect.
I use Ansible on CentOS 10 to get containers, meet parts, and then patch them. I use it specifically for patching.
What is most valuable?
In my opinion, the best features Ansible on CentOS 10 offers include automating user administration tasks, patching tasks, and overall automation.
Definitely for patching is the feature I find most helpful or time-saving because I have to update my servers frequently.
Ansible on CentOS 10 has positively impacted my organization as our servers are up-to-date, they are less vulnerable, and without vulnerability.
I can definitely say that Ansible on CentOS 10 has saved a considerable amount of time and effort for me and my team, as a job that used to be done by ten admins can now be done by only one admin.
What needs improvement?
Regarding improvements for Ansible on CentOS 10, I don't think any improvement is required.
If I would like to add more about the needed improvements, it would be that if the UI can be easier and dynamic inventories could be more advanced.
For how long have I used the solution?
I have been using Ansible on CentOS 10 for the last six years, but on CentOS 10, I have been using it for a couple of years.
What do I think about the stability of the solution?
Ansible on CentOS 10 is stable.
What do I think about the scalability of the solution?
The scalability of Ansible on CentOS 10 is as much as you want, as it is highly scalable.
How are customer service and support?
When it comes to customer support, it's Red Hat, so you can imagine the support; it's the best you could get.
I would rate the customer support for Ansible on CentOS 10 a strong 10.
Which solution did I use previously and why did I switch?
Previously, I did use a different solution, scripting, but I found that scripting is imperative, and I needed something easy and fast, which was Ansible on CentOS 10.
What was our ROI?
I have definitely seen a return on investment with fewer employees, money saved, and time saved.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is positive since I use the open-source version, which means it's free.
Which other solutions did I evaluate?
Before choosing Ansible on CentOS 10, I evaluated other options like Chef and Puppet, but eventually, Ansible on CentOS 10 is the best.
What other advice do I have?
On a scale of one to ten, I would rate Ansible on CentOS 10 a solid ten.
I choose ten out of ten because it's the best for automation.
Regarding Ansible on CentOS 10's AI capabilities, I think it doesn't have anything like AI capability; it's just automation.
When I think of Ansible on CentOS 10's accuracy, I can confirm that it does not have AI capabilities.
My advice for others looking into using Ansible on CentOS 10 is simple: if you're looking for automation, just go for it, don't think twice.
Automation has streamlined user administration and workflow but still needs richer network and AI support
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have used Ansible on CentOS 10 for two years.
What do I think about the stability of the solution?
In my experience, Ansible on CentOS 10 is quite stable. I would like to see additional improvements, but it is not unstable.
How are customer service and support?
Regarding customer support, we did not need to call for assistance.
Which solution did I use previously and why did I switch?
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.
What was our ROI?
I have seen a return on investment with Ansible on CentOS 10 through time savings and a lower total cost of ownership.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing was positive.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Automation has transformed server provisioning, patching, and configuration into fast repeatable tasks
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
Ansible on CentOS 10 can be improved. Currently, I use it in an agentless manner, which works well.
For how long have I used the solution?
I have been using Ansible on CentOS 10 for two years.
What do I think about the stability of the solution?
Ansible on CentOS 10 is very stable.
What do I think about the scalability of the solution?
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.
Which solution did I use previously and why did I switch?
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.
What was our ROI?
I have seen a return on investment. Ansible on CentOS 10 has saved considerable time, money, and resources.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is that I spend more on Red Hat and CentOS regarding those areas.
What other advice do I have?
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.
Automation has improved secure banking configurations but still needs better governance controls
What is our primary use case?
Ansible on CentOS 10 is primarily used for configuration management, particularly managing menus, nested menus, and configurations.
In one of my major projects, I used Ansible on CentOS 10 for automated server configuration management across multiple CentOS environments, where I maintained nested configurations using Ansible roles, group variables, and host variables.
In banking, my main use case for Ansible revolves around automating infrastructure configurations and application deployment across different environments.
What is most valuable?
Ansible on CentOS 10 includes several useful features designed for enterprise DevOps, specifically in banking.
I find the modern security technology to be the most valuable feature of Ansible on CentOS 10 in my day-to-day work, especially for banking applications due to the critical nature of security and compliance.
Before implementing Ansible automation on CentOS 10, my team and I used to handle many server configurations manually, which was time-consuming and led to configuration inconsistencies. After introducing Ansible, we significantly improved our workflows.
After implementing Ansible on CentOS 10, we are able to standardize and simplify many operational processes, particularly in improving security.
I have observed time savings due to the automation of repetitive tasks, which has minimized manual configuration mistakes and improved deployment speed since adopting Ansible on CentOS 10.
What needs improvement?
Ansible on CentOS 10 can be improved by focusing on enhancing automation, efficiencies, and security for better infrastructure management.
For how long have I used the solution?
I have been using Ansible on CentOS 10 for more than four years.
What do I think about the stability of the solution?
Ansible on CentOS 10 seems to be stable, providing a reliable combination of configuration management.
What do I think about the scalability of the solution?
Ansible on CentOS 10 includes agentless architectures, parallel executions, dynamic instances, and rolling updates that support scalability.
How are customer service and support?
In my experience, the customer support has been good.
I would rate customer support with a score of 8 out of 10 based on documentation and community support.
Which solution did I use previously and why did I switch?
Before adopting Ansible, I relied more on manual service administration and script-based automations, facing challenges with human efforts and configuration drift.
What was our ROI?
For the banking projects, I have explained the ROI by reducing operational costs and saving time through Ansible automation.
What's my experience with pricing, setup cost, and licensing?
Regarding pricing, I don't have much knowledge about setup costs and licensing, but I do know that AWS operates on a pay-as-you-go model.
Which other solutions did I evaluate?
I explored various options before choosing Ansible, including Puppet and Chef.
What other advice do I have?
In terms of governance and security regarding Ansible on CentOS 10, I am not fully aware, but I consider data privacy, human approvals, access controls, and secret management to be important.
For the accuracy and reliability of output concerning Ansible on CentOS 10, my approach involves human reviews, monitoring, and continuous auditing.
Ansible on CentOS 10 is deployed in my organization using the public cloud.
My organization uses various cloud providers, including AWS, DigitalOcean, NPT, Oracle, IBM, and VMware.
My advice for anyone planning to use Ansible on CentOS 10 is to start with a clear automation strategy and gradually learn the basics.
Configuration automation has unified hybrid deployments and reduces infrastructure costs
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have used Ansible on CentOS 10 for close to three to four years.
What do I think about the stability of the solution?
Ansible on CentOS 10 is very stable for me. Earlier versions worked great, and the latest version continues to meet my needs effectively.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Automated patching and deployments have transformed how our team manages infrastructure at scale
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Ansible on CentOS 10 for more than two years.
What do I think about the stability of the solution?
Ansible on CentOS 10 is stable.
What do I think about the scalability of the solution?
Ansible on CentOS 10 is very scalable. You can scale it to thousands of instances if you want.
Which solution did I use previously and why did I switch?
Previously, we were doing server management manually.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is that it is very affordable, and I do not have any issues with that.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.