-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Wednesday, March 20, 2013 6:28 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: CLOUDSTACK-1747: fresh deploydb bug in 4.1 requires cherry-
> pick commits from master
>
> On Wed, Mar 20, 2013 at 02:23
On Wed, Mar 20, 2013 at 02:23:33PM -0700, Alex Huang wrote:
> > My take on this is that we shouldn't do anything to 4.1 The people that
> > matter (users) are taken care of when they start the MS - and that is a
> > well-
> > tested path.
> > The only visible benefit for 4.1 is for developers/QA -
> My take on this is that we shouldn't do anything to 4.1 The people that
> matter (users) are taken care of when they start the MS - and that is a well-
> tested path.
> The only visible benefit for 4.1 is for developers/QA - and while I want
> everyone's life to be as easy as possible - last minu
asn't.
--Alex
> -Original Message-
> From: John Burwell [mailto:jburw...@basho.com]
> Sent: Wednesday, March 20, 2013 1:32 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: CLOUDSTACK-1747: fresh deploydb bug in 4.1 requires cherry-
> pick commits from master
&
On Wed, Mar 20, 2013 at 4:24 PM, Alex Huang wrote:
> Hi everyone,
>
> We had a discussion on irc.
>
> To implement something intermediary will be around the same effort as
> finishing the job and there are various reasons why just running the
> create-schema.sql and update*.sql is not enough. S
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: CLOUDSTACK-1747: fresh deploydb bug in 4.1 requires cherry-
>> pick commits from master
>>
>> On Wed, Mar 20, 2013 at 11:43:30AM -0700, Min Chen wrote:
>>> Chip,
>>>
>>>
speak up.
--Alex
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Wednesday, March 20, 2013 12:39 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: CLOUDSTACK-1747: fresh deploydb bug in 4.1 requires cherry-
> pick commits
On Wed, Mar 20, 2013 at 11:43:30AM -0700, Min Chen wrote:
> Chip,
>
> By reading Rohit's email and wiki, I understood current situation on
> this
> issue. Unlike I previously understood, this DB issue not only happens on
> dev environment, but also happens on QA/production environment as we
Corrected a typo, I meant "a different behavior in 4.1 from previous 4.0
release".
Thanks
-min
On 3/20/13 11:43 AM, "Min Chen" wrote:
>Chip,
>
> By reading Rohit's email and wiki, I understood current situation on
> this
>issue. Unlike I previously understood, this DB issue not only happ
Chip,
By reading Rohit's email and wiki, I understood current situation on
this
issue. Unlike I previously understood, this DB issue not only happens on
dev environment, but also happens on QA/production environment as well.
And this introduces a different behavior in 4.1 from previous 4.
Oh, i see. That means that this issue is not only specific to dev
environment, actually exists in QA environment as well. Basically QA
cannot verify DB schema without starting MS once.
I am consulting with Alex to see if we want to fix this in 4.1 or not.
Thanks for clarification. Chip, please hol
For 4.1, you deploydb (that would be 4.0 schema), run mgmt server
(dbupgradechecker should upgrade to 4.1). Starting 4.2, dbcreator
would do that (like on master) and cloud-setup-databases should call
dbcreator as well.
I tried to refactor the tool and upgrade classes, that did not work
smoothly f
Pl see https://cwiki.apache.org/confluence/display/CLOUDSTACK/Database+Creator
Edit/add/modify wiki boldly in case something is confusing, missing.
On Wed, Mar 20, 2013 at 11:43 PM, Chip Childers
wrote:
> On Wed, Mar 20, 2013 at 11:08:01AM -0700, Min Chen wrote:
>> Hi Chip,
>>
>> I created this
Chip,
Based on Rohit's comments, the blocking defect I raised may not be a bug.
I will perform a rebuild tomorrow to determine if the template_s3_ref
table gets created properly.
Thanks,
-John
On Wed, Mar 20, 2013 at 2:13 PM, Chip Childers wrote:
> On Wed, Mar 20, 2013 at 11:08:01AM -0700, M
On Wed, Mar 20, 2013 at 11:08:01AM -0700, Min Chen wrote:
> Hi Chip,
>
> I created this bug https://issues.apache.org/jira/browse/CLOUDSTACK-1747
> because I noticed yesterday in dev setup that after running mvn -P developer
> -pl developer –Ddeploydb, my DB is still at 4.0 version, not expected
On Wed, Mar 20, 2013 at 11:08:01AM -0700, Min Chen wrote:
> Hi Chip,
>
> I created this bug https://issues.apache.org/jira/browse/CLOUDSTACK-1747
> because I noticed yesterday in dev setup that after running mvn -P developer
> -pl developer –Ddeploydb, my DB is still at 4.0 version, not expected
Min,
Between this issue and 1745, it may be prudent to give the create-schema.sql a
good once over to ensure that we don't have any other schema issues.
Thanks,
-John
On Mar 20, 2013, at 2:08 PM, Min Chen wrote:
> Hi Chip,
>
> I created this bug https://issues.apache.org/jira/browse/CLOUDST
Hi Chip,
I created this bug https://issues.apache.org/jira/browse/CLOUDSTACK-1747
because I noticed yesterday in dev setup that after running mvn -P developer
-pl developer –Ddeploydb, my DB is still at 4.0 version, not expected 4.1
version. This is causing so much confusion to developers. We c
18 matches
Mail list logo
