nomad

I can't discern how many are just those "dependabot" bumps but the 1400 forks show some are active https://github.com/hashicorp/nomad/forks?include=active&page... including CircleCI who I would think have a stake in a libre Nomad https://github.com/circleci/nomad/tree/circleci/release-1.5.... Now maybe their goals don't align with the community, and/or they don't want to be in the maintainer business for such a project, but better than nothing

We're using Nomad, and appreciate its comparative simplicity (we launch plain binaries created with Nix), but there are still basic features missing that can create struggles. The ones I hit are: * It can't work down batch jobs in priority order [1] -- a feature even the ultra-old university cluster schedulers had * Sometimes job starts can be in arbitrary order, in the API and the UI, making it difficult to find the most recent ones [2] * Nomad seems to store pretty much everything in its Raft state, making it extremely slow to startup and operate (including GUI) if some rogue process created 100k allocations. Cleaning that up seems to require nuking the Raft state, thus also losing all info about all jobs. I don't know how well Kubernetes does in these areas. [1]: https://github.com/hashicorp/nomad/issues/12792 [2]: https://github.com/h

Yes k8s does not provide a out-of-box logging collection solution but since everything is in containers, we can piggyback on Docker or Containerd via deamonset to get all the logs. Nomad on the other hand support various payload(native exec, exec via chroot, containers, even Firecracker VM by community support), so doing logging collection by end users is trickier. It worth noting that Nomad UI(a official web admin panel) has log tailing utility built-in so maybe partial work has already been done. The developers may have other concerns. The related issue is https://github.com/hashicorp/nomad/issues/10220

Nomad, along with the rest of Hashicorp's flagship products, transitioned to the BUSL-1.1: https://github.com/hashicorp/nomad/blob/main/LICENSE

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"?

I guess it's too early to quote the "RTFM", because the step-by-step tutorial is in another pull request that contributors need to raise against the main Nomad repository so that the website can show the steps. Nevertheless, the "examples" directory has the agent configuration and the example Nomad job file you'll need to deploy onto the server. Let me know if that helps. The PR which would ultimately make the tutorial accessible to all: https://github.com/hashicorp/nomad/pull/17580