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
Rocket DevOps
Score 10.0 out of 10
N/A
Rocket DevOps (formerly Rocket Aldon) enables true end-to-end (CI/CD) for IBM i+ environments. Businesses can extend holistic DevSecOps best practices to the IBM i, pursue innovative experimentation, easily respond to compliance audits, and adapt to the ever-changing expectations of process, technology, or experience.
Red Hat Ansible automates server management, configuration updates, and deployments across our server infrastructure, keeping everything consistent, reducing human error, and saving time. Also provides detailed reports on what is done and uses role-based access controls to keep systems secure by controlling who can make changes.
Rocket Aldon is perfect for simple changes to traditional IBM i development using RPGLE, CL, and DDS. It is great for finding related objects that are referenced in many locations and helping recompile all of these objects. However, Aldon has a particularly hard time with SQL views. For some reason, it is determined to lock every table related to a view even though this is not required by the operating system. Whenever one view references another view, you are always in danger of losing a view permanently if you didn't check it out and promote it. To clarify, imagine you created a view CUSTOMER_INFO. Then you make another view called CUSTOMER_SHIPMENTS that joins the CUSTOMER_INFO to a shipping table. If you ever change CUSTOMER_INFO and then promote it, there is a good chance that Aldon will delete the CUSTOMER_SHIPMENTS view and you will not get a single warning. It doesn't happen every time but when it does you are going to have a real mess on your hands.
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.
It's overall pretty easy to use foe all the applications I've mentioned before: configuring hosts, installing packages through tools like apt, applying yaml, making changes across wide groups of hosts, etc. Its not a 10 because of the inconveinience of the yaml setup, and the time to write is not worth it for something applied one time to only a few hosts
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.
Support is hit and miss. Sometimes they give some great assistance and sometimes they are no help at all. It always seems like they can't replicate the problem but then they never try to get on our system to do deeper research. It's kind of frustrating dealing with them. Also, the website isn't that 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.
Aldon provides needed functions for our current implementations and legacy systems. As we move toward modernization, we are going to look at alternatives from reviewing cost, integration capabilities and functionality
POSITIVE: currently used by the IT department and some others, but we want others to use it.
NEGATIVE: We need less technical output for the non-technical. It should be controllable or a setting within playbooks. We also need more graphical responses (non-technical).
POSITIVE: Always being updated and expanded (CaC, EDA, Policy as Code, execution environments, AI, etc..)