airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Marru (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AIRAVATA-641) Develop a Registry Migrator tool to assist with backward compatibity
Date Fri, 28 Mar 2014 15:42:15 GMT

     [ https://issues.apache.org/jira/browse/AIRAVATA-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Suresh Marru closed AIRAVATA-641.
---------------------------------


We can close this for now, but we will still need a registry migrator for based on new data
models in future. 

> 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
>            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
changes. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message