Closed Bug 292639 Opened 20 years ago Closed 19 years ago

upgrade SFX to Drupal 4.6

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: asa, Assigned: mozillamonks)

Details

Daryl Houston said:
> There's a virtual host set up for the dev site under /var/www/html, and
> there's a database named (I think) spreadfirefox_dev. I had started the
> upgrade but ran into problems with the database upgrade and was
> considering just having a fresh start with a new install, but writing a
> script to import all of our data. As for modules, the main blocker is
> the images module. The others that were a problem were privatemsg (which
> Robin tweaked) and buddylist, which is apparently upgraded somewhere.

Daryl, is the "images module" the same as "gallery"
<http://drupal.org/project/gallery> ? What about this is blocking us? Is our
gallery not compatible with the Drupal one (possibly customized by CivicSpace?)

Apparently Drupal 4.6 has "Improved multi-site support to run multiple Drupal
sites from a single code base." so maybe we want to consider this if we're going
to be using Drupal elsewhere at mozilla.org.
No, this appears to be a different image management module. Which is not to say
that it might not suffice for sfx, though I suppose you'd lose the old images if
you switched over to this. My recollection of the image module we're using is
that it's partially ported but that some major enhancements are in the works
that are gumming up progress. Actually, according to the CivicSpaceLabs roadmap
(http://civicspacelabs.org/home/developers/roadmap), the image module now works
in 4.6, so download and give it a shot.

Regarding multi-site functionality, that's actually possible without terribly
much pain even in the version we've got, and I had implemented it in a test bed
long ago, but we never pulled the trigger. I forget why.
Summary: upgrade SFX to Drupal 4.6 → upgrade SFX to Drupal 4.6
thanks for the follow-up daryl. 

Robin, are you interested or able to help us out with this upgrade? 
(In reply to comment #2)
> thanks for the follow-up daryl. 
> 
> Robin, are you interested or able to help us out with this upgrade? 

Sure, I'm guessing SFX is running on the latest CivicSpace right now, so an
upgrade to Drupal 4.6 should only be a minor headache.  It realy all depends on
how different CivicSpace treats the MySQL database.

If it's just Drupal 4.5 with some extra modules, then it can be done in 2 hours.

Robin
Upgrading is liable to be a real pain, actually. I don't remember right off what
version we're on, but I believe it goes back to just before 4.5, even.
Additionally, there are tweaks to a number of modules, some to fix bugs that may
no longer exist in Drupal/CSL, others to add or modify functionality (node
rating, for example, is a hack to the node module). In other words, be sure to
save a copy of the current tree. The affiliates module is in pretty disgraceful
shape and in fact isn't being used to track incoming hits b/c the Drupal
overhead's too much to invoke for each such request. If you can do it in less
than two hours and without a major headache, I'll be shocked. Kieran at Civic
Space Labs was interested in helping out with an upgrade, but that was before
Chris left the sfx team, and they may be less willing to lend a hand now. Might
be worth looking into, though.
(In reply to comment #4)
> Upgrading is liable to be a real pain, actually. I don't remember right off what
> version we're on, but I believe it goes back to just before 4.5, even.

OK, as long as it is *around* there, and there is no major SQL changes, then it
should be easy.
> Additionally, there are tweaks to a number of modules, some to fix bugs that may
> no longer exist in Drupal/CSL, others to add or modify functionality (node
> rating, for example, is a hack to the node module). In other words, be sure to
> save a copy of the current tree. 
Dosn't realy matter, as the old files are deleted and new ones added during an
upgrade, only the SQL is left.
> The affiliates module is in pretty disgraceful
> shape and in fact isn't being used to track incoming hits b/c the Drupal
> overhead's too much to invoke for each such request. If you can do it in less
> than two hours and without a major headache, I'll be shocked. 

Hmm, do I hear a challenge :)
> Kieran at Civic
> Space Labs was interested in helping out with an upgrade, but that was before
> Chris left the sfx team, and they may be less willing to lend a hand now. Might
> be worth looking into, though.

Nah, we realy should use Drupal, as CivicSpace is a little bloated with excess
modules that we won't need.

Robin


(In reply to comment #5)

> Nah, we realy should use Drupal, as CivicSpace is a little bloated with excess
> modules that we won't need.

You should just go ahead with Drupal 4.6 and add the CS modules later. SFX isn't
really using our modules anyway, so you just need a list of the non-standard
ones to port... I actually think 9/10 of them have already been done. Getting on
4.6 will make your lives SOOO much easier.
Is this something you're actually going to need my help with, or do you have
folks that can take care of it?  (Just trying to sort my buglist :) )
(In reply to comment #7)
> Is this something you're actually going to need my help with, or do you have
> folks that can take care of it?  (Just trying to sort my buglist :) )

It should be rather simple, just a few MySQL and file changes.  The only way for
it to get compilcitated is if we get /.'ed during the actualy move. ;-)

I also have my permissions to the sever too, so I need to know:>
What folder to upgrade to 4.6?
We test initaly, right, then make it live?
Is PHPMyAdmin on the server?

Robin
Status: NEW → ASSIGNED
looks like you meant to take this...
Assignee: justdave → mozillamonks
Status: ASSIGNED → NEW
Robin, there's a dev site and a dev database. I'd copy the production stuff over
to there and upgrade there first. Look under /var/www/html to find the two
sites. You'll then need to go into the community directory to get to the actual
docroot.

The database actually lives on salamander, and I doubt there's phpmyadmin,
though you should be able to access the db from the cli utility from hornytoad.
Note also that you'll have to ssh to hornytoad and not sfx, thanks to the proxy.
You'll get denied otherwise.
Actually, the database is on reptile, and the only proxy we're currently using
is also on hornytoad.  (salamander got moved back to UMO duty a month or two ago)
(In reply to comment #11)
> Actually, the database is on reptile, and the only proxy we're currently using
> is also on hornytoad.  (salamander got moved back to UMO duty a month or two ago)

OK, you're scaring me now.  How shall I acces these databases?

Anyways, mpanel (http://www.mattsscripts.co.uk/mpanel.htm) would be just as
good, and it's easy for someone with access to install.

Until then, I'll just use the password settings in the dev config to edit the
database on a local copy of PHPMyAdmin.

Robin
Yeah, you can use the username, password, and host from the sfx config to
connect to the database, from hornytoad.  I usually just use the mysql
command-line client.  It is firewalled, so you'll need to ssh port-forward port
3306 off of hornytoad in order to use a GUI or web client from your local machine.

ssh -L 3306:reptile:3306 self@hornytoad.mozilla.org

Then point your client at localhost and use the username/pass from the sfx config.
Oddly enough, when I run mkdir or cp -r I get "Cannot create directory blah:
Permission denied"

Robin
I've added you to the devel group and made sure that group has write access on
all files in the production and test directories. I didn't set a umask or
anything, so  you might not be able to edit files others stick in there, but
this should get you started for now, at least.

My bad on the salamander reference earlier. I meant to say reptile for the db.
I was wondering if it would be too much trouble to create a copy of the SFX
database for testing?
Already exists. I think it's spreadfirefox_dev. I think I had probably already
slurped in the new db and started the alterations, but you'll want to start from
scratch.
(In reply to comment #17)
> Already exists. I think it's spreadfirefox_dev. I think I had probably already
> slurped in the new db and started the alterations, but you'll want to start from
> scratch.

Yeah, that would be perfered.  If all goes well I can get update.php to work
some wonders.

Robin
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
This was fixed by Ian and Paul of Glaxstar with assistance from Mozilla sysadmins.
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.