RE: [DISCUSS] Release principles for Apache CloudStack

Remi, couple of questions on the branching part - when we take the Feature PR and Feature is back in Master, feel like we are potentially destabilizing Master ? I know, currently we push changes to master even before anything is tested fully - agree, we are now running the Travis test before

Re: [DISCUSS] LTS releases?

On Jul 2, 2015, at 4:58 PM, Remi Bergsma wrote: > Bug fixing in older releases is actually a lot of work. For security related > issues we could maybe do it. > > Personally, I prefer to have a fast release cycle and smooth (tested) upgrade > paths over 2-year LTS release cycle. It's more agi

Re: [DISCUSS] Release principles for Apache CloudStack

On Jul 3, 2015, at 9:06 AM, Raja Pullela wrote: > Remi, > > couple of questions on the branching part - when we take the Feature PR and > Feature is back in Master, feel like we are potentially destabilizing Master > ? I know, currently we push changes to master even before anything is >

Re: IRC and Slack

Some great ideas in there. I am +1 for: -consolidate #cloudstack-dev and #cloudstack -move bots to #cloudstack-announce -Remi's idea to publish slack message to #cloudstack (and vice versa). -the idea to use something like discourse or stack overflow etc… Somebody wants to take this on :) On

Re: [DISCUSS] Release principles for Apache CloudStack

> On 3 jul. 2015, at 09:21, sebgoa wrote: > > On Jul 3, 2015, at 9:06 AM, Raja Pullela wrote: > >> Remi, >> >> couple of questions on the branching part - when we take the Feature PR and >> Feature is back in Master, feel like we are potentially destabilizing Master >> ? I know, currentl

Re: [PROPOSAL] Commit to master through PR only

On Jul 2, 2015, at 8:43 AM, Wilder Rodrigues wrote: > Sateesh and Rajesh, > > It seems you were the only guys who +1 the squash idea. Could you please > share with us what benefits you think squashing commits will bring? > > I wil give you the simplest example that could come to my mind to

Re: [DISCUSS] Release principles for Apache CloudStack

Hi Rajani, all, I do think we have the same goal in mind: no regression and no cherry-pick mess. Just did some reading on "tofu scale" and see two issues: - if it doesn't happen / isn't completed we'll have regression as we've seen before. I want a working model that prevents regression by defau

Re: IRC and Slack

On Fri, Jul 3, 2015 at 9:27 AM, sebgoa wrote: > Some great ideas in there. > > I am +1 for: > > -consolidate #cloudstack-dev and #cloudstack > -move bots to #cloudstack-announce > -Remi's idea to publish slack message to #cloudstack (and vice versa). > -the idea to use something like discourse or

Re: [DISCUSS] Release principles for Apache CloudStack

On Fri, Jul 3, 2015 at 10:06 AM, Remi Bergsma wrote: > Hi Rajani, all, > > I do think we have the same goal in mind: no regression and no cherry-pick > mess. > > Just did some reading on "tofu scale" and see two issues: > - if it doesn't happen / isn't completed we'll have regression as we've > s

Re: IRC and Slack

I setup a proof-of-concept a while back to test it: http://cloudstackdev.slack.com. There currently are around 30 people, mostly dev from this list. Anyone with an @apache.org account can sign-up and anyone else could ask me, Daan, Rohit, Wilder or Funs for an invite (for now). I can imagine we

Re: IRC and Slack

On Jul 3, 2015, at 10:17 AM, Remi Bergsma wrote: > I setup a proof-of-concept a while back to test it: > http://cloudstackdev.slack.com. There currently are around 30 people, mostly > dev from this list. > > Anyone with an @apache.org account can sign-up and anyone else could ask me, > Daan,

[GitHub] cloudstack pull request: Vpcr Marvin test and some fixes for vprc

Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/558#issuecomment-118274161 Nice one, @isoutham ! I will test it this week and also try to get someone else to have a look so we get the 2 LGTM needed to merge. Thanks!

[GitHub] cloudstack pull request: Vpcr Marvin test and some fixes for vprc

Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/558#issuecomment-118274398 Travis failed due timeout... so, that's not relevant and won't be taken into account when reviewing the PR: === No output has been received in th

Re: IRC and Slack

Yes, I’ll have some time off coming up so I’ll give it a go. > any chance you can try that IRC/Slack integration pointing to #cloudstack ?

[GitHub] cloudstack pull request: Vpcr Marvin test and some fixes for vprc

Github user remibergsma commented on the pull request: https://github.com/apache/cloudstack/pull/558#issuecomment-118275941 @isoutham @wilderrodrigues is there a way to trigger the build again? --- If your project is set up for it, you can reply to this email and have your reply appe

[GitHub] cloudstack pull request: Vpcr Marvin test and some fixes for vprc

Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/558#issuecomment-118279061 Only if something get pushed to the branch which generated the PR. Only 1 job out of 9 timed out... I wouldn't bother. --- If your project is set u

Re: [DISCUSS] LTS releases?

Sebastien, So wouldn't it be nice to make clear which release is still supported and which release is not? On 03.07.2015 09:20, sebgoa wrote: > I think we got in a situation with 4.4 that called for us to keep maintaining > 4.3….and even after 4.5 was released. Because 4.3 was seen as a good re

Re: [GitHub] cloudstack pull request: As an operator I want to be able to chang...

John, The descriptive message should be in the merge commit. It should state the cause of the collective. each individual should have a smaller message stating the reason for a simple atomic change. Taking what you say here we could squah the whole repo with the message 'making an cloud orchestrat

Re: [DISCUSS] LTS releases?

On Jul 3, 2015, at 11:13 AM, Rene Moser wrote: > Sebastien, > > So wouldn't it be nice to make clear which release is still supported > and which release is not? > > On 03.07.2015 09:20, sebgoa wrote: > >> I think we got in a situation with 4.4 that called for us to keep >> maintaining 4.3….

RE: [PROPOSAL] Commit to master through PR only

Personally, if I find a bug, I often go back to find when and why it was introduced, and I find it much more useful to be able to identify a specific changeset rather than a large pull request. -- Stephen Turner -Original Message- From: John Burwell [mailto:john.burw...@shapeblue.com]

[GitHub] cloudstack pull request: BUG-ID:CLOUDSTACK-7472: kvmclock fix for ...

Github user bhaisaab commented on the pull request: https://github.com/apache/cloudstack/pull/557#issuecomment-118302519 LGTM, merging --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this fea

[GitHub] cloudstack pull request: BUG-ID:CLOUDSTACK-7472: kvmclock fix for ...

Github user asfgit closed the pull request at: https://github.com/apache/cloudstack/pull/557 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] cloudstack pull request: CLOUDSTACK-8603: Random list VM failures ...

Github user bhaisaab commented on the pull request: https://github.com/apache/cloudstack/pull/551#issuecomment-118303081 LGTM, merging. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this fe

[GitHub] cloudstack pull request: CLOUDSTACK-8603: Random list VM failures ...

Github user asfgit closed the pull request at: https://github.com/apache/cloudstack/pull/551 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: [DISCUSS] LTS releases?

Agree with the ideal world scenario :-) If we look at it from the other side: Why is it that people want to stay on older releases? From personal experience I know that in the beginning the 4.4 release wasn’t that stable. I upgraded production systems from 4.3.0 to 4.4.2 and it was painful. Th

Re: [PROPOSAL] Commit to master through PR only

Hi John, If you look at the discrete operations wearing a hat of a Project Manager, you won’t care… neither would I. However, from a Software Engineer perspective, as much as the other people contributing with the Java code, I do care and it really makes reviewing the PR easier. As a consumer

Build failed in Jenkins: simulator-singlerun #1333

See -- Started by upstream project "build-master-simulator" build number 2150 originally caused by: Started by an SCM change Started by upstream project "build-master" build number 2444 origin

Jenkins build is back to normal : build-master-jdk18 #183

See

Build failed in Jenkins: package-rhel63-4.5 #290

See -- Started by upstream project "build-4.5" build number 494 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on rpmbuilder-2 i

Build failed in Jenkins: simulator-4.5-singlerun #250

See -- Started by upstream project "build-4.5-simulator" build number 305 originally caused by: Started by upstream project "build-4.5" build number 494 originally caused by: Started by an

Re: [DISCUSS] Release principles for Apache CloudStack

I agree to the goal. No regressions can be achieved either by cherry-picks or merges. Both requires developers to agree to it and has equal probability to miss. The advantage in case of merge is, lets say you do a commit a1 to 4.5 branch and forget to merge to master. now, someone else did a2 and

[GitHub] cloudstack pull request: BUG-ID: CLOUDSTACK-8484 - Hosts without t...

Github user sudhansu7 commented on the pull request: https://github.com/apache/cloudstack/pull/335#issuecomment-118331438 @remibergsma @karuturi I have added marvin test for this issue. Test result from local setup: Sudhansus-MAC:cloudstack sudhansu$ nosetests --with-m

Fairly serious system VM template issue.

Hello all, One of my co-workers and I just installed a Cloudstack 4.5 system. All seemed well until we started trying to import templates from another system we manage. The SSVM downloads the image, then check it using the "vhd-util" utility from XenServer. The error generated is "/bin/vhd-u

Re: SystemVM (kvm) : 3 different versions for the same CloudStack version (4.5.1)

On Mon, Jun 8, 2015 at 5:25 PM, David Nalley wrote: > On Mon, Jun 8, 2015 at 4:52 AM, Erik Weber wrote: > > I'm up for it, delivering from an official ASF source gives it a sense of > > more authenticity (IMHO). > > > > Could we host the RPM/DEB repos there as well? > > > > Yes, that's the easy

Re: [ANNOUNCE] Wilder Rodrigues as a new PMC member of CloudStack

finally someone to do the hard work. Go get'm Wilder! On Thu, Jul 2, 2015 at 5:51 PM, Marco Sinhoreli wrote: > Parabéns Wilder! > > Abs! > > Marco Sinhoreli > > Consultant Manager > > > > > > > > > Phone: +55 21 2586 6390 | Fax: +55 21 2586 6002 | Mobile: +55 21 99159 > 4713 | Mobile: +55 21 9827

Re: [ANNOUNCE] Karen Voung as a new PMC member of CloudStack

Ah, someone to keep the cowboys in line. success Karen. On Fri, Jul 3, 2015 at 7:20 AM, Koushik Das wrote: > Congrats Karen! > > -Original Message- > From: John Burwell [mailto:john.burw...@shapeblue.com] > Sent: Thursday, 2 July 2015 23:45 > To: dev@cloudstack.apache.org > Cc: Karen Vuon

Re: IRC and Slack

+0 Email and MLs are going to stay, so for IMs and chatting we can use one or more of such tools. I like Slack, the searchable history and whatnot, but I think realtime communication in general may face the same problems as with using IRC. Another issue with using tools like slack, hipchat etc.

Re: [ANNOUNCE] Karen Voung as a new PMC member of CloudStack

Congrats Karen! > On 02-Jul-2015, at 11:45 pm, John Burwell wrote: > > All, > > The Project Management Committee (PMC) for Apache CloudStack are pleased to > announce that Karen Voung (karenv) has accepted our invitation to join the > PMC. > > Please join me in congratulating her. > > On behalf

Re: [DISCUSS] Release principles for Apache CloudStack

Hi Rajani, Happy to hear we agree on the goal and on the release process. Also great you want to join the RM effort! What remains is a discussion about the maintenance. I think the difference in our approaches, is that you say “commit to release branch, then bring it to master” and I say the o

Re: IRC and Slack

On Fri, Jul 3, 2015 at 7:30 PM, Rohit Yadav wrote: > +0 > > Email and MLs are going to stay, so for IMs and chatting we can use one or > more of such tools. I like Slack, the searchable history and whatnot, but I > think realtime communication in general may face the same problems as with > using