Contributors

• Re: [SPAM] Re: Odoo OpenUpgrade Wizard status ?

  hello,
  
  thank you holger for mentioning your script, which i did not know about. i did not look into it yet to understand its internals, but its goal seem very similar to the one of odoo openupgrade wizard (oow for short). i would love to see an effort inside the oca to bring people together around one solution to avoid wasted efforts everywhere.
  
  when we started the oow project with sylvain and rémy almost 3 years ago (already!), it was because of discussions between us about all the effort that is required to set up a correct environment to run openupgrade and how time-consuming mistakes can be in that process, as feedback is really slow, especially with huge databases.
  
  at coop it easy we had a set of (bash) scripts to help run migrations and sylvain at grap had already created something more advanced in python. oow is the evolution of sylvain’s tool, with contributions mainly from rémy.
  
  concerning its maturity, it has evolved quite a bit since its inception, and at coop it easy we’ve been using it for all of our client migrations since last year. that said, it’s not perfect: it’s quite opinionated and still a little rough around the edges (for example: debugging docker build errors requires to relaunch the command manually to see the output), but i’ve personally been using it to migrate multiple databases, most of them simultaneously using the same environment.
  
  in summary: it’s ready for production use. feel free to use it and report issues or propose fixes and improvements.
  
  in the long run, we think it should be part of oca’s tooling.
  
  kind regards,
  
  hugues
  
  

  ---

  by hugues - 11:41 - 15 Jan 2025

• Re: Odoo OpenUpgrade Wizard status ?

  
  

  
  

  El mié, 8 ene 2025 a la(s) 9:17 a.m., Росен Владимиров (notifications@odoo-community.org) escribió:
  

  My experience: The logic of OpenUpgrade tools from OCA is not relevant in all cases. The tool is based on logic: Convert sql database with new version of modules and move version step by step and change all modules to have all versions.

  Better way is to prepare new versions with correct modules and to import from old records using the OdooRPC tool. I migrate from 11.0 to 16.0 and to 17.0 using my script The logic there is to import data from old databases to convert in script and to import results in new databases. The trick is to save an external indication link to the old database record id, after which it is possible to move data from the live old database importing again if something is changed. The problem of the script is to have experience in all versions to find differences in data.
  

  
  

  This option in huge DB's or, in most cases is incorrect. The ID of the record failed to keep it in track and business logic do not comply with odoo way of working, this way of migrate is valid only to reestart DB's

  
  

  
  

   

  
  

  Thanks,
  Rosen Vladimirov
  +359886100204
  

  
  

  
  

  На вт, 7.01.2025 г. в 15:52 Holger Brunn <notifications@odoo-community.org> написа:
  

  I can't comment on the maturity of this tool, but wrote one myself mainly with 
  the idea to make the project more accessible for new contributors:
  https://github.com/hbrunn/OpenUpgrade/tree/run-migration
  (you'll have to replace oca with hbrunn in the code snippet)
  
  As for the matureness of this: Works pretty well, but as anything relying on 
  OpenUpgrade it's not very robust against malformed data or other unexpected 
  conditions. So while things *can* work great without any user intervention, 
  there's always a chance you'll need to adapt your data to the upgrade scripts' 
  expectations (or change those), and that will usually require deep technical 
  knowledge about the Odoo versions involved.
  
  
  
  
  -- 
  Your partner for the hard Odoo problems
  https://hunki-enterprises.com

  _______________________________________________
  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
  

  
  

  
  

  --
  

  Nhomar G. Hernández M. about.me/nhomar

  ---

  by Nhomar Hernández - 06:51 - 8 Jan 2025

• Re: Odoo OpenUpgrade Wizard status ?

  My experience: The logic of OpenUpgrade tools from OCA is not relevant in all cases. The tool is based on logic: Convert sql database with new version of modules and move version step by step and change all modules to have all versions.

  Better way is to prepare new versions with correct modules and to import from old records using the OdooRPC tool. I migrate from 11.0 to 16.0 and to 17.0 using my script The logic there is to import data from old databases to convert in script and to import results in new databases. The trick is to save an external indication link to the old database record id, after which it is possible to move data from the live old database importing again if something is changed. The problem of the script is to have experience in all versions to find differences in data.
  

  
  

  Thanks,
  Rosen Vladimirov
  +359886100204
  

  
  

  
  

  На вт, 7.01.2025 г. в 15:52 Holger Brunn <notifications@odoo-community.org> написа:
  

  I can't comment on the maturity of this tool, but wrote one myself mainly with 
  the idea to make the project more accessible for new contributors:
  https://github.com/hbrunn/OpenUpgrade/tree/run-migration
  (you'll have to replace oca with hbrunn in the code snippet)
  
  As for the matureness of this: Works pretty well, but as anything relying on 
  OpenUpgrade it's not very robust against malformed data or other unexpected 
  conditions. So while things *can* work great without any user intervention, 
  there's always a chance you'll need to adapt your data to the upgrade scripts' 
  expectations (or change those), and that will usually require deep technical 
  knowledge about the Odoo versions involved.
  
  
  
  -- 
  Your partner for the hard Odoo problems
  https://hunki-enterprises.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 Rosen Vladimirov - 04:15 - 8 Jan 2025

• Re: Odoo OpenUpgrade Wizard status ?

  I can't comment on the maturity of this tool, but wrote one myself mainly with 
  the idea to make the project more accessible for new contributors:
  https://github.com/hbrunn/OpenUpgrade/tree/run-migration
  (you'll have to replace oca with hbrunn in the code snippet)
  
  As for the matureness of this: Works pretty well, but as anything relying on 
  OpenUpgrade it's not very robust against malformed data or other unexpected 
  conditions. So while things *can* work great without any user intervention, 
  there's always a chance you'll need to adapt your data to the upgrade scripts' 
  expectations (or change those), and that will usually require deep technical 
  knowledge about the Odoo versions involved.
  
  
  -- 
  Your partner for the hard Odoo problems
  https://hunki-enterprises.com

  ---

  by Holger Brunn - 02:51 - 7 Jan 2025

  1 attachments 1 attachments

  signature.asc

• Re: Odoo OpenUpgrade Wizard status ?

  Interesting and -as per the idea- very valuable effort but it is not part of the "official" OCA tools / code as it resides in a repo outside GH. Maybe https://gitlab.com/legalsylvain and Rémy Taymans as the inventors of this can comment on its state of maturity and even better potential future ideas of injecting it to the official OCA repos

  Best Frederik
  

  Am 07.01.25 um 11:43 schrieb Rolando Pérez Rebollo:
  

  Hello dear friends,

  I'm exploring the idea of using Odoo OpenUpgrade Wizard for some customer upgrade projects. From the OCA presentation, it seems like a promising tool.

  The GitLab repository appears active, with the latest release in November. However, I’m wondering if it’s mature enough for production use or if it’s still in its early stages. Is the potential of being an early adopter worth it?

  Is anyone here actively using it in their projects? I’d love to hear your thoughts or experiences!

  --
  

  Rolando Pérez Rebollo Python and Javascript Senior Developer Binhex r.perez@binhex.cloud Office (Spain) : +34 822 17 92 67 Office (USA): +1 305 686 8151

  Offices: Miami | 8325 NE 2nd Ave, Miami, FL 33138, United States Texas | 27027 Westheimer Pkwy Katy, TX 77494, United States Tenerife | Street Subida al Mayorazgo, 13, Office 15-2 Las Palmas | Edificio Polivalente IV Campus de Tafira Parque Tecnológico de Gran Canaria

  Start for free: Try Odoo Community in the cloud

  This email is confidential and intended only for the recipient. If you are not the intended recipient, please notify the sender and delete it immediately. Privacy Policy

  _______________________________________________
  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
  Innungsstraße 7
  21244 Buchholz i.d.N.
  
  Tel:   +49 (0) 4181 13503 12
  Fax:   +49 (0) 4181 13503 10
  Mobil: +49 (0) 179 3901819
  
  Email: frederik.kramer@initos.com
  Internet: www.initos.com
  
  Geschäftsführung:
  Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
  
  Sitz der Gesellschaft: Buchholz i.d.N.
  Amtsgericht Tostedt, HRB 205226
  USt-IdNr.: DE815580155
  Steuer-Nr: 15/200/53247

  ---

  by Frederik Kramer - 11:56 - 7 Jan 2025

1 more replies