Skip to content
This repository has been archived by the owner on Jan 31, 2019. It is now read-only.

Setting Up and Running Your Own Widget Server

Jump to bottom
guy-mograbi-at-gigaspaces edited this page Jan 1, 2013 · 3 revisions

cloudify-widget

The Cloudify Widget is a server that allows to a Cloudify "recipe player" in other website, and allow visitors to launch a certain recipe with a single click. It uses HPCloud to provision VMs and host the installed recipes everytime a user launches a recipe using the widget. Provisioning of the VMs and the interaction with the cloud APIs is done via the jclouds library.

Supported Platforms

The widget server was tested on CentOs 5.6 and ec2-linux. Technically it should also support Debian/Ubuntu flavors (although it has never been tested).

Installation

  • Install a Java SDK (1.6 or 1.7, OpenJDK will also work), e.g.

      yum install java-1.6.0-openjdk-devel

    Note that the above command requires sudo permissions.

  • set the JAVA_HOME environment variable, e.g.

      export JAVA_HOME=/usr/lib/jvm/java-1.6.0-openjdk.x86_64

  • From your home directory, install Play framework 2.0.x, e.g.

      wget 'http://download.playframework.org/releases/play-2.0.4.zip'
  unzip play-2.0.4.zip

  • From your home directory, install Cloudify:

      wget 'http://repository.cloudifysource.org/org/cloudifysource/2.2.0-RELEASE/gigaspaces-cloudify-2.2.0-ga-b2500.zip'
  unzip gigaspaces-cloudify-2.2.0-ga-b2500.zip

  • Install git on the server. You can do so using yum or apt-get depending on the linux flavor you use, e.g.:

      yum install git

  • Clone this repository with git

      git clone https://github.com/CloudifySource/cloudify-widget.git

  • Configure cloud credentials (cloud provider credentials, pem file, ssh user) Copy your cloud ssh keypair file to a known location on the server machine, and set the location of the ssh key file in the conf/cloudify.conf file, e.g.

      server.bootstrap.ssh-private-key=/bin/hpcloud.pem

    Set the HPCloud credentials in the conf/cloudify.conf file. You should set the following two properties to your corresponding HPCloud account details:

      server.bootstrap.api-key=<HP Cloud Password>
  server.bootstrap.username=<tenant>:<user>

  • Configure the location of the Cloudify distribution In the file bin/deployer.sh, edit the following line to point to the root of the cloudify distribution you installed on the server:

      GS_HOME=~/gigaspaces-cloudify-2.2.0-ga

  • Start Play: cd to the directory in which you installed the Play framework. If you're in development mode, type run <port number>, otherwise type start <port number>

  • The login page for widget admins is located at /admin/signin.html

Configuration Options

All configuration options can be found at the cloudify.conf file, here are the major ones you should be aware of:

// The instance ID of the server on HPCloud. Used to filter it out when tearing down VMs on startup
widget.server-id=466999

// Determines whether to clear all the data from the DB and shutdown all running VMs in the account,
// or leave things as is
server-pool.cold-init=false

// The minimum and maximum number of nodes in the server pool
server-pool.min-nodes=2
server-pool.max-nodes=5

//The availability zone on which tp deploy the server and VMs
server.bootstrap.zone-name=az-1.region-a.geo-1

//The name of the keypair used for ssh'ing to the created VMs
server.bootstrap.key-pair=cloudify

//the security group to use when launching machine
server.bootstrap.security-group=default

//the image flavor and id of the widget VMs created by the server
server.bootstrap.flavor-id=102
server.bootstrap.image-id=1358

//ssh user for the created VMs
server.bootstrap.ssh-user=root

//ssh port for the created VMs
server.bootstrap.ssh-port=22

//the location of the ssh key file on the server machine
// note that this is a relative path. ~app_root/bin/hpcloud.pem
server.bootstrap.ssh-private-key=/bin/hpcloud.pem

//the HPCloud account API key, tenant and user ID. Used when starting new VMs
server.bootstrap.api-key=<HP Cloud Password>
server.bootstrap.username=<tenant>:<user>

Open Ports

iptables -A INPUT -i eth0 -p tcp -m multiport --dports 80 -m state --state NEW,ESTABLISHED -j ACCEPT

iptables -A OUTPUT -o eth0 -p tcp -m multiport --sports 80 -m state --state ESTABLISHED -j ACCEPT

service iptables save
/etc/init.d/iptables restart

Edit hosts file

echo "127.0.0.1 `hostname`" >> /etc/hosts

Database

Although Play!Framework 2.0 comes with evolutions - a DB version mechanism, however, we decided to implement our own shell script for auto-manually upgrading the schema.

You can easily re-enable the evolutions mechanism from the configuration file.

Alternatively, you can configure the shell script and run it.

This script is found at bin/migrate_db.sh

For you convenience this script assumes it is already running with mysql. It draws all the configuration from an external file located at /etc/sysconfig/play. ( Best practice for writing multiple scripts with same configuration ).

This file looks something like

WIDGET_HOME=/root/play-2.0.4/cloudify-widget
DB_USER=<user>
DB_PASSWORD=<password>
DB_ADMIN=<root-user>
DB_ADMIN_PASSWORD=<root-password>
DB=<db-schema>

In order to get started, run the "create.sql" and then the migrate script.

bin/migrate_db.sh create

The "create.sql" generates the "patchlevel" table required for the migrate script to work properly.

Use the migrate script by providing it the goal version. For example, if you want to reach version 3, run the command

bin/migrate_db.sh 3

Currently, downgrades are done manually.

Home

Users

Developers

Clone this wiki locally