Hi Sneha, This is an open problem for Airavata and we will be interested in what you plan to propose. Here are some threads on this topic:
https://issues.apache.org/jira/browse/AIRAVATA-2291 <https://issues.apache.org/jira/browse/AIRAVATA-2291> http://www.mail-archive.com/[email protected]/msg11325.html <http://www.mail-archive.com/[email protected]/msg11325.html> Anuj mentioned he attached some ER diagrams of database schemas, you may want to search for them in JIRA. Anuj? Let us know if you have specific questions. Suresh > On Apr 1, 2017, at 6:39 PM, Sneha Tilak <[email protected]> wrote: > > Hello dev, > > I am interested in participating in the Google Summer of Code '17. The > proposal below is what I would like to work on - > > Title: Database Versioning in Apache Airavata. > > Problem Statement: Considering Airavata, which has multiple developers > contributing to the project, there is bound to be a situation where the > databases and the data stored in it are not synchronized. Even with a single > instance, it takes a significant amount of time to make sure that the changes > are in sync when more than one developer works on it. The goal of this > project is to introduce versioning of databases (schema and data) when > merging a developed branch to the master branch before deploying the revision. > > I would love to hear your suggestions regarding the same. > > Regards, > Sneha Tilak
