From: Chip Childers [mailto:chip.child...@sungard.com]
Sent: Wednesday, September 11, 2013 5:54 PM
To: ; Animesh Chaturvedi
Subject: Re: There is no upgrade path from 4.1.1 to 4.2.0
Animesh,
I have not checked on this myself.
I believe that you have not yet promoted the bits from dist/dev to
>
>
>
>
>
>>
>> -Original Message-
>> From: Wei ZHOU [mailto:ustcweiz...@gmail.com]
>> Sent: Wednesday, September 11, 2013 7:37 AM
>> To: dev@cloudstack.apache.org
>> Subject: Re: There is no upgrade path from 4.1.1 to 4.2.0
>>
&g
Is there a problem with applying the sql changes as micro timestamped updates
and keeping a schema version in the db based on the timestamp?
In Ruby on Rails that's how migrations are created, as timestamped ruby file
that defines the changes, for example 20130818033029_add_user_roles.rb. When a
On 09/11/2013 09:12 AM, Alex Huang wrote:
As for separating db version from release version. In general I agree with
that. Again, it's a practical thing. Currently, cloudstack db changes with
every release so even if you separate them basically they just advance in a
parallel path anyways.
---
> From: Soheil Eizadi [mailto:seiz...@infoblox.com]
> Sent: Wednesday, September 11, 2013 9:09 AM
> To: dev@cloudstack.apache.org
> Subject: RE: There is no upgrade path from 4.1.1 to 4.2.0
>
> Forgot to comment, I like the idea of having smaller sql files r
> Why do we even maintain such a thing? DB migration version should not be
> related to the release version. So DB just goes forward in one continuous
> stream, version 42, 43, 44, 45, 46, etc.
>
I also meant to reply about this part. DB upgrade as a continuous stream is
nice in theory but re
: There is no upgrade path from 4.1.1 to 4.2.0
>
> Why do we even maintain such a thing? DB migration version should not be
> related to the release version. So DB just goes forward in one continuous
> stream, version 42, 43, 44, 45, 46, etc.
>
> So why do we have specific from
Ordering and dependency needs to be handled with multiple sql files not an
issue with single file.
-Soheil
From: Alex Huang [alex.hu...@citrix.com]
Sent: Wednesday, September 11, 2013 8:29 AM
To: dev@cloudstack.apache.org
Subject: RE: There is no upgrade
11, 2013 7:37 AM
To: dev@cloudstack.apache.org
Subject: Re: There is no upgrade path from 4.1.1 to 4.2.0
I do not find anything related in
./engine/schema/src/com/cloud/upgrade/DatabaseUpgradeChecker.java, and no
Upgrade411to420.java in ./engine/schema/src/com/cloud/upgrade/dao/ as well.
This
On 09/11/2013 07:19 AM, Milamber wrote:
The path 4.1.1->4.2.0 seems miss?
Why do we even maintain such a thing? DB migration version should not
be related to the release version. So DB just goes forward in one
continuous stream, version 42, 43, 44, 45, 46, etc.
So why do we have specifi
>
> Why do we even maintain such a thing? DB migration version should not be
> related to the release version. So DB just goes forward in one continuous
> stream, version 42, 43, 44, 45, 46, etc.
>
> So why do we have specific from release to release upgrades?
> Additionally, there shouldn't be
Le 11/09/2013 15:36, Wei ZHOU a ecrit :
I do not find anything related in
./engine/schema/src/com/cloud/upgrade/DatabaseUpgradeChecker.java, and no
Upgrade411to420.java in ./engine/schema/src/com/cloud/upgrade/dao/ as well.
This should be a blocker issue.
Thanks for checks.
I've open an issue
This indicates to me that this is tested already
https://issues.apache.org/jira/browse/CLOUDSTACK-4509
-Original Message-
From: Wei ZHOU [mailto:ustcweiz...@gmail.com]
Sent: Wednesday, September 11, 2013 7:37 AM
To: dev@cloudstack.apache.org
Subject: Re: There is no upgrade path from
I do not find anything related in
./engine/schema/src/com/cloud/upgrade/DatabaseUpgradeChecker.java, and no
Upgrade411to420.java in ./engine/schema/src/com/cloud/upgrade/dao/ as well.
This should be a blocker issue.
2013/9/11 Milamber
> Hello,
>
> I've try to upgrade my CS test platform from 4.
14 matches
Mail list logo
