Archive for the ‘Cloud Computing’ Category

One of the strengths of OpenStack is that it exposes a very rich API that can be used to control every aspect of your cloud.  Likewise, one of the more intriguing ways of interacting with an OpenStack cloud is programatically.  There is a Ruby Gem named Fog that allows such interaction.  Details on the API methods that Fog provides support for can be found at http://fog.io/ – the website for Fog: The Ruby Cloud Services Library. (more…)

I was recently asked to show an example of how Windows Server 2012 running Internet Information Service (IIS) 8 can scale out in an OpenStack environment. I accepted the challenge and this post is the result.  To accomplish the task, I did a default install of an evaluation version of Windows Server 2012 and installed/configured IIS8 along with ASP.net support.  I then created a very simple web page that uses server variables and the current date an time to create some dynamic content.  Lastly, I installed the CloudBase Cloud-Init service so that Windows Server could talk to the OpenStack metadata service.  I hope you enjoy the video. (more…)

After a long delay (I was moving into a new house and work keeps me very busy) here is the second part of my post on creating scale out workloads in OpenStack using Heat and Ceilometer.  In part one, we broke down the different parts of the Heat template that we will be using in this part of the posting.  We also covered how I had images and software repos configured to support the WordPress website the template will be deploying.  In this part, we will deploy the application, or stack as it is called in OpenStack lingo, and look at different ways to monitor the application to see what is going on. (more…)

Recently, I have been spending a fair amount of time tinkering with Red Hat Enterprise Linux OpenStack Platform 5 (RHEL-OSP 5) which is Red Hat’s Icehouse based offering of OpenStack.  My goal was to learn how to get OpenStack to scale workloads up and down as needed.  Elasticity like this is one of the essential characteristics of cloud computing as defined by the National Institute of Science and Technology (NIST), and is one of the capabilities that OpenStack has that traditional data center virtualization systems typically don’t possess. (more…)

A lot of people are probably looking at all of the OpenStack offerings that are out there today and wondering “Which one should I use?”  or “What feature makes one company’s OpenStack better the others?”  One feature that causes Red Hat’s offering to stand out among the others is the inclusion of sVirt.  In the simplest terms, sVirt is SELinux for virtualization.  It implements Mandatory Access Controls to provide protection from potential attacks that could result in hosts or virtual machine instances being compromised.  Other Red Hat products take advantage of sVirt as well, including the stand alone KVM hypervisor that comes with Red Hat Enterprise Linux and Red Hat Enterprise Virtualization. (more…)

If you are a fan of OpenStack, then I am sure that you have heard of the new Load Balancer as a Service (LBaaS) features of Neutron (formerly Quantum).  As the name indicates, it allows an OpenStack user to configure a load balancer for virtual machines running in OpenStack with relative ease.  I used Red Hat’s OpenStack and noticed that LBaaS is included, but not configured by default.  The goal of this post will be to walk you through the configuration changes that need to take place on an operational OpenStack install and demonstrate how to load balance two web servers.

My Lab Setup

First, let me talk a bit about my OpenStack lab environment.  It is small, just a couple of servers.  The controller, named openstack-ctrl, runs as a virtual machine in a Red Hat Enterprise Virtualization environment and provides all of the supporting services (mysql, qpid, Keystone, Cinder, Glance, Nova-API and Horizon)  in OpenStack along with the Quantum server.  A physical server, named server3, acts as a Nova Compute node and also hosts the Quantum L3, DHCP and metadata services.

I have the following networks configured in OpenStack:

Internal (Private): 10.0.0.0/24 – this network is used for DHCP as well
External (Public): 192.168.1.0/24 – this network is for connectivity to the external network.
A floating IP range available from 192.168.1.130-143

The web servers that I am using to show how the LBaaS works have been preconfigured with a unique hostname and a php page that returns the hostname of the server that is responding to the request.  The web servers do not need a floating IP assigned to them. (more…)