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

[Apache Jenkins Server]

See 

--
[...truncated 3.85 MB...]
Failed tests: 
org.apache.brooklyn.location.jclouds.DefaultConnectivityResolverTest.testMode(org.apache.brooklyn.location.jclouds.DefaultConnectivityResolverTest)
  Run 1: PASS
  Run 2: PASS
  Run 3: PASS
  Run 4: PASS
  Run 5: PASS
  Run 6: DefaultConnectivityResolverTest.testMode:199 » IllegalState jclouds 
did not re...


Tests run: 163, Failures: 1, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Brooklyn REST JavaScript Web GUI ... SUCCESS [01:40 min]
[INFO] Brooklyn Server Root ... SUCCESS [  2.287 s]
[INFO] Brooklyn Parent Project  SUCCESS [  7.438 s]
[INFO] Brooklyn Test Support Utilities  SUCCESS [  8.807 s]
[INFO] Brooklyn Logback Includable Configuration .. SUCCESS [ 10.909 s]
[INFO] Brooklyn Common Utilities .. SUCCESS [ 37.435 s]
[INFO] Brooklyn API ... SUCCESS [ 10.418 s]
[INFO] CAMP Server Parent Project . SUCCESS [  6.615 s]
[INFO] CAMP Base .. SUCCESS [ 17.262 s]
[INFO] Brooklyn Test Support .. SUCCESS [ 10.275 s]
[INFO] Brooklyn REST Swagger Apidoc Utilities . SUCCESS [  9.012 s]
[INFO] Brooklyn Logback Configuration . SUCCESS [  5.081 s]
[INFO] CAMP Server  SUCCESS [ 15.770 s]
[INFO] Brooklyn Felix Runtime . SUCCESS [ 15.162 s]
[INFO] Brooklyn Groovy Utilities .. SUCCESS [ 11.688 s]
[INFO] Brooklyn Core .. SUCCESS [03:22 min]
[INFO] Brooklyn Policies .. SUCCESS [01:18 min]
[INFO] Brooklyn WinRM Software Entities ... SUCCESS [ 25.087 s]
[INFO] Brooklyn Secure JMXMP Agent  SUCCESS [ 17.321 s]
[INFO] Brooklyn JMX RMI Agent . SUCCESS [  6.710 s]
[INFO] Brooklyn Jclouds Location Targets .. FAILURE [ 49.449 s]
[INFO] Brooklyn Software Base . SKIPPED
[INFO] Brooklyn CAMP .. 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 Karaf Tests ... 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 Simple Web Cluster Example  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 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 .. 

Re: [ANNOUNCE] Apache Brooklyn 0.11.0 released

[Geoff Macartney]

Thanks John

On Fri, 19 May 2017, 23:50 John McCabe,  wrote:

> The client on brew has been updated:
>
>
> https://github.com/Homebrew/homebrew-core/commit/2f9e055be68ccce267477fe38d957d0f65119e1f
>
> https://github.com/Homebrew/homebrew-core/commit/cc78a8539c0de48a2005a58ce736e5edb9a863f8
>
> On Thu, 18 May 2017 at 13:55 Richard Downer  wrote:
>
> > The Apache Brooklyn team is proud to announce the latest release of
> Apache
> > Brooklyn 0.11.0.
> >
> > Apache Brooklyn is a framework for modelling, deploying, and managing
> > applications through autonomic blueprints. More details on Apache
> Brooklyn
> > can be found at https://brooklyn.apache.org/
> >
> > As well as a source code release, we offer a full binary distribution
> > download, and a full set of Maven artifacts for developers.
> >
> > Release notes:
> > https://brooklyn.apache.org/v/0.11.0/misc/release-notes.html
> >
> > Download:
> > https://brooklyn.apache.org/download/
> >
> > User guide:
> > https://brooklyn.apache.org/v/0.11.0/
> >
> > Maven artifacts have also been made available on repository.apache.org
> and
> > Maven Central.
> >
> > Thanks
> > Richard Downer
> > release manager for 0.11.0
> > on behalf of the Brooklyn PMC
> >
>

Re: [ANNOUNCE] Apache Brooklyn 0.11.0 released

[John McCabe]

The client on brew has been updated:

https://github.com/Homebrew/homebrew-core/commit/2f9e055be68ccce267477fe38d957d0f65119e1f
https://github.com/Homebrew/homebrew-core/commit/cc78a8539c0de48a2005a58ce736e5edb9a863f8

On Thu, 18 May 2017 at 13:55 Richard Downer  wrote:

> The Apache Brooklyn team is proud to announce the latest release of Apache
> Brooklyn 0.11.0.
>
> Apache Brooklyn is a framework for modelling, deploying, and managing
> applications through autonomic blueprints. More details on Apache Brooklyn
> can be found at https://brooklyn.apache.org/
>
> As well as a source code release, we offer a full binary distribution
> download, and a full set of Maven artifacts for developers.
>
> Release notes:
> https://brooklyn.apache.org/v/0.11.0/misc/release-notes.html
>
> Download:
> https://brooklyn.apache.org/download/
>
> User guide:
> https://brooklyn.apache.org/v/0.11.0/
>
> Maven artifacts have also been made available on repository.apache.org and
> Maven Central.
>
> Thanks
> Richard Downer
> release manager for 0.11.0
> on behalf of the Brooklyn PMC
>

[GitHub] brooklyn-server pull request #687: Delete deprecated classes

[asfgit]

Github user asfgit closed the pull request at:

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


---
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] [Resolved] (BROOKLYN-498) Deadlock in MembershipTrackingPolicyTest when updating sensors vs group members

[Aled Sage (JIRA)]

 [ 
https://issues.apache.org/jira/browse/BROOKLYN-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aled Sage resolved BROOKLYN-498.

   Resolution: Fixed
Fix Version/s: 0.12.0

Fixed in https://github.com/apache/brooklyn-server/pull/671

> Deadlock in MembershipTrackingPolicyTest when updating sensors vs group 
> members
> ---
>
> Key: BROOKLYN-498
> URL: https://issues.apache.org/jira/browse/BROOKLYN-498
> Project: Brooklyn
>  Issue Type: Bug
>Reporter: Alex Heneveld
> Fix For: 0.12.0
>
>
> Core tests can hang due to this.  Set high invocation count eg on 
> {{testDeprecatedSetGroupWorks}} to expose.



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

[GitHub] brooklyn-docs pull request #187: Add hint for using effector.add.openInbound...

[bostko]

GitHub user bostko opened a pull request:

https://github.com/apache/brooklyn-docs/pull/187

Add hint for using effector.add.openInboundPorts entity config



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

$ git pull https://github.com/bostko/brooklyn-docs ports-effector

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

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


commit 17593650663c320fea77baf8426fe8587a1c9f73
Author: Valentin Aitken 
Date:   2017-05-19T16:42:17Z

Add hint for using effector.add.openInboundPorts entity 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.
---

[GitHub] brooklyn-library pull request #112: Fix Nginx dependencies

[drigodwin]

GitHub user drigodwin opened a pull request:

https://github.com/apache/brooklyn-library/pull/112

Fix Nginx dependencies

On some clouds, notably Azure with CentOS, `kernel-headers` is in the 
disbaled list which causes `gcc` to not install properly. This uses the 
`--disableexcludes=all` to install it.

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

$ git pull https://github.com/drigodwin/brooklyn-library fix-nginx

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

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


commit 4409083a1f2e2b64d41278d319dc9088de3f64e1
Author: Duncan Godwin 
Date:   2017-05-19T16:35:04Z

Fix Nginx dependencies




---
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-505) Amazon provisioning fails with "Illegal key size"

[Aled Sage (JIRA)]

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

Aled Sage commented on BROOKLYN-505:


[~svet] do you think we just need to add a line to 
http://brooklyn.apache.org/v/latest/ops/production-installation.html#a-idprerequisitesaset-up-the-prerequisites
 ?

I take it the rpm install works properly (because it installs OpenJDK itself)?

Will you have a chance to add that to the docs? If doing so, could you also 
change that section to say Java version 8 or later (it currently says "7 or 
later")?

> Amazon provisioning fails with "Illegal key size"
> -
>
> Key: BROOKLYN-505
> URL: https://issues.apache.org/jira/browse/BROOKLYN-505
> Project: Brooklyn
>  Issue Type: Bug
>Affects Versions: 0.11.0
>Reporter: Svetoslav Neykov
>
> Provisioning to Amazon with minimal location selects the image {{
> RightImage_CentOS_7.0_x64_v14.2.1_HVM_EBS}}. Later provisioning fails with 
> {{Exhausted available authentication methods}} error.
> Just before each failure the debug logs show
> {noformat}
> 2017-05-18 12:36:23,551 WARN   73 n.s.s.DefaultConfig [user thread 1] Illegal 
> key size
> 2017-05-18 12:36:23,552 WARN   73 n.s.s.DefaultConfig [user thread 1] Illegal 
> key size or default parameters
> 2017-05-18 12:36:23,552 WARN   73 n.s.s.DefaultConfig [user thread 1] 
> Disabling high-strength ciphers: cipher strengths apparently limited by JCE 
> policy
> {noformat}
> The workaround is to install the "high strength ciphers" extension if using 
> Oracle Java or move to OpenJDK which has those included.



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

Re: Help with Openstack

[Andrew Kennedy]

Graham,

A colleague just suggested that another way to accomplish this would be
with a custom `MachineProvisioningLocation` implementation, that was
configured with the location/credentials of the box with Ansible installed
and the playbook target to execute, and when a location is `obtain()`-ed it
would call the playbook and then determine the newly created VMs address
etc and use that to generate an `SshMachineLocation` for use by other
entities. Have a look at the code to see how it works:

-
https://github.com/apache/brooklyn-server/blob/master/core/src/main/java/org/apache/brooklyn/location/byon/FixedListMachineProvisioningLocation.java
-
https://github.com/apache/brooklyn-server/blob/master/core/src/main/java/org/apache/brooklyn/location/byon/SingleMachineProvisioningLocation.java
-
https://github.com/apache/brooklyn-server/blob/master/core/src/main/java/org/apache/brooklyn/location/localhost/LocalhostMachineProvisioningLocation.java

Hopefully this will give you some ideas.

Andrew.

On Fri, 19 May 2017 at 15:17 Andrew Kennedy <
andrew.kenn...@cloudsoftcorp.com> wrote:

> Hi Graham.
>
> You could certainly create a BYON location that referenced the instance
> created by Ansible, as described at
> http://brooklyn.apache.org/v/latest/locations/index.html#byon you simple
> export the host IP address and required credentials into a BOM file that
> describes the new location, and deploy it using the `br deploy` CLI
> command, or via the REST API and `curl` perhaps.
>
> You could also create an AnsibleEntity, which would then provision a VM
> somewhere and run the `ansible-playbook` commands required on it, but this
> may be a chicken-and-egg type of situation for you - it is more designed
> for the use case where we provision a VM, install ansible on it and then
> use a playbook to install something else on that machine. We are currently
> developing a policy that can create locations from entities, which sounds
> like it would also be useful, I will update this thread with the details
> shortly, when the PR is available.
>
> Andrew.
>
> On Fri, 19 May 2017 at 14:17 Graham Ashby  wrote:
>
>> Well, after much talk over here, our OpenStack servers only support V3
>> authentication.  We're using the Mitaka release. Older instances that
>> support the v2.0 authentication API are all EOL.
>>
>> Which leads me to plan B.  I have an Ansible playbook that  provisions a
>> new instance.  Is there some way to hook that (using an AnsibleEntry) into
>> a location?  I imagine I'd need a way to somehow export the host name and
>> external IP address into something that the Location could use.  And I'd
>> need a Location that could call an Entity to get whatever it needs.
>>
>> Is this possible?
>>
>> Thanks
>> Graham
>>
>>
>>
>> From:   Geoff Macartney 
>> To: Brooklyn dev 
>> Date:   05/03/2017 10:22 AM
>> Subject:Re: Help with Openstack
>>
>>
>>
>> hi Graham
>>
>> as far as I understand you'll need to stick to the v2 API to use Apache
>> Brooklyn, as that is what is currently supported by the underlying jclouds
>> library.
>>
>> As it happens this was a topic of conversation this very morning on the
>> jclouds mailing list [1], so there may be some progress on this in the
>> near
>> but not immediate future.
>>
>> [1]
>>
>> https://lists.apache.org/thread.html/b1162446800011a8343e67a7cda55a5033754881529c74fafa47109b@%3Cdev.jclouds.apache.org%3E
>>
>>
>> regards
>> Geoff
>>
>>
>>
>> On Wed, 3 May 2017 at 14:16 Graham Ashby  wrote:
>>
>> > I need some help with deploying to openstack...
>> >
>> > For some reason, our openstack-nova identity endpoint has to be the v3
>> > version:
>> > endpoint: https://canhdc-controller.canlab.ibm.com:5000/v3
>> >
>> > When I try to deploy, I get an exception:
>> > org.jclouds.http.HttpResponseException: command: POST
>> > https://canhdc-controller.canlab.ibm.com:5000/v3/tokens HTTP/1.1 failed
>> > with response: HTTP/1.1 404 Not Found; content: [{"error": {"message":
>> > "The resource could not be found.", "code": 404, "title": "Not Found"}}
>> >
>> > Do I need to somehow tell jclouds to use the v3 api?  Or am I stuck
>> > needing to use the v2.0 api?
>> >
>> > Also, our https endpoint is self signed, so I need to set OS_CACERT to
>> > make the openstack CLI work.
>> >
>> > For reference, here's the appropriate bit of my yaml:
>> >
>> >   jclouds:openstack-nova:
>> > endpoint: https://canhdc-controller.canlab.ibm.com:5000/v3
>> > identity: "fa4c7f59767d487682a7798550b946bd:graham.as...@ca.ibm.com
>> "
>> > credential: 
>> > displayName: hdc-canada
>> >
>> > imageId: Lobby/e3b40a4f-4e82-41b3-857c-68799c4a9009
>> > hardwareId: Lobby/m1.small
>> > keyPair: openstack-gsa-gen
>> > keyPairName: openstack-gsa-gen
>> > loginUser: cloudusr
>> > loginUser.privateKeyFile: /home/cloudusr/.ssh/openstack-gsa-gen.pem
>> >
>> 

[GitHub] brooklyn-docs pull request #186: Add todo

[Graeme-Miller]

GitHub user Graeme-Miller opened a pull request:

https://github.com/apache/brooklyn-docs/pull/186

Add todo



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

$ git pull https://github.com/Graeme-Miller/brooklyn-docs addTodo

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

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


commit 9f8541ecf345746d7d010d63eb4057b44b1a69a6
Author: graeme.miller 
Date:   2017-05-19T13:07:44Z

added catalog to blueprints

commit 65042d4ae1107b7b795456045156ab5a65db84bb
Author: graeme.miller 
Date:   2017-05-19T14:52:11Z

Revert "added catalog to blueprints"

This reverts commit 9f8541ecf345746d7d010d63eb4057b44b1a69a6.

commit 79a929f5d2385fec02fe1ca73ae0c78f4843df0e
Author: graeme.miller 
Date:   2017-05-19T14:52:22Z

Added a todo




---
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-docs pull request #185: [Suggestion] Merge guide/dev into website/d...

[bostko]

GitHub user bostko opened a pull request:

https://github.com/apache/brooklyn-docs/pull/185

[Suggestion] Merge guide/dev into website/developers

One section for all coding related matters.

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

$ git pull https://github.com/bostko/brooklyn-docs bundle-reload

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

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


commit c9207da10acdd27d1ebac67164fb2bcb01a80d0f
Author: Valentin Aitken 
Date:   2017-05-19T13:45:40Z

Merge guide/dev into website/developers

commit 62ad649854d9a341471cb55962c68e8ff4542781
Author: Valentin Aitken 
Date:   2017-05-19T14:24:15Z

Remove documentation > developers relationship




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

Re: Help with Openstack

[Andrew Kennedy]

Hi Graham.

You could certainly create a BYON location that referenced the instance
created by Ansible, as described at
http://brooklyn.apache.org/v/latest/locations/index.html#byon you simple
export the host IP address and required credentials into a BOM file that
describes the new location, and deploy it using the `br deploy` CLI
command, or via the REST API and `curl` perhaps.

You could also create an AnsibleEntity, which would then provision a VM
somewhere and run the `ansible-playbook` commands required on it, but this
may be a chicken-and-egg type of situation for you - it is more designed
for the use case where we provision a VM, install ansible on it and then
use a playbook to install something else on that machine. We are currently
developing a policy that can create locations from entities, which sounds
like it would also be useful, I will update this thread with the details
shortly, when the PR is available.

Andrew.

On Fri, 19 May 2017 at 14:17 Graham Ashby  wrote:

> Well, after much talk over here, our OpenStack servers only support V3
> authentication.  We're using the Mitaka release. Older instances that
> support the v2.0 authentication API are all EOL.
>
> Which leads me to plan B.  I have an Ansible playbook that  provisions a
> new instance.  Is there some way to hook that (using an AnsibleEntry) into
> a location?  I imagine I'd need a way to somehow export the host name and
> external IP address into something that the Location could use.  And I'd
> need a Location that could call an Entity to get whatever it needs.
>
> Is this possible?
>
> Thanks
> Graham
>
>
>
> From:   Geoff Macartney 
> To: Brooklyn dev 
> Date:   05/03/2017 10:22 AM
> Subject:Re: Help with Openstack
>
>
>
> hi Graham
>
> as far as I understand you'll need to stick to the v2 API to use Apache
> Brooklyn, as that is what is currently supported by the underlying jclouds
> library.
>
> As it happens this was a topic of conversation this very morning on the
> jclouds mailing list [1], so there may be some progress on this in the
> near
> but not immediate future.
>
> [1]
>
> https://lists.apache.org/thread.html/b1162446800011a8343e67a7cda55a5033754881529c74fafa47109b@%3Cdev.jclouds.apache.org%3E
>
>
> regards
> Geoff
>
>
>
> On Wed, 3 May 2017 at 14:16 Graham Ashby  wrote:
>
> > I need some help with deploying to openstack...
> >
> > For some reason, our openstack-nova identity endpoint has to be the v3
> > version:
> > endpoint: https://canhdc-controller.canlab.ibm.com:5000/v3
> >
> > When I try to deploy, I get an exception:
> > org.jclouds.http.HttpResponseException: command: POST
> > https://canhdc-controller.canlab.ibm.com:5000/v3/tokens HTTP/1.1 failed
> > with response: HTTP/1.1 404 Not Found; content: [{"error": {"message":
> > "The resource could not be found.", "code": 404, "title": "Not Found"}}
> >
> > Do I need to somehow tell jclouds to use the v3 api?  Or am I stuck
> > needing to use the v2.0 api?
> >
> > Also, our https endpoint is self signed, so I need to set OS_CACERT to
> > make the openstack CLI work.
> >
> > For reference, here's the appropriate bit of my yaml:
> >
> >   jclouds:openstack-nova:
> > endpoint: https://canhdc-controller.canlab.ibm.com:5000/v3
> > identity: "fa4c7f59767d487682a7798550b946bd:graham.as...@ca.ibm.com"
> > credential: 
> > displayName: hdc-canada
> >
> > imageId: Lobby/e3b40a4f-4e82-41b3-857c-68799c4a9009
> > hardwareId: Lobby/m1.small
> > keyPair: openstack-gsa-gen
> > keyPairName: openstack-gsa-gen
> > loginUser: cloudusr
> > loginUser.privateKeyFile: /home/cloudusr/.ssh/openstack-gsa-gen.pem
> >
> > jclouds.openstack-nova.cacert: /opt/brooklyn/ca-1/hdc.pem
> > jclouds.openstack-nova.openIptables: true
> > jclouds.openstack-nova.selinux.disabled: true
> > jclouds.openstack-nova.auto-create-floating-ips: true
> > jclouds.openstack-nova.auto-generate-keypairs: false
> >
> >
>
>
>
>
> --

Andrew Kennedy ; Founder clocker.io project ; @grkvlt ; Cloudsoft

[GitHub] brooklyn-server pull request #672: Bundle uninstall and snapshot

[aledsage]

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

https://github.com/apache/brooklyn-server/pull/672#discussion_r117490368
  
--- Diff: 
core/src/main/java/org/apache/brooklyn/core/mgmt/ha/OsgiArchiveInstaller.java 
---
@@ -0,0 +1,429 @@
+/*
+ * 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.core.mgmt.ha;
+
+import java.io.File;
+import java.io.FileInputStream;
+import java.io.FileOutputStream;
+import java.io.IOException;
+import java.io.InputStream;
+import java.util.jar.Attributes;
+import java.util.jar.Manifest;
+import java.util.zip.ZipEntry;
+import java.util.zip.ZipFile;
+
+import org.apache.brooklyn.api.catalog.CatalogItem;
+import org.apache.brooklyn.api.typereg.ManagedBundle;
+import org.apache.brooklyn.core.catalog.internal.BasicBrooklynCatalog;
+import 
org.apache.brooklyn.core.mgmt.ha.OsgiBundleInstallationResult.ResultCode;
+import org.apache.brooklyn.core.mgmt.internal.ManagementContextInternal;
+import org.apache.brooklyn.core.typereg.BasicManagedBundle;
+import org.apache.brooklyn.util.core.ResourceUtils;
+import org.apache.brooklyn.util.core.osgi.BundleMaker;
+import org.apache.brooklyn.util.core.osgi.Osgis;
+import org.apache.brooklyn.util.exceptions.Exceptions;
+import org.apache.brooklyn.util.exceptions.ReferenceWithError;
+import org.apache.brooklyn.util.guava.Maybe;
+import org.apache.brooklyn.util.os.Os;
+import org.apache.brooklyn.util.osgi.VersionedName;
+import org.apache.brooklyn.util.stream.Streams;
+import org.apache.brooklyn.util.text.Strings;
+import org.apache.brooklyn.util.text.VersionComparator;
+import org.osgi.framework.Bundle;
+import org.osgi.framework.BundleException;
+import org.osgi.framework.Constants;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import com.google.common.base.Objects;
+
+// package-private so we can move this one if/when we move OsgiManager
+class OsgiArchiveInstaller {
+
+private static final Logger log = 
LoggerFactory.getLogger(OsgiArchiveInstaller.class);
+
+final private OsgiManager osgiManager;
+private ManagedBundle suppliedKnownBundleMetadata;
+private InputStream zipIn;
+
+private boolean start = true;
+private boolean loadCatalogBom = true;
+private boolean force = false;
+private boolean deferredStart = false;
+
+private File zipFile;
+private Manifest discoveredManifest;
+private VersionedName discoveredBomVersionedName;
+OsgiBundleInstallationResult result;
+
+private ManagedBundle inferredMetadata;
+private final boolean inputStreamSupplied;
+
+OsgiArchiveInstaller(OsgiManager osgiManager, ManagedBundle 
knownBundleMetadata, InputStream zipIn) {
+this.osgiManager = osgiManager;
+this.suppliedKnownBundleMetadata = knownBundleMetadata;
+this.zipIn = zipIn;
+inputStreamSupplied = zipIn!=null;
+}
+
+public void setStart(boolean start) {
+this.start = start;
+}
+
+public void setLoadCatalogBom(boolean loadCatalogBom) {
+this.loadCatalogBom = loadCatalogBom;
+}
+
+public void setForce(boolean force) {
+this.force = force;
+}
+
+public void setDeferredStart(boolean deferredStart) {
+this.deferredStart = deferredStart;
+}
+
+private ManagementContextInternal mgmt() {
+return (ManagementContextInternal) osgiManager.mgmt;
+}
+
+private synchronized void init() {
+if (result!=null) {
+if (zipFile!=null || zipIn==null) return;
+throw new IllegalStateException("This installer instance has 
already been used and the input stream discarded");
+}
+result = new OsgiBundleInstallationResult();
+inferredMetadata = 

[GitHub] brooklyn-dist pull request #93: Remove MaxPermSize options

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-dist/pull/93


---
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-docs pull request #184: Remove MaxPermSize options

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-docs/pull/184


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

Jenkins build is back to normal : brooklyn-master-build #1090

[Apache Jenkins Server]

See 

Jenkins build is back to normal : brooklyn-server-master #586

[Apache Jenkins Server]

See 

Re: Help with Openstack

[Graham Ashby]

Well, after much talk over here, our OpenStack servers only support V3 
authentication.  We're using the Mitaka release. Older instances that 
support the v2.0 authentication API are all EOL.

Which leads me to plan B.  I have an Ansible playbook that  provisions a 
new instance.  Is there some way to hook that (using an AnsibleEntry) into 
a location?  I imagine I'd need a way to somehow export the host name and 
external IP address into something that the Location could use.  And I'd 
need a Location that could call an Entity to get whatever it needs.

Is this possible?

Thanks
Graham



From:   Geoff Macartney 
To: Brooklyn dev 
Date:   05/03/2017 10:22 AM
Subject:Re: Help with Openstack



hi Graham

as far as I understand you'll need to stick to the v2 API to use Apache
Brooklyn, as that is what is currently supported by the underlying jclouds
library.

As it happens this was a topic of conversation this very morning on the
jclouds mailing list [1], so there may be some progress on this in the 
near
but not immediate future.

[1]
https://lists.apache.org/thread.html/b1162446800011a8343e67a7cda55a5033754881529c74fafa47109b@%3Cdev.jclouds.apache.org%3E


regards
Geoff



On Wed, 3 May 2017 at 14:16 Graham Ashby  wrote:

> I need some help with deploying to openstack...
>
> For some reason, our openstack-nova identity endpoint has to be the v3
> version:
> endpoint: https://canhdc-controller.canlab.ibm.com:5000/v3
>
> When I try to deploy, I get an exception:
> org.jclouds.http.HttpResponseException: command: POST
> https://canhdc-controller.canlab.ibm.com:5000/v3/tokens HTTP/1.1 failed
> with response: HTTP/1.1 404 Not Found; content: [{"error": {"message":
> "The resource could not be found.", "code": 404, "title": "Not Found"}}
>
> Do I need to somehow tell jclouds to use the v3 api?  Or am I stuck
> needing to use the v2.0 api?
>
> Also, our https endpoint is self signed, so I need to set OS_CACERT to
> make the openstack CLI work.
>
> For reference, here's the appropriate bit of my yaml:
>
>   jclouds:openstack-nova:
> endpoint: https://canhdc-controller.canlab.ibm.com:5000/v3
> identity: "fa4c7f59767d487682a7798550b946bd:graham.as...@ca.ibm.com"
> credential: 
> displayName: hdc-canada
>
> imageId: Lobby/e3b40a4f-4e82-41b3-857c-68799c4a9009
> hardwareId: Lobby/m1.small
> keyPair: openstack-gsa-gen
> keyPairName: openstack-gsa-gen
> loginUser: cloudusr
> loginUser.privateKeyFile: /home/cloudusr/.ssh/openstack-gsa-gen.pem
>
> jclouds.openstack-nova.cacert: /opt/brooklyn/ca-1/hdc.pem
> jclouds.openstack-nova.openIptables: true
> jclouds.openstack-nova.selinux.disabled: true
> jclouds.openstack-nova.auto-create-floating-ips: true
> jclouds.openstack-nova.auto-generate-keypairs: false
>
>

[GitHub] brooklyn-client pull request #51: Remove MaxPermSize options

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-ui pull request #45: Remove MaxPermSize options

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-ui/pull/45


---
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-library pull request #111: Remove MaxPermSize options

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-library/pull/111


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

Suggest merging docs sections guide/dev and website/developers

[Valentin Aitken]

Hi,

What do you think about merging contents of
brooklyn-docs/guide/dev and brooklyn-docs/website/developers?
Those stand for [1] [2]

I am looking for a single index page called Developers Guide
which includes contents from brooklyn-docs/guide/dev/index.md
and also has the index of brooklyn-docs/website/developers

[1] https://brooklyn.apache.org/developers/index.html
[2] https://brooklyn.apache.org/v/latest/dev/index.html

--
Valentin Aitken
Software Engineer
Cloudsoft Corporation Ltd.
www.cloudsoft.io

[GitHub] brooklyn pull request #11: Remove MaxPermSize options

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn/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-server pull request #689: Remove MaxPermSize options

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-docs pull request #184: Remove MaxPermSize options

[neykov]

GitHub user neykov opened a pull request:

https://github.com/apache/brooklyn-docs/pull/184

Remove MaxPermSize options



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

$ git pull https://github.com/neykov/brooklyn-docs remove-max-perm-size

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

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


commit e16181dcb257835a9e47b3c87a4ae4718500610d
Author: Svetoslav Neykov 
Date:   2017-05-19T12:58:27Z

Move to Java 8, remove MaxPermSize options




---
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 #51: Remove MaxPermSize options

[neykov]

GitHub user neykov opened a pull request:

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

Remove MaxPermSize options



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

$ git pull https://github.com/neykov/brooklyn-client remove-max-perm-size

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

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


commit 1fd1ee8ec989855104dd74f81692d0e47e7d1058
Author: Svetoslav Neykov 
Date:   2017-05-19T12:55:29Z

Move to Java 8, remove MaxPermSize options




---
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 #93: Remove MaxPermSize options

[neykov]

GitHub user neykov opened a pull request:

https://github.com/apache/brooklyn-dist/pull/93

Remove MaxPermSize options



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

$ git pull https://github.com/neykov/brooklyn-dist remove-max-perm-size

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

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


commit eb02fac7e19c0274ecdec9f43fffb603bfeead8c
Author: Svetoslav Neykov 
Date:   2017-05-19T12:57:25Z

Move to Java 8, remove MaxPermSize options




---
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-library pull request #111: Remove MaxPermSize options

[neykov]

GitHub user neykov opened a pull request:

https://github.com/apache/brooklyn-library/pull/111

Remove MaxPermSize options



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

$ git pull https://github.com/neykov/brooklyn-library remove-max-perm-size

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

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


commit 357f3694133135ddb6b5d74791e4184d075672bb
Author: Svetoslav Neykov 
Date:   2017-05-19T12:56:11Z

Move to Java 8, remove MaxPermSize options




---
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-ui pull request #45: Remove MaxPermSize options

[neykov]

GitHub user neykov opened a pull request:

https://github.com/apache/brooklyn-ui/pull/45

Remove MaxPermSize options



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

$ git pull https://github.com/neykov/brooklyn-ui remove-max-perm-size

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

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






---
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 #689: Remove MaxPermSize options

[neykov]

GitHub user neykov opened a pull request:

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

Remove MaxPermSize options



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

$ git pull https://github.com/neykov/brooklyn-server remove-max-perm-size

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

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


commit 839a526192f9ee06ab482bd0c07d7f9818f69abe
Author: Svetoslav Neykov 
Date:   2017-05-19T12:55:00Z

Move to Java 8, remove MaxPermSize options




---
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 pull request #11: Remove MaxPermSize options

[neykov]

GitHub user neykov opened a pull request:

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

Remove MaxPermSize options



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

$ git pull https://github.com/neykov/brooklyn remove-max-perm-size

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

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


commit d8cca3e05c6bac24fc2ac9cd9313d692ef79d597
Author: Svetoslav Neykov 
Date:   2017-05-19T12:37:00Z

Move to Java 8, remove MaxPermSize options




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

Re: Roadmap to Apache Brooklyn 1.0

[Duncan Johnston Watt]

Richard

This sounds like a great idea. Would we also carve out the brooklyn-library
blueprints so that these are maintained separately? I am assuming that they
would be still part of the project but available as an option rather than
bundled??

Best

Duncan

On 19 May 2017 at 11:55, Richard Downer  wrote:

> Hello all,
>
> Now that we have release 0.11.0 done, I'd like us to have a discussion
> about our plans for upcoming releases, and to decide when we're going to
> make the jump to version 1.0.
>
> Looking back, the core of Brooklyn is now very strong, and has been tried
> and tested by many people for many months, some using for production
> workloads. The operations side has matured with the support for persistence
> and high availability. Pure YAML blueprints are now extremely capable, and
> the Java-based blueprints in brooklyn-library have in many cases been
> overtaken by pure YAML blueprints written by Brooklyn users. The catalog
> provides a way to manage and compose blueprints, with OSGI providing a
> means to manage and version. Finishing touches, such as supporting ZIP
> files for catalog uploads (removing the requirement that a user must create
> their own OSGI bundles) mean we will have a very compelling story for
> blueprint developers.
>
> So, what's left to do? Are there any major (or even moderate) features that
> we would want in a 1.0 release?
>
> My thoughts are that we release 0.12.0 next. This will put the Karaf-based
> distribution as the primary artifact, with accompanying .deb and .rpms. The
> classic distribution will remain but be deprecated. At this point, we
> should make an effort to mark as "deprecated" as much as we possibly can,
> so we don't have to take unnecessary baggage into the 1.x series.
>
> After that, we aim for 1.0.0 - the classic distribution is removed, and so
> is everything marked as deprecated.
>
> In parallel with this, an effort to overhaul the documentation, so that our
> 1.0 docs are comprehensive and easy to use.
>
> Any other thoughts?
>



-- 

Duncan Johnston-Watt

Founder & Chief Executive Officer

Phone: +44 777 190 2653 | Skype: duncan_johnstonwatt

Twitter: @duncanjw  | LinkedIn:
https://linkedin.com/in/duncanjohnstonwatt

[image: Cloudsoft Logo.jpg] 

Stay up to date with everything Cloudsoft:

[image: Twitter_Logo_White_On_Blue.png]  [image:
YouTube-social-icon_red_48px.png]

[NOTICE] master now on Java 8

[Geoff Macartney]

hi all,

just to note, in case you've not been following the thread [1], that master
in Brooklyn has now moved to Java 8 [2].  Shout out if you encounter any
problems!

Cheers
Geoff

[1]
https://lists.apache.org/thread.html/1f7068d90480bfd20795d35e733033a150bd4cf1c4d8ff65d269@%3Cdev.brooklyn.apache.org%3E
[2] https://github.com/apache/brooklyn-server/pull/684

[GitHub] brooklyn-docs pull request #180: Update bundle upload

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-docs/pull/180


---
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: brooklyn-server-master #585

[Apache Jenkins Server]

See 


Changes:

[aled.sage] Delete usage of Groovy ObservableList

--
[...truncated 3.86 MB...]
2017-05-19 11:43:48,340 WARN  Using DEPRECATED flag OPEN_IPTABLES (will not be 
supported in future versions) for 
SshMachineLocation[173.194.32.1:jenkins@1.2.3.4/1.2.3.4:12345(id=gbn2wwm9tw)] 
at JcloudsLocation[aws-ec2:us-east-1:stub-identity@runpg98xxg]
2017-05-19 11:43:48,340 INFO  No ports to open in iptables (no inbound ports) 
for 
SshMachineLocation[173.194.32.1:jenkins@1.2.3.4/1.2.3.4:12345(id=gbn2wwm9tw)] 
at JcloudsLocation[aws-ec2:us-east-1:stub-identity@runpg98xxg]
2017-05-19 11:43:48,341 INFO  Finished VM aws-ec2:us-east-1 creation: 
jenkins@1.2.3.4/1.2.3.4:12345 ready after 150ms (semaphore obtained in 
0ms;{image={id=us-east-1/bogus-image, providerId=ebs-image-provider, 
name=image, location={scope=REGION, id=us-east-1, description=us-east-1, 
parent=aws-ec2}, os={family=ubuntu, arch=paravirtual, version=1.0, 
description=ubuntu, is64Bit=true}, description=description, version=1.0, 
status=AVAILABLE, loginUser=root, userMetadata={rootDeviceType=ebs}}, 
hardware={id=supporting-bogus, providerId=t2.micro, processors=[{cores=1.0, 
speed=0.1}], ram=1024, 
supportsImage=Predicates.and(requiresRootDeviceType(ebs),requiresVirtualizationType(paravirtual),idIn([us-east-1/bogus-image]),Predicates.alwaysTrue())},
 location={scope=REGION, id=us-east-1, description=us-east-1, parent=aws-ec2}, 
options=Mock for TemplateOptions, hashCode: 1702663130} template built in 0ms; 
{id=mynodeid1, location={scope=REGION, id=us-east-1, description=us-east-1, 
parent=aws-ec2}, status=RUNNING, loginPort=22, privateAddresses=[172.168.10.1], 
publicAddresses=[173.194.32.1]} provisioned in 1ms; 
SshMachineLocation[173.194.32.1:jenkins@1.2.3.4/1.2.3.4:12345(id=gbn2wwm9tw)] 
connection usable in 144ms; and os customized in 5ms - point /dev/random to 
urandom)
2017-05-19 11:43:48,341 INFO  Releasing machine 
SshMachineLocation[173.194.32.1:jenkins@1.2.3.4/1.2.3.4:12345(id=gbn2wwm9tw)] 
in JcloudsLocation[aws-ec2:us-east-1:stub-identity@runpg98xxg], instance id 
mynodeid1
2017-05-19 11:43:48,342 WARN  Releasing port-forwarding of 
SshMachineLocation[173.194.32.1:jenkins@1.2.3.4/1.2.3.4:12345(id=gbn2wwm9tw)] 
not executing in execution-context (e.g. not invoked inside effector); falling 
back to executing sequentially
2017-05-19 11:43:48,343 INFO  Attempted release of unknown machine 
SshMachineLocation[173.194.32.1:jenkins@1.2.3.4/1.2.3.4:12345(id=gbn2wwm9tw)] 
in JcloudsLocation[aws-ec2:us-east-1:stub-identity@runpg98xxg]
2017-05-19 11:43:48,344 INFO  TESTNG PASSED: "Surefire test" - 
org.apache.brooklyn.location.jclouds.networking.JcloudsPortForwardingStubbedTest.testPortForwardingCallsForwarder()
 finished in 155 ms
2017-05-19 11:43:48,344 INFO  TESTNG INVOKING CONFIGURATION: "Surefire test" - 
@AfterMethod 
org.apache.brooklyn.location.jclouds.AbstractJcloudsStubbedUnitTest.tearDown()
2017-05-19 11:43:48,345 INFO  TESTNG PASSED CONFIGURATION: "Surefire test" - 
@AfterMethod 
org.apache.brooklyn.location.jclouds.AbstractJcloudsStubbedUnitTest.tearDown() 
finished in 1 ms
2017-05-19 11:43:48,355 INFO  TESTNG INVOKING CONFIGURATION: "Surefire test" - 
@BeforeMethod 
org.apache.brooklyn.location.jclouds.networking.JcloudsPortForwardingStubbedTest.setUp()
2017-05-19 11:43:48,362 INFO  No Camp-YAML parser registered for parsing 
catalog item DSL; skipping DSL-parsing
2017-05-19 11:43:48,365 INFO  TESTNG PASSED CONFIGURATION: "Surefire test" - 
@BeforeMethod 
org.apache.brooklyn.location.jclouds.networking.JcloudsPortForwardingStubbedTest.setUp()
 finished in 10 ms
2017-05-19 11:43:48,365 INFO  TESTNG INVOKING: "Surefire test" - 
org.apache.brooklyn.location.jclouds.networking.JcloudsPortForwardingStubbedTest.testReleaseVmDoesNotImpactOtherVms()
2017-05-19 11:43:48,365 WARN  Deprecated construction of 
org.apache.brooklyn.core.location.access.PortForwardManagerImpl; instead use 
location resolver
2017-05-19 11:43:48,366 INFO  Creating VM aws-ec2:us-east-1 in 
JcloudsLocation[aws-ec2:us-east-1:stub-identity@kmqzm0b1sh]
2017-05-19 11:43:48,366 WARN  Cannot check imageChooser status for 
aws-ec2:us-east-1 due to manually supplied black-box TemplateBuilder; it is 
recommended to use a PortableTemplateBuilder if you supply a TemplateBuilder
2017-05-19 11:43:48,367 WARN  No context entity found in config or current task
2017-05-19 11:43:48,370 INFO  Using host-and-port=1.2.3.4:12345 and user=myuser 
when connecting to {id=mynodeid1, location={scope=REGION, id=us-east-1, 
description=us-east-1, parent=aws-ec2}, status=RUNNING, loginPort=22, 
privateAddresses=[172.168.10.1], publicAddresses=[173.194.32.1], 
loginUser=myuser}
2017-05-19 11:43:48,371 INFO  Default SSH keys not found or not usable; will 
create new keys for each machine. Create ~/.ssh/id_rsa or set privateKeyFile / 
privateKeyPassphrase / password 

[GitHub] brooklyn-docs pull request #180: Update bundle upload

[alasdairhodge]

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

https://github.com/apache/brooklyn-docs/pull/180#discussion_r117459280
  
--- Diff: guide/blueprints/catalog/index.md ---
@@ -371,6 +373,126 @@ increment an internal version number for the catalog 
item.
 When referencing a blueprint, if a version number is not specified 
 the latest non-snapshot version will be loaded when an entity is 
instantiated.
 
+### Bundling Catalog Resources
+
+It is possible to add an OSGi bundle to AMP. This is useful when you have 
a blueprint that needs to reference external scripts/resources or when you have 
multiple blueprints that you want to keep in sync. Brooklyn will persist any 
uploaded bundles so that they are available after a restart, or a HA failover.
+
+In this example, we will create a simple `my-server` catalog item, bundled 
with a simple script. The script will be run when launching the server.
+
+First, create a folder called bundleFolder, then add a file called 
myfile.sh to it. 
+The contents of myfile.sh should be as follows:
+
+~~~ bash
+echo Hello, World!
+~~~
+
+Now create a file in bundleFolder called `catalog.bom` with the following 
contents:
+
+~~~ yaml
+brooklyn.catalog:
+  bundle: MyServerBundle
+  version: 1.0.0
+  item:  
+id: my-server
+type: org.apache.brooklyn.entity.software.base.VanillaSoftwareProcess
+brooklyn.config:
+  files.runtime:
+classpath://myfile.sh: files/myfile.sh
+  launch.command: |
+chmod +x ./files/myfile.sh
+./files/myfile.sh
+
+  checkRunning.command:
+echo "Running"  
+
+~~~
+
+The `bundle: MyServerBundle` line specifies the OSGI bundle name for this 
bundle. Any resources included
+in this bundle will be accessible on the classpath, but will be scoped to 
this bundle. This prevents an
+issue where multiple bundles include the same resource.
+
+To create the bundle, simply use the BR command as follows:
+
+~~~ bash
+br add-catalog bundleFolder
--- End diff --

`add-catalog` is deprected in favour of `catalog add`


---
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 #686: Delete usage of Groovy ObservableList

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-docs pull request #180: Update bundle upload

[Graeme-Miller]

Github user Graeme-Miller commented on a diff in the pull request:

https://github.com/apache/brooklyn-docs/pull/180#discussion_r117458781
  
--- Diff: guide/blueprints/catalog/index.md ---
@@ -375,153 +375,120 @@ the latest non-snapshot version will be loaded when 
an entity is instantiated.
 
 ### Bundling Catalog Resources
 
-When deploying a blueprint, it is possible to deploy it as an OSGI bundle 
with additional resources scoped
-to this bundle. This is particularly useful when, for example, deploying a 
Tomcat server with a `.war` file
-which is deployed using a classpath path such as `classpath://mywar.war`.
+It is possible to add an OSGi bundle to AMP. This is useful when you have 
a blueprint that needs to reference external scripts/resources or when you have 
multiple blueprints that you want to keep in sync. Brooklyn will persist any 
uploaded bundles so that they are available after a restart, or a HA failover.
 
-In this example, we will create a simple `server` catalog item, bundled 
with a simple text file.
+In this example, we will create a simple `my-server` catalog item, bundled 
with a simple script. The script will be run when launching the server.
 
-First, create the text file with some sample contents:
+First, create a folder called bundleFolder, then add a file called 
myfile.sh to it. 
+The contents of myfile.sh should be as follows:
 
 ~~~ bash
-echo Hello, World! > myfile.txt
+echo Hello, World!
 ~~~
 
-Now create a file called `catalog.bom` with the following contents:
+Now create a file in bundleFolder called `catalog.bom` with the following 
contents:
 
 ~~~ yaml
 brooklyn.catalog:
-  bundle: script-server
+  bundle: MyServerBundle
   version: 1.0.0
-  items:
-  - id: script-server
-itemType: entity
-item:
-  type: server
-  brooklyn.config:
-files.runtime:
-  classpath://myfile.txt: files/myfile.txt
+  item:  
+id: my-server
+type: org.apache.brooklyn.entity.software.base.VanillaSoftwareProcess
+brooklyn.config:
+  files.runtime:
+classpath://myfile.sh: files/myfile.sh
+  launch.command: |
+chmod +x ./files/myfile.sh
+./files/myfile.sh
+
+  checkRunning.command:
+echo "Running"  
+
 ~~~
 
-The `bundle: script-server` line specifies the OSGI bundle name for this 
blueprint. Any resources included
+The `bundle: MyServerBundle` line specifies the OSGI bundle name for this 
bundle. Any resources included
 in this bundle will be accessible on the classpath, but will be scoped to 
this bundle. This prevents an
 issue where multiple bundles include the same resource.
 
-To create the bundle, simply zip the `.bom` and `.txt` files as follows:
+To create the bundle, simply use the BR command as follows:
 
 ~~~ bash
-zip script-server.zip catalog.bom myfile.txt
+br add-catalog bundleFolder
 ~~~
 
-Currently the only supported method for uploading the bundle to the server 
is via the API, e.g. using
-`curl`:
-
-~~~ bash
-curl -X POST -u admin:password -H "Content-Type: application/zip" 
--data-binary @/tmp/zip/script-server.zip "http://127.0.0.1:8081/v1/catalog;
-~~~
-
-We can now deploy an instance of our script server as follows:
+This will have added our bundle to the catalog. We can now deploy an 
instance of our server as follows:
 
 ~~~ yaml
 location: localhost
 services:
-- type: script-server
+- type: my-server
 ~~~
 
-And we can now inspect the contents of the file copied to the server
+We can now see the result of running that script. In the UI find the 
activities for this application. The start activity has a sub task called 
launch (you will have to click through multiple activities called start/launch. 
Looking at the stdout of the launch task you should see:
 
-~~~ bash
-cat 
/tmp/brooklyn-martin/apps/nl9djqbq2i/entities/EmptySoftwareProcess_g52gahfxnt/files/myfile.txt
-~~~
-~~~ bash
+~~~ bash  
 Hello, World!
 ~~~
 
-Now modify `myfile.txt` to contain a different message, change the version 
number in `catalog.bom` to
-`1.1.0`, re-build the zip file and re-post it to the server
-
-If you now deploy a new instance of the script-server using the same YAML 
as used above, you should be
-able to confirm that the new script has been copied to the server:
-
+Alternatively you can view the script directly if you ran this against 
localhost:
 ~~~ bash
-cat 
/tmp/brooklyn-martin/apps/bwu57darkd/entities/EmptySoftwareProcess_umcgshzduk/files/myfile.txt
 
+cat 
/tmp/brooklyn-username/apps/nl9djqbq2i/entities/EmptySoftwareProcess_g52gahfxnt/files/myfile.sh
 ~~~
 

Build failed in Jenkins: brooklyn-server-master #584

[Apache Jenkins Server]

See 


Changes:

[aled.sage] Delete deprecated persistence/rebind code

[aled.sage] Move `newBrooklynMemento` to RebindTestUtils

[aled.sage] Delete `MutableBrooklynMemento`

--
[...truncated 5.99 MB...]
2017-05-19 10:52:50,553 INFO  TESTNG PASSED CONFIGURATION: "Surefire test" - 
@BeforeMethod org.apache.brooklyn.camp.brooklyn.AbstractYamlTest.setUp() 
finished in 2 ms
2017-05-19 10:52:50,553 INFO  TESTNG INVOKING: "Surefire test" - 
org.apache.brooklyn.camp.brooklyn.catalog.CatalogYamlPolicyTest.testLaunchApplicationReferencingPolicy()
2017-05-19 10:52:50,629 INFO  Started application 
BasicApplicationImpl{id=avbxc0n1uy}
2017-05-19 10:52:50,631 INFO  TESTNG PASSED: "Surefire test" - 
org.apache.brooklyn.camp.brooklyn.catalog.CatalogYamlPolicyTest.testLaunchApplicationReferencingPolicy()
 finished in 78 ms
2017-05-19 10:52:50,631 INFO  TESTNG INVOKING CONFIGURATION: "Surefire test" - 
@AfterMethod org.apache.brooklyn.camp.brooklyn.AbstractYamlTest.tearDown()
2017-05-19 10:52:50,633 INFO  Stopping application 
BasicApplicationImpl{id=avbxc0n1uy}
2017-05-19 10:52:50,634 INFO  Stopped application 
BasicApplicationImpl{id=avbxc0n1uy}
2017-05-19 10:52:50,636 INFO  TESTNG PASSED CONFIGURATION: "Surefire test" - 
@AfterMethod org.apache.brooklyn.camp.brooklyn.AbstractYamlTest.tearDown() 
finished in 5 ms
2017-05-19 10:52:50,636 INFO  TESTNG INVOKING CONFIGURATION: "Surefire test" - 
@BeforeMethod org.apache.brooklyn.camp.brooklyn.AbstractYamlTest.setUp()
2017-05-19 10:52:50,639 INFO  TESTNG PASSED CONFIGURATION: "Surefire test" - 
@BeforeMethod org.apache.brooklyn.camp.brooklyn.AbstractYamlTest.setUp() 
finished in 3 ms
2017-05-19 10:52:50,639 INFO  TESTNG INVOKING: "Surefire test" - 
org.apache.brooklyn.camp.brooklyn.catalog.CatalogYamlPolicyTest.testLaunchApplicationReferencingPolicyTopLevelSyntax()
2017-05-19 10:52:50,719 INFO  Started application 
BasicApplicationImpl{id=w6z3zvu02i}
2017-05-19 10:52:50,720 INFO  TESTNG PASSED: "Surefire test" - 
org.apache.brooklyn.camp.brooklyn.catalog.CatalogYamlPolicyTest.testLaunchApplicationReferencingPolicyTopLevelSyntax()
 finished in 81 ms
2017-05-19 10:52:50,721 INFO  TESTNG INVOKING CONFIGURATION: "Surefire test" - 
@AfterMethod org.apache.brooklyn.camp.brooklyn.AbstractYamlTest.tearDown()
2017-05-19 10:52:50,722 INFO  Stopping application 
BasicApplicationImpl{id=w6z3zvu02i}
2017-05-19 10:52:50,723 INFO  Stopped application 
BasicApplicationImpl{id=w6z3zvu02i}
[GC (Allocation Failure)  319245K->80604K(769024K), 0.0108698 secs]
2017-05-19 10:52:50,737 INFO  TESTNG PASSED CONFIGURATION: "Surefire test" - 
@AfterMethod org.apache.brooklyn.camp.brooklyn.AbstractYamlTest.tearDown() 
finished in 16 ms
2017-05-19 10:52:50,738 INFO  TESTNG INVOKING CONFIGURATION: "Surefire test" - 
@BeforeMethod org.apache.brooklyn.camp.brooklyn.AbstractYamlTest.setUp()
2017-05-19 10:52:50,740 INFO  TESTNG PASSED CONFIGURATION: "Surefire test" - 
@BeforeMethod org.apache.brooklyn.camp.brooklyn.AbstractYamlTest.setUp() 
finished in 2 ms
2017-05-19 10:52:50,740 INFO  TESTNG INVOKING: "Surefire test" - 
org.apache.brooklyn.camp.brooklyn.catalog.CatalogYamlPolicyTest.testLaunchApplicationWithCatalogReferencingOtherCatalog()
2017-05-19 10:52:50,872 INFO  Started application 
BasicApplicationImpl{id=o720y4w0et}
2017-05-19 10:52:50,873 INFO  TESTNG PASSED: "Surefire test" - 
org.apache.brooklyn.camp.brooklyn.catalog.CatalogYamlPolicyTest.testLaunchApplicationWithCatalogReferencingOtherCatalog()
 finished in 133 ms
2017-05-19 10:52:50,873 INFO  TESTNG INVOKING CONFIGURATION: "Surefire test" - 
@AfterMethod org.apache.brooklyn.camp.brooklyn.AbstractYamlTest.tearDown()
2017-05-19 10:52:50,874 INFO  Stopping application 
BasicApplicationImpl{id=o720y4w0et}
2017-05-19 10:52:50,875 INFO  Stopped application 
BasicApplicationImpl{id=o720y4w0et}
2017-05-19 10:52:50,877 INFO  TESTNG PASSED CONFIGURATION: "Surefire test" - 
@AfterMethod org.apache.brooklyn.camp.brooklyn.AbstractYamlTest.tearDown() 
finished in 4 ms
2017-05-19 10:52:50,877 INFO  TESTNG INVOKING: "Surefire test" - 
org.apache.brooklyn.camp.brooklyn.catalog.CatalogScanTest.testAnnotationIsDefault()
[GC (Allocation Failure)  322268K->109389K(758272K), 0.0327967 secs]
[GC (Allocation Failure)  332621K->132202K(766976K), 0.0458637 secs]
[GC (Allocation Failure)  355434K->149050K(735232K), 0.0863621 secs]
[GC (Allocation Failure)  340538K->161803K(747520K), 0.0339446 secs]
[GC (Allocation Failure)  353291K->162272K(740352K), 0.0283875 secs]
2017-05-19 10:52:56,125 INFO  ENTITIES loaded for DEFAULT: 
[CatalogPolicyItemDto[org.apache.brooklyn.policy.ha.ServiceRestarter:0.0.0.SNAPSHOT/Service
 Restarter], 
CatalogEnricherItemDto[org.apache.brooklyn.enricher.stock.Aggregator:0.0.0.SNAPSHOT/Aggregator],
 
CatalogEnricherItemDto[org.apache.brooklyn.enricher.stock.Joiner:0.0.0.SNAPSHOT/Joiner],
 

[GitHub] brooklyn-docs pull request #164: Adds documentation for bundling catalog res...

[nakomis]

Github user nakomis closed the pull request at:

https://github.com/apache/brooklyn-docs/pull/164


---
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-docs issue #164: Adds documentation for bundling catalog resources ...

[nakomis]

Github user nakomis commented on the issue:

https://github.com/apache/brooklyn-docs/pull/164
  
Closing in favour of #180 


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

Roadmap to Apache Brooklyn 1.0

[Richard Downer]

Hello all,

Now that we have release 0.11.0 done, I'd like us to have a discussion
about our plans for upcoming releases, and to decide when we're going to
make the jump to version 1.0.

Looking back, the core of Brooklyn is now very strong, and has been tried
and tested by many people for many months, some using for production
workloads. The operations side has matured with the support for persistence
and high availability. Pure YAML blueprints are now extremely capable, and
the Java-based blueprints in brooklyn-library have in many cases been
overtaken by pure YAML blueprints written by Brooklyn users. The catalog
provides a way to manage and compose blueprints, with OSGI providing a
means to manage and version. Finishing touches, such as supporting ZIP
files for catalog uploads (removing the requirement that a user must create
their own OSGI bundles) mean we will have a very compelling story for
blueprint developers.

So, what's left to do? Are there any major (or even moderate) features that
we would want in a 1.0 release?

My thoughts are that we release 0.12.0 next. This will put the Karaf-based
distribution as the primary artifact, with accompanying .deb and .rpms. The
classic distribution will remain but be deprecated. At this point, we
should make an effort to mark as "deprecated" as much as we possibly can,
so we don't have to take unnecessary baggage into the 1.x series.

After that, we aim for 1.0.0 - the classic distribution is removed, and so
is everything marked as deprecated.

In parallel with this, an effort to overhaul the documentation, so that our
1.0 docs are comprehensive and easy to use.

Any other thoughts?

[GitHub] brooklyn-ui pull request #44: Switch to Java 8

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-ui/pull/44


---
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 #684: Switch to Java 8

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 issue #684: Switch to Java 8

[m4rkmckenna]

Github user m4rkmckenna commented on the issue:

https://github.com/apache/brooklyn-server/pull/684
  
Thanks @geomacy verified this locally 

merging now


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

[GitHub] brooklyn-server pull request #688: Delete deprecated rebind-hooks

[aledsage]

GitHub user aledsage opened a pull request:

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

Delete deprecated rebind-hooks

See individual commits for details.

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

$ git pull https://github.com/aledsage/brooklyn-server 
delete-deprecated-rebind-hooks

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

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


commit 846314a7734b6a251f128047fb7fbb19ca1bb69d
Author: Aled Sage 
Date:   2017-05-18T15:01:20Z

Delete deprecated persistence/rebind code

commit 4dac225ba633468cf3a362ad6dcc1bdf20eca103
Author: Aled Sage 
Date:   2017-05-18T15:14:31Z

Move `newBrooklynMemento` to RebindTestUtils

commit 3b41560c64705b0f06d16254927b03f07a9f0d4f
Author: Aled Sage 
Date:   2017-05-18T15:16:15Z

Delete `MutableBrooklynMemento`




---
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 #687: Delete deprecated classes

[aledsage]

GitHub user aledsage opened a pull request:

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

Delete deprecated classes

See individual commits for details of what is being deleted.

All the non-test code was deprecated in 0.7.0 or earlier; the test code was 
deprecated in 0.9.0 or earlier.

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

$ git pull https://github.com/aledsage/brooklyn-server 
delete-deprecated-classes

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

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


commit 093a8d1968d5c9adb8b6b2021ff7c3b40568dd70
Author: Aled Sage 
Date:   2017-05-17T18:25:56Z

Delete ShellUtils (unused & deprecated since 0.7)

commit 858fba4d49e1fd098e66f1faf96f1c0caa1963fc
Author: Aled Sage 
Date:   2017-05-17T18:34:19Z

Delete deprecated test util classes

commit 7350fd621d8b97ab5e98e20d1e7fa4aa399a4ec0
Author: Aled Sage 
Date:   2017-05-17T18:39:43Z

Delete deprecated Repeater class

commit 9911286bcdd1402acab2b7319305bb6d8fcc7076
Author: Aled Sage 
Date:   2017-05-17T18:43:27Z

Delete deprecated Yamls class

commit f665e57aa63132e0930c237d86425c9fe595bdc2
Author: Aled Sage 
Date:   2017-05-18T15:24:25Z

Delete deprecated EntityType.getEffector(name, parameterTypes…)

commit 2b1b41149fe8cb1e2f4f0f9ee3d334ac3654fdc4
Author: Aled Sage 
Date:   2017-05-18T15:39:35Z

Delete deprecated LocationSpec.id()

commit 066a38554bbefbe87bfb07c8b3a7093f1a3e20bd
Author: Aled Sage 
Date:   2017-05-18T15:48:38Z

Delete deprecated AbstractFeed constructors

commit 494dccf078a35b032e3ef248da4e0e1af2dc782a
Author: Aled Sage 
Date:   2017-05-18T15:52:41Z

Delete deprecated LocationConfigUtils methods

commit 397f9a1194a943a9cc0853d84230141dde917ac1
Author: Aled Sage 
Date:   2017-05-18T15:54:16Z

Delete deprecated BrooklynTasks

commit a1df8eb72dc4fda210e57306eddbd9b8b004615a
Author: Aled Sage 
Date:   2017-05-18T15:57:25Z

Delete deprecated EffectorUtils methods

commit fdd2e11619d6e5888d58441a933ca580fa0b2b8b
Author: Aled Sage 
Date:   2017-05-18T16:09:57Z

AbstractManagementContext.runAtEntity protected, instead of public




---
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 #686: Delete usage of Groovy ObservableList

[aledsage]

GitHub user aledsage opened a pull request:

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

Delete usage of Groovy ObservableList



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

$ git pull https://github.com/aledsage/brooklyn-server 
delete-Groovy-ObservableList-usage

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

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


commit d3c7b911fda2b26d3bd1e2e872bf6d0ef686480c
Author: Aled Sage 
Date:   2017-05-17T17:24:01Z

Delete usage of Groovy ObservableList




---
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-449) Intermittent NoClassDefFoundError (org.codehaus.groovy.runtime.InvokerHelper) invoking effector

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on BROOKLYN-449:
-

GitHub user aledsage opened a pull request:

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

BROOKLYN-449 don't use groovy for effector method calls

See https://issues.apache.org/jira/browse/BROOKLYN-449

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

$ git pull https://github.com/aledsage/brooklyn-server 
BROOKLYN-449-not-groovy-effector-calling

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

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


commit 8483359dff42f09e8117c87a588eb3b3eccd3abb
Author: Aled Sage 
Date:   2017-05-19T09:30:53Z

Rename EffectorConcatenateTest to MethodEffectorTest

commit 3984417e4a96f83ce88fb5321ab14c17fd0f128d
Author: Aled Sage 
Date:   2017-05-19T09:34:44Z

MethodEffectorTest: expand test coverage / refactor

commit 3fbd3752125a28241fa2abcb1855409a21285899
Author: Aled Sage 
Date:   2017-05-17T16:34:06Z

BROOKLYN-449: Effector method invoke don’t use Groovy




> Intermittent NoClassDefFoundError (org.codehaus.groovy.runtime.InvokerHelper) 
> invoking effector
> ---
>
> Key: BROOKLYN-449
> URL: https://issues.apache.org/jira/browse/BROOKLYN-449
> Project: Brooklyn
>  Issue Type: Bug
>Reporter: Duncan Grant
> Attachments: amp.debug.log, amp.info.log, karaf.log, karaf output
>
>
> I've seen the following error occasionally during redis deployment.  Most of 
> the time it seems to work.
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.codehaus.groovy.runtime.InvokerHelper
> I'm deploying https://github.com/brooklyncentral/brooklyn-redis-server using 
> the catalog.tests.bom
> Sorry - the logs are in kibana and I don't know how to export them.



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

[GitHub] brooklyn-server pull request #685: BROOKLYN-449 don't use groovy for effecto...

[aledsage]

GitHub user aledsage opened a pull request:

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

BROOKLYN-449 don't use groovy for effector method calls

See https://issues.apache.org/jira/browse/BROOKLYN-449

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

$ git pull https://github.com/aledsage/brooklyn-server 
BROOKLYN-449-not-groovy-effector-calling

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

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


commit 8483359dff42f09e8117c87a588eb3b3eccd3abb
Author: Aled Sage 
Date:   2017-05-19T09:30:53Z

Rename EffectorConcatenateTest to MethodEffectorTest

commit 3984417e4a96f83ce88fb5321ab14c17fd0f128d
Author: Aled Sage 
Date:   2017-05-19T09:34:44Z

MethodEffectorTest: expand test coverage / refactor

commit 3fbd3752125a28241fa2abcb1855409a21285899
Author: Aled Sage 
Date:   2017-05-17T16:34:06Z

BROOKLYN-449: Effector method invoke don’t use Groovy




---
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 issue #684: Switch to Java 8

[duncangrant]

Github user duncangrant commented on the issue:

https://github.com/apache/brooklyn-server/pull/684
  
That's a nice example of java 8ifyng code.  LGTM


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