Re: [DISCUSS] Fixing cloud-setup-databases

2013-02-13 Thread Rohit Yadav
o get this done. I should be on around 9p.m. pst. > > --Alex > >> -Original Message- >> From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf >> Of Rohit Yadav >> Sent: Wednesday, February 13, 2013 1:25 AM >> To: cloudstack-dev@incu

RE: [DISCUSS] Fixing cloud-setup-databases

2013-02-13 Thread Alex Huang
Rohit Yadav > Sent: Wednesday, February 13, 2013 1:25 AM > To: cloudstack-dev@incubator.apache.org > Subject: Re: [DISCUSS] Fixing cloud-setup-databases > > Unassigned CLOUDSTACK-1019 to be picked up by someone else. > I'm not sure how to do it correctly, picked up other thin

Re: [DISCUSS] Fixing cloud-setup-databases

2013-02-13 Thread Rohit Yadav
Run DatabaseCreator (again maybe in a script) to do >>>post-upgrade cleanup. >>> - Release manager produces the create-schema.sql for every major >>>release. >>> >>> For 4.1, we need to get rid of the 4.1-new-schema. I have no idea why >>>that's

Re: [DISCUSS] Fixing cloud-setup-databases

2013-02-12 Thread Abhinandan Prateek
why >>that's created as it obviously doesn't fit into our upgrade strategy. >>Everything in that file should be moved into the DB upgrade scripts and >>that file removed in git and from the developer/pom.xml. Also, the >>version in create-schema.sql needs to sta

Re: [DISCUSS] Fixing cloud-setup-databases

2013-02-12 Thread Rohit Yadav
ex > >> -Original Message- >> From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf >> Of Rohit Yadav >> Sent: Monday, February 11, 2013 9:13 AM >> To: Hugo Trippaers >> Cc: cloudstack-dev@incubator.apache.org >> Subject: Re: [DISCUSS] Fixing

RE: [DISCUSS] Fixing cloud-setup-databases

2013-02-11 Thread Alex Huang
guage as well) in no time. > > > > Regards. > > > > On Mon, Feb 11, 2013 at 10:32 PM, Hugo Trippaers > > wrote: > >> > >> > >>> -Original Message- > >>> From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On >

Re: [DISCUSS] Fixing cloud-setup-databases

2013-02-11 Thread Rohit Yadav
--Original Message- >>> From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf >>> Of Rohit Yadav >>> Sent: Monday, February 11, 2013 5:49 PM >>> To: Hugo Trippaers >>> Cc: cloudstack-dev@incubator.apache.org >>> Subject

Re: [DISCUSS] Fixing cloud-setup-databases

2013-02-11 Thread Rohit Yadav
da...@gmail.com] On Behalf >> Of Rohit Yadav >> Sent: Monday, February 11, 2013 5:49 PM >> To: Hugo Trippaers >> Cc: cloudstack-dev@incubator.apache.org >> Subject: Re: [DISCUSS] Fixing cloud-setup-databases >> >> On Mon, Feb 11, 2013 at 9:57 PM, Hugo Trippaers

RE: [DISCUSS] Fixing cloud-setup-databases

2013-02-11 Thread Hugo Trippaers
> -Original Message- > From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf > Of Rohit Yadav > Sent: Monday, February 11, 2013 5:49 PM > To: Hugo Trippaers > Cc: cloudstack-dev@incubator.apache.org > Subject: Re: [DISCUSS] Fixing cloud-setup-datab

Re: [DISCUSS] Fixing cloud-setup-databases

2013-02-11 Thread Rohit Yadav
On Mon, Feb 11, 2013 at 9:57 PM, Hugo Trippaers wrote: > Hey Rohit, > > As far as I know these are two disctict use cases. > I agree, but only in few sets of sql files. The reasons why DatabaseCreator was introduced: 0. Make life of sysadmins and developers easier 1. If passed --database, it woul

RE: [DISCUSS] Fixing cloud-setup-databases

2013-02-11 Thread Hugo Trippaers
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-data