Re: Master is broken?

Min is about to submit a change as a part of her checkin. Antonio, its due to Long/long auto boxing caused by your api validation stuff. Can you please check other places that could get potentially affected? Thanks, Alena. On 3/13/14, 4:10 PM, "Kelven Yang" wrote: >Anyone encounter this problem

Re: Release cadence

I think we should set that as a goal for 4.5. We should treat 4.4 as business as usual at this point and give "fair warning" for the next release. We should formally define what "tested" means for 4.5 and then take the appropriate course of action from a RC point of view. On Thu, Mar 13, 2014 at

Re: Release cadence

My reasoning here is that otherwise we will just be futilely creating RCs for 4.4 since this expectation was not clearly defined ahead of the release. If we set expectations appropriately for 4.5, then we should expect we can begin RC building right after Feature Freeze for that release. On Thu,

Re: Master is broken?

Thanks Min to look into it Kelven On 3/13/14, 4:14 PM, "Alena Prokharchyk" wrote: >Min is about to submit a change as a part of her checkin. Antonio, its due >to Long/long auto boxing caused by your api validation stuff. Can you >please check other places that could get potentially affected? >

Re: Master is broken?

It's half passed midnight here so you won't get an answer soon from this side of the ocean. The line at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:89) is from juli last year. So I doubt if Antonio knows about it. How does it involve the dispatcher refactoring? I noticed that the par

Re: Release cadence

I agree that we can't move to our end goal in on go. But I disagree that we should go on with business as usual right now. baby steps but never stop taking steps. On Fri, Mar 14, 2014 at 12:20 AM, Mike Tutkowski wrote: > My reasoning here is that otherwise we will just be futilely creating RCs >

Re: Master is broken?

Yes, that is problem. Parameter name is changed to lowercase, which will not be able to retrieve parameters from API job. Thanks -min On 3/13/14 4:31 PM, "Daan Hoogland" wrote: >It's half passed midnight here so you won't get an answer soon from >this side of the ocean. > >The line >at com.clou

Re: Release cadence

I just think we need to call out expectations around test clearly in advance of the next release (4.5). Otherwise we'll be spinning up RCs for 4.4 for the next two months because people were treating it from a test perspective like they were treating prior releases. On Thu, Mar 13, 2014 at 5:33

RE: Release cadence

Feature freeze and Merge criteria is not defined to change the milestone suddenly. We can create build and call it RC but that would take another 2+ months to harden to build next RC. There are only 50 defects logged for 4.4 so far. We are away from another 600+ defects to get acceptable RC ca

Re: Release cadence

Exactly...it is not practical for 4.4 to spin up a RC so soon. Perhaps with more clearly defined criteria for 4.5, this may be possible. On Thu, Mar 13, 2014 at 5:48 PM, Sudha Ponnaganti < sudha.ponnaga...@citrix.com> wrote: > Feature freeze and Merge criteria is not defined to change the mile

Re: Master is broken?

Fixed with commit d3fd66e9f555616530e483d1eacf2525556bf14e on master. Thanks -min On 3/13/14 4:34 PM, "Min Chen" wrote: >Yes, that is problem. Parameter name is changed to lowercase, which will >not be able to retrieve parameters from API job. > >Thanks >-min > >On 3/13/14 4:31 PM, "Daan Hoogla

Re: [Merge] CloudStack IAM branch to master

IAM branch is now merged to master. Thanks -min On 3/13/14 10:13 AM, "Min Chen" wrote: >Since we haven't heard of any objections to this merge for 3 days, I am >going to merge it to master today. > >Thanks >-min > >On 3/11/14 12:23 PM, "Hugo Trippaers" wrote: > >> >>On 11 mrt. 2014, at 19:52,

RE: Release cadence

+1 Radical proposition. Setting goals and exit criteria is good so project can be executed on time with expected level of quality. This is common for most of SDLC processes, that teams would stick to the agreed up on quality cycles and quality plans. Because of open source nature it might b

[REVIEW] OpenStack Swift as Object Storage Service

One comment on the "/v1.0" url hack, seems changing mgt server is unavoidable, would it be easier to add a new api in cloudstack, which can get the endpoint of swift server and the auth? And the UI change should be put under ui plugin: https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+P

Re: Review Request 19195: Automation of CCP Objects Verification after external changes made to the original setup

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/19195/ --- (Updated March 14, 2014, 12:33 a.m.) Review request for cloudstack, Girish Shil

Re: Release cadence

The more I think about this, though, we can't really reasonably create an RC at Feature Freeze time. It's not generally until the week or two before Feature Freeze that features start coming into the master branch. We would need at least a couple weeks after Feature Freeze to perform our own inte

Anybody saw this error on master?

Hi there, Anybody has seen this error on master? It is not blocking, but still an eyesore to see it in the log. 2014-03-13 16:31:54,357 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-8:ctx-87d8612e) Vm cpu utilization 0.08 2014-03-13 16:31:54,357 DEBUG [c.c.h.x.r.CitrixResourceBase] (Direct

Re: [REVIEW] OpenStack Swift as Object Storage Service

What are you referring to as the 'v1.0 url hack'? Bypassing the cloudstack management server is an intentional design decision to improve performance. The introduction of a load balancer in front of the two distinct services to maintain separation of their traffic is a good thing. I will review

RE: [REVIEW] OpenStack Swift as Object Storage Service

The way to talk to swift endpoint, by using haproxy to redirect url request contains "/v1.0" to swift endpoint, so it assumes, the endpoint of swift is the same as cloudstack mgt server. Correct me, if I am wrong, I just try to figure how it works. But what if the swift endpoint is different fro

Build failed in Jenkins: build-master-slowbuild #424

See Changes: [min.chen] Add ACL related DB schema. [min.chen] Populate default out-of-box acl roles, converted from ACCOUNT_TYPE [min.chen] Populate acl_group_account_map for existing accounts. [prachi] During Upgrade to 4

Re: [REVIEW] OpenStack Swift as Object Storage Service

Lets say that we have the following setup to help clarify how this all works. CloudStack Management server is on: 10.10.10.2:8080 Swift Proxy servers are on: 10.10.10.3:8080, 10.10.10.4:8080, 10.10.10.5:8080 We have a load balancer setup on: 52.53.54.55:80 The load balancer is networked to both th

Re: [DISCUSS]{BEHAVIORAL-CHANGE]Domain-Account-User Sync Up Among Multiple Regions

What I think based on your comments are 1. Well, I have a different thought. I'd rather have separated classes instead of having a class with lots of methods, which makes the maintenance easier. And as you show as an example, it is possible to create a method and merge them, but I think it is bett

RE: Anybody saw this error on master?

Sanjay has worked on vGPU for xenserver. AFAIK, new xenserver sdk is pushed and it is required. Are you able to build latest xenserver sdk in master. Thanks Rajesh Battala -Original Message- From: Min Chen [mailto:min.c...@citrix.com] Sent: Friday, March 14, 2014 6:18 AM To: dev@cloudsta

RE: 4.4 Feature Freeze

Hugo Folks in USA will still have their day shining on 3/14. Can you cut it after the day in USA is over in PST time Animesh > -Original Message- > From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers > Sent: Tuesday, March 11, 2014 8:28 AM > To: dev@cloudstack.apache.or

Secondary storage in Alert state

Hi, Secondary storage goes in to "Alert" state. Below logs was sniff before launching zone. It says "AgentDisconnected". After launching zone it creates SSVM & CPVM but am not able to ping public ip of any one of them. In DB Secondary storage still in alert state. SSVM health check shows everythi

Build failed in Jenkins: build-master-slowbuild #425

See -- [...truncated 18053 lines...] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi <<< [INFO] [INFO] -

RE: Affinity Groups and Project

CLOUDSTACK-6237 Affinity Group should not display in project view due Affinity Groups feature does not support projects. has submitted. Thanks!! > From: saksham.srivast...@citrix.com > To: dev@cloudstack.apache.org > Subject: RE: Affinity Groups and Project > Date: Thu, 13 Mar 2014 05:41:16

Re: [Merge] CloudStack IAM branch to master

Min, in looking at this branch merge, I need to be reminded whether we are supposed to squash feature branches when they come in, or preserve history. It's nice to preserve history, but it's a lot easier to undo a squashed merge. On Thu, Mar 13, 2014 at 5:56 PM, Min Chen wrote: > IAM branch is no

Re: [20/31] git commit: updated refs/heads/distributedrouter to a8d43ba

Fixed with commit 16ddc3414ae0269ecb8903f670496e45f68d6ef6 On 13-Mar-2014, at 11:34 PM, David Nalley wrote: > Better yet, feel free to submit a patch that fixes it in addition to > the Jira :) > > --David > > On Thu, Mar 13, 2014 at 2:00 PM, Alena Prokharchyk > wrote: >> Konstantina, feel fre

Re: Review Request 19021: Cloudbyte Elastistor storage plug-in

> On March 14, 2014, 3:54 a.m., Mike Tutkowski wrote: > > plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java, > > line 99 > > > > > > Does th

Re: Review Request 18970: CLOUDSTACK-6215: Updating test case to accomodate condition for VMware

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/18970/#review37165 --- Ship it! Ship It! - SrikanteswaraRao Talluri On March 10, 2014,

Re: Review Request 18970: CLOUDSTACK-6215: Updating test case to accomodate condition for VMware

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/18970/#review37166 --- Commit 286974488eab03efddfea35962161a224e997ab0 in cloudstack's bran

Re: Review Request 18970: CLOUDSTACK-6215: Updating test case to accomodate condition for VMware

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/18970/#review37168 --- Commit 768e91ef4560b15deb4804e3593b3ad22fa18eef in cloudstack's bran

Re: Review Request 18971: CLOUDSTACK-6216: Skip the test if run on already existing setup

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/18971/#review37169 --- test/integration/smoke/test_secondary_storage.py

Re: CLOUDSTACK-5583: vmopsSnapshot plug-in (XenServer) does not return an error when it should

I tried to reproduce the issue the way you mentioned with few changes. I don't have iSCSI SAN on my setup. I connected a 2 GB disk that I presented as storage tagged NFS primary to CS. I created a 1GB disk offering and then deployed a VM on this new primary. Took a couple of snapshots like you ment

<    1   2