Rundeck VS Nomad

Compare to rundeck after they were acquired by Pagerduty

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

Hi! That's reported here, please add your use case.

Strangely enough, when putting 0d in the conguration file, the WebUI field is pre-filled with 0.

Anyway, you can suggest that here :-)

Hello, currently that's not configurable, you can suggest it here. Regards.

Hi! If you decide to call the API from the inline-script step, consider creating a specific plugin for that. Take a look at this and this basic example.

Reproduced here. Thanks for your feedback!

You can use regex expressions on -match: name: blocks, for example, project.*, check this another example (focused on jobs) I think that is what you're looking for.

its an orchestration tool similar to something like K8S https://www.nomadproject.io/

That does seem better! Of course, there are a few lingering issues with support, but overall the trend is good: https://github.com/containers/podman/issues?q=is%3Aissue+is%...

Of course, there's no Swarm support, as evidenced by that very article:

> Caveats

> One known caveat is that Podman has not and will not implement the Swarm function. Therefore, if your Docker Compose instance uses Swarm, it will not work with Podman.

Feels like people will either be pigeonholed into Kubernetes for all of their deployments, or will have to migrate over to something like Hashicorp Nomad: https://www.nomadproject.io/

Curiously, it also supports Podman as a task driver: https://www.nomadproject.io/docs/drivers/podman

I'm not sure I understand the situation here, but for something like running one-off / batch jobs across nodes, that sounds like something nomad should cover, or maybe Ansible depending on what you need.

why don't you consider nomad[0] in your evaluations. i think it should fit your requirement.

[0] - https://www.nomadproject.io

Searching for a solution I found this issue in the repo: Support Linux images in Docker for Windows

or just run nomad? It works from a single node up. https://www.nomadproject.io/

> There is gap in the market between VM oriented simple deployments and kubernetes based setup.

In my experience, there are actually two platforms that do this pretty well.

First, there's Docker Swarm ( https://docs.docker.com/engine/swarm/ ) - it comes preinstalled with Docker, can handle either single machine deployments or clusters, even multi-master deployments. Furthermore, it just adds a few values to Docker Compose YAML format ( https://docs.docker.com/compose/compose-file/compose-file-v3... ) , so it's incredibly easy to launch containers with it. And there are lovely web interfaces, such as Portainer ( https://www.portainer.io/ ) or Swarmpit ( https://swarmpit.io/ ) for simpler management.

Secondly, there's also Hashicorp Nomad ( https://www.nomadproject.io/ ) - it's a single executable package, which allows similar setups to Docker Swarm, integrates nicely with service meshes like Consul ( https://www.consul.io/ ), and also allows non-containerized deployments to be managed, such as Java applications and others ( https://www.nomadproject.io/docs/drivers ). The only serious downsides is having to use the HCL DSL ( https://github.com/hashicorp/hcl ) and their web UI being read only in the last versions that i checked.

There are also some other tools, like CapRover ( https://caprover.com/ ) available, but many of those use Docker Swarm under the hood and i personally haven't used them. Of course, if you still want Kubernetes but implemented in a slightly simpler way, then there's also the Rancher K3s project ( https://k3s.io/ ) which packages the core of Kubernetes into a smaller executable and uses SQLite by default for storage, if i recall correctly. I've used it briefly and the resource usage was indeed far more reasonable than that of full Kubernetes clusters (like RKE).

The renders would take place inside of docker containers. I needed ffmpeg and packages like texlive-latex-extra for hiragana (ひらがな）and katakana (カタカナ). I got the entrypoint to accept a reference character along with my scene name and the batch processing came soon after. I noticed that in the time it'd take for a production render to complete, I could prepare the data for the next 2-5 episodes (and that only one CPU ever ran hot while the rest snoozed). So I started a nomad sandbox and used parameterized jobs execute 16 concurrent renders while I slept.

`IntroScene(SoundScene)` wrapped the main `construct` method to include a common first and last scene for my title and credits, with any subclass content in between. These bookends would be disabled during development renders, letting me move fast (dev builds were 720 @ 10fps). The renders would take place inside of docker containers. I needed `ffmpeg` and packages like `texlive-latex-extra` for hiragana (ひらがな）and katakana (カタカナ). I got the entrypoint to accept a reference character along with my scene name and the batch processing came soon after. I noticed that in the time it'd take for a production render to complete, I could prepare the data for the next 2-5 episodes (and that only one CPU ever ran hot while the rest snoozed). So I started a [nomad](https://www.nomadproject.io/) sandbox and used [parameterized jobs](https://www.nomadproject.io/docs/job-specification/parameterized) execute 16 concurrent renders while I slept. Did you know youtube has a 50-video-upload-per-day limit? Towards the end of my planned content, I had a hefty backlog waiting for the gatekeeper to accept the next load. I hope some of these was a help to someone.