brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [13/13] brooklyn git commit: remove the sandbox/ and release/ dirs from the build
Date Mon, 01 Feb 2016 17:31:42 GMT
remove the sandbox/ and release/ dirs from the build

and update the README in the root

and delete the old in the root.
(it is not maintained; it doesn't even refer to the apache downloads.)

basically make the source build look nice when it's unpacked


Branch: refs/heads/0.8.0-incubating
Commit: 72b6fbeb2b6da8dc8ee720fb61e59baa458d05fd
Parents: 234028b
Author: Alex Heneveld <>
Authored: Thu Sep 3 22:56:39 2015 +0100
Committer: Alex Heneveld <>
Committed: Fri Sep 4 14:33:51 2015 +0100

---------------------------------------------------------------------- | 88 ++++++++--------------------------------------------------
 1 file changed, 11 insertions(+), 77 deletions(-)
diff --git a/ b/
index cfd1393..f068785 100644
--- a/
+++ b/
@@ -1,87 +1,21 @@
-# [![**Brooklyn**](](
+# [![**Brooklyn**](](
-Apache Brooklyn is a library and control plane for deploying and managing distributed applications.
+### Apache Brooklyn helps to model, deploy, and manage systems.
-See []( for details and
+It supports blueprints in YAML or Java, and deploys them to many clouds and other target
+It monitors those deployments, maintains a live model, and runs autonomic policies to maintain
their health.
-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).
+For more information see **[](**.
-### Deployment
-Brooklyn enables single-click deployment of complex applications, while tying-in with other
great tools, and reusing and complementing existing workflows.
+### To Build
-Use Brooklyn to create an Application Blueprint, instructing Brooklyn how to wire together
your applications and components, customizing and extending them as needed. Share the blueprint
with others (optionally using Brooklyn's Web Service Catalog) to allow them to single-click
deploy your application onto the infrastructure of their choice.
+The code can be built with a:
-Brooklyn features:
+    mvn clean install
-* out-of-the-box support for many common software components.
-* 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.
+This creates a build in `usage/dist/target/brooklyn-dist`.  Run with `bin/brooklyn launch`.
-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.
-### Management
-Brooklyn enables [autonomic management](
of applications. (i.e. many small, local, distributed control loops).
-Management policies can be attached to every component part in an application, and to logical
groupings of components (clusters, fabrics). Policies can implement both technical and non-technical
(business) requirements.
-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](
-* Fork or clone the repo: `git clone git://` then
`cd incubator-brooklyn; mvn clean install; cd usage/dist/target/brooklyn-dist; ./brooklyn/bin/brooklyn
-## Community
-* 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 [@ApacheBrooklyn]( and [@BrooklynCentral](
on Twitter.
-## Bug Tracker
-Have a bug or a feature request? [Please open a new issue](
-## Contributing
-Your input will be welcomed.
-See the [full guide to contributing](
-Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.
-See the [NOTICE](NOTICE) file distributed with this work for additional information
-regarding copyright ownership and the [incubation disclaimer](DISCLAIMER) file regarding
project status,
-as Apache Brooklyn is currently undergoing Incubation at the Apache Software Foundation.
-The ASF licenses this file to you under the Apache License, Version 2.0 
-(the "License"); you may not use this file except in compliance with the License.  
-You may obtain a copy of the License at [](
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-KIND, either express or implied.  See the License for the
-specific language governing permissions and limitations
-under the License.
+The **[developer guide](**
+has more information about the source code.

View raw message