Let's build a distributed ansible-like automation tool!

Hi everyone !

For the last couple months, I have been working on the proof of concept of an automation tool (ansible-like) for DevOps that could be scaled (controllers/workers architecture). Right now the project is far from a "v1.0.0" (not optimized at all) but I get it to work under certain conditions.

https://gitlab.com/dux-tool/dux

I would love to know what people think about this Idea and how it is done so far ! Any feedback will be appreciated !

(If somebody is already working on something like this, please let me know. It means I haven't found your project yet ^^)

2 Likes

Also check out Nix and Colmena, those projects have been around for a while.

3 Likes

Sounds like puppet.

I'm intrigued by the problem you're facing with Deserialize tasks. An option per module is going to be painful down the road. Worth asking a specific question about it here in the forum for suggestions.

I'm curious if you intend to have task/module/playbook compatibility with ansible so that existing ansible playbooks can be refused as-is. It would be a huge selling point for convincing professional teams to switch, but will be much more difficult! Dux syntax looks very familiar.

1 Like

Thank you for your time !
About the Deserialize task / 1 option per module, if you are talking about the definition of the step struct in this file, it's (so far) the only solution I found to avoid having to invoke modules with the !module_name syntax. In his (abandonned) jetporch project, Michael DeHaan was using the !module_name syntax which is a YAML tag. It is the proper way I think but, exactly as you point, I want to be as close as possible to the ansible playbook syntax. Full compatibility would be awesome but I am not there yet.

1 Like

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.