Community mailing list archives
Re: Hosting infrastructure based on Odooby
On a side note, a discussion with the Anybox guys convinced me that I need to use Chef/puppet/Salt/Ansible as a subcomponent to no reinvent some part of the wheel. Currently I use the docker versions to maintain the standardization of containers and the upgrade but this will probably not be enough.
The main advantage of using Odoo as the Orchestrator is the flexibility of the interface and workflow, I don't think I'd be able to have this kind of backoffice on Chef/Puppet/Salt/Ansible so I really think they are complementary.
+33 (0) 6 70 74 52 26 | firstname.lastname@example.org
My blog : www.disruptingworld.me/
<img alt="Twitter" src="cid:email@example.com" height="20px"> <img alt="Github" src="cid:firstname.lastname@example.org" height="20px"> <img alt="Facebook" src="cid:email@example.com" height="20px"> <img alt="Google" src="cid:firstname.lastname@example.org" height="20px"> <img alt="RSS" src="cid:email@example.com" height="20px">
Building the tools we need
98 Avenue du general pierre billotte BatD
www.yolo-consulting.net | www.empower-us.net | www.wikicompare.info
Le 07/11/2014 09:52, Yannick Buron a écrit : > Orchestrator! That should make it, thank you :) Yes this is the correct word, and the business for this kind of tools is called "Orchestration" - you named some of the big open source players in this field: Chef, Puppet, Salt, Ansible... I've been toying with the idea of something like this using OpenERP for a long time but never had a real need, I'm glad someone actually made it. I wish you all the best for this project! Lionel.