Hi Prachi ,
Regarding the 3rd point you just mentioned - If in case you are thinking from
the UI perspective , then this change is not required since I can have the
flags set to Yes/No through some UI code hacks for each of those resources. But
yes, if you still want those flags to be set in th
Hi everyone,
I'm trying to submit code for the first time.
I'm following the instructions here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Review+Board+Guidelines
When it says to upload my diff, I assume it means my .patch file. Is that
correct?
I generate such a file this way:
gi
LS,
Lately I've been getting, "com.cloud.exception.InvalidParameterValueException:
ACL item with number 1 already exists in ACL: null", while building cloudstack.
I first thought it was my own hack so I don't know when it was introduced (it
is in a clean master that it happens). The full surfir
Congrats Swamy!!
-Sanjeev
-Original Message-
From: Likitha Shetty [mailto:likitha.she...@citrix.com]
Sent: Sunday, May 26, 2013 9:40 PM
To: dev@cloudstack.apache.org
Subject: RE: [ANNOUNCE] New committer: Venkata Swamy
Congratulations Swamy :)
>-Original Message-
>From: Chip Ch
Congrats Sailaja :)
-Sanjeev
-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: Friday, May 24, 2013 10:20 PM
To: dev@cloudstack.apache.org
Subject: RE: [ANNOUNCE] New committer: Sailaja Mada
Congratulations Sailaja
> -Original Message-
> F
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/11428/
---
Review request for cloudstack, Sheng Yang and Hugo Trippaers.
Description
-
On Sun, May 26, 2013 at 9:12 PM, Hiroaki Kawai (JIRA) wrote:
>
> [
> https://issues.apache.org/jira/browse/CLOUDSTACK-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667432#comment-13667432
> ]
>
> Hiroaki Kawai commented on CLOUDSTACK-2406:
> --
One thing I should add, while it makes perfect sense to me to draw a
line on which technologies should be allowed in our code base, I will
say that I'm fine with Java calling external scripts to do system
admin work. I don't really like to see things split, like we have with
libvirt where we use ja
On Sun, May 26, 2013 at 10:24 AM, Chip Childers
wrote:
> On Sat, May 25, 2013 at 10:52:34AM -0400, Outback Dingo wrote:
> > On Sat, May 25, 2013 at 10:33 AM, Chip Childers
> > wrote:
> >
> > > On May 25, 2013, at 10:16 AM, Sebastien Goasguen
> wrote:
> > >
> > > >
> > > > On May 25, 2013, at 10:0
Yes, you're welcome to rewrite it in Python. You're spot on with why
it's not in Java.
As for why it's in Perl, it was simple for me to do and we already
have a dependency on it. As far as I've seen, the majority of what's
written for the agent to call is in Bash, and this task was fairly
diffic
Congratulations Swamy :)
>-Original Message-
>From: Chip Childers [mailto:chip.child...@sungard.com]
>Sent: Friday, May 24, 2013 3:00 AM
>To:
>Subject: [ANNOUNCE] New committer: Venkata Swamy
>
>The Project Management Committee (PMC) for Apache CloudStack has asked
>Venkata Swamy to becom
Should be fine Swamy,
Test plans are not categorized based on release but test execution results are
so that is how I have setup the structure. You will find test execution
results under each ACS release specific to that release.
Thanks
/sudha
-Original Message-
From: Venkata SwamyBa
Hi,
Here is the link to TestPlan :
https://cwiki.apache.org/confluence/display/CLOUDSTACK/TestPlan+for+PortableIP+feature
Please review and let me know your review comments.
FS Link : https://cwiki.apache.org/CLOUDSTACK/portable-public-ip.html
Earlier, I used to see a category for each release
Hi All,
I've created a 4.1.0 release, with the following artifacts up for a
vote.
The changes from round 3 are two commits related to DEB packaging.
Git Branch and Commit SH:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.1
Commit: db007da15290970c842c3229a11
This vote is cancelled. I'll re-spin a round 4 shortly.
On Fri, May 24, 2013 at 01:41:44PM -0400, Chip Childers wrote:
> Hi All,
>
> I've created a 4.1.0 release, with the following artifacts up for a
> vote:
>
> Git Branch and Commit SH:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.
On Sun, May 26, 2013 at 12:00:19PM +0200, Wido den Hollander wrote:
> Hi Chip,
>
> I'm sorry, but I'm going to have to vote -1 on this one.
>
> It's my bad, but it seems that I made a mistake on the Debian
> packaging side. See this commit:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.
On Sat, May 25, 2013 at 10:52:34AM -0400, Outback Dingo wrote:
> On Sat, May 25, 2013 at 10:33 AM, Chip Childers
> wrote:
>
> > On May 25, 2013, at 10:16 AM, Sebastien Goasguen wrote:
> >
> > >
> > > On May 25, 2013, at 10:08 AM, Outback Dingo
> > wrote:
> > >
> > >> On Sat, May 25, 2013 at 10:0
On Fri, May 24, 2013 at 10:10:25PM +, Animesh Chaturvedi wrote:
> [Animesh>] Plan means targeted for 4.2. Community review and technical
> quality are of course important and being attended to. The effort to find and
> fix issues with this change speaks for the attention to technical qualit
Ok. Vote cancelled.
Wido, is the 4.1 branch corrected now? I'll be back near my laptop
tonight. Just want to know if there is work to do, or can I just
re-spin a forth round?
On May 26, 2013, at 6:01 AM, Wido den Hollander wrote:
> Hi Chip,
>
> I'm sorry, but I'm going to have to vote -1 on t
Hi Chip,
I'm sorry, but I'm going to have to vote -1 on this one.
It's my bad, but it seems that I made a mistake on the Debian packaging
side. See this commit:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commitdiff;h=dc822a83d77830281402175b4a57b25b7e3b180a
I just verified, c
We were setting the static_min in XcpOssResource (resource used by
DevCloud's xcp kronos xen) to 128m and the static_max the offering had
sent through was set to 100m. This caused the violation in the memory
values.
Introduced the appropriate override for the XcpOssResource of
DevCloud. SystemVMs
Hi Marcus,
This is somewhat a rhetorical question, but I wanted to confirm anyway.
The 4.2 SystemVMs use a VirtIO socket on KVM to get their boot
arguments. That is great, since there is no longer a need for patch
disks which enables them to run on RBD.
One of the things I dislike about the
I should say that it randomly fails with the larger memory limits (as
the process grows it eventually causes problems), if dom0 has a small
amount of memory like devcloud does. Shane said in a previous message
that 4.1 works. So I'm not entirely sure, but one thing to check at
least would be that t
It's because the tomcat memory limits were raised in 4.1 to deal with
the initial memory footprint increase back in Feb. It hasn't run in
stock devcloud since. I increased the dom0 memory on mine to make it
work. I think there was subsequent work in April or so to get the
memory back down, so we m
24 matches
Mail list logo
