Two side-by-side installations

We’re about to migrate RT to our own servers. During the transition and
testing phase, we want to run 2 side-by-side installations so we can
work with 3.8.10 and 4.0.1 and see which one works for us better.

What’s the best way to do this? Debian Stable will be the underlying OS.

VM? change paths in the config file?

I’m not very familiar with VMs in a backoffice setup. If we go the VM
route, what’s the preferred VM to use? I use VirtualBox but that’s more
of an end-user GUI type of setup. I’m not familiar with too many of the
others.

Few people are capable of expressing with equanimity opinions which differ from the prejudices of their social environment. Most people are even incapable of forming such opinions.
Albert Einstein

We’re about to migrate RT to our own servers. During the transition
and testing phase, we want to run 2 side-by-side installations so we
can work with 3.8.10 and 4.0.1 and see which one works for us
better.

What’s the best way to do this? Debian Stable will be the underlying OS.

VM? change paths in the config file?

Since you mention you’ll be running Debian squeeze (stable), I’ll
outline one possible approach which involves a single server.

request-tracker3.8 is the Debian package of RT 3.8. It is in squeeze.
request-tracker4 is the Debian package of RT4.0. It is in squeeze-backports.

You can install both of these side by side, and have both running
alongside each other, as long as you use the mod_fastcgi or mod_fcgi
mode, rather than the mod_perl mode.

[disclosure: I’m the Debian maintainer of those packages]

Cheers,
Dominic.

Dominic Hargreaves, Systems Development and Support Team
Computing Services, University of Oxford

signature.asc (198 Bytes)

Dominic Hargreaves wrote:> On Fri, Aug 05, 2011 at 05:02:41AM -0700, Yan Seiner wrote:

We’re about to migrate RT to our own servers. During the transition
and testing phase, we want to run 2 side-by-side installations so we
can work with 3.8.10 and 4.0.1 and see which one works for us
better.

What’s the best way to do this? Debian Stable will be the underlying OS.

VM? change paths in the config file?

Since you mention you’ll be running Debian squeeze (stable), I’ll
outline one possible approach which involves a single server.

request-tracker3.8 is the Debian package of RT 3.8. It is in squeeze.
request-tracker4 is the Debian package of RT4.0. It is in squeeze-backports.

You can install both of these side by side, and have both running
alongside each other, as long as you use the mod_fastcgi or mod_fcgi
mode, rather than the mod_perl mode.

[disclosure: I’m the Debian maintainer of those packages]

That sounds like the way to go. I’ve looked around the wiki and
mod_fastcgi installation doesn’t seem to be well documented. Any hints
on how to proceed?

Few people are capable of expressing with equanimity opinions which differ from the prejudices of their social environment. Most people are even incapable of forming such opinions.
Albert Einstein

That sounds like the way to go. I’ve looked around the wiki and
mod_fastcgi installation doesn’t seem to be well documented. Any
hints on how to proceed?

If you follow the Debian route, you’ll find that the main thing
you need to do is to edit

/etc/request-tracker3.8/apache2-fcgid.conf
/etc/request-tracker4/apache2-fcgid.conf

(for example)

to suit your requirements, and then include that from the relevant
vhost portion of your Apache config.

I’m not sure what the wiki says about Debian; I suspect it’ll be a
collection of tricks and hacks built up over the years which may not
all be relevant. The usual Debian advice applies; after installing
the package with apt-get, check README.Debian which has various pointers
to relevant documentation.

Dominic Hargreaves, Systems Development and Support Team
Computing Services, University of Oxford

signature.asc (198 Bytes)

We’re about to migrate RT to our own servers. During the transition and
testing phase, we want to run 2 side-by-side installations so we can
work with 3.8.10 and 4.0.1 and see which one works for us better.

Keep in mind you can’t have them pointed at the same database.

4.0 is the stable release series. 3.8 will be only maintenance going
forward, so you’re going to want to upgrade at some point anyway. Is
there something about 4.0.1 that makes you think 3.8.10 will work better?

Thomas