2017-05-30 14:06 GMT+02:00 Sergi Almacellas Abellana <[email protected]>: > El 30/05/17 a les 12:21, Dominique Chabord ha escrit: >> >> my questions are : >> - what is the roll-back procedure in case some problems appear at any step >> ? > > > If you are using a new virtualenv just have a backup of your database and > you have it. If everything does not go well, restore the backup and use the > previous version code.
This was a question to Axel about rpm, at OS level iiuc. Do you know how to revert a rpm upgrade ? > >> - is there a dry-run possibility without stopping production ? > > > It's possible but when you run the database upgrade you may get blocked with > existing transactions, especially when modifying the structure of a table > used by a lots of users. The procedure will be: > > 1. Deploy the new version code: > 2. Upgrade the database structure while not stopping the previous server. > (Here is when bad things can happen) > 3. Stop the old server and start the new one. if you use rpm strategy, I think you cannot run two versions on the same machine. This was the question. > I share Axel idea and it would be nice to update Tryton as we update postgresql, but I think we cannot (yet ?) -- You received this message because you are subscribed to the Google Groups "tryton" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton/CAHZrxK66vvi5TC5iLbc9z4VTM9pLc3GqFct7vXsVzDcFjgETtQ%40mail.gmail.com.
