[GitHub] cloudstack pull request: CLOUDSTACK-8800 : Improved the listVirtua...

[maneesha-p]

Github user maneesha-p commented on the pull request:

https://github.com/apache/cloudstack/pull/780#issuecomment-188171070
  
@remibergsma @wido @bhaisaab  2 LGTMs can it be merged?


---
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-8829 : Consecutive cold migrat...

[maneesha-p]

Github user maneesha-p commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/797#discussion_r53916405
  
--- Diff: 
engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java ---
@@ -1776,19 +1773,26 @@ private void orchestrateStorageMigration(final 
String vmUuid, final StoragePool
 // If VM was cold migrated between clusters belonging to 
two different VMware DCs,
 // unregister the VM from the source host and cleanup the 
associated VM files.
 if (vm.getHypervisorType().equals(HypervisorType.VMware)) {
+Long srcClusterId = null;
+Long srcHostId = vm.getHostId() != null ? 
vm.getHostId() : vm.getLastHostId();
+if (srcHostId != null) {
+HostVO srcHost = _hostDao.findById(srcHostId);
--- End diff --

@alexandrelimassantana 'srcHost' variable is local to the if-block but 
'srcClusterId' variable that is populated inside the if-block is outside the 
scope of it and as @GabrielBrascher mentioned its being used in line 1784.


---
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: Question regarding cloudstack logging

[Rafael Weingärtner]

I do not know what the academic literature says about it, but when I
mentioned legacy code, I meant old and not well-designed code. It could
also mean code that uses some old version of a technology. However, in
those cases you pointed out, the technology is still the same (Java), even
though it was probably coded with Java 1.4 or 1.5, at that time there were
ways to treat those exceptions without silencing them, and if you want to
silence an exception, you should/could, at least, log it as a
warn/info/debug message.

I find it a bad programming practice for a simple reason; if an exception
occurs within those methods, there is no easy way to know what is
happening. The flow of execution will continue (the catch silenced the
exception) and that can cause problems that the only way to find the root
cause is a debug of the whole execution flow. That makes it almost
impossible for administrators to trace those exceptions and report a
bug/problem, relying on developers to do that job.

On Wed, Feb 24, 2016 at 1:31 AM, sangeeta lal 
wrote:

> Dear Rafael and Dev Team,
>
> Thanks for your reply.
>
> On internet I found  that legacy code: *is a type of code which is used in
> the software currently, but there are new and better technology that can
> replace it in the future. *Please let me know if my interpretation is
> correct.
>
> Also,  can you please elaborate more, why it is a bad programming practice?
> and where I can find more information about it.
>
>
> Thank You
>
> On Tue, Feb 23, 2016 at 9:17 PM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > Dear Sangeeta,
> >
> > Those examples you provided are a bad programming practice (in my
> opinion).
> > They are legacy code, and we are trying to fix them whenever we uncover
> > one.
> >
> > On Tue, Feb 23, 2016 at 11:11 AM, sangeeta lal 
> > wrote:
> >
> > > Dear Dev Team,
> > >
> > >
> > > I am Sangeeta (PhD) scholar from India. I am working in the area  of
> > mining
> > > software repositories and my aim is to study logging practices of
> > > developers. I am using Apache CloudStack project for my study.
> > > I notice that when a try block consist of following three types of
> > > statements, their corresponding catch block is not logged.
> > >
> > > *Type 1 : * {
> > >   org.apache.axiom.soap.SOAPEnvelope
> > resultEnv=resultContext.getEnvelope();
> > >   java.lang.Object
> > >
> > >
> >
> object=fromOM(resultEnv.getBody().getFirstElement(),com.amazon.ec2.client.AmazonEC2Stub.DescribePlacementGroupsResponse.class,getEnvelopeNamespaces(resultEnv));
> > >
> > >
> > >
> >
> callback.receiveResultdescribePlacementGroups((com.amazon.ec2.client.AmazonEC2Stub.DescribePlacementGroupsResponse)object);
> > > }
> > >
> > > *Type 2:* {
> > >   return
> > >
> > >
> >
> param.getOMElement(com.amazon.ec2.CreateNetworkInterfaceResponse.MY_QNAME,org.apache.axiom.om.OMAbstractFactory.getOMFactory());
> > > }
> > >
> > >
> > > *Type 3:* {
> > >
> > >
> > >
> >
> isReaderMTOMAware=java.lang.Boolean.TRUE.equals(reader.getProperty(org.apache.axiom.om.OMConstants.IS_DATA_HANDLERS_AWARE));
> > > }
> > >
> > >
> > > Can any of you please tell me why is it happening?
> > >
> > > Thank You So Much!!
> > >
> > > --
> > > Regards...
> > > Sangeeta
> > > Assistant Professor
> > > CSE Department @JIIT Noida
> > >
> >
> >
> >
> > --
> > Rafael Weingärtner
> >
>
>
>
> --
> Regards...
> Sangeeta
> Assistant Professor
> CSE Department @JIIT Noida
>



-- 
Rafael Weingärtner

[GitHub] cloudstack pull request: CLOUDSTACK-8830 : VM snapshot creation fa...

[nitt10prashant]

Github user nitt10prashant commented on the pull request:

https://github.com/apache/cloudstack/pull/1377#issuecomment-188173843
  
this is redundant case , and checking time to create vmsnapshot is not 
required for this bug.
I have talked to @sarathkouk , he understood the issue and agreed to modify 
the PR to CATH this specific bug.  


---
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-9140: Testcase to verify if De...

[shwetaag]

Github user shwetaag commented on the pull request:

https://github.com/apache/cloudstack/pull/1218#issuecomment-188178629
  
did code walk through. LGTM


---
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-9140: Testcase to verify if De...

[asfgit]

Github user asfgit closed the pull request at:

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


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

VPC Inline LB VM Plugin

[Nick LIVENS]

Hi all,

I'd like to propose a new plugin called the "VPC Inline LB VM" plugin.
The design document can be found at :
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61340894

Looking forward to hear your reviews / thoughts.

Thanks!

Kind regards,
Nick Livens

Re: Nvidia GRID vGPUs not detected by VMs

[Nux!]

And to answer my own question, what I did to get it working is (in the VM):
- disable the Microsoft Display Adapter
- install the NVIDIA drivers version 
354.56_grid_kepler_win8_win7_64bit_international

Then, after the reboot the VM came back with a NVIDIA GRID card as expected.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Nux!" 
> To: "dev" 
> Cc: "Cloudstack Users List" 
> Sent: Tuesday, 23 February, 2016 20:17:23
> Subject: Nvidia GRID vGPUs not detected by VMs

> Hi,
> 
> Has anyone played with the GRID vGPUs from Nvidia?
> I got it working at some point in the recent past, but not sure what has
> happened in the meanwhile, although Cloudstack allocated the vGPU correctly
> (checked XenCenter), Windows 8.1 VM will not "see it"; driver installations
> fails as well since the correct GPU is not detected.
> 
> Anyone got a clue what voodoo must be invoked?
> The XenServer is up to date and licensed as Enterprise.
> 
> XenCenter shows me the GPU is nicely sliced between the VMs that use the
> feature, confirmed by the Properties section of the said VMs; vGPUs are
> allocated to the, yet Windows only shows a "Microsoft Display Adapter" in
> Device Manager.
> 
> Oddly nvidia-smi should be showing me some vGPUs are in use, which does not 
> seem
> to be the case..
> 
> nvidia-smi
> Tue Feb 23 20:09:19 2016
> +--+
>| NVIDIA-SMI 352.70 Driver Version: 352.70 |
>|---+--+--+
>| GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
>| Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. |
>|===+==+==|
>|   0  GRID K2 On   | :05:00.0 Off |  Off |
>| N/A   35CP828W / 117W |426MiB /  4095MiB |  0%  Default |
> +---+--+--+
>|   1  GRID K2 On   | :06:00.0 Off |  Off |
>| N/A   35CP851W / 117W |906MiB /  4095MiB |  0%  Default |
> +---+--+--+
>   
> +-+
>| Processes:   GPU Memory |
>|  GPU   PID  Type  Process name   Usage  |
>|=|
>|  No running processes found |
> +-+
> 
> Nothing helpful in the logs.
> 
> Thoughts?
> 
> Cheers
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro

[GitHub] cloudstack pull request: [4.7] vmware: improve support for disks

[bhaisaab]

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

https://github.com/apache/cloudstack/pull/1365#discussion_r53929677
  
--- Diff: 
vmware-base/src/com/cloud/hypervisor/vmware/mo/GuestOsDescriptorType.java ---
@@ -0,0 +1,46 @@
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements.  See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership.  The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License.  You may obtain a copy of the License at
+//
+//   http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied.  See the License for the
+// specific language governing permissions and limitations
+// under the License.
+package com.cloud.hypervisor.vmware.mo;
+
+public enum GuestOsDescriptorType
+{
+  windows9Guest,
+  windows9_64Guest,
+  windows9Server64Guest,
+  rhel7Guest,
+  rhel7_64Guest,
+  debian7Guest,
+  debian7_64Guest,
+  debian8Guest,
+  debian8_64Guest,
+  coreos_64Guest,
+  darwin12_64Guest,
+  darwin13_64Guest,
+  darwin14_64Guest;
+
+  public static GuestOsDescriptorType fromValue(String value) {
+if (value == null) {
+  return null;
+}
+GuestOsDescriptorType guestOsType = null;
+try {
+  guestOsType = valueOf(value);
+} catch (IllegalArgumentException e) {
+}
+return guestOsType;
+  }
--- End diff --

Thanks @GabrielBrascher I checked that with latest VMware SDK I could 
remove this wrapper. I've pushed another PR on master that bumps up the vmware 
sdk version to 6.0. I'll remove this soon, and resend for a review.


---
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: [4.5] vmware: improve support for disk co...

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack/pull/1366#issuecomment-188224889
  
@cristofolini I think you're right, both Travis and Jenkins are having 
inconsistent builds. While I could refactor the method in its own method, I 
don't see if it could be reused elsewhere. I'll try to fix the PR soon. Thanks.


---
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-8830 CLONE - VM snapshot fails...

[maneesha-p]

Github user maneesha-p commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/798#discussion_r53932297
  
--- Diff: 
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareStorageManagerImpl.java
 ---
@@ -1464,4 +1440,45 @@ private String deleteDir(String dir) {
 private static String getVolumeRelativeDirInSecStroage(long volumeId) {
 return "volumes/" + volumeId;
 }
+
+/**
+ * This method is to check if a given TaskInfo Object is valid( and 
has name and entity name assigned).It return true if TaskInfo Object is valid 
and false otherwise.
+ *
+ * @param TaskInfo
+ *info
+ * @return boolean(true or false)
+ **/
+private boolean isvalidTaskInfoObj(TaskInfo info){
+return !(info == null || info.getEntityName() == null || 
info.getName() == null);
+}
+
+private boolean waitForRunningTaskOnVM(String vmName, String taskName, 
VmwareContext context) throws Exception {
--- End diff --

@rodrigo93 It returns the same value as method 'waitForTask' .


---
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-www pull request: Updated list with makewholist.py

[thinktwo]

GitHub user thinktwo opened a pull request:

https://github.com/apache/cloudstack-www/pull/25

Updated list with makewholist.py



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

$ git pull https://github.com/thinktwo/cloudstack-www patch-10

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

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


commit 65a0b8327d2183c280ed93ab529251ffa8411d0a
Author: Jan-Arve Nygård 
Date:   2016-02-24T13:26:09Z

Updated list with makewholist.py




---
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-www pull request: Updated list with makewholist.py

[pdion891]

Github user pdion891 commented on the pull request:

https://github.com/apache/cloudstack-www/pull/25#issuecomment-188271044
  
LGTM


---
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-www pull request: Updated list with makewholist.py

[terbolous]

Github user terbolous commented on the pull request:

https://github.com/apache/cloudstack-www/pull/25#issuecomment-188271943
  
Some of these are moved from emeritus to active with this commit



---
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: Question regarding cloudstack logging

[sangeeta lal]

Dear Rafael and Dev Team,

I highly appreciate you effort. Thanks! for your reply.

Thank you

On Wed, Feb 24, 2016 at 3:37 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> I do not know what the academic literature says about it, but when I
> mentioned legacy code, I meant old and not well-designed code. It could
> also mean code that uses some old version of a technology. However, in
> those cases you pointed out, the technology is still the same (Java), even
> though it was probably coded with Java 1.4 or 1.5, at that time there were
> ways to treat those exceptions without silencing them, and if you want to
> silence an exception, you should/could, at least, log it as a
> warn/info/debug message.
>
> I find it a bad programming practice for a simple reason; if an exception
> occurs within those methods, there is no easy way to know what is
> happening. The flow of execution will continue (the catch silenced the
> exception) and that can cause problems that the only way to find the root
> cause is a debug of the whole execution flow. That makes it almost
> impossible for administrators to trace those exceptions and report a
> bug/problem, relying on developers to do that job.
>
> On Wed, Feb 24, 2016 at 1:31 AM, sangeeta lal 
> wrote:
>
> > Dear Rafael and Dev Team,
> >
> > Thanks for your reply.
> >
> > On internet I found  that legacy code: *is a type of code which is used
> in
> > the software currently, but there are new and better technology that can
> > replace it in the future. *Please let me know if my interpretation is
> > correct.
> >
> > Also,  can you please elaborate more, why it is a bad programming
> practice?
> > and where I can find more information about it.
> >
> >
> > Thank You
> >
> > On Tue, Feb 23, 2016 at 9:17 PM, Rafael Weingärtner <
> > rafaelweingart...@gmail.com> wrote:
> >
> > > Dear Sangeeta,
> > >
> > > Those examples you provided are a bad programming practice (in my
> > opinion).
> > > They are legacy code, and we are trying to fix them whenever we uncover
> > > one.
> > >
> > > On Tue, Feb 23, 2016 at 11:11 AM, sangeeta lal <
> sangeeta.6...@gmail.com>
> > > wrote:
> > >
> > > > Dear Dev Team,
> > > >
> > > >
> > > > I am Sangeeta (PhD) scholar from India. I am working in the area  of
> > > mining
> > > > software repositories and my aim is to study logging practices of
> > > > developers. I am using Apache CloudStack project for my study.
> > > > I notice that when a try block consist of following three types of
> > > > statements, their corresponding catch block is not logged.
> > > >
> > > > *Type 1 : * {
> > > >   org.apache.axiom.soap.SOAPEnvelope
> > > resultEnv=resultContext.getEnvelope();
> > > >   java.lang.Object
> > > >
> > > >
> > >
> >
> object=fromOM(resultEnv.getBody().getFirstElement(),com.amazon.ec2.client.AmazonEC2Stub.DescribePlacementGroupsResponse.class,getEnvelopeNamespaces(resultEnv));
> > > >
> > > >
> > > >
> > >
> >
> callback.receiveResultdescribePlacementGroups((com.amazon.ec2.client.AmazonEC2Stub.DescribePlacementGroupsResponse)object);
> > > > }
> > > >
> > > > *Type 2:* {
> > > >   return
> > > >
> > > >
> > >
> >
> param.getOMElement(com.amazon.ec2.CreateNetworkInterfaceResponse.MY_QNAME,org.apache.axiom.om.OMAbstractFactory.getOMFactory());
> > > > }
> > > >
> > > >
> > > > *Type 3:* {
> > > >
> > > >
> > > >
> > >
> >
> isReaderMTOMAware=java.lang.Boolean.TRUE.equals(reader.getProperty(org.apache.axiom.om.OMConstants.IS_DATA_HANDLERS_AWARE));
> > > > }
> > > >
> > > >
> > > > Can any of you please tell me why is it happening?
> > > >
> > > > Thank You So Much!!
> > > >
> > > > --
> > > > Regards...
> > > > Sangeeta
> > > > Assistant Professor
> > > > CSE Department @JIIT Noida
> > > >
> > >
> > >
> > >
> > > --
> > > Rafael Weingärtner
> > >
> >
> >
> >
> > --
> > Regards...
> > Sangeeta
> > Assistant Professor
> > CSE Department @JIIT Noida
> >
>
>
>
> --
> Rafael Weingärtner
>



-- 
Regards...
Sangeeta
Assistant Professor
CSE Department @JIIT Noida

[GitHub] cloudstack-www pull request: Updated list with makewholist.py

[terbolous]

Github user terbolous commented on the pull request:

https://github.com/apache/cloudstack-www/pull/25#issuecomment-188276456
  
My bad, they aren't actually removed from the emeritus list, just added to 
the active list. 



---
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: Question about templates and zones

[Patrick Dube]

Templates can be cross zones if the secondary storage is cross zones. In
the case of Swift, templates are not tied to a zone.

On Tue, Feb 23, 2016 at 4:48 PM, Tutkowski, Mike 
wrote:

> I see. Yeah, I just took a quick peek at the GUI and it drives the
> interaction through the selection of a zone for the template.
> 
> From: Syed Mushtaq 
> Sent: Tuesday, February 23, 2016 2:32 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Question about templates and zones
>
> Yes but that is optional though. You can still delete a template just by
> giving the ID
>
> On Tue, Feb 23, 2016 at 4:20 PM, Tutkowski, Mike <
> mike.tutkow...@netapp.com>
> wrote:
>
> > Hi Syed,
> >
> > I don't have a direct answer for your question, but I do know that when I
> > delete a template, I have to specify a zone.
> >
> > Talk to you later,
> > Mike
> > 
> > From: Syed Mushtaq 
> > Sent: Tuesday, February 23, 2016 11:58 AM
> > To: dev@cloudstack.apache.org
> > Subject: Question about templates and zones
> >
> > Hi,
> >
> > I am trying to figure out a bug where we create a template from snapshot
> > and the API response returns NULL. We use Swift as a secondary storage
> and
> > by default, its scope is REGION. My question is, are templates tied to a
> > zone? Because what I see is in the template_zone_ref table, there is an
> > entry for my template with zone_id=1 but the template_view table shows
> > data_center_id as NULL. So I am now confused as to what is the correct
> > value and what my fix should be.
> >
> > Thanks,
> > -Syed
> >
>

[PROPOSAL] Remove the word active from project members on website

[Jan-Arve Nygård]

Hi all,

We now have a script to populate the project members list (
http://cloudstack.apache.org/who.html) on the website based on Apache
Project Directory. This makes it a lot easier to keep the list up to date.
The problem is that members manually moved to the emeritus will be added to
the list again each time.

A quick fix would be the remove the word "active" from the title of PMC and
committers while the emeritus sections still remains and can be updated
manually with members that are not active anymore.

Thoughts?


-JAN

Re: [PROPOSAL] Remove the word active from project members on website

[Will Stevens]

I have not seen the script, so I am not sure how changing the title will
modify the behavior, but if it will infact make the management of the list
easier, then I am +1.

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Wed, Feb 24, 2016 at 9:43 AM, Jan-Arve Nygård 
wrote:

> Hi all,
>
> We now have a script to populate the project members list (
> http://cloudstack.apache.org/who.html) on the website based on Apache
> Project Directory. This makes it a lot easier to keep the list up to date.
> The problem is that members manually moved to the emeritus will be added to
> the list again each time.
>
> A quick fix would be the remove the word "active" from the title of PMC and
> committers while the emeritus sections still remains and can be updated
> manually with members that are not active anymore.
>
> Thoughts?
>
>
> -JAN
>

Re: [PROPOSAL] Remove the word active from project members on website

[Patrick Dube]

When was the committer list last updated? It seems out of date

On Wed, Feb 24, 2016 at 9:50 AM, Will Stevens  wrote:

> I have not seen the script, so I am not sure how changing the title will
> modify the behavior, but if it will infact make the management of the list
> easier, then I am +1.
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Wed, Feb 24, 2016 at 9:43 AM, Jan-Arve Nygård <
> jan.arve.nyg...@gmail.com>
> wrote:
>
> > Hi all,
> >
> > We now have a script to populate the project members list (
> > http://cloudstack.apache.org/who.html) on the website based on Apache
> > Project Directory. This makes it a lot easier to keep the list up to
> date.
> > The problem is that members manually moved to the emeritus will be added
> to
> > the list again each time.
> >
> > A quick fix would be the remove the word "active" from the title of PMC
> and
> > committers while the emeritus sections still remains and can be updated
> > manually with members that are not active anymore.
> >
> > Thoughts?
> >
> >
> > -JAN
> >
>

Re: [PROPOSAL] Remove the word active from project members on website

[Jan-Arve Nygård]

2016-02-24 15:50 GMT+01:00 Will Stevens :

> I have not seen the script, so I am not sure how changing the title will
> modify the behavior, but if it will infact make the management of the list
> easier, then I am +1.
>

The reasons is that the source (Apache Project Directory) don't have any
information if the members is active or not. Removing "active" in the title
and have the list to just contain all current members (active or not) would
eliminate the need to match the results against the emeritus list.


>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Wed, Feb 24, 2016 at 9:43 AM, Jan-Arve Nygård <
> jan.arve.nyg...@gmail.com>
> wrote:
>
> > Hi all,
> >
> > We now have a script to populate the project members list (
> > http://cloudstack.apache.org/who.html) on the website based on Apache
> > Project Directory. This makes it a lot easier to keep the list up to
> date.
> > The problem is that members manually moved to the emeritus will be added
> to
> > the list again each time.
> >
> > A quick fix would be the remove the word "active" from the title of PMC
> and
> > committers while the emeritus sections still remains and can be updated
> > manually with members that are not active anymore.
> >
> > Thoughts?
> >
> >
> > -JAN
> >
>

Re: [PROPOSAL] Remove the word active from project members on website

[Sebastien Goasguen]

> On Feb 24, 2016, at 4:28 PM, Jan-Arve Nygård  
> wrote:
> 
> 2016-02-24 15:50 GMT+01:00 Will Stevens :
> 
>> I have not seen the script, so I am not sure how changing the title will
>> modify the behavior, but if it will infact make the management of the list
>> easier, then I am +1.
>> 
> 
> The reasons is that the source (Apache Project Directory) don't have any
> information if the members is active or not. Removing "active" in the title
> and have the list to just contain all current members (active or not) would
> eliminate the need to match the results against the emeritus list.
> 

If have had some discussions in the PMC about this list.
People have different views.

The problem I see with the list is that it does not represent the currently 
active people.
There are folks on this list that have not done anything for years, it is not 
bad, it is the nature of open source contribution.

Per ASF bylaws, merit does not expire, so committership does not expire. 
Emeritus is actually a fuzzy term according to bylaws and people are reluctant 
to ask others “hey are you sure you should still be listed as committer ?"

I need to look again at the emeritus status and see if we could make this list 
more “real”.

thoughts welcome,

> 
>> 
>> *Will STEVENS*
>> Lead Developer
>> 
>> *CloudOps* *| *Cloud Solutions Experts
>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> w cloudops.com *|* tw @CloudOps_
>> 
>> On Wed, Feb 24, 2016 at 9:43 AM, Jan-Arve Nygård <
>> jan.arve.nyg...@gmail.com>
>> wrote:
>> 
>>> Hi all,
>>> 
>>> We now have a script to populate the project members list (
>>> http://cloudstack.apache.org/who.html) on the website based on Apache
>>> Project Directory. This makes it a lot easier to keep the list up to
>> date.
>>> The problem is that members manually moved to the emeritus will be added
>> to
>>> the list again each time.
>>> 
>>> A quick fix would be the remove the word "active" from the title of PMC
>> and
>>> committers while the emeritus sections still remains and can be updated
>>> manually with members that are not active anymore.
>>> 
>>> Thoughts?
>>> 
>>> 
>>> -JAN
>>> 
>> 

Re: Question about templates and zones

[Syed Mushtaq]

Right, so if we have a region store (Swift or S3) that means that the
templates should be cross zoned correct? I see this is the case with
registerTemplate API but with createTemplate, it looks like we are not
setting the cross zone flag I'm assuming that is a bug unless someone knows
a reason.

On Wed, Feb 24, 2016 at 9:32 AM, Patrick Dube 
wrote:

> Templates can be cross zones if the secondary storage is cross zones. In
> the case of Swift, templates are not tied to a zone.
>
> On Tue, Feb 23, 2016 at 4:48 PM, Tutkowski, Mike <
> mike.tutkow...@netapp.com>
> wrote:
>
> > I see. Yeah, I just took a quick peek at the GUI and it drives the
> > interaction through the selection of a zone for the template.
> > 
> > From: Syed Mushtaq 
> > Sent: Tuesday, February 23, 2016 2:32 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: Question about templates and zones
> >
> > Yes but that is optional though. You can still delete a template just by
> > giving the ID
> >
> > On Tue, Feb 23, 2016 at 4:20 PM, Tutkowski, Mike <
> > mike.tutkow...@netapp.com>
> > wrote:
> >
> > > Hi Syed,
> > >
> > > I don't have a direct answer for your question, but I do know that
> when I
> > > delete a template, I have to specify a zone.
> > >
> > > Talk to you later,
> > > Mike
> > > 
> > > From: Syed Mushtaq 
> > > Sent: Tuesday, February 23, 2016 11:58 AM
> > > To: dev@cloudstack.apache.org
> > > Subject: Question about templates and zones
> > >
> > > Hi,
> > >
> > > I am trying to figure out a bug where we create a template from
> snapshot
> > > and the API response returns NULL. We use Swift as a secondary storage
> > and
> > > by default, its scope is REGION. My question is, are templates tied to
> a
> > > zone? Because what I see is in the template_zone_ref table, there is an
> > > entry for my template with zone_id=1 but the template_view table shows
> > > data_center_id as NULL. So I am now confused as to what is the correct
> > > value and what my fix should be.
> > >
> > > Thanks,
> > > -Syed
> > >
> >
>

[GitHub] cloudstack pull request: CLOUDSTACK-9252: Support configurable NFS...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-9252: Support configurable NFS...

[rafaelweingartner]

Github user rafaelweingartner commented on the pull request:

https://github.com/apache/cloudstack/pull/1361#issuecomment-188440358
  
merged based on testes and reviews


---
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-9267: String is not localized ...

[rafaelweingartner]

Github user rafaelweingartner commented on the pull request:

https://github.com/apache/cloudstack/pull/1390#issuecomment-188441817
  
@nitin-maharana have you tested everything? @DaanHoogland  Can we merge 
this? And then forward it to master


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

Questions: Volume snapshots

[Tutkowski, Mike]

Hi,


In the process of developing a form of volume snapshots that are stored on 
primary storage (for managed storage only), I have noticed a couple things 
about (traditional) volume snapshots that perhaps one of you may be able to 
answer.


1) After deleting a volume snapshot, I notice the cloud.snapshots.removed cell 
for the applicable row is still set to null. I assume this is a bug? The 
cloud.snapshots.status cell for this row is set to Destroyed, so perhaps this 
is all we look at.


2) When we take a volume snapshot on XenServer, we take a hypervisor snapshot 
of the applicable virtual disk and copy it to secondary storage.


When we delete the volume snapshot, the hypervisor snapshot of that virtual 
disk does not get deleted (even when no more volume snapshots exist for the 
volume in question). Seems like a bug perhaps?


Thanks,

Mike

Contributing to ACS

[Will Stevens]

Sorry I have not been as active as I should be in the development and
support of the project.  I getting my head back into it (slowly).

Are the instructions that I wrote [1
] for
contributing to ACS still the recommended way to contribute?  I see they
are still referenced in the official docs [2
], so I am guessing they are
still valid.

I know there has been some work towards integrating CI, but I am not
currently up to speed on that progress or status, so I am not sure if
things have changed.

[1] https://github.com/apache/cloudstack/blob/master/CONTRIBUTING.md
[2] https://cloudstack.apache.org/developers.html

Thanks,

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

Build failed in Jenkins: build-master-slowbuild #3315

[jenkins]

See 

Changes:

[nicolas.m.vazquez] CLOUDSTACK-9252: Add nfs version to commands

[nicolas.m.vazquez] CLOUDSTACK-9252: Support configurable nfs version

[nicolas.m.vazquez] CLOUDSTACK-9252: Remove duplicates getNfsVersion, refactor

[nicolas.m.vazquez] CLOUDSTACK-9252: Remove static dependencies, refactor

[nicolas.m.vazquez] CLOUDSTACK-9252: New refactor

[nicolas.m.vazquez] CLOUDSTACK-9252: Add unit tests

[nicolas.m.vazquez] CLOUDSTACK-9252: Mock application context for unit test

[nicolas.m.vazquez] CLOUDSTACK-9252: Little refactor

[nicovazquez90] CLOUDSTACK-9252: Add missing licence header

[nicolas.m.vazquez] CLOUDSTACK-9252: Last refactor, passing nfs version to ssvm

--
[...truncated 28689 lines...]
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:findbugs (findbugs) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud ---
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:instrument (default-cli) @ 
cloud-quickcloud ---
[WARNING] No files to instrument.
[INFO] NOT adding cobertura ser file to attached artifacts list.
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-quickcloud ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
cloud-quickcloud ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[1.762s]
[INFO] Apache CloudStack . SUCCESS [2.143s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.794s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.054s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:29.803s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.116s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.342s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.684s]
[INFO] Apache CloudStack API . SUCCESS [1:50.546s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.019s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.017s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.094s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.487s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.881s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.547s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.540s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [37.530s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [13.919s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:06.601s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.510s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [26.546s]
[INFO] Apache CloudStack Server .. SUCCESS [4:12.943s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [38.546s]
[INFO] Apache CloudStack Usage Server  SUCCESS [43.639s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.096s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.079s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.443s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.958s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [47.580s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.479s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.493s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.917s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [22.774s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.175s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.265s]
[INFO] Apache CloudStack Cloud Engine Service 

Build failed in Jenkins: build-master-slowbuild #3316

[jenkins]

See 

--
[...truncated 28679 lines...]
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:findbugs (findbugs) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud ---
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:instrument (default-cli) @ 
cloud-quickcloud ---
[WARNING] No files to instrument.
[INFO] NOT adding cobertura ser file to attached artifacts list.
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-quickcloud ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
cloud-quickcloud ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[2.141s]
[INFO] Apache CloudStack . SUCCESS [2.085s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.781s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [18.790s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.737s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.103s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [52.520s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [28.179s]
[INFO] Apache CloudStack API . SUCCESS [1:47.483s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.317s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.655s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.088s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.452s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.823s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.638s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.677s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.445s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.154s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:06.662s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [39.981s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.733s]
[INFO] Apache CloudStack Server .. SUCCESS [4:15.614s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [36.639s]
[INFO] Apache CloudStack Usage Server  SUCCESS [45.652s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.912s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.074s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.426s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.228s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [47.987s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.983s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [25.404s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [26.103s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [22.933s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [36.131s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.303s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.178s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [1.007s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.560s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.975s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[37.473s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.376s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.131s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [14.632s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.726s]
[INFO] Apache Cloud

[GitHub] cloudstack pull request: CLOUDSTACK-9267: String is not localized ...

[nitin-maharana]

Github user nitin-maharana commented on the pull request:

https://github.com/apache/cloudstack/pull/1390#issuecomment-188609151
  
@rafaelweingartner : I have tested all 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.
---

PR validation using proposed CI.

[Bharat Kumar]

Hi,

As all of you know from earlier discussions in the community, we have been 
working on implementing a CI to test github PRs and publish results. We have 
implemented this 
internally and will start testing PRs and publish the results by mail to dev 
list. 

At this point if a test fails, we do not know it for sure if it is due to a bug 
in the test, in cloudstack or in the CI environment. We do not have anything to 
cross reference. If a test is being
reported as failure but is passing in your local environment,  please let us 
know we will try and fix this in the CI environment.

We also do not have a way to share the management server logs and test run 
logs. we are working on it. 

Please let us know if you guys think any improvements are needed.

Thanks,
Bharat.

Re: ACS CI BVT RUN: xenserver: Pr_number: 1417

[Bharat Kumar]

On 24-Feb-2016, at 10:24 PM, 
jenkins-...@citrix.com wrote:

[http://jenkins-ccp.citrix.com/static/e59dfe28/images/32x32/red.gif]BUILD 
FAILURE
Build Start Date:   Wed Feb 24 06:29:34 2016
Git Repo Url:   https://github.com/apache/cloudstack.git
Git Commit Id:  9d89229942436d98f4897d8030f95bb8702bf
Git Branch Info:1417
Hyper Visor Info:   xenserver
Build No:   11
Health Report
W   Description Score
[http://jenkins-ccp.citrix.com//static/d7293164/images/16x16/health-00to19.png] 
Build stability: All recent builds failed.  0
[http://jenkins-ccp.citrix.com//static/d7293164/images/16x16/health-80plus.png] 
Test Result: 22 tests failing out of a total of 142 tests.  84


Changes
No Changes


Test Result
Package Failed  Passed  Skipped Total
< tt=""><>  2   0   0   2
:teardown
:setup
integration.smoke.test_affinity_groups  0   1   0   1
integration.smoke.test_affinity_groups_projects 0   1   0   1
integration.smoke.test_deploy_vgpu_enabled_vm   0   0   1   1
integration.smoke.test_deploy_vm_iso0   1   0   1
integration.smoke.test_deploy_vm_root_resize0   3   0   3
integration.smoke.test_deploy_vm_with_userdata  0   2   0   2
integration.smoke.test_deploy_vms_with_varied_deploymentplanners0   
3   0   3
integration.smoke.test_disk_offerings   0   5   0   5
integration.smoke.test_global_settings  0   1   0   1
integration.smoke.test_guest_vlan_range 1   0   0   1
integration.smoke.test_guest_vlan_range.TestDedicateGuestVlanRange.test_dedicateGuestVlanRange
integration.smoke.test_internal_lb  0   4   0   4
integration.smoke.test_iso  2   4   1   7
integration.smoke.test_iso.TestISO.test_04_extract_Iso
integration.smoke.test_iso.TestISO.test_07_list_default_iso
integration.smoke.test_loadbalance  0   3   0   3
integration.smoke.test_multipleips_per_nic  0   1   0   1
integration.smoke.test_network  0   10  0   10
integration.smoke.test_network_acl  0   1   0   1
integration.smoke.test_nic  0   1   0   1
integration.smoke.test_nic_adapter_type 0   0   1   1
integration.smoke.test_non_contigiousvlan   0   1   0   1
integration.smoke.test_over_provisioning0   1   0   1
integration.smoke.test_password_server  1   0   0   1
integration.smoke.test_password_server.TestIsolatedNetworksPasswdServer.test_isolate_network_password_server
integration.smoke.test_portable_publicip0   2   0   2
integration.smoke.test_primary_storage  1   1   0   2
integration.smoke.test_primary_storage.TestPrimaryStorageServices.test_01_primary_storage_iscsi
integration.smoke.test_privategw_acl3   1   0   4
integration.smoke.test_privategw_acl.TestPrivateGwACL.test_02_vpc_privategw_static_routes
integration.smoke.test_privategw_acl.TestPrivateGwACL.test_03_vpc_privategw_restart_vpc_cleanup
integration.smoke.test_privategw_acl.TestPrivateGwACL.test_04_rvpc_privategw_static_routes
integration.smoke.test_public_ip_range  0   1   0   1
integration.smoke.test_pvlan0   1   0   1
integration.smoke.test_regions  0   1   0   1
integration.smoke.test_reset_vm_on_reboot   0   1   0   1
integration.smoke.test_resource_detail  0   1   0   1
integration.smoke.test_router_dhcphosts 1   0   0   1
integration.smoke.test_router_dhcphosts.TestRouterDHCPHosts.test_router_dhcphosts
integration.smoke.test_routers  0   9   0   9
integration.smoke.test_routers_iptables_default_policy  0   2   0   
2
integration.smoke.test_routers_network_ops  3   2   0   5
integration.smoke.test_routers_network_ops.TestIsolatedNetworks.test_01_isolate_network_FW_PF_default_routes_egress_true
integration.smoke.test_routers_network_ops.TestRedundantIsolateNetworks.test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true
integration.smoke.test_routers_network_ops.TestRedundantIsolateNetworks.test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false
integration.smoke.test_scale_vm 0   1   0   1
integration.smoke.test_secondary_storage0   2   0   2
integration.smoke.test_service_offerings0   4   0   4
integration.smoke.test_snapshots0   1   0   1
integration.smoke.test_ssvm 0   10  0   10
integration.smoke.test_templates1   7   1   9
integration.smoke.test_templates.TestTemplates.test_04_extract_template
integration.smoke.test_vm_life_cycle1   10  0

Build failed in Jenkins: build-master-slowbuild #3317

[jenkins]

See 

--
[...truncated 28679 lines...]
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:findbugs (findbugs) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud ---
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:instrument (default-cli) @ 
cloud-quickcloud ---
[WARNING] No files to instrument.
[INFO] NOT adding cobertura ser file to attached artifacts list.
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-quickcloud ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
cloud-quickcloud ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[1.719s]
[INFO] Apache CloudStack . SUCCESS [2.646s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.894s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.021s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.335s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.110s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.396s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.353s]
[INFO] Apache CloudStack API . SUCCESS [1:49.702s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.138s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.534s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.102s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.110s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.189s]
[INFO] Apache CloudStack Core  SUCCESS [1:20.425s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.261s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.777s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [15.849s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:08.005s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.208s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.672s]
[INFO] Apache CloudStack Server .. SUCCESS [4:17.373s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.145s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.142s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:23.344s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.081s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.465s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.762s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [47.520s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.940s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.389s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.657s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [21.889s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.695s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.255s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.367s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.987s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.252s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.023s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.625s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.140s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.617s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.849s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.653s]
[INFO] Apache Cloud