aufs based upgrade tests

Michael Vogt mvo at
Mon Mar 16 18:00:12 UTC 2009

On Sun, Mar 15, 2009 at 02:27:16AM -0400, John Vivirito wrote:
> On 03/14/2009 10:13 AM, (``-_-´´) -- BUGabundo wrote:
> > Olá Michael e a todos.
> > This idea seems like a really nice idea, and one that in some other form is requested by users/testers.
> > I would like to add to points:
> > * if all tests go OK, and we end up with this on koala (to late for FFe on jaunty, right?), a checkbox when using update-manager -d / cli question on do-release-upgrade to use Sandbox would be much nicer then running all that code.
> > * to save the system state prior to upgrade, so that a user can restore the system if even after successful package upgrade, some application/kernel/driver upgrade doesnt go as good.
> > 
> I am a bit on the short end of this topic due to trouble with having
> this set to digest mode. What exactly is this going to do. It sounds
> very interesting. is this similar to "system restore" in windows?
> The following quote makes it sound like after reboot it is going to
> restore itself to before the latest upgrade:
> >  All writes go into /tmp so after the upgrade and on the next
> >>> reboot the system is back to its pre-upgraded state again 

Right now its a tool to help test if your version of ubuntu can
upgrade to the next version of ubuntu without errors. It does a
full regular upgrade from 8.10 to 9.04 but instead of writing it to
the system disk it writes all changes to a directory in /tmp
> Doe the above always write to /tmp? If so does it clear upon restart
> automatically?

Yes, after the upgrade the system will be jaunty until the next
reboot, then the writable overlay is removed and the system is exactly
in the same state as before the upgrade.

> Is there somewhere where i can get more information on it, a wiki or,
> blueprint or something?

Unfortunately not right now. I created as a stub wiki page:

and we will probably talk about it at the next UDS and create a more
formal plan. The currently version is build to get experience with the
system and fint bugs and limitations with the aufs based approach,
this is why its relatively complicated to enable it.


More information about the Ubuntu-devel-discuss mailing list