Blueprints are descriptors or patterns which describe how Apache Brooklyn should deploy applications. Blueprints are written in YAML and many of the entities available are defined in the Brooklyn Catalog.
Launching from a Blueprint
- type: org.apache.brooklyn.entity.webapp.tomcat.TomcatServer
Before you can create an application with this configuration, you need to modify the YAML to specify a location. Locations in Apache Brooklyn are server resources which Brooklyn can use to deploy applications. These locations may be servers or cloud providers which provide access to servers.
In order to configure the location in which Apache Brooklyn launches an application, replace the
location: element with values for your chosen target environment. Here are some examples of the various location types:
The Vagrant configuration described in Running Apache Brooklyn, on the previous page is the recommended way of running this tutorial. This configuration comes with four blank vagrant configurations called byon1 to byon4.
These can be launched by entering the following command into the terminal in the vagrant configuration directory.
$ vagrant up byon1 byon2 byon3 byon4
A cloud location
"Bring your own nodes" location
The Bring Your Own Nodes (BYON) configuration allows Apache Brooklyn to make use of already available servers. These can be specified by a list of IP addresses with a user and password as shown below. More information including the full range of configuration options is available here.
Deploying the Application
First, log in to brooklyn with the command line interface (CLI) tool by typing:
$ br login http://localhost:8081/
To secure the Apache Brooklyn instance, you can add a username and password to Brooklyn's properties file, as described in the User Guide here. If this is configured, the login command will require an additional parameter for the userid and will then prompt for a password.
Now you can create the application with the command below:
$ br deploy myapp.yaml
Status: In progress
Depending on your choice of location it may take some time for the application to start, the next page describes how you can monitor the progress of the application deployment and verify if it was successful.
Having deployed an application, the next step is monitoring and managing it.