Re: [VOTE] Release Apache Brooklyn 0.9.0 [rc3]
I addressed the issue with the RPM install: https://github.com/apache/brooklyn-dist/pull/32 (Thanks Svet for pointing it out) Best Regards, Aleksandr Vasilev DevOps Engineer | Cloudsoft Corporation On 7 April 2016 at 15:16, Thomas Bouronwrote: > I created a PR for this: https://github.com/apache/brooklyn-ui/pull/25 > > On Thu, 7 Apr 2016 at 12:55 Thomas Bouron > > wrote: > > > Found the issue: > > > https://github.com/apache/brooklyn-ui/blob/c31ec2c962b925c907d513a62dd095acacb9cea0/src/main/webapp/assets/js/libs/jquery.easy-autocomplete.js#L352-L360 > > > > The jquery.easy-autocomplete.js library creates a new `contains` method > > within the `Array.prototype`. While this usually work for objects, it > > doesn't for arrays as this `contains` methods becomes a key of every > array > > defined afterward. Meaning: > > > > Array.prototype.contains = function() {}; > > // somewhere deep in other javascript code...var a = [1,2,3,4,5];for (x > in a) { > > // Now contains is a part of EVERY array and > > // will show up here as a key of 'a'} > > > > A quick workaround would be to add: > > > > delete Array.prototype.contains; > > > > when the location wizard view is destroyed. I tested it and it worked. > > Unfortunately, it means that any views using the library onward will need > > to do the same. So for the future, we need to swap it for another one. > > > > Are you happy to go with the workaround? > > > > Best. > > > > On Thu, 7 Apr 2016 at 12:38 John McCabe wrote: > > > >> @andrea you need to bump your go to 1.6 and retry. > >> > >> I have: > >> - spun up the vagrant box (had to inject the rc3 download url as its not > >> on > >> the mirrors) without observing any issues > >> - checked port forwarding looks ok - binds to http://localhost:8081 on > >> the > >> host > >> - checked byon location catalog loads without issue > >> - checked display name for inherited locations looks ok > >> - deployed tomcat app to byon location > >> - confirm issue observed by @neykov, and also refresh as suggested by > >> @tbouron > >> - raised BROOKLYN-250, noticed that when adding locations to the catalog > >> (yaml or wizard), the displayName isn't being used in dropdowns or on > the > >> catalog page (it uses name if present and falls back to id) > >> > >> On Thu, 7 Apr 2016 at 11:48 Andrea Turli < > andrea.tu...@cloudsoftcorp.com> > >> wrote: > >> > >> > Hi, > >> > > >> > Borrowing some ideas from Apache jclouds community [1] I'd like to > >> propose > >> > to use the same workflow: > >> > > >> > Validating an Apache Brooklyn release involves verifying the > following: > >> > > >> > - Verify that the checksums are valid. > >> > - Verify that the PGP signatures are valid. > >> > - Check that the expanded source archive matches contents of RC tag. > >> > - Verify that the expanded source archive builds and passes tests. > >> > - Check that LICENSE and NOTICE files are present and correct. > >> > - Make sure all files have license headers where appropriate. > >> > - Check that all dependencies have compatible licenses. > >> > - Verify that no compiled archives bundled in source archive. > >> > > >> > Some steps require a manual verification, and others are fully > >> automated. > >> > The following scripts can be used: > >> > > >> > - Verify RAT, build, tests, checksums and signatures in one script > >> > > >> > Download the verification script: > >> > > >> > Unix: see the attachment > >> > If we accept the script we can then upload it to > >> > https://dist.apache.org/repos/dist/dev/brooklyn/verify_jclouds_rc.sh > >> > > >> > Run it and watch for failures: > >> > > >> > Unix: > >> > chmod +x verify_brooklyn_rc.sh > >> > ./verify_brooklyn_rc.sh 0.9.0-rc3 > >> > > >> > Notice if you're running this on a Mac, you'll need brew and to do a > >> brew > >> > install gpg first. > >> > > >> > By the way running the script I've got > >> > > >> > [INFO] > >> > [INFO] > >> > > > >> > [INFO] Building Brooklyn Client Command Line Interface 0.9.0 > >> > [INFO] > >> > > > >> > [INFO] > >> > [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ > >> > brooklyn-client-cli --- > >> > [INFO] Deleting > >> > > >> > /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client > >> > (includes = [brooklyn*.log, brooklyn*.log.*, stacktrace.log, > >> test-output, > >> > prodDb.*], excludes = []) > >> > [INFO] > >> > [INFO] --- maven-replacer-plugin:1.4.1:replace > >> > (fix-eclipse-dot-classpath-mangling) @ brooklyn-client-cli --- > >> > [INFO] Ignoring missing file > >> > [INFO] Replacement run on 0 file. > >> > [INFO] > >> > [INFO] --- buildnumber-maven-plugin:1.3:create (default) @ > >> > brooklyn-client-cli --- > >> > [INFO] Executing: /bin/sh -c cd > >> > > >> >
Re: [VOTE] Release Apache Brooklyn 0.9.0 [rc3]
I created a PR for this: https://github.com/apache/brooklyn-ui/pull/25 On Thu, 7 Apr 2016 at 12:55 Thomas Bouronwrote: > Found the issue: > https://github.com/apache/brooklyn-ui/blob/c31ec2c962b925c907d513a62dd095acacb9cea0/src/main/webapp/assets/js/libs/jquery.easy-autocomplete.js#L352-L360 > > The jquery.easy-autocomplete.js library creates a new `contains` method > within the `Array.prototype`. While this usually work for objects, it > doesn't for arrays as this `contains` methods becomes a key of every array > defined afterward. Meaning: > > Array.prototype.contains = function() {}; > // somewhere deep in other javascript code...var a = [1,2,3,4,5];for (x in a) > { > // Now contains is a part of EVERY array and > // will show up here as a key of 'a'} > > A quick workaround would be to add: > > delete Array.prototype.contains; > > when the location wizard view is destroyed. I tested it and it worked. > Unfortunately, it means that any views using the library onward will need > to do the same. So for the future, we need to swap it for another one. > > Are you happy to go with the workaround? > > Best. > > On Thu, 7 Apr 2016 at 12:38 John McCabe wrote: > >> @andrea you need to bump your go to 1.6 and retry. >> >> I have: >> - spun up the vagrant box (had to inject the rc3 download url as its not >> on >> the mirrors) without observing any issues >> - checked port forwarding looks ok - binds to http://localhost:8081 on >> the >> host >> - checked byon location catalog loads without issue >> - checked display name for inherited locations looks ok >> - deployed tomcat app to byon location >> - confirm issue observed by @neykov, and also refresh as suggested by >> @tbouron >> - raised BROOKLYN-250, noticed that when adding locations to the catalog >> (yaml or wizard), the displayName isn't being used in dropdowns or on the >> catalog page (it uses name if present and falls back to id) >> >> On Thu, 7 Apr 2016 at 11:48 Andrea Turli >> wrote: >> >> > Hi, >> > >> > Borrowing some ideas from Apache jclouds community [1] I'd like to >> propose >> > to use the same workflow: >> > >> > Validating an Apache Brooklyn release involves verifying the following: >> > >> > - Verify that the checksums are valid. >> > - Verify that the PGP signatures are valid. >> > - Check that the expanded source archive matches contents of RC tag. >> > - Verify that the expanded source archive builds and passes tests. >> > - Check that LICENSE and NOTICE files are present and correct. >> > - Make sure all files have license headers where appropriate. >> > - Check that all dependencies have compatible licenses. >> > - Verify that no compiled archives bundled in source archive. >> > >> > Some steps require a manual verification, and others are fully >> automated. >> > The following scripts can be used: >> > >> > - Verify RAT, build, tests, checksums and signatures in one script >> > >> > Download the verification script: >> > >> > Unix: see the attachment >> > If we accept the script we can then upload it to >> > https://dist.apache.org/repos/dist/dev/brooklyn/verify_jclouds_rc.sh >> > >> > Run it and watch for failures: >> > >> > Unix: >> > chmod +x verify_brooklyn_rc.sh >> > ./verify_brooklyn_rc.sh 0.9.0-rc3 >> > >> > Notice if you're running this on a Mac, you'll need brew and to do a >> brew >> > install gpg first. >> > >> > By the way running the script I've got >> > >> > [INFO] >> > [INFO] >> > >> > [INFO] Building Brooklyn Client Command Line Interface 0.9.0 >> > [INFO] >> > >> > [INFO] >> > [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ >> > brooklyn-client-cli --- >> > [INFO] Deleting >> > >> /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client >> > (includes = [brooklyn*.log, brooklyn*.log.*, stacktrace.log, >> test-output, >> > prodDb.*], excludes = []) >> > [INFO] >> > [INFO] --- maven-replacer-plugin:1.4.1:replace >> > (fix-eclipse-dot-classpath-mangling) @ brooklyn-client-cli --- >> > [INFO] Ignoring missing file >> > [INFO] Replacement run on 0 file. >> > [INFO] >> > [INFO] --- buildnumber-maven-plugin:1.3:create (default) @ >> > brooklyn-client-cli --- >> > [INFO] Executing: /bin/sh -c cd >> > >> /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client >> > && git rev-parse --verify HEAD >> > [INFO] Working directory: >> > >> /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client >> > [INFO] Storing buildNumber: null at timestamp: 1460025523877 >> > [WARNING] Cannot get the branch information from the git repository: >> > Detecting the current branch failed: fatal: Not a git repository (or any >> > of the parent directories): .git >> > >> > [INFO] Executing: /bin/sh -c cd >> > >>
Re: [VOTE] Release Apache Brooklyn 0.9.0 [rc3]
Found the issue: https://github.com/apache/brooklyn-ui/blob/c31ec2c962b925c907d513a62dd095acacb9cea0/src/main/webapp/assets/js/libs/jquery.easy-autocomplete.js#L352-L360 The jquery.easy-autocomplete.js library creates a new `contains` method within the `Array.prototype`. While this usually work for objects, it doesn't for arrays as this `contains` methods becomes a key of every array defined afterward. Meaning: Array.prototype.contains = function() {}; // somewhere deep in other javascript code...var a = [1,2,3,4,5];for (x in a) { // Now contains is a part of EVERY array and // will show up here as a key of 'a'} A quick workaround would be to add: delete Array.prototype.contains; when the location wizard view is destroyed. I tested it and it worked. Unfortunately, it means that any views using the library onward will need to do the same. So for the future, we need to swap it for another one. Are you happy to go with the workaround? Best. On Thu, 7 Apr 2016 at 12:38 John McCabewrote: > @andrea you need to bump your go to 1.6 and retry. > > I have: > - spun up the vagrant box (had to inject the rc3 download url as its not on > the mirrors) without observing any issues > - checked port forwarding looks ok - binds to http://localhost:8081 on the > host > - checked byon location catalog loads without issue > - checked display name for inherited locations looks ok > - deployed tomcat app to byon location > - confirm issue observed by @neykov, and also refresh as suggested by > @tbouron > - raised BROOKLYN-250, noticed that when adding locations to the catalog > (yaml or wizard), the displayName isn't being used in dropdowns or on the > catalog page (it uses name if present and falls back to id) > > On Thu, 7 Apr 2016 at 11:48 Andrea Turli > wrote: > > > Hi, > > > > Borrowing some ideas from Apache jclouds community [1] I'd like to > propose > > to use the same workflow: > > > > Validating an Apache Brooklyn release involves verifying the following: > > > > - Verify that the checksums are valid. > > - Verify that the PGP signatures are valid. > > - Check that the expanded source archive matches contents of RC tag. > > - Verify that the expanded source archive builds and passes tests. > > - Check that LICENSE and NOTICE files are present and correct. > > - Make sure all files have license headers where appropriate. > > - Check that all dependencies have compatible licenses. > > - Verify that no compiled archives bundled in source archive. > > > > Some steps require a manual verification, and others are fully automated. > > The following scripts can be used: > > > > - Verify RAT, build, tests, checksums and signatures in one script > > > > Download the verification script: > > > > Unix: see the attachment > > If we accept the script we can then upload it to > > https://dist.apache.org/repos/dist/dev/brooklyn/verify_jclouds_rc.sh > > > > Run it and watch for failures: > > > > Unix: > > chmod +x verify_brooklyn_rc.sh > > ./verify_brooklyn_rc.sh 0.9.0-rc3 > > > > Notice if you're running this on a Mac, you'll need brew and to do a brew > > install gpg first. > > > > By the way running the script I've got > > > > [INFO] > > [INFO] > > > > [INFO] Building Brooklyn Client Command Line Interface 0.9.0 > > [INFO] > > > > [INFO] > > [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ > > brooklyn-client-cli --- > > [INFO] Deleting > > > /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client > > (includes = [brooklyn*.log, brooklyn*.log.*, stacktrace.log, test-output, > > prodDb.*], excludes = []) > > [INFO] > > [INFO] --- maven-replacer-plugin:1.4.1:replace > > (fix-eclipse-dot-classpath-mangling) @ brooklyn-client-cli --- > > [INFO] Ignoring missing file > > [INFO] Replacement run on 0 file. > > [INFO] > > [INFO] --- buildnumber-maven-plugin:1.3:create (default) @ > > brooklyn-client-cli --- > > [INFO] Executing: /bin/sh -c cd > > > /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client > > && git rev-parse --verify HEAD > > [INFO] Working directory: > > > /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client > > [INFO] Storing buildNumber: null at timestamp: 1460025523877 > > [WARNING] Cannot get the branch information from the git repository: > > Detecting the current branch failed: fatal: Not a git repository (or any > > of the parent directories): .git > > > > [INFO] Executing: /bin/sh -c cd > > > /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client > > && git rev-parse --verify HEAD > > [INFO] Working directory: > > > /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client > > [INFO] Storing buildScmBranch: UNKNOWN_BRANCH > > [INFO] > > [INFO] ---
Re: [VOTE] Release Apache Brooklyn 0.9.0 [rc3]
@andrea you need to bump your go to 1.6 and retry. I have: - spun up the vagrant box (had to inject the rc3 download url as its not on the mirrors) without observing any issues - checked port forwarding looks ok - binds to http://localhost:8081 on the host - checked byon location catalog loads without issue - checked display name for inherited locations looks ok - deployed tomcat app to byon location - confirm issue observed by @neykov, and also refresh as suggested by @tbouron - raised BROOKLYN-250, noticed that when adding locations to the catalog (yaml or wizard), the displayName isn't being used in dropdowns or on the catalog page (it uses name if present and falls back to id) On Thu, 7 Apr 2016 at 11:48 Andrea Turliwrote: > Hi, > > Borrowing some ideas from Apache jclouds community [1] I'd like to propose > to use the same workflow: > > Validating an Apache Brooklyn release involves verifying the following: > > - Verify that the checksums are valid. > - Verify that the PGP signatures are valid. > - Check that the expanded source archive matches contents of RC tag. > - Verify that the expanded source archive builds and passes tests. > - Check that LICENSE and NOTICE files are present and correct. > - Make sure all files have license headers where appropriate. > - Check that all dependencies have compatible licenses. > - Verify that no compiled archives bundled in source archive. > > Some steps require a manual verification, and others are fully automated. > The following scripts can be used: > > - Verify RAT, build, tests, checksums and signatures in one script > > Download the verification script: > > Unix: see the attachment > If we accept the script we can then upload it to > https://dist.apache.org/repos/dist/dev/brooklyn/verify_jclouds_rc.sh > > Run it and watch for failures: > > Unix: > chmod +x verify_brooklyn_rc.sh > ./verify_brooklyn_rc.sh 0.9.0-rc3 > > Notice if you're running this on a Mac, you'll need brew and to do a brew > install gpg first. > > By the way running the script I've got > > [INFO] > [INFO] > > [INFO] Building Brooklyn Client Command Line Interface 0.9.0 > [INFO] > > [INFO] > [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ > brooklyn-client-cli --- > [INFO] Deleting > /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client > (includes = [brooklyn*.log, brooklyn*.log.*, stacktrace.log, test-output, > prodDb.*], excludes = []) > [INFO] > [INFO] --- maven-replacer-plugin:1.4.1:replace > (fix-eclipse-dot-classpath-mangling) @ brooklyn-client-cli --- > [INFO] Ignoring missing file > [INFO] Replacement run on 0 file. > [INFO] > [INFO] --- buildnumber-maven-plugin:1.3:create (default) @ > brooklyn-client-cli --- > [INFO] Executing: /bin/sh -c cd > /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client > && git rev-parse --verify HEAD > [INFO] Working directory: > /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client > [INFO] Storing buildNumber: null at timestamp: 1460025523877 > [WARNING] Cannot get the branch information from the git repository: > Detecting the current branch failed: fatal: Not a git repository (or any > of the parent directories): .git > > [INFO] Executing: /bin/sh -c cd > /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client > && git rev-parse --verify HEAD > [INFO] Working directory: > /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client > [INFO] Storing buildScmBranch: UNKNOWN_BRANCH > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (brooklyn-build-req) @ > brooklyn-client-cli --- > [INFO] > [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ > brooklyn-client-cli --- > [INFO] > [INFO] --- maven-antrun-plugin:1.8:run (process-build-all) @ > brooklyn-client-cli --- > [INFO] Executing tasks > > main: > > all: > [exec] Starting build.sh (brooklyn-client go build script) > [exec] > [exec] ERROR: Incompatible Go language version: go1.5.2 > [exec] > [exec] Go version 1.6 or higher is required to build the > brooklyn-client CLI. > [exec] See golang.org for more information, or run maven with > '-Dno-go-client' to skip. > [exec] > [INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] Brooklyn REST JavaScript Web GUI ... SUCCESS [ > 18.747 s] > [INFO] Brooklyn Server Root ... SUCCESS [ > 0.188 s] > [INFO] Brooklyn Parent Project SUCCESS [ > 2.226 s] > [INFO] Brooklyn Test Support Utilities SUCCESS [ > 4.008 s] > [INFO] Brooklyn Logback Includable Configuration .. SUCCESS [ > 0.861 s] > [INFO] Brooklyn Common
Re: [VOTE] Release Apache Brooklyn 0.9.0 [rc3]
I can reproduce the issue. However, it happens only if you have used previously the location wizard. As soon as you refresh the page, this error is gone. I need to investigate more but it seems to be related to the library jquery.easy-autocomplete.js introduced by the location wizard. I'll let you know. Best. On Thu, 7 Apr 2016 at 11:36 Svetoslav Neykov < svetoslav.ney...@cloudsoftcorp.com> wrote: > -1 > > Found a problem with the UI. Starting a simple app will not show tasks in > the Activity tab and will keep it grayed out, even if having a start task > running. Once started and with the browser refreshed functionality returns > to normal. > Steps to reproduce: > - start with an empty or minimal brooklyn.properties > - go to composer tab > - ui prompts you to create a new location (because none are defined) > - created a localhost location from advanced tab (fill in localhost in all > fields) > - use the location to start a blueprint, here's the one I used > > location: localhost > services: > - type: org.apache.brooklyn.entity.machine.MachineEntity > > The app will go into starting state, but the activity tab doesn't show any > of the tasks. The debugging console contains some errors, see [1]. > > The problem doesn't happen if using localhost as a LocationResolver, only > with the named location just created. > > --- > > Also when installing from rpm I got the following error message (second > line) on centor 7.0. Other than that the instance is running as expected, > working after a restart. > > ... > Инсталиране: apache-brooklyn-0.9.0-1.noarch > > 29/29 > Failed to issue method call: No such file or directory > Проверка : libXext-1.3.3-3.el7.x86_64 > > 1/29 > ... > > > First line says "Installing:", third line "Checking". The error is on the > second line. > > > Svet. > > > > [1] https://paste.apache.org/8pDA > > > > On 7.04.2016 г., at 1:24, Richard Downerwrote: > > > > This is to call for a vote for the release of Apache Brooklyn 0.9.0 > [rc3]. > > > > This release comprises of a source code distribution, and a > > corresponding binary distribution, RPM packages, Vagrant environment > > package, and Maven artifacts. > > > > The source and binary distributions, including signatures, digests, > > etc. can be found at: > > > https://dist.apache.org/repos/dist/dev/brooklyn/apache-brooklyn-0.9.0-rc3 > > > > The artifact SHA-256 checksums are as follows: > > 65e3438c81c76d47f98e637554e4b80c8c869ff482c18ca9b2d838778268a56b > > *apache-brooklyn-0.9.0-rc3-1.noarch.rpm > > 1a1235c10962371f52240f7fcb1c89f1d066cbb55715c493f4fdffc0a6927da0 > > *apache-brooklyn-0.9.0-rc3-bin.tar.gz > > f95a566d5bb086906d8a4657029757b08a90d2483ef00a7eae0ddd55832b0f4c > > *apache-brooklyn-0.9.0-rc3-bin.zip > > bbceefda7444a0235527d9830230acb6a3d9f9c6280f36bccc59486a3ee80db8 > > *apache-brooklyn-0.9.0-rc3-client-cli-linux.tar.gz > > 7a1cabc5d96be11cbd538a202c1712f9bd053be18f37dc533c543004b247a802 > > *apache-brooklyn-0.9.0-rc3-client-cli-linux.zip > > 51ecff55d2c7308efc7f215cc5ab4bdfd8db8d2588fde3346b3c5ad53cf9d396 > > *apache-brooklyn-0.9.0-rc3-client-cli-macosx.tar.gz > > cce8cf9819cb57b1c0bbbdbef76da43fb8142ed2f0a6b9cb613850e2188081d6 > > *apache-brooklyn-0.9.0-rc3-client-cli-macosx.zip > > 6d5f1ca2d9550048c80cdf951f00c780c3766d09960f15a47585c37e44c16926 > > *apache-brooklyn-0.9.0-rc3-client-cli-windows.tar.gz > > d0d021f17efe389558b5d12141694179f3245acd9d016bd9de03917fc6b9fa4c > > *apache-brooklyn-0.9.0-rc3-client-cli-windows.zip > > b993253273280027c45adb4d6899493e8df0301080128d6c8bc10148da3c1a74 > > *apache-brooklyn-0.9.0-rc3-src.tar.gz > > f9e4396ab123b650fe02675e0e753f819c4a5bcbf8ed48fd5fa925a6ba93e149 > > *apache-brooklyn-0.9.0-rc3-src.zip > > 052412c38707152b01117ccf504aa75d742495743b134f2d328dd4725f19ee4e > > *apache-brooklyn-0.9.0-rc3-vagrant.tar.gz > > 4a9cc996b827342c11176257bd1663ecb572913f2d3f3dc1f2d43b54be62aa52 > > *apache-brooklyn-0.9.0-rc3-vagrant.zip > > > > The Nexus staging repositories for the Maven artifacts are located at: > > > https://repository.apache.org/content/repositories/orgapachebrooklyn-1018 > > > https://repository.apache.org/content/repositories/orgapachebrooklyn-1019 > > > > All release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/richard.asc > > > > KEYS file available here: > > https://dist.apache.org/repos/dist/release/brooklyn/KEYS > > > > The artifacts were built from these Git commit IDs: > > brooklyn: acc8ff1930d243d2a5fae1ad2f1a1ef17ca4a19c > > brooklyn-client: bc8593a933fcb76327ae4a511643e39d25a87ba2 > > brooklyn-dist: f08bddf201ab02a4f7066bfa3bcacf01bb430b99 > > brooklyn-docs: 12430d193e1891b87a677d6b45a3b17861c83518 > > brooklyn-library: 2565e6eb2868468ec2528df74fe85efdb887b6d2 > > brooklyn-server: 718aea7d27ce21835860d2de6a31d0e9474bee85 > > brooklyn-ui: 34d196678a8ae37804c698413d4ef19b86719a8f > >
Re: [VOTE] Release Apache Brooklyn 0.9.0 [rc3]
Hi, Borrowing some ideas from Apache jclouds community [1] I'd like to propose to use the same workflow: Validating an Apache Brooklyn release involves verifying the following: - Verify that the checksums are valid. - Verify that the PGP signatures are valid. - Check that the expanded source archive matches contents of RC tag. - Verify that the expanded source archive builds and passes tests. - Check that LICENSE and NOTICE files are present and correct. - Make sure all files have license headers where appropriate. - Check that all dependencies have compatible licenses. - Verify that no compiled archives bundled in source archive. Some steps require a manual verification, and others are fully automated. The following scripts can be used: - Verify RAT, build, tests, checksums and signatures in one script Download the verification script: Unix: see the attachment If we accept the script we can then upload it to https://dist.apache.org/repos/dist/dev/brooklyn/verify_jclouds_rc.sh Run it and watch for failures: Unix: chmod +x verify_brooklyn_rc.sh ./verify_brooklyn_rc.sh 0.9.0-rc3 Notice if you're running this on a Mac, you'll need brew and to do a brew install gpg first. By the way running the script I've got [INFO] [INFO] [INFO] Building Brooklyn Client Command Line Interface 0.9.0 [INFO] [INFO] [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ brooklyn-client-cli --- [INFO] Deleting /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client (includes = [brooklyn*.log, brooklyn*.log.*, stacktrace.log, test-output, prodDb.*], excludes = []) [INFO] [INFO] --- maven-replacer-plugin:1.4.1:replace (fix-eclipse-dot-classpath-mangling) @ brooklyn-client-cli --- [INFO] Ignoring missing file [INFO] Replacement run on 0 file. [INFO] [INFO] --- buildnumber-maven-plugin:1.3:create (default) @ brooklyn-client-cli --- [INFO] Executing: /bin/sh -c cd /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client && git rev-parse --verify HEAD [INFO] Working directory: /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client [INFO] Storing buildNumber: null at timestamp: 1460025523877 [WARNING] Cannot get the branch information from the git repository: Detecting the current branch failed: fatal: Not a git repository (or any of the parent directories): .git [INFO] Executing: /bin/sh -c cd /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client && git rev-parse --verify HEAD [INFO] Working directory: /private/tmp/apache-brooklyn-0.9.0-rc3/apache-brooklyn-0.9.0-src/brooklyn-client [INFO] Storing buildScmBranch: UNKNOWN_BRANCH [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (brooklyn-build-req) @ brooklyn-client-cli --- [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ brooklyn-client-cli --- [INFO] [INFO] --- maven-antrun-plugin:1.8:run (process-build-all) @ brooklyn-client-cli --- [INFO] Executing tasks main: all: [exec] Starting build.sh (brooklyn-client go build script) [exec] [exec] ERROR: Incompatible Go language version: go1.5.2 [exec] [exec] Go version 1.6 or higher is required to build the brooklyn-client CLI. [exec] See golang.org for more information, or run maven with '-Dno-go-client' to skip. [exec] [INFO] [INFO] Reactor Summary: [INFO] [INFO] Brooklyn REST JavaScript Web GUI ... SUCCESS [ 18.747 s] [INFO] Brooklyn Server Root ... SUCCESS [ 0.188 s] [INFO] Brooklyn Parent Project SUCCESS [ 2.226 s] [INFO] Brooklyn Test Support Utilities SUCCESS [ 4.008 s] [INFO] Brooklyn Logback Includable Configuration .. SUCCESS [ 0.861 s] [INFO] Brooklyn Common Utilities .. SUCCESS [ 12.232 s] [INFO] Brooklyn API ... SUCCESS [ 1.555 s] [INFO] CAMP Server Parent Project . SUCCESS [ 0.227 s] [INFO] CAMP Base .. SUCCESS [ 2.305 s] [INFO] Brooklyn Test Support .. SUCCESS [ 1.747 s] [INFO] Brooklyn REST Swagger Apidoc Utilities . SUCCESS [ 6.977 s] [INFO] Brooklyn Logback Configuration . SUCCESS [ 0.392 s] [INFO] CAMP Server SUCCESS [ 4.696 s] [INFO] CAMP Server Jersey . SUCCESS [ 5.072 s] [INFO] Brooklyn Felix Runtime . SUCCESS [ 2.719 s] [INFO] Brooklyn Groovy Utilities .. SUCCESS [ 0.811 s] [INFO] Brooklyn Core .. SUCCESS [02:34 min] [INFO] Brooklyn Policies
Re: [VOTE] Release Apache Brooklyn 0.9.0 [rc3]
-1 Found a problem with the UI. Starting a simple app will not show tasks in the Activity tab and will keep it grayed out, even if having a start task running. Once started and with the browser refreshed functionality returns to normal. Steps to reproduce: - start with an empty or minimal brooklyn.properties - go to composer tab - ui prompts you to create a new location (because none are defined) - created a localhost location from advanced tab (fill in localhost in all fields) - use the location to start a blueprint, here's the one I used location: localhost services: - type: org.apache.brooklyn.entity.machine.MachineEntity The app will go into starting state, but the activity tab doesn't show any of the tasks. The debugging console contains some errors, see [1]. The problem doesn't happen if using localhost as a LocationResolver, only with the named location just created. --- Also when installing from rpm I got the following error message (second line) on centor 7.0. Other than that the instance is running as expected, working after a restart. ... Инсталиране: apache-brooklyn-0.9.0-1.noarch 29/29 Failed to issue method call: No such file or directory Проверка : libXext-1.3.3-3.el7.x86_64 1/29 ... First line says "Installing:", third line "Checking". The error is on the second line. Svet. [1] https://paste.apache.org/8pDA > On 7.04.2016 г., at 1:24, Richard Downerwrote: > > This is to call for a vote for the release of Apache Brooklyn 0.9.0 [rc3]. > > This release comprises of a source code distribution, and a > corresponding binary distribution, RPM packages, Vagrant environment > package, and Maven artifacts. > > The source and binary distributions, including signatures, digests, > etc. can be found at: > https://dist.apache.org/repos/dist/dev/brooklyn/apache-brooklyn-0.9.0-rc3 > > The artifact SHA-256 checksums are as follows: > 65e3438c81c76d47f98e637554e4b80c8c869ff482c18ca9b2d838778268a56b > *apache-brooklyn-0.9.0-rc3-1.noarch.rpm > 1a1235c10962371f52240f7fcb1c89f1d066cbb55715c493f4fdffc0a6927da0 > *apache-brooklyn-0.9.0-rc3-bin.tar.gz > f95a566d5bb086906d8a4657029757b08a90d2483ef00a7eae0ddd55832b0f4c > *apache-brooklyn-0.9.0-rc3-bin.zip > bbceefda7444a0235527d9830230acb6a3d9f9c6280f36bccc59486a3ee80db8 > *apache-brooklyn-0.9.0-rc3-client-cli-linux.tar.gz > 7a1cabc5d96be11cbd538a202c1712f9bd053be18f37dc533c543004b247a802 > *apache-brooklyn-0.9.0-rc3-client-cli-linux.zip > 51ecff55d2c7308efc7f215cc5ab4bdfd8db8d2588fde3346b3c5ad53cf9d396 > *apache-brooklyn-0.9.0-rc3-client-cli-macosx.tar.gz > cce8cf9819cb57b1c0bbbdbef76da43fb8142ed2f0a6b9cb613850e2188081d6 > *apache-brooklyn-0.9.0-rc3-client-cli-macosx.zip > 6d5f1ca2d9550048c80cdf951f00c780c3766d09960f15a47585c37e44c16926 > *apache-brooklyn-0.9.0-rc3-client-cli-windows.tar.gz > d0d021f17efe389558b5d12141694179f3245acd9d016bd9de03917fc6b9fa4c > *apache-brooklyn-0.9.0-rc3-client-cli-windows.zip > b993253273280027c45adb4d6899493e8df0301080128d6c8bc10148da3c1a74 > *apache-brooklyn-0.9.0-rc3-src.tar.gz > f9e4396ab123b650fe02675e0e753f819c4a5bcbf8ed48fd5fa925a6ba93e149 > *apache-brooklyn-0.9.0-rc3-src.zip > 052412c38707152b01117ccf504aa75d742495743b134f2d328dd4725f19ee4e > *apache-brooklyn-0.9.0-rc3-vagrant.tar.gz > 4a9cc996b827342c11176257bd1663ecb572913f2d3f3dc1f2d43b54be62aa52 > *apache-brooklyn-0.9.0-rc3-vagrant.zip > > The Nexus staging repositories for the Maven artifacts are located at: > https://repository.apache.org/content/repositories/orgapachebrooklyn-1018 > https://repository.apache.org/content/repositories/orgapachebrooklyn-1019 > > All release artifacts are signed with the following key: > https://people.apache.org/keys/committer/richard.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/brooklyn/KEYS > > The artifacts were built from these Git commit IDs: > brooklyn: acc8ff1930d243d2a5fae1ad2f1a1ef17ca4a19c > brooklyn-client: bc8593a933fcb76327ae4a511643e39d25a87ba2 > brooklyn-dist: f08bddf201ab02a4f7066bfa3bcacf01bb430b99 > brooklyn-docs: 12430d193e1891b87a677d6b45a3b17861c83518 > brooklyn-library: 2565e6eb2868468ec2528df74fe85efdb887b6d2 > brooklyn-server: 718aea7d27ce21835860d2de6a31d0e9474bee85 > brooklyn-ui: 34d196678a8ae37804c698413d4ef19b86719a8f > All of the above have been tagged as "apache-brooklyn-0.9.0-rc3". > > > Please download the artifacts, test, and vote on releasing this > package as Apache Brooklyn 0.9.0. > > The vote will be open for at least 72 hours. > [ ] +1 Release this package as Apache Brooklyn 0.9.0 (please describe > the tests you have performed) > [ ] +0 no opinion > [ ] -1 Do not release this package (please describe
Re: [VOTE] Release Apache Brooklyn 0.9.0 [rc3]
+1 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 + launched Brooklyn from the .tar.gz - Created a new Cloud Location with the location wizard - Edited this newly location with the YAML composer - Deployed a bash web server to this newly location successfully On Wed, 6 Apr 2016 at 23:24 Richard Downerwrote: > This is to call for a vote for the release of Apache Brooklyn 0.9.0 [rc3]. > > This release comprises of a source code distribution, and a > corresponding binary distribution, RPM packages, Vagrant environment > package, and Maven artifacts. > > The source and binary distributions, including signatures, digests, > etc. can be found at: > https://dist.apache.org/repos/dist/dev/brooklyn/apache-brooklyn-0.9.0-rc3 > > The artifact SHA-256 checksums are as follows: > 65e3438c81c76d47f98e637554e4b80c8c869ff482c18ca9b2d838778268a56b > *apache-brooklyn-0.9.0-rc3-1.noarch.rpm > 1a1235c10962371f52240f7fcb1c89f1d066cbb55715c493f4fdffc0a6927da0 > *apache-brooklyn-0.9.0-rc3-bin.tar.gz > f95a566d5bb086906d8a4657029757b08a90d2483ef00a7eae0ddd55832b0f4c > *apache-brooklyn-0.9.0-rc3-bin.zip > bbceefda7444a0235527d9830230acb6a3d9f9c6280f36bccc59486a3ee80db8 > *apache-brooklyn-0.9.0-rc3-client-cli-linux.tar.gz > 7a1cabc5d96be11cbd538a202c1712f9bd053be18f37dc533c543004b247a802 > *apache-brooklyn-0.9.0-rc3-client-cli-linux.zip > 51ecff55d2c7308efc7f215cc5ab4bdfd8db8d2588fde3346b3c5ad53cf9d396 > *apache-brooklyn-0.9.0-rc3-client-cli-macosx.tar.gz > cce8cf9819cb57b1c0bbbdbef76da43fb8142ed2f0a6b9cb613850e2188081d6 > *apache-brooklyn-0.9.0-rc3-client-cli-macosx.zip > 6d5f1ca2d9550048c80cdf951f00c780c3766d09960f15a47585c37e44c16926 > *apache-brooklyn-0.9.0-rc3-client-cli-windows.tar.gz > d0d021f17efe389558b5d12141694179f3245acd9d016bd9de03917fc6b9fa4c > *apache-brooklyn-0.9.0-rc3-client-cli-windows.zip > b993253273280027c45adb4d6899493e8df0301080128d6c8bc10148da3c1a74 > *apache-brooklyn-0.9.0-rc3-src.tar.gz > f9e4396ab123b650fe02675e0e753f819c4a5bcbf8ed48fd5fa925a6ba93e149 > *apache-brooklyn-0.9.0-rc3-src.zip > 052412c38707152b01117ccf504aa75d742495743b134f2d328dd4725f19ee4e > *apache-brooklyn-0.9.0-rc3-vagrant.tar.gz > 4a9cc996b827342c11176257bd1663ecb572913f2d3f3dc1f2d43b54be62aa52 > *apache-brooklyn-0.9.0-rc3-vagrant.zip > > The Nexus staging repositories for the Maven artifacts are located at: > https://repository.apache.org/content/repositories/orgapachebrooklyn-1018 > https://repository.apache.org/content/repositories/orgapachebrooklyn-1019 > > All release artifacts are signed with the following key: > https://people.apache.org/keys/committer/richard.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/brooklyn/KEYS > > The artifacts were built from these Git commit IDs: > brooklyn: acc8ff1930d243d2a5fae1ad2f1a1ef17ca4a19c > brooklyn-client: bc8593a933fcb76327ae4a511643e39d25a87ba2 > brooklyn-dist: f08bddf201ab02a4f7066bfa3bcacf01bb430b99 > brooklyn-docs: 12430d193e1891b87a677d6b45a3b17861c83518 > brooklyn-library: 2565e6eb2868468ec2528df74fe85efdb887b6d2 > brooklyn-server: 718aea7d27ce21835860d2de6a31d0e9474bee85 > brooklyn-ui: 34d196678a8ae37804c698413d4ef19b86719a8f > All of the above have been tagged as "apache-brooklyn-0.9.0-rc3". > > > Please download the artifacts, test, and vote on releasing this > package as Apache Brooklyn 0.9.0. > > The vote will be open for at least 72 hours. > [ ] +1 Release this package as Apache Brooklyn 0.9.0 (please describe > the tests you have performed) > [ ] +0 no opinion > [ ] -1 Do not release this package (please describe why not) > > Thanks > -- Thomas Bouron • Software Engineer @ Cloudsoft Corporation • http://www.cloudsoftcorp.com/ Github: https://github.com/tbouron Twitter: https://twitter.com/eltibouron