Sorry, did not reply to the list.
From: "Jason Guiditta" <jguiditt(a)redhat.com>
To: "Justin Clift" <jclift(a)redhat.com>
Cc: "Javier Pena" <javier.pena(a)redhat.com>, "aeolus-devel"
<aeolus-devel(a)lists.fedorahosted.org>
Sent: Wednesday, June 20, 2012 5:51:20 PM
Subject: Re: Data safety for our Fedora releases... :)
On 21/06/12 01:45 +1000, Justin Clift wrote:
>On 21/06/2012, at 1:27 AM, Javier Pena wrote:
><snip>
>> RHEV-M is following a very similar approach. They have psql
>> scripts covering each database schema change since the first
>> release, and each new package applies the delta between schema
>> versions. According to our local RHEV-M developer, Eli Mesika
>> designed this schema, so you may want to contact him for more
>> details.
>
>It's definitely a useful data point. Have seen this approach used
>for
>other applications before, and work well. Not fast, but does the
>job.
>
>+ Justin
>
>
How does this approach handle making sure no service is touching the
database while the upgrade happens, and that any such services get
restarted afterward so they continue to work?
What I see from the rhevm-upgrade script is that it stops the JBoss service before the DB
update, and then starts it at the end of the process.
Javier
-j