mitogen VS mgmt

Ran into a variant of this when working on an IO loop, ended up with a little "Side" abstraction to wrap bidirectional/unidirectional descriptors to behave identically for the rest of the library. It's an annoying wart but pretty easy to avoid in userspace.. https://github.com/mitogen-hq/mitogen/blob/798032b9/mitogen/...

It's an odd piece of code for 'self-replicating', and I'd say is a bit of obscure project, but it has something amazing: alternative strategies for Ansible to speedup playbooks. It's rough, badly supported, requires patching to run on modern Ansible versions, and you are on your own if you use it, but it's so fast, that's it's impossible to drop. https://mitogen.networkgenomics.com/

I'm not sure how to interpret running 100 debug messages (https://github.com/ansible-community/ara/blob/master/tests/integration/benchmark_tasks.yaml) into real life performance. Mitogen's Benchmark used either 100 times a "hostname" command on the target machine (https://github.com/mitogen-hq/mitogen/blob/master/tests/ansible/bench/loop-100-items.yml) or running the DebOps project (https://github.com/debops/debops-playbooks/blob/master/playbooks/common.yml) for some sorta real-world module usage.

You can try to decrease the amount of failed connections w mitogen: https://github.com/mitogen-hq/mitogen/tags

It could use a Queue of some kind rather than just pushing onto a deque between threads [1]? Then it would idly wait for the results_thread_main to push results.

I guess that might be what Mitogen does, a faster Ansible strategy. https://github.com/mitogen-hq/mitogen/blob/master/docs/ansib...

[1] https://github.com/ansible/ansible/blob/becf9416736dc911d341...

Yes, I use ansible-base + manually installed collections and mitogen works with both fully qualified module names as well as the short version. Should work since last year actually: https://github.com/mitogen-hq/mitogen/releases/tag/v0.3.0-rc.0

dw did make a comment there, but its definitely got a disgruntled attitude.

> I think etcd is basically a k8s only project now

I hate etcd with the best of them, but etcd is used in a lot more places than just kubernetes:

https://github.com/apache/apisix/blob/master/docs/en/latest/...

https://github.com/traefik/traefik#:~:text=Etcd,

https://github.com/zalando/patroni#patroni-a-template-for-po...

https://github.com/purpleidea/mgmt/tree/0.0.26/etcd (this one shows up on HN quite a bit)

https://github.com/sorintlab/stolon#features

It's actually one of the major reasons I wouldn't touch those projects

This is a new provisioning tool built with https://github.com/purpleidea/mgmt/ that I hope both provides great value and also demonstrates the start of a new way to build certain kinds of software.

Thanks for reading!

I've looked briefly into this project before. Some ideas are similar to what I'm doing in https://github.com/purpleidea/mgmt/ but the really weird thing is that I have no idea who's behind this language. A person? A company? A small group? Are they anonymous for some reason or am I oblivious?

I don't generally believe in orchestrators (they miss the point, things are not single computers and neither is the world) and so I have that feedback here but also for:

> Airflow/Cadence/Temporal/Databuilderframework?

Which don't really think about modelling non-centralized things.

This of course doesn't mean they're not useful, it's just that they don't have what I believe is a good long-term value proposition.

I'm incredibly biased because I'm working on programmatic, real-time modelling of distributed systems with https://github.com/purpleidea/mgmt/

The DAG concurrency stuff feels familiar to what I've been doing with our language, mcl. https://github.com/purpleidea/mgmt/

Our goal is NOT a general-purpose turing-complete language like this one is, but we do some amazing lock-free, DAG concurrency things to achieve the processing wins.

I don't think it's good news, but why is anyone surprised? Nobody wants to pay for open source.

Companies want it for free, and individuals don't have enough luxury time to be able to do it themselves.

Prove me wrong and help patch or fund https://github.com/purpleidea/mgmt/ and you'll have an even better replacement for terraform!

Individual here, not a company. We'd love contributors to https://github.com/purpleidea/mgmt/

Eventually decided puppet wasn't a good enough tool to be able to autonomously deploy and continuously manage such clusters. So I started working on this https://github.com/purpleidea/mgmt/ project. Not quite MVP yet, but trying to get there soon. Got distracted along the way with having to work real jobs (Red Hat, Amazon) to pay bills.