Launching from a Blueprint
When you first access the web console on http://127.0.0.1:8081 you will be requested to create your first application.
We’ll start by deploying an application via a YAML blueprint consisting of the following layers.
- MySQL DB
- Dynamic web application cluster
- Nginx load balancer
- Tomcat app server cluster
Switch to the YAML tab and copy the blueprint below into the large text box.
But before you submit it, modify the YAML to specify the location where the application will be deployed.
name: My Web Cluster location: jclouds:aws-ec2: identity: ABCDEFGHIJKLMNOPQRST credential: s3cr3tsq1rr3ls3cr3tsq1rr3ls3cr3tsq1rr3l services: - type: org.apache.brooklyn.entity.webapp.ControlledDynamicWebAppCluster name: My Web id: webappcluster brooklyn.config: wars.root: http://search.maven.org/remotecontent?filepath=org/apache/brooklyn/example/brooklyn-example-hello-world-sql-webapp/0.8.0-incubating/brooklyn-example-hello-world-sql-webapp-0.8.0-incubating.war java.sysprops: brooklyn.example.db.url: > $brooklyn:formatString("jdbc:%s%s?user=%s&password=%s", component("db").attributeWhenReady("datastore.url"), "visitors", "brooklyn", $brooklyn:external("brooklyn-demo-sample", "hidden-brooklyn-password")) - type: org.apache.brooklyn.entity.database.mysql.MySqlNode name: My DB id: db brooklyn.config: creation.script.password: $brooklyn:external("brooklyn-demo-sample", "hidden-brooklyn-password") datastore.creation.script.url: https://bit.ly/brooklyn-visitors-creation-script
location: element with values for your chosen target environment, for example to use SoftLayer rather than AWS (updating with your own credentials):
location: jclouds:softlayer: identity: ABCDEFGHIJKLMNOPQRST credential: s3cr3tsq1rr3ls3cr3tsq1rr3ls3cr3tsq1rr3l
NOTE: See Locations in the Operations section of the User Guide for instructions on setting up alternate cloud providers, bring-your-own-nodes, or localhost targets, and storing credentials/locations in a file on disk rather than in the blueprint.
With the modified YAML in the dialog, click “Finish”. The dialog will close and Brooklyn will begin deploying your application. Your application will be shown as “Starting” on the web console’s front page.
Depending on your choice of location it may take some time for the application nodes to start, the next page describes how you can monitor the progress of the application deployment and verify its successful deployment.
Launching from the Catalog
Instead of pasting the YAML blueprint each time, it can be added to the Brooklyn Catalog where it will be accessible from the Catalog tab of the Create Application dialog.
See Catalog in the Operations section of the User Guide for instructions on creating a new Catalog entry from your Blueprint YAML.
So far we have touched on Brooklyn’s ability to deploy an application blueprint to a cloud provider.
The next section will show how to Monitor and Manage Applications.