cloudsoft.io

Production Installation

To install Cloudsoft AMP on a production server:

  1. Set up the prerequisites
  2. Download Cloudsoft AMP
  3. Configuring brooklyn.properties
  4. Configuring Karaf Security
  5. Configuring default.catalog.bom
  6. Test the installation

This guide covers the basics. You may also wish to configure:

Set up the Prerequisites

Check that the server meets the requirements. Then configure the server as follows:

  • install Java JRE or JDK (version 8 or later)
  • install an SSH key, if not available
  • if the “localhost” location will be used, enable passwordless ssh login
  • create a ~/.brooklyn directory on the host with $ mkdir ~/.brooklyn
  • check your iptables or other firewall service, making sure that incoming connections on port 8443 is not blocked
  • check that the linux kernel entropy is sufficient
  • check that the ulimit values are sufficiently high
  • ensure external libraries are up-to-date, including nss for SSL.

Download and Configure Cloudsoft AMP

Download Cloudsoft AMP from the Cloudsoft website and install as described in get AMP running.

Configuring brooklyn.cfg

Set up brooklyn.cfg as described here:

  • Configure the users who should have access
  • Turn on HTTPS
  • Supply credentials for any pre-defined clouds

Configuring Karaf Security

Out of the box, Cloudsoft AMP includes the default Karaf security configuration. This configuration is used to manage connections to the ssh port of Karaf (which is available to localhost connections only). It is recommended that you update the credentials as detailed in the Karaf Security page.

Configuring the Catalog

By default AMP loads the catalog of available application components and services from catalog.bom on the classpath. The initial catalog is in catalog/ in the dist. If you have a preferred catalog, simply replace that file.

More information on the catalog is available here.

Confirm Installation

Launch AMP and it will remain running after you have logged out:

bin/start

Cloudsoft AMP should now be running on port 8081 (or other port if so specified).