+1 from me
Tested apache-brooklyn-1.0.0-rc3-bin.tar.gz on macOs running Catalina 10.15.3.
Successfully deployed all blueprints in the quick launch on AWS eu-west-1.
Successfully started unpacked and started
apache-brooklyn-1.0.0-rc3-vagrant.zip. All nodes were correctly created.
Iuliana
+1 from me
Tested apache-brooklyn-1.0.0-rc3-bin.zip on macOS running Mohave 10.14.6
Successfully deployed sample 1 server template successfully on AWS us-east-1
Successfully deployed sample 4 resilient bash web cluster template on AWS
us-east-1
John Campbell
Software Engineer
Cloudsoft |
: Richard Downer
Date: Mon, 3 Feb 2020 at 20:11
Subject: [VOTE] Release Apache Brooklyn 1.0.0 [rc2]
To: Brooklyn dev
I'm very happy to announce the first public release candidate for Apache
Brooklyn 1.0.0. This is rc2 (as rc1 had an error which meant it could not
be published fully). I'd like
My vote is:
-1 (binding)
I discovered a defect in the blueprint composer - it's not able to browse
locations[1].
Furthermore, some defects reported by other people I believe are serious
enough to vote -1 for:
Defect in the Vagrant build and some of the quickstart blueprints, reported
Iuliana
Hi All,
[x] -1 Do not release this package because...
I'm afraid my testing has turned up a couple of issues:
* Attempts to use an invalid default `hardwareId` in AWS London Region.
When deploying to the AWS London region, if the blueprint doesn't specify a
`hardwareId`, Brooklyn will choose
Good catch Iuliana.
I agree with Alex, it would be better to fix these.
On Thu, 6 Feb 2020, 14:56 Alex Heneveld, wrote:
> Good find. I agree this sounds like a blocker. (Easy to fix fortunately!
> IMT guessing log message format changed with the karaf bump? We should grep
> on the Brooklyn
Good find. I agree this sounds like a blocker. (Easy to fix fortunately!
IMT guessing log message format changed with the karaf bump? We should grep
on the Brooklyn started message instead of a karaf message!)
Best
Alex
On Thu, 6 Feb 2020, 14:26 Iuliana Cosmina, <
-1
Here is a summary of my tests.
———
[X] Tested the apache-brooklyn-1.0.0-rc2-vagrant.zip &
apache-brooklyn-1.0.0-rc2-vagrant.tar.gz
The condition to check that Brooklyn is up is wrong. This means that when
calling vagrant up, the Brooklyn node is created, but the command never ends,
and
Solid +1
I tested the artifacts with the `verify_brooklyn_rc.sh` script and here is
the output:
--
Checks successfully completed:
[✓] Download links work.
[✓] Checksums and PGP signatures are valid.
[✓] Expanded source archive matches contents of RC tag.
[✓] Expanded source archive builds
+1
I haven't been able to take the time to do extensive validation on the RC,
but I have been able to validate checksums, install and run it, deploy a
basic application, create an app with the UI. Happy to defer to others if
more comprehensive tests reveal problems.
Excited to see this!
Geoff
I'm very happy to announce the first public release candidate for Apache
Brooklyn 1.0.0. This is rc2 (as rc1 had an error which meant it could not
be published fully). I'd like to thank all our contributors who have worked
hard to bring us to this release.
**This is to call for a vote for the
11 matches
Mail list logo
