Get AMP Running

Objectives

The following steps will walk you through deploying a simple Tomcat application using Cloudsoft AMP.

There are two methods of deployment detailed in this tutorial, firstly using virtualization with Vagrant and then installing AMP on AWS.

To get you up-and-running quickly, the Vagrant option will provision four compute nodes for you to deploy applications to.

Pre-requisites

None! This tutorial takes you from a fresh start to an AMP with a deployed application.

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
• Set up an AWS or BYON location
• Deploy a simple Tomcat app
• Undeploy

Install Cloudsoft AMP

• Vagrant
• CentOS / RHEL
• Ubuntu / Debian
• OSX / DIY
• Microsoft Windows

$ git clone https://github.com/cloudsoft/amp-vagrant.git
$ cd amp-vagrant

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

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

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

cd cloudsoft-amp-karaf-

Launching and Stopping AMP

• Vagrant
• CentOS / RHEL
• Ubuntu / Debian
• OSX / DIY
• Microsoft Windows

$ vagrant up amp

$ vagrant ssh amp --command 'sudo systemctl status amp'

$ vagrant ssh amp --command 'sudo tail -f /var/log/amp/amp.info.log'
$ vagrant ssh amp --command 'sudo tail -f /var/log/amp/amp.debug.log'

$ vagrant up byon1 byon2 byon3 byon4 byon5

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

$ status amp
$ stop amp
$ start amp

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

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

Setting Web Credentials

• If you are using the .rpm, .deb or Vagrant install, 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.

Add a Location

Locations are the environments to which AMP deploys applications. Most commonly these are cloud services such as AWS, GCE, and Microsoft Azure. AMP also supports deploying to a pre-provisioned network or to localhost (useful for testing blueprints).

If you are following the Vagrant steps then you can use the provisioned VMs as part of a Bring Your Own Nodes network or you may follow the steps for setting up an AWS-based location. If you have have deployed AMP on Linux then you will need to use a cloud service (i.e. AWS) for the rest of this tutorial.

• Vagrant
• AWS

Deploy a single VM

We are now going to deploy a Tomcat server with a simple application using the Cloudsoft AMP user interface.

If you have set up an AWS location then AMP will first provision a VM.

If you have set up a Vagrant-based BYON location then AMP will take the first unused VM from the pool that you configured.

Browse to AMP http://localhost:8081/.

Let’s now deploy the Tomcat Server application.

Depending on your version of AMP, you may find it in the quick launch section; if this is the case, just select it.

If you don’t find Tomcat in the quick launch section though, just click Catalog, then Types. You can find it there by typing “Tomcat 7” in the “Search for bundles or types” box. Click it to go to its detail page, then click the “Deploy” button.

Enter a meaningful name e.g. My Tomcat Server.

In the Location box start typing “My First Location”. It should auto-complete.

The AMP examples provide a simple example WAR that you can use (link below). This file contains the simple, existing Java web application that AMP will deploy and manage.

http://search.maven.org/remotecontent?filepath=org/apache/brooklyn/example/brooklyn-example-hello-world-sql-webapp/1.0.0/brooklyn-example-hello-world-sql-webapp-1.0.0.war

Copy the link into the wars.root config box.

Click Deploy.

Click on the View link in the notification that appears in the bottom left of the page.

You should now see a page showing that your Tomcat server is STARTING.

Wait until the Tomcat server is shown as RUNNING (you may need to refresh the page to see this).

Click Open in Inspector.

The Inspector gives you a detailed look into the state of your deployed application. For now, we will just use it to access the web app that we just deployed and then to stop it and tear down the VM we created.

On the left you will see a list of applications that have been deployed. At the moment you should see a single application made up of a single Tomcat Server instance.

Click the Tomcat Server entity.

Click the sensors tab on the right-hand panel. This will show us data specific to the deployed Tomcat.

Use the filter to find the webapp.url sensor. Copy the sensor value (i.e. the web URL) to a new tab or browser window. You should now see the Hello World app that we deployed.

Stop Everything

Congratulations - you have now deployed your first application using Cloudsoft AMP.

Let’s now tear it all down. The next steps will stop your Tomcat Server and, if you have provisioned one, destroy your VM.

Return to the Inspector and click on your top level application (My Tomcat Server).

Click on the Effectors tab.

Click the Invoke button next to the stop effector.

Click Confirm.

Your Tomcat application should now be STOPPING. Once it has stopped it will disappear from the list of deployed applications (you may need to refresh the page to see this).

Summary

Congratulations! You have successfully used Cloudsoft AMP to deploy, manage and tear down an application.

In this tutorial you covered:

• Vagrant
• AWS

Next

• Explore more Tutorials