RE: question about Admin's capability to create a VM on a disabled host

[Raja Pullela]

Yes... that makes sense.  Thanks Praveen!  

-Original Message-
From: Praveen B [mailto:pbprave...@gmail.com] 
Sent: Monday, June 22, 2015 11:13 PM
To: dev@cloudstack.apache.org
Subject: Re: question about Admin's capability to create a VM on a disabled host

Hi Raja,

I can think of this use case -->  An admin can verify if a host is production 
ready by deploying a resource first on it before actual users deploy and fail 
due to any specific reasons.

Thanks,
Praveen Kumar,
Founder,PSI Cloud Solutions,
psiclouds.com.

On Mon, Jun 22, 2015 at 12:14 PM, Raja Pullela 
wrote:

> Hi,
>
> This is regarding a question about Admin user's ability to create a VM 
> on a disabled host...  does anyone know the purpose/use?  can I 
> understand it will help in troubleshooting.
>
> Thanks,
> Raja
>

[GitHub] cloudstack pull request: CLOUDSTACK-8574: Skip testcases for LXC i...

[pritisarap12]

Github user pritisarap12 commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/488#discussion_r33011867
  
--- Diff: test/integration/component/test_stopped_vm.py ---
@@ -53,6 +54,13 @@ def setUpClass(cls):
 cls.domain = get_domain(cls.api_client)
 cls.zone = get_zone(cls.api_client, 
cls.testClient.getZoneForTests())
 
+cls.hypervisor = cls.testClient.getHypervisorInfo()
+
+if cls.hypervisor.lower() == 'lxc':
+if not find_storage_pool_type(cls.apiclient, 
storagetype='rbd'):
+raise unittest.SkipTest("RBD storage type is required for 
data volumes for LXC")
--- End diff --

Done with the review changes.


---
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.
---

Build failed in Jenkins: build-systemvm-master #540

[jenkins]

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on coohq-slave-01 (cloudstack-buildslave-centos6 
systemvmbuilder) in workspace 

 > /usr/bin/git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
 > /usr/bin/git --version # timeout=10
 > /usr/bin/git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git 
 > +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:735)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:983)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1016)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1258)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
at hudson.model.Run.execute(Run.java:1759)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git -c 
core.askpass=true fetch --tags --progress 
https://git-wip-us.apache.org/repos/asf/cloudstack.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: fatal: unable to access 
'https://git-wip-us.apache.org/repos/asf/cloudstack.git/': gnutls_handshake() 
failed: A TLS packet with unexpected length was received.

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1591)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:86)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:324)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:324)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to coohq-slave-01(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
at hudson.remoting.Channel.call(Channel.java:752)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor375.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at sun.proxy.$Proxy46.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:733)
... 11 more
ERROR: Error fetching remote repo 'origin'
Archiving artifacts
Publish artifacts to S3 Bucket Using S3 profile: CloudStack S3 Buckets
Publish artifacts to S3 Bucket 
bucket=systemvm-templates.cloudstack.org/master/32, file=md5sum.txt 
region=US_EAST_1, upload from slave=false managed=false
Publish artifacts to S3 Bucket 
bucket=systemvm-templates.cloudstack.org/master/32, 
file=systemvmtemplate-master-4.6.0-hyperv.vhd.zip region=US_EAST_1, upload from 
slave=false managed=false
Publish artifacts to S3 Bucket 
bucket=systemvm-templates.cloudstack.org/master/32, 
file=systemvmtemplate-master-4.6.0-kvm.qcow2.bz2 region=US_EAST_1, upload from 

Re: question about Admin's capability to create a VM on a disabled host

[Praveen B]

Hi Raja,

I can think of this use case -->  An admin can verify if a host is
production ready by deploying a resource first on it before actual users
deploy and fail due to any specific reasons.

Thanks,
Praveen Kumar,
Founder,PSI Cloud Solutions,
psiclouds.com.

On Mon, Jun 22, 2015 at 12:14 PM, Raja Pullela 
wrote:

> Hi,
>
> This is regarding a question about Admin user's ability to create a VM on
> a disabled host...  does anyone know the purpose/use?  can I understand it
> will help in troubleshooting.
>
> Thanks,
> Raja
>

[GitHub] cloudstack pull request: [WIP] CLOUDSTACK-6276: affinitygroup: imp...

[resmo]

Github user resmo closed the pull request at:

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


---
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: [WIP] CLOUDSTACK-6276: affinitygroup: imp...

[resmo]

Github user resmo commented on the pull request:

https://github.com/apache/cloudstack/pull/264#issuecomment-114142748
  
closing this in favour of re-based and updated PR #508 


---
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: [WIP] CLOUDSTACK-6276: project support in...

[resmo]

GitHub user resmo opened a pull request:

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

[WIP] CLOUDSTACK-6276: project support in affinitygroups



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

$ git pull https://github.com/resmo/cloudstack 
feature/6276-project-affinitygroup

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

https://github.com/apache/cloudstack/pull/508.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 #508


commit 2e129b3ef7b55fc79584305d667b59ae839c2ff2
Author: Rene Moser 
Date:   2015-06-22T14:46:33Z

CLOUDSTACK-6276: add project support to AffinityGroupJoinVO and API

commit c6b91fef14739ab4373e1637d74847180d0d1e0f
Author: Rene Moser 
Date:   2015-06-22T14:49:16Z

CLOUDSTACK-6276: implement searchForAffinityGroups in QueryService

commit 45a88be1d4f0c2b59e81c5e904679dab388ad88f
Author: Rene Moser 
Date:   2015-06-22T14:53:24Z

CLOUDSTACK-6276: use query service for listAffinityGroups

commit 7b322969ab47d943931eda876d54418980adf817
Author: Rene Moser 
Date:   2015-06-22T14:55:41Z

CLOUDSTACK-6276: add project support in AffinityGroupService in create and 
delete




---
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] release candidate 4.4.4 (4.4-RC20150618T1117)

[Daan Hoogland]

tested specifically the blocker issue in a two host cluster with an
isolated network.

both the option values false and true gave expected result on setting
router.reboot.when.outofband.migrated

based on this behavior and the fact that setup worked smoothly

+1 (binding)

one point of attention is that a remark on this option should go in
the release notes.

On Sat, Jun 20, 2015 at 8:49 PM, Milamber  wrote:
> Hello,
>
> +1 (binding)
>
> Tests on Ubuntu 14.04.2 (1 mgr, 2 nodes, 1 nfs), advanced network fresh
> install, NFS storage, KVM, some tests on HA (crash vm/restore), SystemVM
> shape, some tests with templates, and CS<->cloud-init on debian.
>
> Tests on Ubuntu 14.04.2 (All-in-one ansible installation[1]), advanced
> network fresh installation
>
> Thanks for the RM.
>
> Milamber
>
> [1] https://github.com/milamberspace/ansible-cloudstack-ubuntu-aio
>
>
>
> On 18/06/2015 09:24, Daan Hoogland wrote:
>>
>> Hi All,
>>
>> I've created a 4.4.4 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-RC20150618T1117
>> Commit: 6f41061e1428527c3f826d268377557ce607196b
>>
>> List of changes:
>>
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/tags/4.4.4
>>
>> Source release (checksums and signatures are available at the same
>> location):
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.4.4/
>>
>> PGP release keys (signed using 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

Re: 4.6

[sebgoa]

On Jun 22, 2015, at 2:55 PM, Rafael Fonseca  wrote:

> Hi Sebastien, thx for following up so quickly :)
> 
> It's because it's a big change that i think it should be done in a major
> release an not a minor,

We all agree on this. Such as change is for a major release.

The question is 4.6 or 4.7 ...


> nevertheless it will be up to the community to
> decide if we should ship it in 4.6.0 of wait for a long time to have this
> in.
> 
> I've been waiting a long time for that larger discussion, the currently
> open PR is already the second proposal to improve packaging and the
> previous one was open for over a month.. so i wonder how long it will take
> to let everyone take advantage of it, since the code is all ready to
> ship... if anyone can see a reason or a fix that might not be what they
> want, i can just amend whatever quickly... but other than the mysql issue,
> i don't know what would conflict with anyone's interest.. though feel free
> to show me otherwise :)
> 
> Like i said on the PR, this is still not all the changes i'd like to make
> to get a cleaner packaging config, but whatever aesthetical or maintainer
> helpfulness is still needed to be done, can be done later along the path,
> while providing the functionality earlier to everyone. Even if we
> eventually decide to go for a completely different packaging structure like
> using a proper makefile or something like that, most of the cleanup done in
> this PR will just make that switch easier ;)
> 
> For me it will just be a few hours of work to chop it all into pieces and
> explain what each bit does, so just let me know if i should focus on this
> straight away or leave it for later and focus on some more needed fixes not
> related to packaging that everyone should agree to get into releases ASAP.
> 

We need to start testing master (a.k.a) 4.6 , identify blockers through testing 
and see what needs to get fixed.
I have not had the time to check JIRA, to see if it's already with a 4.6 
release and if we already have 4.6 blockers.


> Looking forward for Pyr's input on this :)
> 

Since he is the one who mentioned this feature, I am hoping he can comment soon 
on it.

-sebastien

> 
> On Mon, Jun 22, 2015 at 2:28 PM, sebgoa  wrote:
> 
>> 
>> On Jun 22, 2015, at 2:21 PM, Rafael Fonseca  wrote:
>> 
>>> Hi guys,
>>> 
>>> I plan on getting started on dissecting the embedded Tomcat/Jetty PR this
>>> week, it would be nice to get it into 4.6.0, since it's quite a change in
>>> functional packaging to do it in a minor like 4.6.1 (documentation wise
>> and
>>> stuff), and i guess 4.7.0 is still far down the road.
>> 
>> Rafael, let me copy Pierre-Yves who talked about this new packaging.
>> 
>> I don't think we should try to put it in 4.6.0, it's too big of change,
>> and should really be part of a larger discussion on
>> re-packaging/re-architecture of several things.
>> 
>> Hopefully Pyr can chime in.
>> 
>> -sebastien
>> 
>>> Want to hold off on 4.6.0 until that is chopped to pieces and made easy
>> to
>>> review? Should be able to do it in a couple of days.
>>> I will also remove the mysql bit for now so there are no conflicting
>>> opinions, will revisit that issue further down the road.. as someone very
>>> well versed in Apache licensing explained to me (thanks Leo), we can get
>>> that done, just not by default and provide a switch to include that
>>> functionality so that third party rpm/deb distributors (non-Apache) can
>> use
>>> that. This will also require some classpath changes based on that switch,
>>> so will think about it later.
>>> Everyone in agreement with this? I'm sure quite a few people have been
>>> waiting on it for sometime, so would be nice to include in this release
>> imo
>>> :)
>>> 
>>> Cheers,
>>> Rafael
>>> 
>>> On Fri, Jun 12, 2015 at 2:10 PM, Funs Kessen  wrote:
>>> 
 Hi Seb,
 
 Great way of wording it, and I completely agree! You should be able to
 pick up master and roll it out into production and keep running with it!
 
 Cheers,
 
 Funs
 
> On 11 Jun 2015, at 23:43, Sebastien Goasguen  wrote:
> 
> 
>> On Jun 11, 2015, at 6:43 PM, John Burwell >> 
 wrote:
>> 
>> All,
>> 
>> Why are we averse to cutting a release stabilization branch?  In the
 past, we have cut release stabilization branches to ensure that the flow
 contributions was not interrupted.
> 
> I disagree.
> 
> We have cut branches that way because that’s how Citrix delivers
 software. It develops on master, cuts a branch and put a QA team to
>> work to
 stabilize and make a release.
> 
> I believe it’s a broken model for an open source community made of
 mostly volunteers. We don’t have the luxury to QA a release branch and
 loose that effort (because it does not go back to master).
> 
> In addition, this process has led to many regression, because there
 is/was a disconnect between the Qa team and the guys developing o

[GitHub] cloudstack pull request: CLOUDSTACK-8577: fixing script testpath_d...

[nitt10prashant]

GitHub user nitt10prashant opened a pull request:

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

CLOUDSTACK-8577: fixing script  testpath_disable_enable_zone

disable enable cluster ... === TestName: test_01_disable_enable_cluster | 
Status : SUCCESS ===
ok
disable enable host ... === TestName: test_01_disable_enable_host | Status 
: SUCCESS ===
ok
disable enable Pod ... === TestName: test_01_disable_enable_pod | Status : 
SUCCESS ===
ok
disable enable zone ... === TestName: test_01_disable_enable_zone | Status 
: SUCCESS ===
ok

--
Ran 4 tests in 2818.119s

OK

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

$ git pull https://github.com/nitt10prashant/cloudstack enable_zone

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

https://github.com/apache/cloudstack/pull/507.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 #507


commit 4554ae7eb793ad1a519e5b96d938f380218a18fa
Author: nitt10prashant 
Date:   2015-06-22T12:55:39Z

CLOUDSTACK-8577: fixing script  testpath_disable_enable_zone




---
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: 4.6

[Rafael Fonseca]

Hi Sebastien, thx for following up so quickly :)

It's because it's a big change that i think it should be done in a major
release an not a minor, nevertheless it will be up to the community to
decide if we should ship it in 4.6.0 of wait for a long time to have this
in.

I've been waiting a long time for that larger discussion, the currently
open PR is already the second proposal to improve packaging and the
previous one was open for over a month.. so i wonder how long it will take
to let everyone take advantage of it, since the code is all ready to
ship... if anyone can see a reason or a fix that might not be what they
want, i can just amend whatever quickly... but other than the mysql issue,
i don't know what would conflict with anyone's interest.. though feel free
to show me otherwise :)

Like i said on the PR, this is still not all the changes i'd like to make
to get a cleaner packaging config, but whatever aesthetical or maintainer
helpfulness is still needed to be done, can be done later along the path,
while providing the functionality earlier to everyone. Even if we
eventually decide to go for a completely different packaging structure like
using a proper makefile or something like that, most of the cleanup done in
this PR will just make that switch easier ;)

For me it will just be a few hours of work to chop it all into pieces and
explain what each bit does, so just let me know if i should focus on this
straight away or leave it for later and focus on some more needed fixes not
related to packaging that everyone should agree to get into releases ASAP.

Looking forward for Pyr's input on this :)


On Mon, Jun 22, 2015 at 2:28 PM, sebgoa  wrote:

>
> On Jun 22, 2015, at 2:21 PM, Rafael Fonseca  wrote:
>
> > Hi guys,
> >
> > I plan on getting started on dissecting the embedded Tomcat/Jetty PR this
> > week, it would be nice to get it into 4.6.0, since it's quite a change in
> > functional packaging to do it in a minor like 4.6.1 (documentation wise
> and
> > stuff), and i guess 4.7.0 is still far down the road.
>
> Rafael, let me copy Pierre-Yves who talked about this new packaging.
>
> I don't think we should try to put it in 4.6.0, it's too big of change,
> and should really be part of a larger discussion on
> re-packaging/re-architecture of several things.
>
> Hopefully Pyr can chime in.
>
> -sebastien
>
> > Want to hold off on 4.6.0 until that is chopped to pieces and made easy
> to
> > review? Should be able to do it in a couple of days.
> > I will also remove the mysql bit for now so there are no conflicting
> > opinions, will revisit that issue further down the road.. as someone very
> > well versed in Apache licensing explained to me (thanks Leo), we can get
> > that done, just not by default and provide a switch to include that
> > functionality so that third party rpm/deb distributors (non-Apache) can
> use
> > that. This will also require some classpath changes based on that switch,
> > so will think about it later.
> > Everyone in agreement with this? I'm sure quite a few people have been
> > waiting on it for sometime, so would be nice to include in this release
> imo
> > :)
> >
> > Cheers,
> > Rafael
> >
> > On Fri, Jun 12, 2015 at 2:10 PM, Funs Kessen  wrote:
> >
> >> Hi Seb,
> >>
> >> Great way of wording it, and I completely agree! You should be able to
> >> pick up master and roll it out into production and keep running with it!
> >>
> >> Cheers,
> >>
> >> Funs
> >>
> >>> On 11 Jun 2015, at 23:43, Sebastien Goasguen  wrote:
> >>>
> >>>
>  On Jun 11, 2015, at 6:43 PM, John Burwell  >
> >> wrote:
> 
>  All,
> 
>  Why are we averse to cutting a release stabilization branch?  In the
> >> past, we have cut release stabilization branches to ensure that the flow
> >> contributions was not interrupted.
> >>>
> >>> I disagree.
> >>>
> >>> We have cut branches that way because that’s how Citrix delivers
> >> software. It develops on master, cuts a branch and put a QA team to
> work to
> >> stabilize and make a release.
> >>>
> >>> I believe it’s a broken model for an open source community made of
> >> mostly volunteers. We don’t have the luxury to QA a release branch and
> >> loose that effort (because it does not go back to master).
> >>>
> >>> In addition, this process has led to many regression, because there
> >> is/was a disconnect between the Qa team and the guys developing on
> master.
> >> Plus bad practice when bugs gets fixed. i.e we fix a bug in a release
> >> branch but don’t port it in master.
> >>>
> >>> That’s why we have talked about this at length for almost a year now,
> >> alas without resolution ( I thought we had, but your email indicates
> >> otherwise, too bad you did not chime in earlier).
> >>>
> >>> I am advocating for us to stabilize master and gate master. So that
> >> whenever we release we can do it starting from a stabilized branch.
> Instead
> >> of having to reinvest time in lengthy QA.
> >>>
> >>> I want us to be able to release at anyti

Re: [GitHub] cloudstack pull request: CLOUDSTACK-8576: Skip tests for LXC

[Sanjeev N]

Please ignore my comment. I confirmed with Kishan and he said template
creation from volume is not supported in LXC.

On Mon, Jun 22, 2015 at 5:45 PM, sanju1010  wrote:

> Github user sanju1010 commented on a diff in the pull request:
>
> https://github.com/apache/cloudstack/pull/506#discussion_r32927724
>
> --- Diff: test/integration/component/test_resource_limits.py ---
> @@ -748,6 +748,8 @@ def test_05_templates_per_account(self):
>  #should be denied to create more than 1 template.
>  # 3. Try to create 2 templates in account 2. Verify account 2
> should be
>  #able to create template without any error
> +if self.hypervisor.lower() in ['lxc']:
> --- End diff --
>
> I think template creation from volume is supported in lxc.
>
>
> ---
> 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: 4.6

[sebgoa]

On Jun 22, 2015, at 2:21 PM, Rafael Fonseca  wrote:

> Hi guys,
> 
> I plan on getting started on dissecting the embedded Tomcat/Jetty PR this
> week, it would be nice to get it into 4.6.0, since it's quite a change in
> functional packaging to do it in a minor like 4.6.1 (documentation wise and
> stuff), and i guess 4.7.0 is still far down the road.

Rafael, let me copy Pierre-Yves who talked about this new packaging.

I don't think we should try to put it in 4.6.0, it's too big of change, and 
should really be part of a larger discussion on re-packaging/re-architecture of 
several things.

Hopefully Pyr can chime in.

-sebastien

> Want to hold off on 4.6.0 until that is chopped to pieces and made easy to
> review? Should be able to do it in a couple of days.
> I will also remove the mysql bit for now so there are no conflicting
> opinions, will revisit that issue further down the road.. as someone very
> well versed in Apache licensing explained to me (thanks Leo), we can get
> that done, just not by default and provide a switch to include that
> functionality so that third party rpm/deb distributors (non-Apache) can use
> that. This will also require some classpath changes based on that switch,
> so will think about it later.
> Everyone in agreement with this? I'm sure quite a few people have been
> waiting on it for sometime, so would be nice to include in this release imo
> :)
> 
> Cheers,
> Rafael
> 
> On Fri, Jun 12, 2015 at 2:10 PM, Funs Kessen  wrote:
> 
>> Hi Seb,
>> 
>> Great way of wording it, and I completely agree! You should be able to
>> pick up master and roll it out into production and keep running with it!
>> 
>> Cheers,
>> 
>> Funs
>> 
>>> On 11 Jun 2015, at 23:43, Sebastien Goasguen  wrote:
>>> 
>>> 
 On Jun 11, 2015, at 6:43 PM, John Burwell 
>> wrote:
 
 All,
 
 Why are we averse to cutting a release stabilization branch?  In the
>> past, we have cut release stabilization branches to ensure that the flow
>> contributions was not interrupted.
>>> 
>>> I disagree.
>>> 
>>> We have cut branches that way because that’s how Citrix delivers
>> software. It develops on master, cuts a branch and put a QA team to work to
>> stabilize and make a release.
>>> 
>>> I believe it’s a broken model for an open source community made of
>> mostly volunteers. We don’t have the luxury to QA a release branch and
>> loose that effort (because it does not go back to master).
>>> 
>>> In addition, this process has led to many regression, because there
>> is/was a disconnect between the Qa team and the guys developing on master.
>> Plus bad practice when bugs gets fixed. i.e we fix a bug in a release
>> branch but don’t port it in master.
>>> 
>>> That’s why we have talked about this at length for almost a year now,
>> alas without resolution ( I thought we had, but your email indicates
>> otherwise, too bad you did not chime in earlier).
>>> 
>>> I am advocating for us to stabilize master and gate master. So that
>> whenever we release we can do it starting from a stabilized branch. Instead
>> of having to reinvest time in lengthy QA.
>>> 
>>> I want us to be able to release at anytime, when we feel like it and as
>> soon as someone says I want this fix/feature that was just merged in
>> master. Right no we cannot do that.
>>> 
>>> So yes call me crazy, I want the developers to take it onto themselves
>> to keep their forks in sync with master, develop on their fork. And I want
>> master to be the release branch. We will be able to build up a release
>> through PR from devs with limited merge conflicts. So that we reach a point
>> where master is QA at all time and we don’t loose any investment made in QA.
>>> 
>>> 
 For committers, it is not a big deal since they can manage their
>> branches in the cloudstack repo.  However, for non-committers, this freeze
>> could cause unnecessary frustration and discourage further contributions.
>>> 
>>> A freeze means only the RMs will commit on master. any PR from anyone
>> welcome and let the discussions happen on whether to merge or not…no
>> frustration.
>>> 
>>> 
 
 Thanks,
 -John
 
 
 From: sebgoa 
 Sent: Wednesday, June 10, 2015 6:33 AM
 To: dev@cloudstack.apache.org
 Subject: Re: 4.6
 
 On Jun 8, 2015, at 11:45 PM, Remi Bergsma  wrote:
 
> Hi,
> 
> I can jump in and work with Rohit and Daan to make 4.6 happen.
> 
> +1 for the QA on master. It would be best if we could then all focus
>> on stabilizing 4.6 aka master and wait with refactor stuff and new features
>> until 4.6 is out, which is the start of 4.7.
> 
> On the other hand, building new features in the mean time isn't a big
>> issue, as rebasing to a master that gets more stable every day is much
>> easier than it is today I'd say. You just cannot merge new stuff until 4.6
>> is out.
> 
> Let's write down some guidelines and see if this approach makes sense

Re: 4.6

[Rafael Fonseca]

Hi guys,

I plan on getting started on dissecting the embedded Tomcat/Jetty PR this
week, it would be nice to get it into 4.6.0, since it's quite a change in
functional packaging to do it in a minor like 4.6.1 (documentation wise and
stuff), and i guess 4.7.0 is still far down the road.
Want to hold off on 4.6.0 until that is chopped to pieces and made easy to
review? Should be able to do it in a couple of days.
I will also remove the mysql bit for now so there are no conflicting
opinions, will revisit that issue further down the road.. as someone very
well versed in Apache licensing explained to me (thanks Leo), we can get
that done, just not by default and provide a switch to include that
functionality so that third party rpm/deb distributors (non-Apache) can use
that. This will also require some classpath changes based on that switch,
so will think about it later.
Everyone in agreement with this? I'm sure quite a few people have been
waiting on it for sometime, so would be nice to include in this release imo
:)

Cheers,
Rafael

On Fri, Jun 12, 2015 at 2:10 PM, Funs Kessen  wrote:

> Hi Seb,
>
> Great way of wording it, and I completely agree! You should be able to
> pick up master and roll it out into production and keep running with it!
>
> Cheers,
>
> Funs
>
> > On 11 Jun 2015, at 23:43, Sebastien Goasguen  wrote:
> >
> >
> >> On Jun 11, 2015, at 6:43 PM, John Burwell 
> wrote:
> >>
> >> All,
> >>
> >> Why are we averse to cutting a release stabilization branch?  In the
> past, we have cut release stabilization branches to ensure that the flow
> contributions was not interrupted.
> >
> > I disagree.
> >
> > We have cut branches that way because that’s how Citrix delivers
> software. It develops on master, cuts a branch and put a QA team to work to
> stabilize and make a release.
> >
> > I believe it’s a broken model for an open source community made of
> mostly volunteers. We don’t have the luxury to QA a release branch and
> loose that effort (because it does not go back to master).
> >
> > In addition, this process has led to many regression, because there
> is/was a disconnect between the Qa team and the guys developing on master.
> Plus bad practice when bugs gets fixed. i.e we fix a bug in a release
> branch but don’t port it in master.
> >
> > That’s why we have talked about this at length for almost a year now,
> alas without resolution ( I thought we had, but your email indicates
> otherwise, too bad you did not chime in earlier).
> >
> > I am advocating for us to stabilize master and gate master. So that
> whenever we release we can do it starting from a stabilized branch. Instead
> of having to reinvest time in lengthy QA.
> >
> > I want us to be able to release at anytime, when we feel like it and as
> soon as someone says I want this fix/feature that was just merged in
> master. Right no we cannot do that.
> >
> > So yes call me crazy, I want the developers to take it onto themselves
> to keep their forks in sync with master, develop on their fork. And I want
> master to be the release branch. We will be able to build up a release
> through PR from devs with limited merge conflicts. So that we reach a point
> where master is QA at all time and we don’t loose any investment made in QA.
> >
> >
> >> For committers, it is not a big deal since they can manage their
> branches in the cloudstack repo.  However, for non-committers, this freeze
> could cause unnecessary frustration and discourage further contributions.
> >
> > A freeze means only the RMs will commit on master. any PR from anyone
> welcome and let the discussions happen on whether to merge or not…no
> frustration.
> >
> >
> >>
> >> Thanks,
> >> -John
> >>
> >> 
> >> From: sebgoa 
> >> Sent: Wednesday, June 10, 2015 6:33 AM
> >> To: dev@cloudstack.apache.org
> >> Subject: Re: 4.6
> >>
> >> On Jun 8, 2015, at 11:45 PM, Remi Bergsma  wrote:
> >>
> >>> Hi,
> >>>
> >>> I can jump in and work with Rohit and Daan to make 4.6 happen.
> >>>
> >>> +1 for the QA on master. It would be best if we could then all focus
> on stabilizing 4.6 aka master and wait with refactor stuff and new features
> until 4.6 is out, which is the start of 4.7.
> >>>
> >>> On the other hand, building new features in the mean time isn't a big
> issue, as rebasing to a master that gets more stable every day is much
> easier than it is today I'd say. You just cannot merge new stuff until 4.6
> is out.
> >>>
> >>> Let's write down some guidelines and see if this approach makes sense.
> >>>
> >>
> >> Maybe that's something that you can do at the meetup today and bring it
> back to the list as a proposal ?
> >>
> >> When I talk about freeze I am thinking just letting the RMs commit on
> master, everyone who wants something in 4.6 should submit a PR.
> >>
> >>
> >>
> >>> Regards, Remi
> >>>
>  On 08 Jun 2015, at 21:43, Sebastien Goasguen 
> wrote:
> 
>  Folks,
> 
>  We need to freeze 4.6 asap.
> 
>  I ori

[GitHub] cloudstack pull request: CLOUDSTACK-8576: Skip tests for LXC

[sanju1010]

Github user sanju1010 commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/506#discussion_r32927724
  
--- Diff: test/integration/component/test_resource_limits.py ---
@@ -748,6 +748,8 @@ def test_05_templates_per_account(self):
 #should be denied to create more than 1 template.
 # 3. Try to create 2 templates in account 2. Verify account 2 
should be
 #able to create template without any error
+if self.hypervisor.lower() in ['lxc']:
--- End diff --

I think template creation from volume is supported in lxc. 


---
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.
---

Build failed in Jenkins: simulator-singlerun #1295

[jenkins]

See 

--
Started by upstream project "build-master-simulator" build number 2112
originally caused by:
 Started by upstream project "build-master" build number 2416
 originally caused by:
  Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on simulator in workspace 

 > /usr/bin/git rev-parse --is-inside-work-tree # timeout=400
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git # timeout=400
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
 > /usr/bin/git --version # timeout=400
 > /usr/bin/git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git 
 > +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:735)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:983)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1016)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1258)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
at hudson.model.Run.execute(Run.java:1759)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags 
--progress https://git-wip-us.apache.org/repos/asf/cloudstack.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: error:  while accessing 
https://git-wip-us.apache.org/repos/asf/cloudstack.git/info/refs

fatal: HTTP request failed

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1591)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:86)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:324)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:324)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
at ..remote call to simulator(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
at hudson.remoting.Channel.call(Channel.java:752)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor375.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at sun.proxy.$Proxy46.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:733)
... 11 more
ERROR: Error fetching remote repo 'origin'
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - No test report file(s) were found with the pattern 
'xunit.xml' relative to 
' for the testing 
framework 'JUnit'.  Did you enter a pattern relative to the correct directory?  
Did you generate the result report(s) for 'JUnit'?
[xUnit] [ERROR] - No test reports found for the metric 'JUnit' with the 
resolved pattern 'xunit.xml'. Configuration error?.
[xUnit] [INFO] - Failing BUILD.
[xUnit] [INFO] - Th

Build failed in Jenkins: simulator-singlerun #1294

[jenkins]

See 

--
Started by upstream project "build-master-simulator" build number 2111
originally caused by:
 Started by an SCM change
 Started by an SCM change
 Started by upstream project "build-master" build number 2415
 originally caused by:
  Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on simulator in workspace 

 > /usr/bin/git rev-parse --is-inside-work-tree # timeout=400
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git # timeout=400
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
 > /usr/bin/git --version # timeout=400
 > /usr/bin/git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git 
 > +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:735)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:983)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1016)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1258)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
at hudson.model.Run.execute(Run.java:1759)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags 
--progress https://git-wip-us.apache.org/repos/asf/cloudstack.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: error:  while accessing 
https://git-wip-us.apache.org/repos/asf/cloudstack.git/info/refs

fatal: HTTP request failed

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1591)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:86)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:324)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:324)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
at ..remote call to simulator(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
at hudson.remoting.Channel.call(Channel.java:752)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor375.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at sun.proxy.$Proxy46.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:733)
... 11 more
ERROR: Error fetching remote repo 'origin'
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - No test report file(s) were found with the pattern 
'xunit.xml' relative to 
' for the testing 
framework 'JUnit'.  Did you enter a pattern relative to the correct directory?  
Did you generate the result report(s) for 'JUnit'?
[xUnit] [ERROR] - No test reports found for the metric 'JUnit' with the 
resolved pattern 'xunit.xml'. Configuration error?.

[GitHub] cloudstack pull request: CLOUDSTACK-8576: Skip tests for LXC

[pritisarap12]

GitHub user pritisarap12 opened a pull request:

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

 CLOUDSTACK-8576: Skip tests for LXC

Skipping testcases for LXC as it doesn't support snapshots and templates 
creation also excluded unittest as it was not used.

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

$ git pull https://github.com/pritisarap12/cloudstack resourceLimits

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

https://github.com/apache/cloudstack/pull/506.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 #506


commit 5c8922e640e7ebe5dedc378779ef465987606ef7
Author: pritisarap12 
Date:   2015-06-22T11:14:07Z

 CLOUDSTACK-8576: Skip tests as snapshots and template are not supported on 
LXC




---
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: Attempt to resolve ovm3 jenkins failure

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Attempt to resolve ovm3 jenkins failure

[rsafonseca]

Github user rsafonseca commented on the pull request:

https://github.com/apache/cloudstack/pull/497#issuecomment-114054951
  
@karuturi done in a nicer way, as requested :)
FYI, the only thing that is needed to actually fix the ovm3 problem is the 
changes to 
plugins/hypervisors/ovm3/src/test/java/com/cloud/hypervisor/ovm3/objects/XenTest.java

All the rest are just minor improvements made along the testing of the 
problem, but none are related to actually fixing it. The minor improvements i 
referred to are simply getting rid of some lint checker warnings about 
serializable classes not having the serialversionuid and doing redundant 
explicit casts. Also added a couple of non declared dependencies to the pom, 
and that's it :)


---
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: Attempt to resolve ovm3 jenkins failure

[rsafonseca]

Github user rsafonseca commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/497#discussion_r32917874
  
--- Diff: plugins/hypervisors/ovm3/pom.xml ---
@@ -27,11 +27,31 @@
 ../../pom.xml
   
   
-
-org.apache.xmlrpc
-xmlrpc-client
-3.1.3
-
+
+   xml-apis
+   xml-apis
+   1.4.01
+
+
+  org.apache.xmlrpc
+  xmlrpc-client
+  3.1.3
+
+
+   org.apache.xmlrpc
+   xmlrpc-common
+   3.1.3
+
+
+   org.apache.commons
+   commons-lang3
+   3.4
+
+
+   log4j
+   log4j
+   1.2.17
--- End diff --

We can, though this version is already pretty old and not likely to change, 
will update for consistency


---
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: Attempt to resolve ovm3 jenkins failure

[rsafonseca]

Github user rsafonseca commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/497#discussion_r32917814
  
--- Diff: plugins/hypervisors/ovm3/pom.xml ---
@@ -27,11 +27,31 @@
 ../../pom.xml
   
   
-
-org.apache.xmlrpc
-xmlrpc-client
-3.1.3
-
+
+   xml-apis
+   xml-apis
+   1.4.01
+
+
+  org.apache.xmlrpc
+  xmlrpc-client
+  3.1.3
+
+
+   org.apache.xmlrpc
+   xmlrpc-common
+   3.1.3
--- End diff --

Yes, will update


---
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: Attempt to resolve ovm3 jenkins failure

[rsafonseca]

Github user rsafonseca commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/497#discussion_r32917853
  
--- Diff: plugins/hypervisors/ovm3/pom.xml ---
@@ -27,11 +27,31 @@
 ../../pom.xml
   
   
-
-org.apache.xmlrpc
-xmlrpc-client
-3.1.3
-
+
+   xml-apis
+   xml-apis
+   1.4.01
+
+
+  org.apache.xmlrpc
+  xmlrpc-client
+  3.1.3
+
+
+   org.apache.xmlrpc
+   xmlrpc-common
+   3.1.3
+
+
+   org.apache.commons
+   commons-lang3
+   3.4
--- End diff --

I can, will do. We should also upgrade some other components to lang3 as 
lang is outdated


---
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: Attempt to resolve ovm3 jenkins failure

[rsafonseca]

Github user rsafonseca commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/497#discussion_r32917768
  
--- Diff: plugins/hypervisors/ovm3/pom.xml ---
@@ -27,11 +27,31 @@
 ../../pom.xml
   
   
-
-org.apache.xmlrpc
-xmlrpc-client
-3.1.3
-
+
+   xml-apis
+   xml-apis
--- End diff --

It's not a new dependency, just an explicit declaration of something that 
was a dependency already.


---
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: Attempt to resolve ovm3 jenkins failure

[rsafonseca]

Github user rsafonseca commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/497#discussion_r32917802
  
--- Diff: plugins/hypervisors/ovm3/pom.xml ---
@@ -27,11 +27,31 @@
 ../../pom.xml
   
   
-
-org.apache.xmlrpc
-xmlrpc-client
-3.1.3
-
+
+   xml-apis
+   xml-apis
+   1.4.01
+
+
+  org.apache.xmlrpc
+  xmlrpc-client
+  3.1.3
--- End diff --

We can and should, i just kept this one the way it was, version was already 
specified in the version currently in master, will update


---
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.
---

Build failed in Jenkins: simulator-singlerun #1293

[jenkins]

See 

--
Started by upstream project "build-master-simulator" build number 2110
originally caused by:
 Started by upstream project "build-master" build number 2414
 originally caused by:
  Started by an SCM change
  Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on simulator in workspace 

 > /usr/bin/git rev-parse --is-inside-work-tree # timeout=400
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git # timeout=400
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
 > /usr/bin/git --version # timeout=400
 > /usr/bin/git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git 
 > +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:735)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:983)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1016)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1258)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
at hudson.model.Run.execute(Run.java:1759)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags 
--progress https://git-wip-us.apache.org/repos/asf/cloudstack.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: error:  while accessing 
https://git-wip-us.apache.org/repos/asf/cloudstack.git/info/refs

fatal: HTTP request failed

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1591)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:86)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:324)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:324)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
at ..remote call to simulator(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
at hudson.remoting.Channel.call(Channel.java:752)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor375.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at sun.proxy.$Proxy46.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:733)
... 11 more
ERROR: Error fetching remote repo 'origin'
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - No test report file(s) were found with the pattern 
'xunit.xml' relative to 
' for the testing 
framework 'JUnit'.  Did you enter a pattern relative to the correct directory?  
Did you generate the result report(s) for 'JUnit'?
[xUnit] [ERROR] - No test reports found for the metric 'JUnit' with the 
resolved pattern 'xunit.xml'. Configuration error?.
[xUnit] [INFO] - Failing

Build failed in Jenkins: simulator-singlerun #1292

[jenkins]

See 

--
Started by upstream project "build-master-simulator" build number 2109
originally caused by:
 Started by an SCM change
 Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on simulator in workspace 

 > /usr/bin/git rev-parse --is-inside-work-tree # timeout=400
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git # timeout=400
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
 > /usr/bin/git --version # timeout=400
 > /usr/bin/git fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/cloudstack.git 
 > +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/cloudstack.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:735)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:983)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1016)
at hudson.scm.SCM.checkout(SCM.java:484)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1258)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
at hudson.model.Run.execute(Run.java:1759)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags 
--progress https://git-wip-us.apache.org/repos/asf/cloudstack.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: error:  while accessing 
https://git-wip-us.apache.org/repos/asf/cloudstack.git/info/refs

fatal: HTTP request failed

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1591)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1379)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:86)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:324)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:324)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
at ..remote call to simulator(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
at hudson.remoting.Channel.call(Channel.java:752)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor375.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at sun.proxy.$Proxy46.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:733)
... 11 more
ERROR: Error fetching remote repo 'origin'
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - No test report file(s) were found with the pattern 
'xunit.xml' relative to 
' for the testing 
framework 'JUnit'.  Did you enter a pattern relative to the correct directory?  
Did you generate the result report(s) for 'JUnit'?
[xUnit] [ERROR] - No test reports found for the metric 'JUnit' with the 
resolved pattern 'xunit.xml'. Configuration error?.
[xUnit] [INFO] - Failing BUILD.
[xUnit] [INFO] - There are errors when processing test results.
[xUnit] [INFO] 

[GitHub] cloudstack pull request: Fix findbugs DM_BOXED_PRIMITIVE_FOR_PARSI...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Fix findbugs SQL_PREPARED_STATEMENT_GENER...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Fix findbugs DM_BOXED_PRIMITIVE_FOR_PARSI...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Fix findbugs DM_BOXED_PRIMITIVE_FOR_PARSI...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Fix findbugs DM_BOXED_PRIMITIVE_FOR_PARSI...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Fix 2 more findbugs DM_BOXED_PRIMITIVE_FO...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Fix 2 findbugs occurences of DM_BOXED_PRI...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Fix findbugs DM_BOXED_PRIMITIVE_FOR_PARSI...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-8572:Unable to deploy VM as no...

[pritisarap12]

Github user pritisarap12 closed the pull request at:

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


---
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-8574: Skip testcases for LXC i...

[gauravaradhye]

Github user gauravaradhye commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/488#discussion_r32909733
  
--- Diff: test/integration/component/test_stopped_vm.py ---
@@ -53,6 +54,13 @@ def setUpClass(cls):
 cls.domain = get_domain(cls.api_client)
 cls.zone = get_zone(cls.api_client, 
cls.testClient.getZoneForTests())
 
+cls.hypervisor = cls.testClient.getHypervisorInfo()
+
+if cls.hypervisor.lower() == 'lxc':
+if not find_storage_pool_type(cls.apiclient, 
storagetype='rbd'):
+raise unittest.SkipTest("RBD storage type is required for 
data volumes for LXC")
--- End diff --

Don't skip from setUpClass. Skip through individual test case or setUp().


---
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-8572:Unable to deploy VM as no...

[gauravaradhye]

Github user gauravaradhye commented on the pull request:

https://github.com/apache/cloudstack/pull/480#issuecomment-114025746
  
Please close this review request.


---
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.
---