Installing Turbonomic AWS Cloud Manager

This post will cover the installation of Turbonomic Cloud Manager for Amazon Web Services. Turbonomic is an autonomous management platform able to continuously analyse your environment and provide recommendations for downsizing applications without sacrificing performance. This saves administrators time and effort and directly reduces infrastructure costs for pay as you go cloud services. Each Turbonomic instance is able to target up to 100 EC2 instances (virtual machines), you can read more product information here.

In this post we will deploy v.5.6 of Turbonomic Operations Manager for AWS. The installation consists of creating a new user to authenticate the AWS account from Turbonomic, launching the Turbonomic AMI, running the setup wizard, and finally setting our budget.

Requirements

  • Turbonomic is deployed as an AMI (Amazon Machine Image), it is recommended that the AMI is deployed as m3.xlarge – 4 vCPU, 15 GB RAM, 2 x 40 GB SSDs, with an additional 150 GB disk.
  • Sign up here for a license key, contact your Turbonomic sales representative for full licensing information.
  • Remember that to spin up the AMI you will be charged for infrastructure costs in line with your AWS agreement. If you are new to AWS there is a free tier which you can read about here, to be eligible for free infrastructure services the AMI will be deployed as t1.micro (this is insufficient for production environments).

For further resources see the Green Circle Community or the Turbonomic User Guide.

User Configuration

First we need a user account to connect to the target AWS account from Turbonomic. If you want to read more about AWS users and permissions click here. Open the AWS console and expand the drop down Services menu. Under Security, Identity & Compliance select IAM (Identity and Access Management). Click Users and then Add User. Configure a username and select Programmatic access to generate an access key ID and access key secret. Click Next.

user1

Next we need to assign permissions to the user, select Attach existing policies directly. Search for, and select, AmazonS3FullAcess and AmazonEC2FullAccess. Click Next.

user2

Check the information on the review page, it should look something like the screenshot below. Click Create User.

user3

The user will now be created and the access key ID and secret generated. Make a note of both the access key ID and the secret, we will need them to configure Turbonomic shortly. You may also want to record these details in a password safe, since they cannot be retrieved from AWS once you exit this page.

Launch Turbonomic AMI

From the EC2 management console select Instances and click Launch Instance. Select Community AMIs and search for the Turbonomic public AMI ID: ami-4d01295a. Click Select.

ami

Select the m3.xlarge instance size and click Next.

amiami2

On the configuration page review the instance details, if you need to change anything specific to your environment then do so, otherwise accept the default settings and click Next.

On the storage page verify that an additional 150 GB disk volume has been added, click Next.

ami3

Add any tags if required and click Next. Add firewall rules for SSH, HTTP, and HTTPS by clicking Add Rule and using the dropdown menu. You can specify an IP range to allow access from in the source fields, or leave the default values to allow access from an IP. Once complete click Review and Launch.

ami4

Determine the boot volume type and click Next. Check the details on the review page and click Launch to launch the instance. Select the key pair to use when prompted.

ami5

To check on the progress of the deployment go back to the EC2 management console and select Instances from the left hand navigation pane. When the instance state changes to running you need to wait a minimum of 5 minutes (possibly longer) for background configuration to take place. Make a note of the values in the Instance ID, Public DNS and Public IP columns.

Turbonomic Configuration

Access Turbonomic by browsing to either the public IP address or public DNS name. Log in with the administrator account, the default password is the unique instance ID.

561

The first time you log in the setup wizard will automatically start, click Next.

562

Select the full product license. Retrieve the evaluation email from Turbonomic and copy and past the contents of the license.txt file into the license field. Click Next.

563

Now we need to add our target system to monitor. Click Add.

564

Change the target to Cloud Management and select AWS. Enter an identifiable name for the AWS account in the address field. You will need the the access key details we recorded earlier; enter the access key ID in the username field and the access key secret in the password field. To commit the information click Add, then Apply and Next.

5655

Enter an SMTP server and email address to receive alerts and notifications, click Next. Review the getting started page and click Finish.

566

Turbonomic will now scan the configured target and begin making recommendations after 1-2 hours.

dashboard

Set Preferences

The final step is to configure a budget for the targeted AWS account, this allows Turbonomic to factor in cloud costs when analysing workload placements. Open a terminal session, there are a number of different ways to do this, in my case I have opened an SSH session with an Amazon Linux AMI I had running in the same EC2 instance on the same subnet. You can read more about connecting to a Linux terminal here, and using the AWS CLI here.

First we need to obtain the UUID, run the following, where username and password are the administrator login credentials used to access the Turbonomic web GUI, and turbonomic is the IP address or public DNS name of the Turbonomic instance:

curl -u “username:password” -X GET “https://turbonomic/vmturbo/api/targets” -k

Locate the UUID value, this will be after the targetType=”AWS”. Make a note of the UUID.

In the example below you can see I have added the administrator username, the password which is still the instance ID, and the public IP address. The UUID for my particular instance is highlighted.

uuid

The budget can now be defined using the following command, you will need to replace account with the name of the AWS business account, replace amount with the amount limit in $ per hour, and replace uuid with the UUID recorded in the previous step. Once again username and password relate to the administrator login account for the Turbonomic GUI, and turbonomic should be replaced with the IP address or public DNS name.

curl -v -X POST -d “name=account&budget=amount&targets[]=uuid” https://username:password@turbonomic/vmturbo/api/accounts -k

You can see the details I have entered in the example below.

enter

The budget has now been set and will be taken into consideration by Turbonomic when making recommendations. Use the Turbonomic User Guide and the documentation on your evaluation email from the sign up link above to configure policies for cross cloud migration and behavioural environments tailored for your environment.

For more information see the related content section at the bottom of this page, or contact cloud_support at turbonomic.com.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: