Build failed in Jenkins: brooklyn-master-windows #52

[Apache Jenkins Server]

See 

--
[...truncated 38250 lines...]
[INFO] CAMP Server  SUCCESS [  8.505 s]
[INFO] CAMP Server Jersey . SUCCESS [  7.914 s]
[INFO] Brooklyn Felix Runtime . SUCCESS [  4.818 s]
[INFO] Brooklyn Groovy Utilities .. SUCCESS [  1.158 s]
[INFO] Brooklyn Core .. SUCCESS [04:14 min]
[INFO] Brooklyn Policies .. SUCCESS [01:21 min]
[INFO] Brooklyn WinRM Software Entities ... SUCCESS [  9.472 s]
[INFO] Brooklyn Secure JMXMP Agent  SUCCESS [ 10.229 s]
[INFO] Brooklyn JMX RMI Agent . SUCCESS [  0.955 s]
[INFO] Brooklyn Jclouds Location Targets .. SUCCESS [ 24.980 s]
[INFO] Brooklyn Software Base . SUCCESS [01:19 min]
[INFO] Brooklyn CAMP REST API . SUCCESS [05:03 min]
[INFO] Brooklyn Hazelcast Storage . SUCCESS [  4.604 s]
[INFO] Brooklyn Launcher Common ... SUCCESS [  5.698 s]
[INFO] Brooklyn REST API .. SUCCESS [ 10.902 s]
[INFO] Brooklyn REST Resources  SUCCESS [01:05 min]
[INFO] Brooklyn REST Server ... SUCCESS [ 25.162 s]
[INFO] Brooklyn Launcher .. FAILURE [34:13 min]
[INFO] Brooklyn Command Line Interface  SKIPPED
[INFO] Brooklyn REST Client ... SKIPPED
[INFO] Brooklyn REST Server with Jersey dependencies .. SKIPPED
[INFO] Brooklyn Test Framework  SKIPPED
[INFO] Brooklyn OSGi init . SKIPPED
[INFO] Brooklyn Karaf . SKIPPED
[INFO] Jetty config fragment .. SKIPPED
[INFO] Brooklyn Karaf Features  SKIPPED
[INFO] Brooklyn Karaf Distro .. SKIPPED
[INFO] Brooklyn Karaf Shell Commands .. SKIPPED
[INFO] Brooklyn Karaf pax-exam itest .. 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 Downstream Project Parent . SKIPPED
[INFO] Brooklyn Dist Root . SKIPPED
[INFO] Brooklyn All Things  SKIPPED
[INFO] Brooklyn Distribution .. SKIPPED
[INFO] Brooklyn Vagrant Getting Started Environment ... SKIPPED
[INFO] Brooklyn Quick-Start Project Archetype . SKIPPED
[INFO] Brooklyn Root .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 51:19 min
[INFO] Finished at: 2016-04-06T03:40:51+01:00
[INFO] Final Memory: 128M/474M
[INFO] 
Waiting for Jenkins to finish collecting data
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on 
project brooklyn-launcher: Execution default-test of goal 
org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test failed: The forked 
VM terminated without properly saying goodbye. VM crash or System.exit called?
[ERROR] Command was cmd.exe /X /C 
"f:\hudson\tools\java\latest-1.7-64\jre\bin\java -Xms768m 

[jira] [Commented] (BROOKLYN-249) errors using external config for JcloudsLocation

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/BROOKLYN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226706#comment-15226706
 ] 

ASF GitHub Bot commented on BROOKLYN-249:
-

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

https://github.com/apache/brooklyn-server/pull/103#discussion_r58579137
  
--- Diff: 
core/src/test/java/org/apache/brooklyn/location/byon/ByonLocationResolverRebindTest.java
 ---
@@ -0,0 +1,69 @@
+/*
+ * 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 org.apache.brooklyn.location.byon;
+
+import static org.testng.Assert.assertEquals;
+import static org.testng.Assert.assertTrue;
+
+import org.apache.brooklyn.api.location.LocationSpec;
+import org.apache.brooklyn.api.location.MachineLocation;
+import org.apache.brooklyn.api.location.MachineProvisioningLocation;
+import org.apache.brooklyn.core.mgmt.rebind.RebindTestFixtureWithApp;
+import org.apache.brooklyn.location.ssh.SshMachineLocation;
+import org.testng.annotations.Test;
+
+import com.google.common.collect.ImmutableMap;
+
+public class ByonLocationResolverRebindTest extends 
RebindTestFixtureWithApp {
--- End diff --

This should have been included in 
https://github.com/apache/brooklyn-server/pull/91, but was accidentally missed 
out!

Not quite appropriate to include it in this commit, but no big deal in my 
opinion.


> errors using external config for JcloudsLocation
> 
>
> Key: BROOKLYN-249
> URL: https://issues.apache.org/jira/browse/BROOKLYN-249
> Project: Brooklyn
>  Issue Type: Bug
>Reporter: Aled Sage
>
> Using 0.10.0-SNAPSHOT (also affecting 0.9.0-rc2), I hit problems using 
> external config with JcloudsLocation.
> First it failed to resolve the external config for the ssh publicKeyData and 
> privateKeyData.
> After fixing that, it failed to rebind to my persisted state that included 
> the external config in the location (it tried to coerce the 
> {{DeferredSupplier}} to a String).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [CANCEL][VOTE] Release Apache Brooklyn 0.9.0 [rc2]

[Aled Sage]

Thanks all.

John has fixed this [1]. I'll review, merge, and cherry-pick to the 
0.9.0 branch.


Given we are producing another release candidate anyway, can we include 
the fix for BROOKLYN-249 (see [2,3]). Can someone please review that and 
give their opinion for whether it should be included in the 0.9.0 release?


Aled

[1] https://github.com/apache/brooklyn-server/pull/102
[2] https://issues.apache.org/jira/browse/BROOKLYN-249
[3] https://github.com/apache/brooklyn-server/pull/103


On 05/04/2016 10:30, John McCabe wrote:

Note that it also breaks the add location wizard in jsgui.

On Tue, 5 Apr 2016 at 10:26 Richard Downer  wrote:


After discussing with John, I agree that BROOKLYN-246 is a blocker.
The catalog file that the Brooklyn Vagrant distributable uses is using
the broken format, so it won't work - and we really don't want our
simplest-possible-get-started to require manual modifications before
it'll work. It also breaks the documented way of using BYON[1] so we
are at high risk of breaking user's working configurations.

Therefore due to this critical bug, I am cancelling the vote.

Richard.

[1]https://brooklyn.apache.org/v/latest/ops/locations/index.html#byon

On 4 April 2016 at 18:11, John McCabe  wrote:

@all, I hit an issue with location handling while following up on @svets
comments - https://issues.apache.org/jira/browse/BROOKLYN-246

Looks like a blocker.

On Mon, 4 Apr 2016 at 14:35 John McCabe  wrote:


@svet, latest isn't required, 1.8+ should suffice.

On Mon, 4 Apr 2016 at 12:53 Svetoslav Neykov <
svetoslav.ney...@cloudsoftcorp.com> wrote:


+1 binding

* Tested the .zip & .tar.gz dists
* Tested CLI
* Tried a simple blueprint
* Tested the vagrant artifact - "vagrant up" *fails* because it's

looking

at the release url


https://www.apache.org/dyn/closer.lua?action=download=brooklyn/apache-brooklyn-0.9.0/apache-brooklyn-0.9.0-bin.tar.gz

<


https://www.apache.org/dyn/closer.lua?action=download=brooklyn/apache-brooklyn-0.9.0/apache-brooklyn-0.9.0-bin.tar.gz

.

Once released should work.
Unrelated, but do we require the absolute latest vagrant version on
purpose? Can we relax this version requirement?

Svet.



On 4.04.2016 г., at 13:14, Sam Corbett <

sam.corb...@cloudsoftcorp.com>

wrote:

+1 binding

I have:
* Verified release signatures
* Built from the source archive
* Generated a project from the archetype
* Verified all subsequent archetype instructions were correct
* Verified a simple application deployed to AWS.
* Given the CLI a work out.


On 01/04/2016 16:58, Richard Downer wrote:

This is to call for a vote for the release of Apache Brooklyn 0.9.0

[rc2].

This release comprises of a source code distribution, and a
corresponding binary distribution, RPM packages, Vagrant environment
package, and Maven artifacts.

The source and binary distributions, including signatures, digests,
etc. can be found at:


https://dist.apache.org/repos/dist/dev/brooklyn/apache-brooklyn-0.9.0-rc2

The artifact SHA-256 checksums are as follows:
426ca93aad28ac8281b2015fc0ea419cd6db19c3ed87ffd11910a6baf2e9e3ab
*apache-brooklyn-0.9.0-rc2-1.noarch.rpm
b2a65642fb86198b9fd9992ef3464025d9b41c453c4dd5366699d569a65709c6
*apache-brooklyn-0.9.0-rc2-bin.tar.gz
999fd6f1d21417278ffe153fc1f0346d44235dfbbd39f200815f61cea82edbe5
*apache-brooklyn-0.9.0-rc2-bin.zip
00e0a76775775957e92498d0b5ea3e13f844155eda3251a8ead05cf4b4a4455b
*apache-brooklyn-0.9.0-rc2-src.tar.gz
c7a9a286993b1d520ae6a32e25c0dd3bef7227290d59347256bd96480b70a02b
*apache-brooklyn-0.9.0-rc2-src.zip
907267c5d2e7c1622e11f2bc57b6afe12ddf2136d82bad63661e43570aaa78fa
*apache-brooklyn-0.9.0-rc2-vagrant.tar.gz
0ae8384426d6b7197ca3d194c1e8032b85c5bb80671157c274487220d3ba65e9
*apache-brooklyn-0.9.0-rc2-vagrant.zip

The Nexus staging repositories for the Maven artifacts are located

at:
https://repository.apache.org/content/repositories/orgapachebrooklyn-1016
https://repository.apache.org/content/repositories/orgapachebrooklyn-1017

All release artifacts are signed with the following key:
https://people.apache.org/keys/committer/richard.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/brooklyn/KEYS

The artifacts were built from these Git commit IDs:
brooklyn: acc8ff1930d243d2a5fae1ad2f1a1ef17ca4a19c
brooklyn-client: 64573c8e1b8630f59b23356520282c91cc46a8a1
brooklyn-dist: 0b8b81df458fa4323939582d9f0dda10b2f6eaee
brooklyn-docs: 12430d193e1891b87a677d6b45a3b17861c83518
brooklyn-library: 2565e6eb2868468ec2528df74fe85efdb887b6d2
brooklyn-server: d031cea080613645219ba982c93264943798d4fc
brooklyn-ui: 307382128951bb237bc351ac22136745e5d50475
All of the above have been tagged as "apache-brooklyn-0.9.0-rc2".


Please download the artifacts, test, and vote on releasing this
package as Apache Brooklyn 0.9.0.

The vote will be open for at least 72 hours.
[ ] +1 Release this package as Apache Brooklyn 0.9.0 (please

describe

the tests you have performed)
[ ] +0 no 

[GitHub] brooklyn-server pull request: Fix BROOKLYN-249

[aledsage]

GitHub user aledsage opened a pull request:

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

Fix BROOKLYN-249

See more detailed descriptions in each commit message.

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

$ git pull https://github.com/aledsage/brooklyn-server fix/BROOKLYN-249

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

https://github.com/apache/brooklyn-server/pull/103.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 #103


commit 99dd3ba4fc507988bdecd4e57c2b36cbb465b2a5
Author: Aled Sage 
Date:   2016-04-05T16:58:31Z

BROOKLYN-249: JcloudsLocation resolves external config

Previously we were just resolving it for identity/credential in 
getComputeService(). Now we resolve it for everything that obtain()
does.

commit ee3159bf4e94a1ef9a32c8c5c46a790be2c56146
Author: Aled Sage 
Date:   2016-04-05T16:59:03Z

Trim publicKeyData

Otherwise get incorrect warning about the publicKey not matching
the privateKey.

commit b35ec4aabbcc2fe2dc07f1b1cc23a0f92d3d9155
Author: Aled Sage 
Date:   2016-04-05T17:00:21Z

BROOKLYN-249: fix location rebind for external config

Fixes it only for ConfigKeys, rather than for fields that use
`@SetFromFlag`. The latter can be addressed in a separate pull request.

commit 6fd90b6c1d097ff18c18bcea321bccb94897efbf
Author: Aled Sage 
Date:   2016-04-05T17:05:43Z

BROOKLYN-249: test JcloudsLocation external config




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

[jira] [Commented] (BROOKLYN-249) errors using external config for JcloudsLocation

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/BROOKLYN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226671#comment-15226671
 ] 

ASF GitHub Bot commented on BROOKLYN-249:
-

GitHub user aledsage opened a pull request:

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

Fix BROOKLYN-249

See more detailed descriptions in each commit message.

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

$ git pull https://github.com/aledsage/brooklyn-server fix/BROOKLYN-249

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

https://github.com/apache/brooklyn-server/pull/103.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 #103


commit 99dd3ba4fc507988bdecd4e57c2b36cbb465b2a5
Author: Aled Sage 
Date:   2016-04-05T16:58:31Z

BROOKLYN-249: JcloudsLocation resolves external config

Previously we were just resolving it for identity/credential in 
getComputeService(). Now we resolve it for everything that obtain()
does.

commit ee3159bf4e94a1ef9a32c8c5c46a790be2c56146
Author: Aled Sage 
Date:   2016-04-05T16:59:03Z

Trim publicKeyData

Otherwise get incorrect warning about the publicKey not matching
the privateKey.

commit b35ec4aabbcc2fe2dc07f1b1cc23a0f92d3d9155
Author: Aled Sage 
Date:   2016-04-05T17:00:21Z

BROOKLYN-249: fix location rebind for external config

Fixes it only for ConfigKeys, rather than for fields that use
`@SetFromFlag`. The latter can be addressed in a separate pull request.

commit 6fd90b6c1d097ff18c18bcea321bccb94897efbf
Author: Aled Sage 
Date:   2016-04-05T17:05:43Z

BROOKLYN-249: test JcloudsLocation external config




> errors using external config for JcloudsLocation
> 
>
> Key: BROOKLYN-249
> URL: https://issues.apache.org/jira/browse/BROOKLYN-249
> Project: Brooklyn
>  Issue Type: Bug
>Reporter: Aled Sage
>
> Using 0.10.0-SNAPSHOT (also affecting 0.9.0-rc2), I hit problems using 
> external config with JcloudsLocation.
> First it failed to resolve the external config for the ssh publicKeyData and 
> privateKeyData.
> After fixing that, it failed to rebind to my persisted state that included 
> the external config in the location (it tried to coerce the 
> {{DeferredSupplier}} to a String).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (BROOKLYN-249) errors using external config for JcloudsLocation

[Aled Sage (JIRA)]

Aled Sage created BROOKLYN-249:
--

 Summary: errors using external config for JcloudsLocation
 Key: BROOKLYN-249
 URL: https://issues.apache.org/jira/browse/BROOKLYN-249
 Project: Brooklyn
  Issue Type: Bug
Reporter: Aled Sage


Using 0.10.0-SNAPSHOT (also affecting 0.9.0-rc2), I hit problems using external 
config with JcloudsLocation.

First it failed to resolve the external config for the ssh publicKeyData and 
privateKeyData.

After fixing that, it failed to rebind to my persisted state that included the 
external config in the location (it tried to coerce the {{DeferredSupplier}} to 
a String).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] brooklyn-server pull request: Don't force binding to 127.0.0.1 whe...

[neykov]

Github user neykov commented on the pull request:

https://github.com/apache/brooklyn-server/pull/101#issuecomment-205888283
  
@johnmccabe It's meant as a simple copy aid (or click for terminals 
that support it). So better to use a real address.


---
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: Don't force binding to 127.0.0.1 whe...

[johnmccabe]

Github user johnmccabe commented on the pull request:

https://github.com/apache/brooklyn-server/pull/101#issuecomment-205885095
  
@neykov I'm seeing it bind to all interfaces as expected now, but we still 
see the loopback logged to the console. I can't recall seeing it log that its 
bound to all interfaces in the past but it might be nice to show that for 
correctness.


---
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: pass brooklynConfig when making call...

[johnmccabe]

Github user johnmccabe commented on the pull request:

https://github.com/apache/brooklyn-server/pull/102#issuecomment-205865191
  
fyi @aledsage @rdowner @neykov 


---
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-client pull request: Update build so that it includes onl...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-client/pull/14


---
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-client pull request: Update documented required Go versio...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-client/pull/15


---
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: Don't force binding to 127.0.0.1 whe...

[neykov]

GitHub user neykov opened a pull request:

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

Don't force binding to 127.0.0.1 when using AnyoneSecurityProvider

Keeps backwards compatibility - using AnyoneSecurityProvider wouldn't force 
brooklyn server to bind to loopback only, but then changed to being treated 
same as noSecurityProvider. Revert to initial behaviour.

/cc @johnmccabe 

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

$ git pull https://github.com/neykov/brooklyn-server fix/skip-security

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

https://github.com/apache/brooklyn-server/pull/101.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 #101






---
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-client pull request: remove brooklyn-client Godep from re...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-client/pull/11


---
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-client pull request: remove brooklyn-client Godep from re...

[neykov]

Github user neykov commented on the pull request:

https://github.com/apache/brooklyn-client/pull/11#issuecomment-205828973
  
Thanks @johnmccabe, merging.


---
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: Populate catalog from bundle bom

[geomacy]

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

https://github.com/apache/brooklyn-server/pull/80#discussion_r58542079
  
--- Diff: karaf/init/src/main/resources/OSGI-INF/blueprint/blueprint.xml ---
@@ -20,63 +20,63 @@ limitations under the License.

xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.2.0;
xsi:schemaLocation="
  http://www.osgi.org/xmlns/blueprint/v1.0.0 
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
- 
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.1.0.xsd
+ http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.2.0 
http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.2.0.xsd
  ">
 
 
 
--- End diff --

Me too! not sure how I managed that.


---
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: Populate catalog from bundle bom

[geomacy]

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

https://github.com/apache/brooklyn-server/pull/80#discussion_r58541474
  
--- Diff: core/src/main/resources/catalog.bom ---
@@ -0,0 +1,21 @@
+# 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.
+
+brooklyn.catalog:
--- End diff --

They would be handled better by the build, but I think this would require a 
moderately significant amount of work, to scan the code for the appropriate 
annotations, which I think would be best treated as a separate bit of 
development.


---
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: Support removal of catalog entries f...

[geomacy]

GitHub user geomacy opened a pull request:

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

Support removal of catalog entries from bundle BOM when the bundle is 
stopped.


This change follows on from 
https://github.com/apache/brooklyn-server/pull/80.

With this change any catalog members that were added by scanning the 
bundle's
catalog.bom when the bundle started will be removed upon stopping the 
bundle.

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

$ git pull https://github.com/geomacy/brooklyn-server 
prune-catalog-on-bundle-stop

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

https://github.com/apache/brooklyn-server/pull/100.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 #100


commit 7a1d51c6c9d0ea084ad09be51a27dec06fb0d365
Author: Geoff Macartney 
Date:   2016-04-05T13:22:05Z

Support removal of catalog entries from bundle BOM when the bundle is 
stopped.

This change follows on from 
https://github.com/apache/brooklyn-server/pull/80.

With this change any catalog members that were added by scanning the 
bundle's
catalog.bom when the bundle started will be removed upon stopping the 
bundle.




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

[jira] [Created] (BROOKLYN-247) Unreliable test: EntityExecutionManagerTest.testGetTasksAndGcBoringTags

[Sam Corbett (JIRA)]

Sam Corbett created BROOKLYN-247:


 Summary: Unreliable test: 
EntityExecutionManagerTest.testGetTasksAndGcBoringTags
 Key: BROOKLYN-247
 URL: https://issues.apache.org/jira/browse/BROOKLYN-247
 Project: Brooklyn
  Issue Type: Bug
Reporter: Sam Corbett


Failed in https://builds.apache.org/job/brooklyn-server-pull-requests/283.

Log from test:
{code}
2016-04-05 11:36:40,973 INFO  TESTNG INVOKING CONFIGURATION: "Surefire test" - 
@BeforeMethod 
org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.setUp()
2016-04-05 11:36:40,973 INFO  TESTNG PASSED CONFIGURATION: "Surefire test" - 
@BeforeMethod 
org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.setUp() 
finished in 0 ms
2016-04-05 11:36:40,974 INFO  TESTNG INVOKING: "Surefire test" - 
org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.testGetTasksAndGcBoringTags()
2016-04-05 11:36:41,045 INFO  TESTNG FAILED: "Surefire test" - 
org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.testGetTasksAndGcBoringTags()
 finished in 69 ms
java.lang.AssertionError: Tasks were [Task[should-be-kept]@OG4fEF4y, 
Task[should-be-gcd]@InYWSGnl] expected [1] but found [2]
at 
org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest$2.call(EntityExecutionManagerTest.java:150)
at 
org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest$2.call(EntityExecutionManagerTest.java:145)
at 
org.apache.brooklyn.util.repeat.Repeater.runKeepingError(Repeater.java:332)
at 
org.apache.brooklyn.util.repeat.Repeater.runRequiringTrue(Repeater.java:303)
at 
org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.assertTaskCountForEntitySoon(EntityExecutionManagerTest.java:145)
at 
org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.testGetTasksAndGcBoringTags(EntityExecutionManagerTest.java:164)
2016-04-05 11:36:41,055 INFO  TESTNG INVOKING CONFIGURATION: "Surefire test" - 
@AfterMethod 
org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.tearDown()
2016-04-05 11:36:41,067 INFO  TESTNG PASSED CONFIGURATION: "Surefire test" - 
@AfterMethod 
org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.tearDown() 
finished in 12 ms
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] brooklyn-server pull request: Rest API location transformers use m...

[neykov]

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

https://github.com/apache/brooklyn-server/pull/99#discussion_r58533880
  
--- Diff: 
rest/rest-api/src/main/java/org/apache/brooklyn/rest/domain/LocationSpec.java 
---
@@ -53,7 +54,7 @@ public LocationSpec(
 @JsonProperty("config") @Nullable Map config) {
 this.name = name;
 this.spec = spec;
-this.config = (config == null) ? Collections. 
emptyMap() : ImmutableMap.copyOf(config);
+this.config = (config == null) ? Collections. 
emptyMap() : MutableMap.copyOf(config);
--- End diff --

(minor) could add `asUnmodifiable` or `asImmutableCopy` to keep the 
immutability.


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

[jira] [Commented] (BROOKLYN-247) Unreliable test: EntityExecutionManagerTest.testGetTasksAndGcBoringTags

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/BROOKLYN-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226211#comment-15226211
 ] 

ASF GitHub Bot commented on BROOKLYN-247:
-

Github user sjcorbett commented on the pull request:

https://github.com/apache/brooklyn-server/pull/99#issuecomment-205792423
  
Test failure unrelated. Filed at 
https://issues.apache.org/jira/browse/BROOKLYN-247. Trying again.


> Unreliable test: EntityExecutionManagerTest.testGetTasksAndGcBoringTags
> ---
>
> Key: BROOKLYN-247
> URL: https://issues.apache.org/jira/browse/BROOKLYN-247
> Project: Brooklyn
>  Issue Type: Bug
>Reporter: Sam Corbett
>
> Failed in https://builds.apache.org/job/brooklyn-server-pull-requests/283.
> Log from test:
> {code}
> 2016-04-05 11:36:40,973 INFO  TESTNG INVOKING CONFIGURATION: "Surefire test" 
> - @BeforeMethod 
> org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.setUp()
> 2016-04-05 11:36:40,973 INFO  TESTNG PASSED CONFIGURATION: "Surefire test" - 
> @BeforeMethod 
> org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.setUp() 
> finished in 0 ms
> 2016-04-05 11:36:40,974 INFO  TESTNG INVOKING: "Surefire test" - 
> org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.testGetTasksAndGcBoringTags()
> 2016-04-05 11:36:41,045 INFO  TESTNG FAILED: "Surefire test" - 
> org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.testGetTasksAndGcBoringTags()
>  finished in 69 ms
> java.lang.AssertionError: Tasks were [Task[should-be-kept]@OG4fEF4y, 
> Task[should-be-gcd]@InYWSGnl] expected [1] but found [2]
>   at 
> org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest$2.call(EntityExecutionManagerTest.java:150)
>   at 
> org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest$2.call(EntityExecutionManagerTest.java:145)
>   at 
> org.apache.brooklyn.util.repeat.Repeater.runKeepingError(Repeater.java:332)
>   at 
> org.apache.brooklyn.util.repeat.Repeater.runRequiringTrue(Repeater.java:303)
>   at 
> org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.assertTaskCountForEntitySoon(EntityExecutionManagerTest.java:145)
>   at 
> org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.testGetTasksAndGcBoringTags(EntityExecutionManagerTest.java:164)
> 2016-04-05 11:36:41,055 INFO  TESTNG INVOKING CONFIGURATION: "Surefire test" 
> - @AfterMethod 
> org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.tearDown()
> 2016-04-05 11:36:41,067 INFO  TESTNG PASSED CONFIGURATION: "Surefire test" - 
> @AfterMethod 
> org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.tearDown() 
> finished in 12 ms
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] brooklyn-server pull request: Rest API location transformers use m...

[sjcorbett]

Github user sjcorbett closed the pull request at:

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


---
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: Rest API location transformers use m...

[sjcorbett]

GitHub user sjcorbett reopened a pull request:

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

Rest API location transformers use mutable map

LocationConfig contains null values which Guava's ImmutableMap rejects with 
a NullPointerException.

This fixes an error observed when deploying the "Template 1: Server" sample 
to localhost then running `br application ` with the CLI. The output from 
the CLI was "500 Server Error". The server logs contained:

```
java.lang.NullPointerException: null value in entry: byon.machineSpecs=null
at 
com.google.common.collect.CollectPreconditions.checkEntryNotNull(CollectPreconditions.java:33)
 ~[com.google.guava-guava-16.0.1.jar:na]
at 
com.google.common.collect.ImmutableMap.entryOf(ImmutableMap.java:135) 
~[com.google.guava-guava-16.0.1.jar:na]
at 
com.google.common.collect.ImmutableMap$Builder.put(ImmutableMap.java:206) 
~[com.google.guava-guava-16.0.1.jar:na]
at 
org.apache.brooklyn.rest.transform.LocationTransformer.copyConfig(LocationTransformer.java:128)
 
~[org.apache.brooklyn-brooklyn-rest-resources-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
at 
org.apache.brooklyn.rest.transform.LocationTransformer.newInstance(LocationTransformer.java:189)
 
~[org.apache.brooklyn-brooklyn-rest-resources-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
at 
org.apache.brooklyn.rest.resources.LocationResource.get(LocationResource.java:139)
 
~[org.apache.brooklyn-brooklyn-rest-resources-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
at 
org.apache.brooklyn.rest.resources.LocationResource.get(LocationResource.java:132)
 
~[org.apache.brooklyn-brooklyn-rest-resources-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
~[na:1.8.0_05]

```

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

$ git pull https://github.com/sjcorbett/brooklyn-server fix/location-spec

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

https://github.com/apache/brooklyn-server/pull/99.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 #99


commit 067c208fc3e23658dc757dcc5c203c6dab928482
Author: Sam Corbett 
Date:   2016-04-05T11:25:46Z

Rest API location transformers use mutable map

LocationConfig contains null values which Guava's ImmutableMap rejects
with a NullPointerException




---
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: Rest API location transformers use m...

[sjcorbett]

Github user sjcorbett commented on the pull request:

https://github.com/apache/brooklyn-server/pull/99#issuecomment-205792423
  
Test failure unrelated. Filed at 
https://issues.apache.org/jira/browse/BROOKLYN-247. Trying again.


---
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-dist pull request: lower minimum Vagrant version to 1.8.0

[neykov]

Github user neykov commented on the pull request:

https://github.com/apache/brooklyn-dist/pull/30#issuecomment-205791607
  
Testing on OS X now. Turns out that virtualbox can't run inside another VM. 
Other than that the host shouldn't make a difference.

Removing the failing `vagrant-catalog.bom` allowed me to start brooklyn. 
It's listening on `127.0.0.1:8081` only. Can't connect to it on the 
`10.10.10.x` network. The port is not mapped on the NAT interface as well (no 
`forwarded_ports` section inside the yaml).


---
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-dist pull request: lower minimum Vagrant version to 1.8.0

[johnmccabe]

Github user johnmccabe commented on the pull request:

https://github.com/apache/brooklyn-dist/pull/30#issuecomment-205784061
  
@neykov Ubuntu 14.04 again?

Interesting tweak to the nics!!


---
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-client pull request: remove brooklyn-client Godep from re...

[johnmccabe]

Github user johnmccabe commented on the pull request:

https://github.com/apache/brooklyn-client/pull/11#issuecomment-205783233
  
@neykov that change wasn't carried out at the time (see 
[comment](https://github.com/apache/brooklyn-client/pull/11#issuecomment-199831958),
 the PR as-is allows the client to build as expected pending the 1.6 vendoring 
support @geomacy plans to add - suggest we merge in its absence.


---
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-dist pull request: lower minimum Vagrant version to 1.8.0

[neykov]

Github user neykov commented on the pull request:

https://github.com/apache/brooklyn-dist/pull/30#issuecomment-205778386
  
Getting the following error when testing with `1.8.0`
```
==> brooklyn: Destroying VM and associated drives...

/opt/vagrant/embedded/gems/gems/vagrant-1.8.0/plugins/provisioners/shell/provisioner.rb:162:in
 `quote_and_escape': undefined method `gsub' for false:FalseClass 
(NoMethodError)
from 
/opt/vagrant/embedded/gems/gems/vagrant-1.8.0/plugins/provisioners/shell/provisioner.rb:50:in
 `block in provision_ssh'
from 
/opt/vagrant/embedded/gems/gems/vagrant-1.8.0/plugins/provisioners/shell/provisioner.rb:50:in
 `each'
from 
/opt/vagrant/embedded/gems/gems/vagrant-1.8.0/plugins/provisioners/shell/provisioner.rb:50:in
 `map'
from 
/opt/vagrant/embedded/gems/gems/vagrant-1.8.0/plugins/provisioners/shell/provisioner.rb:50:in
 `provision_ssh'
```

Related to https://github.com/mitchellh/vagrant/issues/6707. Needed to 
convert the `false` in the env section to a string by quoting it.

Also updating the packages takes forever, adding the following to 
`Vagrantfile` speeds it up considerably.
```
vb.customize ["modifyvm", :id, "--nictype1", "virtio"]
vb.customize ["modifyvm", :id, "--nictype2", "virtio"]
```

Still waiting for the `up` to complete, will report with the result.


---
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: Rest API location transformers use m...

[sjcorbett]

GitHub user sjcorbett opened a pull request:

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

Rest API location transformers use mutable map

LocationConfig contains null values which Guava's ImmutableMap rejects with 
a NullPointerException.

This fixes an error observed when deploying the "Template 1: Server" sample 
to localhost then running `br application ` with the CLI. The output from 
the CLI was "500 Server Error". The server logs contained:

```
java.lang.NullPointerException: null value in entry: byon.machineSpecs=null
at 
com.google.common.collect.CollectPreconditions.checkEntryNotNull(CollectPreconditions.java:33)
 ~[com.google.guava-guava-16.0.1.jar:na]
at 
com.google.common.collect.ImmutableMap.entryOf(ImmutableMap.java:135) 
~[com.google.guava-guava-16.0.1.jar:na]
at 
com.google.common.collect.ImmutableMap$Builder.put(ImmutableMap.java:206) 
~[com.google.guava-guava-16.0.1.jar:na]
at 
org.apache.brooklyn.rest.transform.LocationTransformer.copyConfig(LocationTransformer.java:128)
 
~[org.apache.brooklyn-brooklyn-rest-resources-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
at 
org.apache.brooklyn.rest.transform.LocationTransformer.newInstance(LocationTransformer.java:189)
 
~[org.apache.brooklyn-brooklyn-rest-resources-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
at 
org.apache.brooklyn.rest.resources.LocationResource.get(LocationResource.java:139)
 
~[org.apache.brooklyn-brooklyn-rest-resources-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
at 
org.apache.brooklyn.rest.resources.LocationResource.get(LocationResource.java:132)
 
~[org.apache.brooklyn-brooklyn-rest-resources-0.10.0-SNAPSHOT.jar:0.10.0-SNAPSHOT]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
~[na:1.8.0_05]

```

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

$ git pull https://github.com/sjcorbett/brooklyn-server fix/location-spec

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

https://github.com/apache/brooklyn-server/pull/99.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 #99


commit 067c208fc3e23658dc757dcc5c203c6dab928482
Author: Sam Corbett 
Date:   2016-04-05T11:25:46Z

Rest API location transformers use mutable map

LocationConfig contains null values which Guava's ImmutableMap rejects
with a NullPointerException




---
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-dist pull request: lower minimum Vagrant version to 1.8.0

[neykov]

Github user neykov commented on the pull request:

https://github.com/apache/brooklyn-dist/pull/30#issuecomment-205753420
  
I tested on Ubuntu 14.04. Btw by default it install `1.4.3` :).


---
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-dist pull request: lower minimum Vagrant version to 1.7.0

[johnmccabe]

Github user johnmccabe commented on the pull request:

https://github.com/apache/brooklyn-dist/pull/30#issuecomment-205750915
  
Hmm, looks like my 1.8.1 hadn't been blown away, was in 
`/usr/local/bin/vagrant` rather than the `/usr/bin/vagrant` that the Vagrant 
docs on uninstallation refer to..

Regarding getting rid of env, I'd don't think we should do that to cater to 
users running obsolete versions


---
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-dist pull request: lower minimum Vagrant version to 1.7.0

[neykov]

Github user neykov commented on the pull request:

https://github.com/apache/brooklyn-dist/pull/30#issuecomment-205744736
  
Tested with vagrant `1.7.0`. It's failing with `The following settings 
shouldn't exist: env`. Seems this was introduced in 1.8.0. So either need to 
move away from using env or bump the version to `1.8.0`.


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

[jira] [Commented] (BROOKLYN-246) Unable to add byon locations

[John McCabe (JIRA)]

[ 
https://issues.apache.org/jira/browse/BROOKLYN-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15225993#comment-15225993
 ] 

John McCabe commented on BROOKLYN-246:
--

Likewise for the Vagrant location bom, it had been working in previous weeks.

> Unable to add byon locations
> 
>
> Key: BROOKLYN-246
> URL: https://issues.apache.org/jira/browse/BROOKLYN-246
> Project: Brooklyn
>  Issue Type: Bug
>Affects Versions: 0.9.0
>Reporter: John McCabe
>Priority: Blocker
>
> Running both the most recent 0.9.0-SNAPSHOT dist from maven and a freshly 
> build 0.10.0-SNAPSHOT from master I'm seeing the following behaviour.
> 1. Attempting to add a BYON location via jsgui is rejected with the following 
> error:
> {code}
> Could not resolve item 'testingid': Transformer for Brooklyn OASIS CAMP 
> interpreter gave an error creating this plan: No class or resolver found for 
> location type byon
> {code}
> 2. Trying the the generated JSON via the composer also fails:
> {code}
> brooklyn.catalog:
>   version: 0.0.1
>   items:
>   - id: testingid
> itemType: location
> item:
>   type: byon
>   brooklyn.config:
> displayName: testingdisplayName
> user: testinguser
> password: testingpassword
> privateKeyFile: testingprivateKeyFile
> privateKeyPassphrase: testingprivateKeyPassphrase
> hosts:
> - 10.10.10.102
> {code}
> 3. *BUT* this works:
> {code}
> brooklyn.catalog:
>   version: 0.0.1
>   items:
>   - id: testingid
> itemType: location
> item:
>   type: byon:(hosts="10.10.10.102")
>   brooklyn.config:
> displayName: testingdisplayName
> user: testinguser
> password: testingpassword
> privateKeyFile: testingprivateKeyFile
> privateKeyPassphrase: testingprivateKeyPassphrase
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (BROOKLYN-246) Unable to add byon locations

[Thomas Bouron (JIRA)]

[ 
https://issues.apache.org/jira/browse/BROOKLYN-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15225989#comment-15225989
 ] 

Thomas Bouron commented on BROOKLYN-246:


When I added the location wizard, the first format of location described in the 
issue worked during my tests. So the bug probably comes from something merged 
at the same time or after.

> Unable to add byon locations
> 
>
> Key: BROOKLYN-246
> URL: https://issues.apache.org/jira/browse/BROOKLYN-246
> Project: Brooklyn
>  Issue Type: Bug
>Affects Versions: 0.9.0
>Reporter: John McCabe
>Priority: Blocker
>
> Running both the most recent 0.9.0-SNAPSHOT dist from maven and a freshly 
> build 0.10.0-SNAPSHOT from master I'm seeing the following behaviour.
> 1. Attempting to add a BYON location via jsgui is rejected with the following 
> error:
> {code}
> Could not resolve item 'testingid': Transformer for Brooklyn OASIS CAMP 
> interpreter gave an error creating this plan: No class or resolver found for 
> location type byon
> {code}
> 2. Trying the the generated JSON via the composer also fails:
> {code}
> brooklyn.catalog:
>   version: 0.0.1
>   items:
>   - id: testingid
> itemType: location
> item:
>   type: byon
>   brooklyn.config:
> displayName: testingdisplayName
> user: testinguser
> password: testingpassword
> privateKeyFile: testingprivateKeyFile
> privateKeyPassphrase: testingprivateKeyPassphrase
> hosts:
> - 10.10.10.102
> {code}
> 3. *BUT* this works:
> {code}
> brooklyn.catalog:
>   version: 0.0.1
>   items:
>   - id: testingid
> itemType: location
> item:
>   type: byon:(hosts="10.10.10.102")
>   brooklyn.config:
> displayName: testingdisplayName
> user: testinguser
> password: testingpassword
> privateKeyFile: testingprivateKeyFile
> privateKeyPassphrase: testingprivateKeyPassphrase
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [CANCEL][VOTE] Release Apache Brooklyn 0.9.0 [rc2]

[John McCabe]

Note that it also breaks the add location wizard in jsgui.

On Tue, 5 Apr 2016 at 10:26 Richard Downer  wrote:

> After discussing with John, I agree that BROOKLYN-246 is a blocker.
> The catalog file that the Brooklyn Vagrant distributable uses is using
> the broken format, so it won't work - and we really don't want our
> simplest-possible-get-started to require manual modifications before
> it'll work. It also breaks the documented way of using BYON[1] so we
> are at high risk of breaking user's working configurations.
>
> Therefore due to this critical bug, I am cancelling the vote.
>
> Richard.
>
> [1]https://brooklyn.apache.org/v/latest/ops/locations/index.html#byon
>
> On 4 April 2016 at 18:11, John McCabe  wrote:
> > @all, I hit an issue with location handling while following up on @svets
> > comments - https://issues.apache.org/jira/browse/BROOKLYN-246
> >
> > Looks like a blocker.
> >
> > On Mon, 4 Apr 2016 at 14:35 John McCabe  wrote:
> >
> >> @svet, latest isn't required, 1.8+ should suffice.
> >>
> >> On Mon, 4 Apr 2016 at 12:53 Svetoslav Neykov <
> >> svetoslav.ney...@cloudsoftcorp.com> wrote:
> >>
> >>> +1 binding
> >>>
> >>> * Tested the .zip & .tar.gz dists
> >>> * Tested CLI
> >>> * Tried a simple blueprint
> >>> * Tested the vagrant artifact - "vagrant up" *fails* because it's
> looking
> >>> at the release url
> >>>
> https://www.apache.org/dyn/closer.lua?action=download=brooklyn/apache-brooklyn-0.9.0/apache-brooklyn-0.9.0-bin.tar.gz
> >>> <
> >>>
> https://www.apache.org/dyn/closer.lua?action=download=brooklyn/apache-brooklyn-0.9.0/apache-brooklyn-0.9.0-bin.tar.gz
> >.
> >>> Once released should work.
> >>>Unrelated, but do we require the absolute latest vagrant version on
> >>> purpose? Can we relax this version requirement?
> >>>
> >>> Svet.
> >>>
> >>>
> >>> > On 4.04.2016 г., at 13:14, Sam Corbett <
> sam.corb...@cloudsoftcorp.com>
> >>> wrote:
> >>> >
> >>> > +1 binding
> >>> >
> >>> > I have:
> >>> > * Verified release signatures
> >>> > * Built from the source archive
> >>> > * Generated a project from the archetype
> >>> > * Verified all subsequent archetype instructions were correct
> >>> > * Verified a simple application deployed to AWS.
> >>> > * Given the CLI a work out.
> >>> >
> >>> >
> >>> > On 01/04/2016 16:58, Richard Downer wrote:
> >>> >> This is to call for a vote for the release of Apache Brooklyn 0.9.0
> >>> [rc2].
> >>> >>
> >>> >> This release comprises of a source code distribution, and a
> >>> >> corresponding binary distribution, RPM packages, Vagrant environment
> >>> >> package, and Maven artifacts.
> >>> >>
> >>> >> The source and binary distributions, including signatures, digests,
> >>> >> etc. can be found at:
> >>> >>
> >>>
> https://dist.apache.org/repos/dist/dev/brooklyn/apache-brooklyn-0.9.0-rc2
> >>> >>
> >>> >> The artifact SHA-256 checksums are as follows:
> >>> >> 426ca93aad28ac8281b2015fc0ea419cd6db19c3ed87ffd11910a6baf2e9e3ab
> >>> >> *apache-brooklyn-0.9.0-rc2-1.noarch.rpm
> >>> >> b2a65642fb86198b9fd9992ef3464025d9b41c453c4dd5366699d569a65709c6
> >>> >> *apache-brooklyn-0.9.0-rc2-bin.tar.gz
> >>> >> 999fd6f1d21417278ffe153fc1f0346d44235dfbbd39f200815f61cea82edbe5
> >>> >> *apache-brooklyn-0.9.0-rc2-bin.zip
> >>> >> 00e0a76775775957e92498d0b5ea3e13f844155eda3251a8ead05cf4b4a4455b
> >>> >> *apache-brooklyn-0.9.0-rc2-src.tar.gz
> >>> >> c7a9a286993b1d520ae6a32e25c0dd3bef7227290d59347256bd96480b70a02b
> >>> >> *apache-brooklyn-0.9.0-rc2-src.zip
> >>> >> 907267c5d2e7c1622e11f2bc57b6afe12ddf2136d82bad63661e43570aaa78fa
> >>> >> *apache-brooklyn-0.9.0-rc2-vagrant.tar.gz
> >>> >> 0ae8384426d6b7197ca3d194c1e8032b85c5bb80671157c274487220d3ba65e9
> >>> >> *apache-brooklyn-0.9.0-rc2-vagrant.zip
> >>> >>
> >>> >> The Nexus staging repositories for the Maven artifacts are located
> at:
> >>> >>
> >>>
> https://repository.apache.org/content/repositories/orgapachebrooklyn-1016
> >>> >>
> >>>
> https://repository.apache.org/content/repositories/orgapachebrooklyn-1017
> >>> >>
> >>> >> All release artifacts are signed with the following key:
> >>> >> https://people.apache.org/keys/committer/richard.asc
> >>> >>
> >>> >> KEYS file available here:
> >>> >> https://dist.apache.org/repos/dist/release/brooklyn/KEYS
> >>> >>
> >>> >> The artifacts were built from these Git commit IDs:
> >>> >> brooklyn: acc8ff1930d243d2a5fae1ad2f1a1ef17ca4a19c
> >>> >> brooklyn-client: 64573c8e1b8630f59b23356520282c91cc46a8a1
> >>> >> brooklyn-dist: 0b8b81df458fa4323939582d9f0dda10b2f6eaee
> >>> >> brooklyn-docs: 12430d193e1891b87a677d6b45a3b17861c83518
> >>> >> brooklyn-library: 2565e6eb2868468ec2528df74fe85efdb887b6d2
> >>> >> brooklyn-server: d031cea080613645219ba982c93264943798d4fc
> >>> >> brooklyn-ui: 307382128951bb237bc351ac22136745e5d50475
> >>> >> All of the above have been tagged as "apache-brooklyn-0.9.0-rc2".
> >>> >>
> >>> >>
> >>> >> Please download the artifacts, test, and vote on releasing this
> >>> 

[CANCEL][VOTE] Release Apache Brooklyn 0.9.0 [rc2]

[Richard Downer]

After discussing with John, I agree that BROOKLYN-246 is a blocker.
The catalog file that the Brooklyn Vagrant distributable uses is using
the broken format, so it won't work - and we really don't want our
simplest-possible-get-started to require manual modifications before
it'll work. It also breaks the documented way of using BYON[1] so we
are at high risk of breaking user's working configurations.

Therefore due to this critical bug, I am cancelling the vote.

Richard.

[1]https://brooklyn.apache.org/v/latest/ops/locations/index.html#byon

On 4 April 2016 at 18:11, John McCabe  wrote:
> @all, I hit an issue with location handling while following up on @svets
> comments - https://issues.apache.org/jira/browse/BROOKLYN-246
>
> Looks like a blocker.
>
> On Mon, 4 Apr 2016 at 14:35 John McCabe  wrote:
>
>> @svet, latest isn't required, 1.8+ should suffice.
>>
>> On Mon, 4 Apr 2016 at 12:53 Svetoslav Neykov <
>> svetoslav.ney...@cloudsoftcorp.com> wrote:
>>
>>> +1 binding
>>>
>>> * Tested the .zip & .tar.gz dists
>>> * Tested CLI
>>> * Tried a simple blueprint
>>> * Tested the vagrant artifact - "vagrant up" *fails* because it's looking
>>> at the release url
>>> https://www.apache.org/dyn/closer.lua?action=download=brooklyn/apache-brooklyn-0.9.0/apache-brooklyn-0.9.0-bin.tar.gz
>>> <
>>> https://www.apache.org/dyn/closer.lua?action=download=brooklyn/apache-brooklyn-0.9.0/apache-brooklyn-0.9.0-bin.tar.gz>.
>>> Once released should work.
>>>Unrelated, but do we require the absolute latest vagrant version on
>>> purpose? Can we relax this version requirement?
>>>
>>> Svet.
>>>
>>>
>>> > On 4.04.2016 г., at 13:14, Sam Corbett 
>>> wrote:
>>> >
>>> > +1 binding
>>> >
>>> > I have:
>>> > * Verified release signatures
>>> > * Built from the source archive
>>> > * Generated a project from the archetype
>>> > * Verified all subsequent archetype instructions were correct
>>> > * Verified a simple application deployed to AWS.
>>> > * Given the CLI a work out.
>>> >
>>> >
>>> > On 01/04/2016 16:58, Richard Downer wrote:
>>> >> This is to call for a vote for the release of Apache Brooklyn 0.9.0
>>> [rc2].
>>> >>
>>> >> This release comprises of a source code distribution, and a
>>> >> corresponding binary distribution, RPM packages, Vagrant environment
>>> >> package, and Maven artifacts.
>>> >>
>>> >> The source and binary distributions, including signatures, digests,
>>> >> etc. can be found at:
>>> >>
>>> https://dist.apache.org/repos/dist/dev/brooklyn/apache-brooklyn-0.9.0-rc2
>>> >>
>>> >> The artifact SHA-256 checksums are as follows:
>>> >> 426ca93aad28ac8281b2015fc0ea419cd6db19c3ed87ffd11910a6baf2e9e3ab
>>> >> *apache-brooklyn-0.9.0-rc2-1.noarch.rpm
>>> >> b2a65642fb86198b9fd9992ef3464025d9b41c453c4dd5366699d569a65709c6
>>> >> *apache-brooklyn-0.9.0-rc2-bin.tar.gz
>>> >> 999fd6f1d21417278ffe153fc1f0346d44235dfbbd39f200815f61cea82edbe5
>>> >> *apache-brooklyn-0.9.0-rc2-bin.zip
>>> >> 00e0a76775775957e92498d0b5ea3e13f844155eda3251a8ead05cf4b4a4455b
>>> >> *apache-brooklyn-0.9.0-rc2-src.tar.gz
>>> >> c7a9a286993b1d520ae6a32e25c0dd3bef7227290d59347256bd96480b70a02b
>>> >> *apache-brooklyn-0.9.0-rc2-src.zip
>>> >> 907267c5d2e7c1622e11f2bc57b6afe12ddf2136d82bad63661e43570aaa78fa
>>> >> *apache-brooklyn-0.9.0-rc2-vagrant.tar.gz
>>> >> 0ae8384426d6b7197ca3d194c1e8032b85c5bb80671157c274487220d3ba65e9
>>> >> *apache-brooklyn-0.9.0-rc2-vagrant.zip
>>> >>
>>> >> The Nexus staging repositories for the Maven artifacts are located at:
>>> >>
>>> https://repository.apache.org/content/repositories/orgapachebrooklyn-1016
>>> >>
>>> https://repository.apache.org/content/repositories/orgapachebrooklyn-1017
>>> >>
>>> >> All release artifacts are signed with the following key:
>>> >> https://people.apache.org/keys/committer/richard.asc
>>> >>
>>> >> KEYS file available here:
>>> >> https://dist.apache.org/repos/dist/release/brooklyn/KEYS
>>> >>
>>> >> The artifacts were built from these Git commit IDs:
>>> >> brooklyn: acc8ff1930d243d2a5fae1ad2f1a1ef17ca4a19c
>>> >> brooklyn-client: 64573c8e1b8630f59b23356520282c91cc46a8a1
>>> >> brooklyn-dist: 0b8b81df458fa4323939582d9f0dda10b2f6eaee
>>> >> brooklyn-docs: 12430d193e1891b87a677d6b45a3b17861c83518
>>> >> brooklyn-library: 2565e6eb2868468ec2528df74fe85efdb887b6d2
>>> >> brooklyn-server: d031cea080613645219ba982c93264943798d4fc
>>> >> brooklyn-ui: 307382128951bb237bc351ac22136745e5d50475
>>> >> All of the above have been tagged as "apache-brooklyn-0.9.0-rc2".
>>> >>
>>> >>
>>> >> Please download the artifacts, test, and vote on releasing this
>>> >> package as Apache Brooklyn 0.9.0.
>>> >>
>>> >> The vote will be open for at least 72 hours.
>>> >> [ ] +1 Release this package as Apache Brooklyn 0.9.0 (please describe
>>> >> the tests you have performed)
>>> >> [ ] +0 no opinion
>>> >> [ ] -1 Do not release this package (please describe why not)
>>> >>
>>> >> Thanks
>>> >> Richard.
>>> >
>>>
>>>

[GitHub] brooklyn-client pull request: Update build so that it includes onl...

[geomacy]

Github user geomacy commented on the pull request:

https://github.com/apache/brooklyn-client/pull/14#issuecomment-205721969
  
recycle



---
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-client pull request: Update build so that it includes onl...

[geomacy]

Github user geomacy commented on the pull request:

https://github.com/apache/brooklyn-client/pull/14#issuecomment-205721778
  
recycle



---
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-client pull request: Update build so that it includes onl...

[geomacy]

Github user geomacy closed the pull request at:

https://github.com/apache/brooklyn-client/pull/14


---
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-client pull request: Update build so that it includes onl...

[geomacy]

Github user geomacy commented on the pull request:

https://github.com/apache/brooklyn-client/pull/14#issuecomment-205720267
  
Looks like build break is a build machine availability issue, will recycle 
the request to test.


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