Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8344AD286 for ; Mon, 11 Feb 2013 16:27:31 +0000 (UTC) Received: (qmail 50559 invoked by uid 500); 11 Feb 2013 16:27:31 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 50509 invoked by uid 500); 11 Feb 2013 16:27:31 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 50496 invoked by uid 99); 11 Feb 2013 16:27:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2013 16:27:31 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [195.66.90.41] (HELO sbprmx2.schubergphilis.com) (195.66.90.41) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2013 16:27:23 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by sbprmx2.schubergphilis.com (Postfix) with ESMTP id 49F0612D2E for ; Mon, 11 Feb 2013 17:27:02 +0100 (MET) X-Virus-Scanned: amavisd-new at schubergphilis.com Received: from sbprmx2.schubergphilis.com ([127.0.0.1]) by localhost (sbprmx2.schubergphilis.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GwUmkfk7F9kN for ; Mon, 11 Feb 2013 17:27:02 +0100 (MET) Received: from SBPOTMG401.sbp.lan (edge.schubergphilis.com [195.66.90.11]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by sbprmx2.schubergphilis.com (Postfix) with ESMTP id 3C9B912D10; Mon, 11 Feb 2013 17:27:02 +0100 (MET) Received: from SBPOMF102.sbp.lan (10.71.2.131) by SBPOTMG401.sbp.lan (10.71.3.110) with Microsoft SMTP Server (TLS) id 14.1.379.0; Mon, 11 Feb 2013 17:27:01 +0100 Received: from SBPOMB402.sbp.lan ([fe80::2410:c2c8:67bf:d067]) by SBPOMF102.sbp.lan ([fe80::9049:fc5b:72ee:dd7%15]) with mapi id 14.02.0318.001; Mon, 11 Feb 2013 17:27:01 +0100 From: Hugo Trippaers To: 'Rohit Yadav' , "cloudstack-dev@incubator.apache.org" Subject: RE: [DISCUSS] Fixing cloud-setup-databases Thread-Topic: [DISCUSS] Fixing cloud-setup-databases Thread-Index: AQHOCEDNvU+791jZIUKxY9MKelY62Zh017/g Date: Mon, 11 Feb 2013 16:27:00 +0000 Message-ID: <6DE00C9FDF08A34683DF71786C70EBF02F6C1C4A@SBPOMB402.sbp.lan> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.71.96.47] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Hey Rohit, As far as I know these are two disctict use cases.=20 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 devel= opers 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 d= atabase after they have deployed the packages. It has several purposes, set= up 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-syn= c and also the upgrade sql script should be in sync with these changes. Cheers, Hugo > -----Original Message----- > From: rohityadav89@gmail.com [mailto:rohityadav89@gmail.com] On Behalf > Of Rohit Yadav > Sent: Monday, February 11, 2013 11:15 AM > To: cloudstack-dev@incubator.apache.org > Subject: [DISCUSS] Fixing cloud-setup-databases >=20 > 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 >=20 > Following runs only from maven's deploydb: > com.cloud.upgrade.DatabaseUpgradeChecker >=20 > Following runs only from cloud-setup-databases: > com.cloud.test.DatabaseConfig >=20 > Pl. advise if we need to run those as part of maven's deploydb, or cloud- > setup-database or both? >=20 > Regards.