Re: [midgard-user] Migrating Content to Sitegroups

[Philipp Rotmann, Linksystem Muenchen]

On 02.02.01 (22:33), Fred Hirsch wrote:
> Well, I looked at my old package, decided to remove it without
> looking at dates and then grabbed the new one from the Midgard
> site. The dates on the files are Dec 29, so I figured they
> must still be old, so I grabbed a CVS copy.. 

Dec 29 would've been o.k., but CVS isn't bad either, I suppose.

> The only major change I see is the Asgard+Admin+VMUC.sql file
> that was added, and an updated xsg.conf. Everything else is
> the same.

Can't say much about that.

> On with the show:
>     - DB Backup, check.
>     - New DB, called midgard2, check.
>     - Ripped midgard-data from CVS (gotta be newest, right?), check.
>     - empty.sql, check.
>     - midgard-en.sql, check.
>     - update-snippet-admin.sql, check.
>     - GUIDSforOLDSITE.sql, check.
>     - Create a new blobdir (mkdir -p /home/httpd/blobs2), check.
>     - Create midgard user (granted midgard rights to midgard2), check.
>     - Change repligard.conf (dbname and blobsdir), check.
>     - Repligard AsgardSite.xml... oops, forgot to copy the blobs (copied
> from previous 1.4 install).. ok, check.
> 
> So far, so good.

Oookay, part II:

First adjust the new database's host table in order to get
Asgard working. Check your login and access rights as root in
SG0 by creating the needed additional sitegroup(s): Sitegroup ->
Create Sitegroup. Along with your sitegroup an admin group in
this SG is created whose name seems to be bound to the
sitegroup's name even if you supply another one (that would be a
bug in Asgard -- can anyone confirm this behaviour?). All other
modifications to the new sitegroup could only be made after
relogging as <admin-user>+<new-sitegroup> (where <admin-user>
means a user who is member in the Midgard Admin group (#0) -- at
this point this should only be the standard 'admin'
('password'), if you haven't already created users or changed
the admin password. But empty sitegroups are the best starting
point for your re-import, so just confirm that you are able to
log in to the new sitegroup.

If you're working at a production system and can't afford much
downtime, you could either set up another apache instance with
another configuration to work with the new database while the
old sites keep running, or you could create the new sitegroup(s)
directly via the mysql command line interface (more on that if
needed).

After having created a brand new and clean Midgard 1.4 database,
make a backup of it for the case you would later have to go back
to this state.

For every new sitegroup you created, do the following:

Then edit a copy of repligard.conf and 
 - change the database to your new db's name,
 - change the blobdir to its new location and
 - change the login information to the username and password you
   just used to successfully log into the new sitegroup.

Now (this is the last point to freeze changes on the old
database and create a current dump of SG0) use this modified
repligard.conf to import your whole SG0 into the new
sitegroup(s):

  repligard -c /path/to/modified/repligard.conf -i SG0.xml.gz

(end foreach ;-))

In order to keep downtime to a minimum, you can now (either via
Asgard -- then switch databases _now_ -- or via the mysql
command line interface again) edit your host table in order to
get the right version of every site working: Disable admin sites
in sitegroups <> SG0 and disable all other sites in the
sitegroups they don't belong to, in order to have exactly one
record per name:port/prefix combination marked online. Then your
sites should be back at work, and you can clean up your
database. You could now simply use Asgard to remove all host,
page, style and topic trees as well as groups, users and
snippetdirs (if you already had those) you don't need in that
sitegroup -- esp. the admin sites, of course.

     Good luck again!
     phr
-- 
Linksystem Muenchen GmbH                          [EMAIL PROTECTED]
Schloerstrasse 10                           http://www.link-m.de
80634 Muenchen                              Tel. 089 / 890 518-0
We make the Net work.                       Fax 089 / 890 518-77

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]