cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajani Karuturi (JIRA)" <>
Subject [jira] [Updated] (CLOUDSTACK-8310) commit to commit db upgrades and db version control
Date Tue, 28 Mar 2017 08:34:42 GMT


Rajani Karuturi updated CLOUDSTACK-8310:
    Security:     (was: Public)

> commit to commit db upgrades and db version control
> ---------------------------------------------------
>                 Key: CLOUDSTACK-8310
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>            Reporter: Rajani Karuturi
>              Labels: gsoc2017
> Cloudstack currently uses a homegrown tool to do the database upgrades. 
> The challenges with the current one being, it can only do version to version but not
commit to commit upgrades.
> Due to this, when different people work on the same branch and have db changes, environment
is broken untill you do fresh db deploy.
> To achieve this, we can use existing and well tested tools like liquibase, flywaydb etc.
or improve on the existing one. 
> Related discussions on dev lists

This message was sent by Atlassian JIRA

View raw message