Contributors mailing list archives

contributors@odoo-community.org

Avatar

Re: Place to share knowledge/tools on deployment

by
dar
- 28/10/2019 04:36:12
I plan to eventually write up some "ODEPs" ( like python PEPs ) " Odoo Dev Enhancement Proposal " where I want to lay out the reasoning behind some design decisions I made in DockeryOdoo over the past few years.

However, I have a problem: if there is no second owner of such proposals and if there is no legitimate approval process of any sort, it's going to be yet another tribal silo.

So I hope by writing up some "ODEPs", the discussion might get a chance to become structured, hence contribution might get a chance to become structured, hence consolidation and mind share might become a chance to get structured. Hence a legitimate constituency for this topic (outside of OCA path dependent reasoning) will be possible.

People might think "what an overkill", but ultimately, we all know, that pulling tribes together around a common goal is not only a challenging task since open source communities exist.

Maybe the best approach is formulating understandable, complete and concise proposals in human readable form (the vision behind "ODEPs").

My 2 cents.

El dom., 27 oct. 2019, 10:07 a.m., Maxime Chambreuil <mchambreuil@opensourceintegrators.com> escribió:
The interest will grow if the few involve here make it work...

El dom., 27 de octubre de 2019 08:16, <admin@ygol.com> escribió:
What is the next step for this to move on?
- Should we put to vote Maxime's idea to create those 2 repositories? Where would they live?
- Or is it better to keep the discussion outside of OCA? David Arnold prepared a place (odooOps)?

It would be nice to know who is interested by this topic.

tnx
--
Yves Goldberg
--


----- Original message -----
From: Maxime Chambreuil <mchambreuil@opensourceintegrators.com>
Subject: Re: Place to share knowledge/tools on deployment
Date: Tuesday, October 22, 2019 19:52

Hi Jordi,

I think we could start with:
  • one repository to store a base/minimal docker image + documented extensions.
  • one repository per orchestrator (or 1 for all) where we can share configuration with documentation of how to orchestrate the previous Docker images
My 2 cents.

MAXIME CHAMBREUIL
PROJECT MANAGER/CONSULTANT
P.O. BOX 940, HIGLEY, AZ 85236






On Tue, Oct 22, 2019 at 11:22 AM Jordi Riera <jordi.riera@numigi.com> wrote:
Hello list,

During the OCA code sprint in belgium, I had the opportunity to talk again about docker. While the first talk, in 2018, was focused on usage of Docker. This year, the discussion focused on orchestration solutions.
The discussion was interesting and it was found that we could use a place to share good practices and solutions. Regarding orchestration, but also on dockers (odoo and other services like postgres, acsone/kwkhtmltopdf) and around deployments helpers (git-aggregator, gitoo, clik-odoo, etc.)

How would you see it ?

What do you think about to start with a single place where we could have docker-compose templates (or link to repo with templates) and best practices, FAQs, etc (I was thinking questions like: https://odoo-community.org/groups/contributors-15/contributors-148040?mode=thread&date_begin=&date_end=)
The aim would be to ease the adoption of docker based infrastructure over OCA members. Docker-compose is a good tool to ease docker adoption.


Let me know what you think

Jordi


--

Jordi Riera - VP Technique
NUMIGI SOLUTIONS INC.
(514) 317-7944

Longueuil, Québec, Canada













_______________________________________________

_______________________________________________


_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

Reference