[Twisted-Python] trac's reliability

Jean-Paul Calderone exarkun at divmod.com
Mon Nov 27 21:12:05 EST 2006

On Mon, 27 Nov 2006 15:12:50 -0800, Cory Dodt <corydodt at gmail.com> wrote:
>I support using foom's /usr/local compiled SVN 1.4 on wolfwood as-is, and
>migrating to fsfs.  I have used fsfs a bit here, and I'm confident that it
>will not lose data.  If we migrate the SVN database, it might actually make
>a server-wide upgrade to a supported (recent) OS a little easier.

FWIW, http://subversion.tigris.org/issues/show_bug.cgi?id=2467

But sure, upgrading to svn 1.4.2 on wolfwood is probably reasonable.  I'm not sure whether I'd rather see a /usr/local/ install or a systemwide upgrade to a newer version of Debian or Ubuntu.  However, it doesn't really matter which I'd rather see, since I am not wolfwood's sysadmin, and that is for whom this is a choice.

>I wouldn't recommend using a /usr/local compiled postgresql, however.  If we
>switch to a pg backend for trac, I have a hunch things will go smoother if
>the server-wide upgrade is done first.

Quite, I don't think anyone is thinking about doing this. :)

>In my head the basic plan looks like:
>1- migrate to fsfs on a recent SVN.  Watch for improvements in trac.  If
>trac starts to behave, stop here.

You skipped some steps here, but yes, this sounds like a reasonable thing to start with.

>2- upgrade wolfwood server.  Watch for improvments in trac.  Upgrade pyramid
>while you're in there. ;-)  If trac improves, stop here.

This won't have any noticable effect on trac, since trac doesn't interact with any components on wolfwood directly (nor use anything of significance from the system-wide installs of anything on pyramid).

>3- Migrate backend to pgsql.  Watch for improvements in trac.  If trac
>doesn't improve, migrate to something not-trac.

Making this the second step (again with some explicit pieces missing, like porting any tools we need to port), and I don't have anything to suggest we do before this.

>Yes, I am volunteering my time.  I don't currently have any permissions on
>these servers apart from commits.

Great, thank you.


More information about the Twisted-Python mailing list