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 milam...@apache.org
Hello,
I've try to upgrade my CS test
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
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
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 a big
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
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
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 release to release upgrades?
Additionally
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
: 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 release to release upgrades
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 rather than one
large file. -Soheil
@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 should be a blocker issue.
2013/9
From: Chip Childers [mailto:chip.child...@sungard.com]
Sent: Wednesday, September 11, 2013 5:54 PM
To: dev@cloudstack.apache.org; 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
12 matches
Mail list logo