Build failed in Jenkins: brooklyn-master-build #991

2017-04-03 Thread Apache Jenkins Server 
See 

--
[...truncated 5.70 MB...]
[INFO] Brooklyn Logback Includable Configuration .. SUCCESS [  3.957 s]
[INFO] Brooklyn Common Utilities .. SUCCESS [ 34.743 s]
[INFO] Brooklyn API ... SUCCESS [  5.174 s]
[INFO] CAMP Server Parent Project . SUCCESS [  2.591 s]
[INFO] CAMP Base .. SUCCESS [  6.485 s]
[INFO] Brooklyn Test Support .. SUCCESS [  4.516 s]
[INFO] Brooklyn REST Swagger Apidoc Utilities . SUCCESS [  4.641 s]
[INFO] Brooklyn Logback Configuration . SUCCESS [  3.947 s]
[INFO] CAMP Server  SUCCESS [  8.504 s]
[INFO] Brooklyn Felix Runtime . SUCCESS [  7.910 s]
[INFO] Brooklyn Groovy Utilities .. SUCCESS [  6.018 s]
[INFO] Brooklyn Core .. SUCCESS [03:20 min]
[INFO] Brooklyn Policies .. SUCCESS [ 56.475 s]
[INFO] Brooklyn WinRM Software Entities ... SUCCESS [ 11.254 s]
[INFO] Brooklyn Secure JMXMP Agent  SUCCESS [ 12.877 s]
[INFO] Brooklyn JMX RMI Agent . SUCCESS [  4.470 s]
[INFO] Brooklyn Jclouds Location Targets .. SUCCESS [ 48.070 s]
[INFO] Brooklyn Software Base . SUCCESS [01:43 min]
[INFO] Brooklyn CAMP .. FAILURE [03:37 min]
[INFO] Brooklyn Hazelcast Storage . SKIPPED
[INFO] Brooklyn Launcher Common ... SKIPPED
[INFO] Brooklyn REST API .. SKIPPED
[INFO] Brooklyn REST Resources  SKIPPED
[INFO] Brooklyn REST Server ... SKIPPED
[INFO] Brooklyn Launcher .. SKIPPED
[INFO] Brooklyn Command Line Interface  SKIPPED
[INFO] Brooklyn Test Framework  SKIPPED
[INFO] Brooklyn OSGi init . SKIPPED
[INFO] Brooklyn Karaf . SKIPPED
[INFO] Jetty config fragment .. SKIPPED
[INFO] Apache Http Component extension  SKIPPED
[INFO] Brooklyn Karaf Features  SKIPPED
[INFO] Brooklyn Karaf Shell Commands .. SKIPPED
[INFO] Brooklyn Library Root .. SKIPPED
[INFO] Brooklyn CM SaltStack .. SKIPPED
[INFO] Brooklyn CM Ansible  SKIPPED
[INFO] Brooklyn CM Integration Root ... SKIPPED
[INFO] Brooklyn Network Software Entities . SKIPPED
[INFO] Brooklyn OSGi Software Entities  SKIPPED
[INFO] Brooklyn Database Software Entities  SKIPPED
[INFO] Brooklyn Web App Software Entities . SKIPPED
[INFO] Brooklyn Messaging Software Entities ... SKIPPED
[INFO] Brooklyn NoSQL Data Store Software Entities  SKIPPED
[INFO] Brooklyn Monitoring Software Entities .. SKIPPED
[INFO] Brooklyn QA  SKIPPED
[INFO] Brooklyn Examples Aggregator Project ... SKIPPED
[INFO] Brooklyn Examples Aggregator Project - Webapps . SKIPPED
[INFO] hello-world-webapp Maven Webapp  SKIPPED
[INFO] hello-world-sql-webapp Maven Webapp  SKIPPED
[INFO] Brooklyn Simple Web Cluster Example  SKIPPED
[INFO] Brooklyn Global Web Fabric Example . SKIPPED
[INFO] Brooklyn Simple Messaging Publish-Subscribe Example  SKIPPED
[INFO] Brooklyn NoSQL Cluster Examples  SKIPPED
[INFO] Brooklyn Library Karaf integration . SKIPPED
[INFO] Brooklyn Library Catalog ... SKIPPED
[INFO] Brooklyn Library Karaf Features  SKIPPED
[INFO] Brooklyn Client  SKIPPED
[INFO] Brooklyn Client Command Line Interface . SKIPPED
[INFO] Brooklyn REST java Client .. SKIPPED
[INFO] Brooklyn Downstream Project Parent . SKIPPED
[INFO] Brooklyn Dist Root . SKIPPED
[INFO] Brooklyn All Things  SKIPPED
[INFO] Brooklyn Distribution .. SKIPPED
[INFO] Brooklyn Karaf Distribution Parent . SKIPPED
[INFO] Brooklyn Karaf Server Configuration  SKIPPED
[INFO] Brooklyn Dist Karaf Features ... SKIPPED
[INFO] Brooklyn Karaf Distribution  SKIPPED
[INFO] Brooklyn Karaf pax-exam itest ..

Build failed in Jenkins: brooklyn-master-build #990

2017-04-03 Thread Apache Jenkins Server 
See 

--
[...truncated 5.81 MB...]
[INFO] Brooklyn Test Support Utilities  SUCCESS [  9.512 s]
[INFO] Brooklyn Logback Includable Configuration .. SUCCESS [  6.489 s]
[INFO] Brooklyn Common Utilities .. SUCCESS [ 39.716 s]
[INFO] Brooklyn API ... SUCCESS [  7.508 s]
[INFO] CAMP Server Parent Project . SUCCESS [  3.525 s]
[INFO] CAMP Base .. SUCCESS [ 14.630 s]
[INFO] Brooklyn Test Support .. SUCCESS [  6.618 s]
[INFO] Brooklyn REST Swagger Apidoc Utilities . SUCCESS [  7.648 s]
[INFO] Brooklyn Logback Configuration . SUCCESS [  5.775 s]
[INFO] CAMP Server  SUCCESS [ 12.965 s]
[INFO] Brooklyn Felix Runtime . SUCCESS [ 10.621 s]
[INFO] Brooklyn Groovy Utilities .. SUCCESS [  8.825 s]
[INFO] Brooklyn Core .. SUCCESS [03:33 min]
[INFO] Brooklyn Policies .. SUCCESS [01:00 min]
[INFO] Brooklyn WinRM Software Entities ... SUCCESS [ 18.512 s]
[INFO] Brooklyn Secure JMXMP Agent  SUCCESS [ 13.891 s]
[INFO] Brooklyn JMX RMI Agent . SUCCESS [ 14.026 s]
[INFO] Brooklyn Jclouds Location Targets .. SUCCESS [ 53.196 s]
[INFO] Brooklyn Software Base . SUCCESS [01:39 min]
[INFO] Brooklyn CAMP .. FAILURE [03:49 min]
[INFO] Brooklyn Hazelcast Storage . SKIPPED
[INFO] Brooklyn Launcher Common ... SKIPPED
[INFO] Brooklyn REST API .. SKIPPED
[INFO] Brooklyn REST Resources  SKIPPED
[INFO] Brooklyn REST Server ... SKIPPED
[INFO] Brooklyn Launcher .. SKIPPED
[INFO] Brooklyn Command Line Interface  SKIPPED
[INFO] Brooklyn Test Framework  SKIPPED
[INFO] Brooklyn OSGi init . SKIPPED
[INFO] Brooklyn Karaf . SKIPPED
[INFO] Jetty config fragment .. SKIPPED
[INFO] Apache Http Component extension  SKIPPED
[INFO] Brooklyn Karaf Features  SKIPPED
[INFO] Brooklyn Karaf Shell Commands .. SKIPPED
[INFO] Brooklyn Library Root .. SKIPPED
[INFO] Brooklyn CM SaltStack .. SKIPPED
[INFO] Brooklyn CM Ansible  SKIPPED
[INFO] Brooklyn CM Integration Root ... SKIPPED
[INFO] Brooklyn Network Software Entities . SKIPPED
[INFO] Brooklyn OSGi Software Entities  SKIPPED
[INFO] Brooklyn Database Software Entities  SKIPPED
[INFO] Brooklyn Web App Software Entities . SKIPPED
[INFO] Brooklyn Messaging Software Entities ... SKIPPED
[INFO] Brooklyn NoSQL Data Store Software Entities  SKIPPED
[INFO] Brooklyn Monitoring Software Entities .. SKIPPED
[INFO] Brooklyn QA  SKIPPED
[INFO] Brooklyn Examples Aggregator Project ... SKIPPED
[INFO] Brooklyn Examples Aggregator Project - Webapps . SKIPPED
[INFO] hello-world-webapp Maven Webapp  SKIPPED
[INFO] hello-world-sql-webapp Maven Webapp  SKIPPED
[INFO] Brooklyn Simple Web Cluster Example  SKIPPED
[INFO] Brooklyn Global Web Fabric Example . SKIPPED
[INFO] Brooklyn Simple Messaging Publish-Subscribe Example  SKIPPED
[INFO] Brooklyn NoSQL Cluster Examples  SKIPPED
[INFO] Brooklyn Library Karaf integration . SKIPPED
[INFO] Brooklyn Library Catalog ... SKIPPED
[INFO] Brooklyn Library Karaf Features  SKIPPED
[INFO] Brooklyn Client  SKIPPED
[INFO] Brooklyn Client Command Line Interface . SKIPPED
[INFO] Brooklyn REST java Client .. SKIPPED
[INFO] Brooklyn Downstream Project Parent . SKIPPED
[INFO] Brooklyn Dist Root . SKIPPED
[INFO] Brooklyn All Things  SKIPPED
[INFO] Brooklyn Distribution .. SKIPPED
[INFO] Brooklyn Karaf Distribution Parent . SKIPPED
[INFO] Brooklyn Karaf Server Configuration  SKIPPED
[INFO] Brooklyn Dist Karaf Features ... SKIPPED
[INFO] Brooklyn Karaf Distribution

[jira] [Created] (BROOKLYN-462) Invalid icon for "server" entity

2017-04-03 Thread Svetoslav Neykov (JIRA) 
Svetoslav Neykov created BROOKLYN-462:
-

 Summary: Invalid icon for "server" entity
 Key: BROOKLYN-462
 URL: https://issues.apache.org/jira/browse/BROOKLYN-462
 Project: Brooklyn
  Issue Type: Bug
Reporter: Svetoslav Neykov


Deploying the following bluepritn:
{noformat}
services:
- type: server
{noformat}

results in broken icon in the left pane.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] brooklyn-server pull request #617: Persist management plane ID

2017-04-03 Thread neykov 
Github user neykov commented on a diff in the pull request:

https://github.com/apache/brooklyn-server/pull/617#discussion_r109357619
  
--- Diff: 
api/src/main/java/org/apache/brooklyn/api/mgmt/ManagementContext.java ---
@@ -66,9 +67,20 @@
  * In other words the value of {@link 
Application#getManagementContext()#getManagementPlaneId()} 
  * will generally be constant (in contrast to {@link 
#getManagementNodeId()}).
  * 
- * This value should not be null unless the management context is a 
non-functional
- * (non-deployment) instance. */
+ * Throws an {@link NullPointerException} if the value hasn't been 
initialized yet. The value is set:
--- End diff --

Wonder whether we should leave this to return `null` when not initialised. 
It's been useful to find instances of wrong (too early) usage but on the other 
hand changes the method behaviour.


---
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] brooklyn-server pull request #617: Persist management plane ID

2017-04-03 Thread neykov 
GitHub user neykov opened a pull request:

https://github.com/apache/brooklyn-server/pull/617

Persist management plane ID

Some considerations on where to place the planeId initialisation:
 * BrooklynMemento (RebindManager). `planeId` will be available only after 
rebind, so it will
   be available to MASTER nodes only (and potentially HOT_STANDBY)
 * ManagementPlaneSyncRecord (HighAvailabilityManager). Used only when HA 
is enabled. When HA is disabled
   HighAvailabilityManager is not initialised, doesn't access the store at 
all, no
   records are getting written.
 * Separate init step in BrooklynLauncher. Early in the lifecycle so users 
need not to care
   too much when they are allowed to read it. On the other hand it's not 
encapsulated so
   need to touch all places that use persistence (i.e. launcher, 
copy-state, backup). Can
   only read from the store at this point, write access is not enabled yet. 
If HA is configured
   store writes are enabled only after becoming master. Writing to the 
store in this case would
   be risky, even if we know that it's a clean state (no planeId file). 
Better leave only the
   master update the store.

Because of the above I decided to go for a mixed approach:
  * persist the `planeId` immediately after starting persistence (i.e. 
MASTER when HA) and repeat hourly
  * don't overwrite persisted store `planeId` if different
  * init `planeId` as part of the rebind sequence; if no `planeId` exists 
in store generate one
  * init `planeId` when reading the management records so we have it 
initialized for non-`MASTER` nodes as well; don't generate one if not in 
persisted store

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

$ git pull https://github.com/neykov/brooklyn-server plane-id

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

https://github.com/apache/brooklyn-server/pull/617.patch

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

This closes #617


commit 7bcc566bec9e4875207036b1943c4528aae72bea
Author: Svetoslav Neykov 
Date:   2017-03-30T14:19:43Z

Persist management plane ID

commit 701c716aa27dbc3999c9c2fdd728e09089448b1a
Author: Svetoslav Neykov 
Date:   2017-04-03T07:32:54Z

Persisting management plane ID test coverage




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