Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

  • Proposing "Kitti U." as PSC for Accounting
    Dear community,

    Lastly :), I would like to propose myself, Kitti U., https://github.com/kittiu, as the PSC of Accounting

    I have been actively contributing to OCA in various repository, and we as a company also adopted OCA process in our workflow.

    I think it is time for us to be responsible more in OCA as PSC of some repository.

    Thank you!
    by Kitti Upariphutthiphong - 08:00 - 3 Feb 2020

    13 replies 13 replies

  • Proposing "Pimolnat" as PSC for Logistics
    Dear community,

    I would like to propose my team member, Pimolnat, https://github.com/ps-tubtim, as the PSC of Logistics

    Pimpolnat has actively participate in OCA for various repository, and can be more focus on Logistics in helping in more reviews and migrations.

    Thank you!
    by Kitti Upariphutthiphong - 07:56 - 3 Feb 2020

    10 replies 10 replies

  • Proposing "Saran" as PSC of Human Resources
    Dear community,

    I would like to propose my team member, Saran, https://github.com/Saran440 as the PSC of HR

    Saran has actively participate in OCA for various repository, and can be more focus on Human Resources in helping in more reviews and migrations.

    Thank you!
    by Kitti Upariphutthiphong - 07:56 - 3 Feb 2020

    5 replies 5 replies

  • Odoo instance in Azure/Google Cloud ?
    hello list!

    Here at Numigi, all of our infrastructure is under DigitalOcean. While pricewise we are very happy with them, technologically we start to see some stoppers (mainly the FileSystem of DigitalOcean that prevent scaling).
    A while ago, we tried AWS, but the price at the end of the month was WAY too high.

    Would you have experience with Azure or Google Cloud to host your favorite ERP ?
    I wonder how expensive it is to be in these clouds. I would target Azure, as it is getting better and better compared to Google cloud.

    Let's chat
    Jordi

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

    Longueuil, Québec, Canada

    by Jordi Riera - 03:46 - 31 Jan 2020

    5 replies 5 replies

    • Re: Odoo instance in Azure/Google Cloud ?
      Oh, Jordi.

      I forgot that you can also use Preemptible VMs in Google Cloud with Kubernetes, this would reduce the cost by 40% - 60%.

      Regards,

      On Fri, Jan 31, 2020 at 3:56 PM Gustavo Valverde <gustavo@iterativo.do> wrote:
      Actually, this is a multi-tenant stack with v10, v12 using test and production environments. Right now is holding 10+ databases and around 80 users (and growing), it should hold over 100 users and 40/80 databases (but it's' a naive statement as this will impact the performance).

      The tech stack consist of GKE (with Istio, instead of Nginx), Filestore (I'd prefer Buckets though), CloudSQL, Cloud Build (for CI/CD) and Memorystore (for sessions).

      On Fri, Jan 31, 2020 at 3:02 PM Jordi Riera <jordi.riera@numigi.com> wrote:
      Thank you for sharing !

      I am wondering, the $600 is for a single odoo stack/client ?
      We are looking to start with only a simple k8s migration, with nginx, psql, odoo (12) to begin with.

      Best,
      Jord

      Le ven. 31 janv. 2020 à 13:47, Gustavo Valverde <gustavo@iterativo.do> a écrit :
      Hi Jordi,

      It will actually depend on what you'd like to do, and the level of automation (CI/CD, GitOps, NoOps, etc).

      As an example, we've been using Google Cloud for the last 8 months with Kubernetes (GKE). The hardest part is the designing everything and adapting each piece of Odoo to work in a multi-tenant and distributed system (I've been working on this Docker environment to accomplish thi ; but after everything is in place, your imagination is the limit. It comes at a cost, as it's not cheap. The cheapest setup that I've done is around US$600 and the most expensive around USD$3,000. But there's a bunch of variables (HA, Performance, GitOps, Diversity of environments [9,10,11,12 / dev, prod, staging].

      Regards,

      On Fri, Jan 31, 2020 at 10:47 AM Jordi Riera <jordi.riera@numigi.com> wrote:
      hello list!

      Here at Numigi, all of our infrastructure is under DigitalOcean. While pricewise we are very happy with them, technologically we start to see some stoppers (mainly the FileSystem of DigitalOcean that prevent scaling).
      A while ago, we tried AWS, but the price at the end of the month was WAY too high.

      Would you have experience with Azure or Google Cloud to host your favorite ERP ?
      I wonder how expensive it is to be in these clouds. I would target Azure, as it is getting better and better compared to Google cloud.

      Let's chat
      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



      --

      Gustavo Valverde

      Chief Technology Officer

      M (829) 686 8270 D  (829) 956 5191 ext. 202

      E  gustavo@iterativo.do


      ITERATIVO SRL

      Roble Corporate Center, Piso 7

      Rafael Augusto Sánchez 86, Piantini, Santo Domingo, R. Dominicana


      T (829) 956 5191| E info@iterativo.do | www.iterativo.do


      Member firm of ITERATIVO LLC & Progressa Corporate Group


      Este mensaje y sus anexos pueden contener información confidencial y privilegiada con la intención de que sea utilizada por las personas u organizaciones a quienes esta dirigida, por lo que su uso es exclusivo para su destinatario. Si usted ha recibido este mensaje por error, favor de eliminarlo e informar al remitente del mensaje a través de un correo de respuesta. Si este es el caso, le notificamos que queda estrictamente prohibida la distribución o reproducción de este e-mail y/o sus anexos. iterativo no se hace responsable de las opiniones vertidas en esta comunicación que no estén acordes con su quehacer y fines, y que no se revistan de un carácter oficial. 

      This message and its enclosures may contain confidential and privileged information intended for the use of people and organizations to which it is directed and its use is thus limited to its addressee. If you have received this message by mistake, please eliminate it and inform the sender through a reply message. Should this be the case, you are advised that the distribution or reproduction of this e-mail and/or any attachments contained herein is strictly forbidden. iterativo is not liable for opinions expressed in this message which may not coincide with its responsibilities and purpose and which may not express official matters. 

       

      https://iterativo.do/web/image/39802/hoja-verde.png

      No imprimas este correo si no es necesario. Cuidemos del ambiente!

      Do not print this mail if it's not necessary. Let's take care of the environment!

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



      --
      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



      --

      Gustavo Valverde

      Chief Technology Officer

      M (829) 686 8270 D  (829) 956 5191 ext. 202

      E  gustavo@iterativo.do


      ITERATIVO SRL

      Roble Corporate Center, Piso 7

      Rafael Augusto Sánchez 86, Piantini, Santo Domingo, R. Dominicana


      T (829) 956 5191| E info@iterativo.do | www.iterativo.do


      Member firm of ITERATIVO LLC & Progressa Corporate Group



      --

      Gustavo Valverde

      Chief Technology Officer

      M (829) 686 8270 D  (829) 956 5191 ext. 202

      E  gustavo@iterativo.do


      ITERATIVO SRL

      Roble Corporate Center, Piso 7

      Rafael Augusto Sánchez 86, Piantini, Santo Domingo, R. Dominicana


      T (829) 956 5191| E info@iterativo.do | www.iterativo.do


      Member firm of ITERATIVO LLC & Progressa Corporate Group


      Este mensaje y sus anexos pueden contener información confidencial y privilegiada con la intención de que sea utilizada por las personas u organizaciones a quienes esta dirigida, por lo que su uso es exclusivo para su destinatario. Si usted ha recibido este mensaje por error, favor de eliminarlo e informar al remitente del mensaje a través de un correo de respuesta. Si este es el caso, le notificamos que queda estrictamente prohibida la distribución o reproducción de este e-mail y/o sus anexos. iterativo no se hace responsable de las opiniones vertidas en esta comunicación que no estén acordes con su quehacer y fines, y que no se revistan de un carácter oficial. 

      This message and its enclosures may contain confidential and privileged information intended for the use of people and organizations to which it is directed and its use is thus limited to its addressee. If you have received this message by mistake, please eliminate it and inform the sender through a reply message. Should this be the case, you are advised that the distribution or reproduction of this e-mail and/or any attachments contained herein is strictly forbidden. iterativo is not liable for opinions expressed in this message which may not coincide with its responsibilities and purpose and which may not express official matters. 

       

      https://iterativo.do/web/image/39802/hoja-verde.png

      No imprimas este correo si no es necesario. Cuidemos del ambiente!

      Do not print this mail if it's not necessary. Let's take care of the environment!

      by Gustavo Valverde <gustavo@iterativo.do> - 06:01 - 1 Feb 2020
    • Re: Odoo instance in Azure/Google Cloud ?
      Actually, this is a multi-tenant stack with v10, v12 using test and production environments. Right now is holding 10+ databases and around 80 users (and growing), it should hold over 100 users and 40/80 databases (but it's' a naive statement as this will impact the performance).

      The tech stack consist of GKE (with Istio, instead of Nginx), Filestore (I'd prefer Buckets though), CloudSQL, Cloud Build (for CI/CD) and Memorystore (for sessions).

      On Fri, Jan 31, 2020 at 3:02 PM Jordi Riera <jordi.riera@numigi.com> wrote:
      Thank you for sharing !

      I am wondering, the $600 is for a single odoo stack/client ?
      We are looking to start with only a simple k8s migration, with nginx, psql, odoo (12) to begin with.

      Best,
      Jord

      Le ven. 31 janv. 2020 à 13:47, Gustavo Valverde <gustavo@iterativo.do> a écrit :
      Hi Jordi,

      It will actually depend on what you'd like to do, and the level of automation (CI/CD, GitOps, NoOps, etc).

      As an example, we've been using Google Cloud for the last 8 months with Kubernetes (GKE). The hardest part is the designing everything and adapting each piece of Odoo to work in a multi-tenant and distributed system (I've been working on this Docker environment to accomplish thi ; but after everything is in place, your imagination is the limit. It comes at a cost, as it's not cheap. The cheapest setup that I've done is around US$600 and the most expensive around USD$3,000. But there's a bunch of variables (HA, Performance, GitOps, Diversity of environments [9,10,11,12 / dev, prod, staging].

      Regards,

      On Fri, Jan 31, 2020 at 10:47 AM Jordi Riera <jordi.riera@numigi.com> wrote:
      hello list!

      Here at Numigi, all of our infrastructure is under DigitalOcean. While pricewise we are very happy with them, technologically we start to see some stoppers (mainly the FileSystem of DigitalOcean that prevent scaling).
      A while ago, we tried AWS, but the price at the end of the month was WAY too high.

      Would you have experience with Azure or Google Cloud to host your favorite ERP ?
      I wonder how expensive it is to be in these clouds. I would target Azure, as it is getting better and better compared to Google cloud.

      Let's chat
      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



      --

      Gustavo Valverde

      Chief Technology Officer

      M (829) 686 8270 D  (829) 956 5191 ext. 202

      E  gustavo@iterativo.do


      ITERATIVO SRL

      Roble Corporate Center, Piso 7

      Rafael Augusto Sánchez 86, Piantini, Santo Domingo, R. Dominicana


      T (829) 956 5191| E info@iterativo.do | www.iterativo.do


      Member firm of ITERATIVO LLC & Progressa Corporate Group


      Este mensaje y sus anexos pueden contener información confidencial y privilegiada con la intención de que sea utilizada por las personas u organizaciones a quienes esta dirigida, por lo que su uso es exclusivo para su destinatario. Si usted ha recibido este mensaje por error, favor de eliminarlo e informar al remitente del mensaje a través de un correo de respuesta. Si este es el caso, le notificamos que queda estrictamente prohibida la distribución o reproducción de este e-mail y/o sus anexos. iterativo no se hace responsable de las opiniones vertidas en esta comunicación que no estén acordes con su quehacer y fines, y que no se revistan de un carácter oficial. 

      This message and its enclosures may contain confidential and privileged information intended for the use of people and organizations to which it is directed and its use is thus limited to its addressee. If you have received this message by mistake, please eliminate it and inform the sender through a reply message. Should this be the case, you are advised that the distribution or reproduction of this e-mail and/or any attachments contained herein is strictly forbidden. iterativo is not liable for opinions expressed in this message which may not coincide with its responsibilities and purpose and which may not express official matters. 

       

      https://iterativo.do/web/image/39802/hoja-verde.png

      No imprimas este correo si no es necesario. Cuidemos del ambiente!

      Do not print this mail if it's not necessary. Let's take care of the environment!

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



      --
      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



      --

      Gustavo Valverde

      Chief Technology Officer

      M (829) 686 8270 D  (829) 956 5191 ext. 202

      E  gustavo@iterativo.do


      ITERATIVO SRL

      Roble Corporate Center, Piso 7

      Rafael Augusto Sánchez 86, Piantini, Santo Domingo, R. Dominicana


      T (829) 956 5191| E info@iterativo.do | www.iterativo.do


      Member firm of ITERATIVO LLC & Progressa Corporate Group


      Este mensaje y sus anexos pueden contener información confidencial y privilegiada con la intención de que sea utilizada por las personas u organizaciones a quienes esta dirigida, por lo que su uso es exclusivo para su destinatario. Si usted ha recibido este mensaje por error, favor de eliminarlo e informar al remitente del mensaje a través de un correo de respuesta. Si este es el caso, le notificamos que queda estrictamente prohibida la distribución o reproducción de este e-mail y/o sus anexos. iterativo no se hace responsable de las opiniones vertidas en esta comunicación que no estén acordes con su quehacer y fines, y que no se revistan de un carácter oficial. 

      This message and its enclosures may contain confidential and privileged information intended for the use of people and organizations to which it is directed and its use is thus limited to its addressee. If you have received this message by mistake, please eliminate it and inform the sender through a reply message. Should this be the case, you are advised that the distribution or reproduction of this e-mail and/or any attachments contained herein is strictly forbidden. iterativo is not liable for opinions expressed in this message which may not coincide with its responsibilities and purpose and which may not express official matters. 

       

      https://iterativo.do/web/image/39802/hoja-verde.png

      No imprimas este correo si no es necesario. Cuidemos del ambiente!

      Do not print this mail if it's not necessary. Let's take care of the environment!

      by Gustavo Valverde <gustavo@iterativo.do> - 09:00 - 31 Jan 2020
    • Re: Odoo instance in Azure/Google Cloud ?
      Did you try odoo.sh base? It is a digital ocean with steroids and scale by itself.

      On Fri 31 Jan 2020 at 13:02 Jordi Riera <jordi.riera@numigi.com> wrote:
      Thank you for sharing !

      I am wondering, the $600 is for a single odoo stack/client ?
      We are looking to start with only a simple k8s migration, with nginx, psql, odoo (12) to begin with.

      Best,
      Jord

      Le ven. 31 janv. 2020 à 13:47, Gustavo Valverde <gustavo@iterativo.do> a écrit :
      Hi Jordi,

      It will actually depend on what you'd like to do, and the level of automation (CI/CD, GitOps, NoOps, etc).

      As an example, we've been using Google Cloud for the last 8 months with Kubernetes (GKE). The hardest part is the designing everything and adapting each piece of Odoo to work in a multi-tenant and distributed system (I've been working on this Docker environment to accomplish thi ; but after everything is in place, your imagination is the limit. It comes at a cost, as it's not cheap. The cheapest setup that I've done is around US$600 and the most expensive around USD$3,000. But there's a bunch of variables (HA, Performance, GitOps, Diversity of environments [9,10,11,12 / dev, prod, staging].

      Regards,

      On Fri, Jan 31, 2020 at 10:47 AM Jordi Riera <jordi.riera@numigi.com> wrote:
      hello list!

      Here at Numigi, all of our infrastructure is under DigitalOcean. While pricewise we are very happy with them, technologically we start to see some stoppers (mainly the FileSystem of DigitalOcean that prevent scaling).
      A while ago, we tried AWS, but the price at the end of the month was WAY too high.

      Would you have experience with Azure or Google Cloud to host your favorite ERP ?
      I wonder how expensive it is to be in these clouds. I would target Azure, as it is getting better and better compared to Google cloud.

      Let's chat
      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



      --

      Gustavo Valverde

      Chief Technology Officer

      M (829) 686 8270 D  (829) 956 5191 ext. 202

      E  gustavo@iterativo.do


      ITERATIVO SRL

      Roble Corporate Center, Piso 7

      Rafael Augusto Sánchez 86, Piantini, Santo Domingo, R. Dominicana


      T (829) 956 5191| E info@iterativo.do | www.iterativo.do


      Member firm of ITERATIVO LLC & Progressa Corporate Group


      Este mensaje y sus anexos pueden contener información confidencial y privilegiada con la intención de que sea utilizada por las personas u organizaciones a quienes esta dirigida, por lo que su uso es exclusivo para su destinatario. Si usted ha recibido este mensaje por error, favor de eliminarlo e informar al remitente del mensaje a través de un correo de respuesta. Si este es el caso, le notificamos que queda estrictamente prohibida la distribución o reproducción de este e-mail y/o sus anexos. iterativo no se hace responsable de las opiniones vertidas en esta comunicación que no estén acordes con su quehacer y fines, y que no se revistan de un carácter oficial. 

      This message and its enclosures may contain confidential and privileged information intended for the use of people and organizations to which it is directed and its use is thus limited to its addressee. If you have received this message by mistake, please eliminate it and inform the sender through a reply message. Should this be the case, you are advised that the distribution or reproduction of this e-mail and/or any attachments contained herein is strictly forbidden. iterativo is not liable for opinions expressed in this message which may not coincide with its responsibilities and purpose and which may not express official matters. 

       

      https://iterativo.do/web/image/39802/hoja-verde.png

      No imprimas este correo si no es necesario. Cuidemos del ambiente!

      Do not print this mail if it's not necessary. Let's take care of the environment!

      _______________________________________________



      --
      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 Nhomar Hernández - 08:51 - 31 Jan 2020
    • Re: Odoo instance in Azure/Google Cloud ?
      Thank you for sharing !

      I am wondering, the $600 is for a single odoo stack/client ?
      We are looking to start with only a simple k8s migration, with nginx, psql, odoo (12) to begin with.

      Best,
      Jord

      Le ven. 31 janv. 2020 à 13:47, Gustavo Valverde <gustavo@iterativo.do> a écrit :
      Hi Jordi,

      It will actually depend on what you'd like to do, and the level of automation (CI/CD, GitOps, NoOps, etc).

      As an example, we've been using Google Cloud for the last 8 months with Kubernetes (GKE). The hardest part is the designing everything and adapting each piece of Odoo to work in a multi-tenant and distributed system (I've been working on this Docker environment to accomplish thi ; but after everything is in place, your imagination is the limit. It comes at a cost, as it's not cheap. The cheapest setup that I've done is around US$600 and the most expensive around USD$3,000. But there's a bunch of variables (HA, Performance, GitOps, Diversity of environments [9,10,11,12 / dev, prod, staging].

      Regards,

      On Fri, Jan 31, 2020 at 10:47 AM Jordi Riera <jordi.riera@numigi.com> wrote:
      hello list!

      Here at Numigi, all of our infrastructure is under DigitalOcean. While pricewise we are very happy with them, technologically we start to see some stoppers (mainly the FileSystem of DigitalOcean that prevent scaling).
      A while ago, we tried AWS, but the price at the end of the month was WAY too high.

      Would you have experience with Azure or Google Cloud to host your favorite ERP ?
      I wonder how expensive it is to be in these clouds. I would target Azure, as it is getting better and better compared to Google cloud.

      Let's chat
      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



      --

      Gustavo Valverde

      Chief Technology Officer

      M (829) 686 8270 D  (829) 956 5191 ext. 202

      E  gustavo@iterativo.do


      ITERATIVO SRL

      Roble Corporate Center, Piso 7

      Rafael Augusto Sánchez 86, Piantini, Santo Domingo, R. Dominicana


      T (829) 956 5191| E info@iterativo.do | www.iterativo.do


      Member firm of ITERATIVO LLC & Progressa Corporate Group


      Este mensaje y sus anexos pueden contener información confidencial y privilegiada con la intención de que sea utilizada por las personas u organizaciones a quienes esta dirigida, por lo que su uso es exclusivo para su destinatario. Si usted ha recibido este mensaje por error, favor de eliminarlo e informar al remitente del mensaje a través de un correo de respuesta. Si este es el caso, le notificamos que queda estrictamente prohibida la distribución o reproducción de este e-mail y/o sus anexos. iterativo no se hace responsable de las opiniones vertidas en esta comunicación que no estén acordes con su quehacer y fines, y que no se revistan de un carácter oficial. 

      This message and its enclosures may contain confidential and privileged information intended for the use of people and organizations to which it is directed and its use is thus limited to its addressee. If you have received this message by mistake, please eliminate it and inform the sender through a reply message. Should this be the case, you are advised that the distribution or reproduction of this e-mail and/or any attachments contained herein is strictly forbidden. iterativo is not liable for opinions expressed in this message which may not coincide with its responsibilities and purpose and which may not express official matters. 

       

      https://iterativo.do/web/image/39802/hoja-verde.png

      No imprimas este correo si no es necesario. Cuidemos del ambiente!

      Do not print this mail if it's not necessary. Let's take care of the environment!

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



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

      Longueuil, Québec, Canada

      by Jordi Riera - 08:01 - 31 Jan 2020
    • Re: Odoo instance in Azure/Google Cloud ?
      Hi Jordi,

      It will actually depend on what you'd like to do, and the level of automation (CI/CD, GitOps, NoOps, etc).

      As an example, we've been using Google Cloud for the last 8 months with Kubernetes (GKE). The hardest part is the designing everything and adapting each piece of Odoo to work in a multi-tenant and distributed system (I've been working on this Docker environment to accomplish thi ; but after everything is in place, your imagination is the limit. It comes at a cost, as it's not cheap. The cheapest setup that I've done is around US$600 and the most expensive around USD$3,000. But there's a bunch of variables (HA, Performance, GitOps, Diversity of environments [9,10,11,12 / dev, prod, staging].

      Regards,

      On Fri, Jan 31, 2020 at 10:47 AM Jordi Riera <jordi.riera@numigi.com> wrote:
      hello list!

      Here at Numigi, all of our infrastructure is under DigitalOcean. While pricewise we are very happy with them, technologically we start to see some stoppers (mainly the FileSystem of DigitalOcean that prevent scaling).
      A while ago, we tried AWS, but the price at the end of the month was WAY too high.

      Would you have experience with Azure or Google Cloud to host your favorite ERP ?
      I wonder how expensive it is to be in these clouds. I would target Azure, as it is getting better and better compared to Google cloud.

      Let's chat
      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



      --

      Gustavo Valverde

      Chief Technology Officer

      M (829) 686 8270 D  (829) 956 5191 ext. 202

      E  gustavo@iterativo.do


      ITERATIVO SRL

      Roble Corporate Center, Piso 7

      Rafael Augusto Sánchez 86, Piantini, Santo Domingo, R. Dominicana


      T (829) 956 5191| E info@iterativo.do | www.iterativo.do


      Member firm of ITERATIVO LLC & Progressa Corporate Group


      Este mensaje y sus anexos pueden contener información confidencial y privilegiada con la intención de que sea utilizada por las personas u organizaciones a quienes esta dirigida, por lo que su uso es exclusivo para su destinatario. Si usted ha recibido este mensaje por error, favor de eliminarlo e informar al remitente del mensaje a través de un correo de respuesta. Si este es el caso, le notificamos que queda estrictamente prohibida la distribución o reproducción de este e-mail y/o sus anexos. iterativo no se hace responsable de las opiniones vertidas en esta comunicación que no estén acordes con su quehacer y fines, y que no se revistan de un carácter oficial. 

      This message and its enclosures may contain confidential and privileged information intended for the use of people and organizations to which it is directed and its use is thus limited to its addressee. If you have received this message by mistake, please eliminate it and inform the sender through a reply message. Should this be the case, you are advised that the distribution or reproduction of this e-mail and/or any attachments contained herein is strictly forbidden. iterativo is not liable for opinions expressed in this message which may not coincide with its responsibilities and purpose and which may not express official matters. 

       

      https://iterativo.do/web/image/39802/hoja-verde.png

      No imprimas este correo si no es necesario. Cuidemos del ambiente!

      Do not print this mail if it's not necessary. Let's take care of the environment!

      by Gustavo Valverde <gustavo@iterativo.do> - 07:45 - 31 Jan 2020
  • Filestore in the cloud
    Hello everyone,

    I was under my shower, and, as I often had a strange idea.
    What about putting the filestore in a storage in the cloud ? Something like D3 Azure Storage etc.
    The aim is to be able to scale up like crazy without to care about the location of the filestore (like volumes mounted on a single machine)
    Do you know any module, article, or initiative that worked on that ?
    Does it seem realistic to you ?

    Let's chat !

    Jordi

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

    Longueuil, Québec, Canada

    by Jordi Riera - 03:35 - 31 Jan 2020

    11 replies 11 replies

  • Localisation PSC - Croatia 
    Hello all,
I would like to propose/introduce  new PSC member for Croatia 
localisation : Goran Kliska

Also, i would like to add Decodio Applications to same PSC.

As for Goran, he is author of several well known and used modules
( l10n_hr - in odoo main source, account_storno used in many countries... )
and i belive is one of top odoo developers in Croatia

Also we would like to start mailing list for Croatia localisation so we can
inform other potential members of our communit activity

Greets to all.
B


-- 
S poštovanjem,
Davor Bojkić - Bole
mob: +385 95 1996 726
    by Davor Bojkić - Bole - 11:15 - 30 Jan 2020

    2 replies 2 replies

    • Re: Localisation PSC - Croatia
      The mailing list is ready: https://odoo-community.org/groups

      Best regards,

      -sbi

      On Fri, Jan 31, 2020 at 1:08 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      Hello,

      +1 to add Goran as PSC member for l10n-croatia.

      I'll also create the mailing list.

      Best regards,

      --
      Stéphane Bidoul | @SBidoul
      Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

      On Thu, Jan 30, 2020 at 11:16 AM Davor Bojkić - Bole <bole@dajmi5.com> wrote:
      Hello all,
I would like to propose/introduce  new PSC member for Croatia 
localisation : Goran Kliska

Also, i would like to add Decodio Applications to same PSC.

As for Goran, he is author of several well known and used modules
( l10n_hr - in odoo main source, account_storno used in many countries... )
and i belive is one of top odoo developers in Croatia

Also we would like to start mailing list for Croatia localisation so we can
inform other potential members of our communit activity

Greets to all.
B



-- 
S poštovanjem,
Davor Bojkić - Bole
mob: +385 95 1996 726

      _______________________________________________
      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 - 01:16 - 31 Jan 2020
    • Re: Localisation PSC - Croatia
      Hello,

      +1 to add Goran as PSC member for l10n-croatia.

      I'll also create the mailing list.

      Best regards,

      --
      Stéphane Bidoul | @SBidoul
      Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

      On Thu, Jan 30, 2020 at 11:16 AM Davor Bojkić - Bole <bole@dajmi5.com> wrote:
      Hello all,
I would like to propose/introduce  new PSC member for Croatia 
localisation : Goran Kliska

Also, i would like to add Decodio Applications to same PSC.

As for Goran, he is author of several well known and used modules
( l10n_hr - in odoo main source, account_storno used in many countries... )
and i belive is one of top odoo developers in Croatia

Also we would like to start mailing list for Croatia localisation so we can
inform other potential members of our communit activity

Greets to all.
B



-- 
S poštovanjem,
Davor Bojkić - Bole
mob: +385 95 1996 726

      _______________________________________________
      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 - 01:10 - 31 Jan 2020
  • 2020 OCA Membership
    Happy New Year to our OCA Contributors.

    Our membership renewals have been sent out earlier in the month. If you think should have received one and didn't please get in touch. 

    If you haven't been a member before but would like to join us for 2020, please have a look here for more information and the link to purchasing a membership or respond on this list and I will get in touch with you.

    As a non-profit organisation we rely on membership as one of our sources of revenue, this annual financial commitment helps to keep the wheels turning behind the scenes.

    The new 2020 logos are up on the website too.

    We look forward to a productive 2020 within the OCA Community.

    Warm regards,
    Rebecca

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 01:55 - 30 Jan 2020

    3 replies 3 replies

  • Reliable integrator in Ivory Coast
    Hello,

    I am looking for a local and reliable Odoo integrator for a manufacturing project in Abidjan, Ivory Coast.

    Any recommendation?

    Thank you.

    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
    by Maxime Chambreuil - 06:01 - 29 Jan 2020

    1 replies 1 replies

  • TimeSheet with Client Signature

    Hi All,


    Has anybody got an example app / info or use case for a timesheet app with client signing the entry (like delivery do on their mobile tracking solutions)?

    Else, any hint how to incorporate a signature field.in the app and (how to) deploy it?

    Best Regards,

    David A.
    by dar - 03:41 - 29 Jan 2020

    2 replies 2 replies

  • Enable Price List using code
    Hello List,

    I struggle with a simple task. Well something that I thought would be simple.
    I would like to enable the Price Lists using xml or python. So I can test my data that rely on.

    I tried using get_values() in res.config.parameter, an XML record. Nothing stick.

    Would you have advice on how to achieve my quest?

    Thank you all,
    Jordi

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

    Longueuil, Québec, Canada

    by Jordi Riera - 10:25 - 28 Jan 2020

    2 replies 2 replies

  • Pre-commit updates
    tl;dr: pre-commit is getting updated, expect conflicts in your PRs. XML and JS autoformatting!

    Hi community.

    As you might know, for v13 we took a big step forward in our coding standards introducing pre-commit in our workflow, which rewrites all python code in a beautiful-enough fashion.

    After the work we've done in https://github.com/OCA/maintainer-quality-tools/pull/618, our dear Stéphane Bidoul will soon update the pre-commit configuration and it will enable even more code automatic standardization.

    In this case, the main change comes from the inclusion of Prettier and ESLint --fix in our pipeline. They will take the job of prettifying code of these files:
    • .scss/.css
    • .js
    • .xml (via prettier plugin)
    • Others not so common in our codebase: .md, .html, .less, .yaml
    • Before you ask, files created or modified by bots are excluded from the reformat.
    • Only for v13+
    The case for JS is a little bit special in the sense that style changes will be done by Prettier, and AST changes will be done by ESLit, but ESLint still have some linter rules that are not autofixable, and in such case your commit will fail until you satisfy them manually.

    Given this will produce a big diff commit (just like isort+black did), I took this chance to update some of the tools that we were already using, so there could be a little more diff in python maybe. It shouldn't be too much.

    We hope this saves you a lot of time and pain when writing these files. Just write ugly & quick code, and pre-commit will handle the rest 😁

    How does this affect you?

    Really not much; just:
    1. Your open PRs could get conflicts. Rebase it and fix them as usual.
    2. Remember to do pre-commit install when you clone a repo.
    3. JS code might need an update to satisfy the linter.
    4. You are encouraged to enable eslint, black, prettier and editorconfig plugins in your favourite IDE, as you probably already did with flake8 and pylint. They should work out of the box, although pre-commit is the maximum authority regarding code reformatting because it works exactly the same in all envs.
    The change is planned for february 15th, although Stéphane will tell more details in this thread if needed (please) and I'm advancing it for web and website where the change is most interesting.

    Have a nice day!
    --
    Jairo Llopis
    by Jairo Llopis - 03:01 - 24 Jan 2020

    8 replies 8 replies

    • Re: Pre-commit updates
      Hi all,

      The new configurations have been pushed. Let me know of any issue.

      Take care,

      -sbi

      On Sat, Mar 7, 2020 at 1:43 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      Okay folks, after a few weeks of fine tuning we are ready to launch this update.


      I just wanted to insist on the fact that all XML files on the 13.0 branches are going to be reformatted.
      This is for the better, IMO, but if you have major refactorings in progress this may disturb your workflow.

      So if any PSC want to temporarily opt-out some repos of this update, let me know before Friday March 13th.

      Best regards,

      -sbi

      --
      Stéphane Bidoul | @SBidoul
      Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

      On Fri, Jan 24, 2020 at 3:02 PM Jairo Llopis <jairo.llopis@tecnativa.com> wrote:
      tl;dr: pre-commit is getting updated, expect conflicts in your PRs. XML and JS autoformatting!

      Hi community.

      As you might know, for v13 we took a big step forward in our coding standards introducing pre-commit in our workflow, which rewrites all python code in a beautiful-enough fashion.

      After the work we've done in https://github.com/OCA/maintainer-quality-tools/pull/618, our dear Stéphane Bidoul will soon update the pre-commit configuration and it will enable even more code automatic standardization.

      In this case, the main change comes from the inclusion of Prettier and ESLint --fix in our pipeline. They will take the job of prettifying code of these files:
      • .scss/.css
      • .js
      • .xml (via prettier plugin)
      • Others not so common in our codebase: .md, .html, .less, .yaml
      • Before you ask, files created or modified by bots are excluded from the reformat.
      • Only for v13+
      The case for JS is a little bit special in the sense that style changes will be done by Prettier, and AST changes will be done by ESLit, but ESLint still have some linter rules that are not autofixable, and in such case your commit will fail until you satisfy them manually.

      Given this will produce a big diff commit (just like isort+black did), I took this chance to update some of the tools that we were already using, so there could be a little more diff in python maybe. It shouldn't be too much.

      We hope this saves you a lot of time and pain when writing these files. Just write ugly & quick code, and pre-commit will handle the rest 😁

      How does this affect you?

      Really not much; just:
      1. Your open PRs could get conflicts. Rebase it and fix them as usual.
      2. Remember to do pre-commit install when you clone a repo.
      3. JS code might need an update to satisfy the linter.
      4. You are encouraged to enable eslint, black, prettier and editorconfig plugins in your favourite IDE, as you probably already did with flake8 and pylint. They should work out of the box, although pre-commit is the maximum authority regarding code reformatting because it works exactly the same in all envs.
      The change is planned for february 15th, although Stéphane will tell more details in this thread if needed (please) and I'm advancing it for web and website where the change is most interesting.

      Have a nice day!
      --
      Jairo Llopis

      _______________________________________________
      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 - 05:10 - 14 Mar 2020
    • Re: Pre-commit updates
      Thanks for your hard work 
      On Mon, 9 Mar 2020, 1:07 pm Jairo Llopis, <jairo.llopis@tecnativa.com> wrote:
      Thanks a lot!

      El sáb., 7 mar. 2020 a las 12:47, Stéphane Bidoul (<stephane.bidoul@acsone.eu>) escribió:
      Okay folks, after a few weeks of fine tuning we are ready to launch this update.


      I just wanted to insist on the fact that all XML files on the 13.0 branches are going to be reformatted.
      This is for the better, IMO, but if you have major refactorings in progress this may disturb your workflow.

      So if any PSC want to temporarily opt-out some repos of this update, let me know before Friday March 13th.

      Best regards,

      -sbi

      --
      Stéphane Bidoul | @SBidoul
      Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

      On Fri, Jan 24, 2020 at 3:02 PM Jairo Llopis <jairo.llopis@tecnativa.com> wrote:
      tl;dr: pre-commit is getting updated, expect conflicts in your PRs. XML and JS autoformatting!

      Hi community.

      As you might know, for v13 we took a big step forward in our coding standards introducing pre-commit in our workflow, which rewrites all python code in a beautiful-enough fashion.

      After the work we've done in https://github.com/OCA/maintainer-quality-tools/pull/618, our dear Stéphane Bidoul will soon update the pre-commit configuration and it will enable even more code automatic standardization.

      In this case, the main change comes from the inclusion of Prettier and ESLint --fix in our pipeline. They will take the job of prettifying code of these files:
      • .scss/.css
      • .js
      • .xml (via prettier plugin)
      • Others not so common in our codebase: .md, .html, .less, .yaml
      • Before you ask, files created or modified by bots are excluded from the reformat.
      • Only for v13+
      The case for JS is a little bit special in the sense that style changes will be done by Prettier, and AST changes will be done by ESLit, but ESLint still have some linter rules that are not autofixable, and in such case your commit will fail until you satisfy them manually.

      Given this will produce a big diff commit (just like isort+black did), I took this chance to update some of the tools that we were already using, so there could be a little more diff in python maybe. It shouldn't be too much.

      We hope this saves you a lot of time and pain when writing these files. Just write ugly & quick code, and pre-commit will handle the rest 😁

      How does this affect you?

      Really not much; just:
      1. Your open PRs could get conflicts. Rebase it and fix them as usual.
      2. Remember to do pre-commit install when you clone a repo.
      3. JS code might need an update to satisfy the linter.
      4. You are encouraged to enable eslint, black, prettier and editorconfig plugins in your favourite IDE, as you probably already did with flake8 and pylint. They should work out of the box, although pre-commit is the maximum authority regarding code reformatting because it works exactly the same in all envs.
      The change is planned for february 15th, although Stéphane will tell more details in this thread if needed (please) and I'm advancing it for web and website where the change is most interesting.

      Have a nice day!
      --
      Jairo Llopis

      _______________________________________________
      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



      --
      Jairo Llopis

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

      by alfadil - 11:26 - 9 Mar 2020
    • Re: Pre-commit updates
      Thanks a lot!

      El sáb., 7 mar. 2020 a las 12:47, Stéphane Bidoul (<stephane.bidoul@acsone.eu>) escribió:
      Okay folks, after a few weeks of fine tuning we are ready to launch this update.


      I just wanted to insist on the fact that all XML files on the 13.0 branches are going to be reformatted.
      This is for the better, IMO, but if you have major refactorings in progress this may disturb your workflow.

      So if any PSC want to temporarily opt-out some repos of this update, let me know before Friday March 13th.

      Best regards,

      -sbi

      --
      Stéphane Bidoul | @SBidoul
      Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

      On Fri, Jan 24, 2020 at 3:02 PM Jairo Llopis <jairo.llopis@tecnativa.com> wrote:
      tl;dr: pre-commit is getting updated, expect conflicts in your PRs. XML and JS autoformatting!

      Hi community.

      As you might know, for v13 we took a big step forward in our coding standards introducing pre-commit in our workflow, which rewrites all python code in a beautiful-enough fashion.

      After the work we've done in https://github.com/OCA/maintainer-quality-tools/pull/618, our dear Stéphane Bidoul will soon update the pre-commit configuration and it will enable even more code automatic standardization.

      In this case, the main change comes from the inclusion of Prettier and ESLint --fix in our pipeline. They will take the job of prettifying code of these files:
      • .scss/.css
      • .js
      • .xml (via prettier plugin)
      • Others not so common in our codebase: .md, .html, .less, .yaml
      • Before you ask, files created or modified by bots are excluded from the reformat.
      • Only for v13+
      The case for JS is a little bit special in the sense that style changes will be done by Prettier, and AST changes will be done by ESLit, but ESLint still have some linter rules that are not autofixable, and in such case your commit will fail until you satisfy them manually.

      Given this will produce a big diff commit (just like isort+black did), I took this chance to update some of the tools that we were already using, so there could be a little more diff in python maybe. It shouldn't be too much.

      We hope this saves you a lot of time and pain when writing these files. Just write ugly & quick code, and pre-commit will handle the rest 😁

      How does this affect you?

      Really not much; just:
      1. Your open PRs could get conflicts. Rebase it and fix them as usual.
      2. Remember to do pre-commit install when you clone a repo.
      3. JS code might need an update to satisfy the linter.
      4. You are encouraged to enable eslint, black, prettier and editorconfig plugins in your favourite IDE, as you probably already did with flake8 and pylint. They should work out of the box, although pre-commit is the maximum authority regarding code reformatting because it works exactly the same in all envs.
      The change is planned for february 15th, although Stéphane will tell more details in this thread if needed (please) and I'm advancing it for web and website where the change is most interesting.

      Have a nice day!
      --
      Jairo Llopis

      _______________________________________________
      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



      --
      Jairo Llopis
      by Jairo Llopis - 11:06 - 9 Mar 2020
    • Re: Pre-commit updates
      Amazing work, thanks everybody!

      On Sat, Mar 7, 2020 at 2:46 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
      Thank you very much!

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

      by Simone Orsi. - 08:36 - 9 Mar 2020
    • Re: Pre-commit updates
      Thank you very much!
      by Pedro M. Baeza - 02:45 - 7 Mar 2020

  • Odoo2Odoo
    Hi community and Happy New Year!

    We plan a new project with multi-companies on distinct databases and servers.
    We noticed that https://github.com/OCA/connector-odoo2odoo seems seems to be on break.

    Do you use other ways or mitigation when you meet this requirement?

    Have a nice day and receive greetings from "Numigiens" ;-)

    Bruno Joliveau - Architecte applications - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    by Bruno Joliveau - 12:11 - 8 Jan 2020

    13 replies 13 replies

  • Odoo documentation tool
    A former Odoo employee, Nans (len-odoo), has opened-source a tool he has been developing internally for auto-documenting Odoo models.

    He has sent me the link:


    and I think it's worth checking.

    If you think the same and want to adopt it/expand it under OCA umbrella, I think he will glad to give OCA the grant to do it.

    Thanks Nans for this fine contribution.

    Regards.
    by Pedro M. Baeza - 02:35 - 7 Jan 2020

    6 replies 6 replies

  • datetime error when accessing parts of Odoo
    Hello Contributors,

    I am running Odoo v10 and I have an odd error that has just started popping up and it only seems to appear in the Discuss, Sales, and Project Tasks:

    Traceback (most recent call last):
      File "/usr/lib/python2.7/dist-packages/odoo/http.py", line 642, in _handle_exception
        return super(JsonRequest, self)._handle_exception(exception)
      File "/usr/lib/python2.7/dist-packages/odoo/http.py", line 684, in dispatch
        result = self._call_function(**self.params)
      File "/usr/lib/python2.7/dist-packages/odoo/http.py", line 334, in _call_function
        return checked_call(self.db, *args, **kwargs)
      File "/usr/lib/python2.7/dist-packages/odoo/service/model.py", line 101, in wrapper
        return f(dbname, *args, **kwargs)
      File "/usr/lib/python2.7/dist-packages/odoo/http.py", line 327, in checked_call
        result = self.endpoint(*a, **kw)
      File "/usr/lib/python2.7/dist-packages/odoo/http.py", line 942, in __call__
        return self.method(*args, **kw)
      File "/usr/lib/python2.7/dist-packages/odoo/http.py", line 507, in response_wrap
        response = f(*args, **kw)
      File "/usr/lib/python2.7/dist-packages/odoo/addons/calendar/controllers/main.py", line 65, in notify
        return request.env['calendar.alarm_manager'].get_next_notif()
      File "/usr/lib/python2.7/dist-packages/odoo/addons/calendar/models/calendar.py", line 380, in get_next_notif
        for one_date in meeting._get_recurrent_date_by_event():
      File "/usr/lib/python2.7/dist-packages/odoo/addons/calendar/models/calendar.py", line 570, in _get_recurrent_date_by_event
        return [d.astimezone(pytz.UTC) if d.tzinfo else d for d in rset1]
      File "/usr/lib/python2.7/dist-packages/dateutil/rrule.py", line 1144, in _iter
        self._genitem(rlist, gen)
      File "/usr/lib/python2.7/dist-packages/dateutil/rrule.py", line 1082, in __init__
        self.dt = advance_iterator(gen)
      File "/usr/lib/python2.7/dist-packages/dateutil/rrule.py", line 652, in _iter
        if until and res > until:
    TypeError: can't compare offset-naive and offset-aware datetimes

    Other users on the system do not get this error at all. The only thing I can think of that I did recently was to remove a recurring event from my google calendar that is no longer relevant.
    Short of creating a new user I have not figured out a good solution and I was hoping someone here might be able to shine a light on what is causing the error.

    Thank you,


    --
    Nathan Kennedy
    Jack of all trades
    Master of none
    Just don't call me Jack
    by nathan - 08:01 - 4 Jan 2020

    2 replies 2 replies

    • Re: datetime error when accessing parts of Odoo
      On Sat, 2020-01-04 at 23:06 +0000, Iván Todorovich wrote:
      Check if the user has a timezone configured in his preferences.

      I remember encountering something like this a while back
      Hello Ivan,

      Thank you for the response but that is the first thing I checked in case it had gotten cleared somehow. Just for the heck of it I changed the timezone and changed it back but that had no effect.

      Cheers,

      --
      Nathan Kennedy
      Contracted Professional IT
      (360) 637-1090
      https://www.nkent.us/
      by Nathan Kennedy - 12:51 - 5 Jan 2020
    • Re: datetime error when accessing parts of Odoo
      Hi Nathan!

      Check if the user has a timezone configured in his preferences.

      I remember encountering something like this a while back

      Le sam. 4 janv. 2020 à 16:02, Nathan Kennedy <nathan@wakennedys.us> a écrit :
      Hello Contributors,

      I am running Odoo v10 and I have an odd error that has just started popping up and it only seems to appear in the Discuss, Sales, and Project Tasks:

      Traceback (most recent call last):
        File "/usr/lib/python2.7/dist-packages/odoo/http.py", line 642, in _handle_exception
          return super(JsonRequest, self)._handle_exception(exception)
        File "/usr/lib/python2.7/dist-packages/odoo/http.py", line 684, in dispatch
          result = self._call_function(**self.params)
        File "/usr/lib/python2.7/dist-packages/odoo/http.py", line 334, in _call_function
          return checked_call(self.db, *args, **kwargs)
        File "/usr/lib/python2.7/dist-packages/odoo/service/model.py", line 101, in wrapper
          return f(dbname, *args, **kwargs)
        File "/usr/lib/python2.7/dist-packages/odoo/http.py", line 327, in checked_call
          result = self.endpoint(*a, **kw)
        File "/usr/lib/python2.7/dist-packages/odoo/http.py", line 942, in __call__
          return self.method(*args, **kw)
        File "/usr/lib/python2.7/dist-packages/odoo/http.py", line 507, in response_wrap
          response = f(*args, **kw)
        File "/usr/lib/python2.7/dist-packages/odoo/addons/calendar/controllers/main.py", line 65, in notify
          return request.env['calendar.alarm_manager'].get_next_notif()
        File "/usr/lib/python2.7/dist-packages/odoo/addons/calendar/models/calendar.py", line 380, in get_next_notif
          for one_date in meeting._get_recurrent_date_by_event():
        File "/usr/lib/python2.7/dist-packages/odoo/addons/calendar/models/calendar.py", line 570, in _get_recurrent_date_by_event
          return [d.astimezone(pytz.UTC) if d.tzinfo else d for d in rset1]
        File "/usr/lib/python2.7/dist-packages/dateutil/rrule.py", line 1144, in _iter
          self._genitem(rlist, gen)
        File "/usr/lib/python2.7/dist-packages/dateutil/rrule.py", line 1082, in __init__
          self.dt = advance_iterator(gen)
        File "/usr/lib/python2.7/dist-packages/dateutil/rrule.py", line 652, in _iter
          if until and res > until:
      TypeError: can't compare offset-naive and offset-aware datetimes

      Other users on the system do not get this error at all. The only thing I can think of that I did recently was to remove a recurring event from my google calendar that is no longer relevant.
      Short of creating a new user I have not figured out a good solution and I was hoping someone here might be able to shine a light on what is causing the error.

      Thank you,


      --
      Nathan Kennedy
      Jack of all trades
      Master of none
      Just don't call me Jack

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

      by Iván Todorovich - 12:06 - 5 Jan 2020
  • Gsuite [Action Required] Switch to apps that use secure OAuth access

    Hey guys,

    Just thought I'd check here to see if anyone has started to make plans surrounding Googles recent announcement
    to drop support for "less secure apps" aka SMTP.

    The timeline they have set is as follows:

    Best Regards,

    Jacob Oldfield

    Development Analyst

    WilldooIT Pty Ltd

    E: jacob.oldfield@willdooit.com

    P: +61 3 9135 1900

    A: 10/435 Williamstown Road, Port Melbourne, Vic 3207

     

    Making growth through technology easy

     

    cid:image005.png@01D33CFB.CF033C70

     

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by WilldooIT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.


    by jacob.oldfield - 01:35 - 2 Jan 2020

    2 attachments 2 attachments

    Outlook-cid_image0.png
    Outlook-rbiyqh4r.png

    3 replies 3 replies

    • Re: Gsuite [Action Required] Switch to apps that use secure OAuth access 
      Hello Jacob,

I think you are mixing two different things:

* SMTP support is not (yet) being dropped by Google (and there is
nothing in
https://gsuiteupdates.googleblog.com/2019/12/less-secure-apps-oauth-google-username-password-incorrect.html
about this )

* IMAP is impacted though, and this can have an impact for Odoo users
who poll a google mail box using that protocol.

Best wishes for 2020

Alexandre

On 02/01/2020 01:41, Jacob Oldfield wrote:

> Hey guys,

> 

> Just thought I'd check here to see if anyone has started to make plans

> surrounding Googles recent announcement

> to drop support for "less secure apps" aka SMTP.

> 

> The timeline they have set is as follows:

> 

>  1. *June 15, 2020 *- MDM push of IMAP, CalDAV, CardDAV, and Exchange

>     ActiveSync (Google Sync) will no longer work for *new* users.

>  2. *February 15, 2021* - MDM push of IMAP, CalDAV, CardDAV, and

>     Exchange ActiveSync (Google Sync) will no longer work for existing

>     users.

> 

> 

> TLDR; SMTP will be dropped in favour of the new MTA-STS standard.

> 

> 

> The issue of OAuth surrounding email has been raised previously with

> Odoo and they as yet have not added support.

> 

> More about the announcement here.

> https://security.googleblog.com/2019/04/gmail-making-email-more-secure-with-mta.html

> 

> 	

> Google Online Security Blog: Gmail making email more secure with MTA-STS

> standard

> 

> Posted by Nicolas Lidzborski, Senior Staff Software Engineer, Google

> Cloud and Nicolas Kardas, Senior Product Manager, Google Cloud We’re

> excited to announce that Gmail will become the first major email

> provider to follow the new SMTP MTA Strict Transport Security (MTA-STS)

> RFC 8461 and SMTP TLS Reporting RFC 8460 internet standards. Those new

> email security standards are the result of three ...

> security.googleblog.com

> 

> 

> Sorry, accidentally sent this email while I was still typing.

> 

> 

> 

> Regards,

> 

> 

> 	

> 

> Best Regards,

> 

> *Jacob Oldfield

> *

> 

> /Development Analyst/

> 

> *WilldooIT Pty Ltd***

> 

> *E:* jacob.oldfield@willdooit.com<mailto:geoff.szentesi@willdooit.com>

> 

> *P:* +61 3 9135 1900

> 

> *A:* 10/435 Williamstown Road, Port Melbourne, Vic 3207

> 

> / /

> 

> /*Making growth through technology easy*///

> 

>  

> 

> cid:image005.png@01D33CFB.CF033C70 
> 
> * *
> 
> *DISCLAIMER* | This electronic message together with any attachments is
> confidential. If you are not the recipient, do not copy, disclose, or
> use the contents in any way. Please also advise us by e-mail that you
> have received this message in error and then please destroy this email
> and any of its attachments. WilldooIT Pty. Ltd. is not responsible for
> any changes made to this message and/or any attachments after sending by
> WilldooIT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but
> exclude all liability for virus or anything similar in this email or
> attachment.
> 
> 
> ------------------------------------------------------------------------
> *From:* Jacob Oldfield
> *Sent:* Thursday, 2 January 2020 11:33 AM
> *To:* Contributors <contributors@odoo-community.org>
> *Subject:* Gsuite [Action Required] Switch to apps that use secure OAuth
> access
>  
> Hey guys,
> 
> Just thought I'd check here to see if anyone has started to make plans
> surrounding Googles recent announcement
> to drop support for "less secure apps" aka SMTP.
> 
> The timeline they have set is as follows:
> 
> 
> 
> 	
> 
> Best Regards,
> 
> *Jacob Oldfield
> *
> 
> /Development Analyst/
> 
> *WilldooIT Pty Ltd***
> 
> *E:* jacob.oldfield@willdooit.com<mailto:geoff.szentesi@willdooit.com>
> 
> *P:* +61 3 9135 1900
> 
> *A:* 10/435 Williamstown Road, Port Melbourne, Vic 3207
> 
> / /
> 
> /*Making growth through technology easy*///
> 
>  
> 
> cid:image005.png@01D33CFB.CF033C70 
> 
> * *
> 
> *DISCLAIMER* | This electronic message together with any attachments is
> confidential. If you are not the recipient, do not copy, disclose, or
> use the contents in any way. Please also advise us by e-mail that you
> have received this message in error and then please destroy this email
> and any of its attachments. WilldooIT Pty. Ltd. is not responsible for
> any changes made to this message and/or any attachments after sending by
> WilldooIT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but
> exclude all liability for virus or anything similar in this email or
> attachment.
> 
> 
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe
> 


-- 
Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
      by Alexandre Fayolle - 11:35 - 3 Jan 2020
    • Re: Gsuite [Action Required] Switch to apps that use secure OAuth access 
      I think you are mixing two different

On 02/01/2020 01:41, Jacob Oldfield wrote:

> Hey guys,

> 

> Just thought I'd check here to see if anyone has started to make plans

> surrounding Googles recent announcement

> to drop support for "less secure apps" aka SMTP.

> 

> The timeline they have set is as follows:

> 

>  1. *June 15, 2020 *- MDM push of IMAP, CalDAV, CardDAV, and Exchange

>     ActiveSync (Google Sync) will no longer work for *new* users.

>  2. *February 15, 2021* - MDM push of IMAP, CalDAV, CardDAV, and

>     Exchange ActiveSync (Google Sync) will no longer work for existing

>     users.

> 

> 

> TLDR; SMTP will be dropped in favour of the new MTA-STS standard.

> 

> 

> The issue of OAuth surrounding email has been raised previously with

> Odoo and they as yet have not added support.

> 

> More about the announcement here.

> https://security.googleblog.com/2019/04/gmail-making-email-more-secure-with-mta.html

> 

> 	

> Google Online Security Blog: Gmail making email more secure with MTA-STS

> standard

> 

> Posted by Nicolas Lidzborski, Senior Staff Software Engineer, Google

> Cloud and Nicolas Kardas, Senior Product Manager, Google Cloud We’re

> excited to announce that Gmail will become the first major email

> provider to follow the new SMTP MTA Strict Transport Security (MTA-STS)

> RFC 8461 and SMTP TLS Reporting RFC 8460 internet standards. Those new

> email security standards are the result of three ...

> security.googleblog.com

> 

> 

> Sorry, accidentally sent this email while I was still typing.

> 

> 

> 

> Regards,

> 

> 

> 	

> 

> Best Regards,

> 

> *Jacob Oldfield

> *

> 

> /Development Analyst/

> 

> *WilldooIT Pty Ltd***

> 

> *E:* jacob.oldfield@willdooit.com<mailto:geoff.szentesi@willdooit.com>

> 

> *P:* +61 3 9135 1900

> 

> *A:* 10/435 Williamstown Road, Port Melbourne, Vic 3207

> 

> / /

> 

> /*Making growth through technology easy*///

> 

>  

> 

> cid:image005.png@01D33CFB.CF033C70 
> 
> * *
> 
> *DISCLAIMER* | This electronic message together with any attachments is
> confidential. If you are not the recipient, do not copy, disclose, or
> use the contents in any way. Please also advise us by e-mail that you
> have received this message in error and then please destroy this email
> and any of its attachments. WilldooIT Pty. Ltd. is not responsible for
> any changes made to this message and/or any attachments after sending by
> WilldooIT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but
> exclude all liability for virus or anything similar in this email or
> attachment.
> 
> 
> ------------------------------------------------------------------------
> *From:* Jacob Oldfield
> *Sent:* Thursday, 2 January 2020 11:33 AM
> *To:* Contributors <contributors@odoo-community.org>
> *Subject:* Gsuite [Action Required] Switch to apps that use secure OAuth
> access
>  
> Hey guys,
> 
> Just thought I'd check here to see if anyone has started to make plans
> surrounding Googles recent announcement
> to drop support for "less secure apps" aka SMTP.
> 
> The timeline they have set is as follows:
> 
> 
> 
> 	
> 
> Best Regards,
> 
> *Jacob Oldfield
> *
> 
> /Development Analyst/
> 
> *WilldooIT Pty Ltd***
> 
> *E:* jacob.oldfield@willdooit.com<mailto:geoff.szentesi@willdooit.com>
> 
> *P:* +61 3 9135 1900
> 
> *A:* 10/435 Williamstown Road, Port Melbourne, Vic 3207
> 
> / /
> 
> /*Making growth through technology easy*///
> 
>  
> 
> cid:image005.png@01D33CFB.CF033C70 
> 
> * *
> 
> *DISCLAIMER* | This electronic message together with any attachments is
> confidential. If you are not the recipient, do not copy, disclose, or
> use the contents in any way. Please also advise us by e-mail that you
> have received this message in error and then please destroy this email
> and any of its attachments. WilldooIT Pty. Ltd. is not responsible for
> any changes made to this message and/or any attachments after sending by
> WilldooIT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but
> exclude all liability for virus or anything similar in this email or
> attachment.
> 
> 
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe
> 


-- 
Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
      by Alexandre Fayolle - 11:31 - 3 Jan 2020
    • Re: Gsuite [Action Required] Switch to apps that use secure OAuth access

      Hey guys,

      Just thought I'd check here to see if anyone has started to make plans surrounding Googles recent announcement
      to drop support for "less secure apps" aka SMTP.

      The timeline they have set is as follows:
      1. June 15, 2020 - MDM push of IMAP, CalDAV, CardDAV, and Exchange ActiveSync (Google Sync) will no longer work for new users.
      2. February 15, 2021 - MDM push of IMAP, CalDAV, CardDAV, and Exchange ActiveSync (Google Sync) will no longer work for existing users.

      TLDR; SMTP will be dropped in favour of the new MTA-STS standard.


      The issue of OAuth surrounding email has been raised previously with Odoo and they as yet have not added support.

      More about the announcement here.
      Posted by Nicolas Lidzborski, Senior Staff Software Engineer, Google Cloud and Nicolas Kardas, Senior Product Manager, Google Cloud We’re excited to announce that Gmail will become the first major email provider to follow the new SMTP MTA Strict Transport Security (MTA-STS) RFC 8461 and SMTP TLS Reporting RFC 8460 internet standards. Those new email security standards are the result of three ...
      security.googleblog.com

      Sorry, accidentally sent this email while I was still typing.



      Regards,

      Best Regards,

      Jacob Oldfield

      Development Analyst

      WilldooIT Pty Ltd

      E: jacob.oldfield@willdooit.com

      P: +61 3 9135 1900

      A: 10/435 Williamstown Road, Port Melbourne, Vic 3207

       

      Making growth through technology easy

       

      cid:image005.png@01D33CFB.CF033C70

       

      DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by WilldooIT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.


      From: Jacob Oldfield
      Sent: Thursday, 2 January 2020 11:33 AM
      To: Contributors <contributors@odoo-community.org>
      Subject: Gsuite [Action Required] Switch to apps that use secure OAuth access
       
      Hey guys,

      Just thought I'd check here to see if anyone has started to make plans surrounding Googles recent announcement
      to drop support for "less secure apps" aka SMTP.

      The timeline they have set is as follows:

      Best Regards,

      Jacob Oldfield

      Development Analyst

      WilldooIT Pty Ltd

      E: jacob.oldfield@willdooit.com

      P: +61 3 9135 1900

      A: 10/435 Williamstown Road, Port Melbourne, Vic 3207

       

      Making growth through technology easy

       

      cid:image005.png@01D33CFB.CF033C70

       

      DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by WilldooIT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.


      by jacob.oldfield - 01:41 - 2 Jan 2020

      4 attachments 4 attachments

      Outlook-cid_image0.png
      Outlook-3w4oaxj3.png
      Outlook-cid_image0.png
      Outlook-rbiyqh4r.png
  • Upgrade / migration of OCA runbots today 
    Hello

I'll work on upgrading the OCA runbots today. There will be a downtime
of a few hours.

Best regards,


-- 
Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
    by Alexandre Fayolle - 11:25 - 29 Dec 2019

    7 replies 7 replies

    • RE: Upgrade / migration of OCA runbots today

      Thank you!  Happy new year!

       

      De: Alexandre Fayolle [mailto:alexandre.fayolle@camptocamp.com]
      Enviado el: martes, 31 de diciembre de 2019 9:32
      Para: Contributors <contributors@odoo-community.org>
      Asunto: Re: Upgrade / migration of OCA runbots today

       

      On 29/12/2019 11:25, Alexandre Fayolle wrote:
       
      > Hello
       
      > 
       
      > I'll work on upgrading the OCA runbots today. There will be a downtime
       
      > of a few hours.
       
      > 
       
      > Best regards,
       
      > 
       
      Sorry for the delayed update notice.
       
      The runbots are back up (since yesterday morning, actually).
       
      The servers have been updated to the current stable Debian release,
      docker was updated to version 19, Odoo was upgraded to 11.0 using the
      wonderful OpenUpgrade project, PostgreSQL was upgraded to 10.0, the
      Runbot module was upgraded to the 11.0 version (without the docker
      improvements, because these are not compatible with the
      runbot_travis2docker module we are using).
       
      Longer story available at
      https://twitter.com/gurneyalex/status/1211397322430697475
       
      After some tinkering, I got the new stack to work ;) There is one issue
      with nginx I'll need to tackle: the build logs for builds which were
      made on runbot1-2 and runbot2-2 are not visible (HTTP error 404). I'll
      look into this when I'm back from vacations, now is time to get busy in
      the kitchen for tonight's dinner :-p
       
      Happy new year to all OCA contributors ;)
       
       
      -- 
      Alexandre Fayolle
      Chef de Projet
      Tel : +33 4 58 48 20 30
       
      Camptocamp France SAS
      18 rue du Lac Saint André
      73 370 Le Bourget-du-Lac
      France
       
      http://www.camptocamp.com
      by Rafael Blasco (Moduon) - 11:26 - 1 Jan 2020
    • Re: Upgrade / migration of OCA runbots today
      Thanks Alexandre,
      And happy new year.

      > “Im resuming my vacations”

      hahaha


      On Tue 31 Dec 2019 at 2:32 Alexandre Fayolle <alexandre.fayolle@camptocamp.com> wrote:
      On 29/12/2019 11:25, Alexandre Fayolle wrote:


> Hello


> 


> I'll work on upgrading the OCA runbots today. There will be a downtime


> of a few hours.


> 


> Best regards,


> 

Sorry for the delayed update notice.

The runbots are back up (since yesterday morning, actually).

The servers have been updated to the current stable Debian release,
docker was updated to version 19, Odoo was upgraded to 11.0 using the
wonderful OpenUpgrade project, PostgreSQL was upgraded to 10.0, the
Runbot module was upgraded to the 11.0 version (without the docker
improvements, because these are not compatible with the
runbot_travis2docker module we are using).

Longer story available at
https://twitter.com/gurneyalex/status/1211397322430697475

After some tinkering, I got the new stack to work ;) There is one issue
with nginx I'll need to tackle: the build logs for builds which were
made on runbot1-2 and runbot2-2 are not visible (HTTP error 404). I'll
look into this when I'm back from vacations, now is time to get busy in
the kitchen for tonight's dinner :-p

Happy new year to all OCA contributors ;)


      

-- 
Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com

      _______________________________________________
      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ón
      Mobile: (+521) 477-752-22-30
      Twitter: @moylop260
      hangout: moylop260@vauxoo.com
      http://www.vauxoo.com - Odoo Gold Partner
      Twitter: @vauxoo
      by Moisés López Calderón - 06:31 - 31 Dec 2020
    • Re: Upgrade / migration of OCA runbots today
      Thanks for the great effort, Alexandre.

      Happy New Year to all.
      by Pedro M. Baeza - 12:25 - 31 Dec 2020
    • Re: Upgrade / migration of OCA runbots today

      Thanks Alexandre, looks like it was a high action situation :).


      Happy new year to you and all other contributors!


      Kind Regards,

      Kiril

      On 31.12.19 09:31, Alexandre Fayolle wrote:
      On 29/12/2019 11:25, Alexandre Fayolle wrote:

> Hello

> 

> I'll work on upgrading the OCA runbots today. There will be a downtime

> of a few hours.

> 

> Best regards,

> 

Sorry for the delayed update notice.

The runbots are back up (since yesterday morning, actually).

The servers have been updated to the current stable Debian release,
docker was updated to version 19, Odoo was upgraded to 11.0 using the
wonderful OpenUpgrade project, PostgreSQL was upgraded to 10.0, the
Runbot module was upgraded to the 11.0 version (without the docker
improvements, because these are not compatible with the
runbot_travis2docker module we are using).

Longer story available at
https://twitter.com/gurneyalex/status/1211397322430697475

After some tinkering, I got the new stack to work ;) There is one issue
with nginx I'll need to tackle: the build logs for builds which were
made on runbot1-2 and runbot2-2 are not visible (HTTP error 404). I'll
look into this when I'm back from vacations, now is time to get busy in
the kitchen for tonight's dinner :-p

Happy new year to all OCA contributors ;)


-- 
Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com

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

      -- 
Lambda IS DOOEL - free/open-source information systems implementation & development

Kiril Vangelovski - consultant/developer 

web: https://www.lambda-is.com
tel: +38971753823
      by Kiril Vangelovski - 11:50 - 31 Dec 2020
    • Re: Upgrade / migration of OCA runbots today 
      Great work man. I've read your allnighter on twitter. What shall we do
without you ;-)

Have a great dinner and celebration tonight

Best Frederik

Am Dienstag, den 31.12.2019, 08:31 +0000 schrieb Alexandre Fayolle:

> On 29/12/2019 11:25, Alexandre Fayolle wrote:

> 

> > Hello

> 

> > 

> 

> > I'll work on upgrading the OCA runbots today. There will be a

> downtime

> 

> > of a few hours.

> 

> > 

> 

> > Best regards,

> 

> > 

> 

> Sorry for the delayed update notice.

> 

> The runbots are back up (since yesterday morning, actually).

> 

> The servers have been updated to the current stable Debian release,

> docker was updated to version 19, Odoo was upgraded to 11.0 using the

> wonderful OpenUpgrade project, PostgreSQL was upgraded to 10.0, the

> Runbot module was upgraded to the 11.0 version (without the docker

> improvements, because these are not compatible with the

> runbot_travis2docker module we are using).

> 

> Longer story available at

> https://twitter.com/gurneyalex/status/1211397322430697475

> 

> After some tinkering, I got the new stack to work ;) There is one

> issue

> with nginx I'll need to tackle: the build logs for builds which were

> made on runbot1-2 and runbot2-2 are not visible (HTTP error 404).

> I'll

> look into this when I'm back from vacations, now is time to get busy

> in

> the kitchen for tonight's dinner :-p

> 

> Happy new year to all OCA contributors ;)

> 

> 

> -- 

> Alexandre Fayolle

> Chef de Projet

> Tel : +33 4 58 48 20 30

> 

> Camptocamp France SAS

> 18 rue du Lac Saint André

> 73 370 Le Bourget-du-Lac

> France

> 

> http://www.camptocamp.com

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe

-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155
      by Frederik Kramer. - 11:01 - 31 Dec 2020

  • Proposing Enric Tobella as Maintenance PSC
    Hi,

    It is a small repository but lately both Creu Blanca and ForgeFlow teams have been working on it, adding features, fixes and doing migrations (now to v12 but likely soon to v13). None of the above teams have a PSC in maintenance and, in fact, there is only 2 PSC. Therefore, I'm proposing Enric Tobella as a new PSC to help here.

    Regards,

    --
    Lois Rilo Antelo - Odoo consultant at ForgeFlow
    twitter: @LoisRForgeFlow
    by Lois Rilo Antelo - 10:11 - 19 Dec 2019

    5 replies 5 replies

  • EPM application users list

    Hi,

    I was on a website today and thought would you be interested in EPM Application Users List around the globe? For your marketing and other business campaigns?

     

    Information fields: Names, Title, Email, Phone, Company Name, Company URL, Company physical address, SIC Code, Industry and Company Size (Revenue and Employee).

    We also have alternate users like: ERP, APM, TPM, CPM, PPM and many more.


     
    If you are not the right person, please forward to the right person in your organization.

    Regards,

    Stephen Robert

    Marketing Executive

     

                                     To opt out, please response Remove.

     


    by stephen robert <stephenrobert.us@yahoo.com> - 05:41 - 5 Dec 2019
  • 2020 OCA RFQS - CLOSE FRIDAY 6TH DECEMBER

    Hello Contributors.

    A reminder that the OCA 2020 RFQs close on Friday 6th December. (6pm, UTC)

    You can see more details here: https://odoo-community.org/page/rfq-process

    Open RFQs:
    ▪️Migration of www.odoo-community.org from Odoo 12 to Odoo 13
    ▪️2020 Graphic Designer
    ▪️ General Secretary
    ▪️ Systems Administrator
    ▪️ Accounting Expert

    If you have any questions or to register your interest please get in touch by sending an email to rfq AT odoo-community DOT org

    Warm regards,
    Rebecca
    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 12:10 - 5 Dec 2019
  • Maintenance on odoo-community.org server today circa 12:00 UTC+1 
    Hello,

I'm seeing a high load on the main odoo-community server which hosts
various services (our main instance, weblate, some databases...). Since
this server has an uptime of 171 days, I think I'll take the opportunity
to install the latest kernel updates and reboot the server which can't
do harm. Expect some downtime between 12:00 CET and 14:00 CET today.

Best regards



-- 
Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
    by Alexandre Fayolle - 08:55 - 2 Dec 2019

    3 replies 3 replies

    • Re: Maintenance on odoo-community.org server today circa 12:00 UTC+1
      Thanks a lot

      Bonne journée


      David BEAL - akretion.com
      Chef de projet
      Odoo Développement / Intégration


      Le lun. 2 déc. 2019 à 13:52, Alexandre Fayolle <alexandre.fayolle@camptocamp.com> a écrit :
      Maintenance done. All services should be back up. Please ping me if you
notice something's not working.

Thanks for your patience

Alexandre

On 02/12/2019 13:07, Alexandre Fayolle wrote:


> Rebooting now :)


> 


> On 02/12/2019 08:54, Alexandre Fayolle wrote:


>> Hello,


>>


>> I'm seeing a high load on the main odoo-community server which hosts


>> various services (our main instance, weblate, some databases...). Since


>> this server has an uptime of 171 days, I think I'll take the opportunity


>> to install the latest kernel updates and reboot the server which can't


>> do harm. Expect some downtime between 12:00 CET and 14:00 CET today.


>>


>> Best regards


>>


>>


> 


> 




-- 
Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com

      _______________________________________________
      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 - 02:05 - 2 Dec 2019
    • Re: Maintenance on odoo-community.org server today circa 12:00 UTC+1 
      Maintenance done. All services should be back up. Please ping me if you
notice something's not working.

Thanks for your patience

Alexandre

On 02/12/2019 13:07, Alexandre Fayolle wrote:

> Rebooting now :)

> 

> On 02/12/2019 08:54, Alexandre Fayolle wrote:

>> Hello,

>>

>> I'm seeing a high load on the main odoo-community server which hosts

>> various services (our main instance, weblate, some databases...). Since

>> this server has an uptime of 171 days, I think I'll take the opportunity

>> to install the latest kernel updates and reboot the server which can't

>> do harm. Expect some downtime between 12:00 CET and 14:00 CET today.

>>

>> Best regards

>>

>>

> 

> 



-- 
Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
      by Alexandre Fayolle - 01:51 - 2 Dec 2019
    • Re: Maintenance on odoo-community.org server today circa 12:00 UTC+1 
      Rebooting now :)

On 02/12/2019 08:54, Alexandre Fayolle wrote:

> Hello,

> 

> I'm seeing a high load on the main odoo-community server which hosts

> various services (our main instance, weblate, some databases...). Since

> this server has an uptime of 171 days, I think I'll take the opportunity

> to install the latest kernel updates and reboot the server which can't

> do harm. Expect some downtime between 12:00 CET and 14:00 CET today.

> 

> Best regards

> 

> 



-- 
Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
      by Alexandre Fayolle - 01:09 - 2 Dec 2019