That fix doesn't work correctly. I'll explain in another thread.
On Fri, Dec 13, 2013 at 2:41 AM, Abhinandan Prateek
wrote:
> Fixed the build script a 3rd round of voting is due now, so please hold on
> voting for this round.
>
> -abhi
>
> On 13/12/13 10:57 am, "Abhinandan Prateek"
> wrote:
>
>
On Fri, Dec 13, 2013 at 03:16:04AM +, Abhinandan Prateek wrote:
> Wei,
>
> The build was made after this commit
> 55c56b6cc26d4e1f5156b0a6a387594659d271f5 .
> I think the commit that I put in the e-mail is the one that was generated
> by the script and unfortunately that I did not push.
> Th
t;
> 2. Make sure you use the configuration as mentioned in below mail.
>
> Santhosh
>
> From: Wei ZHOU [ustcweiz...@gmail.com]
> Sent: Friday, December 13, 2013 4:47 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] 2rd round of v
I did test a xenserver environment and it works if you put the
vhd-util under your eclipse cloud-core-snapshot dir in the right
place. I don't see why it shouldn't work but I haven't tested the
upgrade scenario on a unix ms host.
I did check our hosts to be upgraded and they already have a vhd-util
Santhosh,
Thanks for your reply. I will test it later.
-Wei
Hi Daan,
Sorry I did not notice that you were using devcloud for testing.
The fresh 4.2.1 installation should be ok.
However, the issue may impact the upgrade.
vhd-util was in /opt/xensource/ directory in 4.2, so
/opt/cloud/bin/vhd-util may be missing after upgrade to 4.2.1.
I do not have xenserve
.com]
Sent: Friday, December 13, 2013 4:47 AM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] 2rd round of voting for ASF 4.2.1 third RC
Santhosh,
Please see the following.
[root@centos master(4.2)]# python tools/marvin/marvin/deployDataCenter.py
-i tools/devcloud/devcloud-advancedsg.cfg
Trace
On Fri, Dec 13, 2013 at 9:56 AM, Wei ZHOU wrote:
> This is because of commit 7f9463bb54f19e7676f8c6049d1ebc02330a730f
> Author: Anthony Xu
> Date: Tue Dec 3 01:36:24 2013 -0800
>
> put shell scripts to a seperate directory in XS
> use same scripts for both XS and XCP
>
> In this commit,
devcloud-advancedsg.cfg
>
> Regards,
> Santhosh
>
> From: Wei ZHOU [ustcweiz...@gmail.com]
> Sent: Friday, December 13, 2013 3:56 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] 2rd round of voting for ASF 4.2.1 thi
/devcloud-advancedsg.cfg
Regards,
Santhosh
From: Wei ZHOU [ustcweiz...@gmail.com]
Sent: Friday, December 13, 2013 3:56 AM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] 2rd round of voting for ASF 4.2.1 third RC
Abhi,
Thanks for your reply.
Another issue after
Abhi,
Thanks for your reply.
Another issue after commit 55c56b6cc26d4e1f5156b0a6a387594659d271f5 is that
I can not use devcloud for testing any more.
(1) All of the following command will fail when I want to add a zone and
host.
mvn -P developer -pl tools/devcloud -Ddeploysvr
python tools/marvin/
Fixed the build script a 3rd round of voting is due now, so please hold on
voting for this round.
-abhi
On 13/12/13 10:57 am, "Abhinandan Prateek"
wrote:
> The build script explicitly removes the SNAPSHOT from the version before
>it builds.
>AS per CLOUDSTACK-4827 the the xapi version in deps/X
The build script explicitly removes the SNAPSHOT from the version before
it builds.
AS per CLOUDSTACK-4827 the the xapi version in deps/XenServerJava/pom.xml
should not change.
But then I see someone explicitly add the following in
tools/build/build_asf.sh :
mv deps/XenServerJava/pom.xml.versions
On 12/12/13 10:00 pm, "Wei ZHOU" wrote:
>Abhi,
>I have two problems
>(1) I can not checkout the commit
>43350d64ce66e366f08a9fa13ad09bca462b66da,
>it looks not exist
>(2) the xapi version in deps/XenServerJava/pom.xml should not be changed
>when you bump the version from 4.2.1-SNAPSHOT to 4.2.1.
Wei,
The build was made after this commit
55c56b6cc26d4e1f5156b0a6a387594659d271f5 .
I think the commit that I put in the e-mail is the one that was generated
by the script and unfortunately that I did not push.
That generally results in two commits one with bumping the version and
another with
-Original Message-
From: sebgoa [mailto:run...@gmail.com]
Sent: Thursday, December 12, 2013 12:36 AM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] 2rd round of voting for ASF 4.2.1 third RC
On Dec 12, 2013, at 3:08 AM, Abhinandan Prateek
wrote:
>
>
> On 11/12/13
Abhi,
I have two problems
(1) I can not checkout the commit 43350d64ce66e366f08a9fa13ad09bca462b66da,
it looks not exist
(2) the xapi version in deps/XenServerJava/pom.xml should not be changed
when you bump the version from 4.2.1-SNAPSHOT to 4.2.1. (see
CLOUDSTACK-4827)
-Wei
2013/12/10 Abhinan
It is a +1 from my side.
I could successfully bring up the management server and deployed advanced
zone with XenServer 6.2 , system Vms came up.
Tested following :
1. Created a VM
2. Configured VPN on Source NAT IP.
3. Configured VPN users.
4. I could successfully connect to the network from a
On 12/12/13 2:06 pm, "sebgoa" wrote:
>>developers distributed across the globe I think it is very
>> difficult to control the commits going into a branch after RC has been
>> cut. As a RN I can only go thru the commits and see if any of those can
>> cause unwanted changes and try to test those
You are absolutely right and though it is kind of unsettling I will
now formally change my vote to
+1 (binding)
On Thu, Dec 12, 2013 at 6:01 AM, Abhinandan Prateek
wrote:
> Well Daan, you said "well, mine is a go, I have a symptom not a decease.²
> and voted +1 on first voting round with this exc
>>
>>? With
>> so many developers distributed across the globe I think it is very
>> difficult to control the commits going into a branch after RC has been
>> cut. As a RN I can only go thru the commits and see if any of those can
>> cause unwanted changes and try to test those out.
>>>
>>
>
>Abh
On Dec 12, 2013, at 3:08 AM, Abhinandan Prateek
wrote:
>
>
> On 11/12/13 11:24 pm, "Chip Childers" wrote:
>
>> On Wed, Dec 11, 2013 at 05:56:50PM +0100, Daan Hoogland wrote:
>>> Though I'm out of principle not very appreciative for the 'extra'
>>> fixes form RC to RC, ...
>>
>> Looking at
Well Daan, you said "well, mine is a go, I have a symptom not a decease.²
and voted +1 on first voting round with this exception :-)
On 11/12/13 10:27 pm, "Daan Hoogland" wrote:
>H,
>
>I carried on with my sanity tests and all succeed only a disconcerning
>exception trace appears that I have not
On 11/12/13 11:24 pm, "Chip Childers" wrote:
>On Wed, Dec 11, 2013 at 05:56:50PM +0100, Daan Hoogland wrote:
>> Though I'm out of principle not very appreciative for the 'extra'
>> fixes form RC to RC, ...
>
>Looking at the log, it seems that most of the activity are tied to test
>script fixes.
On Wed, Dec 11, 2013 at 05:56:50PM +0100, Daan Hoogland wrote:
> Though I'm out of principle not very appreciative for the 'extra'
> fixes form RC to RC, ...
Looking at the log, it seems that most of the activity are tied to test
script fixes. That sort-of makes sense, but at the same time it
tri
H,
I carried on with my sanity tests and all succeed only a disconcerning
exception trace appears that I have not seen before. After creating a
network and instance and then deleting it:
WARN [agent.manager.AgentManagerImpl] (AgentManager-Handler-2:) Caught:
java.lang.NumberFormatException: For
Wei,
Thanks for the smack in the face. The problem was in my funky test
setup with a local ms (on windows).
Though I'm out of principle not very appreciative for the 'extra'
fixes form RC to RC, this one would not have affected me had I been a
good boy.
On Wed, Dec 11, 2013 at 1:14 PM, Daan Hoo
I might agree as my env is running from source on windows but this is
an upgrade scenario and the page you refer is about installing! Is
that covered somewhere? Or does the copy take place automatically?
regards,
Daan
On Wed, Dec 11, 2013 at 12:00 PM, Wei ZHOU wrote:
> It looks you did not follo
Yes, I think tagging with a date is a good idea, as I can see once a RC is
created the tag fails in subsequent RC.
I am not sure about the procedure to change this tag naming convention but
+1 for this from me.
On 11/12/13 4:20 pm, "Daan Hoogland" wrote:
>On a side note: Can we set a tag of "RC-
It looks you did not follow the instruction.
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/management-server-install-flow.html
I think it is not a blocker or critical issue.
2013/12/11 Daan Hoogland
> I can confirm that the folowing fixes the problem
>
On a side note: Can we set a tag of "RC-" on creating release
candidates? this in combination with a branch will be helpful in
chasing changes like I just did.
Or should I start a new [DISCUSS] thread on this?
Or just change the wiki and burden the release managers with it
without telling? (no ser
I can confirm that the folowing fixes the problem
[root@mccdxen1 bin]# pwd
/opt/cloud/bin
[root@mccdxen1 bin]# ln -s /opt/xensource/bin/vhd-util .
I don't think we should let this to the people doing a migration from
one version to another so
-1 (binding) to this rc
I want to set this link in c
On Wed, Dec 11, 2013 at 5:24 AM, David Nalley wrote:
> Why, for a bug fix release would we do something like change the
> expected location of vhd-util on a XS host?
Or more specifically; What bug does this fix?
And why is it not copied to the hypervisors as part of the zone
configuration/addHos
On Tue, Dec 10, 2013 at 9:18 PM, Anthony Xu wrote:
> My best guess is you don't have vhd-util in your management server.
>
> Check if vhd-util exists in /opt/cloud/bin in your XS host, if not, you need
> to do following,
> 1. make sure vhd-util is downloaded in your management server
> 2. clear
Xe host-param-clear host-uuid= param-name=tags
3. restart management server
Anthony
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Tuesday, December 10, 2013 2:09 PM
To: dev
Subject: Re: [VOTE] 2rd round of voting for ASF 4.2.1 third RC
I am goi
I am going to tentatively -1 this one. There has changed something
since last rc that makes this one not start a ssvm in my sanity check
env after creating a zone. I have not pinned down the culprit commit
yet so I will keep looking till I can be sure as to what is wrong. I
have been going back and
The vote is open till 13 Dec 2013.
On 10/12/13 6:28 pm, "Abhinandan Prateek"
wrote:
>Hi,
>
> This release candidate addresses the following additional issues
>reported by community:
>
>1. CLOUDSTACK-5145 : ListNetworkACL API should list ACLs owned by the user
>only
>2. CLOUDSTACK-5214 : 4.2.
37 matches
Mail list logo
