1. Mailing Lists
  2. Contributors
  3. Re: Place to share knowledge/tools on deployment

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

RE: Place to share knowledge/tools on deployment

Re: Place to share knowledge/tools on deployment

Avatar

Re: Place to share knowledge/tools on deployment

by
dar
- 23/10/2019 10:50:33
/R DockeryOdoo:

./ep/009_EP_reverse_proxy_dev_sandboxing_for_support_operations.md
./ep/010_EP_strongly_conventional_dev_folders_layout_for_distributed_teams.mg
./ep/011_EP_makefile_customizable_workdir_lifecycle_scripting.md
./ep/012_EP_rebase_on_upstream_tooling_as_outsouced_chore_repo_maintenance.md

El mié., 23 oct. 2019, 3:35 a.m., David Arnold <dar@xoe.solutions> escribió:
/R doodba:

./ep/006_EP_runtime_environment_footprint.md
./ep/007_EP_ops_team_config_lifecycle_mgt.md
./ep/008_EP_secops_team_secrets_lifecycle_mgt_and_secure_secrets_provisioning.md

... and so forth ...

El mié., 23 oct. 2019, 3:22 a.m., David Arnold <dar@xoe.solutions> escribió:
/R gitoo:

./ep/003_EP_dev_prod_parity_principle.md
./ep/004_EP_upstream_contribution_workflow_during_dev.md
./el/005_EP_dockerignore_as_build_artifact_gatekeeper.md

Just a few example topics that pop into my mind to be seriously discussed... ;-)


El mié., 23 oct. 2019, 2:40 a.m., David Arnold <dar@xoe.solutions> escribió:
Maybe we could start with a bare project with a single subfolder ep (Enhancement Proposals).

There we start with the first enhancement through a series of PR to define Specs for a base docker.

And so forth. While always keeping an eye to evolve only the canonical form (or variant) of doing things in master.

There is a lot of thought about commiting EP as part of the project evolution and good project governance, which I cannot resume here.

Maybe we should copycat a good example out there in a PoC project to explain the concept.

But that only works upon commitment of the interested parties.

Project name?

El mar., 22 oct. 2019, 12:38 p.m., David Arnold <dar@xoe.solutions> escribió:
Hi all,

Most importantly we have to understand that it's not about tools, but about codified best practices.

Then we have to understand that there are two topics involved with different needs, teams and lifecycles:

- DevOps
- Operations

Then we need a place to share (and evolve) Best Practices in a human readable format (in order to lift the median proficiency in the ecosystem).

When sufficient alignment is achieved, we can talk about tools.

One tool which implicitly tries to codify those best practices is DockeryOdoo, but there are others, too. However there is little documentation about the motivations and line of thoughts behind it. This is what's missing most.

The challenge is to discuss and formalize on the green field about best practices. ;-)

Best Regards,

David A.

El mar., 22 oct. 2019, 12:12 p.m., Juan José Scarafía (ADHOC) <scarafia.juanjose@gmail.com> escribió:
+1 for having somewhere to share and build together. Not sure which media would be the best to make it easy. A repo could be, but perhaps also a google doc or something, at lest for draft proposals.
But yes, perhaps the repo, later issues, and perhaps issues links to google docs or whatever.
A kubernates report for a start would be great.


Ing. Juan José Scarafía

(+54 9 341) 3 278039

twitter: @jjscarafia

github: @jjscarafia



El mar., 22 de oct. de 2019 a la(s) 13:52, Maxime Chambreuil (mchambreuil@opensourceintegrators.com) escribió:
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
O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com
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

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

Reference