I agree with Alex's philosophy: make most/simple blueprints work well
out-of-the-box with minimal configuration. But allow it to be fully
controlled for power users or more advanced use-cases.
---
How about also a config option of something like:
inboundPorts.autoInfer=true
If explicitly
Hi all,
I suggest we rename the entity SimpleShellCommandTest [1] to
TestSshCommand. This would make it more consistent with the naming of
things like ShellFeed [2] and SshFeed [3]: "shell" means executing a
command on the local brooklyn server, whereas "ssh" means executing a
command on the
for
thoroughness as well).
Aled
On 07/06/2016 10:53, Alex Heneveld wrote:
+1
On 07/06/2016 11:37, Aled Sage wrote:
Hi all,
I suggest we rename the entity SimpleShellCommandTest [1] to
TestSshCommand. This would make it more consistent with the naming of
things like ShellFeed [2] and SshFeed [3
Hi all,
TL;DR we hopefully have a fix for what might have caused many tests to
fail non-deterministically. Please review.
Having investigated a few non-deterministic tests, I think I've finally
got to the bottom of what might be causing some/many of them to fail.
I've raised a Jira and a
ing the override can define whether he prefers merge or override.
It makes sense when developing blueprints because you know what the
catalog items being inherited are and can decide which way to go.
Svet.
On 25.05.2016 г., at 14:12, Aled Sage <aled.s...@gmail.com> wrote:
Hi
Hi all,
This is now merged into master - the docs are at
https://github.com/apache/brooklyn-docs/blob/master/guide/yaml/entity-configuration.md
Aled
On 01/06/2016 19:26, Aled Sage wrote:
Hi all,
I've created https://issues.apache.org/jira/browse/BROOKLYN-286 to
capture this.
I've
Hi all,
I've added to the Brooklyn ops troubleshooting guide [1], a page on how
to investigate a slow or unresponsive Brooklyn server [2]. I also added
a page about diagnostics that can be collected [3].
Hopefully you'll find these useful.
Please do add to (and correct) it. Or let me know
making merge work in the
general case of leaf nodes in an arbitrary tree structure is going to be
required anyway.
Basically, if we follow the principle of least surprise when
implementing,
it should also be reasonably intuitive.
Andrew.
On Wed, 25 May 2016 at 21:56 Aled Sage <ale
Hi Valentin,
As per the discussion in you PR #151, I think this has been superseded
by the discussion in the thread "[PROPOSAL] merging config keys".
There is now a jira issue [1] and a PR [2] for it.
I'd appreciate through thoughts as to whether that PR meets your
requirements.
Aled
On
Hi all,
The YAML format for adding catalog items accepts several different ways
of defining them. This has led to our examples being inconsistent, our
code more complicated, and potential confusion for users when they see
different things that turn out to mean the same.
I think we should
+1
Sent from my iPhone
> On 14 Jan 2016, at 17:10, Ciprian Ciubotariu wrote:
>
> This seems to clear up the way locations are assigned in these corner cases,
> making blueprint authoring an easier task.
>
> +1
>
>> On Thursday 14 January 2016 15:52:01 Alex Heneveld
Hi all,
I'd like to write a bash-based entity that has different shell.env per
command (e.g. for install and customize).
_*Proposal*_
The entity configuration could look like the following:
services:
- type: org.apache.brooklyn.entity.software.base.VanillaSoftwareProcess
Thanks Alex, sounds great.
I'm running through the brooklyn-repo-split release script locally now,
to reproduce.
A few initial comments...
---
https://github.com/ahgittin/brooklyn-repo-split/blob/master/README.md
needs updated.
It says that "Steps 1 and 2 are done and checked in as reorg*
Thanks for pointing this out Robert.
TL;DR: does anyone working on OSGi recently have bandwidth to look at
this please?
---
The failing test is
org.apache.brooklyn.AssemblyTest.checkBrooklynCoreFeature (in
brooklyn-itest).
---
Perhaps unrelated, this test also failed non-deterministically
Hi Duncan,
Agree this is not intuitive, and doesn't work for you "out of the box".
What you can do is supply the contents of brooklyn.properties, to set up
the authentication you require. For example:
services:
- type: org.apache.brooklyn.entity.brooklynnode.BrooklynNode
Hi, thanks for the offer!
I think the initial/primary focus would be on the code in [1], and the
other associated Apache Brooklyn repos [2,3,4,5,6].
The downstream projects like
https://github.com/brooklyncentral/advanced-networking are also
important, but not as important as the core of
Hi Aleksandr,
It's in the root's pom.xml: if you use -Dno-go-client then it disables
the profile that adds the brooklyn-client module to those being built by
maven.
go-client
!no-go-client
candidate.
Aled
[1] http://brooklyn.apache.org/download/index.html
On 06/04/2016 18:31, Aled Sage wrote:
Thanks Sam,
That is now cherry-picked into 0.9.0. Agree it is low-risk and worth
including.
---
Can someone please review and test John's
https://github.com/apache/brooklyn-dist/pull/31
the cutoff I'd like
https://github.com/apache/brooklyn-server/pull/99 to be included.
On 6 April 2016 at 17:19, Richard Downer <rich...@apache.org> wrote:
On 6 April 2016 at 17:17, Aled Sage <aled.s...@gmail.com> wrote:
I believe that Richard is discussing which Geoff about which
bro
://github.com/apache/brooklyn-dist/pull/32
Thanks!
Best Regards,
Aleksandr Vasilev
DevOps Engineer | Cloudsoft Corporation
On 7 April 2016 at 23:42, Aled Sage <aled.s...@gmail.com> wrote:
Hi all,
Based on the bug Svet found, and his -1, I'm cancelling the 0.9.0 rc3 vote.
I've cherry-
Thanks all.
John has fixed this [1]. I'll review, merge, and cherry-pick to the
0.9.0 branch.
Given we are producing another release candidate anyway, can we include
the fix for BROOKLYN-249 (see [2,3]). Can someone please review that and
give their opinion for whether it should be included
1 non-binding +1s, and no 0 or -1.
Vote thread link:
https://mail-archives.apache.org/mod_mbox/brooklyn-dev/201604.mbox/%3CCABQFKi2rBXoGSD5MoAbePJx71RD7KZZx1nbPO-sjuGk45HYvyA%40mail.gmail.com%3E
Binding +1s:
Andrea Turli
Aled Sage
Svetoslav Neykov
Non-binding +1s:
Aleksandr Vasilev
Thanks to ev
Regarding Svet's finding that RiakCluster has a problem:
Found a problem with template 3 - it's failing because of a problem
in RiakCluster. It's swapping the install scripts for redhat and
debian based systems, see [1].
[1]
+1 (binding)
I've checked the sha1, sha256, md5 and .asc of each artifact using the
script attached (which is a tweaked version of Andrea's script). This
also confirms that each .tar.gz and .zip file can be unpacked successfully.
I launched brooklyn successfully, and deployed to AWS a Riak
s zero. I will elaborate this
with an example
if test -z `which dir`; then echo executing the other; else echo
executing dir; fi
---
Aled, I think Riak is not tested in CentOS 7. The installation steps
should be the same but it may have some small differences with
firewall or else.
Valentin.
On
platform artifacts are required. Once that is agreed and
sorted, then I think we are good to go.
Last chance before the RC: any more bugs that need addressed or PRs that
you think need merged/cherry-picked?
Aled
On 06/04/2016 17:03, Aled Sage wrote:
Thanks Thomas.
I've cherry-picked PR #23
have (documents the go 1.6 requirement).
Svet.
[1] https://github.com/apache/brooklyn-client/pull/14
<https://github.com/apache/brooklyn-client/pull/14>
[2] https://github.com/apache/brooklyn-client/pull/15
<https://github.com/apache/brooklyn-client/pull/15>
On 5.04.2016 г., at
+1 (binding)
I have:
* Verified the sha1, sha256, md5 and asc for each of the artifacts.
* Verified that each zip and .tar.gz could be unpacked
* Installed the RPM
* Installed + launched from the .tar.gz
* Deployed a tomcat app to OpenStack
On 01/04/2016 16:58, Richard Downer wrote:
Hi all,
When running our LoadTest on master (i.e. same code as 0.9.0 release
candidate), I hit the deadlock described at [1]. I think others are
unlikely to hit it, but given the consequences I suggest we fix it for
the 0.9.0 release and produce another release candidate. I've fixed it
in
Hi Yavor,
I favour option 2.
When you say "post-install", I think this can be part of the commands
for installing java rather than using the VanillaSoftwareProcess
"post.install.command".
--
For SameServer entity, then it's the responsibility of the blueprint
author (i.e. the person
ent you in a private email the think to the proposal).
Best,
Jose
El 12/04/2016, a las 23:39, Aled Sage <aled.s...@gmail.com>
escribió:
Hi Jose,
The timeline on https://community.apache.org/gsoc.html says the
next
steps are:
* 2016-04-12: Proposals to ASF projects must be reviewed ro
13:27, Richard Downer wrote:
Hi Aled,
What did you use as the base for the branch? The
`rel/apache-brooklyn-0.9.0` tag or something else?
Richard.
On 26 April 2016 at 13:17, Aled Sage <aled.s...@gmail.com> wrote:
Hi all,
I've created a 0.9.x branch (at version 0.9.1-SNAPSHOT) for
Hi all,
TL;DR: let's disable non-deterministic failing unit tests while they are
being fixed.
---
We have a small number of non-deterministic test failures that are
causing false-negatives when jenkins builds master or builds a PR branch.
Clearly we should fix these tests (either
ge and that it's non-deterministic. Otherwise we risk someone
coming along later, saying "works for me" and re-enabling it without
sufficient investigation.
Aled
On 24/05/2016 09:54, Aled Sage wrote:
Hi all,
TL;DR: let's disable non-deterministic failing unit tests while they
a
ay 2016 at 14:28, Andrea Turli <
andrea.tu...@cloudsoftcorp.com
wrote:
Great discussion guys!
It seems that it is a shared need, and I wanted to discuss with
you
as
I
was not sure about my approach.
Andrew,
I like your proposal, thanks!
Thanks,
Andrea
On 3 May 2016 at 13
those tests. However, I would use the
`enabled=false` parameter[1] of the `@Test` annotation instead of commented
them out.
[1] http://www.mkyong.com/unittest/testng-tutorial-3-ignore-test/
On Tue, 24 May 2016 at 09:54 Aled Sage <aled.s...@gmail.com> wrote:
Hi all,
TL;DR: let's disab
Hi all,
TL;DR: we should merge config when overriding entities/locations, where
it's obvious that such behaviour is desired. For example, where an
entity type defines shell.env, then a new entity extending this type
should inherit and add to those values.
_*REQUIREMENTS*_
_*shell.env in
Hi Graham,
There are many ways to tackle this problem - the general philosophy in
Brooklyn is to do it in the way that is best practice for the software
under management (sorry that's a bit vague!).
Are these "replicated components" stateless, which need upgraded?
If you can entirely
h MUST appear in this order: type, id, name, description, services
9. Names MUST be quoted strings
10. The description value MUST use the multi-line string syntax
11. Parameters SHOULD use the following keys, which MUST appear in this
order: name, label, description, type, default, constraints
Hi all,
Motivated by Andrew's recent PR [1] and Svet's suggestion, I'd like to
propose a change to the semantics/arguments to
$brooklyn:attributeWhenReady().
_*Current Behaviour*_
_Simple example_
If you write in a YAML blueprint something like:
brooklyn.config:
myurl:
Hi all,
We are looking at implementing a "cleaner" that can remove orphaned
locations from persisted state.
_*Problem statement*_
In older versions of Brooklyn (e.g. prior to [1]), we sometimes did not
unmanage locations when the associated entity was deleted. This means
that the persisted
+1
I don't know of anyone who would be negatively impacted by the defaults
changing from ubuntu to centos.
---
Switching from ubuntu 14.04 to 16.04 as the default ubuntu might well
break some blueprints though (as I've seen examples that just use
`osFamily: ubuntu`, without an explicit
Hi all,
I propose we switch to Java 8 for Apache Brooklyn (i.e. require Java 8;
remove support for using Java 7 when running Brooklyn).
This will make our testing simpler, improving coverage (e.g. we don't
currently test everything with Brooklyn running both on Java 7 and Java
8). It will
Hi all,
I'd like to resurrect the discussion of whether the yaml DSL should
support invoking effectors.
See https://github.com/apache/brooklyn-server/pull/155. (That was
merged, but Alex will revert it while we discuss if we want it, and if
so then how it would behave).
If folk have
licName and version - they can be
auto-generated.
Svet.
On 20.12.2016 г., at 17:50, Aled Sage <aled.s...@gmail.com> wrote:
Hi all,
+1
(D) sounds good. What version are you imagining the bundle would be, if one
runs `br catalog add ~/my/project/ --name com.example.myproject`?
---
I li
ecifying, but the catalog item versions too? (I
guess unless the item explicitly supplies its own version.)
Geoff
On Wed, 1 Mar 2017 at 17:26 Aled Sage <aled.s...@gmail.com> wrote:
Hi all,
Discussion of the REST api kicked off again in
https://github.com/apache/brooklyn-server/pull/485#issu
the child entity I suggested at #155 -- until we have sequence
effector YAML. Is there anything `$brooklyn:effector` gives us that an
initializer wouldn't do in a cleaner way?
Best
Alex
On 1 March 2017 at 11:54, Aled Sage <aled.s...@gmail.com> wrote:
Hi all,
I'd like to resurrect the discussion of whet
Hi all,
I'd like to remove from Brooklyn the feature where you can login
authenticated from localhost.
_*
Current Situation*_
When you first start Brooklyn on a new machine (so no
brooklyn.properties etc), it will auto-generate an initial username +
password and log that. For example:
.
And for Brooklyn on a server, I think we should taking security
seriously so not allow unauthenticated access from any user who does a
curl command from that server!
Aled
On 08/09/2016 15:35, Aled Sage wrote:
Hi Mike,
That touches on a bigger piece of work: to look at the runtime
management of user
Aled Sage <aled.s...@gmail.com> wrote:
Hi all,
I'd like to remove from Brooklyn the feature where you can login
authenticated from localhost.
_*
Current Situation*_
When you first start Brooklyn on a new machine (so no
brooklyn.properties etc), it will auto-generate an initial us
(And do people really evaluate software on a shared server, in this
day and age???)
Best
Alex
On 08/09/2016 15:42, Aled Sage wrote:
I'd expect a lot of folk evaluating Brooklyn for real use-cases to
install Brooklyn on a server, rather than their laptop owned by their
employer. Or for t
+1
Alex has merged this PR.
Aled
> On 29 Aug 2016, at 17:52, Andrew Kennedy
> wrote:
>
> All,
>
> I've run into an issue with the `SoftwareProcess` entities, where the default
> inheritance settings for configuration keys like `install.command` and so on
ash screen that browsers show if you
have
a self-signed cert is a compelling reason in my mind to adopt the same
philosophy, start easy and document security, rather than start secure
but
hard-to-use.
--A
On 08/09/2016 16:58, Aled Sage wrote:
Hi Alex,
Good points.
Are you strongly against
Hi Sam,
Long term, we want to switch to just Karaf (installed via RPM/DEB).
However, before we switch to Karaf being the "official Brooklyn way",
we'll need to spend some more time working on Karaf and on RPM/DEB.
(The previous RPM/DEB work was against the tgz dist, and will need
revisiting).
+1 for single brooklyn-client repo with subfolders 'cli' and 'java'.
Aled
On 09/09/2016 13:41, Geoff Macartney wrote:
hi Alex et al.
I guess those are fair points - it still makes me a bit queasy but I’ll go with
the majority if they are happy to move it there. Don’t think I voted yet so I
Alex, sounds good.
Sam, I agree that in general it would also be useful to have a sensor
that polls just once (or polls repeatedly until successful, such as the
first non-zero exit code).
Another thing that would be useful (in variants of this situation) is a
Hi all,
I'd like us to make a few enhancements to the YAML DSL support. These
are mostly motivated by trying to write some more complicated YAML test
case examples.
_*$brooklyn:entity() to support nested DSLs*_
See [1], and the PR at [2].
For example, being able to write:
Hi all,
TL;DR: I'd like to change the defaults for an app so that it is "down"
and "on-fire" if any of its children are failed.
_*Current Situation*_
Currently in Brooklyn, it is surprising what values are set for an app's
"service.isUp" and its "service.state" sensors:
* If any of the app's
child/member by index")?
Aled
On 08/11/2016 17:51, Aled Sage wrote:
Hi all,
I'd like us to make a few enhancements to the YAML DSL support. These
are mostly motivated by trying to write some more complicated YAML
test case examples.
_*$brooklyn:entity() to support nested DSLs*_
See [1],
Hi Mike,
Off the top of my head, I'd expect it to be:
```
name: Server (Brooklyn Example)
location:
aws-ec2-us-east-1:
imageId: us-east-1/ami-6224a40a
services:
- type: server
name: My VM
```
Alternatively (less good), you could rely on inheriting the
"provisioning.properties" in the
-6224a40a # 6 spaces indent
brooklyn.children: # 2 spaces indent
- type: server # 2 spaces indent
name: vm1 # 4 spaces indent
- type: server # 2 spaces indent
name: vm2 # 4 spaces indent
```
On 21/10/2016 00:42, Aled Sage wrote:
Hi Mike,
Off the top of my head, I'd expect
ptive for users!
--a
On 23/11/2016 10:09, Aled Sage wrote:
// The @SetFromFlag is an implementation detail - this proposal is
just to discuss whether we should have aliases.
As Alex says, the main problem being solved is that having multiple
names makes things confusing (even if we were to
Hi all,
TL;DR: deprecate `@SetFromFlag`; instead explicitly set deprecatedAlias
(and/or alias?) on the ConfigKey.
We should change this *after* releasing 0.10.0, to decrease risk.
_*Current Situation*_
When writing a Java entity, one can declare a config key type as a
static field. One can
tching the
recommended distribution to the Karaf based one.
Svet.
On 16.11.2016 г., at 13:22, Aled Sage <aled.s...@gmail.com> wrote:
Hi all,
It's far past time that we did a Brooklyn 0.10.0 release! I suggest we
aim for that soon.
To that end, I suggest the following steps:
* Deal with o
Hi all,
It's far past time that we did a Brooklyn 0.10.0 release! I suggest we
aim for that soon.
To that end, I suggest the following steps:
* Deal with open PRs:
o People shout out about any PRs you think are very important to
be merged, before that release.
o Review open
yn-server/pull/415 <
https://github.com/apache/brooklyn-server/pull/415> and
https://github.com/apache/brooklyn-server/pull/409 <
https://github.com/apache/brooklyn-server/pull/409>.
Svet.
On 16.11.2016 г., at 13:22, Aled Sage <aled.s...@gmail.com> wrote:
Hi all,
It's far past t
Hi all,
FYI It seems that the github mirror for brooklyn-server is not
synchronizing (i.e. commits in
https://git-wip-us.apache.org/repos/asf?p=brooklyn-server.git;a=summary
are not showing up in https://github.com/apache/brooklyn-server/commits).
I've raised this with the Apache
/11/2016 16:48, Aled Sage wrote:
Hi all,
FYI It seems that the github mirror for brooklyn-server is not
synchronizing (i.e. commits in
https://git-wip-us.apache.org/repos/asf?p=brooklyn-server.git;a=summary
are not showing up in https://github.com/apache/brooklyn-server/commits).
I've raised
briefly but is less relevant as
we
push pure-YAML blueprints. Deprecating the feature will be a relatively
simple, unintrusive change that will make the codebase easier to reason
with.
Sam
On 23/11/2016 11:44, Aled Sage wrote:
Responding to some more of Alex's comments that he made in the renamed
mFlag annotation is an
abstraction that might have made sense briefly but is less relevant as we
push pure-YAML blueprints. Deprecating the feature will be a relatively
simple, unintrusive change that will make the codebase easier to reason
with.
Sam
On 23/11/2016 11:44, Aled Sage wrote:
Responding to som
-1 (binding)
This is because the NOTICE file is missing at the top level of the karaf
distro. In [1], it says "The NOTICE file must included within the
distributed next to the LICENSE file."
I interpret that "must" as meaning we need to produce a new release
candidate, so that the NOTICE
+1 (binding)
I used the verify_brooklyn_rc.sh script to validate the checksums etc.
Confirmed that NOTICE is now included in apache-brooklyn-0.10.0-karaf.
Deployed apps to AWS, GCE and Softlayer, including a windows-based app
to AWS. All worked great!
Aled
On 14/12/2016 12:30, Geoff
Hi all,
Great discussion - really like the direction this is going of using
tasks in yaml blueprints.
However, it feels like we've launched into discussing a complex use-case
(concurrency control) without having first discussed what yaml
blueprints would look like for simpler tasks (*). I
dSecurityProvider.java#L55
On 20.12.2016 г., at 16:48, Aled Sage <aled.s...@gmail.com> wrote:
Alex, all,
I've created https://issues.apache.org/jira/browse/BROOKLYN-417 to
track this - and have included details from my initial investigation.
I'm in two minds about whether it block
tall, and specific
hardening steps need to be followed before running the software on a
server.
I think authentication needs a bigger discussion post 0.10.0 - I have
several valid use cases from customers that Brooklyn does not currently
support.
Thanks
Richard.
On 21 December 2016 at 10:59, Aled Sage &l
com/apache/brooklyn-dist/blob/0.10.0/vagrant/src/main/vagrant/files/brooklyn.properties#L21
On 21/12/2016 14:08, Aled Sage wrote:
Thanks all - please review
https://github.com/apache/brooklyn-server/pull/499 for this change.
---
I still need to look at the vagrant configuration (str
+1 (binding)
I downloaded the tar.gz, and ran it on OS X. I deployed TomcatServer to
AWS, Softlayer, Openstack (bluebox-london) and Google Compute Engine.
I ran the verify_brooklyn_rc.sh script (see attachment in rc1 vote).
I relied on the rat check when running `mvn clean install` for
sses tests.
[✓] LICENSE is present and correct.
[✓] NOTICE is present and correct, including copyright date.
[✓] All files have license headers where appropriate.
[✓] All dependencies have compatible licenses.
[✓] No compiled archives bundled in source archive.
[-] I follow this project’s commits lis
): will you be available to build RC4?
Aled
[1] https://github.com/apache/brooklyn-server/pull/499
[2] https://github.com/apache/brooklyn-server/commits/0.10.0
On 21/12/2016 14:41, Aled Sage wrote:
+1 to Mike's comment in [CANCEL][VOTE] thread: we can leave vagrant
as-is because it explicitly
/brooklyn-docs/pulls
On 21/12/2016 16:47, Svetoslav Neykov wrote:
Thanks for the taking care of the PR Aled. I'll kick off another build.
Svet.
On 21.12.2016 г., at 18:46, Aled Sage <aled.s...@gmail.com> wrote:
Hi all,
The PR [1] is merged, and cherry-picked into the 0.10.0 bra
Hi all,
+1
(D) sounds good. What version are you imagining the bundle would be, if
one runs `br catalog add ~/my/project/ --name com.example.myproject`?
---
I like the idea of uploading a plain zip (rather than only supporting
OSGi bundles) - that makes it simpler for non-java folk. The use
+1 (binding)
I installed (via classic tgz) on OS X (java 7) and on CentOS 7 (java 8).
I confirmed that the default (on both localhost and on the remote VM) is
for no username/password required.
I also confirmed that adding security config to
~/.brooklyn/brooklyn.properties, and starting
ies in the application.
I tried the following on the entity, but it just hangs:
brooklyn.config:
cm_cluster_first_host:
$Brooklyn:entity("cm_cluster").attributeWhenReady("cluster_first_host")
So, what is the "correct" way?
Thanks
Graham
From
e
we are, the more confusing it is, and the harder to get right. If
we're
going to add this capability let's just have one way to do it; if you
are
going to do a ZIP upload, you MUST have a catalog.bom, which MUST
contain a
manifest section, which MUST have both a symbolic name and a version
Hi all,
I'm writing a UsageListener [1] that is going to record the Brooklyn
instance's apps in an external inventory. This is mostly
straight-forward (except needing the fix at [2]).
The tricky bit is when a Brooklyn standby instance is promoted to master
- I want my listener to be
quot;cluster_first_host")
enricher.targetValue:
$brooklyn:entity($brooklyn:attributeWhenReady("cluster.first.entity")).attributeWhenReady("host.name")
Graham
From: Aled Sage <aled.s...@gmail.com>
To: dev@brooklyn.apache.org
Date: 03/23/2017
Hi Graham, Mike, all,
Graham: for why your transformer isn't populating the sensor value, see
the explanation I've written up at
https://issues.apache.org/jira/browse/BROOKLYN-458.
For a workaround, see my first comment on that jira issue:
+1; let's support arbitrary objects.
As for DSL, it does work if your very careful which DSL expressions to
use (e.g. see [1]).
Things like `$brooklyn:external` etc may well be useful, but that's
tricky: we've said elsewhere that we will not store the resolved value
of such a DSL
?
Valentin.
На 31/03/17 в 14:50, Aled Sage написа:
+1; let's support arbitrary objects.
As for DSL, it does work if your very careful which DSL expressions
to use (e.g. see [1]).
Things like `$brooklyn:external` etc may well be useful, but that's
tricky: we've said elsewhere that we
Hi all,
It's time we did another Brooklyn release: 0.11.0. I propose we kick off
RC1 tomorrow. Any volunteers for being release manager?
I also suggest we be conservative about the PRs we merge before then -
let's not view that as a deadline for merging large / high-risk PRs, but
instead
Hi,
For your localhost failure, the brooklyn output shows "Cannot establish
ssh connection to ... 127.0.0.1:22".
You said earlier that you were running on Windows 7. Therefore deploying
to localhost will not work with this blueprint, as it does not support
windows.
You could instead try
Hi,
For the trystack deployment, your pastebin shows an exception while
jclouds is trying to destroy the node (presumably because of an earlier
error). It expects the VM's id to be in the format "regionId/id". It got
this id by calling the OpenStack api's Get_Server_Details.
Unfortunately
Thanks Mark,
I agreed that's a blocker.
I'm also working on a fix for
https://issues.apache.org/jira/browse/BROOKLYN-474, which I think will
be worth including given we'll be producing another RC soon.
Aled
On 13/04/2017 15:16, Mark McKenna wrote:
Hi all
0.11.0 RC1 Fails to rebind to old
ruary 2017 at 13:08, Aled Sage <aled.s...@gmail.com> wrote:
Hi all,
I propose we switch to Java 8 for Apache Brooklyn (i.e. require Java 8;
remove support for using Java 7 when running Brooklyn).
This will make our testing simpler, improving coverage (e.g. we don't
currently test ev
Hi all,
I propose we deprecate and then remove the remaining groovy code from
Brooklyn: deprecate for 0.11.0, and delete a couple of releases later.
I think we should treat Groovy like any other JVM-based language that
users might want to use: it's the user's responsibility; we present a
I'd also like us to include:
https://github.com/apache/brooklyn-server/pull/639
which fixes:
https://issues.apache.org/jira/browse/BROOKLYN-475
Aled
On 18/04/2017 09:54, Graeme Miller wrote:
Hi Richard,
Duncan Grant, should this PR be merged in as it fixes node.js requirements:
Hi Taylor,
Glad to hear you have a workaround.
I'm surprised that snapshotting while the service is running would cause
a problem, from the Brooklyn perspective. When persisting to the
filesystem, we are careful to ensure files are always in a valid state
(e.g. write a tmp file and then do
Hi,
Taking a step back to justify why this kind of thing is really important...
This has come up because we want to call Brooklyn in a robust way from
another system, and to handle a whole load of failure scenarios (e.g.
that Brooklyn is temporarily down, connection fails at some point during
/55eb11fa91e9091447d56bb45116ccc3dc6009df
On 07/07/2017 18:28, Aled Sage wrote:
Hi,
Taking a step back to justify why this kind of thing is really
important...
This has come up because we want to call Brooklyn in a robust way from
another system, and to handle a whole load of failure
fig key or reusing `camp.id`? We already use
the latter one if there is a user-specified ID on an entity so it feels
natural to use it, give it special meaning for apps (blocking repeat
deployments), and add support for searching for it. (Apologies if this was
explained and I missed it.)
--A
On 26 July 201
1 - 100 of 660 matches
Mail list logo