hashi-ui VS Juju

Nomad also scales really well. In my experience swarm had a lot of issues with going above 10 machines in a cluster. Stuck containers, containers that are there but swarm can't see them and more. But still i loved using swarm with my 5 node arm cluster, it is a good place to start when you hit the limit of a single node.

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

1. IIRC you can run jobs directly from UI now, but IMO this is kinda useless. Running a job is simple as 'nomad run jobspec.nomad'. You can also run a great alternative UI ( https://github.com/jippi/hashi-ui ).

2. IMO HCL > YAML for job definitions. I've used both extensively and HCL always felt much more human friendly. The way K8s uses YAML looks to me like stretching it to it's limits and barely readable at times with templates.

One thing that makes nomad a go-to for me is that it is able to run workloads pretty much anywhere. Linux, Windows, FreeBSD, OpenBSD, Illumos and ofc Mac.

Hashicorp Nomad combined with Hashi-ui (https://github.com/jippi/hashi-ui) comes relatively close, but is disqualified because it provides no support for easy to use provisioning. Azkaban comes relatively close, but seems not to have strong supoort for containers.

Basically juju is used to deploy microservices, and other stuff too: https://juju.is/

Juju https://juju.is/

https://juju.is/

Each app is packaged in a charm which seems to be a yaml declaring inputs, dependencies and other meta data and optional python code that can respond to certain lifecycle hooks

https://discourse.charmhub.io/t/implementing-relations/1051

   name: my-node-app

I am currently working myself through setting up our new Research GPU-Cluster where we have "sort of" managed to deploy MAAS to manage all the servers more efficiently, and on top of MAAS then use Juju to deploy the further components of the cluster. The components here are

Kubernetes Custom Resources were created to allow the Kubernetes API to be extended for domain-specific logic, by defining new resource types and controllers. OSS frameworks like operator-sdk, kubebuilder and juju were created to simplify the creation of custom resources and their controllers. Tools built with these frameworks came to be known as Operators.

Depending on what you're trying to accomplish, Juju and MAAS, if not just automate with preseed for custom desktops.

At Canonical I work on two open-source projects written in Go: Juju, a large cloud-based application deployment tool, and Pebble, a small Linux service manager. Both include CLI clients and API-based server daemons. Juju in particular is a large distributed system.

The new Portainer charm allows users of Canonical’s Charmed Kubernetes distribution to automatically install and integrate Portainer Business as part of the Kubernetes cluster deployment process, using Juju, the Charmed Operator framework.