Open source Puppet provides tools to automate the configuration and management of IT infrastructure. It is supported by a community of users and contributors. Users can get involved by fixing bugs, influencing new feature direction, publishing modules, and engage with the community to share knowledge and expertise.
N/A
Ansible
Score 9.2 out of 10
N/A
The Red Hat Ansible Automation Platform (acquired by Red Hat in 2015) is a foundation for building and operating automation across an organization. The platform includes tools needed to implement enterprise-wide automation, and can automate resource provisioning, and IT environments and configuration of systems and devices. It can be used in a CI/CD process to provision the target environment and to then deploy the application on it.
$5,000
per year
VMware Cloud Foundation
Score 9.0 out of 10
N/A
VMware Cloud Foundation is a hybrid cloud platform for managing VMs and orchestrating containers, built on full-stack hyperconverged infrastructure (HCI) technology. With a single architecture that is desribed by the vendor as easy to deploy, VMware Cloud Foundation aims to enable consistent, secure infrastructure and operations across private and public cloud.
As I said earlier, Red Hat Ansible remains a top choice because it is a perfect combination of multiple capabilities. Terraform is good in IAC but not in config automation. Puppet is well-suited for developers, but not for system administrators and infrastructure integrators. …
Puppet is more constant state management for us than Red Hat Ansible Automation Platform is, Red Hat Ansible Automation Platform is a more one off configuration then we transfer over to a pupper configuration for steady state.
I used puppet prior to moving to open source Ansible and eventually to Red Hat Ansible Automation Platform. I appreciate the agentless approach of Red Hat Ansible Automation Platform and feel that its deterministic approach to applying code is superior to puppet
Ease of use, once you understand how to configure the tool, everything is a piece of cake. It runs pretty fast also, can use GITLab to manage our playbooks. Security options is great, can setup granular security depending on each team using Red Hat Ansible Automation …
There's 0 comparison. Red Hat Ansible Automation Platform leaves them in the dust. It is easier to configure and wipe playbooks for, and has way more community support and documentation making it a no brainer.
Red Hat Ansible Automation Platform requires little to no configuration on the nodes to manage the systems. However, this means that the inventory source of Truth must come from somewhere else. Red Hat Ansible Automation Platform is able to manage things beyond typical nodes …
AAP doesn't truly stack up against any of the products mentioned except for Aria Automation. But, it is extensible and open and has a lower cost to entry.
Red Hat Ansible Automation Platform is much easier to setup than Puppet, because it is agentless. The Ansible community seems to be more active than Puppet's in the recent years. Red Hat Ansible Automation Platform does not require learning a programming language where Puppet …
Integration with CyberArk is not comfortable at this moment, but we are trying to make it work. If it works, it'll be more helpful to us. Integration with CyberArk, like the wall, takes the password automatically from there and executes certain things in a secure and beneficial way. Once we have the playbooks and the inventory, we can run many services under one charge. That's more advantageous.
It is best suited for an on-premise cloud solution where customer can shift their entire production environment. Also, the customer has a preference for a Homogenous Infrastructure Environment where budget is not a challenge. It is not at all suited for a Heterogenous Environment, e.g., a Public cloud where integration becomes a huge issue, also in SMB sections where budget is challenging.
It reduces custom scripting efforts because everything can be scripted in simple, human-readable YAML playbooks.
Not only servers, but also network devices, VMs, Containers, Kubernetes clusters, etc., can be automated via Ansible, showcasing its extensive list of supported devices.
It is agentless, which makes it lightweight and allows for easy integration into CI/CD and GitOps pipelines.
Many Tier-1 telcos use Ansible for Day 0/1/2 automation of RAN, transport, and core infrastructure (e.g., network function lifecycle management, NE configuration push, patching VNFs).
I can't think of any right now because I've heard about the Lightspeed and I'm really excited about that. Ansible has been really solid for us. We haven't had any issues. Maybe the upgrade process, but other than that, as coming from a user, it's awesome.
Even is if it's a great tool, we are looking to renew our licence for our production servers only. The product is very expensive to use, so we might look for a cheaper solution for our non-production servers. One of the solution we are looking, is AWX, free, and similar to AAP. This is be perfect for our non-production servers.
Overall, the product is excellent, with daily-use features for both large and small infrastructure. Ansible does its job quickly and ensures compliance, keeping the environment up to date and safe from open vulnerabilities. Large-scale inventory management and license management. Industry standard followed by best practices to maintain continuity. Budget-friendly compared to other products.
Great in almost every way compared to any other configuration management software. The only thing I wish for is python3 support. Other than that, YAML is much improved compared to the Ruby of Chef. The agentless nature is incredibly convenient for managing systems quickly, and if a member of your term has no terminal experience whatsoever they can still use the UI.
There is a lot of good documentation that Ansible and Red Hat provide which should help get someone started with making Ansible useful. But once you get to more complicated scenarios, you will benefit from learning from others. I have not used Red Hat support for work with Ansible, but many of the online resources are helpful.
AAP compares favorably with Terraform and Power Automate. I don't have much experience with Terraform, but I find AAP and Ansible easier to use as well as having more capabilities. Power Platform is also an excellent automation tool that is user friendly but I feel that Ansible has more compatibility with a variety of technologies.
Although the public Cloud Model follows Opex Costing Model, it actually leads to very high costs also, the infra model in my organization is not suited for a Public Cloud Model. Hence We decided on an On-Premise Model, and the best suited was VMware Cloud Foundation, which is a complete Software-Defined Scale-Out Architecture. I also prefer a Homogenous environment; i.e, support and services from a Single OEM, so that I Can get faster resolutions to my tickets raised.
First, it keeps our entire server infrastructure aligned with our standards and reduces the time and effort needed to maintain our systems.
Automate routine IT tasks to save time, reduce errors, and ensure every server is configured and updated consistently.
Tasks that used to take our teams weeks to complete manually now run automatically and reliably, with full visibility, making our infrastructure management more effective and our compliance tracking much easier.
My organization has a size of 1300+ employees, using multiple applications and an exchange mail server that is hosted on On-Premise Cloud, hence scalability has not been a challenge.
Having hosted my Production environment and Mail exchange Server on VCF, there has been optimum resource utilization with very little scope downtime. Hence have been able to save a lot of funds on Hardware resources.
Due to the size of my organization and due the data load, I have been able to save on Resource Utilization and Organization Funds