Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mitogen, an infrastructure code baseline that sucks less

pythonsweetness.tumblr.com

Post reply on HN
Print view View original

21–24 of 24 posts

Re: Mitogen, an infrastructure code baseline that sucks less

#21

Post by _wmd »

guhcampos wrote: post #5
grabcocque wrote: post #3

A thought occurs that by making this backwards compatible with Ansible playbooks, by having an AoT compiler that compiles a playbook down to pure Python and then feeds that into Mitogen, then as a migration path it could look indistinguishable from Ansible from the perspective of a playbook user.

I believe this is not meant to replace Ansible, but work like an "engine" that Ansible and other similar tools can run under the hood. This is quite low level code even for an everyday Python developer.

Ansible internally abstracts all its SSH bits into a 'connection plug-in', the initial goal is implementing another one of those. So with one or two extra lines in ansible.cfg you will get a much faster Ansible, with no other changes necessary.

I've no desire to replace Ansible, I'm just sick of wasting hours waiting for it to finish

Re: Mitogen, an infrastructure code baseline that sucks less

#22

Post by _wmd »

e12e wrote: post #11

Cool. This is essentially about creating a single image cluster that runs python. I suppose if one can accept the need for python and a python module be installed on all "nodes" - this would start to look a lot like parallel python: http://www.parallelpython.com/ From an architectural point of view, an si cluster could be viewed as code+communication (+data, but the data could be "wrapped" in code). Ssh and shell pro…

A zero byte Python script can grow up to be anything in the absence of constraints, the infrastructure label makes it simple to say no when thinking about including a feature, and to ease selecting one implementation strategy over another. The nerd within would love to implement subtree detachment ( https://github.com/dw/mitogen/blob/master/docs/images/discon... ): this is basically the beginnings of an Internet worm, but it has zero practical use for infrastructure, so it's complexity I'd prefer to avoid.

Commercially, the killer feature for me in this library will be its Python 2.4 support. I need that for consulting work, but that constraint stands in direct contrast to a general purpose framework for use in application development. Developers want shiny new Python 3 and suchlike, commercially I've never needed that and will be unlikely to need it for a few more Debian/RHEL/Ubuntu releases (I'm guessing, probably 2019)

I don't want to rewrite Pyro4 or end up with a design as complex as CORBA (with all the pain transparent object proxies entail).. it should have just enough complexity to make it ideal for the target use case.

Re: Mitogen, an infrastructure code baseline that sucks less

#23

Post by _ix »

marmaduke wrote: post #17

The appeal of Ansible is that you can declaratively spec infrastructure and it happens (more or less). I don't see how this competes with that.

If I understand it correctly, this is intended to replace the dependencies or subsystems of applications like Ansible rather than Ansible itself.
Post reply on HN