External reviews
External reviews are not included in the AWS star rating for the product.
Great core, but rough around the edges
What do you like best about the product?
Installing scheduled tasks in Rundeck, rather than individual servers, helps to centralize operations. Being able to develop forms to handle common IT tasks cuts down on our support volume - considerably, in some cases - and additionally provides an audit log. In all, it enables a greater level of transparency and access, and I'm a huge fan of the "IT self-service panel" concept.
What do you dislike about the product?
Rundeck's ACL system is powerful and granular but needlessly complex. It should be possible to assign or edit permissions using a graphical interface. There is currently no way to automatically clean out old job runs, so you either cobble something together yourself or let runs perpetually accumulate.
What problems is the product solving and how is that benefiting you?
I originally deployed Rundeck for use with my Ansible playbooks. At the time, Ansible Tower was a proprietary product without an open source equivalent. Over time, I found additional uses for it. For instance, I created a Project that lets our customer support agents add phone numbers to the phone system's blacklist without going through me.
After Red Hat acquired Ansible, it released AWX, an open source upstream for Ansible Tower, which I've begun using in place of Rundeck. AWX features deeper integration with Ansible playbooks, and the interface is, on the whole, a bit cleaner. There aren't quite so many options that I'll never use as there are with Rundeck. AWX is also written in Python, which I much prefer to Rundeck, which uses Java.
For me, AWX improves on Rundeck's annoyances enough that I plan to phase Rundeck out. However, for those who don't rely on Ansible so heavily, Rundeck is still a good product. There's nothing else quite like it - capable of running quite a lot, commercially sponsored, and open source.
But is it my first pick when given the choice of more specialized alternatives? No.
After Red Hat acquired Ansible, it released AWX, an open source upstream for Ansible Tower, which I've begun using in place of Rundeck. AWX features deeper integration with Ansible playbooks, and the interface is, on the whole, a bit cleaner. There aren't quite so many options that I'll never use as there are with Rundeck. AWX is also written in Python, which I much prefer to Rundeck, which uses Java.
For me, AWX improves on Rundeck's annoyances enough that I plan to phase Rundeck out. However, for those who don't rely on Ansible so heavily, Rundeck is still a good product. There's nothing else quite like it - capable of running quite a lot, commercially sponsored, and open source.
But is it my first pick when given the choice of more specialized alternatives? No.
Recommendations to others considering the product:
If you're trying to use Rundeck for a specific purpose, see if there's a purpose-built tool that you can use. Rundeck is a good general-purpose tool, but it may not be the best for very specific use cases.
- Leave a Comment |
- Mark review as helpful
Solves our tracking of scheduled tasks problem
What do you like best about the product?
I am able to build complex, or simple scheduled tasks that run and alert me when failed. I can then go back and view the point of failure and correct the problem when it fails.
What do you dislike about the product?
Had to custom build a module to work with http based tasks
What problems is the product solving and how is that benefiting you?
Scheduled task running. Automated reports, etc.
Recommendations to others considering the product:
Give it a try, it is well worth it!
Instant Admin Dashboard
What do you like best about the product?
We did not have time to build a full fledged administrative dashboard for our technical customer support team. We were able to utilize Run Deck as a method to execute one-off scripts on our production servers and provide privileged tier-based access to the customer support SMEs so that they can execute these scripts. This represented substantial savings in engineering cost as an engineer is no longer necessary to solve these support tickets.
What do you dislike about the product?
There doesn't seem an easy way to kill a script once it has started running.
What problems is the product solving and how is that benefiting you?
It's ability to allow us to execute scripts on the server-side and provide access to our customer support team.
RUNDECK - Self service for everyone
What do you like best about the product?
I like how easy it is to take my existing scripts and self service common tasks for non technical users.
What do you dislike about the product?
For windows the documentation feels a little like it might be outdated, setting up things like LDAP and SSL took a fair amount of effort.
What problems is the product solving and how is that benefiting you?
We are giving users the power to refresh there own environments without needing to know how it all works under the hood. Also scheduling refreshes of dev environments.
Recommendations to others considering the product:
Just try it, I suspect you won't look back.
Excellent and simple to deploy
What do you like best about the product?
The simplicity to schedule new workflow and the variety of plugins.
WE use it for ansible, Backup process and retention and to manage all the other operations before managed with crontabs
WE use it for ansible, Backup process and retention and to manage all the other operations before managed with crontabs
What do you dislike about the product?
The bad history manage options, you can't set the maximum age of jobs you want to keep. By this way, you 'll use a lot of stoarge on the DB's server and the Rundeck's server becuse of the logs.
What problems is the product solving and how is that benefiting you?
The scheduling of backup jobs, crontabs without control or error notification.
By this way we have semplified the control and updates of every job and process.
By this way we have semplified the control and updates of every job and process.
Very good managing system
What do you like best about the product?
The best is that you can run I command on multiple servers as different users and different sudo passwords. Amazing!
What do you dislike about the product?
Not too secure. Passwords stored in files, not database
What problems is the product solving and how is that benefiting you?
Much quicker to fix one issue on multiple server.
Swiss knife for sys admins
What do you like best about the product?
With Rundeck is very easy to automate and monitor repetitive task
What do you dislike about the product?
There are some settings that aren't available via web interface
What problems is the product solving and how is that benefiting you?
Automate task and manage them easily via web interface
Ease of use for jr admins
What do you like best about the product?
Open Source and highly configurable. We can make scripts for whatever we need.
What do you dislike about the product?
Interface could be better. As you see in my screen shot it is currently broken on chrome in macOS
What problems is the product solving and how is that benefiting you?
User creation in our environment
Recommendations to others considering the product:
Organize your scripts and make one script for every action so it is portable.
Rundeck has saved us a lot of time.
What do you like best about the product?
The self service part, it helps users automate tasks without coding knowledge.
What do you dislike about the product?
The UI can be a bit dated.It could use a refresh.
What problems is the product solving and how is that benefiting you?
Some times the nodes would lose connection
Great solution for on call
What do you like best about the product?
When it's 3:00 AM and you get paged to deal with some crazy issue, you don't want to worry about how to navigate through a clunky UI to access the information you need to remediate the problem. Pager Duty is very intuitive to use and has never gotten in the way of resolving an incident.
I've also had the pleasure of attending some conferences with talks by the Pager Duty team, and I think their own approach and commitment to product availability and resiliency is top notch. The worst thing this type of service could do is fail to page you when an actual incident is occurring; I'm quite confident that they're able to provide service when we need it.
I've also had the pleasure of attending some conferences with talks by the Pager Duty team, and I think their own approach and commitment to product availability and resiliency is top notch. The worst thing this type of service could do is fail to page you when an actual incident is occurring; I'm quite confident that they're able to provide service when we need it.
What do you dislike about the product?
For the nature of my on-call, I often need to take application level remediation rather than just infrastructure remediation. When reading the page of related alerts for a particular incident, I've basically written a few JavaScript scripts that I can run in the browser in order to pull data from the web page into a more structured format. I would love if there were instead an easy way to export structured incident information directly from the UI -- we're sending JSON over to their API, so we ought to be able to get it back out. There are times when it's easier for me to dig through out logs to grab this type of data, but that's even more of a pain. I'd love to be able to get incident and alert info in just one click instead.
What problems is the product solving and how is that benefiting you?
We use Pager Duty as our on call paging and incident management solution for our SaaS business. It helps us stay organized and recruit the right people to remediate incidents.
Recommendations to others considering the product:
Get developers on call with it. My primary role is in application development, but taking ownership for my product and being on call with it has been a fantastic growth experience.
showing 351 - 360