Micro Focus Operations Orchestration vs. Rundeck

The products are being paired by the company with different software to specifically fit multiple scenarios. As a standalone platform, it can answer any task with its build-in content or the ability to create your own content and solution.

Rundeck is a really good solution to formalize , standardize and automate your infrastructure operational run book. It can be also used in combination with your monitoring solution to auto heal your services. As for example when you get a specific alert, instead of triggering your notification channel to first trigger the Rundeck job to try and fix the issues (service restart etc..) and only then if the problem still persist to escalate and notify through an alert. It is also super handy to run all tasks from a central location and making sure there is no other person running the same job on the same servers at the same time, been able to see statistic about how fast or successful a job runs is also a big plus.

Incentivized

• Allows for the quick disconnection of accounts that break our terms of service
• Seamless integration with our billing system
• Has the ability to house all member/client account information in one single location

Incentivized

• The advantage is that it is extremely easy to lead and document because tasks can be managed in one place.
• As a consequence, there will be fewer crashes
• If you have trouble using crontab frequently, you should definitely use it.

Incentivized

• The product build in portal need to be more flexible

• Sudo privileges, this can be attained but it's not obvious when trying to build a job that needs to sudo up.
• Have a human time schedule instead of a linux cron schedule timer when creating jobs
• When calling a job from the API, the ability to pass back a result parameter that a job outputs, i.e., a job creates a job ticket reference and returns the reference, the API call will just return if the job fired correctly and not the ticket reference. Getting the ticket reference needs some engineering to attain; for example, you may need to write it to a file, then another job read that file to find out what it is.
• It would be very nice to just be able to fire off the job on the API. The API sits and waits for the return and gets back any outputted data in the one call. I know it's an API, but it would be nice to have the option to sit and wait for the result.

Incentivized

Most product works well enough, but none of them combine the non-agent/client approach to automation with an easy to develop mechanism (the drag&drop development approach) This alone put this solution on top of our preferred implantation product list

Ansible Tower (or AWX) is very poor in comparison to Rundeck and only runs well Ansible talks versus Rundeck can support all kind of scripts and tools. Rundeck UI is much more intuitive and robust

Incentivized

• If time is money, the time saved by using this all-in-one product has certainly saved time AND money.

Incentivized

• Business logic can now run on time.
• In Cron, error management and error reporting skills are required, but the introduction of Rundeck has eliminated personality.
• It is a centrally managed job management system.

Incentivized