cloudsoft.io

Get AMP Running

Objectives

The following instructions will guide you through the necessary steps to set up and run Cloudsoft AMP.

Pre-requisites

None! This tutorial takes you from a fresh start to an AMP ready to deploy applications.

System Requirements

Server Specification

The size of server required by Cloudsoft AMP is determined by a variety of factors:

  • The number of entities and Virtual Machines (VMs) being managed
  • The number of VMs being deployed concurrently
  • The amount of management and monitoring required per entity

For development and testing or when there are only a handful of VMs being managed, a small VM is sufficient. For example, an AWS m3.medium instance with one vCPU, 3.75GiB RAM and a 4GB disk.

For larger production uses, a more appropriate machine specification would be two or more cores, at least 8GiB RAM and 100GB disk. The disk is just for logs, a small amount of persisted state, and any binaries for custom blueprints/integrations.

Instructions

The instructions below guide you through the following steps:

  • Install pre-requisites of Cloudsoft AMP
  • Install AMP
  • Configure AMP
  • Run AMP
  • Undeploy

Install Cloudsoft AMP

You will need Java or JDK (version 8) installed.

From Downloads, please download the .rpm package.

sudo yum -y update
sudo yum -y install cloudsoft-amp-karaf--xxxxxxxx-noarch.rpm

replacing VERSION with the appropriate value from the filename of your download.

This will install the AMP binaries in /opt/amp, and start AMP using the appropriate service management tool for your system (e.g. upstart). (Alternatively rpm -Uvh can be used, and --prefix /custom/install/path/ is supported to install to a different location.)

You will need Java or JDK (version 8) installed.

From Downloads, please download the .deb package.

sudo apt-get update
sudo apt-get install -y openjdk-8-jre
sudo dpkg -i cloudsoft-amp-karaf--xxxxxxxx-all.deb

replacing xxxxxxxx with the appropriate value from the filename of your download.

This will install the AMP binaries in /opt/amp, and start AMP using the appropriate service management tool for your system (e.g. systemd).

You will need Java or JDK (version 8) installed.

From Downloads, please download the tar.gz archive.

Extract the tar.gz archive and navigate into the expanded cloudsoft-amp-karaf- folder.

$ tar -zxf cloudsoft-amp-karaf-.tar.gz
$ cd cloudsoft-amp-karaf-

You will need Java or JDK (version 8) installed.

From Downloads, please download the zip archive.

Extract the zip archive and navigate into the expanded cloudsoft-amp-karaf- folder.

cd cloudsoft-amp-karaf-

Launching and Stopping AMP

AMP is managed as a system service using the appropriate tool for your system (e.g. systemd). When the AMP package is installed, the amp service is started for you.

Now, as root (or using sudo), you can monitor AMP’s status, and stop and start it, with the following commands for systemd:

$ systemctl status amp
$ systemctl stop amp
$ systemctl start amp

Configuration can be edited at /etc/amp/.

Logs are written to /var/log/amp/amp.info.log and /var/log/amp/amp.debug.log.

You should now be able to login to the AMP user interface (as admin/password) on port 8081 of the server, such as http://localhost:8081/. To set your own credentials see Setting Web Credentials.

AMP is managed as a system service using the appropriate tool for your system (e.g. upstart). When the AMP package is installed, the amp service is started for you.

Now, as root (or using sudo), you can monitor AMP’s status, and stop and start it, with the following commands for upstart:

$ status amp
$ stop amp
$ start amp

Configuration can be edited at /etc/amp/.

Logs are written to /var/log/amp/amp.info.log and /var/log/amp/amp.debug.log.

You should now be able to login to the AMP user interface (as admin/password) on port 8081 of the server, such as http://localhost:8081/. To set your own credentials see Setting Web Credentials.

To start Cloudsoft AMP (assuming you are in the cloudsoft-amp-karaf- directory):

$ ./bin/status amp
$ ./bin/stop amp
$ ./bin/start amp

Configuration can be edited at etc/.

Logs are written to data/log/amp.info.log and data/log/amp.debug.log.

You should now be able to login to the AMP user interface (as admin/password) on port 8081 of the server, such as http://localhost:8081/. To set your own credentials see Setting Web Credentials.

To start Cloudsoft AMP (assuming you are in the cloudsoft-amp-karaf- directory):

bin\status.bat amp
bin\stop.bat amp
bin\start.bat amp

Configuration can be edited at etc\.

Logs are written to data\log\amp.info.log and data\log\amp.debug.log.

You should now be able to login to the AMP user interface (as admin/password) on port 8081 of the server, such as http://localhost:8081/. To set your own credentials see Setting Web Credentials.

Setting Web Credentials

  • If you are using the .rpm or .deb, the path to the files (below), will be /etc/amp
  • If you are using the .tar.gz install, the path to the files (below), will be <YOUR INSTALL PATH>/cloudsoft-amp-karaf

By default AMP is secured with the following credentials:

Username: admin
Password: password

It is strongly recommended that the default username/password is changed. To do so, edit the file brooklyn.cfg (e.g. sudo vim /path/to/amp/etc/brooklyn.cfg) and set the appropriate values for the brooklyn.webconsole.security properties, e.g. to give the user user1 a password of 12str0ngPa5swor+d:

# Credentials for user 'user1'
brooklyn.webconsole.security.users=user1
brooklyn.webconsole.security.user.user1.password=12str0ngPa5swor+d

You will need to restart the AMP instance for the changes to take effect.

Persistence Data

The default location for persistence data for AMP is ~/.brooklyn/brooklyn-persisted-state.

This can be changed by updating the persistenceDir and persistenceLocation values in the file /etc/org.apache.brooklyn.osgilauncher.cfg.

Next

AMP and Maeztro are developed and supported by Cloudsoft Corporation.