[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Downtimeless upgrades

Hi Chris,

I am wondering, what about an automated upgrade process?

For example the workflow could be this:

This is a draft idea, really need polish: what about already logged users/transactions, how to detect in runtime the changed files and version changes etc.

But that would be reaaaallllllyyyyyy comfortable :)





----------------eredeti üzenet-----------------
Feladó: "Chris Travers" <..hidden..>
Címzett: "Development discussion for LedgerSMB" <..hidden..>
Dátum: Wed, 26 Feb 2014 22:46:22 -0800

Hosting providers for LedgerSMB may appreciate the downtimeless upgrade structure in 1.3.38.  This allows one to tell LedgerSMB to temporarily stop checking database version numbers on requests.  The idea is that this gives you time to update the system without kicking users off.
This will be first available when upgrading to 1.3.39.
To do a downtimeless upgrade, do the following:
1.  select setting_set('ignore_version', '1');
if in a transaction, commit.
2.  Update the files.
3.  Run the setup.pl to update the dbs
4.  in psql: select setting_set('ignore_version', '0');
Verify both version settings and the ignore_version setting.
This is aimed at instances where everyone on a single instance is on the same version.  It is not intended to address cases where a company accesses dbs on the same db server across major versions.  Accidently logging into a db on another version has undefined consequences if you do more than log in.
Best Wishes,
Chris Travers
Efficito:  Hosted Accounting and ERP.  Robust and Flexible.  No vendor lock-in.

Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.

Ledger-smb-devel mailing list