Re: 4.9 Release Management

[Daan Hoogland]

People,

I agree that CI is an important issue and I thank Will for taking owner
ship. Will: Thank you. I will keep watching the builds.apache.org part of
it and hammer on new or old :/s findbugs issues that come up.
4.9 and CI are not related directly. CI would be related to release process
and not to a release.
If the quality of 4.9 can be guaranteed by means of good code review and
partly CI (the builds.apache.org and travis jobs) partly running test jobs
by hand (in bubbles i.e. devcloud new style) as we did with 4.6 through 4.8
let's go for that and release.


€0,02
-- 
Daan

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

[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.735s]
[INFO] Apache CloudStack . SUCCESS [2.353s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.794s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.940s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:32.694s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.107s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.276s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.291s]
[INFO] Apache CloudStack API . SUCCESS [1:49.924s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [17.123s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.625s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.089s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.371s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.760s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.301s]
[INFO] Apache CloudStack Agents .. SUCCESS [37.010s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.764s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.108s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:08.061s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.947s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.677s]
[INFO] Apache CloudStack Server .. SUCCESS [4:17.546s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.774s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.722s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.657s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.069s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.433s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.345s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [47.696s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.593s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [27.052s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [26.337s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [21.246s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [34.416s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.677s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.870s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [1.026s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [27.030s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[24.019s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.151s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.352s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.518s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.940s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.142s]
[INFO] Apache Cloud

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

[jenkins]

See 

--
[...truncated 3372 lines...]

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

100% [Working]
  
100% [Packages 28.5 MB]
100% [Packages 28.5 MB]
   
100% [Working]
  
100% [Translation-en 1,212 kB]
  
100% [Working]
  
100% [Translation-en 18.5 MB]
100% [Translation-en 18.5 MB]
 
100% [Working]
  
100% [Sources 10.3 kB]
  
100% [Working]
  
100% [Translation-en 14.2 kB]
 
100% [Working]
  
Fetched 7,601 B in 3s (1,986 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... 51%

Reading package lists... 64%

Reading package lists... 64%

Reading package lists... 84%

Reading package lists... 84%

Reading package lists... 86%

Reading package lists... 86%

Reading package lists... 87%

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-03 09:30:14--  
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-03 09:30:15 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-03 09:30:17] DEBUG: on_exit: veewee_destroy'
+ '[' -t 2 ']'
+ echo '[2016-03-03 09:30:17] DEBUG: on_exit: veewee_destroy'
[2016-03-03 09:30:17] 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-03 09:30:17] INFO: destroying existing veewee image, if 
any'
++ '[' -t 2 ']'
++ echo '[2016-03-03 09:30:17] INFO: destroying existing veewee image, if any'
[2016-03-03 09:30:17] 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-03 09:30:24] DEBUG: on_exit: rm -f 
cloud_scripts_shar_archive.sh'
+ '[' -t 2 ']'
+ echo '[2016-03-03 09:30:24] DEBUG: on_exit: rm -f 
cloud_scripts_shar_archive.sh'
[2016-03-03 09:30:24] 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-03 09:30:26] DEBUG: on_exit: rm -rf 
definitions/systemvm64template-master-4.6.0'
+ '[' -t 2 ']'
+ echo '[2016-03-03 09:30:26] DEBUG: on_exit: rm -rf 
definitions/systemvm64template-master-4.6.0'
[2016-03-03 09:30:26] DEBUG: on_exit: rm -rf 
definitions/systemvm64template-master-4.6.0
+ eval rm -rf 

Re: Build failed in Jenkins: build-systemvm64-master #766

[Daan Hoogland]

Rajesh or anybody else involved,

The systemvm build job in buildacloud keeps failing trying to connect to an
old user directory. Does anybody know why this dir is used? Is there a
stock hv-kvp-daemon_3.1_amd64.deb we can use instead?

On Thu, Mar 3, 2016 at 10:23 AM,  wrote:

> See 
>
> --
> [...truncated 3372 lines...]
>
> 100% [Working]
>
> 100% [Packages 28.5 MB]
> 100% [Packages 28.5 MB]
>
> 100% [Working]
>
> 100% [Packages 1,790 kB]
>
> 100% [Working]
>
> 100% [Packages 28.5 MB]
> 100% [Packages 28.5 MB]
>
> 100% [Working]
>
> 100% [Translation-en 1,212 kB]
>
> 100% [Working]
>
> 100% [Translation-en 18.5 MB]
> 100% [Translation-en 18.5 MB]
>
> 100% [Working]
>
> 100% [Sources 10.3 kB]
>
> 100% [Working]
>
> 100% [Translation-en 14.2 kB]
>
> 100% [Working]
>
> Fetched 7,601 B in 3s (1,986 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... 51%
>
> Reading package lists... 64%
>
> Reading package lists... 64%
>
> Reading package lists... 84%
>
> Reading package lists... 84%
>
> Reading package lists... 86%
>
> Reading package lists... 86%
>
> Reading package lists... 87%
>
> 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-03 09:30:14--
> 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-03 09:30:15 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-03 09:30:17] DEBUG: on_exit: veewee_destroy'
> + '[' -t 2 ']'
> + echo '[2016-03-03 09:30:17] DEBUG: on_exit: veewee_destroy'
> [2016-03-03 09:30:17] 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-03 09:30:17] INFO: destroying existing veewee
> image, if any'
> ++ '[' -t 2 ']'
> ++ echo '[2016-03-03 09:30:17] INFO: destroying existing veewee image, if
> any'
> [2016-03-03 09:30:17] 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-03 09:30:24] DEBUG: on_exit: rm -f
> cloud_scripts_shar_archive.sh'
> + '[' -t 2 ']'
> + echo '[2016-03-03 09:30:24] DEBUG: on_exit: rm -f
> cloud_scripts_shar_archive.sh'
> [2016-03-03 09:30:24] 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-03 

[DISCUSS] Request for comments: Out-of-band Management for CloudStack (new feature)

[Rohit Yadav]

Hi all,

I want to propose this new feature for CloudStack, to support out-of-band 
management for CloudStack.

In practice, most hosts have a out-of-band management such as iLO or iDRAC 
(that can support IPMI 2.0 for example). The idea is to allow admins to access 
this out-of-band management interface. Initially power-state related operations 
will be supported such as power on/off/reset etc. and a background service to 
synchronize the power states of the out-of-band management enabled hosts.

Please have a look at the FS and share your feedback on the same:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Out-of-band+Management+for+CloudStack

For testing this feature, I’ve created this tool/library that is a fake ipmi 
server that can be run as a standalone server/tool and also importable to write 
Marvin tests: https://github.com/bhaisaab/ipmisim

Thanks and regards.
PS. I’ll be demoing this feature in today’s CSEUG meetup in London

[ShapeBlue]
Rohit Yadav
Software Architect  ,   ShapeBlue


d:   | s: +44 203 603 0540  |  
m:  +91 8826230892

e:  rohit.ya...@shapeblue.com | t: 
   |  w:  
www.shapeblue.com

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


[cid:image4b88c6.png@2526f1f5.4a8f6b4e]


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.




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

Re: [DISCUSS] Request for comments: Out-of-band Management for CloudStack (new feature)

[Wido den Hollander]

Short note (on tablet), please make sure it supports IPv6 :)

We at PCextreme manage our IPMI for example over IPv6 only.

Wido

> Op 3 mrt. 2016 om 11:43 heeft Rohit Yadav  het 
> volgende geschreven:
> 
> Hi all,
> 
> I want to propose this new feature for CloudStack, to support out-of-band 
> management for CloudStack.
> 
> In practice, most hosts have a out-of-band management such as iLO or iDRAC 
> (that can support IPMI 2.0 for example). The idea is to allow admins to 
> access this out-of-band management interface. Initially power-state related 
> operations will be supported such as power on/off/reset etc. and a background 
> service to synchronize the power states of the out-of-band management enabled 
> hosts.
> 
> Please have a look at the FS and share your feedback on the same:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Out-of-band+Management+for+CloudStack
> 
> For testing this feature, I’ve created this tool/library that is a fake ipmi 
> server that can be run as a standalone server/tool and also importable to 
> write Marvin tests: https://github.com/bhaisaab/ipmisim
> 
> Thanks and regards.
> PS. I’ll be demoing this feature in today’s CSEUG meetup in London
> 
>   
> Rohit Yadav
> Software Architect,   ShapeBlue
> d: | s: +44 203 603 0540   |  m:  +91 8826230892
> e:rohit.ya...@shapeblue.com | t:   |  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.
> 
> 
> 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

Re: [DISCUSS] Request for comments: Out-of-band Management for CloudStack (new feature)

[Rohit Yadav]

Hi Wido,

The feature does not assumption IPv4 or IPv6, it’s upto the driver and the 
address you provide. Presently, the driver simply forks out a ipmitool process 
with a bunch of validated arguments. So, if the driver can reach to the 
specified address/port  (address can be a fqdn, ipv4 or ipv6 address) it will 
work with your ipv6 servers. (if you can do a ipmitool   from the 
mgmt server host, the feature will work in your env)

> On 03-Mar-2016, at 11:13 AM, Wido den Hollander  wrote:
>
> Short note (on tablet), please make sure it supports IPv6 :)
>
> We at PCextreme manage our IPMI for example over IPv6 only.
>
> Wido
>
>> Op 3 mrt. 2016 om 11:43 heeft Rohit Yadav  het 
>> volgende geschreven:
>>
>> Hi all,
>>
>> I want to propose this new feature for CloudStack, to support out-of-band 
>> management for CloudStack.
>>
>> In practice, most hosts have a out-of-band management such as iLO or iDRAC 
>> (that can support IPMI 2.0 for example). The idea is to allow admins to 
>> access this out-of-band management interface. Initially power-state related 
>> operations will be supported such as power on/off/reset etc. and a 
>> background service to synchronize the power states of the out-of-band 
>> management enabled hosts.
>>
>> Please have a look at the FS and share your feedback on the same:
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Out-of-band+Management+for+CloudStack
>>
>> For testing this feature, I’ve created this tool/library that is a fake ipmi 
>> server that can be run as a standalone server/tool and also importable to 
>> write Marvin tests: https://github.com/bhaisaab/ipmisim
>>
>> Thanks and regards.
>> PS. I’ll be demoing this feature in today’s CSEUG meetup in London
>>
>>
>> Rohit Yadav
>> Software Architect   ,   ShapeBlue
>> d:| s: +44 203 603 0540   |  m:  +91 8826230892
>> e:   rohit.ya...@shapeblue.com | t:   |  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.
>>
>>
>> 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

Regards.

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

Re: [DISCUSS] Request for comments: Out-of-band Management for CloudStack (new feature)

[Erik Weber]

Sounds like a decent addition to me, +1

-- 
Erik

On Thu, Mar 3, 2016 at 11:43 AM, Rohit Yadav 
wrote:

> Hi all,
>
> I want to propose this new feature for CloudStack, to support out-of-band
> management for CloudStack.
>
> In practice, most hosts have a out-of-band management such as iLO or iDRAC
> (that can support IPMI 2.0 for example). The idea is to allow admins to
> access this out-of-band management interface. Initially power-state related
> operations will be supported such as power on/off/reset etc. and a
> background service to synchronize the power states of the out-of-band
> management enabled hosts.
>
> Please have a look at the FS and share your feedback on the same:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Out-of-band+Management+for+CloudStack
>
> For testing this feature, I’ve created this tool/library that is a fake
> ipmi server that can be run as a standalone server/tool and also importable
> to write Marvin tests: https://github.com/bhaisaab/ipmisim
>
> Thanks and regards.
> PS. I’ll be demoing this feature in today’s CSEUG meetup in London
>
> [image: ShapeBlue] 
> Rohit Yadav
> Software Architect ,  ShapeBlue
> d:  * | s: +44 203 603 0540* <%7C%20s:%20+44%20203%20603%200540>  |  m:
> *+91 8826230892* <+91%208826230892>
> e:  *rohit.ya...@shapeblue.com | t: *
>   |  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.
>
>
> 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 
>

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

[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.808s]
[INFO] Apache CloudStack . SUCCESS [2.470s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.769s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.356s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.003s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.108s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [52.994s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [26.964s]
[INFO] Apache CloudStack API . SUCCESS [1:48.739s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.477s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.668s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.083s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.464s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.269s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.514s]
[INFO] Apache CloudStack Agents .. SUCCESS [35.960s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.346s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.098s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.205s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.852s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [26.276s]
[INFO] Apache CloudStack Server .. SUCCESS [4:13.627s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.236s]
[INFO] Apache CloudStack Usage Server  SUCCESS [43.915s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:23.398s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.074s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.463s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.537s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.047s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.924s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [25.842s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.633s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [23.231s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [36.651s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.465s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.954s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.982s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.916s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.373s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.067s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.725s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.450s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.657s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.312s]
[INFO] Apache Cloud

LDAP auth failures

[Rene Moser]

We are experiencing authentication issues with LDAP since upgrade to 4.5.1.

After some time (...), users can not authenticate anymore, however,
authentication in other services using ldap works during this time. The
issue is only related to cloudstack login it seems.

We haven't found the root cause yet, a network setup issue or openldap
config issue can not be excluded.

Stacktrace:

2016-02-29 10:05:36,375 DEBUG [cloudstack.ldap.LdapContextFactory]
(catalina-exec-4:ctx-9ffa7c60) initializing ldap with provider url:
ldap://ldap.example.com:389
2016-02-29 10:05:42,382 DEBUG [cloudstack.ldap.LdapManagerImpl]
(catalina-exec-4:ctx-9ffa7c60) ldap Exception:
javax.naming.NamingException: LDAP response read timed out, timeout
used:6000ms.; remaining name 'dc=foo,dc=bar'
at com.sun.jndi.ldap.Connection.readReply(Connection.java:485)
at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:639)
at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:562)
at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1985)
at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1847)
at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1772)
at
org.apache.cloudstack.ldap.LdapUserManager.searchUsers(LdapUserManager.java:206)
at
org.apache.cloudstack.ldap.LdapUserManager.getUser(LdapUserManager.java:122)
at
org.apache.cloudstack.ldap.LdapManagerImpl.getUser(LdapManagerImpl.java:173)
at
org.apache.cloudstack.ldap.LdapManagerImpl.canAuthenticate(LdapManagerImpl.java:97)
at
org.apache.cloudstack.ldap.LdapAuthenticator.authenticate(LdapAuthenticator.java:61)
2016-02-29 10:05:42,383 DEBUG [cloudstack.ldap.LdapManagerImpl]
(catalina-exec-4:ctx-9ffa7c60) Exception while doing an LDAP bind for
user  johndoe
org.apache.cloudstack.ldap.NoLdapUserMatchingQueryException: No users
matching: No Ldap User found for username: johndoe

As I understand there is a username lookup (bind with top reader
credentials) to see if a user exists in the ldap. if found a new
connection will be etablished for auth. In the above stacktrace it seem
that the username lookup fails.

Further we see on the ACS management server however, is that LDAP
connection are not going to be closed at any time.

For _every_ successful auth, the tcp connection remains established forever.

In my understanding of
http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html
these connections will become idle after successful authentication and
reused for new authentication.

However, the reuse for the auth doesn't seem to work. _Every_ new
successful auth of a user _creates_ a new ldap connection. We don't know
if this is related to our problem, but at least it doesn't look like a
wanted behavior.

In the docs we read: "By default, idle connections remain in the pool
indefinitely until they are garbage-collected"

But as said, they seem never be gc-ed. After we added
-Dcom.sun.jndi.ldap.connect.pool.timeout=6 to the
/etc/cloudstack/management/tomcat6.conf which resulted in the
connections beeing gc-ed and we didn't have any report about missing
login since then.

Has anyone also see such an issue? Any thoughts?

René

Re: [DISCUSS] Request for comments: Out-of-band Management for CloudStack (new feature)

[Will Stevens]

Maybe I am not understanding something here.

Does this control the power cycle of the management server(s) or the
hypervisor hosts?  The wording is throwing me off.

I am guessing it is for managing the hypervisor hosts. If this is the case,
does it also handle the "maintenance mode" for the host as well? At least
with XenServer, if you do a power cycle without putting the host into
maintenance mode first, all the VRs will have to be restarted on that host
once it is back up in order for their networking to work again.

How does this fit into this?
On Mar 3, 2016 5:43 AM, "Rohit Yadav"  wrote:

> Hi all,
>
> I want to propose this new feature for CloudStack, to support out-of-band
> management for CloudStack.
>
> In practice, most hosts have a out-of-band management such as iLO or iDRAC
> (that can support IPMI 2.0 for example). The idea is to allow admins to
> access this out-of-band management interface. Initially power-state related
> operations will be supported such as power on/off/reset etc. and a
> background service to synchronize the power states of the out-of-band
> management enabled hosts.
>
> Please have a look at the FS and share your feedback on the same:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Out-of-band+Management+for+CloudStack
>
> For testing this feature, I’ve created this tool/library that is a fake
> ipmi server that can be run as a standalone server/tool and also importable
> to write Marvin tests: https://github.com/bhaisaab/ipmisim
>
> Thanks and regards.
> PS. I’ll be demoing this feature in today’s CSEUG meetup in London
>
> [image: ShapeBlue] 
> Rohit Yadav
> Software Architect ,  ShapeBlue
> d:  * | s: +44 203 603 0540* <%7C%20s:%20+44%20203%20603%200540>  |  m:
> *+91 8826230892* <+91%208826230892>
> e:  *rohit.ya...@shapeblue.com | t: *
>   |  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.
>
>
> 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 
>

Re: [DISCUSS] Request for comments: Out-of-band Management for CloudStack (new feature)

[Koushik Das]

Hi Rohit,


Host maintenance is already there to address the use cases mentioned. What 
additional value would this feature add? Also if it is just providing the IPMI 
based operations then it is only limited to the hosts already added to CS, what 
about new hosts not added in CS? What if host IP/name/password etc. which are 
already stored in CS needs to be changed?


Some questions on use cases.


  *   Restarting stalled/failed hosts

[Koushik] How do you determine if a host stalled/failed? What happens if the 
host lost network connectivity intermittently?


  *   Powering off under-utilised hosts

[Koushik] What is the definition of "under-utilised" - no VMs or based on some 
resource threshold? If there are some running VMs (HA and non-HA) what happens 
to them?


  *   Powering on hosts for provisioning and to increase capacity (for hosts 
already provisioned)

[Koushik] Again how do you power on new hosts not yet added to CS?


  *   Allowing system administrators to see the current power state of the host

[Koushik] When would the power state differ from the existing host state shown 
in CS? There can be certain corner scenarios when CS may not determine the host 
state conclusively (e.g. last host in cluster), but otherwise shouldn't it be 
the same?

Thanks,
Koushik


From: Rohit Yadav 
Sent: Thursday, March 3, 2016 4:13 PM
To: dev@cloudstack.apache.org
Subject: [DISCUSS] Request for comments: Out-of-band Management for CloudStack 
(new feature)

Hi all,

I want to propose this new feature for CloudStack, to support out-of-band 
management for CloudStack.

In practice, most hosts have a out-of-band management such as iLO or iDRAC 
(that can support IPMI 2.0 for example). The idea is to allow admins to access 
this out-of-band management interface. Initially power-state related operations 
will be supported such as power on/off/reset etc. and a background service to 
synchronize the power states of the out-of-band management enabled hosts.

Please have a look at the FS and share your feedback on the same:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Out-of-band+Management+for+CloudStack

For testing this feature, I've created this tool/library that is a fake ipmi 
server that can be run as a standalone server/tool and also importable to write 
Marvin tests: https://github.com/bhaisaab/ipmisim

Thanks and regards.
PS. I'll be demoing this feature in today's CSEUG meetup in London

[ShapeBlue]
Rohit Yadav
Software Architect  ,   ShapeBlue


d:   | s: +44 203 603 0540  |  
m:  +91 8826230892

e:  rohit.ya...@shapeblue.com | t: 
   |  w:  
www.shapeblue.com

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


[cid:image4b88c6.png@2526f1f5.4a8f6b4e]


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.




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



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 
viru

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

[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.771s]
[INFO] Apache CloudStack . SUCCESS [3.359s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [1.106s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.536s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.914s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.100s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.662s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [26.968s]
[INFO] Apache CloudStack API . SUCCESS [1:47.843s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.782s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.794s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.101s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.364s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.844s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.813s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.304s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [37.837s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [13.821s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:06.126s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.750s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.836s]
[INFO] Apache CloudStack Server .. SUCCESS [4:14.979s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.602s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.462s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:23.006s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.072s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.468s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.720s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.777s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.958s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.129s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.976s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [23.668s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [34.775s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.839s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.804s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.970s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.483s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[24.010s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.179s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.804s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.609s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [16.041s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.626s]
[INFO] Apache Cloud

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

[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.728s]
[INFO] Apache CloudStack . SUCCESS [2.222s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.751s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [18.874s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:31.271s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.108s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.563s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.021s]
[INFO] Apache CloudStack API . SUCCESS [1:48.803s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.590s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.924s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.084s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.279s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.436s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.440s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.197s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [37.720s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [15.387s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:10.543s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.836s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.870s]
[INFO] Apache CloudStack Server .. SUCCESS [4:17.579s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.320s]
[INFO] Apache CloudStack Usage Server  SUCCESS [43.975s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.112s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.072s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.426s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.409s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [49.947s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.062s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.844s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.998s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [22.303s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.325s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.711s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.868s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [1.026s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.377s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.749s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.750s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.156s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.762s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [14.823s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.220s]
[INFO] Apache Cloud

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

[nvazquez]

Github user nvazquez commented on the pull request:

https://github.com/apache/cloudstack/pull/1425#issuecomment-191930272
  
@rafaelweingartner @pedro-martins I followed your suggestions and made a 
big refactor, hope this would be better now. I'm planning to run integration 
tests and post the results later.
Thanks!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[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.912s]
[INFO] Apache CloudStack . SUCCESS [2.246s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.808s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.331s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.117s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.115s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.491s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.720s]
[INFO] Apache CloudStack API . SUCCESS [1:51.001s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.214s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.016s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.089s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.817s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.665s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.095s]
[INFO] Apache CloudStack Agents .. SUCCESS [35.671s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.395s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.312s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:08.404s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.606s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.424s]
[INFO] Apache CloudStack Server .. SUCCESS [4:19.842s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.850s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.594s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.138s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.068s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.434s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.609s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.413s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.186s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.499s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.646s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.717s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [36.312s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.480s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.642s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.988s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.298s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.436s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.459s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.539s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.242s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [14.645s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.492s]
[INFO] Apache Cloud

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

[rafaelweingartner]

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

https://github.com/apache/cloudstack/pull/1425#discussion_r54964238
  
--- Diff: 
server/src/com/cloud/api/query/dao/GenericDaoBaseWithTagInformation.java ---
@@ -0,0 +1,58 @@
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements.  See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership.  The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License.  You may obtain a copy of the License at
+//
+//   http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied.  See the License for the
+// specific language governing permissions and limitations
+// under the License.
+package com.cloud.api.query.dao;
+
+import java.io.Serializable;
+
+import org.apache.cloudstack.api.BaseResponseWithTagInformation;
+
+import com.cloud.api.ApiDBUtils;
+import com.cloud.api.query.vo.BaseViewWithTagInformationVO;
+import com.cloud.api.query.vo.ResourceTagJoinVO;
+import com.cloud.utils.db.GenericDaoBase;
+
+public abstract class GenericDaoBaseWithTagInformation extends GenericDaoBase {..}"


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

[rafaelweingartner]

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

https://github.com/apache/cloudstack/pull/1425#discussion_r54969574
  
--- Diff: 
server/test/com/cloud/api/query/dao/GenericDaoBaseWithTagInformationBaseTest.java
 ---
@@ -0,0 +1,59 @@
+// Licensed to the Apache Software Foundation (ASF) under one
+// or more contributor license agreements.  See the NOTICE file
+// distributed with this work for additional information
+// regarding copyright ownership.  The ASF licenses this file
+// to you under the Apache License, Version 2.0 (the
+// "License"); you may not use this file except in compliance
+// with the License.  You may obtain a copy of the License at
+//
+//   http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing,
+// software distributed under the License is distributed on an
+// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+// KIND, either express or implied.  See the License for the
+// specific language governing permissions and limitations
+// under the License.
+package com.cloud.api.query.dao;
+
+import static org.junit.Assert.assertEquals;
+
+import java.io.Serializable;
+
+import org.apache.cloudstack.api.BaseResponseWithTagInformation;
+import org.apache.cloudstack.api.response.ResourceTagResponse;
+import org.powermock.api.mockito.PowerMockito;
+
+import com.cloud.api.ApiDBUtils;
+import com.cloud.api.query.vo.BaseViewWithTagInformationVO;
+
+public abstract class GenericDaoBaseWithTagInformationBaseTest {
+
+public void prepareSetup(String tagKey, String tagValue){
+PowerMockito.spy(ApiDBUtils.class);
+PowerMockito.stub(PowerMockito.method(ApiDBUtils.class, 
"newResourceTagResponse")).toReturn(getResourceTagResponse(tagKey, tagValue));
+}
+
+private ResourceTagResponse getResourceTagResponse(String tagKey, 
String tagValue){
+ResourceTagResponse tagResponse = new ResourceTagResponse();
+tagResponse.setKey(tagKey);
+tagResponse.setValue(tagValue);
+return tagResponse;
+}
+
+public void 
testUpdateTagInformation(GenericDaoBaseWithTagInformation dao, T 
baseView, Z baseResponse,
--- End diff --

What about checking every property that the method "updateTagInformation" 
touches?
Additionally, to test that, you do not need to pass as parameter "tagId, 
key and others" to set at the baseView. If you always use the same values (I 
see no problem on that), no need to receive those parameters.


---
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 #3379

[jenkins]

See 

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

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
cloud-quickcloud ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[1.951s]
[INFO] Apache CloudStack . SUCCESS [2.245s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.769s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [18.934s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.368s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.110s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.651s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.945s]
[INFO] Apache CloudStack API . SUCCESS [1:55.293s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [15.964s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.409s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.095s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.398s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.929s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.287s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.733s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.496s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.213s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:06.393s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.488s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.036s]
[INFO] Apache CloudStack Server .. SUCCESS [4:15.852s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.291s]
[INFO] Apache CloudStack Usage Server  SUCCESS [43.491s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.472s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.069s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.453s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.809s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [47.668s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.176s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.646s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [30.894s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [22.874s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [34.857s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.252s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.188s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.942s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [27.156s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.470s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.904s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.466s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.126s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.876s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.895s]
[INFO] Apache Cloud

[PROPOSAL] Minimum Viable CI Integration

[Will Stevens]

Hey Everyone,
As I am sure most of you are aware, I have been focusing a lot on ways to
get CI integrated back into the community.

Today I build a little POC to validate some ideas and get a feel for a
potential approach for getting CI integrated into the Github pull request
workflow.

There are multiple individuals/companies focusing on CI right now (which is
a good thing), but there has not really been much discussion (that I am
aware of) for how these different CI runs will push back results to the
community.  I want to make sure that nobody's work on this topic goes to
waste, so my goal is to provide a simple and consistent way for everyone to
push their results back to the community.

Here is the basic idea (please give feedback):
- A simple cross platform command line tool with zero dependencies will be
provided (and open sourced) which will handle the submission of the CI
results back to the community.  It is written in Golang and is currently
called 'notify_pr'.
- At the end of a CI execution, the CI should automate the execution of
this tool to handle updating the appropriate PR with the results.

Configuration can be done via the command line or through an INI file.
Here is an example of the configuration details.  The commit is the commit
that the CI just executed against.

token  = 
owner  = apache
repo   = cloudstack
commit = c8443496d3fad78a4b1a48a0992ce545bde299e8

summary_file = 
full_detail_dir = 
full_detail_files = 
store_api = 
store_endpoint = 
store_identity = 
store_secret = 

I have not yet implemented the object storage endpoints, but I have code to
do it from a different project, so I just need to add it.  I will be able
to host my CI output in a swift object store, but others may need to use
AWS S3.  Maybe we can get sponsorship for this storage.  We will only keep
the logs for a window of like a week or so on the object store so the
storage usage will not be ever growing.

Basically, the tool takes the details of the repository you are validating
a Pull Request for and the commit you are building.  It also takes the
files you would like to push to the pull request.  The summary file will be
shown as text in the pull request comment and the other files will be
uploaded to an object store and will be publically available for a period
of time (probably about a week and then get cleaned up, details TBD).  The
files to be uploaded to object store could be either specified as
individual files, OR a target directory and all the files in that directory
will be recursively uploaded to the object store.

When the tool is run, it will scan through all the open pull requests in
the target repository and when it finds the pull request corresponding to
the commit in question, it will post the details as a comment to that pull
request.  This functionality is currently working (see the attached
screenshot).  I can change the formatting and such, this is just an example.

This is still a very rough concept that I have only worked on for a day,
but hopefully you guys agree that it is a good start towards a consistent
feedback mechanism for the community to take advantage of the different
distributed CI installations.

Please voice your feedback and concerns.  I am sure I have not thought of
everything and we may still want to make fundamental changes to the
approach, but I think the concept is solid.

Cheers,

Will

Re: [PROPOSAL] Minimum Viable CI Integration

[Will Stevens]

Apparently attached files don't work when sending to the mailing list.

Find the screenshot here:
https://objects-east.cloud.ca/v1/5ef827605f884961b94881e928e7a250/swill/Screen%20Shot%202016-03-03%20at%207.53.42%20PM.png

On Thu, Mar 3, 2016 at 7:54 PM, Will Stevens 
wrote:

> Hey Everyone,
> As I am sure most of you are aware, I have been focusing a lot on ways to
> get CI integrated back into the community.
>
> Today I build a little POC to validate some ideas and get a feel for a
> potential approach for getting CI integrated into the Github pull request
> workflow.
>
> There are multiple individuals/companies focusing on CI right now (which
> is a good thing), but there has not really been much discussion (that I am
> aware of) for how these different CI runs will push back results to the
> community.  I want to make sure that nobody's work on this topic goes to
> waste, so my goal is to provide a simple and consistent way for everyone to
> push their results back to the community.
>
> Here is the basic idea (please give feedback):
> - A simple cross platform command line tool with zero dependencies will be
> provided (and open sourced) which will handle the submission of the CI
> results back to the community.  It is written in Golang and is currently
> called 'notify_pr'.
> - At the end of a CI execution, the CI should automate the execution of
> this tool to handle updating the appropriate PR with the results.
>
> Configuration can be done via the command line or through an INI file.
> Here is an example of the configuration details.  The commit is the
> commit that the CI just executed against.
>
> token  = 
> owner  = apache
> repo   = cloudstack
> commit = c8443496d3fad78a4b1a48a0992ce545bde299e8
>
> summary_file = 
> full_detail_dir =  object store>
> full_detail_files =  store>
> store_api = 
> store_endpoint = 
> store_identity = 
> store_secret = 
>
> I have not yet implemented the object storage endpoints, but I have code
> to do it from a different project, so I just need to add it.  I will be
> able to host my CI output in a swift object store, but others may need to
> use AWS S3.  Maybe we can get sponsorship for this storage.  We will only
> keep the logs for a window of like a week or so on the object store so the
> storage usage will not be ever growing.
>
> Basically, the tool takes the details of the repository you are validating
> a Pull Request for and the commit you are building.  It also takes the
> files you would like to push to the pull request.  The summary file will be
> shown as text in the pull request comment and the other files will be
> uploaded to an object store and will be publically available for a period
> of time (probably about a week and then get cleaned up, details TBD).  The
> files to be uploaded to object store could be either specified as
> individual files, OR a target directory and all the files in that directory
> will be recursively uploaded to the object store.
>
> When the tool is run, it will scan through all the open pull requests in
> the target repository and when it finds the pull request corresponding to
> the commit in question, it will post the details as a comment to that pull
> request.  This functionality is currently working (see the attached
> screenshot).  I can change the formatting and such, this is just an example.
>
> This is still a very rough concept that I have only worked on for a day,
> but hopefully you guys agree that it is a good start towards a consistent
> feedback mechanism for the community to take advantage of the different
> distributed CI installations.
>
> Please voice your feedback and concerns.  I am sure I have not thought of
> everything and we may still want to make fundamental changes to the
> approach, but I think the concept is solid.
>
> Cheers,
>
> Will
>

Re: [PROPOSAL] Minimum Viable CI Integration

[Gandikota Srinivas]

Will,
I guess Bharat has something similar in working.

Bharat,
Can you please elaborate your approach for sharing the CI results with
community ?

Thanks,
Srinivas

On Fri, Mar 4, 2016 at 6:28 AM, Will Stevens 
wrote:

> Apparently attached files don't work when sending to the mailing list.
>
> Find the screenshot here:
>
> https://objects-east.cloud.ca/v1/5ef827605f884961b94881e928e7a250/swill/Screen%20Shot%202016-03-03%20at%207.53.42%20PM.png
>
> On Thu, Mar 3, 2016 at 7:54 PM, Will Stevens 
> wrote:
>
> > Hey Everyone,
> > As I am sure most of you are aware, I have been focusing a lot on ways to
> > get CI integrated back into the community.
> >
> > Today I build a little POC to validate some ideas and get a feel for a
> > potential approach for getting CI integrated into the Github pull request
> > workflow.
> >
> > There are multiple individuals/companies focusing on CI right now (which
> > is a good thing), but there has not really been much discussion (that I
> am
> > aware of) for how these different CI runs will push back results to the
> > community.  I want to make sure that nobody's work on this topic goes to
> > waste, so my goal is to provide a simple and consistent way for everyone
> to
> > push their results back to the community.
> >
> > Here is the basic idea (please give feedback):
> > - A simple cross platform command line tool with zero dependencies will
> be
> > provided (and open sourced) which will handle the submission of the CI
> > results back to the community.  It is written in Golang and is currently
> > called 'notify_pr'.
> > - At the end of a CI execution, the CI should automate the execution of
> > this tool to handle updating the appropriate PR with the results.
> >
> > Configuration can be done via the command line or through an INI file.
> > Here is an example of the configuration details.  The commit is the
> > commit that the CI just executed against.
> >
> > token  = 
> > owner  = apache
> > repo   = cloudstack
> > commit = c8443496d3fad78a4b1a48a0992ce545bde299e8
> >
> > summary_file = 
> > full_detail_dir =  > object store>
> > full_detail_files =  > store>
> > store_api = 
> > store_endpoint = 
> > store_identity = 
> > store_secret = 
> >
> > I have not yet implemented the object storage endpoints, but I have code
> > to do it from a different project, so I just need to add it.  I will be
> > able to host my CI output in a swift object store, but others may need to
> > use AWS S3.  Maybe we can get sponsorship for this storage.  We will only
> > keep the logs for a window of like a week or so on the object store so
> the
> > storage usage will not be ever growing.
> >
> > Basically, the tool takes the details of the repository you are
> validating
> > a Pull Request for and the commit you are building.  It also takes the
> > files you would like to push to the pull request.  The summary file will
> be
> > shown as text in the pull request comment and the other files will be
> > uploaded to an object store and will be publically available for a period
> > of time (probably about a week and then get cleaned up, details TBD).
> The
> > files to be uploaded to object store could be either specified as
> > individual files, OR a target directory and all the files in that
> directory
> > will be recursively uploaded to the object store.
> >
> > When the tool is run, it will scan through all the open pull requests in
> > the target repository and when it finds the pull request corresponding to
> > the commit in question, it will post the details as a comment to that
> pull
> > request.  This functionality is currently working (see the attached
> > screenshot).  I can change the formatting and such, this is just an
> example.
> >
> > This is still a very rough concept that I have only worked on for a day,
> > but hopefully you guys agree that it is a good start towards a consistent
> > feedback mechanism for the community to take advantage of the different
> > distributed CI installations.
> >
> > Please voice your feedback and concerns.  I am sure I have not thought of
> > everything and we may still want to make fundamental changes to the
> > approach, but I think the concept is solid.
> >
> > Cheers,
> >
> > Will
> >
>

Re: [PROPOSAL] Minimum Viable CI Integration

[Will Stevens]

Last I knew Bharat did not have a solution for posting results back to the
community. I could be wrong though, I don't really know how complete a
solution Bharat has at this point.

There are two other CI implementations in various states of completeness
and I think it is important to have a common mechanism which will work to
post results back to the community regardless of the CI implementation.

"bubble" from SBP seems to be the most complete so far and has been used to
test over 100 PRs, but I don't think the results have formally contributed
back for the community to review.

"trillian" is a project shapeblue is working on, but I am still getting
details for when it is expected to be operational.

This may not be a final solution, but I feel it is a good first step which
will be easy for everyone to work with.
On Mar 3, 2016 8:35 PM, "Gandikota Srinivas" 
wrote:

> Will,
> I guess Bharat has something similar in working.
>
> Bharat,
> Can you please elaborate your approach for sharing the CI results with
> community ?
>
> Thanks,
> Srinivas
>
> On Fri, Mar 4, 2016 at 6:28 AM, Will Stevens 
> wrote:
>
> > Apparently attached files don't work when sending to the mailing list.
> >
> > Find the screenshot here:
> >
> >
> https://objects-east.cloud.ca/v1/5ef827605f884961b94881e928e7a250/swill/Screen%20Shot%202016-03-03%20at%207.53.42%20PM.png
> >
> > On Thu, Mar 3, 2016 at 7:54 PM, Will Stevens 
> > wrote:
> >
> > > Hey Everyone,
> > > As I am sure most of you are aware, I have been focusing a lot on ways
> to
> > > get CI integrated back into the community.
> > >
> > > Today I build a little POC to validate some ideas and get a feel for a
> > > potential approach for getting CI integrated into the Github pull
> request
> > > workflow.
> > >
> > > There are multiple individuals/companies focusing on CI right now
> (which
> > > is a good thing), but there has not really been much discussion (that I
> > am
> > > aware of) for how these different CI runs will push back results to the
> > > community.  I want to make sure that nobody's work on this topic goes
> to
> > > waste, so my goal is to provide a simple and consistent way for
> everyone
> > to
> > > push their results back to the community.
> > >
> > > Here is the basic idea (please give feedback):
> > > - A simple cross platform command line tool with zero dependencies will
> > be
> > > provided (and open sourced) which will handle the submission of the CI
> > > results back to the community.  It is written in Golang and is
> currently
> > > called 'notify_pr'.
> > > - At the end of a CI execution, the CI should automate the execution of
> > > this tool to handle updating the appropriate PR with the results.
> > >
> > > Configuration can be done via the command line or through an INI file.
> > > Here is an example of the configuration details.  The commit is the
> > > commit that the CI just executed against.
> > >
> > > token  = 
> > > owner  = apache
> > > repo   = cloudstack
> > > commit = c8443496d3fad78a4b1a48a0992ce545bde299e8
> > >
> > > summary_file = 
> > > full_detail_dir =  > > object store>
> > > full_detail_files =  object
> > > store>
> > > store_api = 
> > > store_endpoint = 
> > > store_identity = 
> > > store_secret = 
> > >
> > > I have not yet implemented the object storage endpoints, but I have
> code
> > > to do it from a different project, so I just need to add it.  I will be
> > > able to host my CI output in a swift object store, but others may need
> to
> > > use AWS S3.  Maybe we can get sponsorship for this storage.  We will
> only
> > > keep the logs for a window of like a week or so on the object store so
> > the
> > > storage usage will not be ever growing.
> > >
> > > Basically, the tool takes the details of the repository you are
> > validating
> > > a Pull Request for and the commit you are building.  It also takes the
> > > files you would like to push to the pull request.  The summary file
> will
> > be
> > > shown as text in the pull request comment and the other files will be
> > > uploaded to an object store and will be publically available for a
> period
> > > of time (probably about a week and then get cleaned up, details TBD).
> > The
> > > files to be uploaded to object store could be either specified as
> > > individual files, OR a target directory and all the files in that
> > directory
> > > will be recursively uploaded to the object store.
> > >
> > > When the tool is run, it will scan through all the open pull requests
> in
> > > the target repository and when it finds the pull request corresponding
> to
> > > the commit in question, it will post the details as a comment to that
> > pull
> > > request.  This functionality is currently working (see the attached
> > > screenshot).  I can change the formatting and such, this is just an
> > example.
> > >
> > > This is still a very rough concept that I have only worked on for a
> day,
> > > but hopefully you guys agree that it is a good start towards a
> consi

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

[jenkins]

See 

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

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
cloud-quickcloud ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[1.719s]
[INFO] Apache CloudStack . SUCCESS [2.065s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.796s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.069s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:26.441s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.110s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.461s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.519s]
[INFO] Apache CloudStack API . SUCCESS [1:48.387s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.303s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.713s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.089s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.381s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.810s]
[INFO] Apache CloudStack Core  SUCCESS [1:23.186s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.338s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.943s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.139s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:08.707s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.636s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [24.908s]
[INFO] Apache CloudStack Server .. SUCCESS [4:15.761s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.970s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.012s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.449s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.073s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.465s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.997s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [47.659s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.912s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.193s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.889s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.306s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.104s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.568s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.934s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.960s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.451s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.402s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.592s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.134s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.294s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.800s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.818s]
[INFO] Apache Cloud

Re: [PROPOSAL] Minimum Viable CI Integration

[Bharat Kumar]

Hi will,

we have a solution to post the results to the community by email. We also have 
a github integration to fetch the Prs , run tests against them and post
the consolidated results by email and share the logs using dropbox.

We are facing some setup delays to get this up and running. I am sure we will 
be able to do this shortly.

I am also working on posting the results in PR as comments.

Thanks,
Bharat.



> On 04-Mar-2016, at 7:36 AM, Will Stevens  wrote:
>
> Last I knew Bharat did not have a solution for posting results back to the
> community. I could be wrong though, I don't really know how complete a
> solution Bharat has at this point.
>
> There are two other CI implementations in various states of completeness
> and I think it is important to have a common mechanism which will work to
> post results back to the community regardless of the CI implementation.
>
> "bubble" from SBP seems to be the most complete so far and has been used to
> test over 100 PRs, but I don't think the results have formally contributed
> back for the community to review.
>
> "trillian" is a project shapeblue is working on, but I am still getting
> details for when it is expected to be operational.
>
> This may not be a final solution, but I feel it is a good first step which
> will be easy for everyone to work with.
> On Mar 3, 2016 8:35 PM, "Gandikota Srinivas" 
> wrote:
>
>> Will,
>> I guess Bharat has something similar in working.
>>
>> Bharat,
>> Can you please elaborate your approach for sharing the CI results with
>> community ?
>>
>> Thanks,
>> Srinivas
>>
>> On Fri, Mar 4, 2016 at 6:28 AM, Will Stevens 
>> wrote:
>>
>>> Apparently attached files don't work when sending to the mailing list.
>>>
>>> Find the screenshot here:
>>>
>>>
>> https://objects-east.cloud.ca/v1/5ef827605f884961b94881e928e7a250/swill/Screen%20Shot%202016-03-03%20at%207.53.42%20PM.png
>>>
>>> On Thu, Mar 3, 2016 at 7:54 PM, Will Stevens 
>>> wrote:
>>>
 Hey Everyone,
 As I am sure most of you are aware, I have been focusing a lot on ways
>> to
 get CI integrated back into the community.

 Today I build a little POC to validate some ideas and get a feel for a
 potential approach for getting CI integrated into the Github pull
>> request
 workflow.

 There are multiple individuals/companies focusing on CI right now
>> (which
 is a good thing), but there has not really been much discussion (that I
>>> am
 aware of) for how these different CI runs will push back results to the
 community.  I want to make sure that nobody's work on this topic goes
>> to
 waste, so my goal is to provide a simple and consistent way for
>> everyone
>>> to
 push their results back to the community.

 Here is the basic idea (please give feedback):
 - A simple cross platform command line tool with zero dependencies will
>>> be
 provided (and open sourced) which will handle the submission of the CI
 results back to the community.  It is written in Golang and is
>> currently
 called 'notify_pr'.
 - At the end of a CI execution, the CI should automate the execution of
 this tool to handle updating the appropriate PR with the results.

 Configuration can be done via the command line or through an INI file.
 Here is an example of the configuration details.  The commit is the
 commit that the CI just executed against.

 token  = 
 owner  = apache
 repo   = cloudstack
 commit = c8443496d3fad78a4b1a48a0992ce545bde299e8

 summary_file = 
 full_detail_dir = >>> object store>
 full_detail_files = > object
 store>
 store_api = 
 store_endpoint = 
 store_identity = 
 store_secret = 

 I have not yet implemented the object storage endpoints, but I have
>> code
 to do it from a different project, so I just need to add it.  I will be
 able to host my CI output in a swift object store, but others may need
>> to
 use AWS S3.  Maybe we can get sponsorship for this storage.  We will
>> only
 keep the logs for a window of like a week or so on the object store so
>>> the
 storage usage will not be ever growing.

 Basically, the tool takes the details of the repository you are
>>> validating
 a Pull Request for and the commit you are building.  It also takes the
 files you would like to push to the pull request.  The summary file
>> will
>>> be
 shown as text in the pull request comment and the other files will be
 uploaded to an object store and will be publically available for a
>> period
 of time (probably about a week and then get cleaned up, details TBD).
>>> The
 files to be uploaded to object store could be either specified as
 individual files, OR a target directory and all the files in that
>>> directory
 will be recursively uploaded to the object store.

 When the tool is run, it will scan through all the open pull requests
>> in
 the target r

Re: [PROPOSAL] Minimum Viable CI Integration

[Will Stevens]

Awesome, thanks for the update Bharat, that is great progress.

If you need a hand with the posting back to the pull requests on github,
just let me know, I have that piece working.  My implementation is a cross
platform binary without any dependencies so it could be easy to integrate
if that would be helpful.  I plan to clean it up a bit and open source it.
I have only spent a few hours on it so far, so I want to do a once through
to get it ready to release.

Just an FYI, it is not very easy to post back to github using the 'Pull
Requests' API because of the code reference requirements.  Checkout the
'Issues' API which is basically the same thing, but enables you to create
comments without having to specify a specific location in the PRs code
which you are commenting on.  This tripped me up for a while today and once
I realized I could do it through the Issues instead of the Pull Requests,
it made things infinitely easier.

Let me know if you have other questions.

Cheers,

Will


On Thu, Mar 3, 2016 at 11:29 PM, Bharat Kumar 
wrote:

> Hi will,
>
> we have a solution to post the results to the community by email. We also
> have a github integration to fetch the Prs , run tests against them and post
> the consolidated results by email and share the logs using dropbox.
>
> We are facing some setup delays to get this up and running. I am sure we
> will be able to do this shortly.
>
> I am also working on posting the results in PR as comments.
>
> Thanks,
> Bharat.
>
>
>
> > On 04-Mar-2016, at 7:36 AM, Will Stevens 
> wrote:
> >
> > Last I knew Bharat did not have a solution for posting results back to
> the
> > community. I could be wrong though, I don't really know how complete a
> > solution Bharat has at this point.
> >
> > There are two other CI implementations in various states of completeness
> > and I think it is important to have a common mechanism which will work to
> > post results back to the community regardless of the CI implementation.
> >
> > "bubble" from SBP seems to be the most complete so far and has been used
> to
> > test over 100 PRs, but I don't think the results have formally
> contributed
> > back for the community to review.
> >
> > "trillian" is a project shapeblue is working on, but I am still getting
> > details for when it is expected to be operational.
> >
> > This may not be a final solution, but I feel it is a good first step
> which
> > will be easy for everyone to work with.
> > On Mar 3, 2016 8:35 PM, "Gandikota Srinivas" <
> gandikota.srini...@gmail.com>
> > wrote:
> >
> >> Will,
> >> I guess Bharat has something similar in working.
> >>
> >> Bharat,
> >> Can you please elaborate your approach for sharing the CI results with
> >> community ?
> >>
> >> Thanks,
> >> Srinivas
> >>
> >> On Fri, Mar 4, 2016 at 6:28 AM, Will Stevens 
> >> wrote:
> >>
> >>> Apparently attached files don't work when sending to the mailing list.
> >>>
> >>> Find the screenshot here:
> >>>
> >>>
> >>
> https://objects-east.cloud.ca/v1/5ef827605f884961b94881e928e7a250/swill/Screen%20Shot%202016-03-03%20at%207.53.42%20PM.png
> >>>
> >>> On Thu, Mar 3, 2016 at 7:54 PM, Will Stevens  >
> >>> wrote:
> >>>
>  Hey Everyone,
>  As I am sure most of you are aware, I have been focusing a lot on ways
> >> to
>  get CI integrated back into the community.
> 
>  Today I build a little POC to validate some ideas and get a feel for a
>  potential approach for getting CI integrated into the Github pull
> >> request
>  workflow.
> 
>  There are multiple individuals/companies focusing on CI right now
> >> (which
>  is a good thing), but there has not really been much discussion (that
> I
> >>> am
>  aware of) for how these different CI runs will push back results to
> the
>  community.  I want to make sure that nobody's work on this topic goes
> >> to
>  waste, so my goal is to provide a simple and consistent way for
> >> everyone
> >>> to
>  push their results back to the community.
> 
>  Here is the basic idea (please give feedback):
>  - A simple cross platform command line tool with zero dependencies
> will
> >>> be
>  provided (and open sourced) which will handle the submission of the CI
>  results back to the community.  It is written in Golang and is
> >> currently
>  called 'notify_pr'.
>  - At the end of a CI execution, the CI should automate the execution
> of
>  this tool to handle updating the appropriate PR with the results.
> 
>  Configuration can be done via the command line or through an INI file.
>  Here is an example of the configuration details.  The commit is the
>  commit that the CI just executed against.
> 
>  token  = 
>  owner  = apache
>  repo   = cloudstack
>  commit = c8443496d3fad78a4b1a48a0992ce545bde299e8
> 
>  summary_file = 
>  full_detail_dir =   object store>
>  full_detail_files =  >> object
>  store>
>  store_api = 
>  store_e

Re: [PROPOSAL] Minimum Viable CI Integration

[Bharat Kumar]

Thanks for the info Will.

I also faced a similar problem. I will get back to you if i see any further 
issues.

Thanks,
Bharat.

> On 04-Mar-2016, at 10:12 AM, Will Stevens  wrote:
>
> Awesome, thanks for the update Bharat, that is great progress.
>
> If you need a hand with the posting back to the pull requests on github,
> just let me know, I have that piece working.  My implementation is a cross
> platform binary without any dependencies so it could be easy to integrate
> if that would be helpful.  I plan to clean it up a bit and open source it.
> I have only spent a few hours on it so far, so I want to do a once through
> to get it ready to release.
>
> Just an FYI, it is not very easy to post back to github using the 'Pull
> Requests' API because of the code reference requirements.  Checkout the
> 'Issues' API which is basically the same thing, but enables you to create
> comments without having to specify a specific location in the PRs code
> which you are commenting on.  This tripped me up for a while today and once
> I realized I could do it through the Issues instead of the Pull Requests,
> it made things infinitely easier.
>
> Let me know if you have other questions.
>
> Cheers,
>
> Will
>
>
> On Thu, Mar 3, 2016 at 11:29 PM, Bharat Kumar 
> wrote:
>
>> Hi will,
>>
>> we have a solution to post the results to the community by email. We also
>> have a github integration to fetch the Prs , run tests against them and post
>> the consolidated results by email and share the logs using dropbox.
>>
>> We are facing some setup delays to get this up and running. I am sure we
>> will be able to do this shortly.
>>
>> I am also working on posting the results in PR as comments.
>>
>> Thanks,
>> Bharat.
>>
>>
>>
>>> On 04-Mar-2016, at 7:36 AM, Will Stevens 
>> wrote:
>>>
>>> Last I knew Bharat did not have a solution for posting results back to
>> the
>>> community. I could be wrong though, I don't really know how complete a
>>> solution Bharat has at this point.
>>>
>>> There are two other CI implementations in various states of completeness
>>> and I think it is important to have a common mechanism which will work to
>>> post results back to the community regardless of the CI implementation.
>>>
>>> "bubble" from SBP seems to be the most complete so far and has been used
>> to
>>> test over 100 PRs, but I don't think the results have formally
>> contributed
>>> back for the community to review.
>>>
>>> "trillian" is a project shapeblue is working on, but I am still getting
>>> details for when it is expected to be operational.
>>>
>>> This may not be a final solution, but I feel it is a good first step
>> which
>>> will be easy for everyone to work with.
>>> On Mar 3, 2016 8:35 PM, "Gandikota Srinivas" <
>> gandikota.srini...@gmail.com>
>>> wrote:
>>>
 Will,
 I guess Bharat has something similar in working.

 Bharat,
 Can you please elaborate your approach for sharing the CI results with
 community ?

 Thanks,
 Srinivas

 On Fri, Mar 4, 2016 at 6:28 AM, Will Stevens 
 wrote:

> Apparently attached files don't work when sending to the mailing list.
>
> Find the screenshot here:
>
>

>> https://objects-east.cloud.ca/v1/5ef827605f884961b94881e928e7a250/swill/Screen%20Shot%202016-03-03%20at%207.53.42%20PM.png
>
> On Thu, Mar 3, 2016 at 7:54 PM, Will Stevens >>
> wrote:
>
>> Hey Everyone,
>> As I am sure most of you are aware, I have been focusing a lot on ways
 to
>> get CI integrated back into the community.
>>
>> Today I build a little POC to validate some ideas and get a feel for a
>> potential approach for getting CI integrated into the Github pull
 request
>> workflow.
>>
>> There are multiple individuals/companies focusing on CI right now
 (which
>> is a good thing), but there has not really been much discussion (that
>> I
> am
>> aware of) for how these different CI runs will push back results to
>> the
>> community.  I want to make sure that nobody's work on this topic goes
 to
>> waste, so my goal is to provide a simple and consistent way for
 everyone
> to
>> push their results back to the community.
>>
>> Here is the basic idea (please give feedback):
>> - A simple cross platform command line tool with zero dependencies
>> will
> be
>> provided (and open sourced) which will handle the submission of the CI
>> results back to the community.  It is written in Golang and is
 currently
>> called 'notify_pr'.
>> - At the end of a CI execution, the CI should automate the execution
>> of
>> this tool to handle updating the appropriate PR with the results.
>>
>> Configuration can be done via the command line or through an INI file.
>> Here is an example of the configuration details.  The commit is the
>> commit that the CI just executed against.
>>
>> token  = 
>> owne

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

[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.969s]
[INFO] Apache CloudStack . SUCCESS [2.131s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.787s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.088s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.022s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.103s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.218s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.916s]
[INFO] Apache CloudStack API . SUCCESS [1:47.822s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.086s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.335s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.085s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [27.795s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.539s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.134s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.531s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.994s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.144s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.367s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.627s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.631s]
[INFO] Apache CloudStack Server .. SUCCESS [4:09.970s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.503s]
[INFO] Apache CloudStack Usage Server  SUCCESS [43.915s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:23.102s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.068s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.475s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.340s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.146s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.284s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [25.918s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [22.098s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.571s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [34.943s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.530s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.942s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.950s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.523s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.424s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.843s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.282s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.274s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.812s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.849s]
[INFO] Apache Cloud