where is process-csv.py ?

This readme is pretty outdated.

Depending on what you want to do, the good documentation is http://openupgrade-server.readthedocs.org/en/latest/analyse.html (to analyse the changes between different versions of a database for writing you own migrations scripts, I don't believe that's what you want to do) or https://openupgrade-server.readthedocs.org/en/latest/intro.html#migrating-your-database (just do a migration).

For running a migration, there is a helper script that does all the steps mentioned above: http://bazaar.launchpad.net/~openupgrade-committers/openupgrade-server/6.1/view/head:/scripts/migrate.py

Hi Holger ,

Thanks for the replies and after much changes in v7.0 in terms of getting a more enterprise look , we as a community really need this upgrade project to stay alive for alternative.

And I do have some questions regarding about how to get the upgrade server run . so let me what steps is the correct one,

Migration from 5.0 to 6.0

1. download and run openupgrade server v5.0 by pointing to my own v5 addons directory. then install the
    [openupgrade_records] found . ( do not work on the live but to backup and restore one for this migration test)
   as i could not find any version 5 addon modules , so i presume it is pointing to my own v5 addons folders.

2. download and run openupgrade server v6.0 by pointing to openupgrade v6.0 addons directory , then create the
    new target db , install all the necessary modules which found in my v5 database including the [openupgrade_records]

3. compare the database , by issuing the command with point to the database you want to upgrade,
    which defined at item 1 above
    and add the –update all –stop-after-init flags.

4. read and log file and the manually write the pre and post migration script or use the scripts that you pointed ,
http://bazaar.launchpad.net/~openupgrade-committers/openupgrade-server/6.1/view/head:/scripts/migrate.py

5. try and continue test until the db is migrated over to v6.0.

Thanks for your ansers.

Kalmen,

forget about all the stuff concerning comparing databases. This is only necessary for *developing* migration modules.

Do do a migration, you just have to

* Download the 6.0 branch of openupgrade-server *and* openupgrade-addons (you want to upgrade *to* 6.0)
* Create a config file that points to their addons directories (openupgrade-server contains base, openupgrade-addons the rest)
* run this server with parameter --update=all

If all went well, you can use this database with your regular 6.0 installation now.

The script I mentioned is meant to automate all that, so another way to do the migration is

* download the script
* run migrate.py --config=[your production config file] --database=[your database name] --run-migrations=6.0
* wait for ages

That's it.

If you want to go to 6.1 immediately, just run
migrate.py --config=[your production config file] --database=[your database name] --run-migrations=6.0,6.1
and wait longer.

The migration for 7.0 is work in progress, I wouldn't advise you to do that right now.