Re: Next ACS release?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/22/2015 12:38 AM, Andrei Mikhailovsky wrote: > Ilya, Mark, thanks for your feedback, > > I also see the need to restructure the release schedule for ACS as > the current release cycles are not really working. There is no > _reliable_ release c

Re: getting rid of 3rd party repositories (ceph, libvirt)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/21/2015 09:12 PM, Laszlo Hornyak wrote: > Hi, > > I have uploaded the libvirt dependency to maven central and you > should never get the maven failure if the libvirt.org server goes > down, it will be downloaded from central. I have sent a PR

Jenkins build is still unstable: simulator-singlerun #1135

See

RE: Next ACS release?

I have to admit I'm a bit sceptical because when we did have a four-month release cycle, we never seemed to manage to meet it. Personally I think six-monthly might be easier. Having said that, part of the problem was the long close-down period where we kept finding critical bugs, so more automa

announce mail to announce lists

Can someone forward the announce mail I send yesterday to the lists annou...@apache.org and annou...@cloudstack.apache.org. My login at apache is not allright and mail from other domains to these lists is rejected. thanks -- Daan

Re: Next ACS release?

I strongly advice my fellow community members to go for a lower duration, not longer. Each feature deserves a release and I'd say let's release every 2 months, provides a new feature was added. Also we now release fix releases when we feel the urgency. This means users, that are not also developers

Re: Next ACS release?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/22/2015 10:08 AM, Daan Hoogland wrote: > I strongly advice my fellow community members to go for a lower > duration, not longer. Each feature deserves a release and I'd say > let's release every 2 months, provides a new feature was added. > A

Re: Next ACS release?

the community is us... (well not just us, Wido) Having a master RM would be my first step towards this goal. On Wed, Apr 22, 2015 at 10:18 AM, Wido den Hollander wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > On 04/22/2015 10:08 AM, Daan Hoogland wrote: >> I strongly advice my f

Re: Next ACS release?

On Wed, Apr 22, 2015 at 9:49 AM, Stephen Turner wrote: > I have to admit I'm a bit sceptical because when we did have a four-month > release cycle, we never seemed to manage to meet it. Personally I think > six-monthly might be easier. > > Having said that, part of the problem was the long close-

Re: Next ACS release?

What is required for this RM to happen? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Daan Hoogland" > To: "dev" > Sent: Wednesday, 22 April, 2015 09:28:27 > Subject: Re: Next ACS release? > the community is us... (well not just u

Re: Next ACS release?

Yes, Eric and the amount of qa needed is less as well. Bare with me for a little rant here. When less new features are introduced less new interdependencies are introduced. I could try and expand on this but people make phd on the subject so that would be presumptuous of me. un-educated guess is

Re: Next ACS release?

for us all to agree we should go this way. then for us to have a (scheduled?) volunteer. On Wed, Apr 22, 2015 at 10:44 AM, Nux! wrote: > What is required for this RM to happen? > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > - Original Message - >> F

Re: Next ACS release?

On Wed, Apr 22, 2015 at 10:46 AM, Daan Hoogland wrote: > On Wed, Apr 22, 2015 at 10:29 AM, Erik Weber wrote: > > On Wed, Apr 22, 2015 at 9:49 AM, Stephen Turner < > stephen.tur...@citrix.com> > > wrote: > > > >> I have to admit I'm a bit sceptical because when we did have a > four-month > >> rel

Re: Next ACS release?

I'd be happy to help here as well. Last week in Austin, we also discussed this topic a couple of times. I do agree shorter release cycles are better. In my opinion, the first thing to improve is the minor releases in both the 4.4 and 4.5 branches. If we speed those up to let's say once every 2-wee

AW: Next ACS release?

In my opinion we need to improve QA! If smaller cycles will help to do that this is the way to go. I joined this list after the "release" of 4.5, but as far as I know 4.5 is not really usable for production because of critical bugs in it that good QA would not have passed. So if CS releases new

[GitHub] cloudstack pull request: Incorporated Review comments provided in ...

GitHub user sanju1010 opened a pull request: https://github.com/apache/cloudstack/pull/187 Incorporated Review comments provided in PR # 183 You can merge this pull request into a Git repository by running: $ git pull https://github.com/sanju1010/cloudstack CS-38815 Alternati

[GitHub] cloudstack pull request: Add more verifications to make sure that ...

Github user sanju1010 closed the pull request at: https://github.com/apache/cloudstack/pull/183 --- 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

[GitHub] cloudstack pull request: Add more verifications to make sure that ...

Github user sanju1010 commented on the pull request: https://github.com/apache/cloudstack/pull/183#issuecomment-95104669 Created new PR #187 with the review comments incorporated. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] cloudstack pull request: Escalations

Github user sanju1010 commented on the pull request: https://github.com/apache/cloudstack/pull/184#issuecomment-95113695 Looks good. I am taking this patch. --- 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

RE: [DISCUSS] 4.6 release management

Sebastien, I am taking about the tests we have under "test/integration/smoke" folder. Not sure how the tests run through Travis, will try to understand. These are tests were run on a local cloudstack env. best, Raja -Original Message- From: Sebastien Goasguen [mailto:run...@gmail.com]

[GitHub] cloudstack pull request: Incorporated Review comments provided in ...

Github user sanju1010 closed the pull request at: https://github.com/apache/cloudstack/pull/187 --- 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

Re: getting rid of 3rd party repositories (ceph, libvirt)

Hi Wido, I should have read the git log first :-) No license issues and no code change needed. All I want to have is rados-java in the central maven repository for two reasons: - central is the most reliable service - we can not upload our artifacts to central until we have a dependency on other

Jenkins build is still unstable: simulator-singlerun #1136

See

Re: Jenkins build is still unstable: simulator-singlerun #1136

The simulator run has not been stable for three weeks. Anybody knows what the problem with the ISO test is? On Wed, Apr 22, 2015 at 1:48 PM, wrote: > See > -- Daan

Re: Jenkins build is still unstable: simulator-singlerun #1136

Traceback (most recent call last): File "/var/lib/jenkins/workspace/simulator-singlerun/tools/marvin/marvin/sshClient.py", line 121, in createConnection timeout=self.timeout) File "/usr/local/lib/python2.7/site-packages/paramiko/client.py", line 251, in connect retry_on_signal(lambda

Re: [DISCUSS] Moving to Java 8

Hi Wido, Thanks for the reply and making a good point concerning Ubuntu 14.04. Besides the difficulty in writing testes without increasing even more out technical dept, another point on the Java 8 platform is the EOL (end of this month) of Java 1.7. For now I created a ticket on Apache Jira to

Re: [DISCUSS] Moving to Java 8

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/22/2015 02:13 PM, Wilder Rodrigues wrote: > Hi Wido, > > Thanks for the reply and making a good point concerning Ubuntu > 14.04. > > Besides the difficulty in writing testes without increasing even > more out technical dept, another point on

Doc need to update for ACS 4.5 Important

Hi All, I installed ACS 4.5 with reference below link. http://cloudstack-installation.readthedocs.org/en/latest/management-server/index.html#install-the-management-server-on-the-first-host In the doc there is a step which says need to download the vhd-util and copy. Downloading vhd-util

[GitHub] cloudstack-docs-install pull request: Update xenserver.rst

GitHub user SheerIce opened a pull request: https://github.com/apache/cloudstack-docs-install/pull/23 Update xenserver.rst Fixed typo. You can merge this pull request into a Git repository by running: $ git pull https://github.com/SheerIce/cloudstack-docs-install patch-1 Alter

[GitHub] cloudstack pull request: CLOUDSTACK-8395: vmops plugin should work...

Github user bhaisaab commented on the pull request: https://github.com/apache/cloudstack/pull/186#issuecomment-95254152 @xenserverarmy @agneya2001 the latest update I did was to flush iptables rules before setting up ipset rules, this removes ipset references so easier to remove old i

RE: Next ACS release?

I fully support the idea of a stable master with an automated CD process to protect against regressions. However, we obviously don't currently have fantastic integration testing otherwise we wouldn't have relied on 'people' to pick up the release blockers recently. A 2 week release cycle I

Re: Next ACS release?

+1 what Paul said. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Paul Angus" > To: dev@cloudstack.apache.org > Sent: Wednesday, 22 April, 2015 19:13:04 > Subject: RE: Next ACS release? > I fully support the idea of a stable master

Re: Next ACS release?

Hi, The '2 week cycle' was intended as something to work towards, like a mission. The nice thing is that it immediately shows that we cannot achieve such a thing if we keep our current method of (semi)manual testing, as you said. Totally agree. That's why we need to improve on our automated funct

Re: [DISCUSS] Moving to Java 8

Is java 1.8 on the roadmap for ubuntu 14? It does not seem to make sense to have a LTS supported until 2019 with a JDK no longer supported. On Wed, Apr 22, 2015 at 2:43 PM, Wido den Hollander wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > On 04/22/2015 02:13 PM, Wilder Rodrigu

Re: AW: Next ACS release?

We need a distributed QA framework, where folks with all kind of setups - fetch code continuously, build cloudstack, run tests, sanitize outputs and submit upstream. Some folks on this list would want to remain anonymous, but this build, deploy, test and submit results process needs to be auto

Re: Next ACS release?

We just have to do it. We just freeze master at some point, do all of the release bugfixes, and when it is solid enough to pass a release vote we branch a release from it, and then only allow merges to master that have been tested in a merge branch, or something along those lines. Things will slip

Re: [DISCUSS] Moving to Java 8

I agree with Wido. The first thing that came to mind is legacy installs of CentOS that have java6,7 but not java8. I'd prefer to wait until we can reasonably say that Ubuntu 12.04 and CentOS6.x are artifacts of the past that people should not be running (maybe 6-12mo past LTS, or something). Unless

Re: [DISCUSS] Moving to Java 8

Kind of a tangent, but I'd actually like to see some work done to clean up LibvirtComputing resource. One model I've prototyped that seems to work is to create an annotation, such as 'KVMCommandExecutor', with a 'handles' property. With this annotation, you implement a class that handles, e.g. Star

Re: Next ACS release?

On Wed, Apr 22, 2015 at 4:47 PM, Marcus wrote: > We just have to do it. We just freeze master at some point, do all of > the release bugfixes, and when it is solid enough to pass a release > vote we branch a release from it, and then only allow merges to master > that have been tested in a merge

Re: CentOS 7 KVM Agent installation fails

The changes came in from the commit 555c4329462ac632890c7cde3bac8db8b6e8a682 and were reverted by 16806b19a04f8a8df1b8d106e9757395e47ee710 The revert only reverted in management package and not in agent or usage package. ~Rajani On Wed, Apr 22, 2015 at 1:41 AM, Remi Bergsma wrote: > Hi Wido, >

Jenkins build is still unstable: simulator-singlerun #1137

See

[GitHub] cloudstack pull request: CLOUDSTACK-8308-Adding-automation-test-ca...

Github user gauravaradhye commented on a diff in the pull request: https://github.com/apache/cloudstack/pull/181#discussion_r28939755 --- Diff: test/integration/testpaths/testpath_volume_cuncurrent_snapshots.py --- @@ -0,0 +1,827 @@ +# Licensed to the Apache Software Foundation

[GitHub] cloudstack pull request: CLOUDSTACK-8308-Adding-automation-test-ca...

Github user gauravaradhye commented on a diff in the pull request: https://github.com/apache/cloudstack/pull/181#discussion_r28939823 --- Diff: test/integration/testpaths/testpath_volume_cuncurrent_snapshots.py --- @@ -0,0 +1,827 @@ +# Licensed to the Apache Software Foundation

[GitHub] cloudstack pull request: CLOUDSTACK-8308-Adding-automation-test-ca...

Github user gauravaradhye commented on a diff in the pull request: https://github.com/apache/cloudstack/pull/181#discussion_r28940101 --- Diff: test/integration/testpaths/testpath_volume_cuncurrent_snapshots.py --- @@ -0,0 +1,827 @@ +# Licensed to the Apache Software Foundation

[GitHub] cloudstack pull request: CLOUDSTACK-8308-Adding-automation-test-ca...

Github user gauravaradhye commented on a diff in the pull request: https://github.com/apache/cloudstack/pull/181#discussion_r28940210 --- Diff: test/integration/testpaths/testpath_volume_cuncurrent_snapshots.py --- @@ -0,0 +1,827 @@ +# Licensed to the Apache Software Foundation

[GitHub] cloudstack pull request: CLOUDSTACK-8308-Adding-automation-test-ca...

Github user gauravaradhye commented on a diff in the pull request: https://github.com/apache/cloudstack/pull/181#discussion_r28940257 --- Diff: test/integration/testpaths/testpath_volume_cuncurrent_snapshots.py --- @@ -0,0 +1,827 @@ +# Licensed to the Apache Software Foundation