Red Hat Ansible Automation Platform vs. Rocket DevOps

It has helped save us so much time, as it was designed to automate mundane and repetitive tasks that we were using other tools to perform and that required so much manual intervention. It does not work very well within Windows environments, understandably, but I would love to see more integration. I want it to be sexy and attractive to more than just geeky sysadmins.

Incentivized

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.

Incentivized

• Debugging is easy, as it tells you exactly within your job where the job failed, even when jumping around several playbooks.
• Ansible seems to integrate with everything, and the community is big enough that if you are unsure how to approach converting a process into a playbook, you can usually find something similar to what you are trying to do.
• Security in AAP seems to be pretty straightforward. Easy to organize and identify who has what permissions or can only see the content based on the organization they belong to.

Incentivized

• Allows flexibility for user groups
• Scripting for releasing of code
• Ease of comparing code versions within the tool

Incentivized

• YAML is hard for many to adopt. Moving to a system that is not as white space sensitive would likely increase uptake.
• AAP and EDA should be more closely aligned. There are differences that can trip users of the integration up. An example would be the way that variables are used.
• Event-driven Ansible output is not as informative as AAP.

Incentivized

• SQL object promotions
• User interface
• Incomplete error checking
• Fragmented promotion logs

Incentivized

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.

Incentivized

Based on current integration with our release process, we will need to keep this for the future.

Incentivized

the yaml is easy to write and most people can be taught to write basic playbooks in a few weeks

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

I spoke on this topic today!

Incentivized

I haven't thought of any right now other than just doing our own home-brewed shell scripts. Command line scripts. And how does this compare? It's light years ahead, especially with the ability to share credentials without giving the person the actual credentials. You can delegate that within, I guess what used to be called Ansible Tower, which is now the Ansible Automation platform. It lets you share, I can give you the keys without you being able to see the keys. It's great

Incentivized

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

Incentivized

• Red Hat Ansible Automation Platform offers automation and ML tools that allow me to automate complex IT tasks.
• Through automation analytics, it is seamless to gain full visibility into automation performance allowing me to make informed decisions.
• Red Hat Ansible Automation Platform allows me to move rapidly from insights to action.
• Creating and sharing automation content in one place unify a team in one place hence enhancing real-time collaboration.

• Software promotion is much easier and doesn't require custom coding.
• Developers can work collaboratively with less overlap.
• Developers can find objects faster and research code more thoroughly.

Incentivized