Archives
Contributors
-
Re: Delivery carrier development
If the original repo is in good shape, then it's a matter of transferring it to the OCA organization.-sbiOn Mon, Oct 28, 2019 at 2:57 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:@OCA core maintainers. Where are we in the process to create repo ? Do we have yet enough +1's ?On Wed, Jun 12, 2019 at 6:17 PM David Beal <david.beal@akretion.com> wrote:I'll let Raphael FR answer ;-)a chance to be in first place in search engine list, I imaginebut need a good description and metaLe mer. 12 juin 2019 à 16:47, Yannick Vaucher <yannick.vaucher@camptocamp.com> a écrit :+1Having a common transporter API in a separate python lib is definitively the way to go.Would be great to be able to contribute by adding some other transporter (like swiss postlogistics).What was the name "Roulier" for BTW?Cheers,Yannick VaucherBusiness Solutions Software DeveloperCamptocamp SAPSE A, CH-1015 LausannePhone: +41 21 619 10 30Office: +41 21 619 10 10On Wed, 12 Jun 2019 at 16:37, Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:+1 tooOn Wed, Jun 12, 2019 at 4:22 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:+1 for me.That could help carriers implementation in Odoo.On Fri, Jun 7, 2019 at 2:22 PM David Beal <david.beal@akretion.com> wrote:Hi Oca nistas,@akretion Raphael Reverdy initiate a project named Roulierto develop communication with carriers and mainly get shipping label.Consequently to https://github.com/OCA/delivery-carrier/issues/197I propose to integrate Roulier to OCA to promote this developmentAre you OK with this proposal ?If ok, we may have Raphael (at least him) as PSC._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel : +352 20 21 10 20 19
Fax : +352 20 21 10 21
Gsm : +352 691 50 60 88Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDepartment HeadBusiness Solutions_______________________________________________
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
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel : +352 20 21 10 20 19
Fax : +352 20 21 10 21
Gsm : +352 691 50 60 88Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Stéphane Bidoul - 07:31 - 28 Oct 2019 -
Re: Delivery carrier development
@OCA core maintainers. Where are we in the process to create repo ? Do we have yet enough +1's ?On Wed, Jun 12, 2019 at 6:17 PM David Beal <david.beal@akretion.com> wrote:I'll let Raphael FR answer ;-)a chance to be in first place in search engine list, I imaginebut need a good description and metaLe mer. 12 juin 2019 à 16:47, Yannick Vaucher <yannick.vaucher@camptocamp.com> a écrit :+1Having a common transporter API in a separate python lib is definitively the way to go.Would be great to be able to contribute by adding some other transporter (like swiss postlogistics).What was the name "Roulier" for BTW?Cheers,Yannick VaucherBusiness Solutions Software DeveloperCamptocamp SAPSE A, CH-1015 LausannePhone: +41 21 619 10 30Office: +41 21 619 10 10On Wed, 12 Jun 2019 at 16:37, Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> wrote:+1 tooOn Wed, Jun 12, 2019 at 4:22 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:+1 for me.That could help carriers implementation in Odoo.On Fri, Jun 7, 2019 at 2:22 PM David Beal <david.beal@akretion.com> wrote:Hi Oca nistas,@akretion Raphael Reverdy initiate a project named Roulierto develop communication with carriers and mainly get shipping label.Consequently to https://github.com/OCA/delivery-carrier/issues/197I propose to integrate Roulier to OCA to promote this developmentAre you OK with this proposal ?If ok, we may have Raphael (at least him) as PSC._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel : +352 20 21 10 20 19
Fax : +352 20 21 10 21
Gsm : +352 691 50 60 88Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSJoël Grand-GuillaumeDepartment HeadBusiness Solutions_______________________________________________
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
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Luxembourg
Tel : +352 20 21 10 20 19
Fax : +352 20 21 10 21
Gsm : +352 691 50 60 88Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
www.acsone.eu
by Denis Roussel - 02:56 - 28 Oct 2019 -
DevOps: Sway Remote Sessions
Hi All,I was faced with an issue recently that some company NUKs smeared all the sudden without further sign of life.I wondered the possibility to run user sessions over the local network on a more reliable server accessed from Raspberry PI thin clients.Enter Ubuntu 19.10 (released some days ago) with Gnome 3.34 shipped which finally has tenable Wayland support. (I use the Pop OS distribution)x2go server has been well documented and in use for a couple of years. But Wayland support: non existent.Enter waypipe a GSOC sponsored network transport for Wayland which works similar to ssh -X.Enter sway a lightweight tiling window manager (a port of i3 to Wayland).Enter Raspberry Pi 4 release earlier this year with better GPU drivers and therefore support of Wayland.Sway, like i3, can be heavily configured with keybindings for any company's role based productivity scenarios (shortcuts for sales, dev, admon, etc.) It is lightweight on server resources and still pretty sleek for a mainly keyboard driven window manager.Pulling the strings together, I'm trying to configure archlinux on raspberry to login into `waypipe ssh login@server sway`.Not sure how many sessions a NUK Intel i7U Quad-Core with 32GB can bear, but I bet it's quite some.Let's see how DockeryOdoo plays with this setup as for server side development. Maybe using git worktree for all working on a single repo? Maybe split abstract serviced like db, email sink and reverse proxy from the particular odoo-dev service all joining on a odoo-dev network where all developers share abstract services?To be continued ...BR,D. Arnold
by dar - 06:06 - 28 Oct 2019 -
Re: Place to share knowledge/tools on deployment
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>To: Contributors <contributors@odoo-community.org>Subject: Re: Place to share knowledge/tools on deploymentDate: Tuesday, October 22, 2019 19:52Hi 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.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 thinkJordi--
Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada
_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: 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
by dar - 05:41 - 28 Oct 2019 - one repository to store a base/minimal docker image + documented extensions.
-
Re: Place to share knowledge/tools on deployment
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>To: Contributors <contributors@odoo-community.org>Subject: Re: Place to share knowledge/tools on deploymentDate: Tuesday, October 22, 2019 19:52Hi 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.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 thinkJordi--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: 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
by Maxime Chambreuil - 04:06 - 27 Oct 2019 - one repository to store a base/minimal docker image + documented extensions.
-
Re: Place to share knowledge/tools on deployment
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>To: Contributors <contributors@odoo-community.org>Subject: Re: Place to share knowledge/tools on deploymentDate: Tuesday, October 22, 2019 19:52Hi 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.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 thinkJordi--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe
by Yves Goldberg - 03:16 - 27 Oct 2019 - one repository to store a base/minimal docker image + documented extensions.
-
Re: Escape python lint
Thanks a lot Moise for you complete informationLe mer. 23 oct. 2019 à 21:46, Moises Lopez <moylop260@vauxoo.com> a écrit :I have created the following script in a file:```python
import logging
_logger = logging.getLogger(__name__)
query = """SELECT
'Hello World'"""
self.env.cr.execute(query)
_logger.warn("Query error %s", self.env.cr.query)
```
So, I called it using the following command:
`~/odoo-12.0/odoo-bin shell -d openerp_test --log-level=warn < query_test.py`
The output was:
Since that python3 is using bytes by default it is printed using bytes (Notice the "\n" instead of a real newline).
Using `print` the output is ignored for `--log-file=out.txt` parameter or a odoo started using a service.
So it is better using a logger.
But if you like skip this pylint check you can use a comment:
`# pylint: disable=print-used`
More info about:
- https://docs.pylint.org/en/latest/faq.html#do-i-have-to-remember-all-these-numbersEl mié., 23 oct. 2019 a las 12:57, David Beal (<david.beal@akretion.com>) escribió:Thanks Pedro.For my information about ways to escape python lint.- no way- documented somewhere or exampleThanks
David BEALLe mer. 23 oct. 2019 à 19:12, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :Answered in the PR as well: Why not emit it as logger.warning or similar?_______________________________________________
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
--Moisés López CalderónMobile: (+521) 477-752-22-30Twitter: @moylop260Twitter: @vauxoo_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by David BEAL - 10:36 - 24 Oct 2019 -
Re: Place to share knowledge/tools on deployment
Maybe in order to incorporate existing work, people might want to transfer their developments under this Github Organization?For example I could transfer odooup, dockery-* and dodoo-* and others to this organization,but that would only make sense if other people would do the same thing./cc @Akretion @Campotcamp @Acsone @Tecnativa @Numigi @ITPPOf course it's lessening the company branding, but maybe that's what's needed in order to collaborate on the green field...On Wed, Oct 23, 2019 at 4:00 PM David Arnold <dar@xoe.solutions> wrote:Please let me know if anyone wants to collaborate as a member of the organization.I just copied some generic boilerplate and will likely complete with additional boilerplate in the coming days.For now, this is just meant as a PoC to see how collaboration on those topics can be organised across the entire and diverse community.It's clear that it's a relatively slow process, but better slow than sticking with the current mode of "opinion race conditions" and later "path dependency lockins".On Wed, Oct 23, 2019 at 3:13 PM David Arnold <dar@xoe.solutions> wrote:Jordi,ok if we collaborate and discuss an initial project setup:
https://github.com/OdooOps/We can start the conversion with a first issue, and from there keep on evolving.Better than this tribal mailing list...Once we get to a decent point for the general boilerplate we can ask OCA to endorse this effort...Is that ok?On Wed, Oct 23, 2019 at 4:17 AM <admin@ygol.com> wrote:+1.We are using dockery-odoo for development already. I thing it will be great to have docker deployment examples and best practice under OCA.In general, it make sense to join forces on the devops front as it is required by our customers but it is not a core competency (for me).--Yves Goldberg - איב גולדברגodoo| Official Partner - OCA delegateOpen Source ERP, CRM & CMST +972 (3) 720 8818
M +972 (55) 966 1405T +32 (2) 588 2500
------- Original message -----From: Jordi Riera <jordi.riera@numigi.com>To: Contributors <contributors@odoo-community.org>Subject: Place to share knowledge/tools on deploymentDate: Tuesday, October 22, 2019 19:22Hello 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 thinkJordi--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: 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
by dar - 11:26 - 23 Oct 2019 -
Re: Place to share knowledge/tools on deployment
Please let me know if anyone wants to collaborate as a member of the organization.I just copied some generic boilerplate and will likely complete with additional boilerplate in the coming days.For now, this is just meant as a PoC to see how collaboration on those topics can be organised across the entire and diverse community.It's clear that it's a relatively slow process, but better slow than sticking with the current mode of "opinion race conditions" and later "path dependency lockins".On Wed, Oct 23, 2019 at 3:13 PM David Arnold <dar@xoe.solutions> wrote:Jordi,ok if we collaborate and discuss an initial project setup:
https://github.com/OdooOps/We can start the conversion with a first issue, and from there keep on evolving.Better than this tribal mailing list...Once we get to a decent point for the general boilerplate we can ask OCA to endorse this effort...Is that ok?On Wed, Oct 23, 2019 at 4:17 AM <admin@ygol.com> wrote:+1.We are using dockery-odoo for development already. I thing it will be great to have docker deployment examples and best practice under OCA.In general, it make sense to join forces on the devops front as it is required by our customers but it is not a core competency (for me).--Yves Goldberg - איב גולדברגodoo| Official Partner - OCA delegateOpen Source ERP, CRM & CMST +972 (3) 720 8818
M +972 (55) 966 1405T +32 (2) 588 2500 ------- Original message -----From: Jordi Riera <jordi.riera@numigi.com>To: Contributors <contributors@odoo-community.org>Subject: Place to share knowledge/tools on deploymentDate: Tuesday, October 22, 2019 19:22Hello 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 thinkJordi--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: 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
by dar - 11:00 - 23 Oct 2019 -
Re: Place to share knowledge/tools on deployment
Jordi,ok if we collaborate and discuss an initial project setup:
https://github.com/OdooOps/We can start the conversion with a first issue, and from there keep on evolving.Better than this tribal mailing list...Once we get to a decent point for the general boilerplate we can ask OCA to endorse this effort...Is that ok?On Wed, Oct 23, 2019 at 4:17 AM <admin@ygol.com> wrote:+1.We are using dockery-odoo for development already. I thing it will be great to have docker deployment examples and best practice under OCA.In general, it make sense to join forces on the devops front as it is required by our customers but it is not a core competency (for me).--Yves Goldberg - איב גולדברגodoo| Official Partner - OCA delegateOpen Source ERP, CRM & CMST +972 (3) 720 8818
M +972 (55) 966 1405T +32 (2) 588 2500 ------- Original message -----From: Jordi Riera <jordi.riera@numigi.com>To: Contributors <contributors@odoo-community.org>Subject: Place to share knowledge/tools on deploymentDate: Tuesday, October 22, 2019 19:22Hello 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 thinkJordi--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: 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
by dar - 10:16 - 23 Oct 2019 -
Re: Escape python lint
I have created the following script in a file:```python
import logging
_logger = logging.getLogger(__name__)
query = """SELECT
'Hello World'"""
self.env.cr.execute(query)
_logger.warn("Query error %s", self.env.cr.query)
```
So, I called it using the following command:
`~/odoo-12.0/odoo-bin shell -d openerp_test --log-level=warn < query_test.py`
The output was:
Since that python3 is using bytes by default it is printed using bytes (Notice the "\n" instead of a real newline).
Using `print` the output is ignored for `--log-file=out.txt` parameter or a odoo started using a service.
So it is better using a logger.
But if you like skip this pylint check you can use a comment:
`# pylint: disable=print-used`
More info about:
- https://docs.pylint.org/en/latest/faq.html#do-i-have-to-remember-all-these-numbersEl mié., 23 oct. 2019 a las 12:57, David Beal (<david.beal@akretion.com>) escribió:Thanks Pedro.For my information about ways to escape python lint.- no way- documented somewhere or exampleThanks
David BEALLe mer. 23 oct. 2019 à 19:12, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :Answered in the PR as well: Why not emit it as logger.warning or similar?_______________________________________________
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
--Moisés López CalderónMobile: (+521) 477-752-22-30Twitter: @moylop260Twitter: @vauxoo
by Moisés López Calderón - 09:46 - 23 Oct 2019 -
Re: Escape python lint
Thanks Pedro.For my information about ways to escape python lint.- no way- documented somewhere or exampleThanks
David BEALLe mer. 23 oct. 2019 à 19:12, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :Answered in the PR as well: Why not emit it as logger.warning or similar?_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by David BEAL - 07:56 - 23 Oct 2019 -
Re: Escape python lint
Answered in the PR as well: Why not emit it as logger.warning or similar?
by Pedro M. Baeza - 07:11 - 23 Oct 2019 -
Escape python lint
HI all,I've done this PRYes a non academic one.I searched a way to escape ring bell from hereAs I understand, only xml files can legitimates trigger these bypass.In my case it concerns python files.Maybe something I don't understood or a better way to display plain queryThanks a lotChef de projetOdoo Développement / Intégration
by David BEAL - 07:05 - 23 Oct 2019 -
Re: Place to share knowledge/tools on deployment
+1.We are using dockery-odoo for development already. I thing it will be great to have docker deployment examples and best practice under OCA.In general, it make sense to join forces on the devops front as it is required by our customers but it is not a core competency (for me).--Yves Goldberg - איב גולדברגodoo| Official Partner - OCA delegateOpen Source ERP, CRM & CMST +972 (3) 720 8818
M +972 (55) 966 1405T +32 (2) 588 2500 ------- Original message -----From: Jordi Riera <jordi.riera@numigi.com>To: Contributors <contributors@odoo-community.org>Subject: Place to share knowledge/tools on deploymentDate: Tuesday, October 22, 2019 19:22Hello 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 thinkJordi--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe
by Yves Goldberg - 11:15 - 23 Oct 2019 -
Re: Place to share knowledge/tools on deployment
+👍👍Mit freundlichen Grüßen
We look forward to see you. Best Regards
Dipl. Ing. (Fh) Georg Notter
Agent ERP GmbH
www.agenterp.comAm 23.10.2019 um 12:57 schrieb Johan Van Hirtum <johan@vanhirtum.be>:
Hey Jordi,
Very cool plan ! Would indeed be very helpful.
With kind regards,
Van Hirtum Johan
Van: Jordi Riera [mailto:jordi.riera@numigi.com]
Verzonden: dinsdag 22 oktober 2019 18:22
Aan: Contributors
Onderwerp: Place to share knowledge/tools on deploymentHello 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
by Georg Notter - 11:05 - 23 Oct 2019 -
RE: Place to share knowledge/tools on deployment
Hey Jordi,
Very cool plan ! Would indeed be very helpful.
With kind regards,
Van Hirtum Johan
Van: Jordi Riera [mailto:jordi.riera@numigi.com]
Verzonden: dinsdag 22 oktober 2019 18:22
Aan: Contributors
Onderwerp: Place to share knowledge/tools on deploymentHello 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
by johan - 10:51 - 23 Oct 2019 -
Re: Place to share knowledge/tools on deployment
/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.mdEl 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.mdJust 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- OperationsThen 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.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/CONSULTANTO: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.comP.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 thinkJordi--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, 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
by dar - 10:51 - 23 Oct 2019 -
Re: Place to share knowledge/tools on deployment
/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.mdJust 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- OperationsThen 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.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/CONSULTANTO: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.comP.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 thinkJordi--Jordi Riera - VP TechniqueNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, 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
by dar - 10:36 - 23 Oct 2019
