You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Rohit Yadav (JIRA)" <ji...@apache.org> on 2013/02/13 10:22:12 UTC
[jira] [Updated] (CLOUDSTACK-1019) Fix cloud-setup-database to use
DatabaseCreator and make DatabaseCreator do the upgrades
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohit Yadav updated CLOUDSTACK-1019:
------------------------------------
Summary: Fix cloud-setup-database to use DatabaseCreator and make DatabaseCreator do the upgrades (was: Fix cloud-setup-database to use DatabaseCreator for setting up cloudstack databases)
> Fix cloud-setup-database to use DatabaseCreator and make DatabaseCreator do the upgrades
> ----------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1019
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1019
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Environment: branch: javelin (or master if merge happens)
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Fix For: 4.1.0
>
>
> A new tool/class called DatabaseCreator is introduced in javelin, the idea is that DatabaseCreator can be used by mgmt server, cloud-setup-database script, maven (developer/pom.xml) and possibly by plugins in future to:
> 1. Initialize database using db.properties file
> 2. Run sql scripts
> 3. Run database upgrades
> Presently, this has been fixed in javelin, in cloud-server and is used by maven to deploydb, the task is to fix that same for cloud-setup-databases.
> Current help doc, usage and options:
> DatabaseCreator creates the database schema by removing the
> previous schema, creating the schema, and running
> through the database updaters.
> Usage: DatabaseCreator [options] [db.properties file] [schema.sql files] [database upgrade class]
> Options:
> --database=a,b comma separate databases to initialize, use the db name in db.properties defined as db.xyz.host, xyz should be passed
> --rootpassword=password, by default it will try with an empty password
> --dry or -d, this would not run any process, just does a dry run
> --verbose or -v to print running sql commands, by default it won't print them
> --help or -h for help
--
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