of config from catalog items convinces me.
Can we mark it @Beta / internal in case we need to change the
approach? With that I'd be happy with your proposal.
Best
Alex
On 27/07/2017 07:23, Aled Sage wrote:
Hi Alex,
I explored setting a config key in my PR. The downsides of that
compared
an
`X-caller-request-uid` and a filter which caches them server side for a
short period of time, blocking duplicates.
Solves an overlapping set of problems. Your way deals with a
"deploy-if-not-present" much later in time.
--A
On 25 July 2017 at 17:44, Aled Sage <aled.s...@gmail.c
? Imagine an
`X-caller-request-uid` and a filter which caches them server side for a
short period of time, blocking duplicates.
Solves an overlapping set of problems. Your way deals with a
"deploy-if-not-present" much later in time.
--A
On 25 July 2017 at 17:44, Aled Sage <aled.s...@
or
source.
Go with deploymentUid or similar? Or camp.id?
Best
Alex
On 26 Jul 2017 15:00, "Aled Sage" <aled.s...@gmail.com> wrote:
Hi Mark,
We removed from EntitySpec the ability to set the id for two reasons:
1. there was no use-case at that time; simplifying the code by deleting
Hi Richard,
Thanks for raising this. FYI Alex has created a PR with tests
demonstrating the behaviour [1] you describe.
---
In the docs [2], we encourage the use of the format below for "entity"
(because there is only one thing, the `services: ` is unnecessary and
misleading - it suggests
Hi Alex,
Interesting question. A few initial thoughts:
*YOML*
YOML (PR #363) is an exceptional case - we should not use that as an
example when discussing this meta-question. The PR is 12,000 lines
(including comments/notes), and was not discussed on the mailing list
before it was submitted.
d.html/6d50d242d1ed8e98776eb871c397de1aac06d3baf600edecc53415ff@%3Cdev.brooklyn.apache.org%3E
>
> On Mon, 6 Mar 2017 at 19:48 Geoff Macartney <
> geoff.macart...@cloudsoftcorp.com> wrote:
>
>> hi Aled,
>>
>> sure, I'll have a look at that.
>>
>
Hi all,
I suggest we delete the java/groovy examples in
brooklyn-library/examples [1] (but not "webapps" in that dir, which is
used to build WAR files used in demos apps).
These do not follow the new (*) recommended way of writing blueprints.
Since then, we have written better yaml-based
10 May 2017 at 14:40 bostko <bos...@gmail.com> wrote:
edit
On 10/05/17 16:37, bostko wrote:
+1
for *deleting* contents in
https://github.com/apache/brooklyn-library/tree/master/examples except
[1]
[1]
https://github.com/apache/brooklyn-library/tree/master/examples/webapps
On 10/05/17 16:3
+1; sounds great.
I think the next steps would be for the code to be made publicly
viewable, for any 3rd party licenses etc to be checked, and then for us
to kick off a formal vote?
Richard: can you please guide us on the process?
Aled
On 10/05/2017 17:14, Duncan Johnston-Watt wrote:
+1
My guess for why it worked previously is that it used to default to centos 6,
whereas now it's using a centos 7 vm image that has different default config.
I agree it should not block the release.
Aled
Sent from my iPhone
> On 17 May 2017, at 15:25, Geoff Macartney
Thanks Mohan,
That's helpful. Really useful to get different people's perspectives for
how to summarise the key points of Brooklyn!
The diagrams are also interesting - good for communicating the control
flow to Brooklyn developers and new folk who want to contribute, or to
power-users who
+1; sounds sensible.
You said /"I propose we resolve this by recommending a version syntax
which fits what most things people are doing and which is bi-di mappable
to OSGi"/.
To clarify, I think you're saying we recommend a version syntax like of
1.0.0-SNAPSHOT (and discourage
+1 to this approach, but I suspect there's a lot more to discuss/plan.
_*Leaking OSGi*_
I agree with Geoff's worry of us "leaking OSGi". However, we should just
"leak" the semantics of bundle dependencies and versioning, which need
to be explained to the user. I think we can avoid exposing
Hi Daan,
Sounds interesting! Brooklyn seems like a good fit for what you're
looking for.
Within Brooklyn, there's a separation of the application definition and
the location to which it is to be deployed - apps can be written to be
location-agnostic. From your perspective, the good thing
in a timely way.
Best
Alex
[1] https://github.com/apache/brooklyn-server/pull/600
[2] https://github.com/apache/brooklyn-server/pull/575
On 02/05/2017 19:21, Aled Sage wrote:
Hi Alex,
Interesting question. A few initial thoughts:
*YOML*
YOML (PR #363) is an exceptional case - we shou
+1 (binding)
On 08/05/2017 11:55, Richard Downer wrote:
There have been recent discussions about how the committers assess PRs for
merging. The discussion is summarised below and the original thread
available at [1].
The consensus of the discussion is to adopt new standards for committers
+1 (binding)
On 31/05/2017 11:56, Andrew Kennedy wrote:
All,
- https://github.com/cloudsoft/brooklyn-container-service
This repository contains Brooklyn Container Service, which is a set of
locations and entities for Apache Brooklyn that allow deployment of
applications to container based
Hi all,
I'd like to deprecate the `@Catalog` annotation [1], and the support for
`scanFromAnnotations` [2].
Previously, we annotated some entity/policy Java classes with catalog
information, such as descriptions and icon urls. However, we've moved to
using .bom files as the way to define
Hi all,
TL;DR: low-level discussion of error-handling, and entity state; should
we change what we set the entity's "expected state" to when there are
errors?
---
I'm trying to fix https://issues.apache.org/jira/browse/BROOKLYN-534
(when stopping, ensure the `ServiceRestarter` doesn't
for things beyond my use-case?
Yes. I needed this exact functionality last week - for a piece of code shared
between all applications. I ended up writing a poller thread that monitors the
state.
I think it will be a useful thing to add.
Svet.
On 22.03.2017 г., at 19:11, Aled Sage <aled.s...@gmail.
/v2/catalog?category=enricher
/v2/catalog?category=location
Doubt 'category' is quite right but something appropriate.
Geoff
On Wed, 20 Sep 2017 at 18:37 Aled Sage <aled.s...@gmail.com> wrote:
Hi all,
For `/subtypes` versus `/types`, it's not really about code
duplication.
It's that the A
ree with the points
made
there.)
My answers:
(1) slight preference for the `/catalog` prefix
(2) strong pref to deprecate old calls - they are redundant and multiple
is
confusing
(3) strong pref to stay with `/v1` for now
(4) slight pref for explicit `[/catalog]/subtypes` endpoint
Best
Alex
On
Thanks Alex.
As per my comment in the PR at
https://github.com/apache/brooklyn-server/pull/810#issuecomment-330824643.
---
TL;DR:
Given this is a big API change and given I'm suggesting a `/v2` REST api
then I wanted to raise it on the list as well.
I propose we split this PR into two. The
Hi all,
I want to change how Brooklyn populates its catalog at startup. I want
it to install the "initial catalog", and then add the items from
persisted state.
See the PR at [1].
---
Currently, if there is any persisted state then we ignore the "initial
catalog" and use only the persisted
Hi all,
I approach this question as "what is essential for a 1.0 release",
versus nice-to-have. I think pretty much every feature/change is
nice-to-have and can be developed incrementally - if it's ready in time
for a 1.0 then great, otherwise it will go in 1.x or 2.x.
I personally have
+1 (binding)
I focused mainly on upgrade and rebind testing:
* I deployed a simple app to AWS, which I susbsequently used for testing.
* Tested upgrade from 0.11.0 to 0.12.0-rc3 on CentOS 7.
(I installed 0.11 and deployed an app, then followed the
instructions in
+1
On 03/10/2017 16:33, Duncan Godwin wrote:
Hi All,
Following the release last week of Apache Brooklyn 0.12.0 I propose that we
make the next version of Apache Brooklyn 1.0.0.
Apache Brooklyn is robust, stable, feature rich and being used in
production by multiple enterprises. Our
On 26/09/2017 09:53, Aled Sage wrote:
Hi all,
TL;DR: I propose we *delete* support for `--catalogReset`, for the
next release. It's not supported in karaf mode, and it's dangerous
(could break rebind of entities)!
Note that I'm not suggesting deprecate. We've moved to karaf as the
default
Hi all,
TL;DR: I propose we *delete* support for `--catalogReset`, for the next
release. It's not supported in karaf mode, and it's dangerous (could
break rebind of entities)!
Note that I'm not suggesting deprecate. We've moved to karaf as the
default in 0.12 release, so effectively the
Hi Taylor, thanks for getting in touch.
Improving the docs would be awesome!
Is there a use-case you have in mind as well, or is it to just get a
better understanding of how Brooklyn works?
---
See
http://brooklyn.apache.org/v/latest/blueprints/java/entities.html#softwareprocess-lifecycle
Hi all,
I propose that we *delete* Brooklyn classic-mode from master now, in
preparation for the 1.0.0 release.
---
In 0.12.0, we switched the main distro to be the karaf-mode. We also
built the classic-mode distro - the intent being for users to have a
usable classic mode, rather than
Downer <rich...@apache.org> wrote:
+1
On 15 September 2017 at 14:12, Aled Sage <aled.s...@gmail.com> wrote:
Hi all,
I'd like to deprecate the `@Catalog` annotation [1], and the support for
`scanFromAnnotations` [2].
Previously, we annotated some entity/policy Java classes with catalog
Hi all,
I'd like to change the default value of highAvailabilityMode from
DISABLED to AUTO.
Currently, if you start two Brooklyn servers pointing at the same
persisted state (file-system directory or object store's bucket), then
they are independent (because HA is 'disabled' by default).
For these changes, please review:
* https://github.com/apache/brooklyn-server/pull/964
* https://github.com/apache/brooklyn-server/pull/966
On 24/05/2018 15:22, Aled Sage wrote:
Hi all,
I'd like to improve the efficiency of Brooklyn persistence - depending
on your entities, a lot
Geoff, all,
I've added some docs (about behaviour when there is a single server):
https://github.com/apache/brooklyn-docs/pull/254
Aled
On 24/05/2018 16:37, Aled Sage wrote:
Thanks all,
Here's the PR to change the default behaviour:
https://github.com/apache/brooklyn-server/pull/965
14:51 Duncan Grant <duncan.gr...@cloudsoft.io>
wrote:
Aled,
+1 sounds like a sensible plan
Duncan
On Tue, 22 May 2018 at 13:59 Aled Sage <aled.s...@gmail.com> wrote:
Hi all,
I'd like to change the default value of highAvailabilityMode from
DISABLED to AUTO.
Currently, if you
Hi all,
I'd like to improve the efficiency of Brooklyn persistence - depending
on your entities, a lot of files/objects can be written a lot of times.
This results in overly high traffic to the persistence directory (be it
an object store like S3, or the file system).
Below are three big
me init better describes what
we
are doing anyway given there is no option to log out.
Regards
Duncan
On Mon, 11 Jun 2018 at 17:49 Aled Sage wrote:
Hi all,
TL;DR: I want to add `--endpoint` to the br command, because `br login`
has global scope.
We at Cloudsoft use `br` in our qa jenkins
Hi all,
TL;DR: I want to add `--endpoint` to the br command, because `br login`
has global scope.
We at Cloudsoft use `br` in our qa jenkins jobs. However, the `br login`
command has global scope. This means that two jobs run on the same
jenkins slave (both running as user `jenkins`) will
+1
On 29/05/2018 18:23, Mark McKenna wrote:
+1 Will be a great addition
On Mon, 28 May 2018 at 19:04, John McCabe wrote:
Awesome +1
On Mon, May 28, 2018 at 2:05 PM Andrea Turli wrote:
+1
On 28 May 2018 at 14:51, Duncan Grant wrote:
+1 (non-binding)
This will make it much easier
Hi Duncan,
Agree, this can be an issue for folk not specifying the explicit
instance type - either it not working in newer regions, or it choosing a
sub-optimal instance type.
It is tracked in:
* https://issues.apache.org/jira/browse/BROOKLYN-582
*
Hi all,
I propose we make it mandatory to specify the bundle id and version
(currently it is optional).
I think we should do this asap, before 1.0.0 is released.
This is a breaking change - it will require users to add a `bundle: ...`
line to their .bom files (if they are not supplying the
deprecate or make it a breaking change.
Deprecating feels right, though I think it would mean we can't
actually remove until 2.0 ?
Best
Alex
On 26/10/2017 12:06, Aled Sage wrote:
Hi all,
I propose we make it mandatory to specify the bundle id and version
(currently it is optional).
I
Hi all,
I agree with Geoff: documenting the different approaches as you've done
here sounds like the best way forward.
---
Note that:
br catalog add
https://github.com/brooklyncentral/brooklyn-dns/archive/master.zip
is not the same as:
br catalog add
#982 - better type coercion
#971 - location DSL
There are a few others in library, docs, and dist, which we should take
care of as general housekeeping but not ahead of an M1 IMO.
Best
Alex
On 03/09/2018 13:24, Aled Sage wrote:
+1
Assuming there's consensus, shall we give 24 ho
+1 to deprecating it Thomas.
Alex, I agree with you in general. In this case, we don't particularly
care about a yaml equivalent of jboss 7 because it's so old. We would
like a yaml blueprint for wildfly [1] in the community at some point. I
thought that someone had done that in the past, but
Hi all,
The Apache Brooklyn master build [1] has failed the last couple of times
for the Go build of brooklyn-client (see end of email for the error text).
It looks to me like our dependency github.com/NodePrime/jsonpath has
been deleted! It definitely used to be there (lots of google hits
Hi all,
Our brooklyn-ui PR builds (e.g. [1]) were failing with the same error as
is given in INFRA-17055 [2].
```
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags
--progress git://github.com/apache/brooklyn-ui.git
+refs/pull/*:refs/remotes/origin/pr/*" returned status
+1
Assuming there's consensus, shall we give 24 hours for folk to get any
outstanding PRs submitted/merged, before we kick an RC1 etc?
Aled
On 03/09/2018 13:17, Richard Downer wrote:
All,
It's probably about time we made a release - shockingly, it's been nearly a
year since the last one.
Hi all,
Do any brooklyn folk know what the
`brooklyn-master-build-docker_ws-cleanup_.*` workspaces are for, and why
they are not being cleaned up?
It sounds like this bug in ws-cleanup-plugin [1]. It was fixed, but then
folk reported that they were still experiencing the same problem [2].
straints between each config -
On X:
constraints:
- requiredUnless("Y")
- forbiddenIf("Y")
On Y:
constraints:
- requiredUnless("X")
- forbiddenIf("X")
Geoff
On Tue, 18 Sep 2018 at 17:05 Aled Sage wrote:
Hi all,
I'd like to ad
'm looking
into how we could do this.
Are there any good example configurations of other Apache projects
building and running tests (ideally using maven) in docker containers,
on apache jenkins slaves?
Aled
On 21/09/2018 10:03, Aled Sage wrote:
Hi all,
Do any brooklyn folk know what the
`brook
Hi all,
TL;DR: I've hit a problem with rebinding to historic persisted state,
when wrap:mvn has been used for OSGi bundles - the symbolic name
changed, so classloading didn't work on rebind. Which of the solutions
should we go for?
_*PROBLEM*_
The persisted state refers to a class in
://github.com/apache/brooklyn-library/blob/master/Jenkinsfile
On 24/09/2018 15:20, Aled Sage wrote:
Hi Chris, all,
Thomas has just pointed me at
https://issues.apache.org/jira/browse/INFRA-16417, in which you recommend:
"The problem is the bind mount for .m2 and permissions conflicts
be
+1 from me.
We need "Consensus in the project (documented via the mailing list)" - I
interpreted that as us needing a formal vote, but if an informal email
thread will do then that's fine with me
Aled
On 12/12/2018 16:41, Richard Downer wrote:
Brooklyn team,
Apart from myself, I don't
Hi Brooklyn community members,
We use https://git-wip-us.apache.org/repos/asf/brooklyn, so this impacts us.
We have the choice of waiting a month or two, or volunteering to move to
either gitbox.apache.org OR github [1] for our development and code pushes.
Being able to merge pull requests
Hi all,
TL;DR: we should reconfigure the `brooklyn-ui` build (and probably
others) to be triggered daily and/or when `brooklyn-server` builds.
_*
Problem*_
Our brooklyn-ui build is configured to only run when the repo changes
[1]. However, its parent pom is
+1 from me.
Here's what I tested:
1. installed/ran brooklyn (tar.gz) from local machine (os x); used it
to spin up a blueprint for...
2. install/run brooklyn (rpm) on CentOS machine in AWS
3. deployed each of the 4 templates to aws:
1. server-template
2. bash-web-server-template
/ReleaseNote.jspa?projectId=12311140=12342748
[2] https://issues.apache.org/jira/browse/KARAF-5860
[3] https://securitytracker.com/id/1041194
[4] https://github.com/apache/brooklyn-server/blob/master/pom.xml#L173
On 15/09/2018 10:55, Aled Sage wrote:
The build is failing because karaf has jetty 9.3.14
The build is failing because karaf has jetty 9.3.14, but we tried to
upgrade our dependency to 9.3.24 [1].
At least I think that is the cause, based on the clue in [2].
I’m not at my computer just now so can’t check properly what versions of
jetty is included in karaf / pax web versions.
If we
Hi all,
I'd like to add support for more sophisticated config constraints, where
there are inter-dependencies between config keys. I'd like the blueprint
composer web-console to understand (a small number of) these, and thus
to give feedback to the user about what is required and whether
nt level with this latest Karaf.
Cheers
Geoff
On Mon, 2 Dec 2019 at 13:28, Aled Sage <mailto:aled.s...@gmail.com>> wrote:
Hi all,
TL;DR: I'm looking at upgading CXF from 3.2.8 to 3.3.2.
---
For dependency:
system//javax/mail/mail: [1.4.7, 1.4.4]
notation, it was
happy to just use org.apache.felix.framework.
Aled
[1]
http://mail-archives.apache.org/mod_mbox/cxf-users/201912.mbox/%3C9a1d1ab6-8d00-234d-29b0-c86c31506c87%40gmail.com%3E
[2]
http://karaf.922171.n3.nabble.com/features-xml-dependency-quot-true-quot-td3286359.html
On 04/1
/gson/gson: [2.5, 2.3]
I'll take a look at these and see if they really are a problem or not.
Aled
[1] https://github.com/apache/brooklyn-server/pull/1068
[2] https://github.com/apache/brooklyn-server/pull/1069
On 02/12/2019 09:27, Aled Sage wrote:
Hi,
Thanks Ludo, all: - great list, and
Hi,
Thanks Ludo, all: - great list, and +1 from me.
I think most of those sound fairly small and manageable.
The one that stands out as potentially hard is the "Karaf version bump"
(which would fix the "Two different versions of jetty-server"). We've
had problems in the past getting all
/org.apache.aries.spifly.dynamic.bundle:
[1.2.2, 1.2]
Feature 'jetty' brings in v1.2.2, whereas feature 'pax-jetty' brings in
v1.2, so it's out of our control.
Aled
On 02/12/2019 10:38, Aled Sage wrote:
Hi all,
I see there was great progress with the karaf version bump last week
and over
Thanks Martin,
Which environment(s) is it passing and failing in?
If this works in our apache jenkins and for contributors locally, and
especially if the environment it fails in is "niche" then a +1 from me
for skipping the test so we can get the release candidate built.
Aled
p.s. the test
Hi Geoff, all,
For using vagrant, Iuliana said:
"Successfully started unpacked and started
apache-brooklyn-1.0.0-rc3-vagrant.zip. All nodes were correctly created."
Geoff, did your steps match the vagrant instructions at
http://brooklyn.apache.org/v/latest/start/running.html?
+1 from me.
I did some exploratory testing on OS X with the tar.gz, and deployed a
few blueprints.
--
For the dockerfile not working out-of-the-box with base image
`maven:3.6.3-jdk-8`, that's something we should include in the release
notes (saying what the simple workaround is). However,
Hi all,
I believe we are (finally!) ready to produce Apache Brooklyn 1.0.0 RC1.
Assuming folk agree, then we can kick off the RC1 release process and
build it over the weekend or Monday.
Please give an information +1 or -1 (we'll do a proper vote on the
actual RCs).
---
We proposed a
Hi Thomas,
Sounds really interesting.
I'd view the docs issues slightly differently: what are our biggest pain
points and what should be the first incremental steps to solve those?
I think the biggest pain points (and thus biggest bang for buck) are:
_*1. How to build and release the
Hi Justin,
Thanks for spotting this and reaching out.
Looking at the license/notice generation, I think there are two things
that went wrong for 1.0 release:
1. The maven license plugin [1] picked the wrong license for
dependencies when there were multiple to choose from (i.e. LGPL vs
Aled Sage created BROOKLYN-199:
--
Summary: Web-console activity view shows wrong entity after using
browser's back-button
Key: BROOKLYN-199
URL: https://issues.apache.org/jira/browse/BROOKLYN-199
Project
[
https://issues.apache.org/jira/browse/BROOKLYN-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aled Sage resolved BROOKLYN-184.
Resolution: Fixed
Assignee: Aled Sage
Fix Version/s: 0.9.0
> Entities to be a
Aled Sage created BROOKLYN-212:
--
Summary: Auto-scaling in finite BYON cluster keeps adding on-fire
entities
Key: BROOKLYN-212
URL: https://issues.apache.org/jira/browse/BROOKLYN-212
Project: Brooklyn
Aled Sage created BROOKLYN-209:
--
Summary: Web-console application tab rendered badly: tree not shown
Key: BROOKLYN-209
URL: https://issues.apache.org/jira/browse/BROOKLYN-209
Project: Brooklyn
[
https://issues.apache.org/jira/browse/BROOKLYN-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aled Sage updated BROOKLYN-209:
---
Attachment: Screen Shot 2015-12-19 at 20.19.47.png
> Web-console application tab rendered ba
Aled Sage created BROOKLYN-214:
--
Summary: OutOfMemoryError (too many threads): repeated calls to
AttributeWhenReady
Key: BROOKLYN-214
URL: https://issues.apache.org/jira/browse/BROOKLYN-214
Project
Aled Sage created BROOKLYN-297:
--
Summary: Support yaml DSL for "name"
Key: BROOKLYN-297
URL: https://issues.apache.org/jira/browse/BROOKLYN-297
Project: Brooklyn
Issue Type: I
Aled Sage created BROOKLYN-292:
--
Summary: jetty "broken pipe" exceptions logged at warning if
browser stops loading web-console welcome page
Key: BROOKLYN-292
URL: https://issues.apache.org/jira/browse/BR
Aled Sage created BROOKLYN-291:
--
Summary: Manually setting service.isUp is overwritten by enricher
(causing non-deterministic test failures)
Key: BROOKLYN-291
URL: https://issues.apache.org/jira/browse/BROOKLYN-291
Aled Sage created BROOKLYN-295:
--
Summary: jclouds-openstack destroyNode failed after VM failed to
provision: id must be in format regionId/id
Key: BROOKLYN-295
URL: https://issues.apache.org/jira/browse/BROOKLYN-295
Aled Sage created BROOKLYN-298:
--
Summary: sshj hangs (waiting for shell to finish) after script
completed - maybe VPN went down+up during exec
Key: BROOKLYN-298
URL: https://issues.apache.org/jira/browse/BROOKLYN
[
https://issues.apache.org/jira/browse/BROOKLYN-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aled Sage resolved BROOKLYN-289.
Resolution: Duplicate
> Broken link in brooklyn-client README
[
https://issues.apache.org/jira/browse/BROOKLYN-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aled Sage resolved BROOKLYN-293.
Resolution: Fixed
Fix Version/s: 0.10.0
> Web-console should not allow directory list
[
https://issues.apache.org/jira/browse/BROOKLYN-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325856#comment-15325856
]
Aled Sage commented on BROOKLYN-282:
See PRs:
* https://github.com/apache/brooklyn-server/pull/185
[
https://issues.apache.org/jira/browse/BROOKLYN-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aled Sage resolved BROOKLYN-273.
Resolution: Fixed
Fix Version/s: 0.10.0
> VanillaSoftwareProcess.restart() should call
Aled Sage created BROOKLYN-299:
--
Summary: Stopping app takes long time: blocked on
LocalUsageManager.recordLocationEvent, waiting for ssh connection timeout
Key: BROOKLYN-299
URL: https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/BROOKLYN-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aled Sage resolved BROOKLYN-271.
Resolution: Fixed
Fix Version/s: 0.10.0
> ConfigKey card shows object hashCode of defa
[
https://issues.apache.org/jira/browse/BROOKLYN-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aled Sage resolved BROOKLYN-284.
Resolution: Fixed
Fix Version/s: 0.10.0
> Deadlock in entity creation, when toStr
[
https://issues.apache.org/jira/browse/BROOKLYN-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325854#comment-15325854
]
Aled Sage commented on BROOKLYN-287:
As commented in the duplicate (BROOKLYN-300)...
To work
[
https://issues.apache.org/jira/browse/BROOKLYN-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aled Sage resolved BROOKLYN-300.
Resolution: Duplicate
> MySQL provisioning fails on centos when perl not on base
[
https://issues.apache.org/jira/browse/BROOKLYN-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15331936#comment-15331936
]
Aled Sage commented on BROOKLYN-297:
There is a workaround for this, using the config
[
https://issues.apache.org/jira/browse/BROOKLYN-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15331376#comment-15331376
]
Aled Sage commented on BROOKLYN-282:
Note that with 0.10.0 and later, it will be important to always
[
https://issues.apache.org/jira/browse/BROOKLYN-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aled Sage resolved BROOKLYN-286.
Resolution: Fixed
Fix Version/s: 0.10.0
> merge config keys map values, where appropri
[
https://issues.apache.org/jira/browse/BROOKLYN-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305409#comment-15305409
]
Aled Sage commented on BROOKLYN-272:
Also encountered a non-deterministic failure
[
https://issues.apache.org/jira/browse/BROOKLYN-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aled Sage resolved BROOKLYN-285.
Resolution: Fixed
Fix Version/s: 0.10.0
> Dangling reference in Propagator.producer:
Aled Sage created BROOKLYN-285:
--
Summary: Dangling reference in Propagator.producer: can cause
subscription to self, and infinite subscription loop
Key: BROOKLYN-285
URL: https://issues.apache.org/jira/browse
Aled Sage created BROOKLYN-284:
--
Summary: Deadlock in entity creation, when toString() calls
getConfig
Key: BROOKLYN-284
URL: https://issues.apache.org/jira/browse/BROOKLYN-284
Project: Brooklyn
101 - 200 of 660 matches
Mail list logo
