Nomad VS Rundeck

While I do understand the reasoning in their FAQ on the subject (https://www.hashicorp.com/license-faq). I however failed to noticed those intentions in their license text (https://github.com/hashicorp/nomad/commit/b3e30b1dfa185d9437...).

Specifically the part in FAQ which says "internal production use is fine", but then license says that "non-production use only" and then "You may make production use of the Licensed Work, provided such use does not include offering the Licensed Work to third parties on a hosted or embedded basis which is competitive with HashiCorp's products.".

IANAL, but even to me this statement is full loopholes. WHO do we consider 3rd party? WHAT do we consider "hosted or embedded basis"? WHEN do we consider it "competitive with Hashicorps products"?

You'll probably want to take https://www.nomadproject.io/ and layer it on top of jails with pot:

Nomad[1] is one alternative that gives you the same infra-as-code warm and fuzzies but isn't a behemoth like k8s. It's simple to deploy, simple to operate and unless you're truly scaling big, it probably does everything you need.

I'm sure there are others in the same league that I don't know about. Maybe I'm just getting old but I'll never understand the rush to use k8s in teams of <100 developers.

[1] https://www.nomadproject.io/

Hashicorp Nomad? I ran it across a bunch of raspberry pis and proxmox VMs/LXCs. Being a Hashicorp product it plays well with Terraform. The only reason I swapped it out for k3s was upskilling for work.

[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.

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