I don't mind signing up again.
 
The longer we support a kludge of things, the harder it gets for any other
upgrades in the future.
 
Better to bring things into line with the new working stuff, then to try to
make the new stuff work with the old.
 
And Easier too.
 

  _____  

From: plug-discuss-bounces@lists.plug.phoenix.az.us
[mailto:plug-discuss-bounces@lists.plug.phoenix.az.us] On Behalf Of Lisa
Kachold
Sent: Tuesday, June 16, 2009 7:14 AM
To: Main PLUG discussion list
Cc: der.hans; The PLUG Web Site Development Discussion List; der.hans
Subject: Verari 1U New Server Build && Drupal Upgrade for New PLUG Site


I have build up and burned in the Verari 1U server (under OS specified by
"the boys" [I would have preferred CentOs 5.3 network build hardened
kernel]) [it was only failing drive recognition due to no tiny MASTER/SLAVE
pins].

I have hardened and added various other excellent tools (details sent to
Hans 65 days ago).

I have built a Drupal for the current PLUG site/server running 6.2 on port
81.
I have built a Drupal for the new server running 6.3.

I have evaluated current PLUG site Drupal database table structure for the
purposes of upgrading and found that we are using modules that are not
Drupal 6+ compatible.  All of our data is located in the modules.  Hans went
on at length at the last HackFest with some strange ideas that "I should be
able to seamlessly upgrade Drupal (even via an apt-get from Ubuntu)" which
might be true for the core, but certainly not the modules.  Additionally,
the current PLUG Drupal has some upgrade <ahem!> "anomolies" <read former
upgrade issue or module incompatibilities in that some features and
functions don't work (like the export database functions, date event
reocurring functions, etc.>.  Most of the core upgrades require as part of
the steps an export function.  

I have attempted to just use mysql and just dump the database and import
selectively to new version, but since the entire module/data (OpenID/all
role based events/signups) table structure is different, we will need to
repopulate all the old data to the new SITE manually.
It's funny but the Mail plugins for the list server are still the same,
however use new OpenID core.

Our choices are probably going to be:
A) Stay in old Server/Site (security issues and other problems)

B) Use New Server/Site
1) Manually repopulate data.
2) Ask everyone to re-signup.

Some people also contend that the old cactus penguin logo and site layout
seriously need upgrading!

I actually have a good deal more experience with drbd in web systems than
Drupal. [ Let me setup the existing PLUG server and this one to fail over?
Laugh - I know you have "the people who donated this server" as experts on
drbd.]  

Please advise.  I would happily work on this with:

1) Vast heartfelt appreciation and respect aka THANKS!
2) Good direction/choices!
3) Disgression to do what must be done!
4) Creative license to make some much needed changes!
5) Assistance and buy in from other volunteers!

I will bring the Verari 1U <screaming fast> server to be placed into the NOC
(it's ready) tonight to Stammtiche on Broadway.

See you there!
-- 
(503)754-4452
http://en.wikipedia.org/wiki/User:LisaKachold
http://www.theregister.co.uk/2009/05/29/wikipedia_bans_scientology/