I don't understand why this is a problem.
>From a systems perspective there is only one (correct) timezone.
Actually using timezones, especially in a geographically distributed
cloud is problematic.
--David
On Sun, Jun 30, 2013 at 11:27 PM, Ryan Lei wrote:
> Great. Both the OSS and non-OSS buil
Great. Both the OSS and non-OSS builds fine on the 4.1 branch now! Tested
on OS X 10.6.8 and CentOS 6.3.
But here's another flaw in DB upgrade:
The upgrade writes the timestamp in UTC+0 time zone in MySQL (in 4.1, 4.2,
master):
[4.1] mysql> select * from version;
++-+-
Hey Ryan,
This is left-over from older versions. The nonoss build used to be a premium
build and had a few differences in the database. Hence the two different
database upgrade classes.
It should go away soon :-)
Cheers,
Hugo
Sent from my iPhone
On 28 jun. 2013, at 20:46, Ryan Lei wrote:
Hugo, thanks for the quick fix. I'll verify it on Monday when I have access
to the server.
But can you briefly explain why the OSS-build wouldn't have this problem?
Ryan
Hugo Trippaers 於 2013年6月29日星期六寫道：
> Hello :-)
>
> Nice find!
>
> I've pushed this commit to the branch:
>
> commit b330f2aa9
Hello :-)
Nice find!
I've pushed this commit to the branch:
commit b330f2aa909d7ddc387863e0806f71964f6d5f80
Author: Hugo Trippaers
Date: Fri Jun 28 10:57:51 2013 -0700
CLOUDSTACK-3278 Add the 410 to 411 upgrade to the
PremiumDatabaseUpgradeChecker
Can you verify if this fixes your pro
Actually, the errors happen only in non-OSS build with git 4.1
(4.1.1-SNAPSHOT).
OSS build with git 4.1 and non-OSS build with 4.1.0 source code work fine.
They are able to run the Upgrade40to41 or Upgrade410to411.
I have created a JIRA ticket for this issue:
https://issues.apache.org/jira/browse
Hi all,
I was trying to use the git 4.1 branch to run non-OSS CloudStack from
source. My commands were:
(1) Put the neccessary jars in deps
(2) Run deps/install-non-oss.sh with success
(3) $ mvn clean install -DskipTests=true -Dnonoss
(4) $ mvn -P developer -pl developer -Ddeploydb
(5) $ mvn -pl :
