Re: [DISCUSS] 4.6 release management

[Sebastien Goasguen]

> On Apr 18, 2015, at 8:36 AM, Marcus  wrote:
> 
> Have they diverged that much? Due to cherry-picking, I guess.
> Otherwise you should be able to do it cleanly.
> 
> There's a good opportunity to do this next release. Instead of
> creating a release branch, we freeze master and start creating dev
> branches.

+1 

This just amounts to treating master now like a release branch. Getting back to 
PL suggestion, that means
that any commit to master would be through a PR or MERGE request on the ML. 
Anything else will be reverted by the RM.

Marcus, do you feel like writing down a little process for this and some dates 
that we can target.
It would be nice to do this for 4.6.

> 
> On Fri, Apr 17, 2015 at 10:46 PM, Daan Hoogland  
> wrote:
>> We heavily invested in code now on master. Not looking forward to
>> backporting that.
>> 
>> mobile dev with bilingual spelling checker used (read at your own risk)
>> Op 17 apr. 2015 21:02 schreef "Marcus" :
>> 
>>> Well, would we just swap the last release branch with master? Master
>>> is the dev branch, and the last release is really what we have as a
>>> stable branch.
>>> 
>>> On Fri, Apr 17, 2015 at 8:44 AM, Daan Hoogland 
>>> wrote:
 On Fri, Apr 17, 2015 at 2:43 AM, Sebastien Goasguen 
>>> wrote:
> 
>> On Apr 17, 2015, at 12:49 AM, Pierre-Luc Dion 
>>> wrote:
>> 
>> Today during the CloudStackdays  we did a round table about Release
>> management targeting the next 4.6 releases.
>> 
>> 
>> Quick bullet point discussions:
>> 
>> ideas to change release planning
>> 
>>  - Plugin contribution is complicated because often  a new plugin
>>> involve
>>  change on the core:
>> - ex: storage plugin involve changes on Hypervisor code
>>  - There is an idea of going on a 2 weeks release model which could
>>  introduce issue the database schema.
>>  - Database schema version should be different then the application
>>  version.
>>  - There is a will to enforce git workflow in 4.6  and trigger
>>> simulator
>>  job on  PullRequest.
>>  - Some people (I'm part of them) are concerned on our current way of
>>  supporting and back porting fixes to multiple release (4.3.x, 4.4.x,
>>  4.5.x). But the current level of confidence against latest release
>>> is low,
>>  so that need to be improved.
>> 
>> 
>> So, the main messages is that w'd like to improve the release
>>> velocity, and
>> release branch stability.  so we would like to propose few change in
>>> the
>> way we would add code to the 4.6 branch as follow:
>> 
>> - All new contribution to 4.6 would be thru Pull Request or merge
>>> request,
>> which would trigger a simulator job, ideally only if that pass the PR
>>> would
>> be accepted and automatically merged.  At this time, I think we pretty
>>> much
>> have everything in place to do that. At a first step we would use
>> simulator+marvin jobs then improve tests coverage from there.
> 
> +1
> 
> We do need to realize what this means and be all fine with it.
> 
> It means that if someone who is not RM directly commits to the release
>>> branch, the commit will be reverted.
> And that from the beginning of the branching…
 I agree and we can even go as far as reverting fixes that are
 cherry-picked in favour of merged forward.
 
> 
> IMHO, I think this would be a good step but I don’t think it goes far
>>> enough.
 Agreed here as well but let's take the step while discussing further
 steps and not implement to much process as well
 
> 
> This still uses a paradigm where a release is made from a release
>>> branch that was started from an unstable development branch.
> Hence you still need *extensive* QA.
 The problem here is that there is no stable point to fork from at the
 moment. We will get there and we shouldn't stop taking steps in that
 direction.
 
> 
> If we truly want to release faster, we need to release from the same
>>> QA’d branch time after time….a release needs to be based on a previous
>>> release
> 
> Basically, we need a rolling release cycle. That will have the added
>>> benefit to not leave releases behind and have to focus on backporting.
> 
>> 
>> Please comments :-)
> 
 
 
 
 --
 Daan
>>> 

[UPDATE] IP clearance for ec2stack and gstack

[Sebastien Goasguen]

Folks,

The IP clearance forms for ec2stack and gstack have been received by the ASF 
secretary.
I started filling the rest of the paperwork.
Once that’s done there will be a vote on the incubator list and when it passes 
we will be able to move the code over.

Couple more weeks I think,

-sebastien

[GitHub] cloudstack pull request: RFC: improve iptables persistent on VR

[resmo]

Github user resmo closed the pull request at:

https://github.com/apache/cloudstack/pull/178


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

CloudStack git clone - SSL certificate problem

[Praveen B]

Hi,

I'm getting following error while cloning CloudStack repo. Has anything
changed at repo side? Can someone assist me how to fix this issue?

Error:
$ git clone https://git-wip-us.apache.org/repos/asf/cloudstack.git
Cloning into 'cloudstack'...
fatal: unable to access '
https://git-wip-us.apache.org/repos/asf/cloudstack.git/': SSL certificate
problem: unable to get local issuer certificate


Thanks,
Praveen

Download volume - where is the image stored ?

[Andrija Panic]

Hi,

when I get the link from ACS to download the volume, where is this volume
located temporary - I tried finding the file by name on both secondary
storage, on SSVM, etc - but I cant file the file.

Example:
http://46.232.xxx.yyy/userdata/1a0c555a-15d5-43fc-bb4e-d7e689f192cb.raw

Original volume is located on CEPH - I see some time before geting link,
suspecting the CEPH volume is geting copied over - somewhere as the .raw
image...

Thanks for the info in advanced !
-- 

Andrija Panić

Re: Download volume - where is the image stored ?

[Andrija Panic]

Nevermind, found it:

root@SSVM: ls -la /var/ww/html/userdata/someLINK -->
/mnt/SecStorage//volumes/xxx/yyy/othername.raw

So basicaly the 1a0c555a-15d5-43fc-bb4e-d7e689f192cb.raw
 is
just a symlink to the differenet filename of the actual file on the
Secondary Storage

cheers

On 18 April 2015 at 15:51, Andrija Panic  wrote:

> Hi,
>
> when I get the link from ACS to download the volume, where is this volume
> located temporary - I tried finding the file by name on both secondary
> storage, on SSVM, etc - but I cant file the file.
>
> Example:
> http://46.232.xxx.yyy/userdata/1a0c555a-15d5-43fc-bb4e-d7e689f192cb.raw
>
> Original volume is located on CEPH - I see some time before geting link,
> suspecting the CEPH volume is geting copied over - somewhere as the .raw
> image...
>
> Thanks for the info in advanced !
> --
>
> Andrija Panić
>



-- 

Andrija Panić

[GitHub] cloudstack pull request: CLOUDSTACK-8335: removed libvirt.org repo...

[K0zka]

GitHub user K0zka opened a pull request:

https://github.com/apache/cloudstack/pull/180

CLOUDSTACK-8335: removed libvirt.org repository

The only artifact resolved from libvirt.org was org.libvirt:libvirt:0.5.1
this artifact is now available from maven's default central repository

Signed-off-by: Laszlo Hornyak 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/K0zka/cloudstack libvirt_rem_master2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/180.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #180


commit e999fe7539b0583ef538827ffd1e44cad017dbf7
Author: Laszlo Hornyak 
Date:   2015-04-18T20:22:59Z

CLOUDSTACK-8335: removed libvirt.org repository

The only artifact resolved from libvirt.org was org.libvirt:libvirt:0.5.1
this artifact is now available from maven's default central repository

Signed-off-by: Laszlo Hornyak 




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: CLOUDSTACK-8304: disable snapshots from n...

[K0zka]

Github user K0zka closed the pull request at:

https://github.com/apache/cloudstack/pull/172


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [VOTE] Apache Cloudstack 4.4.3

[Nux!]

Forgot to mention my +1 is binding.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Nux!" 
> To: dev@cloudstack.apache.org
> Sent: Thursday, 16 April, 2015 21:09:55
> Subject: Re: [VOTE] Apache Cloudstack 4.4.3

> No, that's ok, though we definitely need to fix it in the next one.
> 
> +1 from me, the product seems functional from the testing I did on
> CentOS6/KVM/Adv+SG
> 
> Lucian
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
>> From: "Daan Hoogland" 
>> To: "dev" 
>> Sent: Thursday, 16 April, 2015 17:52:29
>> Subject: Re: [VOTE] Apache Cloudstack 4.4.3
> 
>> sorry guys, for ignoring you all about this all day so far. Do we
>> thinks this warrants yet another RC? (implied no from me, is real)
>> 
>> On Thu, Apr 16, 2015 at 7:37 AM, Ian Southam
>>  wrote:
>>> Change ceph.com to eu.ceph.com in ./plugins/hypervisors/kvm/pom.xml then it 
>>> will
>>> compile again.
>>>
>>> —
>>> Grts!
>>> Ian
>>>
>>> On 16 Apr 2015, at 10:37, Nux!  wrote:
>>>
 Looks like there is a pom here
 http://repo1.maven.org/maven2/com/github/K0zka/libvirt/0.5.1/

 What file needs to be modified to point the build process there?

 --
 Sent from the Delta quadrant using Borg technology!

 Nux!
 www.nux.ro

 - Original Message -
> From: "Nux!" 
> To: dev@cloudstack.apache.org
> Sent: Thursday, 16 April, 2015 09:30:24
> Subject: Re: [VOTE] Apache Cloudstack 4.4.3

> Ok, I can't even build it, it stops at:
>
> [INFO] 
> 
> [INFO] Building Apache CloudStack Plugin - Hypervisor KVM 4.4.3
> [INFO] 
> 
> Downloading:
> http://libvirt.org/maven2/org/libvirt/libvirt/0.5.1/libvirt-0.5.1.pom
> Downloading: 
> http://ceph.com/maven/org/libvirt/libvirt/0.5.1/libvirt-0.5.1.pom
>
>
> Apparently those URLs do not work.
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
>> From: "Nux!" 
>> To: dev@cloudstack.apache.org
>> Sent: Thursday, 16 April, 2015 09:00:50
>> Subject: Re: [VOTE] Apache Cloudstack 4.4.3
>
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.4/ does not exist.
>>
>> I guess the valid one is either
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.4.3/ OR simply
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=snapshot;h=e9441d47867104505ef260c1857549f93df96aba;sf=tgz
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> - Original Message -
>>> From: "Daan Hoogland" 
>>> To: "dev" 
>>> Sent: Wednesday, 15 April, 2015 23:02:55
>>> Subject: [VOTE] Apache Cloudstack 4.4.3
>>
>>> Hi All,
>>>
>>> I've created a 4.4.3 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.4
>>> Commit: e9441d47867104505ef260c1857549f93df96aba
>>>
>>> List of changes:
>>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.4
>>> https://issues.apache.org/jira/issues/?filter=12330007
>>>
>>> Source release (checksums and signatures are available at the same
>>> location):
>>> https://dist.apache.org/repos/dist/dev/cloudstack/4.4/
>>>
>>> PGP release keys (signed using 2048D/5AABEBEA):
>>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>>
>>> Vote will be open for 72 hours.
>>>
>>> For sanity in tallying the vote, can PMC members please be sure to
>>> indicate "(binding)" with their vote?
>>>
>>> [ ] +1  approve
>>> [ ] +0  no opinion
>>> [ ] -1  disapprove (and reason why)
>>>
>>> --
>>> Daan
>>>
>> 
>> 
>> 
>> --
> > Daan

simulator failing runs in j.b.a.c.o

[Srikanteswararao Talluri]

Simulator jobs have been failing for a while due to incompatible/missing python 
nose plugins. I fixed the jenkins slave and the jobs to update the marvin for 
each build.
http://jenkins.buildacloud.org/view/simulator/job/simulator-singlerun/

Thanks,
~Talluri

Build failed in Jenkins: simulator-singlerun #1127

[jenkins]

See 

--
[...truncated 10943 lines...]
from marvin.lib.common import *
  File 
"
 line 91, in 
from marvin.lib.vcenter import Vcenter
  File 
"
 line 22, in 
ssl._create_default_https_context = ssl._create_unverified_context
AttributeError: 'module' object has no attribute '_create_unverified_context'
/usr/local/lib/python2.7/site-packages/Crypto/Util/number.py:57: 
PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp 
>= 5 to avoid timing attack vulnerability.
  _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid 
timing attack vulnerability.", PowmInsecureWarning)
Traceback (most recent call last):
  File 
"
 line 23, in 
from marvin.lib.common import *
  File 
"
 line 91, in 
from marvin.lib.vcenter import Vcenter
  File 
"
 line 22, in 
ssl._create_default_https_context = ssl._create_unverified_context
AttributeError: 'module' object has no attribute '_create_unverified_context'
/usr/local/lib/python2.7/site-packages/Crypto/Util/number.py:57: 
PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp 
>= 5 to avoid timing attack vulnerability.
  _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid 
timing attack vulnerability.", PowmInsecureWarning)
Traceback (most recent call last):
  File 
"
 line 25, in 
from marvin.lib.common import *
  File 
"
 line 91, in 
from marvin.lib.vcenter import Vcenter
  File 
"
 line 22, in 
ssl._create_default_https_context = ssl._create_unverified_context
AttributeError: 'module' object has no attribute '_create_unverified_context'
/usr/local/lib/python2.7/site-packages/Crypto/Util/number.py:57: 
PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp 
>= 5 to avoid timing attack vulnerability.
  _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid 
timing attack vulnerability.", PowmInsecureWarning)
Traceback (most recent call last):
  File 
"
 line 24, in 
from marvin.lib.common import *
  File 
"
 line 91, in 
from marvin.lib.vcenter import Vcenter
  File 
"
 line 22, in 
ssl._create_default_https_context = ssl._create_unverified_context
AttributeError: 'module' object has no attribute '_create_unverified_context'
/usr/local/lib/python2.7/site-packages/Crypto/Util/number.py:57: 
PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp 
>= 5 to avoid timing attack vulnerability.
  _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid 
timing attack vulnerability.", PowmInsecureWarning)
Traceback (most recent call last):
  File 
"
 line 26, in 
from marvin.lib.common import *
  File 
"
 line 91, in 
from marvin.lib.vcenter import Vcenter
  File 
"
 line 22, in 
ssl._create_default_https_context = ssl._create_unverified_context
AttributeError: 'module' object has no attribute '_create_unverified_context'
/usr/local/lib/python2.7/site-packages/Crypto/Util/number.py:57: 
PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp 
>= 5 to avoid timing attack vulnerability.
  _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >= 5 to avoid 
timing attack vulnerability.", PowmInsecureWarning)
Traceback (most recent call last):
  File 
"
 line 26, in 
from marvin.lib.common import *
  File 
"