Contributors mailing list archives
Re: Proposal for new repo - Clouderby
Accomodata, Jos De Graeve
At Apertoso we also built something focused on the way we do development and hosting of our customer instances.
I dit a short presentation about it last week: https://docs.google.com/presentation/d/1lDdgoSRIJhSQ4KFrxN-HO9knFJEVashuo7UJddUzALo/edit#slide=id.g1785582584_0_78
We published what we use internally here:
What i see today is that everybody already uses something to manage their infrastructure, but everybody is doing it in their own way There are a lot of ways to do your infrastructure wrong, but there are also multiple ways to do it right. Bottom line is that a lot of duplicated work already has been done.
What everybody needs is the basic host inventory information on which instances you need to run, and their configuration parameters. This inventory information can be on odoo instances, but imho it should not be limited only to that.
The next step is to use that information to setup your infrastructure. If you use a classical setup where instances are deployed on a VM, one can use ansible for that. Ansible allows to use a "dynamic inventory" script. An example for such a script is: https://github.com/apertoso/tools/blob/master/ansible_env_all.py. Next to ansible there are other tools as well. ( Puppet, Chef, ... )
For the hipster dev-ops there is docker. With docker your instances get simplified to the absolute minimal, so there is no longer a real need for a full fledged configuration management tool to setup an individual instance. We created a few scripts to take our inventory information and build a docker image for that. The scripts fetch the required modules, generate a dockerfile and run docker to build an image. These images can be used on a production environment as well as on your development laptop as well as on your staging environment.
What @YannickB has done is great work. Unfortunately i could not attend his presentation last week but i'm looking forward to see the slides of his presentation. His clouder project is the best i seen so far. What i don't like however, is that i see templating code inside an odoo module. So there is no de-coupling between the "infrastructure data" and the "infrastructure implementation".
So i feel there is real opportunity here to put a lot of experience together and build something great :)
As a suggestion i would like to propose "infrastructure-inventory"
2016-10-12 14:22 GMT+02:00 Juan José Scarafía (ADHOC) <email@example.com>:
+1 for "clouder". FYI we have a set of modules (https://github.com/ingadhoc/
odoo-infrastructure) for a similar approach but only focus for odoo deployment. Ther are not OCA quality modules. They need a complete refactoring. I think I like Yennik clouder approach more, let's join efforts.El sáb., 8 oct. 2016 a las 15:07, Daniel Reis (<firstname.lastname@example.org>) escribió:I also agree with "clouder": This is a project with it's own identity and it wouldn't be helpful to later add here unrelated modules just because they are features for SaaS deployment. -- Daniel--