RE: CloudStack Quality Process

Not dominated, majority presence > -Original Message- > From: Stephen Turner [mailto:stephen.tur...@citrix.com] > Sent: Monday, January 12, 2015 3:30 AM > To: dev@cloudstack.apache.org > Subject: RE: CloudStack Quality Process > > 17:00 is the earliest I can do this week, although I reali

RE: CloudStack Quality Process

ix.com] > Sent: 16 December 2014 13:03 > To: dev@cloudstack.apache.org > Subject: RE: CloudStack Quality Process > > Were we planning to have another meeting at the same time tomorrow (2014- > 12-17T17:00Z)? Animesh, can you set up a GTM again? > > (Hoping that no-one's goi

RE: [OFFLINE] Animesh offline from 12/18 - 12/28

> > Happy xmas & new year > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > ----- Original Message - > > From: "Animesh Chaturvedi" > > To: dev@cloudstack.apache.org > > Sent: Monday, 1

[OFFLINE] Animesh offline from 12/18 - 12/28

Happy holidays everyone. I will be offline from 12/18 - 12/28. Thanks Animesh

RE: CloudStack Quality Process

che.org > Cc: Steve Wilson > Subject: Re: CloudStack Quality Process > > Thanks for sharing the notes. Sorry, I couldn't make it this time. Will > definitely > plan to join the next meeting. > > ~Rajani > > On Thu, Dec 11, 2014 at 1:27 AM, Animesh Chaturvedi < &g

RE: CloudStack Quality Process

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Quality+and+Process+Improvement+Initiative > -Original Message- > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] > Sent: Wednesday, December 10, 2014 9:05 AM > To: dev@cloudstack.apache.org > Cc: Steve

RE: CloudStack Quality Process

The meeting is on ... > -Original Message- > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] > Sent: Tuesday, December 09, 2014 8:56 PM > To: dev@cloudstack.apache.org > Cc: Steve Wilson > Subject: RE: CloudStack Quality Process > > Yes I am pl

RE: CloudStack Quality Process

le to record the meeting? Maybe we can post it so others can view > it > if they are not able to attend (or only become interested after the first > couple > meetings and wants to catch up)? > > Will > On Dec 9, 2014 9:52 PM, "Animesh Chaturvedi" > w

RE: CloudStack Quality Process

? wait for wednesday? > > > > On Sat, Dec 6, 2014 at 5:46 PM, Chip Childers > > > > wrote: > > > Thanks for listening to my concerns folks... and I'll be rooting > > > for > > those > > > of you that are "doing" to co

RE: CloudStack Quality Process

v7hyim55 > > > > On Fri, Dec 5, 2014 at 6:36 PM, Animesh Chaturvedi < > animesh.chaturv...@citrix.com> wrote: > > > > > > > > having said so, I propose to set a date for our first (irc/goto) > > > meeting; wednesday 10 december 16:00 UTC? >

RE: CloudStack Quality Process

. It > > is hard to beat real time when working through this sort of stuff. > > > > Does this make sense to others? Thoughts? > > > > Will > > > > > > *Will STEVENS* > > Lead Developer > > > > *CloudOps* *| *Cloud Solutions Experts > >

RE: CloudStack Quality Process

> > *Will STEVENS* > Lead Developer > > *CloudOps* *| *Cloud Solutions Experts > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw > @CloudOps_ > > On Thu, Dec 4, 2014 at 5:17 PM, Animesh Chaturvedi < > animesh.chaturv...@citrix.com> wro

RE: 4.5.0 status

Cool, let's roll it out before the holidays. Folks I had called out in JIRA for New features and Improvements that were tagged for 4.5 but still open to update the status and move out the ones that did not make it to Future. Please take care of your issues Animesh > -Original Message-

RE: CloudStack Quality Process

CCC, I discussed with several people the idea that we commission a small > sub team to go hash out a proposal for how we handle the following topics > within the ACS community (which can then be brought back to the larger > community for ratification): > >> > >> * Continuo

RE: review board cleanup

> -Original Message- > From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com] > Sent: Friday, November 28, 2014 1:44 AM > To: dev@cloudstack.apache.org > Subject: Re: review board cleanup > > > > On 28-Nov-2014, at 2:43 pm, Rajani Karuturi wrote: > > > > Is there a way to 'force' close a

RE: [PROPOSAL] Move to github PR only during moratorium on commit

wrote: > > Hi, > > > >> On 23-Oct-2014, at 11:47 am, Animesh Chaturvedi > wrote: > ... > >> The approach for fixing issues in release branch first and master later is > not practical as we may miss out commits not made into master and future > release

RE: [PROPOSAL] Move to github PR only during moratorium on commit

> -Original Message- > From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com] > Sent: Thursday, October 23, 2014 1:22 AM > To: dev@cloudstack.apache.org > Subject: Re: [PROPOSAL] Move to github PR only during moratorium on > commit > > Hi, > > > On

RE: [PROPOSAL] Move to github PR only during moratorium on commit

> -Original Message- > From: sebgoa [mailto:run...@gmail.com] > Sent: Saturday, October 18, 2014 2:00 AM > To: dev@cloudstack.apache.org > Subject: [PROPOSAL] Move to github PR only during moratorium on > commit > > After [1] I would like to officially bring up the following proposal. >

RE: [ACS45]reverting commits or branching?

That’s correct Mike, Daan master is also the release branch for 4.5 and as such you are seeing issues getting fixed there. Animesh From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] Sent: Saturday, October 11, 2014 8:52 PM To: dev@cloudstack.apache.org Cc: Animesh Chaturvedi Subject: Re

Re: [ACS45]reverting commits or branching?

e need to revert a lot, Animesh. I don't think you can say that all the commits since the 1st amount to bugfixes. At least they are not commented as such. And if so, they should have gone into 4.4, not master. On Fri, Oct 10, 2014 at 8:19 PM, Animesh Chaturvedi mailto:animesh.chaturv.

RE: [ACS45]reverting commits or branching?

> -Original Message- > From: David Nalley [mailto:da...@gnsa.us] > Sent: Thursday, October 09, 2014 10:20 PM > To: Daan Hoogland > Cc: dev > Subject: Re: [ACS45]reverting commits or branching? > > I agree - it makes no sense - I am working on a branch minus the latest few > features. I'm

RE: Shellshock

While testing before release is needed but the component update process with new system template as we have now takes a long time logistically. Thanks Animesh > -Original Message- > From: Sheng Yang [mailto:sh...@yasker.org] > Sent: Tuesday, September 30, 2014 6:08 PM > To: > Subject:

Re: Review Request 25248: Fix NPE in case VM is started and its template does not exist anymore

> On Sept. 2, 2014, 7:01 p.m., Nitin Mehta wrote: > > engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java, line > > 814 > > > > > > Checking for template==null masks the whole problem. > > 1. Suc

RE: issues remaining for 4.4.1

> -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Thursday, August 07, 2014 1:53 AM > To: dev > Subject: issues remaining for 4.4.1 > > H, > > have a look at https://issues.apache.org/jira/browse/CLOUDSTACK- > 6358?filter=12328007 > > It is a disappoin

RE: [VOTE] git workflow

> > (Like most of the internet...) I strongly believe using cherry picks as the > basic > tool for (release) branch management is one of the worst choices you can > make. > > But. Please. Can. We. Just. Stop. Cherry. Picking!!! :-D [1] > [Animesh] Leo I don't mind moving to merging branches r

RE: [VOTE] git workflow

> -Original Message- > From: Sebastien Goasguen [mailto:run...@gmail.com] > Sent: Wednesday, August 06, 2014 3:19 PM > To: dev@cloudstack.apache.org > Subject: Re: [VOTE] git workflow > > [top posting, apologies in advance] > > I am on vacation, so I will go straight to it :) > > This

RE: [VOTE] git workflow

+0 While this protects master with only commits which are merges from release branch and keeps it clean but the issues that we have shift to develop branch. > -Original Message- > From: Rajani Karuturi [mailto:rajani.karut...@citrix.com] > Sent: Thursday, July 31, 2014 3:28 AM > To: de

RE: [VOTE] git workflow

> -Original Message- > From: Sebastien Goasguen [mailto:run...@gmail.com] > Sent: Friday, August 01, 2014 7:42 AM > To: dev@cloudstack.apache.org > Subject: Re: [VOTE] git workflow > > > On Aug 1, 2014, at 10:30 AM, Nate Gordon > wrote: > > > +1 > > > > On CI, I think it should run on

RE: [ACS44] template upgrade code

+ Abhi > -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Thursday, July 31, 2014 12:14 PM > To: dev > Subject: [ACS44] template upgrade code > > Devs, > > It seems there is a big problem in the 4.4 release. The templates need a new > java version but the

Re: [ACS44] merge of forward branch

gt; On Tue, Jul 29, 2014 at 5:43 AM, Animesh Chaturvedi > wrote: >> Yes that's how I did for 4.2 and 4.3 >> >> Sent from my iPhone >> >> On Jul 28, 2014, at 6:28 PM, "Sheng Yang" wrote: >> >> Daan, >> >> 4.4-forward sh

Re: [ACS44] merge of forward branch

Yes that's how I did for 4.2 and 4.3 Sent from my iPhone On Jul 28, 2014, at 6:28 PM, "Sheng Yang" mailto:sh...@yasker.org>> wrote: Daan, 4.4-forward should contain all the commits for 4.4. So 4.4-forward itself should be able to make as 4.4, without merge back to 4.4? That's what we want to

RE: [PROPOSAL]remove 4.4-forward

Yes that’s what we did for 4.3. Merge 4.4-forward into 4.4 > -Original Message- > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > Sent: Thursday, July 24, 2014 7:48 AM > To: dev@cloudstack.apache.org > Subject: Re: [PROPOSAL]remove 4.4-forward > > Yep...what Wei said. :) > >

RE: [VOTE] Apache Cloudstack 4.4.0

Hugo My understanding is only binding votes are counted. Non-binding votes are informational > -Original Message- > From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers > Sent: Wednesday, July 02, 2014 11:50 PM > To: dev@cloudstack.apache.org > Subject: Re: [VOTE] Apache

RE: [ACS4.4] RC1

Ok so we are good. Looking forward to VOTE thread > -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Tuesday, July 01, 2014 12:56 PM > To: dev > Subject: Re: [ACS4.4] RC1 > > thats the one, > > On Tue, Jul 1, 2014 at 8:16 PM,

RE: [ACS4.4] RC1

> Sent: Tuesday, July 01, 2014 5:05 AM > To: dev > Subject: Re: [ACS4.4] RC1 > > Animesh, > > Do you send this as a counter proposal or overriding the procedure on the > wiki? That is the one I am following. > > On Mon, Jun 30, 2014 at 9:56 PM, Animesh Chaturvedi >

RE: [ACS4.4] RC1

Daan We have been following the convention for Release VOTE threads like [1] as example. [1] http://markmail.org/message/ksyv4gftcsjc4pma Thanks Animesh > -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Monday, June 30, 2014 2:23 AM > To: dev > Subjec

RE: [ANNOUNCE] Santhosh Edukulla as a committer...

Congrats Santhosh > -Original Message- > From: Alex Huang [mailto:alex.hu...@citrix.com] > Sent: Monday, June 30, 2014 9:25 AM > To: dev@cloudstack.apache.org > Subject: [ANNOUNCE] Santhosh Edukulla as a committer... > > Hi All, > > The Project Management Committee (PMC) for Apache Cloud

RE: [ACS45][ACS50][PROPOSAL] move forward feature freeze

In response to Brocade I see your response "feature should be done (in it's branch) by 19th july. merging and fixing issues may take to mid august" that essentially means feature freeze (cutting the branch) by mid august Animesh > -Original Message----- > Fro

RE: [ACS45][ACS50][PROPOSAL] move forward feature freeze

t; > No certainly not, that would mean yet another bigger release and another > extra shift. It is now at 19 July And I was proposing to move it forward to > last 19th of june. > > On Wed, Jun 25, 2014 at 10:46 PM, Animesh Chaturvedi > wrote: > > > > > >

RE: [ACS45][ACS50][PROPOSAL] move forward feature freeze

> -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Thursday, May 29, 2014 10:45 AM > To: dev > Subject: Re: [ACS45][ACS50][PROPOSAL] move forward feature freeze > > Seeing what objections there might be I want to amend my proposal to > > 1. move forward

RE: [ACS44] are we RC-ready?

014 11:21 PM > To: dev > Subject: Re: [ACS44] are we RC-ready? > > I know some of them are not, but a lot may be. We all need to have a look > at that. I will, but the total number is over 350! (including those not marked > as critical.) > > On Mon, Jun 16, 2014 at 10:0

RE: [ACS44] are we RC-ready?

84 is a bug number to call RC ready unless the issues are not really critical > -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Monday, June 16, 2014 7:11 AM > To: dev > Subject: [ACS44] are we RC-ready? > > s far as I can tell the only remaining blocker

RE: [PROPOSAL] irc meeting for release 4.4

> -Original Message- > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] > Sent: Thursday, June 12, 2014 2:04 PM > To: dev@cloudstack.apache.org > Subject: RE: [PROPOSAL] irc meeting for release 4.4 > > > > > -Original Message

RE: [PROPOSAL] irc meeting for release 4.4

> -Original Message- > From: sebgoa [mailto:run...@gmail.com] > Sent: Thursday, June 12, 2014 5:37 AM > To: dev@cloudstack.apache.org > Subject: Re: [PROPOSAL] irc meeting for release 4.4 > > > On Jun 12, 2014, at 2:33 PM, Pierre-Luc Dion > wrote: > > > +1 > > > > I feel clue less for

RE: [DISCUSS] Release 4.4

ction. > > On Thu, Jun 12, 2014 at 12:43 AM, Animesh Chaturvedi > wrote: > > Yes we cannot cancel the release. IMHO we started the 4.4-forward > branch way early. I had created the forward branch for 4.2 and 4.3 only > after first RC because up until RC we have always seen

RE: [DISCUSS] Release 4.4

Yes we cannot cancel the release. IMHO we started the 4.4-forward branch way early. I had created the forward branch for 4.2 and 4.3 only after first RC because up until RC we have always seen a lot of code churn and I did not think RM can scale with all the cherry-picks given that RM has to foc

FW: New Defects reported by Coverity Scan for cloudstack

Folks please check on the issues reported. > -Original Message- > From: scan-ad...@coverity.com [mailto:scan-ad...@coverity.com] > Sent: Monday, June 09, 2014 7:37 PM > Subject: New Defects reported by Coverity Scan for cloudstack > > > Hi, > > > Please find the latest report on new de

RE: [ACS44] 112 unpicked cherries in 4.4-forward. why?

> -Original Message- > From: David Nalley [mailto:da...@gnsa.us] > Sent: Monday, June 09, 2014 9:24 AM > To: dev@cloudstack.apache.org > Subject: Re: [ACS44] 112 unpicked cherries in 4.4-forward. why? > > On Mon, Jun 9, 2014 at 10:39 AM, Mike Tutkowski > wrote: > > Right - we need to dec

Realhostip service extended till Sep 30th

Folks I wanted to provide an update on shutting down of RealhostIp service. Citrix has decided to move the date by one quarter and the new date will be Sep 30th. The new dates allow users of CloudStack additional time for updating their infrastructure. While testing Realhostip fixes addition

RE: [GIT] 4.3.0 vs 4.3.0-forward - where to commit?

> > [Animesh] Edison had merged 4.3-forward into 4.3 yesterday and I > > deleted 4.3-forward branch this morning > > > > So was there a lot of bug fixes that went in 4.3 during the merge ? if yes we > might want to release a 4.3.1 ? [Animesh] yes there were around 170 commits that came in with t

RE: [GIT] 4.3.0 vs 4.3.0-forward - where to commit?

> -Original Message- > From: sebgoa [mailto:run...@gmail.com] > Sent: Wednesday, June 04, 2014 11:17 PM > To: dev@cloudstack.apache.org > Subject: Re: [GIT] 4.3.0 vs 4.3.0-forward - where to commit? > > > On Jun 5, 2014, at 8:14 AM, ilya musayev wrote: > > > Looks like few patches tha

RE: New Defects reported by Coverity Scan for cloudstack

While we should wait for the next run for actual results but I am expecting the defect density as reported by Coverity to drop down from 6.4 to about 3.4 after excluding AWSAPI generated code. Animesh > -Original Message- > From: Animesh Chaturvedi [mailto:animesh.c

RE: New Defects reported by Coverity Scan for cloudstack

Rajani Thanks for bringing this up, I looked at the analysis settings and I think the pattern to exclude aws code should have a leading /. I have fixed it and lets check it on the next run. We should see a significant bump up in defect density. Good job in noticing this. Thanks Animesh >

RE: [DISCUSS] old forward branches

I will merge 4.3-forward into 4.3 later today. Animesh > -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Saturday, May 31, 2014 1:38 PM > To: dev > Subject: [DISCUSS] old forward branches > > The older forward branches are still heavily used, while the r

RE: [ANNOUNCE] Saksham Srivastava as committer

Congrats Saksham > -Original Message- > From: sebgoa [mailto:run...@gmail.com] > Sent: Wednesday, May 28, 2014 11:48 PM > To: dev@cloudstack.apache.org > Subject: [ANNOUNCE] Saksham Srivastava as committer > > The Project Management Committee (PMC) for Apache CloudStack has asked > Saksha

Can we use "In Progress" state when we start working on an issue

Folks One thing as former RM I have struggled with is visibility of whether an issue is being worked upon rather than being just assigned. JIRA has a simple nice thing called "In Progress" please make use of it. When you start working on an issue I suggest please change the state to "In Progr

RE: New Defects reported by Coverity Scan for cloudstack

Hugo Can you share the latest results? How can I get access to the reports? Animesh > -Original Message- > From: Hugo Trippaers [mailto:trip...@gmail.com] > Sent: Friday, November 29, 2013 7:58 AM > To: dev@cloudstack.apache.org > Subject: Fwd: New Defects reported by Coverity Scan for c

RE: [PROPOSAL] Using continuous integration to maintain our code quality...

> > I'll also state for the record, that I will -1 any decision that leads us to > depend on a single company's infrastructure as a project level policy. That > said, having it available from Citrix for use is a great thing for that > company > to donate! It's going to be difficult to balance o

RE: [PROPOSAL] Using continuous integration to maintain our code quality...

> -Original Message- > From: sebgoa [mailto:run...@gmail.com] > Sent: Tuesday, May 20, 2014 11:30 PM > To: dev@cloudstack.apache.org > Subject: Re: [PROPOSAL] Using continuous integration to maintain our code > quality... > > > On May 21, 2014, at 12:40 AM,

RE: [ACS44][PROPOSAL] old blocker bugs

Daan I concur with Sudha we should not change the priority of individual defects without technical reasons. The outgoing defect rate is much lower for this time of the release and certainly is a concern as you have raised. We should publish daily list of blockers and ask for status update. Yo

RE: [PROPOSAL] Using continuous integration to maintain our code quality...

Hugo without putting certain rules we are not going to get out of the situation. I think it may seem draconian but stating "No merges are allowed without a successful run of the automation" is beneficial for everyone. It forces focus on automation and helps mitigate regression. If we run into c

RE: [ACS44] critical issue assesment

I will put a slot in my calendar for triaging bugs daily from now on. Animesh > -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Wednesday, May 07, 2014 1:05 AM > To: dev > Subject: [ACS44] critical issue assesment > > Friend and (yes I consider you) col

RE: 4.4 release-notes

ogland [mailto:daan.hoogl...@gmail.com] > Sent: Monday, May 05, 2014 11:53 AM > To: Animesh Chaturvedi > Cc: dev > Subject: Re: 4.4 release-notes > > Animesh, > > Can you (give me rights to) add these filters to the release dashboard? > > On Fri, May 2, 2014 at 4:43 AM, Pierr

[OFFLIST] I will be offlist from 4/17 - 5/6

Folks FYI I will be out on PTO for 2 weeks starting 4/17 Thanks Animesh

RE: 4.3 system vm template job failing in jenkins

May be this can be a quick hackathon in collab. Copying Wido and Hugo > -Original Message- > From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com] > Sent: Thursday, April 10, 2014 9:18 AM > To: dev@cloudstack.apache.org > Subject: Re: 4.3 system vm template job failing in jenkins

RE: OpenSSL vunerability (bleedheart)

Courtesy Chiradeep - CPVM uses JSSE so that should not be affected - VR is not affected since it does not offer any HTTPS/TLS service. The RA VPN and S2S VPN use the OpenSSL lib only for crypto and not for any transport - The only vulnerable service is the volume upload service and template copy

RE: [ACS4.3] Schedule reminder : 10 days to code freeze

ule reminder : 10 days to code freeze > > 4.3/4.4? > > > > -Original Message- > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] > Sent: Tuesday, November 26, 2013 9:20 PM > To: dev@cloudstack.apache.org > Subject: [ACS4.3] Schedule reminder

RE: release estimations for ACS 4.3

Release VOTE passed we are working on formal release announcement and it should be out soon Animesh > -Original Message- > From: Andrei Mikhailovsky [mailto:and...@arhont.com] > Sent: Monday, March 24, 2014 7:26 AM > To: dev@cloudstack.apache.org > Subject: release estimations for ACS 4.

Re: [VOTE] [RESULTS] Apache CloudStack 4.3.0 (ninth round)

ause all my test hypervisors only leverage vSwitch0. > > If i undefine the vSwitch0 label, ACS then picks up proper default vSwitch0. > > On 3/22/14, 3:39 AM, Wilder Rodrigues wrote: >> Great news! >> >> Have a nice weekend, guys and gals! >> >> Cheers,

[VOTE] [RESULTS] Apache CloudStack 4.3.0 (ninth round)

elease into the distribution repo now and other release tasks. Thanks Animesh > -Original Message----- > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] > Sent: Tuesday, March 18, 2014 12:06 PM > To: dev@cloudstack.apache.org > Subject: [VOTE] Apache CloudStack 4.3.0

RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)

+ 1 (binding) verified the release artifacts and tested with devcloud > -Original Message- > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] > Sent: Tuesday, March 18, 2014 12:06 PM > To: dev@cloudstack.apache.org > Subject: [VOTE] Apache CloudStack 4.3

RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)

Can you clear up browser cache and try again? > -Original Message- > From: Animesh Chaturvedi > Sent: Thursday, March 20, 2014 4:54 PM > To: dev@cloudstack.apache.org > Cc: Jessica Wang > Subject: RE: [VOTE] Apache CloudStack 4.3.0 (ninth round) > > That'

RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)

last > > round. > > > > > -Original Message- > > > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] > > > Sent: Tuesday, March 18, 2014 12:06 PM > > > To: dev@cloudstack.apache.org > > > Subject: [VOTE] Apache CloudStac

RE: concole proxy in 4.3RC9

> -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Thursday, March 20, 2014 9:50 AM > To: dev > Subject: Re: concole proxy in 4.3RC9 > > meaning the console of the ssvm? or the cpvm? > > I just confirmed myself that there is indeed a diff between 4.2.1 a

RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)

> -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Thursday, March 20, 2014 10:25 AM > To: dev > Cc: Amogh Vasekar; Suresh Sadhu > Subject: Re: [VOTE] Apache CloudStack 4.3.0 (ninth round) > > On Thu, Mar 20, 2014 at 6:21 PM, Ani

RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)

>> Thanks in advance. > >>> > >>> Cheers, > >>> Wilder > >>> > >>> -Original Message- > >>> From: ilya musayev [mailto:ilya.mailing.li...@gmail.com] > >>> Sent: Tuesday, March 18, 2014 9:11 PM > >>&g

RE: [ACS 4.4] RE: 4.4 Feature Freeze

Daan/ Hugo We need to update the wiki release page for 4.4 and also setup the JIRA dashboard similar to what I did for 4.2 and 4.3. Let me know if you have questions on how it was done for 4.3 Thanks Animesh > -Original Message- > From: Sudha Ponnaganti [mailto:sudha.ponnaga...@citrix.

RE: Release cadence

> -Original Message- > From: Rajani Karuturi [mailto:rajani.karut...@citrix.com] > Sent: Wednesday, March 19, 2014 4:46 AM > To: dev > Subject: Re: Release cadence > > The primary problem I feel is that we dont plan our releases.(I am fairly new > here and I may be wrong) The role of the

[VOTE] Apache CloudStack 4.3.0 (ninth round)

Hi All, I've created a 4.3.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.git;a=shortlog;h=refs/heads/4.3 Commit: 0810029f274878eca8fd74b44ab1117054e929a5 List of changes: New Features in 4.3: ht

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

> -Original Message- > From: Nux! [mailto:n...@li.nux.ro] > Sent: Tuesday, March 18, 2014 7:04 AM > To: Animesh Chaturvedi > Cc: dev@cloudstack.apache.org; Edison Su > Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round) > > On 17.03.2014 22:39,

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

> -Original Message- > From: Nux! [mailto:n...@li.nux.ro] > Sent: Monday, March 17, 2014 3:57 PM > To: dev@cloudstack.apache.org > Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round) > > On 17.03.2014 22:39, Animesh Chaturvedi wrote: > > Edison > &

[CANCELLED] [VOTE] Apache CloudStack 4.3.0 (eighth round)

Cancelling this VOTE too because of Nux's finding of KVM SecurityGroup is broken. Thanks Animesh From: Animesh Chaturvedi Sent: Wednesday, March 12, 2014 5:27 PM To: dev@cloudstack.apache.org Subject: [VOTE] Apache CloudStack 4.3.0 (eighth round) Hi All, I've created a 4.3.0 rel

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

Edison Thanks for taking care of this issue. Nux can you try with this fix and I will go off building RC > -Original Message- > From: Edison Su [mailto:edison...@citrix.com] > Sent: Monday, March 17, 2014 2:52 PM > To: dev@cloudstack.apache.org > Subject: RE: [VOTE] Apache CloudStack 4.3

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

...@stratosec.co>> wrote: > > Before we go to 9th round, let's get > https://issues.apache.org/jira/browse/CLOUDSTACK-6156 resolved. > > I'm pretty busy this week, but will see if I can come up with. Just tried > doing > a clean awsapi build on a clean AWS ins

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

gt; > I'm pretty busy this week, but will see if I can come up with. Just tried > doing > a clean awsapi build on a clean AWS instance again and it still fails. > > > On Mar 12, 2014, at 5:26 PM, Animesh Chaturvedi > mailto:animesh.chaturv...@citrix.com>> &g

RE: 32 vs 64 bit systemvm on 43 and secondary NFS storage used / capacity Re: [VOTE] Apache CloudStack 4.3.0 (eighth round)

98534883328,"result":true,"contextMap":{},"wait":0}}] > ... > > With a 32-bit systemvm, ACS43 GetStorageStatsAnswer reports used=0 and > capacity=0. > > /Ove > > > On 03/13/2014 01:26 AM, Animesh Chaturvedi wrote: > > Hi All,

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

> -Original Message- > From: Edison Su [mailto:edison...@citrix.com] > Sent: Friday, March 14, 2014 2:57 PM > To: dev@cloudstack.apache.org > Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round) > > Add a fix: e5c391fcf3852e50ebd99d4a72fd51d1753b05eb on 4.3-forward > branch. > I do

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

> -Original Message- > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] > Sent: Friday, March 14, 2014 2:28 PM > To: dev@cloudstack.apache.org > Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round) > > > > > -Original Me

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

> -Original Message- > From: Edison Su [mailto:edison...@citrix.com] > Sent: Friday, March 14, 2014 1:59 PM > To: dev@cloudstack.apache.org > Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round) > > The following change will the be root cause: > > -refs = execute("iptables

RE: cherrypick to 4.3

If I build another RC I will pick it up From: Alena Prokharchyk Sent: Friday, March 14, 2014 12:43 PM To: Animesh Chaturvedi Cc: dev@cloudstack.apache.org Subject: Re: cherrypick to 4.3 Animesh, one more commit for the same bug needs to be cherry-picked: 94817c1b4b89cfa69f2db50a7060dcb7d7c39dbb

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

> -Original Message- > From: Edison Su [mailto:edison...@citrix.com] > Sent: Friday, March 14, 2014 12:37 PM > To: dev@cloudstack.apache.org > Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round) > > > > > -Original Message- > > From: Nux! [mailto:n...@li.nux.ro] > > Sent

RE: Differences between 4.3 and 4.3-forward

> -Original Message- > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > Sent: Friday, March 14, 2014 7:43 AM > To: dev@cloudstack.apache.org > Subject: Re: Differences between 4.3 and 4.3-forward > > Yes, and we definitely cannot just take all of 4.3.1 and put it in 4.3 as ma

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

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

> -Original Message- > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] > Sent: Thursday, March 13, 2014 1:25 PM > To: dev@cloudstack.apache.org > Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round) > > > > > -Original Message

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

> -Original Message- > From: Nux! [mailto:n...@li.nux.ro] > Sent: Thursday, March 13, 2014 12:41 PM > To: dev@cloudstack.apache.org > Subject: Re: [VOTE] Apache CloudStack 4.3.0 (eighth round) > > On 13.03.2014 18:58, Nux! wrote: > > On 13.03.2014 00:2

RE: [WIKI] Release test procedure contains wrong version of Java Open JDK

The change has been reverted. > -Original Message- > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] > Sent: Wednesday, March 12, 2014 7:32 PM > To: dev@cloudstack.apache.org > Subject: RE: [WIKI] Release test procedure contains wrong version of Java >

RE: [WIKI] Release test procedure contains wrong version of Java Open JDK

Yes that is correct. 1.7 was changes in master / 4.4. I will revert the changes for 4.3 release test procedure > -Original Message- > From: Amogh Vasekar [mailto:amogh.vase...@citrix.com] > Sent: Wednesday, March 12, 2014 1:41 PM > To: dev@cloudstack.apache.org > Subject: Re: [WIKI] Relea

[VOTE] Apache CloudStack 4.3.0 (eighth round)

Hi All, I've created a 4.3.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.git;a=shortlog;h=refs/heads/4.3 Commit: 6a6ec648099553a42f830dcd566eab2452428908 List of changes: New Features in 4.3: https

RE: [4.3][CLOUDSTACK-6232]isolated network can no longer reserve ip range

> -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Wednesday, March 12, 2014 11:45 AM > To: dev; Animesh Chaturvedi > Subject: [4.3][CLOUDSTACK-6232]isolated network can no longer reserve ip > range > > Animesh, I really feel

RE: [VOTE] Apache CloudStack 4.3.0 (seventh round)

> -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Wednesday, March 12, 2014 2:52 PM > To: dev > Cc: Hugo Trippaers; Animesh Chaturvedi > Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round) > > If we produce a new f

  1   2   3   4   5   6   7   8   >