brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [4/6] brooklyn git commit: Added What:Brooklyn, removed Versioning, simplified licence, & other small tweaks.
Date Mon, 01 Feb 2016 17:31:19 GMT
Added What:Brooklyn, removed Versioning, simplified licence, & other small tweaks.


Branch: refs/heads/0.6.0
Commit: d7b9c8d4eda2961c3ac847118abc0cf7761e60f1
Parents: 5f6375c
Author: David Toy <>
Authored: Thu Apr 18 14:35:14 2013 +0100
Committer: David Toy <>
Committed: Thu Apr 18 14:35:14 2013 +0100

---------------------------------------------------------------------- | 72 ++++++++++++++++++++++++++++++++++------------------------
 1 file changed, 42 insertions(+), 30 deletions(-)
diff --git a/ b/
index e5691b5..6072351 100644
--- a/
+++ b/
@@ -4,41 +4,62 @@ Brooklyn is a library and control plane for deploying and managing distributed
 See []( for details and examples.
-## Quick Start
+Brooklyn's main emphasis is managing live applications (e.g auto-scaling, exception handling,
auto recovery from failure, and working across multiple clouds). Brooklyn considers deployment
part of management, like the opening move in a game of chess. (Distributed-application-management-chess,
no less).
-Three quick start options are available:
+### Deployment
-* Follow the [getting started guide](
-* [Download the latest release](
-* Clone the repo: `git clone git://`.
+Brooklyn enables single-click deployment of complex applications.
-## Versioning
-For transparency and insight into our release cycle, and for striving to maintain backward
compatibility, Brooklyn will be maintained under the [Semantic Versioning guidelines](
+Brooklyn features:
-Releases will be numbered with the following format:
+* out-of-the-box support for many common software entities.
+* integration with jclouds, allowing deployment to the majority of public and private clouds,
in addition to pools of fixed IP machines.
+* integration with Apache Whirr (and thereby Chef and Puppet), allowing deployment of well-known
services such as Hadoop and elasticsearch (and you can still use POBS, plain-old-bash-scripts).
+* integration with PaaS's such as OpenShift, allowing use of PaaSes alongside self-built
clusters, for maximum flexibility.
+Brooklyn works with and ties into other tools, adding the concepts of manageable clusters
and fabrics.
-And constructed with the following guidelines:
+In DevOps fashion, Brooklyn allows applications and roll-outs to be version controlled, tested
programatically, and reused across locations and contexts. Develop on localhost, then reuse
the same application descriptor to deploy to QA, and then to your production environment.
-* Breaking backward compatibility bumps the major (and resets the minor and patch)
-* New additions without breaking backward compatibility bumps the minor (and resets the patch)
-* Bug fixes and misc changes bumps the patch
+### Management
-Milestones (`<major>.<minor>.<patch>-M<milestone>`) and Release Candidates
(`<major>.<minor>.<patch>-rc.<candidate>`) are used in the release
+Brooklyn enables [autonomic management](
of applications. (i.e. many small, local, distributed control loops).
-## Bug Tracker
+Management policies can be attached to every component part in an application, and to logic
groupings of components (clusters, fabrics). Policies can implement both technical and non-technical
(business) requirements.
-Have a bug or a feature request? [Please open a new issue](
+At runtime, policies have access to all aspects of the deployment, including deployment topology
(hierarchical) and locations (machines, PaaSes, and jurisdictions), as well as scripts, instrumentation,
and operational goals and constraints. This means that once the application is launched, the
policies are all set to keep the application running optimally, based on whatever optimally
means in that context.
+These deployment patterns and management policies are expressed as Java (or Groovy) classes,
open-sourced here and giving you full control over what you want to happen. More importantly,
however, this code can be shared, improved, and extended.
+### Use As a Library
+Import Brooklyn into your application to natively use its distributed management smarts.
e.g. [Cloudera's Certification Cluster Builder Tool](
+### Use As a Control Plane
+Alternatively, use Brooklyn as an integrated-stand-alone management node for your application
or bespoke platform.
+## Quick Start
+Three quick start options are available:
+* The [getting started guide](
will step you through downloading and installing Brooklyn and running the examples.
+* Alternatively, [download the latest release](
+* or, fork or clone the repo: `git clone git://` then
`mvn clean install`.
 ## Community
-Keep track of development and community news.
-* Follow [@brooklyncentral on Twitter](
-* Have a question that's not a feature request or bug report? [Ask on the mailing list.](
+* Have a question that's not a feature request or bug report? Ask on the mailing lists: [brooklyn-users](
or [brooklyn-dev](
 * Chat with us over IRC. On the `` server, in the `#brooklyncentral` channel.
+* Follow [@brooklyncentral on Twitter](
+## Bug Tracker
+Have a bug or a feature request? [Please open a new issue](
 ## Contributing
@@ -53,16 +74,7 @@ Thanks!
 Copyright 2013 Cloudsoft Corporation, ltd.
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this work except in compliance with the License.
-You may obtain a copy of the License in the LICENSE file, or at:
-  [](
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-See the License for the specific language governing permissions and
-limitations under the License.
+Licensed under the Apache License, Version 2.0:
+You may obtain a copy of the License in the LICENSE file, or at: [](
 brooklyn is a registered trademark of Cloudsoft Corporation.

View raw message