#Computing on the cloud

Since yesterday a number of people have asked how to build web servers as described in the below post. Load Balancing with the IBM Smart Cloud tutorial

This is super simple and is achieved in 7 steps once again this will be based on using SUSE Linux but the method is transferable to all mainstream Linux distro’s if you are using Windows look here. Using Apache HTTP Server on Microsoft Windows. 

To start with download the latest version of the Apache Server at time of writing this was version 2.2 as 2.4 was still in beta

$wget http://apache.mirrors.timporter.net//httpd/httpd-2.2.22.tar.gz


Next we need to pen the correct ports on the firewall this is OS dependent. SUSE uses yast and to get the advanced function we require to run this as root via sudo

$sudo /sbin/yast

Open port 80 if you are going to use the standard web port for your website

Once you have open the ports extract the apache download the file comes tared and gun zipped use

$tar –zxvf httpd-2.2.22.tar.gz

If you need a simple way of referencing Linux commands then try this The One Page Linux Manual

Once this has extracted change directory to http-2.2.22/

Once in run

$sudo ./configure

This builds the Apache HTTPd source tree for your particular platform and personal requirements.

Now you can build the various parts which form the Apache HTTPd package by simply running the command:

$ make

Now install the server using

$sudo make install

Using sudo for this allows the installer to make directories and install files where idcuser doesn’t have permissions.

once this has completed its then just a case of starting the webserver for this we need to be in /usr/local/apache2/bin/ in here you can find the script required to start the web server run

$sudo apachectl start

This is also the script required to restart once the server has changed such as updates to htdocs.

Now test the server open any web browser and point it at the IP address or DNS name of the server you have just installed apache on and you should see the below message.


If this doesn’t work or times out 9 times out of 10 its an issue with the firewall so double check that port 80 is open.

I have recently been asked how to achieve load balancing on the IBM Smart Cloud as our customers endeavour to deploy more scale out web infrastructure.  To this end I have written this tutorial to demonstrate the relative ease with which this can be accomplished at its basic level. Load balancing on the IBM Smart Cloud is achieved by using IBM’s approved load balancing ISV image Riverbeds Stingray Product. I’m going to demonstrate by using the Stingray image on the Smart Cloud global catalogue how http load balancing can be achieved in under an hour ( the majority of which is waiting for the image to provision on the Smart Cloud).

In this tutorial I assume that you are confident in using the Smart Cloud portal to provision Linux instances and that you are also confident in managing them through a product like Putty using key based authentication if not please see a previous post Deploying an Instance on the IBM public cloud

Installing the Load Balancer on SUSE Linux.

So lets get started. Login to the smart cloud and deploy the Stingray Traffic Manager image of your choice. I am going to chose SUSE 64bit as this is the version I prefer using.


Once deployed wait for the image to become active.


Once the image is active, SSH into the image and perform the list of actions below:

  • Open ports required for the management of the load balancer $sudo /sbin/yast will open the systems management tool where you can open ports to enable web management. Port 9090 is required by the Stingray web management console. Port 80 is also required should you intend on load balancing HTTP web pages
  • Once this is complete, perform the following commands as root. To gain root use $sudo su root
  • Ensure you are the superuser.
  • Run the installation script: /home/idcuser/stingray-install
  • Run the configuration script: /usr/local/zeus/zxtm/configure
    1. Accept the license agreement
    2. When prompted for the license key enter: /tmp/stingray_devkey.txt
    3. Accept the default values for UNIX user and UNIX group
    4. When prompted with Would you like to restrict Stingray Traffic Manager management to one IP?, enter N
    5. When prompted for the cluster option enter C
    6. Enter a password for the Admin server when prompted. This password will be required to access the browser Administration interface.
    7. When prompted with Would you like Stingray Traffic Manager to start at boot time?, enter Y
    8. Verify the Traffic Manager starts (look for the message Starting Stingray Traffic Manager Software… OK)
  • Connect to the Admin server at the URL provided at the completion of the configuration script. Username is admin and the password is the one specified in step 6. Please see below web admin address in box.


Once you have the address of the web admin console use this to connect to the login screen, enter the password you created during the setup. Once logged in you will see the screen below.


Configuring Simple HTTP Load Balancing.

For this part of the tutorial I assume that you have something to load balance. For this I am simply using two apache web servers running on SUSE Linux. These have one web page each in htdocs with WebServer 1 and WebServer 2, to demonstrate that load balancing is occurring. I have found this a great method of testing load balancing is working as expected, if you want to use these files please feel free to download them from here: Webserver load balancing test index.htlm

To configure load balancing start by gathering together the DNS names or IP address of the webservers intended to load balance. From here click on Services and select Pool. This defines the load balanced resources (web servers) that the load balancer uses.


I have configured the pool to monitor the webservers using Simple HTTP. However, there are a number of other options available to you.  Once pool has been created add the second webserver and then click update.


Now Select Virtual Servers. We need to build a virtual web server which will be used as the point of entry to our load balanced web servers.

Start by giving the virtual server a name. Select the protocol which in this case is going to be HTTP, a port, which is 80, and then a pool which in this example is SmartCloud_LoadBalanced_Pool. Click create. Once this is created you can edit the load balancing settings. I have simply set this to round robin but you can setup load balancing based on link response time, weighted, predictive etc.


Go back to the home screen and click start in the services area that has appeared after setup. After a few seconds you will see the button you clicked go green and the Load balancer is up.


Now try accessing the web page you setup earlier, but use the load balancer DNS with HTTP. You should see the test webpage come up, refresh a couple more times and you will soon see the other web page demonstrating that requests are being sent to alternate web servers.


Hope this helps. We have really only scraped the surface of the product, so for more information check out the Riverbed website. Please feel free to leave comments.

Working today with a partner we ran into trouble while trying to workout the software licensing costs for Cognos. after a bit of digging found the below. Enjoy…

Taken from IBM Passport Advantage web site: http://www-01.ibm.com/software/lotus/passportadvantage/licensing_for_IBM_Cloud.html

The IBM SmartCloud Enterprise offering provides a hosted infrastructure service, including hardware, operating system, and services available on a pay as you go or reserved capacity basis. There are nine virtual machine (Instance) sizes available, and three licensing options for IBM customers to use IBM software. Customers can:

Access pre-configured virtual machine Images (Images) under the pay as you go (PAYG) option.
Access Images under the bring your own license (BYOL) option.
Bring and upload IBM software Programs under the bring your own software and license (BYOSL) option.

For more information about the IBM SmartCloud Enterprise service and the PAYG option, visit IBM SmartCloud Enterprise or email david.fearne@arrowecs.co.uk.

Customers can use software licenses, acquired under IBM’s International Passport Advantage or Passport Advantage Express Agreements (collectively PA or PA Program) with the IBM SmartCloud Enterprise service. For licensing requirements under either the BYOL or BYOSL use options, select the respective tab at the top of this webpage.

IBM Passport Advantage Customers can access or upload and install IBM Programs on Instances using Program licenses obtained from IBM. See the BYOL and BYOSL tabs for more information. For software Images and Programs which are licensed by Processor Value Unit (PVU), the Table of PVUs required per Instance below lists the number of PVU Entitlements required per software Image or Program for each IBM SmartCloud Enterprise (SCE) Instance size as of the Table publish date.


(a.) For more information about IBM Cloud Instances, visit IBM SmartCloud Enterprise

(b.) Certain restrictions may apply; consult the BYOL or BYOSL tabs for additional licensing requirements for software Images or Programs, respectively.

Note: PVU licensing requirements per Instance are subject to change without notice.

IBM Cloud is available through IBM.com/cloud. This is the landing page for all IBM’s cloud service offerings both public, private and virtual private. Today we are going to take a look at depolying an instance from the IBM Smart Cloud Enterprise which we will refer to as SCE. SCE is IBM’s IaaS offering and can be used to provision instances based on a pre-defined list of images. imageWe are Login to the SCE control panel by selecting Cloud portal login. If you don’t have an account send me an email at david.fearne@arrowecs.co.uk. The IBM cloud as I posted below is not an EC2 or GoGrid type of cloud the IBM cloud is managed and charged in a more traditional method using the IBM reseller channel. This has its pro’s and its cons as you might imagine but the main reason for this is that unlike the other cloud providers mentioned above, IBM has rules of operation that do not allow them to host certain business types such as gambling or pornography. This also enables the traditional IBM business partner value add model. The video below is a brief introduction to getting started with the IBM SCE Cloud.

Introduction to getting started with the IBM SCE Cloud.

This video has been cut down but total deployment length is 20mins. come back soon to see how we implement overlay networks to provide global private network, load balancing and high availability.

Getting up and running with a useful cloud service has never been so simple

Bitnami (odd name but great service) have gone to the trouble of creating a large number of pre-built either packages or entire images that can be deployed as or to common Linux operating systems or Windows. The packages include Ruby on Rails, LAMP and WAMP, WordPress, Joumla and many others. The very variety and speed at which you can deploy a fully working website, blog or application makes them very attractive to people looking to deploy web services quickly and with little or no further customisation. I have experimented with a few packages now and run the very blog you are reading this post from on a bitnami WordPress package on Linux. with a few teaks…

BitNami Stacks

BitNami Stacks make it incredibly easy to deploy your favorite open source software. BitNami Stacks include an open source application and all of the other software necessary to run it, such as Apache, MySQL, PHP or Ruby. All you need to do is select your deployment format of choice (Native Installer, Virtual Machine Image or Cloud Image) and either run the installation wizard or start the image. In just minutes, your new application will be ready to run. All Native Installers for the Stacks have been packaged using BitRock’s multiplatform installer.
There are other ways of using BitNami. If you choose to install a BitNami Stack natively on your system, you can download a base Stack and then use BitNami Modules for the added benefit of being able to install several applications on top of a single infrastructure stack. Learn more about BitNami modules. We also offer VMWare images and Cloud Images for most Linux-based stacks as a download option.

BitNami Application Stacks

SugarCRM Redmine Alfresco JasperServer
WordPress Drupal Joomla OSQA
Coppermine Photo Gallery DokuWiki Moodle eZ Publish
Gallery Mantis MediaWiki ocPortal

IBM cloud comes in 4 different options 3 to buy as components and one as previously mentioned for use as an on demand solution. I would like to focus this post on the three options available to the so called cloud builders. The companies whom deem it beneficial to adopt an on premise solution. These fall into two categories. Cloud Service Providers and cloud users. Cloud users are defined as companies whom see that aligning business process with IT service delivery is going to make good ROI. Working in this way can considerably up utilization of available compute power. By turning IT into a cost center for an organization and not just a black hole of money can get some CFO’s giddy with delight. But it is critical then to provide services that meet business requirements. The whole thing falls down as soon as someone mentions the word cross charge! But it doesn’t have to be that way. Provide a solution billed by a temporal metric and you are truly onto a winner.
Cloud Service Providers or CSP’s are ISV or traditional ISP’s looking to take advantage of new markets for their businesses. To this end IBM has a solution that provides a proven platform (proven in that in forms the core of their cloud offerings) to host in the case of ISV’s their application and via a simple to use portal deploy scale and manage the application very much like a sales force.com approach or to become an IaaS or PaaS providers such as IBM SCE or Amazon EC2 this os more aimed at the ISP’s looking to diversify and enable new revenue streams