Hey Rohit, As far as I know these are two disctict use cases.
The maven deploy db is just for developers or at least people who are just working from source directly, and should provide a convenient way for developers to refresh their test database or deploy a new schema. The cloud-setup-databases is a tool that is used the sysadmins to setup a database after they have deployed the packages. It has several purposes, setup db.properties, configure encryption and load a database (if the supplied database is empty). In my view both should remain for these purposes, but they should be in-sync and also the upgrade sql script should be in sync with these changes. Cheers, Hugo > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > Of Rohit Yadav > Sent: Monday, February 11, 2013 11:15 AM > To: [email protected] > Subject: [DISCUSS] Fixing cloud-setup-databases > > DatabaseCreator was introduce for 4.1 so both maven deploydb target and > cloud-setup-databases would use that. > Following does not run on maven's deploydb: > cloudbridge_db.sql > schema-level.sql > server-setup.sql > > Following runs only from maven's deploydb: > com.cloud.upgrade.DatabaseUpgradeChecker > > Following runs only from cloud-setup-databases: > com.cloud.test.DatabaseConfig > > Pl. advise if we need to run those as part of maven's deploydb, or cloud- > setup-database or both? > > Regards.
