Release note for 0.5.0.
Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/07da3879 Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/07da3879 Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/07da3879 Branch: refs/heads/0.5.0 Commit: 07da38791fde9053a3fc7945b25ef0f5b997a3dd Parents: 9b14431 Author: David Toy <[email protected]> Authored: Thu Apr 18 18:13:46 2013 +0100 Committer: David Toy <[email protected]> Committed: Wed May 8 18:29:02 2013 +0100 ---------------------------------------------------------------------- docs/start/release-notes.md | 93 ++++++++++++++++++---------------------- 1 file changed, 41 insertions(+), 52 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/07da3879/docs/start/release-notes.md ---------------------------------------------------------------------- diff --git a/docs/start/release-notes.md b/docs/start/release-notes.md index 7c19f1e..8d7a934 100644 --- a/docs/start/release-notes.md +++ b/docs/start/release-notes.md @@ -4,80 +4,69 @@ title: Release Notes toc: ../toc.json --- -## Brooklyn Version 0.5.0 RC2 (0.5.0-rc.2) +## Brooklyn Version 0.5.0 -* Fix compatibility issue with Java 7 builds -* Fix regression in HttpFeed: if polling same URL for multiple sensors, share the same http request. -* Fix rebind of nginx entity -* Fix redis install (was failing on some platforms) -* Fix doc build problems -* Fix Whirr cluster problems from rc.1 -* Cloud Foundry examples moved to [a separate repo](https://github.com/cloudsoft/brooklyn-cloudfoundry). +This release includes many big features. It incorporates a lot of improvements and feedback from our community. Thank you! -## Brooklyn Version 0.5.0 RC1 (0.5.0-rc.1) +Thanks also go to Brooklyn's commercial users. Already Brooklyn has been adopted into some very exciting projects including controlling custom PaaS offerings, big data clusters, and three-tier web-apps. -* API Tidy on top of M2, using `init()` as the method to override when building composed Application and Entity classes. +New Features +------------ -* There are known issues with Whirr clusters and the Cloud Foundry example (moving) which will be resolved for RC2. +The major changes between 0.4.*x* and 0.5 are: +* "Rebind" suppport: allow Brooklyn to restart and re-binding to the entities in the applications. + The state is automatically persisted as entities change, so Brooklyn can survive unexpected termination + and retarts. -## Brooklyn Version 0.5.0 Milestone Two (0.5.0-M2) +* Entities have been separated into an interface and implementation, rather than just a single class. + Construction of entities is now done using an EntitySpec, rather than directly calling the constructor. + This improvement is required to simplify remoting in a distributed brooklyn management plane. -### Introduction +* Downloading of entity installers is greatly improved: -This milestone release includes many big features, and brings us much closer to a 0.5.0 release. + * More configurable, with ability to specify URLs in the brooklyn configuration files or to override in code. -It incorporates a lot of improvements and feedback from our community. Thank you! + * Will fallback to a repository maintained by Cloudsoft, so if an artifact is removed from the official public site then it will not break the entity. (*See also:* [downloads.cloudsoftcorp.com/brooklyn/repository](http://downloads.cloudsoftcorp.com/brooklyn/repository/)) -Thanks also go to Brooklyn's commercial users. Already Brooklyn has been adopted into some very exciting projects including controlling custom PaaS offerings, big data clusters, and three-tier web-apps. +* Support for running applications across private subnets. + +* Policies can now be re-configured on-the-fly through the REST API and through the web-console. -Work on this release can be tracked using Brooklyn's GitHub issue tracker: - -* [github.com/brooklyncentral/brooklyn/issues?milestone=1](https://github.com/brooklyncentral/brooklyn/issues?milestone=1) +* New `feed` classes for entities to poll for their sensor values. + This replaces the now-deprecated `SensorAdapter` classes. -And via the mailing lists: - -* [[email protected]](http://groups.google.com/group/brooklyn-dev) -* [[email protected]](http://groups.google.com/group/brooklyn-users) - -### New Features +* Some entities now support configuration files being supplied in FreeMarker template format. These include JBoss AS7, ActiveMQ and MySql. More will be converted to use this pattern. -The major changes between M1 and M2 are: +* A CLI-based ssh-tool implementation (Brooklyn can be configured to use that, rather than the default sshj). + This is useful for things like Tectia integration, which does not work with sshj due to key file formats. -1. Entities have been separated into an interface and implementation, rather than just a single class. Construction of entities is now done using an EntitySpec, rather than directly calling the constructor. This improvement is required to simplify remoting in a distributed brooklyn management plane. +* Several new entities have been added, including: -2. Downloading of entity installers is greatly improved: - * More configurable, with ability to specify URLs in the brooklyn configuration files or to override in code. - * Will fallback to a repository maintained by Cloudsoft, so if an artifact is removed from the official public site then it will not break the entity. - - See [downloads.cloudsoftcorp.com/brooklyn/repository/](http://downloads.cloudsoftcorp.com/brooklyn/repository/) + * MongoDB + * Cassandra + * PostgreSQL + * RubyRep + * Kafka + * DynamicWebAppFabric -3. Support for running applications across private subnets. +Backwards Compatibility +--------------------- -4. Policies can now be re-configured on-the-fly through the REST api and through the web-console. +For upgrading from 0.4.*x* to 0.5.0: -5. Some entities now support configuration files being supplied in FreeMarker template format. These include JBoss AS7, ActiveMQ and MySql. More will be converted to use this pattern. +* Entity classes have been renamed, e.g. `MySqlNode` is now an interface and the implementationis `MySqlNodeImpl`. -6. Several new entities have been added, including: - * MongoDB - * Cassandra - * RubyRep - * DynamicWebAppFabric + * The minimum change for this to work is to update your references to include the `-Impl` suffixes. However, that will result in deprecation warnings. + * The recommended approach is to use the EntitySpec when constructing entities. A good place to start is to look at the updated example applications. -### Backwards Compatibility +* The default username for provisioning with jclouds has changed to use the name of the user executing the Brooklyn process. -For upgrading from 0.5.0-M1 to M2: + * Java's `System.getProperty("user.name")` is used instead of 'root' or 'ubuntu' -1. Entity classes have been renamed, e.g. MySqlNode is now an interface and the implementationis MySqlNodeImpl. - * The minimum change for this to work is to update your references to include the Impl suffixes. However, that will result in deprecation warnings. - * The recommended approach is to use the EntitySpec when constructing entities. A good place to start is to look at the updated example applications. + * Usernames can be overridden in brooklyn.properties or using system properties. For example, by entering `brooklyn.location.named.acmecloud.user=root` in brooklyn.properties or using the command syntax `-Dbrooklyn.location.named.acmecloud.user=root`. -2. The default username for provisioning with jclouds has changed to use the name of the user executing the Brooklyn process. - * Java's `System.getProperty("user.name")` is used instead of 'root' or 'ubuntu' - * Usernames can be overridden in `brooklyn.properties` or using system properties. - For example, by entering '`brooklyn.location.named.acmecloud.user=root`' in `brooklyn.properties` or using the command syntax `-Dbrooklyn.location.named.acmecloud.user=root`. - - '`brooklyn.jclouds.aws-ec2.user=root`' could also be used to apply `user=root` to all aws-ec2 VMs. + `brooklyn.jclouds.aws-ec2.user=root` could also be used to apply user=root to all aws-ec2 VMs. -3. Some deprecated code has been deleted. All of this code was commented in 0.4.0 with text such as "will be deleted in 0.5". \ No newline at end of file +* Some deprecated code has been deleted. All of this code was commented in 0.4.0 with text such as "will be deleted in 0.5". Where code has been deprecated in 0.5.0, there are javadoc comments indicating what should be used instead.
