Clocker

The Docker Cloud Maker

View On GitHub

Overview

The Clocker blueprints run in Apache Brooklyn. These instructions assume some familiarity with Apache Brooklyn. Appropriate links are included for those new to Brooklyn. For background information, see The Theory Behind Brooklyn and the Brooklyn Getting Started guide.

To use the Clocker blueprints you have two options:

  1. Download AMP
  2. Install AMP. For more detailed instructions, see the docs.
  3. Open the AMP UI in your favourite web browser (as per the detailed instructions within the link above) and setup a location for where you want to deploy to (e.g. your preferred cloud, or a list of IPs for pre-existing machines). We came up with location’s templates to add to your catalog, that you can use out of the box for AWS, SoftLayer, Azure, GCE and Blue Box. For more information, head to the tutorial section.

    Please note that we recommend the official Centos 7 images. Images from other providers may be less functional or incompatible.

  4. AMP includes a set of quick launch applications, for point-and-click deployment to your favourite location. These include Docker Swarm with Discovery and CA and Kubernetes Cluster. Choose the desired application, then your location, and any custom configuration options such as the size of cluster. Then click Deploy. Quick-launch of a Kubernetes cluster
  5. View your application in the App Dashboard (for a high-level overview) or the App Inspector (for a more detailed view). Once the app is deployed, this will show important information such as the connection details.

Clocker relies on some recent Brooklyn features that will be available in the next 0.10.0 release. Before that release is available, you can either use a pre-built early access release of Brooklyn or you can download the code and build Brooklyn master from source.

The instructions below assume you are using the Brooklyn in the “classic mode” (i.e. not using Karaf). They pick up from where you have the .tgz or .zip file).

  1. Install Apache Brooklyn. For more detailed instructions, see the docs.
  2. Download the required Clocker files, and add them to the Brooklyn ./lib/dropins/ folder (though these are jar files, the Clocker jars just package resources such as YAML files rather than Java code):
  3. Launch Brooklyn and add the Clocker blueprints to the catalog by using the clocker.bom file that lists the catalog items:
    • If you’d like to use the command line to do this, you will need the Apache Brooklyn CLI and run br add-catalog clocker.bom. For more details, see the docs.
    • Alternatively, if you’d like to use the web-console, choose the “Composer” tab, click the “Catalog” button, paste the contents of the clocker.bom file into the online editor, and click “Deploy”. For more details, see the docs.
  4. Setup a location for where you want to deploy to. This can be done by defining your location configuration in a .bom file and deploying using the br CLI. Alternatively, the web-console can be used: click on the Catalog tag, then the “+” button”, choose “Location”, and follow the instructions in the wizard. We came up with location’s templates to add to your catalog, that you can use out of the box for AWS, SoftLayer, Azure, GCE and Blue Box. For more information, head to the tutorial section.

    Please note that we recommend the official Centos 7 images. Images from other providers may be less functional or incompatible.

  5. The catalog items added previously will be available in the Brooklyn quick launch. In the web-console, from the Home tab click the “Add application” button, choose your application, then your location, and any custom configuration options such as the size of cluster. Then click Deploy. For more details, see the docs. Quick-launch of a Swarm or Kubernetes cluster
  6. View your application in the “Applications” tab. Once the app is deployed, this will show important information such as the connection details. Click on the entity (i.e. component) in the tree view, and the “Sensors” tab to see details of that entity. For more details, the docs.