Rundeck VS Nomad

Have a look at rundeck.org

Firstly, I tried Rundeck and Apache Airflow. They are complete overkill for what I want to do. Then I found Cronicle which is light enough, besides it can pull double duty as a general purpose scheduler.

Yesterday we posted a Security Advisory to Github for a critical vulnerability in Rundeck Community and Rundeck Enterprise Docker images, versions 4.0 and earlier. Those Docker images contained a pre-generated SSH key pair in the default file path. If that key was used to configure SSH access to hosts, they would allow access to anyone with the exposed private key.

Never used it myself (we're currently working on deploying Tower) but I've heard that Rundeck is the goto for your exact use case: "Tower, but less heavy". I looked at it when evaluating for my current job and it looks like a good middle of the road solution and looks way easier to deploy than AWX. The tradeoff is that since it's not custom built for Ansible you can automate lots of other things with it (like just bash scripts and the like) but you get less of the Ansible-specific integrations and tooling that Tower offers.

Hi! This fix solves the bug, is ready to be included in the next release. Regards.

There is already an open GitHub issue on this, but I wanted to mention it here as it can cause some nasty surprises for those unaware.

Compare to rundeck after they were acquired by Pagerduty

https://github.com/rundeck/rundeck/graphs/contributors

[Nomad]

Lob’s core API has been fully migrated to HashiCorp's Nomad, Lob’s Next Generation service platform. This is a major milestone for the Nomad Project, the Platform Team, and Lob Engineering. This migration is the culmination of a year of R&D, months of practice migrating other Lob services, and weeks of work on this particular service. It’s absolutely worth celebrating for the complexity and customer impact.

Most of our API’s migration to Nomad happened in August, but the key feature of autoscaling was not working as expected. This turned out to be a bug in Nomad which James Douglas tracked down. The issue was recently fixed and autoscaling works as expected, completing the migration!

Nomad by HashiCorp

There's also https://pot.pizzamig.dev/ which even has a Nomad(https://www.nomadproject.io/) driver in case you want to "orchestrate" the jails(as in deploy many jails at the same time across multiple servers)

The check stanza runs a health check on the service Since the service is registered to Consul, the health check runs on Consul. The above health check is configured to run every 10 seconds, and is given 5 seconds for the health check query to succeed. Health checks in Nomad are similar to Kubernetes health checks.

Not sure if it fits here, and might be a little more complex than what you’re looking for, but Nomad is definitely worth a look.

I'd like to also mention hashicorp nomad + consul. They're worth evaluating.

Hashicorp Nomad

We had a hard time finding this data when experimenting with carbon aware scheduling in Nomad. There seem to be a lot of orgs working on this, but it’s all third party as far as I know. I couldn’t find a first party (eg Amazon, Microsoft, Google, etc) that provided this data via an API. Very frustrating.

There are a couple resources linked here: https://github.com/hashicorp/nomad/blob/h-carbon-meta/CARBON...

The silver lining is that the folks who are working in this space are extremely friendly and passionate in my experience. Don’t be scared to “contact sales for an API let.” The few folks I talked to were extremely helpful.