You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Suresh Marru (JIRA)" <ji...@apache.org> on 2012/11/11 15:01:12 UTC
[jira] [Created] (AIRAVATA-641) Develop a Registry Migrator tool to
assist with backward compatibity
Suresh Marru created AIRAVATA-641:
-------------------------------------
Summary: Develop a Registry Migrator tool to assist with backward compatibity
Key: AIRAVATA-641
URL: https://issues.apache.org/jira/browse/AIRAVATA-641
Project: Airavata
Issue Type: New Feature
Reporter: Suresh Marru
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 changes.
--
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: http://www.atlassian.com/software/jira