date:20160302

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

2016-03-02 Thread 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.780s]
[INFO] Apache CloudStack . SUCCESS [2.161s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.798s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [18.947s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.425s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.103s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.142s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.749s]
[INFO] Apache CloudStack API . SUCCESS [1:49.417s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.192s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.311s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.094s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.272s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.573s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.649s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.194s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [37.023s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.087s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.818s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.394s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [24.950s]
[INFO] Apache CloudStack Server .. SUCCESS [4:18.019s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.894s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.100s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:23.930s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.076s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.459s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.870s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.137s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.527s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.788s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [22.584s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [21.445s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.444s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.422s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.074s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.977s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.524s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[24.100s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[37.696s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.340s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.846s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [16.928s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.778s]
[INFO] Apache Cloud

Bug on delete snapshot function / CLOUDSTACK-9297

2016-03-02 Thread Özhan Rüzgar Karaman

Hi;
2 weeks ago we noticed a bug on delete snapshot function/api for ACS 4.8.
We have created a jira ticket for this bug.

https://issues.apache.org/jira/browse/CLOUDSTACK-9297

issue looks like its similar bug which was mentioned on CLOUDSTACK-8845 .
But because its on other function we have created new ticket.

Our idea is we like to store vm snapshots as disk backup even if we delete
its original(referenced) vm. To achieve this we made a test and we took
some snapshots of vm and after deleting its originating, same vm we noticed
that if we try to delete its snapshot ACS throws exception like "Error
Message : Unable to determine the storage pool of the snapshot."

We checked details from database and we noticed that issue is like
CLOUDSTACK-8845 and snapshot looses its reference vm id. There are more
rich details and test cases on jira ticket.

Does anyone likes to take and work on this issue, if someone could supply a
fix, we could directly make tests on our working environment.

Kindly Regards
Ozhan Ruzgar Karaman

Re: Bug on delete snapshot function / CLOUDSTACK-9297

2016-03-02 Thread Wei ZHOU

Hi Ozhan,

please check the comments of the ticket.

-Wei

2016-03-02 10:22 GMT+01:00 Özhan Rüzgar Karaman :

> Hi;
> 2 weeks ago we noticed a bug on delete snapshot function/api for ACS 4.8.
> We have created a jira ticket for this bug.
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-9297
>
> issue looks like its similar bug which was mentioned on CLOUDSTACK-8845 .
> But because its on other function we have created new ticket.
>
> Our idea is we like to store vm snapshots as disk backup even if we delete
> its original(referenced) vm. To achieve this we made a test and we took
> some snapshots of vm and after deleting its originating, same vm we noticed
> that if we try to delete its snapshot ACS throws exception like "Error
> Message : Unable to determine the storage pool of the snapshot."
>
> We checked details from database and we noticed that issue is like
> CLOUDSTACK-8845 and snapshot looses its reference vm id. There are more
> rich details and test cases on jira ticket.
>
> Does anyone likes to take and work on this issue, if someone could supply a
> fix, we could directly make tests on our working environment.
>
> Kindly Regards
> Ozhan Ruzgar Karaman
>

Build failed in Jenkins: build-systemvm64-master #765

2016-03-02 Thread jenkins

See 

--
[...truncated 3395 lines...]
100% [Packages 28.5 MB]
   
100% [Working]
  
100% [Packages 1,777 kB]

100% [Working]
  
100% [Packages 28.5 MB]
100% [Packages 28.5 MB]
   
100% [Working]
  
100% [Packages 1,790 kB]

100% [Working]
  
100% [Translation-en 18.5 MB]
100% [Translation-en 18.5 MB]
 
100% [Working]
  
100% [Translation-en 1,212 kB]
  
100% [Working]
  
100% [Sources 10.3 kB]
  
100% [Working]
  
100% [Translation-en 14.2 kB]
 
100% [Working]
  
Fetched 7,601 B in 3s (2,026 B/s)

Reading package lists... 0%

Reading package lists... 0%

Reading package lists... 1%

Reading package lists... 26%

Reading package lists... 31%

Reading package lists... 31%

Reading package lists... 48%

Reading package lists... 64%

Reading package lists... 64%

Reading package lists... 75%

Reading package lists... 84%

Reading package lists... 84%

Reading package lists... 86%

Reading package lists... 86%

Reading package lists... 88%

Reading package lists... 88%

Reading package lists... 90%

Reading package lists... 90%

Reading package lists... 90%

Reading package lists... 90%

Reading package lists... 90%

Reading package lists... 90%

Reading package lists... 90%

Reading package lists... 90%

Reading package lists... 93%

Reading package lists... 93%

Reading package lists... 97%

Reading package lists... 97%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... Done

+ apt-get -y --force-yes upgrade

Reading package lists... 0%

Reading package lists... 100%

Reading package lists... Done


Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree   


Reading state information... 0%

Reading state information... 0%

Reading state information... Done

The following packages have been kept back:
  openswan
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
+ '[' amd64 == amd64 ']'
+ wget http://people.apache.org/~rajeshbattala/hv-kvp-daemon_3.1_amd64.deb
--2016-03-02 09:32:40--  
http://people.apache.org/~rajeshbattala/hv-kvp-daemon_3.1_amd64.deb
Resolving people.apache.org (people.apache.org)... 163.172.16.173, 
2001:bc8:2142:100::
Connecting to people.apache.org (people.apache.org)|163.172.16.173|:80... 
connected.
HTTP request sent, awaiting response... 404 Not Found
2016-03-02 09:32:40 ERROR 404: Not Found.

ERROR: exit code 8
Error executing command ./install_systemvm_packages.sh : Exitcode was not what 
we expected
Exitcode was not what we expected
+ on_exit
+ (( i=5-1  ))
+ (( i>=0  ))
+ sleep 2
+ log DEBUG 'on_exit: veewee_destroy'
+ local level=DEBUG
+ shift
+ [[ 1 != \1 ]]
+ local code=
++ date '+%F %T'
+ local 'line=[2016-03-02 09:32:42] DEBUG: on_exit: veewee_destroy'
+ '[' -t 2 ']'
+ echo '[2016-03-02 09:32:42] DEBUG: on_exit: veewee_destroy'
[2016-03-02 09:32:42] DEBUG: on_exit: veewee_destroy
+ eval veewee_destroy
++ veewee_destroy
++ log INFO 'destroying existing veewee image, if any'
++ local level=INFO
++ shift
++ [[ 1 != \1 ]]
++ local code=
+++ date '+%F %T'
++ local 'line=[2016-03-02 09:32:42] INFO: destroying existing veewee image, if 
any'
++ '[' -t 2 ']'
++ echo '[2016-03-02 09:32:42] INFO: destroying existing veewee image, if any'
[2016-03-02 09:32:42] INFO: destroying existing veewee image, if any
++ set +e
++ bundle exec veewee vbox destroy systemvm64template-master-4.6.0
Shutting down vm systemvm64template-master-4.6.0
VBoxManage unregistervm  "systemvm64template-master-4.6.0" --delete
Deleting vm systemvm64template-master-4.6.0
++ set -e
+ (( i--  ))
+ (( i>=0  ))
+ sleep 2
+ log DEBUG 'on_exit: rm -f cloud_scripts_shar_archive.sh'
+ local level=DEBUG
+ shift
+ [[ 1 != \1 ]]
+ local code=
++ date '+%F %T'
+ local 'line=[2016-03-02 09:32:49] DEBUG: on_exit: rm -f 
cloud_scripts_shar_archive.sh'
+ '[' -t 2 ']'
+ echo '[2016-03-02 09:32:49] DEBUG: on_exit: rm -f 
cloud_scripts_shar_archive.sh'
[2016-03-02 09:32:49] DEBUG: on_exit: rm -f cloud_scripts_shar_archive.sh
+ eval rm -f cloud_scripts_shar_archive.sh
++ rm -f cloud_scripts_shar_archive.sh
+ (( i--  ))
+ (( i>=0  ))
+ sleep 2
+ log DEBUG 'on_exit: rm -rf definitions/systemvm64template-master-4.6.0'
+ local level=DEBUG
+ shift
+ [[ 1 != \1 ]]
+ local code=
++ date '+%F %T'
+ local 'line=[2016-03-02 09:32:51] DEBUG: on_exit: rm -rf 
definitions/systemvm64template-master-4.6.0'
+ '[' -t 2 ']'
+ echo '[2016-03-02 09:32:51] DEBUG: on_exit: rm -rf 
definitions/systemvm64template-master-4.6.0'
[2016-03-02 09:32:51] DEBUG: on_exit: rm -rf 
definitions/systemvm64template-master-4.6.0
+ eval rm -rf

[GitHub] cloudstack-docs-admin pull request: Be explicit in regards to Open...

2016-03-02 Thread ntavares

GitHub user ntavares opened a pull request:

https://github.com/apache/cloudstack-docs-admin/pull/35

Be explicit in regards to OpenSwan ipsec.secrets rule.

According to:
http://linux.die.net/man/5/ipsec.secrets

A preshared secret is most conveniently represented as a sequence of 
characters, delimited by the double-quote character ("). The sequence cannot 
contain a newline or double-quote.

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

$ git pull https://github.com/ntavares/cloudstack-docs-admin ipsec-psk-rules

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

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


commit 0ad528a99f001a1cfee770cabdd6394f0f689046
Author: Nuno Tavares 
Date:   2016-03-02T09:37:45Z

Be explicit in regards to OpenSwan ipsec.secrets rule.




---
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: PR validation using proposed CI.

2016-03-02 Thread Bharat Kumar

Hi Will,

I was not having  email access since few days, so could’ t  reply in time.

Yes, The idea is to run this on each PR.

Once i am done with this, it should be easy to replicate this locally if needed.

Thanks,
Bharat.

> On 27-Feb-2016, at 2:47 AM, Will Stevens  wrote:
> 
> I am also interested in setting this up locally.
> 
> Bharat, once you are happy with the state of this implementation, is the
> idea to set it up to run against every pull request branch submitted in
> github?   Or is there a different implementation in mind?
> 
> Thanks,
> 
> *Will STEVENS*
> Lead Developer
> 
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
> 
> On Fri, Feb 26, 2016 at 2:27 PM, Sebastien Goasguen 
> wrote:
> 
>> 
>>> On Feb 26, 2016, at 7:58 PM, Bharat Kumar 
>> wrote:
>>> 
>>> Hi ilya,
>>> 
>>> We use cloudstack marvin framework to run tests. All of the tests were
>> written in the community, you can take a look at them
>>> in the source (tests/integration)
>>> 
>> 
>> Bharat, Ilya is aware of Marvin and all the tests, I think his question is
>> more about the description of the actual CI environment, the hardware, the
>> triggers etc…did you write a wiki page for it ?
>> 
>>> Thanks,
>>> Bharat.
>>> 
 On 25-Feb-2016, at 11:45 PM, ilya  wrote:
 
 Bharat,
 
 Hope all is well,
 
 Perhaps you can explain the workflow and extensiveness of your tests.
 
 Thanks
 ilya
 
 
 
 On 2/24/16 9:23 PM, Bharat Kumar wrote:
> 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.
> 
>>> 
>> 
>> 




DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

Re: Bug on delete snapshot function / CLOUDSTACK-9297

2016-03-02 Thread Özhan Rüzgar Karaman

Hi Wei;
We will follow up the ticket with you and Mike's guidance.

Thanks
Özhan

On Wed, Mar 2, 2016 at 11:35 AM, Wei ZHOU  wrote:

> Hi Ozhan,
>
> please check the comments of the ticket.
>
> -Wei
>
> 2016-03-02 10:22 GMT+01:00 Özhan Rüzgar Karaman  >:
>
> > Hi;
> > 2 weeks ago we noticed a bug on delete snapshot function/api for ACS 4.8.
> > We have created a jira ticket for this bug.
> >
> > https://issues.apache.org/jira/browse/CLOUDSTACK-9297
> >
> > issue looks like its similar bug which was mentioned on CLOUDSTACK-8845 .
> > But because its on other function we have created new ticket.
> >
> > Our idea is we like to store vm snapshots as disk backup even if we
> delete
> > its original(referenced) vm. To achieve this we made a test and we took
> > some snapshots of vm and after deleting its originating, same vm we
> noticed
> > that if we try to delete its snapshot ACS throws exception like "Error
> > Message : Unable to determine the storage pool of the snapshot."
> >
> > We checked details from database and we noticed that issue is like
> > CLOUDSTACK-8845 and snapshot looses its reference vm id. There are more
> > rich details and test cases on jira ticket.
> >
> > Does anyone likes to take and work on this issue, if someone could
> supply a
> > fix, we could directly make tests on our working environment.
> >
> > Kindly Regards
> > Ozhan Ruzgar Karaman
> >
>

[GitHub] cloudstack pull request: ADD be explicit about the underlying limi...

2016-03-02 Thread ntavares

GitHub user ntavares opened a pull request:

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

ADD be explicit about the underlying limitation - OpenSwan

According to:
http://linux.die.net/man/5/ipsec.secrets

A preshared secret is most conveniently represented as a sequence of 
characters, delimited by the double-quote character ("). The sequence cannot 
contain a newline or double-quote.

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

$ git pull https://github.com/ntavares/cloudstack ipsec-psk-rules

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

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


commit 783aac8268398a68dd73d282893a4b517fce5666
Author: Nuno Tavares 
Date:   2016-03-02T10:11:34Z

ADD be explicit about the underlying limitation - OpenSwan




---
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-master-slowbuild #3367

2016-03-02 Thread 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.301s]
[INFO] Apache CloudStack . SUCCESS [2.701s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.794s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.831s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:32.565s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.120s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.689s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.472s]
[INFO] Apache CloudStack API . SUCCESS [1:50.743s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.653s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.842s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.095s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.012s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.877s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.185s]
[INFO] Apache CloudStack Agents .. SUCCESS [37.323s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.599s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.430s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:06.627s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.186s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.810s]
[INFO] Apache CloudStack Server .. SUCCESS [4:15.995s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.272s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.884s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.665s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.077s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.476s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.114s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [47.779s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [31.033s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.011s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [22.691s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.391s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.015s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.508s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.353s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.961s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.429s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.253s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.907s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.605s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.117s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.941s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.562s]
[INFO] Apache Cloud

[GitHub] cloudstack pull request: findbugs: new found old instance of DM_DE...

2016-03-02 Thread DaanHoogland

GitHub user DaanHoogland opened a pull request:

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

findbugs: new found old instance of DM_DEFAULT_ENCODING fixed

  this quick fix to silence the findbugs
   which seems to think this is a new issue

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

$ git pull https://github.com/DaanHoogland/cloudstack newFoundOldBug

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

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


commit c4a9ba1cda57bcd1aaea83c44ca39629d0aae21a
Author: Daan Hoogland 
Date:   2016-03-02T12:32:29Z

findbugs: new found old instance of DM_DEFAULT_ENCODING fixed

  this quick fix to silence the findbugs
   which seems to think this is a new issue




---
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: Important Pending Items

2016-03-02 Thread Will Stevens

Thanks Sanjeev, I did not realize that the whole simulator was tested.  Ok
that is good...  :)

*Will STEVENS*
Lead Developer

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

On Wed, Mar 2, 2016 at 12:15 AM, Sanjeev N  wrote:

> Hi Steve,
>
> Currently travis runs all simulator tests(marvin tests which does not
> require any hardware, tagged with requierd_hardware=false) on every PR. If
> any test fails it updates the PR and marks it red. IMO apart from 2 LGTMs
> travis test pass is also mandatory for PR merge.
>
> Thanks,
> Sanjeev N
> Chief Product Engineer@Accelerite
>
> On Wed, Mar 2, 2016 at 3:13 AM, Will Stevens 
> wrote:
>
> > Awesome, thanks Remi.  I will review this.
> >
> > *Will STEVENS*
> > Lead Developer
> >
> > *CloudOps* *| *Cloud Solutions Experts
> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > w cloudops.com *|* tw @CloudOps_
> >
> > On Tue, Mar 1, 2016 at 4:29 PM, Remi Bergsma <
> rberg...@schubergphilis.com>
> > wrote:
> >
> > > Hi Will,
> > >
> > > We used this to test hundreds of PRs:
> > > https://github.com/schubergphilis/MCT-shared/. I can talk you through
> it
> > > sometime next week or so if you want.
> > >
> > > Regards,
> > > Remi
> > >
> > >
> > > On 01/03/16 21:50, "williamstev...@gmail.com on behalf of Will
> Stevens"
> > <
> > > williamstev...@gmail.com on behalf of wstev...@cloudops.com> wrote:
> > >
> > > >Thanks Paul.  Great to hear you are planning to make everything
> > available
> > > >and you are willing to take contributions from the community.
> > > >
> > > >I am currently trying to get up to speed on everything that has been
> > done
> > > >and all the different pieces in play.  I would like to have a CI in
> > place
> > > >(even if it is only locally on my hardware) for testing PRs for 4.9.
> My
> > > >focus right now is solving the CI problem, so I am interested in any
> > > >developments on this front.
> > > >
> > > >We have Travis doing smoke tests on every PR right now.  Travis is
> free
> > > for
> > > >open source projects.  Is there a reason we are not doing more
> extensive
> > > >tests with Travis since it is already integrated into github?  Like
> > maybe
> > > >running the simulator on every PR?  I think this could be a good first
> > > step
> > > >to weed out some of the PRs that are likely to fail a full CI run.
> > > >
> > > >Cheers,
> > > >
> > > >*Will STEVENS*
> > > >Lead Developer
> > > >
> > > >*CloudOps* *| *Cloud Solutions Experts
> > > >420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > > >w cloudops.com *|* tw @CloudOps_
> > > >
> > > >On Tue, Mar 1, 2016 at 3:40 PM, Paul Angus 
> > > wrote:
> > > >
> > > >> Hi Will,
> > > >>
> > > >> It will be 100% open source. The $dayjob has blocked the team from
> > > working
> > > >> on it recently. I'd like to get some of our ideas into the
> CloudStack
> > > wiki
> > > >> this week before I go on leave for a week.
> > > >> Rohit has created a repo for us:
> > https://github.com/shapeblue/Trillian
> > > >> (which looks a bit sad at the moment - I hope to push our Ansible
> > roles
> > > >> for building mgmt. servers and Marvin boxes into it this week also)
> > > >>
> > > >> Internally we're planning a two week sprint on it starting 14th
> March.
> > > >> Having to dip in and out of this effort is making it very difficult
> to
> > > get
> > > >> anywhere
> > > >>
> > > >> I think the biggest part of the work will be to get Marvin up to
> > > scratch,
> > > >> the log output from the tests is pretty bad.
> > > >>
> > > >> We very much want this to be a community 'thing', and we're happy to
> > > work
> > > >> with everyone/anyone to get there.
> > > >>
> > > >> Any ideas on the most effective way to have a number of people on
> > this -
> > > >> I'm all ears.
> > > >> In the meantime I'll try to make good on my promises to get our
> ideas
> > > >> visible to everyone...
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> Paul Angus
> > > >> VP Technology   ,   ShapeBlue
> > > >>
> > > >>
> > > >> t:  @cloudyangus
> > > >>
> > > >> e:  paul.an...@shapeblue.com
> > > >> |  w:  www.shapeblue.com
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> -Original Message-
> > > >> From: williamstev...@gmail.com [mailto:williamstev...@gmail.com] On
> > > >> Behalf Of Will Stevens
> > > >> Sent: Monday, February 29, 2016 9:52 PM
> > > >> To: dev@cloudstack.apache.org
> > > >> Subject: Re: Important Pending Items
> > > >>
> > > >> @Paul and @Bharat, thank you for the quality write-ups on this
> topic.
> > > >>
> > > >> re:Paul's Details:
> > > >> I share a lot of your thoughts on this. The hypervisor in hypervisor
> > > setup
> > > >> with the ability to test multiple environments is also core to my
> > > thinking.
> > > >> I can't find any details on Trillian, other than what is in this
> > > thread. Is
> > > >> it open source and freely available? This

[GitHub] cloudstack pull request: CLOUDSTACK-9164: Prevent firefox's quick ...

2016-03-02 Thread footplus

Github user footplus commented on the pull request:

https://github.com/apache/cloudstack/pull/1271#issuecomment-191264802
  
Hello, I was able to confirm this patch works on CloudStack 4.8.0. The only 
thing is to take care of removing the systemvm-4.8.0.iso from the secondary 
storage, and destroy the consoleproxy VM. This will cause CloudStack to 
reprovision the ISO from the package, and then when the consoleproxy is back, 
this works.


---
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-master-slowbuild #3368

2016-03-02 Thread 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.742s]
[INFO] Apache CloudStack . SUCCESS [2.087s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.775s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.383s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.165s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.105s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.117s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [28.191s]
[INFO] Apache CloudStack API . SUCCESS [1:50.059s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [17.530s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.621s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.096s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.469s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.653s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.865s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.544s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [37.109s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.344s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.394s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.716s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [26.299s]
[INFO] Apache CloudStack Server .. SUCCESS [4:11.665s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [38.103s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.160s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.727s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.068s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.439s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.719s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.034s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [31.044s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [25.593s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [31.054s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [21.145s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.388s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.364s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.080s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.972s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.574s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.430s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[37.241s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.313s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.066s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.016s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.699s]
[INFO] Apache Cloud

4.9 Release Management

2016-03-02 Thread Will Stevens

Hello Everyone,
I have mentioned this in other related threads, but I wanted to make an
official thread on the topic.

I am nominating myself as the release manager for 4.9.  Please feel free to
discuss if you have comments or concerns.

I will not be working alone, I will be assisted by Koushik Das and Patrick
Dube.  I will be running point, but all three of us will be working
together as a unit for this release.

Our main focus for this release is the integration of hardware Continuous
Integration (CI) into the PR flow.  Koushik and his team will be setting up
a CI environment which will be used for testing PRs and I will also be
setting up a CI environment for testing PRs.

The details of the CI integration will be handled publicly, but we will
likely have to work with a minimum viable implementation initially and move
forward from there.  Here are some of the key aspects of the CI which are
top of mind for me.

- Standardize a feedback mechanism to post the result of CI runs back to
the relevant PR.  I believe the best way to do this would be to post a
summary of the CI run in the PR thread on Github.  With the existing
integration, this will then get pushed to the mailing list (since all
comments on a PR are pushed to the mailing list).
- Ideally, we will also make the CI logs available for the run.  We are
still working out the details of how we do this, but we will likely be
pushing the logs to an object store with a cleanup window to remove the
logs after a set period of time (probably a week).  This should give people
the opportunity to pull the logs if they are interested in the test
results, but will reduce the need for ever growing storage.
- In order to parallelize the CI operations, we will not be automatically
kicking off a CI run for every PR for now.  Instead, we will communicate
between us and each run distinct PRs so we can maximize the utilization of
our hardware.

Some longer term goals of the CI in my mind are as follows:

- I would like the core CI framework to be easily distributed and
accessible to anyone who has hardware available.  This would enable anyone
to setup a CI on their hardware and it would automatically be hooked up to
feedback the results to the Github PRs.  I feel this is very important long
term because every individual or organization depends on a different
configuration and hardware setup, so it empowers them to validate their own
use case while adding value back to the community.

Additional details will follow, namely the release schedule etc.

Please contribute your ideas and feedback.

Cheers,

Will

[GitHub] cloudstack pull request: [CLOUDSTACK-8973] Fix create template fro...

2016-03-02 Thread syed

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

https://github.com/apache/cloudstack/pull/1424#discussion_r54762197
  
--- Diff: server/src/com/cloud/api/ApiResponseHelper.java ---
@@ -1388,7 +1388,7 @@ public TemplateResponse 
createTemplateUpdateResponse(ResponseView view, VirtualM
 @Override
 public List createTemplateResponses(ResponseView 
view, VirtualMachineTemplate result, Long zoneId, boolean readyOnly) {
 List tvo = null;
-if (zoneId == null || zoneId == -1) {
+if (zoneId == null || zoneId == -1 || result.isCrossZones()) {
--- End diff --

Sure, Added tests now. 


---
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-8973] Fix create template fro...

2016-03-02 Thread syed

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

https://github.com/apache/cloudstack/pull/1424#discussion_r54762401
  
--- Diff: server/src/com/cloud/template/TemplateManagerImpl.java ---
@@ -275,6 +277,8 @@
 private StorageCacheManager cacheMgr;
 @Inject
 private EndPointSelector selector;
+@Inject
+private ImageStoreDao _imgStoreDao;
--- End diff --

So all other "Dao" variables in the class have a "_" before their name. I 
tried to keep it that way to follow convention. I've moved my variable to the 
same group where the other Dao variables are defiend, it should be more 
consistent now. 


---
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-master-slowbuild #3369

2016-03-02 Thread 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.927s]
[INFO] Apache CloudStack . SUCCESS [2.201s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.766s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.044s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:31.818s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.102s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.534s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.702s]
[INFO] Apache CloudStack API . SUCCESS [1:49.179s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [17.538s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.179s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.114s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.251s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.900s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.559s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.371s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.702s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.177s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:08.206s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [41.007s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.270s]
[INFO] Apache CloudStack Server .. SUCCESS [4:13.484s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [38.101s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.436s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.290s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.068s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.448s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.633s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.234s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.042s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.820s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.986s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.703s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.190s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.434s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.002s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.968s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.554s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.386s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[37.655s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.959s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.234s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [17.183s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.508s]
[INFO] Apache Cloud

Fwd: Build failed in Jenkins: build-master-slowbuild #3368

2016-03-02 Thread Daan Hoogland

People, these were irritating me. I wrote a quick fix [1].

Anyone feels like running a test on it?

[1] https://github.com/apache/cloudstack/pull/1427

-- Forwarded message --
From: 
Date: Wed, Mar 2, 2016 at 4:09 PM
Subject: Build failed in Jenkins: build-master-slowbuild #3368
To: dev@cloudstack.apache.org, nicolas.m.vazq...@gmail.com,
priti.sa...@clogeny.com, nitin.mahar...@gmail.com, nicovazque...@gmail.com

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 <
http://jenkins.buildacloud.org/job/build-master-slowbuild/ws/quickcloud/src/test/resources
>
[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.742s]
[INFO] Apache CloudStack . SUCCESS [2.087s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.775s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.383s]
[INFO] Apache CloudStack Utils ... SUCCESS
[1:30.165s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.105s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.117s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [28.191s]
[INFO] Apache CloudStack API . SUCCESS
[1:50.059s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [17.530s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.621s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.096s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.469s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.653s]
[INFO] Apache CloudStack Core  SUCCESS
[1:21.865s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.544s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [37.109s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.344s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS
[2:07.394s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.716s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS
[26.299s]
[INFO] Apache CloudStack Server .. SUCCESS
[4:11.665s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [38.103s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.160s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS
[1:21.727s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.068s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.439s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.719s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.034s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [31.044s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [25.593s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS
[31.054s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [21.145s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS
[35.388s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.364s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.080s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.972s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.574s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS
[23.430s]
[INFO] Ap

RE: Build failed in Jenkins: build-master-slowbuild #3368

2016-03-02 Thread Raja Pullela

Daan, I will try to test this out.. 

-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] 
Sent: Wednesday, March 2, 2016 11:57 PM
To: dev 
Subject: Fwd: Build failed in Jenkins: build-master-slowbuild #3368

People, these were irritating me. I wrote a quick fix [1].

Anyone feels like running a test on it?

[1] https://github.com/apache/cloudstack/pull/1427

-- Forwarded message --
From: 
Date: Wed, Mar 2, 2016 at 4:09 PM
Subject: Build failed in Jenkins: build-master-slowbuild #3368
To: dev@cloudstack.apache.org, nicolas.m.vazq...@gmail.com, 
priti.sa...@clogeny.com, nitin.mahar...@gmail.com, nicovazque...@gmail.com

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 < 
http://jenkins.buildacloud.org/job/build-master-slowbuild/ws/quickcloud/src/test/resources
>
[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.742s] [INFO] Apache CloudStack . SUCCESS 
[2.087s] [INFO] Apache CloudStack Maven Conventions Parent  SUCCESS 
[0.775s] [INFO] Apache CloudStack Framework - Managed Context . SUCCESS 
[19.383s] [INFO] Apache CloudStack Utils ... SUCCESS 
[1:30.165s] [INFO] Apache CloudStack Framework ... SUCCESS 
[0.105s] [INFO] Apache CloudStack Framework - Event Notification .. SUCCESS 
[54.117s] [INFO] Apache CloudStack Framework - Configuration ... SUCCESS 
[28.191s] [INFO] Apache CloudStack API . SUCCESS 
[1:50.059s] [INFO] Apache CloudStack Framework - REST  SUCCESS 
[17.530s] [INFO] Apache CloudStack Framework - IPC . SUCCESS 
[29.621s] [INFO] Apache CloudStack Cloud Engine  SUCCESS 
[0.096s] [INFO] Apache CloudStack Cloud Engine API  SUCCESS 
[28.469s] [INFO] Apache CloudStack Framework - Security  SUCCESS 
[24.653s] [INFO] Apache CloudStack Core  SUCCESS 
[1:21.865s] [INFO] Apache CloudStack Agents .. SUCCESS 
[36.544s] [INFO] Apache CloudStack Framework - Clustering .. SUCCESS 
[37.109s] [INFO] Apache CloudStack Framework - Event Notification .. SUCCESS 
[14.344s] [INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS 
[2:07.394s] [INFO] Apache CloudStack Framework - Jobs  SUCCESS 
[40.716s] [INFO] Apache CloudStack Cloud Engine Internal Components API  
SUCCESS [26.299s] [INFO] Apache CloudStack Server .. 
SUCCESS [4:11.665s] [INFO] Apache CloudStack Framework - Quota ... 
SUCCESS [38.103s] [INFO] Apache CloudStack Usage Server  
SUCCESS [44.160s] [INFO] Apache CloudStack Cloud Engine Orchestration Component 
 SUCCESS [1:21.727s] [INFO] Apache CloudStack Cloud Services .. 
SUCCESS [0.068s] [INFO] Apache CloudStack Secondary Storage ... 
SUCCESS [0.439s] [INFO] Apache CloudStack Secondary Storage Service ... 
SUCCESS [54.719s] [INFO] Apache CloudStack Engine Storage Component  
SUCCESS [48.034s] [INFO] Apache CloudStack Engine Storage Volume Component . 
SUCCESS [31.044s] [INFO] Apache CloudStack Engine Storage Image Component .. 
SUCCESS [25.593s] [INFO] Apache CloudStack Engine Storage Data Motion Component 
 SUCCESS [31.054s] [INFO] Apache CloudStack Engine Storage Cache Component .. 
SUCCESS [21.145s] [INFO] Apache CloudStack Engine Storage Snapshot Component  
SUCCESS [35.388s] [INFO] Apache CloudStack Cloud Engine API  
SUCCESS [12.364s] [INFO] Apache CloudStack Cloud Engine

Re: Build failed in Jenkins: build-master-slowbuild #3368

2016-03-02 Thread Daan Hoogland

thanks Raja

On Wed, Mar 2, 2016 at 7:48 PM, Raja Pullela 
wrote:

> Daan, I will try to test this out..
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Wednesday, March 2, 2016 11:57 PM
> To: dev 
> Subject: Fwd: Build failed in Jenkins: build-master-slowbuild #3368
>
> People, these were irritating me. I wrote a quick fix [1].
>
> Anyone feels like running a test on it?
>
> [1] https://github.com/apache/cloudstack/pull/1427
>
> -- Forwarded message --
> From: 
> Date: Wed, Mar 2, 2016 at 4:09 PM
> Subject: Build failed in Jenkins: build-master-slowbuild #3368
> To: dev@cloudstack.apache.org, nicolas.m.vazq...@gmail.com,
> priti.sa...@clogeny.com, nitin.mahar...@gmail.com, nicovazque...@gmail.com
>
>
> 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 <
> http://jenkins.buildacloud.org/job/build-master-slowbuild/ws/quickcloud/src/test/resources
> >
> [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.742s] [INFO] Apache CloudStack .
> SUCCESS [2.087s] [INFO] Apache CloudStack Maven Conventions Parent 
> SUCCESS [0.775s] [INFO] Apache CloudStack Framework - Managed Context .
> SUCCESS [19.383s] [INFO] Apache CloudStack Utils
> ... SUCCESS [1:30.165s] [INFO] Apache CloudStack
> Framework ... SUCCESS [0.105s] [INFO] Apache CloudStack
> Framework - Event Notification .. SUCCESS [54.117s] [INFO] Apache
> CloudStack Framework - Configuration ... SUCCESS [28.191s] [INFO]
> Apache CloudStack API . SUCCESS [1:50.059s]
> [INFO] Apache CloudStack Framework - REST  SUCCESS
> [17.530s] [INFO] Apache CloudStack Framework - IPC .
> SUCCESS [29.621s] [INFO] Apache CloudStack Cloud Engine
>  SUCCESS [0.096s] [INFO] Apache CloudStack Cloud Engine
> API  SUCCESS [28.469s] [INFO] Apache CloudStack Framework -
> Security  SUCCESS [24.653s] [INFO] Apache CloudStack Core
>  SUCCESS [1:21.865s] [INFO] Apache CloudStack
> Agents .. SUCCESS [36.544s] [INFO] Apache
> CloudStack Framework - Clustering .. SUCCESS [37.109s] [INFO]
> Apache CloudStack Framework - Event Notification .. SUCCESS [14.344s]
> [INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS
> [2:07.394s] [INFO] Apache CloudStack Framework - Jobs 
> SUCCESS [40.716s] [INFO] Apache CloudStack Cloud Engine Internal Components
> API  SUCCESS [26.299s] [INFO] Apache CloudStack Server
> .. SUCCESS [4:11.665s] [INFO] Apache CloudStack
> Framework - Quota ... SUCCESS [38.103s] [INFO] Apache
> CloudStack Usage Server  SUCCESS [44.160s] [INFO]
> Apache CloudStack Cloud Engine Orchestration Component  SUCCESS [1:21.727s]
> [INFO] Apache CloudStack Cloud Services .. SUCCESS [0.068s]
> [INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.439s]
> [INFO] Apache CloudStack Secondary Storage Service ... SUCCESS
> [54.719s] [INFO] Apache CloudStack Engine Storage Component 
> SUCCESS [48.034s] [INFO] Apache CloudStack Engine Storage Volume Component
> . SUCCESS [31.044s] [INFO] Apache CloudStack Engine Storage Image Component
> .. SUCCESS [25.593s] [INFO] Apache CloudStack Engine Storage Data Motion
> Component  SUCCESS [31.054s] [INFO] Apache CloudStack Engine Storage Cache
> Component .. SUCCESS [21.145s] [INF

[GitHub] cloudstack pull request: findbugs: new found old instance of DM_DE...

2016-03-02 Thread swill

Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1427#issuecomment-191389512
  
It looks like your IDE had a field day with this class.  So other than the 
reordering of imports, adding `final` to a ton of variables and removing some 
unneeded brackets, this is really the only change?  Right?

`
-String dir = UUID.nameUUIDFromBytes(nfsPath.getBytes()).toString();
+final String dir = 
UUID.nameUUIDFromBytes(nfsPath.getBytes(getPreferredCharset())).toString();
`


---
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-9298: Improve performance of r...

2016-03-02 Thread nvazquez

Github user nvazquez commented on the pull request:

https://github.com/apache/cloudstack/pull/1425#issuecomment-191393797
  
@rafaelweingartner @pedro-martins thanks for your comments! I deleted the 
constructor and used setters instead and not included the Builder pattern, but 
if you want I can include it.
I also included unit tests for new methods.


---
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.9 Release Management

2016-03-02 Thread Samir Agarwal

Kudos Will!

I had received many private notes wondering if Accelerite will continue to play 
a strong role in contributions to the community; here is your proof!

We wanted to take on the biggest pain points in the community, and see how we 
can make positive contributions. Koushik Das will work alongside Will and 
Patrick to address both of these problem areas. I believe that this will put 
the community on a path to more manageable releases going forward.

Best

Samir




-Original Message-
From: Will Stevens [mailto:williamstev...@gmail.com] 
Sent: Wednesday, March 02, 2016 9:15 AM
To: dev@cloudstack.apache.org
Subject: 4.9 Release Management

Hello Everyone,
I have mentioned this in other related threads, but I wanted to make an 
official thread on the topic.

I am nominating myself as the release manager for 4.9.  Please feel free to 
discuss if you have comments or concerns.

I will not be working alone, I will be assisted by Koushik Das and Patrick 
Dube.  I will be running point, but all three of us will be working together as 
a unit for this release.

Our main focus for this release is the integration of hardware Continuous 
Integration (CI) into the PR flow.  Koushik and his team will be setting up a 
CI environment which will be used for testing PRs and I will also be setting up 
a CI environment for testing PRs.

The details of the CI integration will be handled publicly, but we will likely 
have to work with a minimum viable implementation initially and move forward 
from there.  Here are some of the key aspects of the CI which are top of mind 
for me.

- Standardize a feedback mechanism to post the result of CI runs back to the 
relevant PR.  I believe the best way to do this would be to post a summary of 
the CI run in the PR thread on Github.  With the existing integration, this 
will then get pushed to the mailing list (since all comments on a PR are pushed 
to the mailing list).
- Ideally, we will also make the CI logs available for the run.  We are still 
working out the details of how we do this, but we will likely be pushing the 
logs to an object store with a cleanup window to remove the logs after a set 
period of time (probably a week).  This should give people the opportunity to 
pull the logs if they are interested in the test results, but will reduce the 
need for ever growing storage.
- In order to parallelize the CI operations, we will not be automatically 
kicking off a CI run for every PR for now.  Instead, we will communicate 
between us and each run distinct PRs so we can maximize the utilization of our 
hardware.

Some longer term goals of the CI in my mind are as follows:

- I would like the core CI framework to be easily distributed and accessible to 
anyone who has hardware available.  This would enable anyone to setup a CI on 
their hardware and it would automatically be hooked up to feedback the results 
to the Github PRs.  I feel this is very important long term because every 
individual or organization depends on a different configuration and hardware 
setup, so it empowers them to validate their own use case while adding value 
back to the community.

Additional details will follow, namely the release schedule etc.

Please contribute your ideas and feedback.

Cheers,

Will



DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

RE: 4.9 Release Management

2016-03-02 Thread Paul Angus

Thanks for taking up the baton Will et al.

Just for clarity - given that getting CI 'done' will take some time (mainly 
because of the state of the Marvin Tests and Marvin output) - are 'we' now 
dropping the monthly releases?


[ShapeBlue]
Paul Angus
VP Technology   ,   ShapeBlue


d:  +44 203 617 0528 | s: +44 203 603 
0540 |  
m:  +44 7711 418784

e:  paul.an...@shapeblue.com | t: 
@cloudyangus  |
  w:  www.shapeblue.com

a:  53 Chandos Place, Covent Garden London WC2N 4HS UK


[cid:image1c9d01.png@0dd3a650.4f94077d]


Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services 
India LLP is a company incorporated in India and is operated under license from 
Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in 
Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd 
is a company registered by The Republic of South Africa and is traded under 
license from Shape Blue Ltd. ShapeBlue is a registered trademark.
This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error.




-Original Message-
From: Will Stevens [mailto:williamstev...@gmail.com]
Sent: 02 March 2016 17:15
To: dev@cloudstack.apache.org
Subject: 4.9 Release Management

Hello Everyone,
I have mentioned this in other related threads, but I wanted to make an 
official thread on the topic.

I am nominating myself as the release manager for 4.9. Please feel free to 
discuss if you have comments or concerns.

I will not be working alone, I will be assisted by Koushik Das and Patrick 
Dube. I will be running point, but all three of us will be working together as 
a unit for this release.

Our main focus for this release is the integration of hardware Continuous 
Integration (CI) into the PR flow. Koushik and his team will be setting up a CI 
environment which will be used for testing PRs and I will also be setting up a 
CI environment for testing PRs.

The details of the CI integration will be handled publicly, but we will likely 
have to work with a minimum viable implementation initially and move forward 
from there. Here are some of the key aspects of the CI which are top of mind 
for me.

- Standardize a feedback mechanism to post the result of CI runs back to the 
relevant PR. I believe the best way to do this would be to post a summary of 
the CI run in the PR thread on Github. With the existing integration, this will 
then get pushed to the mailing list (since all comments on a PR are pushed to 
the mailing list).
- Ideally, we will also make the CI logs available for the run. We are still 
working out the details of how we do this, but we will likely be pushing the 
logs to an object store with a cleanup window to remove the logs after a set 
period of time (probably a week). This should give people the opportunity to 
pull the logs if they are interested in the test results, but will reduce the 
need for ever growing storage.
- In order to parallelize the CI operations, we will not be automatically 
kicking off a CI run for every PR for now. Instead, we will communicate between 
us and each run distinct PRs so we can maximize the utilization of our hardware.

Some longer term goals of the CI in my mind are as follows:

- I would like the core CI framework to be easily distributed and accessible to 
anyone who has hardware available. This would enable anyone to setup a CI on 
their hardware and it would automatically be hooked up to feedback the results 
to the Github PRs. I feel this is very important long term because every 
individual or organization depends on a different configuration and hardware 
setup, so it empowers them to validate their own use case while adding value 
back to the community.

Additional details will follow, namely the release schedule etc.

Please contribute your ideas and feedback.

Cheers,

Will
Find out more about ShapeBlue and our range of CloudStack related services:
IaaS Cloud Design & Build | 
CSForge – rapid IaaS deployment framework
CloudStack Consulting | 
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support | CloudStack 
Bootcamp Training Courses

[GitHub] cloudstack pull request: findbugs: new found old instance of DM_DE...

2016-03-02 Thread DaanHoogland

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1427#issuecomment-19145
  
:) @swill it is the only part I typed


---
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.9 Release Management

2016-03-02 Thread Will Stevens

I don't think I can answer that at this time.  My personal opinion is that
CI is more important than the release timeline, but others may not share
this opinion (as it is only my opinion).   I am full steam ahead trying to
review what we have in place and the work that different parties have done
on CI to date.  I am hoping to have a CI implementation setup in my
environment soon, which will enable me to better assess the current state
of affairs.

There are a lot of moving parts involved and I will be the first to admit
that I don't have a firm grasp on everything yet, so reviewing our Marvin
test coverage and output is something I have not yet had a chance to tackle.

Does that answer your question well enough?  :)

*Will STEVENS*
Lead Developer

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

On Wed, Mar 2, 2016 at 12:25 PM, Paul Angus 
wrote:

> Thanks for taking up the baton Will et al.
>
> Just for clarity - given that getting CI 'done' will take some time
> (mainly because of the state of the Marvin Tests and Marvin output) - are
> 'we' now dropping the monthly releases?
>
>
> [image: ShapeBlue] 
> Paul Angus
> VP Technology ,  ShapeBlue
> d:  *+44 203 617 0528 | s: +44 203 603 0540*
> <+44%20203%20617%200528%20%7C%20s:%20+44%20203%20603%200540>  |  m:
> *+44 7711 418784* <+44%207711%20418784>
> e:  *paul.an...@shapeblue.com | t: @cloudyangus*
>   |  w:
> *www.shapeblue.com* 
> a:  53 Chandos Place, Covent Garden London WC2N 4HS UK
> Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue
> Services India LLP is a company incorporated in India and is operated under
> license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> company incorporated in Brasil and is operated under license from Shape
> Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of
> South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is
> a registered trademark.
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error.
>
>
> -Original Message-
> From: Will Stevens [mailto:williamstev...@gmail.com]
> Sent: 02 March 2016 17:15
> To: dev@cloudstack.apache.org
> Subject: 4.9 Release Management
>
> Hello Everyone,
> I have mentioned this in other related threads, but I wanted to make an
> official thread on the topic.
>
> I am nominating myself as the release manager for 4.9. Please feel free to
> discuss if you have comments or concerns.
>
> I will not be working alone, I will be assisted by Koushik Das and Patrick
> Dube. I will be running point, but all three of us will be working together
> as a unit for this release.
>
> Our main focus for this release is the integration of hardware Continuous
> Integration (CI) into the PR flow. Koushik and his team will be setting up
> a CI environment which will be used for testing PRs and I will also be
> setting up a CI environment for testing PRs.
>
> The details of the CI integration will be handled publicly, but we will
> likely have to work with a minimum viable implementation initially and move
> forward from there. Here are some of the key aspects of the CI which are
> top of mind for me.
>
> - Standardize a feedback mechanism to post the result of CI runs back to
> the relevant PR. I believe the best way to do this would be to post a
> summary of the CI run in the PR thread on Github. With the existing
> integration, this will then get pushed to the mailing list (since all
> comments on a PR are pushed to the mailing list).
> - Ideally, we will also make the CI logs available for the run. We are
> still working out the details of how we do this, but we will likely be
> pushing the logs to an object store with a cleanup window to remove the
> logs after a set period of time (probably a week). This should give people
> the opportunity to pull the logs if they are interested in the test
> results, but will reduce the need for ever growing storage.
> - In order to parallelize the CI operations, we will not be automatically
> kicking off a CI run for every PR for now. Instead, we will communicate
> between us and each run distinct PRs so we can maximize the utilization of
> our hardware.
>
> Some longer term goals of the CI in my mind are as follows:
>
> - I would like the core CI framework to be easily distributed and
> accessible to anyone who has hardware available. This would enable anyone
> to setup a CI on their hardware and it would automa

[GitHub] cloudstack pull request: findbugs: new found old instance of DM_DE...

2016-03-02 Thread swill

Github user swill commented on the pull request:

https://github.com/apache/cloudstack/pull/1427#issuecomment-191424588
  
Haha.  Fair enough.  I will let Raja test, but otherwise it 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.
---

Re: 4.9 Release Management

2016-03-02 Thread Paul Angus

That's good enough for me (tm). you're figuring out what you need to figure 
out. I know the feeling. :)

We probably need to have a concensus around release cadence and stick to it for 
a while. Otherwise we're going to lose some credibility as project.





From: Will Stevens 
Sent: 2 Mar 2016 20:46
To: dev@cloudstack.apache.org
Subject: Re: 4.9 Release Management

I don't think I can answer that at this time.  My personal opinion is that
CI is more important than the release timeline, but others may not share
this opinion (as it is only my opinion).   I am full steam ahead trying to
review what we have in place and the work that different parties have done
on CI to date.  I am hoping to have a CI implementation setup in my
environment soon, which will enable me to better assess the current state
of affairs.

There are a lot of moving parts involved and I will be the first to admit
that I don't have a firm grasp on everything yet, so reviewing our Marvin
test coverage and output is something I have not yet had a chance to tackle.

Does that answer your question well enough?  :)

*Will STEVENS*
Lead Developer

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

On Wed, Mar 2, 2016 at 12:25 PM, Paul Angus 
wrote:

> Thanks for taking up the baton Will et al.
>
> Just for clarity - given that getting CI 'done' will take some time
> (mainly because of the state of the Marvin Tests and Marvin output) - are
> 'we' now dropping the monthly releases?
>
>
> [image: ShapeBlue] 
> Paul Angus
> VP Technology ,  ShapeBlue
> d:  *+44 203 617 0528 | s: +44 203 603 0540*
> <+44%20203%20617%200528%20%7C%20s:%20+44%20203%20603%200540>  |  m:
> *+44 7711 418784* <+44%207711%20418784>
> e:  *paul.an...@shapeblue.com | t: @cloudyangus*
>   |  w:
> *www.shapeblue.com* 
> a:  53 Chandos Place, Covent Garden London WC2N 4HS UK
> Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue
> Services India LLP is a company incorporated in India and is operated under
> license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> company incorporated in Brasil and is operated under license from Shape
> Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of
> South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is
> a registered trademark.
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error.
>
>
>


Paul Angus
VP Technology   ,   ShapeBlue


t:  @cloudyangus

e:  paul.an...@shapeblue.com|  
w:  www.shapeblue.com





-Original Message-
> From: Will Stevens [mailto:williamstev...@gmail.com]
> Sent: 02 March 2016 17:15
> To: dev@cloudstack.apache.org
> Subject: 4.9 Release Management
>
> Hello Everyone,
> I have mentioned this in other related threads, but I wanted to make an
> official thread on the topic.
>
> I am nominating myself as the release manager for 4.9. Please feel free to
> discuss if you have comments or concerns.
>
> I will not be working alone, I will be assisted by Koushik Das and Patrick
> Dube. I will be running point, but all three of us will be working together
> as a unit for this release.
>
> Our main focus for this release is the integration of hardware Continuous
> Integration (CI) into the PR flow. Koushik and his team will be setting up
> a CI environment which will be used for testing PRs and I will also be
> setting up a CI environment for testing PRs.
>
> The details of the CI integration will be handled publicly, but we will
> likely have to work with a minimum viable implementation initially and move
> forward from there. Here are some of the key aspects of the CI which are
> top of mind for me.
>
> - Standardize a feedback mechanism to post the result of CI runs back to
> the relevant PR. I believe the best way to do this would be to post a
> summary of the CI run in the PR thread on Github. With the existing
> integration, this will then get pushed to the mailing list (since all
> comments on a PR are pushed to the mailing list).
> - Ideally, we will also make the CI logs available for the run. We are
> still working out the details of how we do this, but we will likely be
> pushing the logs to an object store with a cleanup window to remove the
> logs after a set period of time (probably a week). This should give people
> the opportunity to pull the logs if they are interested i

Re: 4.9 Release Management

2016-03-02 Thread Simon Weller

Will,

You have our support!

Let us know what we can do to help.

- Si


From: Paul Angus 
Sent: Wednesday, March 2, 2016 3:09 PM
To: dev@cloudstack.apache.org
Subject: Re: 4.9 Release Management

That's good enough for me (tm). you're figuring out what you need to figure 
out. I know the feeling. :)

We probably need to have a concensus around release cadence and stick to it for 
a while. Otherwise we're going to lose some credibility as project.





From: Will Stevens 
Sent: 2 Mar 2016 20:46
To: dev@cloudstack.apache.org
Subject: Re: 4.9 Release Management

I don't think I can answer that at this time.  My personal opinion is that
CI is more important than the release timeline, but others may not share
this opinion (as it is only my opinion).   I am full steam ahead trying to
review what we have in place and the work that different parties have done
on CI to date.  I am hoping to have a CI implementation setup in my
environment soon, which will enable me to better assess the current state
of affairs.

There are a lot of moving parts involved and I will be the first to admit
that I don't have a firm grasp on everything yet, so reviewing our Marvin
test coverage and output is something I have not yet had a chance to tackle.

Does that answer your question well enough?  :)

*Will STEVENS*
Lead Developer

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

On Wed, Mar 2, 2016 at 12:25 PM, Paul Angus 
wrote:

> Thanks for taking up the baton Will et al.
>
> Just for clarity - given that getting CI 'done' will take some time
> (mainly because of the state of the Marvin Tests and Marvin output) - are
> 'we' now dropping the monthly releases?
>
>
> [image: ShapeBlue] 
> Paul Angus
> VP Technology ,  ShapeBlue
> d:  *+44 203 617 0528 | s: +44 203 603 0540*
> <+44%20203%20617%200528%20%7C%20s:%20+44%20203%20603%200540>  |  m:
> *+44 7711 418784* <+44%207711%20418784>
> e:  *paul.an...@shapeblue.com | t: @cloudyangus*
>   |  w:
> *www.shapeblue.com* 
> a:  53 Chandos Place, Covent Garden London WC2N 4HS UK
> Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue
> Services India LLP is a company incorporated in India and is operated under
> license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> company incorporated in Brasil and is operated under license from Shape
> Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of
> South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is
> a registered trademark.
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error.
>
>
>


Paul Angus
VP Technology   ,   ShapeBlue


t:  @cloudyangus

e:  paul.an...@shapeblue.com|  
w:  www.shapeblue.com





-Original Message-
> From: Will Stevens [mailto:williamstev...@gmail.com]
> Sent: 02 March 2016 17:15
> To: dev@cloudstack.apache.org
> Subject: 4.9 Release Management
>
> Hello Everyone,
> I have mentioned this in other related threads, but I wanted to make an
> official thread on the topic.
>
> I am nominating myself as the release manager for 4.9. Please feel free to
> discuss if you have comments or concerns.
>
> I will not be working alone, I will be assisted by Koushik Das and Patrick
> Dube. I will be running point, but all three of us will be working together
> as a unit for this release.
>
> Our main focus for this release is the integration of hardware Continuous
> Integration (CI) into the PR flow. Koushik and his team will be setting up
> a CI environment which will be used for testing PRs and I will also be
> setting up a CI environment for testing PRs.
>
> The details of the CI integration will be handled publicly, but we will
> likely have to work with a minimum viable implementation initially and move
> forward from there. Here are some of the key aspects of the CI which are
> top of mind for me.
>
> - Standardize a feedback mechanism to post the result of CI runs back to
> the relevant PR. I believe the best way to do this would be to post a
> summary of the CI run in the PR thread on Github. With the existing
> integration, this will then get pushed to the mailing list (since all
> comments on a PR are pushed to the mailing list).
> - Ideally, we will also make the CI logs available for the run. We are
> still working out the details of how we do

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

2016-03-02 Thread 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.021s]
[INFO] Apache CloudStack . SUCCESS [2.336s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [1.006s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [18.898s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.597s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.109s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.053s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.072s]
[INFO] Apache CloudStack API . SUCCESS [1:51.879s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.242s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.084s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.088s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.630s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [26.430s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.583s]
[INFO] Apache CloudStack Agents .. SUCCESS [35.960s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [37.288s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.333s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.687s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [41.049s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.853s]
[INFO] Apache CloudStack Server .. SUCCESS [4:18.328s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.520s]
[INFO] Apache CloudStack Usage Server  SUCCESS [43.174s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.410s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.074s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.426s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.859s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.155s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.067s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [25.981s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [30.606s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.572s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.326s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.149s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.910s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.950s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.612s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.900s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.201s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.179s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.171s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [14.816s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.705s]
[INFO] Apache Cloud

Re: 4.9 Release Management

2016-03-02 Thread Will Stevens

Yes, I understand and agree with you.  On the flip side, the lack of CI has
been a thorn in our side for a long time and the increased cadence only
adds to this problem, so I am trying to walk a thin line here.

Personally, if CI is the only thing I can contribute to ACS as the 4.9 RM,
I will be happy with that.  It is a problem that has to be solved and
someone has to own it.

*Will STEVENS*
Lead Developer

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

On Wed, Mar 2, 2016 at 4:09 PM, Paul Angus  wrote:

> That's good enough for me (tm). you're figuring out what you need to
> figure out. I know the feeling. :)
>
> We probably need to have a concensus around release cadence and stick to
> it for a while. Otherwise we're going to lose some credibility as project.
>
>
>
>
>
> From: Will Stevens 
> Sent: 2 Mar 2016 20:46
> To: dev@cloudstack.apache.org
> Subject: Re: 4.9 Release Management
>
> I don't think I can answer that at this time.  My personal opinion is that
> CI is more important than the release timeline, but others may not share
> this opinion (as it is only my opinion).   I am full steam ahead trying to
> review what we have in place and the work that different parties have done
> on CI to date.  I am hoping to have a CI implementation setup in my
> environment soon, which will enable me to better assess the current state
> of affairs.
>
> There are a lot of moving parts involved and I will be the first to admit
> that I don't have a firm grasp on everything yet, so reviewing our Marvin
> test coverage and output is something I have not yet had a chance to
> tackle.
>
> Does that answer your question well enough?  :)
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Wed, Mar 2, 2016 at 12:25 PM, Paul Angus 
> wrote:
>
> > Thanks for taking up the baton Will et al.
> >
> > Just for clarity - given that getting CI 'done' will take some time
> > (mainly because of the state of the Marvin Tests and Marvin output) - are
> > 'we' now dropping the monthly releases?
> >
> >
> > [image: ShapeBlue] 
> > Paul Angus
> > VP Technology ,  ShapeBlue
> > d:  *+44 203 617 0528 | s: +44 203 603 0540*
> > <+44%20203%20617%200528%20%7C%20s:%20+44%20203%20603%200540>  |  m:
> > *+44 7711 418784* <+44%207711%20418784>
> > e:  *paul.an...@shapeblue.com | t: @cloudyangus*
> >   |  w:
> > *www.shapeblue.com* 
> > a:  53 Chandos Place, Covent Garden London WC2N 4HS UK
> > Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue
> > Services India LLP is a company incorporated in India and is operated
> under
> > license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> > company incorporated in Brasil and is operated under license from Shape
> > Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of
> > South Africa and is traded under license from Shape Blue Ltd. ShapeBlue
> is
> > a registered trademark.
> > This email and any attachments to it may be confidential and are intended
> > solely for the use of the individual to whom it is addressed. Any views
> or
> > opinions expressed are solely those of the author and do not necessarily
> > represent those of Shape Blue Ltd or related companies. If you are not
> the
> > intended recipient of this email, you must neither take any action based
> > upon its contents, nor copy or show it to anyone. Please contact the
> sender
> > if you believe you have received this email in error.
> >
> >
> >
>
>
> Paul Angus
> VP Technology   ,   ShapeBlue
>
>
> t:  @cloudyangus
>
> e:  paul.an...@shapeblue.com
> |  w:  www.shapeblue.com
>
>
>
>
>
> -Original Message-
> > From: Will Stevens [mailto:williamstev...@gmail.com]
> > Sent: 02 March 2016 17:15
> > To: dev@cloudstack.apache.org
> > Subject: 4.9 Release Management
> >
> > Hello Everyone,
> > I have mentioned this in other related threads, but I wanted to make an
> > official thread on the topic.
> >
> > I am nominating myself as the release manager for 4.9. Please feel free
> to
> > discuss if you have comments or concerns.
> >
> > I will not be working alone, I will be assisted by Koushik Das and
> Patrick
> > Dube. I will be running point, but all three of us will be working
> together
> > as a unit for this release.
> >
> > Our main focus for this release is the integration of hardware Continuous
> > Integration (CI) into the PR flow. Koushik and his team will be setting
> up
> > a CI environment which will be used for testing PRs and I will also be
> > setting up a CI environment for testing PRs.
> >
> > The details of the CI integration will be handled publicly, but we will
> > likely have to work with a minimum viable implementation initially and
> mov

Re: 4.9 Release Management

2016-03-02 Thread Will Stevens

Thanks Simon.  :)

*Will STEVENS*
Lead Developer

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

On Wed, Mar 2, 2016 at 4:14 PM, Simon Weller  wrote:

> Will,
>
> You have our support!
>
> Let us know what we can do to help.
>
> - Si
>
> 
> From: Paul Angus 
> Sent: Wednesday, March 2, 2016 3:09 PM
> To: dev@cloudstack.apache.org
> Subject: Re: 4.9 Release Management
>
> That's good enough for me (tm). you're figuring out what you need to
> figure out. I know the feeling. :)
>
> We probably need to have a concensus around release cadence and stick to
> it for a while. Otherwise we're going to lose some credibility as project.
>
>
>
>
>
> From: Will Stevens 
> Sent: 2 Mar 2016 20:46
> To: dev@cloudstack.apache.org
> Subject: Re: 4.9 Release Management
>
> I don't think I can answer that at this time.  My personal opinion is that
> CI is more important than the release timeline, but others may not share
> this opinion (as it is only my opinion).   I am full steam ahead trying to
> review what we have in place and the work that different parties have done
> on CI to date.  I am hoping to have a CI implementation setup in my
> environment soon, which will enable me to better assess the current state
> of affairs.
>
> There are a lot of moving parts involved and I will be the first to admit
> that I don't have a firm grasp on everything yet, so reviewing our Marvin
> test coverage and output is something I have not yet had a chance to
> tackle.
>
> Does that answer your question well enough?  :)
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Wed, Mar 2, 2016 at 12:25 PM, Paul Angus 
> wrote:
>
> > Thanks for taking up the baton Will et al.
> >
> > Just for clarity - given that getting CI 'done' will take some time
> > (mainly because of the state of the Marvin Tests and Marvin output) - are
> > 'we' now dropping the monthly releases?
> >
> >
> > [image: ShapeBlue] 
> > Paul Angus
> > VP Technology ,  ShapeBlue
> > d:  *+44 203 617 0528 | s: +44 203 603 0540*
> > <+44%20203%20617%200528%20%7C%20s:%20+44%20203%20603%200540>  |  m:
> > *+44 7711 418784* <+44%207711%20418784>
> > e:  *paul.an...@shapeblue.com | t: @cloudyangus*
> >   |  w:
> > *www.shapeblue.com* 
> > a:  53 Chandos Place, Covent Garden London WC2N 4HS UK
> > Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue
> > Services India LLP is a company incorporated in India and is operated
> under
> > license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> > company incorporated in Brasil and is operated under license from Shape
> > Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of
> > South Africa and is traded under license from Shape Blue Ltd. ShapeBlue
> is
> > a registered trademark.
> > This email and any attachments to it may be confidential and are intended
> > solely for the use of the individual to whom it is addressed. Any views
> or
> > opinions expressed are solely those of the author and do not necessarily
> > represent those of Shape Blue Ltd or related companies. If you are not
> the
> > intended recipient of this email, you must neither take any action based
> > upon its contents, nor copy or show it to anyone. Please contact the
> sender
> > if you believe you have received this email in error.
> >
> >
> >
>
>
> Paul Angus
> VP Technology   ,   ShapeBlue
>
>
> t:  @cloudyangus
>
> e:  paul.an...@shapeblue.com
> |  w:  www.shapeblue.com
>
>
>
>
>
> -Original Message-
> > From: Will Stevens [mailto:williamstev...@gmail.com]
> > Sent: 02 March 2016 17:15
> > To: dev@cloudstack.apache.org
> > Subject: 4.9 Release Management
> >
> > Hello Everyone,
> > I have mentioned this in other related threads, but I wanted to make an
> > official thread on the topic.
> >
> > I am nominating myself as the release manager for 4.9. Please feel free
> to
> > discuss if you have comments or concerns.
> >
> > I will not be working alone, I will be assisted by Koushik Das and
> Patrick
> > Dube. I will be running point, but all three of us will be working
> together
> > as a unit for this release.
> >
> > Our main focus for this release is the integration of hardware Continuous
> > Integration (CI) into the PR flow. Koushik and his team will be setting
> up
> > a CI environment which will be used for testing PRs and I will also be
> > setting up a CI environment for testing PRs.
> >
> > The details of the CI integration will be handled publicly, but we will
> > likely have to work with a minimum viable implementation initially and
> move
> > forward from there. Here are some of the key aspects of the CI which are
> > top of mind for

Re: 4.9 Release Management

2016-03-02 Thread Sebastien Goasguen


> On Mar 2, 2016, at 10:21 PM, Will Stevens  wrote:
> 
> Yes, I understand and agree with you.  On the flip side, the lack of CI has
> been a thorn in our side for a long time and the increased cadence only
> adds to this problem, so I am trying to walk a thin line here.
> 
> Personally, if CI is the only thing I can contribute to ACS as the 4.9 RM,
> I will be happy with that.  It is a problem that has to be solved and
> someone has to own it.

100% agree, and I am glad you are stepping up.

-sebastien


> 
> *Will STEVENS*
> Lead Developer
> 
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
> 
> On Wed, Mar 2, 2016 at 4:09 PM, Paul Angus  wrote:
> 
>> That's good enough for me (tm). you're figuring out what you need to
>> figure out. I know the feeling. :)
>> 
>> We probably need to have a concensus around release cadence and stick to
>> it for a while. Otherwise we're going to lose some credibility as project.
>> 
>> 
>> 
>> 
>> 
>> From: Will Stevens 
>> Sent: 2 Mar 2016 20:46
>> To: dev@cloudstack.apache.org
>> Subject: Re: 4.9 Release Management
>> 
>> I don't think I can answer that at this time.  My personal opinion is that
>> CI is more important than the release timeline, but others may not share
>> this opinion (as it is only my opinion).   I am full steam ahead trying to
>> review what we have in place and the work that different parties have done
>> on CI to date.  I am hoping to have a CI implementation setup in my
>> environment soon, which will enable me to better assess the current state
>> of affairs.
>> 
>> There are a lot of moving parts involved and I will be the first to admit
>> that I don't have a firm grasp on everything yet, so reviewing our Marvin
>> test coverage and output is something I have not yet had a chance to
>> tackle.
>> 
>> Does that answer your question well enough?  :)
>> 
>> *Will STEVENS*
>> Lead Developer
>> 
>> *CloudOps* *| *Cloud Solutions Experts
>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> w cloudops.com *|* tw @CloudOps_
>> 
>> On Wed, Mar 2, 2016 at 12:25 PM, Paul Angus 
>> wrote:
>> 
>>> Thanks for taking up the baton Will et al.
>>> 
>>> Just for clarity - given that getting CI 'done' will take some time
>>> (mainly because of the state of the Marvin Tests and Marvin output) - are
>>> 'we' now dropping the monthly releases?
>>> 
>>> 
>>> [image: ShapeBlue] 
>>> Paul Angus
>>> VP Technology ,  ShapeBlue
>>> d:  *+44 203 617 0528 | s: +44 203 603 0540*
>>> <+44%20203%20617%200528%20%7C%20s:%20+44%20203%20603%200540>  |  m:
>>> *+44 7711 418784* <+44%207711%20418784>
>>> e:  *paul.an...@shapeblue.com | t: @cloudyangus*
>>>   |  w:
>>> *www.shapeblue.com* 
>>> a:  53 Chandos Place, Covent Garden London WC2N 4HS UK
>>> Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue
>>> Services India LLP is a company incorporated in India and is operated
>> under
>>> license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
>>> company incorporated in Brasil and is operated under license from Shape
>>> Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of
>>> South Africa and is traded under license from Shape Blue Ltd. ShapeBlue
>> is
>>> a registered trademark.
>>> This email and any attachments to it may be confidential and are intended
>>> solely for the use of the individual to whom it is addressed. Any views
>> or
>>> opinions expressed are solely those of the author and do not necessarily
>>> represent those of Shape Blue Ltd or related companies. If you are not
>> the
>>> intended recipient of this email, you must neither take any action based
>>> upon its contents, nor copy or show it to anyone. Please contact the
>> sender
>>> if you believe you have received this email in error.
>>> 
>>> 
>>> 
>> 
>> 
>> Paul Angus
>> VP Technology   ,   ShapeBlue
>> 
>> 
>> t:  @cloudyangus
>> 
>> e:  paul.an...@shapeblue.com
>> |  w:  www.shapeblue.com
>> 
>> 
>> 
>> 
>> 
>> -Original Message-
>>> From: Will Stevens [mailto:williamstev...@gmail.com]
>>> Sent: 02 March 2016 17:15
>>> To: dev@cloudstack.apache.org
>>> Subject: 4.9 Release Management
>>> 
>>> Hello Everyone,
>>> I have mentioned this in other related threads, but I wanted to make an
>>> official thread on the topic.
>>> 
>>> I am nominating myself as the release manager for 4.9. Please feel free
>> to
>>> discuss if you have comments or concerns.
>>> 
>>> I will not be working alone, I will be assisted by Koushik Das and
>> Patrick
>>> Dube. I will be running point, but all three of us will be working
>> together
>>> as a unit for this release.
>>> 
>>> Our main focus for this release is the integration of hardware Continuous
>>> Integration (CI) into the PR flow. Koushik and his team will be setting
>> up
>>> a CI environment which will be

[GitHub] cloudstack pull request: CLOUDSTACK-9298: Improve performance of r...

2016-03-02 Thread pedro-martins

Github user pedro-martins commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1425#discussion_r54797480
  
--- Diff: server/test/com/cloud/api/query/dao/TemplateJoinDaoImplTest.java 
---
@@ -0,0 +1,56 @@
+package com.cloud.api.query.dao;
+
+import junit.framework.TestCase;
+
+import org.apache.cloudstack.api.response.ResourceTagResponse;
+import org.apache.cloudstack.api.response.TemplateResponse;
+import org.apache.cloudstack.framework.config.dao.ConfigurationDao;
+import org.junit.Before;
+import org.junit.Test;
+import org.junit.runner.RunWith;
+import org.mockito.InjectMocks;
+import org.mockito.Mock;
+import org.mockito.MockitoAnnotations;
+import org.powermock.api.mockito.PowerMockito;
+import org.powermock.core.classloader.annotations.PrepareForTest;
+import org.powermock.modules.junit4.PowerMockRunner;
+
+import com.cloud.api.ApiDBUtils;
+import com.cloud.api.query.vo.TemplateJoinVO;
+import com.cloud.user.AccountService;
+
+@RunWith(PowerMockRunner.class)
+@PrepareForTest(ApiDBUtils.class)
+public class TemplateJoinDaoImplTest extends TestCase {
+
+@Mock(name="_configDao")
+private ConfigurationDao _configDao;
+
+@Mock(name="_accountService")
+private AccountService _accountService;
+
+@InjectMocks
+private TemplateJoinDaoImpl _templateJoinDaoImpl;
+
+private TemplateJoinVO template = new TemplateJoinVO();
+private TemplateResponse templateResponse = new TemplateResponse();
+
+private final static long TAG_ID = 1l;
+private final static String TAG_UUID = "---";
+
+@Before
+public void setup() {
+MockitoAnnotations.initMocks(this);
+template.setTagId(TAG_ID);
+template.setTagUuid(TAG_UUID);
+PowerMockito.spy(ApiDBUtils.class);
+PowerMockito.stub(PowerMockito.method(ApiDBUtils.class, 
"newResourceTagResponse")).toReturn(new ResourceTagResponse());
+}
+
+@Test
+public void testUpdateTemplateTagInfo(){
+assertEquals(0, templateResponse.getTags().size());
+_templateJoinDaoImpl.updateTemplateTagInformation(template, 
templateResponse);
+assertEquals(1, templateResponse.getTags().size());
+}
--- End diff --

Hi, @nvazquez.

I see a little mistake in you test, you are testing if the method has 
inserted a tag or not, I think that this test needs to verify if the template 
inserted in the templateResponse is the same that you has passed in the first 
param of the method.
You can do it checking if each variable in both templates are equals.

The same problem in the other tests cases.

Ty.


---
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.9 Release Management

2016-03-02 Thread Ahmad Emneina

4.9 should only be released if it passes the CI tests... pardon the pun.

On Wed, Mar 2, 2016 at 1:21 PM, Will Stevens  wrote:

> Yes, I understand and agree with you.  On the flip side, the lack of CI has
> been a thorn in our side for a long time and the increased cadence only
> adds to this problem, so I am trying to walk a thin line here.
>
> Personally, if CI is the only thing I can contribute to ACS as the 4.9 RM,
> I will be happy with that.  It is a problem that has to be solved and
> someone has to own it.
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Wed, Mar 2, 2016 at 4:09 PM, Paul Angus 
> wrote:
>
> > That's good enough for me (tm). you're figuring out what you need to
> > figure out. I know the feeling. :)
> >
> > We probably need to have a concensus around release cadence and stick to
> > it for a while. Otherwise we're going to lose some credibility as
> project.
> >
> >
> >
> >
> >
> > From: Will Stevens 
> > Sent: 2 Mar 2016 20:46
> > To: dev@cloudstack.apache.org
> > Subject: Re: 4.9 Release Management
> >
> > I don't think I can answer that at this time.  My personal opinion is
> that
> > CI is more important than the release timeline, but others may not share
> > this opinion (as it is only my opinion).   I am full steam ahead trying
> to
> > review what we have in place and the work that different parties have
> done
> > on CI to date.  I am hoping to have a CI implementation setup in my
> > environment soon, which will enable me to better assess the current state
> > of affairs.
> >
> > There are a lot of moving parts involved and I will be the first to admit
> > that I don't have a firm grasp on everything yet, so reviewing our Marvin
> > test coverage and output is something I have not yet had a chance to
> > tackle.
> >
> > Does that answer your question well enough?  :)
> >
> > *Will STEVENS*
> > Lead Developer
> >
> > *CloudOps* *| *Cloud Solutions Experts
> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > w cloudops.com *|* tw @CloudOps_
> >
> > On Wed, Mar 2, 2016 at 12:25 PM, Paul Angus 
> > wrote:
> >
> > > Thanks for taking up the baton Will et al.
> > >
> > > Just for clarity - given that getting CI 'done' will take some time
> > > (mainly because of the state of the Marvin Tests and Marvin output) -
> are
> > > 'we' now dropping the monthly releases?
> > >
> > >
> > > [image: ShapeBlue] 
> > > Paul Angus
> > > VP Technology ,  ShapeBlue
> > > d:  *+44 203 617 0528 | s: +44 203 603 0540*
> > > <+44%20203%20617%200528%20%7C%20s:%20+44%20203%20603%200540>  |  m:
> > > *+44 7711 418784* <+44%207711%20418784>
> > > e:  *paul.an...@shapeblue.com | t: @cloudyangus*
> > >   |  w:
> > > *www.shapeblue.com* 
> > > a:  53 Chandos Place, Covent Garden London WC2N 4HS UK
> > > Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue
> > > Services India LLP is a company incorporated in India and is operated
> > under
> > > license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
> > > company incorporated in Brasil and is operated under license from Shape
> > > Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic
> of
> > > South Africa and is traded under license from Shape Blue Ltd. ShapeBlue
> > is
> > > a registered trademark.
> > > This email and any attachments to it may be confidential and are
> intended
> > > solely for the use of the individual to whom it is addressed. Any views
> > or
> > > opinions expressed are solely those of the author and do not
> necessarily
> > > represent those of Shape Blue Ltd or related companies. If you are not
> > the
> > > intended recipient of this email, you must neither take any action
> based
> > > upon its contents, nor copy or show it to anyone. Please contact the
> > sender
> > > if you believe you have received this email in error.
> > >
> > >
> > >
> >
> >
> > Paul Angus
> > VP Technology   ,   ShapeBlue
> >
> >
> > t:  @cloudyangus
> >
> > e:  paul.an...@shapeblue.com
> > |  w:  www.shapeblue.com
> >
> >
> >
> >
> >
> > -Original Message-
> > > From: Will Stevens [mailto:williamstev...@gmail.com]
> > > Sent: 02 March 2016 17:15
> > > To: dev@cloudstack.apache.org
> > > Subject: 4.9 Release Management
> > >
> > > Hello Everyone,
> > > I have mentioned this in other related threads, but I wanted to make an
> > > official thread on the topic.
> > >
> > > I am nominating myself as the release manager for 4.9. Please feel free
> > to
> > > discuss if you have comments or concerns.
> > >
> > > I will not be working alone, I will be assisted by Koushik Das and
> > Patrick
> > > Dube. I will be running point, but all three of us will be working
> > together
> > > as a unit for this release.
> > >
> > > Our main focus for this release

[GitHub] cloudstack pull request: CLOUDSTACK-9298: Improve performance of r...

2016-03-02 Thread rafaelweingartner

Github user rafaelweingartner commented on the pull request:

https://github.com/apache/cloudstack/pull/1425#issuecomment-191455410
  
@nvazquez I have reviewed your code.
Class âVolumeJoinDaoImplâ at line 46, why did you change the get Logger 
method to use âVolumeJoinDaoImplTestâ?

The method âupdateTemplateTagInformationâ is duplicated (I would say 
triplicated) at âVolumeJoinDaoImplâ, âUserVmJoinDaoImplâ and 
âTemplateJoinDaoImplâ. I know, you may argue that the method 
âupdateTemplateTagInformationâ has a conditional in 
âTemplateJoinDaoImplâ and âVolumeJoinDaoImplâ; still, that conditional 
is executed with some additional checks in âUserVmJoinDaoImplâ. The point 
here is that you should let that conditional out of the method scope, and then 
extract the method to a place that can be reused in all of those classes. All 
of them (VolumeJoinDaoImpl, UserVmJoinDaoImpl, and TemplateJoinDaoImpl) extend 
âGenericDaoBaseâ class. You can easily create a new class that extend 
âGenericDaoBaseâ, with that âupdateTemplateTagInformationâ and make all 
of those classes extend this new one. Please, keep that in mind in your next 
PRs.

That same is happening for VolumeJoinVO, UserVmJoinVO, and TemplateJoinVO 
classes. All of them have attributes âtagAccountNameâ, âtagDomainUuidâ 
and âtagDomainNameâ and their respective getters and setters. They all 
extend âBaseViewVOâ, you can do that same trick I mentioned you above here.

Now about the tests. First, when writing tests, you should ask yourself, 
âWhat am I going to test?â, âIf this method changes the behavior would I 
like to catch it?â, âWhat is the behavior I want to monitor the behavior 
of?â. Those are the basic questions.
I believe your tests, should test the method 
âupdateTemplateTagInformationâ that you wrote. So, what do you want to 
detect if that method stops setting a property? Do you want to detect if it 
sets a property in a wrong place? If you want that, your tests now are not 
adequate, if you do not want that, you should delete the tests classes.

I personally believe that the method deserves tests, to check if it is 
working as expected. Meaning, that it sets the properties you want in the right 
place.

Additionally, when writing tests try to code as little as possible. 
Variables âaccountServiceâ and âconfigDaoâ are not needed to test the 
âupdateTemplateTagInformationâ; keep in mind that is a unit test. To test 
âupdateTemplateTagInformationâ you only need a simple instance of 
âTemplateJoinDaoImplâ and a mock of 
âApiDBUtils.newResourceTagResponse(vtag, false)â


---
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: Important Pending Items

2016-03-02 Thread Will Stevens

I would love that.  Thank you.  I have done a very high level review of the
code and I like what I see.

Are my current assumptions correct?

- It uses KVM as its base hypervisor and all environments are spun up and
tested on it?
- It currently supports testing KVM and Xen?
- It currently supports both Basic and Advanced networking?

It looks like you have other things supported as well, like; OVS, NSX,
openvswitch, etc...

Looking forward to talking with you.  :)

Cheers,

On Tue, Mar 1, 2016 at 4:29 PM, Remi Bergsma 
wrote:

> Hi Will,
>
> We used this to test hundreds of PRs:
> https://github.com/schubergphilis/MCT-shared/. I can talk you through it
> sometime next week or so if you want.
>
> Regards,
> Remi
>
>
> On 01/03/16 21:50, "williamstev...@gmail.com on behalf of Will Stevens" <
> williamstev...@gmail.com on behalf of wstev...@cloudops.com> wrote:
>
> >Thanks Paul.  Great to hear you are planning to make everything available
> >and you are willing to take contributions from the community.
> >
> >I am currently trying to get up to speed on everything that has been done
> >and all the different pieces in play.  I would like to have a CI in place
> >(even if it is only locally on my hardware) for testing PRs for 4.9.  My
> >focus right now is solving the CI problem, so I am interested in any
> >developments on this front.
> >
> >We have Travis doing smoke tests on every PR right now.  Travis is free
> for
> >open source projects.  Is there a reason we are not doing more extensive
> >tests with Travis since it is already integrated into github?  Like maybe
> >running the simulator on every PR?  I think this could be a good first
> step
> >to weed out some of the PRs that are likely to fail a full CI run.
> >
> >Cheers,
> >
> >*Will STEVENS*
> >Lead Developer
> >
> >*CloudOps* *| *Cloud Solutions Experts
> >420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> >w cloudops.com *|* tw @CloudOps_
> >
> >On Tue, Mar 1, 2016 at 3:40 PM, Paul Angus 
> wrote:
> >
> >> Hi Will,
> >>
> >> It will be 100% open source. The $dayjob has blocked the team from
> working
> >> on it recently. I'd like to get some of our ideas into the CloudStack
> wiki
> >> this week before I go on leave for a week.
> >> Rohit has created a repo for us: https://github.com/shapeblue/Trillian
> >> (which looks a bit sad at the moment - I hope to push our Ansible roles
> >> for building mgmt. servers and Marvin boxes into it this week also)
> >>
> >> Internally we're planning a two week sprint on it starting 14th March.
> >> Having to dip in and out of this effort is making it very difficult to
> get
> >> anywhere
> >>
> >> I think the biggest part of the work will be to get Marvin up to
> scratch,
> >> the log output from the tests is pretty bad.
> >>
> >> We very much want this to be a community 'thing', and we're happy to
> work
> >> with everyone/anyone to get there.
> >>
> >> Any ideas on the most effective way to have a number of people on this -
> >> I'm all ears.
> >> In the meantime I'll try to make good on my promises to get our ideas
> >> visible to everyone...
> >>
> >>
> >>
> >>
> >> Paul Angus
> >> VP Technology   ,   ShapeBlue
> >>
> >>
> >> t:  @cloudyangus
> >>
> >> e:  paul.an...@shapeblue.com
> >> |  w:  www.shapeblue.com
> >>
> >>
> >>
> >>
> >>
> >> -Original Message-
> >> From: williamstev...@gmail.com [mailto:williamstev...@gmail.com] On
> >> Behalf Of Will Stevens
> >> Sent: Monday, February 29, 2016 9:52 PM
> >> To: dev@cloudstack.apache.org
> >> Subject: Re: Important Pending Items
> >>
> >> @Paul and @Bharat, thank you for the quality write-ups on this topic.
> >>
> >> re:Paul's Details:
> >> I share a lot of your thoughts on this. The hypervisor in hypervisor
> setup
> >> with the ability to test multiple environments is also core to my
> thinking.
> >> I can't find any details on Trillian, other than what is in this
> thread. Is
> >> it open source and freely available? This is being developed at
> ShapeBlue?
> >>
> >> re:Bharat's Details:
> >> This seems like it is the most likely candidate for being able to offer
> >> value in the short term. Thank you for the work documenting it and
> making
> >> the source available. I still need to review the code. This approach
> will
> >> take quite a bit of work get setup initially, but once setup, it looks
> like
> >> it will do the trick. By using only freely available software makes it
> more
> >> accessible than some options which have been suggested in the past.
> >>
> >> My thoughts on the topic:
> >> - I think it is important that the CI can test all the different
> >> hypervisors and any hardware integrations available in the environment.
> >> - Ideally the CI tool would be easily distributed and installed at
> >> multiple sites. Every company who depends on ACS will have their own
> >> configuration, hardware and mission critical features. If the CI can be
> >> distributed (as

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

2016-03-02 Thread jenkins

See 

--
[...truncated 824 lines...]
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
2016-03-02 23:13:41,562 DEBUG [utils.script.Script] (main:) Executing: 
/bin/bash -c /not/existing/scripts/1456960421562 
2016-03-02 23:13:41,566 DEBUG [utils.script.Script] (main:) Exit value is 127
2016-03-02 23:13:41,566 DEBUG [utils.script.Script] (main:) /bin/bash: 
/not/existing/scripts/1456960421562: No such file or directory
2016-03-02 23:13:41,567 DEBUG [utils.script.Script] (main:) Executing: 
/bin/bash -c echo 'hello world!' 
2016-03-02 23:13:41,570 DEBUG [utils.script.Script] (main:) Execution is 
successful.
2016-03-02 23:13:41,571 DEBUG [utils.script.Script] (main:) Executing: 
/bin/bash -c echo 'hello world!' 
2016-03-02 23:13:41,573 DEBUG [utils.script.Script] (main:) Execution is 
successful.
Tests run: 10, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.048 sec - in 
com.cloud.utils.ScriptTest
Running com.cloud.utils.TestProfiler
Configure log4j with default properties
2016-03-02 23:13:41,603 INFO  [cloud.utils.TestProfiler] (main:) testProfiler() 
started
2016-03-02 23:13:42,614 INFO  [cloud.utils.TestProfiler] (main:) Duration in 
Millis: 1010
2016-03-02 23:13:42,614 INFO  [cloud.utils.TestProfiler] (main:) testProfiler() 
stopped
Configure log4j with default properties
Configure log4j with default properties
2016-03-02 23:13:43,646 INFO  [cloud.utils.TestProfiler] (main:) Duration in 
Nano: 1010155288
Configure log4j with default properties
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.069 sec - in 
com.cloud.utils.TestProfiler
Running com.cloud.utils.net.NetUtilsTest
2016-03-02 23:13:43,693 INFO  [utils.net.NetUtils] (main:) Invalid value of 
cidr 10.3.6.5/50
2016-03-02 23:13:43,703 INFO  [utils.net.NetUtilsTest] (main:) IP is 
1234:5678::2
2016-03-02 23:13:43,704 INFO  [utils.net.NetUtilsTest] (main:) IP is 
1234:5678::1
2016-03-02 23:13:43,706 INFO  [utils.net.NetUtilsTest] (main:) IP is 
1234:5678::1
2016-03-02 23:13:43,707 INFO  [utils.net.NetUtilsTest] (main:) IP is 
1234:5678::1
2016-03-02 23:13:43,708 INFO  [utils.net.NetUtilsTest] (main:) IP is 
1234:5678::1
2016-03-02 23:13:43,709 INFO  [utils.net.NetUtilsTest] (main:) IP is 
1234:5678::e1b1:87dc:9052:aeb8
2016-03-02 23:13:43,712 INFO  [utils.net.NetUtilsTest] (main:) IP is 
1234:5678::4b70:a2ef:780:ad5c
2016-03-02 23:13:43,713 INFO  [utils.net.NetUtilsTest] (main:) IP is 
1234:5678::8da4:9e41:ce5b:ce6f
2016-03-02 23:13:43,715 INFO  [utils.net.NetUtilsTest] (main:) IP is 
1234:5678::fd61:6e38:f0bf:e6d5
2016-03-02 23:13:43,716 INFO  [utils.net.NetUtilsTest] (main:) IP is 
1234:5678::8317:6e9c:77ee:e276
2016-03-02 23:13:43,718 INFO  [utils.net.NetUtilsTest] (main:) IP is 
1234:5678::a06:940:7d55:658e
2016-03-02 23:13:43,719 INFO  [utils.net.NetUtilsTest] (main:) IP is 
1234:5678::532b:faba:42a0:b2c8
2016-03-02 23:13:43,721 INFO  [utils.net.NetUtilsTest] (main:) IP is 
1234:5678::37dc:24f7:a067:4b23
2016-03-02 23:13:43,722 INFO  [utils.net.NetUtilsTest] (main:) IP is 
1234:5678::9f94:5e0e:9c5e:5673
2016-03-02 23:13:43,724 INFO  [utils.net.NetUtilsTest] (main:) IP is 
1234:5678::b3e0:202f:e70b:c68d
2016-03-02 23:13:43,742 ERROR [utils.net.NetUtils] (main:) empty cidr can not 
be converted to longs
com.cloud.utils.exception.CloudRuntimeException: empty cidr can not be 
converted to longs
at com.cloud.utils.net.NetUtils.cidrToLong(NetUtils.java:887)
at com.cloud.utils.net.NetUtils.isNetworksOverlap(NetUtils.java:1174)
at 
com.cloud.utils.net.NetUtilsTest.testIsNetworksOverlapWithEmptyValues(NetUtilsTest.java:509)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunn

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

2016-03-02 Thread 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.799s]
[INFO] Apache CloudStack . SUCCESS [2.629s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.916s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.114s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:26.630s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.110s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [52.567s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.391s]
[INFO] Apache CloudStack API . SUCCESS [1:47.119s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [15.687s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.655s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.100s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.185s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.227s]
[INFO] Apache CloudStack Core  SUCCESS [1:20.407s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.480s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.487s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.083s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.673s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.491s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [26.054s]
[INFO] Apache CloudStack Server .. SUCCESS [4:17.109s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [38.795s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.195s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.287s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.075s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.482s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.862s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.508s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.959s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.170s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [22.163s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.310s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.173s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.398s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.126s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.978s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.484s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[22.987s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.301s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.078s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.392s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.055s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.799s]
[INFO] Apache Cloud

Re: 4.9 Release Management

2016-03-02 Thread Koushik Das

Thanks Will for initiating the discussion on 4.9 release management. As already 
mentioned, I along with Patrick will be helping out Will with the release 
process.

Having a reliable CI system is very important going forward. There are 
discussions already happening in the list related to it. I agree that CI should 
be the top priority for 4.9 release.

The initial idea is to run the CI manually against each PR and publish the 
results in github itself. The details of the CI environment, test scenarios and 
configurations will be published as well. Simulator based tests are already 
running as part of Travis, if required some more tests scenarios can be added 
there.

In the longer run, if more contributors/organizations come up with their own CI 
environment and help test PRs then it will be even better.

-Koushik

From: Will Stevens 
Sent: Wednesday, March 2, 2016 10:44 PM
To: dev@cloudstack.apache.org
Subject: 4.9 Release Management

Hello Everyone,
I have mentioned this in other related threads, but I wanted to make an
official thread on the topic.

I am nominating myself as the release manager for 4.9.  Please feel free to
discuss if you have comments or concerns.

I will not be working alone, I will be assisted by Koushik Das and Patrick
Dube.  I will be running point, but all three of us will be working
together as a unit for this release.

Our main focus for this release is the integration of hardware Continuous
Integration (CI) into the PR flow.  Koushik and his team will be setting up
a CI environment which will be used for testing PRs and I will also be
setting up a CI environment for testing PRs.

The details of the CI integration will be handled publicly, but we will
likely have to work with a minimum viable implementation initially and move
forward from there.  Here are some of the key aspects of the CI which are
top of mind for me.

- Standardize a feedback mechanism to post the result of CI runs back to
the relevant PR.  I believe the best way to do this would be to post a
summary of the CI run in the PR thread on Github.  With the existing
integration, this will then get pushed to the mailing list (since all
comments on a PR are pushed to the mailing list).
- Ideally, we will also make the CI logs available for the run.  We are
still working out the details of how we do this, but we will likely be
pushing the logs to an object store with a cleanup window to remove the
logs after a set period of time (probably a week).  This should give people
the opportunity to pull the logs if they are interested in the test
results, but will reduce the need for ever growing storage.
- In order to parallelize the CI operations, we will not be automatically
kicking off a CI run for every PR for now.  Instead, we will communicate
between us and each run distinct PRs so we can maximize the utilization of
our hardware.

Some longer term goals of the CI in my mind are as follows:

- I would like the core CI framework to be easily distributed and
accessible to anyone who has hardware available.  This would enable anyone
to setup a CI on their hardware and it would automatically be hooked up to
feedback the results to the Github PRs.  I feel this is very important long
term because every individual or organization depends on a different
configuration and hardware setup, so it empowers them to validate their own
use case while adding value back to the community.

Additional details will follow, namely the release schedule etc.

Please contribute your ideas and feedback.

Cheers,

Will


DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

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

2016-03-02 Thread 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.086s]
[INFO] Apache CloudStack . SUCCESS [3.135s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [1.079s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.994s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.946s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.103s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.554s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.795s]
[INFO] Apache CloudStack API . SUCCESS [1:50.431s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.127s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.586s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.095s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.464s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.903s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.752s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.616s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.357s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.108s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:06.239s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.738s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.772s]
[INFO] Apache CloudStack Server .. SUCCESS [4:14.789s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.959s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.701s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.816s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.071s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.471s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.192s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.820s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.683s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.507s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.635s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [23.798s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.045s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [11.989s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.651s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.964s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.343s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[24.901s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[34.552s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.043s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.066s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [14.629s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.590s]
[INFO] Apache Cloud

41 matches

Mail list logo