airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chathuri Wimalasena (JIRA)" <>
Subject [jira] [Commented] (AIRAVATA-641) Develop a Registry Migrator tool to assist with backward compatibity
Date Wed, 23 Jan 2013 19:31:15 GMT


Chathuri Wimalasena commented on AIRAVATA-641:

Registry migrate tool will do following tasks at the moment.
   * In airavata 0.6, we added new columns for Configuration table and Node_data table. If
some user wants to upgrade to airavata 0.6 keeping the 0.5 database, this tool will be helpful.
It will alter above mentioned tables and their primary key constraints. After migrating, users
should be able to work with airavata 0.6 which will pointing to the previous database 
   * Simple script file is available where users need to pass JDBC url, JDBC username and
JDBC password 
> Develop a Registry Migrator tool to assist with backward compatibity
> --------------------------------------------------------------------
>                 Key: AIRAVATA-641
>                 URL:
>             Project: Airavata
>          Issue Type: New Feature
>            Reporter: Suresh Marru
>            Assignee: Chathuri Wimalasena
> As we are starting to see Airavata being used in production by friendly users, we need
to ensure backward compatibility and also switching between releases. A Airavata-Migration-Tool
might help here. The migration tool should assist with two tasks:
> * say if I deploy airavata 0.5 on a tomcat, i want to deploy a new 0.5, the migration
tool should be able to export the data and import into new deployment. A database dump and
restore might work, but the trick here is to make sure the security mappings and gateway id's
and so on correct.
> * going forward with every release we probably want to ship the migrator tools, so users
with previous version deployments can migrate to newer ones adapting to any registry schema

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message