Apache Brooklyn contains a number of configuration options managed across several files. Historically Brooklyn has been configured through a brooklyn.properties file, this changed to a brooklyn.cfg file when the Karaf release became the default in Brooklyn 0.12.0.
Configuration of Apache Brooklyn when running under Karaf is largely done through standard Karaf mechanisms.
The Karaf "Configuration Admin" subsystem is used to manage configuration values loaded at first boot from the
.cfg files in the
etc directory of the distribution. In the Karaf command line these can then be viewed
and manipulated by the
config: commands, see the Karaf documentation for full details.
Configuring Brooklyn Properties
To configure the Brooklyn runtime create an
etc/brooklyn.cfg file. If you have previously used
brooklyn.properties it follows the same
file format. Values can be viewed and managed dynamically via the OSGI configuration admin commands in Karaf,
config:property-set. The global
~/.brooklyn/brooklyn.properties is still supported and has higher
priority for duplicate keys, but its values can't be manipulated with the Karaf commands, so its use is
You can use the standard
~/.brooklyn/brooklyn.properties file to configure Brooklyn. Alternatively
etc/brooklyn.cfg inside the distribution folder (same file format). The keys in the former override
those in the latter.
Web console related configuration is done through the corresponding Karaf mechanisms:
- The port is set in
- For authentication the JAAS realm "webconsole" is used; by default it will use any
SecurityProvider implementations configured in Brooklyn falling back to auto generating
the password. To configure a custom JAAS realm see the
brooklyn-server/karaf/jetty-config/src/main/resourcesand override it by creating a custom one in
etcfolder. Point the "webconsole" login service to the JAAS realm you would like to use.
- For other Jetty related configuration consult the Karaf and pax-web docs.
The amount of memory required by Apache Brooklyn process depends on the usage - for example the number of entities/VMs under management.
For a standard Brooklyn deployment, the defaults are to start with 256m, and to grow to 2g of memory. These numbers can be overridden
by setting the
JAVA_MAX_PERM_MEM in the
Apache Brooklyn stores a task history in-memory using soft references. This means that, once the task history is large, Brooklyn will continually use the maximum allocated memory. It will only expunge tasks from memory when this space is required for other objects within the Brooklyn process.
Authentication and Security
There are two areas of authentication used in Apache Brooklyn, these are as follows:
- Karaf authentication
- Apache Brooklyn authentication
Users and passwords for Brooklyn can be configured in the brooklyn.cfg as detailed here.
See HTTPS Configuration for general information on configuring HTTPS.
Catalog in Karaf
With the traditional launcher, Brooklyn loads the initial contents of the catalog from a
as described in the section on installation. Brooklyn finds Java
implementations to provide for certain things in blueprints (entities, enrichers etc.) by scanning the classpath.
In the OSGI world this approach is not used, as each bundle only has visibility of its own and its imported Java packages.
Instead, in Karaf, each bundle can declare its own
catalog.bom file, in the root of the bundle,
with the catalog declarations for any entities etc. that the bundle contains.
For example, the
catalog.bom file for Brooklyn's Webapp bundle looks like (abbreviated):
- id: org.apache.brooklyn.entity.webapp.nodejs.NodeJsWebAppService
name: Node.JS Application
- id: resilient-bash-web-cluster-template
name: "Template: Resilient Load-Balanced Bash Web Cluster with Sensors"
Sample YAML to provision a cluster of the bash/python web server nodes,
with sensors configured, and a load balancer pointing at them,
and resilience policies for node replacement and scaling
name: Resilient Load-Balanced Bash Web Cluster (Brooklyn Example)
In the above YAML the first item declares that the bundle provides an entity whose type is
org.apache.brooklyn.entity.webapp.nodejs.NodeJsWebAppService, and whose name is 'Node.JS Application'. The second
item declares that the bundle provides a template application, with id
includes a description for what this is.
Configuring the applications in the Catalog
When running some particular deployment of Brooklyn it may not be desirable for the sample applications to appear in
the catalog (for clarity, "application" here in the sense of an item with
For example, if you have developed
some bundle with your own application and added it to Karaf then you might want only your own application to appear in
Brooklyn contains a mechanism to allow you to configure what bundles will add their applications to the catalog.
The Karaf configuration file
/etc/org.apache.brooklyn.core.catalog.bomscanner.cfg contains two properties,
whitelist and the other
blacklist, that bundles must satisfy for their applications to be added to the catalog.
Each property value is a comma-separated list of regular expressions. The symbolic id of the bundle must match one of
the regular expressions on the whitelist, and not match any expression on the blacklist, if its applications
are to be added to the bundle. The default values of these properties are to admit all bundles, and forbid none.
In the OSGi world specifying class names by string in Brooklyn's configuration will work only for classes living in Brooklyn's core modules. Raise an issue or ping us on IRC if you find a case where this doesn't work for you. For custom SecurityProvider implementations refer to the documentation of BrooklynLoginModule.