It supports blueprints in YAML or Java, and deploys them to many clouds and other target environments. It monitors those deployments, maintains a live model, and runs autonomic policies to maintain their health.
For more information visit brooklyn.apache.org, where you'll find:
This is the uber-repo. To build the entire codebase, get this project and its sub-modules:
git clone http://github.com/apache/brooklyn/ cd brooklyn git submodule init git submodule update --remote --merge --recursive
And then, with jdk 1.8+ and maven 3.1+ installed:
mvn clean install -Dno-go-client -Dno-rpm -Dno-deb
However, you won‘t be able to build the RPM/DEB packages, as well as the CLI. That’s why we would recommand to use the alternative: a docker container to build this project:
docker build -t brooklyn . docker run -i --rm --name brooklyn -v ${HOME}/.m2:/root/.m2 -v ${PWD}:/usr/build -w /usr/build brooklyn mvn clean install
The results are in brooklyn-dist/dist/target/
, including a tar and a zip. Or to run straight after the build, do:
pushd brooklyn-dist/dist/target/brooklyn-dist/brooklyn/ bin/brooklyn launch
The Developers section of the main website contains more detail on working with the codebase. There is also a more Developer Guide specific to each version, including this branch (1.0.0-SNAPSHOT), latest stable, and older releases.
Useful topics include:
getting the source code
setting up Git with forks, submodules (or alternatively avoiding submodules) and other productivity hints
the maven build and what to do on build errors
project structure of the codebase and submodules
the people behind Apache Brooklyn
This software is distributed under the Apache License, version 2.0, copyright (c) The Apache Software Foundation and contributors. Please see the LICENSE file for (1) the full text of the Apache License, followed by (2) notices for bundled software and (3) licenses for bundled software.