Tag Archives: Market Oriented Cloud

The Structure of the New IT Frontier: Part 2 – Market Oriented Computing

By Christian Vecchiola, Dexter Duncan, and Rajkumar Buyya

Cloud Computing’s first outcome is the delivery of an infrastructure model that is approaching commodity like prices and fast implementation times. The main adopters of the public cloud are start-ups, small companies, enterprise test-beds, non-critical applications and delivery of back-up resources. There is a high amount of innovation expected above this commodity layer, namely in platforms (platform as a service) area leading to what we call Market Oriented Cloud Computing (MOCC). Partial adoption of MOCC is happening now inside private clouds with full adoption expected once security, control, trust and “standards” are in place. The cloud qualities enterprises are adopting include reservation aware scheduling, ability to apply Quality of Service (QoS) policies with alternative offers, Virtualization, support of multi-tenant and multi-applications of same resources, ability to apply pricing and charge-back policies and more. This is driving high demand for platforms that help enterprises move into the cloud.

In the previous article we provided an overview of Cloud Computing. We covered the reference model and provided some real examples of IT companies operating in the field. In this article we dig into the details of the Infrastructure-as-a-Service (IaaS) solutions, which are the most popular outcome of this technology, and introduce a new phenomenon called Market Oriented Cloud Computing.

Enterprise CIOs focus to deliver return on investment and/or provide strategic advantage with applications and services that align to the business (and difficult for competitors to copy). Most CIOs have excess capacity and a huge investment in equipment. With an oversupply of servers and constant requests for more, they are looking to use their internal infrastructure more effectively. The recent global recession helped grow the hype around Cloud Computing as an alternative, and many are adopting the cloud ideas internally before buying whole-heartedly into the public cloud.

The commoditization of infrastructure through virtualization and super efficient management in hosted data centers lowers the cost of delivering the compute and storage needed to a price lower than the costs of purchasing and maintaining current IT infrastructures. A majority of enterprises have successfully installed some form of virtualization or plan to do so in a short time[1].  However, only about 2-5% have built an internal cloud, mostly just based on Virtual Machines (VM’s). Only a few large organizations have the man-power and budget to get the same economies of scale that hosting companies provide. Security, control, trust and lock-in concerns are temporary with a new wave of innovation coming that makes it easier to move into the cloud. While some start-ups, small companies and non-strategic compute business areas are moving to the cloud now, the smart ones are developing their IT transformation strategy to focus on innovation to take full advantage of the fast time to market that pay-per-use, elastic services deliver. This new focus on building demand-based private network clouds to work seamlessly with Public Clouds is a natural step we call Market Oriented Computing. Furthermore, as adoption of Cloud Computing becomes more prevalent a new area called Market Oriented Cloud Computing[2] begins to take shape.

Companies that help organizations align their internal infrastructure to move easily into the cloud are the new heroes and therefore the new winners.

Brief Overview of Infrastructure as a Service (IaaS) – offering compute and storage as a commodity

Infrastructure-as-a-Service (IaaS) solutions deliver customizable IT infrastructures on demand. This is the most popular form of delivering IT services introduced by Cloud Computing, and it is also the most consolidated one. Table 1 shows some of the biggest players in the IaaS sector. The range of offerings varies from bare metal servers to entire virtual infrastructures customized for web applications. Some vendors own the underlying physical infrastructure serviced to users while others rely on these providers and provide additional value such as system design and application packaging. The most common pricing strategy is pay-as-you-go but many vendors also offer monthly plans.

Vendor Service Type Product Pricing Model
Amazon Infrastructure EC2 [C], S3 [S], CloudFront [Cnt], … PAYG
Joyent Infrastructure Joyent Cloud [C] Monthly
Rackspace/Mosso Infrastructure Cloud Servers [C] Cloud Files [S], Cloud Sites [SD,C,S] PAYG, Monthly
ElasticHosts Infrastructure [C] PAYG, Plans
FlexiScale Infrastructure [C] PAYG
Rightscale Infrastructure [C] PAYG
Cloud Central (Australia) Infrastructure [C,SD] PAYG
Terremark Infrastructure vCloud Express [C], Enterprise Cloud [C] PAYG, Plan
Melbourne IT  (Australia) Infrastructure vCloud Express Beta[C] PAYG
Rejila (Australia) Infrastructure [C,SD] PAYG, Licensing
AT&T Infrastructure Synaptic Compute as a Service [C], Synaptic Storage as a Service [S], Synaptic Hosting as a Service [C,S] PAYG, Monthly
IBM Infrastructure/Platform IBM Smart Business Services [C,S,..] ND
VMWare Infrastructure vCloud Express [C] PAYG
Google Platform AppEngine [C] PAYG
Heroku Infrastructure/Platform [C,S] PAYG
Microsoft Platform, Infrastructure (M) Azure [C,S], Dynamic Data Center Toolkit [C,S] PAYG
Enomaly Infrastructure (M) [C] ND
Eucalyptus Infrastructure (M) [C] Free, Consulting
Elastra Infrastructure (M) [C, SD] ND
Skytap Infrastructure [C,S,SD] Monthly
Zimory Infrastructure (M) [C] ND
Akamai Infrastructure [Cnt] ND
Nirvanix Infrastructure [Cnt] PAYG

Table 1. Comparison table of the major IaaS vendors.

Legend:

C              :               Compute

S              :               Storage

Cnt          :               Content (CDN)

H             :               Hosting

SD            :               System Design and Application Packaging

(M)          :               The vendor does not provide any infrastructure support but only the management software

ND           :               Not Disclosed

PAYG      :               Pay As You Go

Amazon is definitely the most popular player in the field of Infrastructure on demand. The company launched Elastic Compute Cloud (EC2) three years ago and it is now the king of offering a pay-as-you-go elastic hosting service and a reference model for many other vendors providing compute on demand services. The entire IaaS offering of Amazon, which goes under the umbrella of Amazon Web Services, also includes Simple Storage Service (S3) providing virtual storage on demand that is combined with EC2 for an integrated solution and maximum savings. The list of Amazon customers ranges from very large enterprises to the end users that simply enter credit card details to instantly provision virtual servers. Another big player in the field is Joyent, which provides hosting, infrastructure, and application services for clients looking to run collaborative applications for their users. Joyent offers compute on demand and web application virtualization and helps to successfully scale social network websites like LinkedIn and Facebook, with nearly have 300 million users. On the same line, GoGrid, ElasticHosts, Rackspace, FlexiScale, RightScale, Melbourne IT and TerraMark provide bare metal virtual servers and storage space on demand.

Some vendors specialize by providing added value on top of the basic IaaS offerings. For example, RightScale eliminates vendor lock-in by letting the user choose the specific virtual infrastructure (Amazon, VMWare, etc) and software stack to compose their virtual environment (SkyTap). Other vendors, such as Cloud Central and Rejila, add specific features for composing your own virtual infrastructure and automating application packaging and deployment. Other solutions are completely specialized in providing a flexible and full featured virtual infrastructure design environment and rely on others to provide bare metal virtual servers or storage (Elastra, CohesiveFT).

With the exception of Google Inc, which offered a Cloud Computing model from inception, the big players of IT such as IBM, Microsoft, Sun, and AT&T made their move quite late and mostly concentrate their efforts in supporting service providers with infrastructure management software and vertically integrated service offerings.

Finally, if you want to build your own Cloud on your premises or elastically manage your datacenter, without leveraging integrated solutions such as those proposed by IBM and VMWare, virtual infrastructure management platforms like Enomaly Enterprise Cloud, Eucalyptus Enterprise Edition, or Zimory are your best choice.

This is just a selection of the plethora of vendors that offer compute and storage services on demand. Such services are the foundation for turning capital expense (CapEx) into an Operating Expense (OpEx) on corporate balance sheets and are called Infrastructure as a Service or IaaS. IaaS is fast approaching pricing models that look like commodity based pricing and the opportunity of exploiting Public Clouds to elastically shape your IT infrastructure is tempting. Rackspace offers compute time for less than 2¢ per hour with additional charges for bandwidth between 8¢ and 22¢ per GB/month. For comparison, Amazon has bandwidth rates between 10¢ and 17¢ per GB/month. Their EC2 compute service starts at 10¢ for a small Linux server with a slightly higher price for Windows. Both charge 15¢ per GB for storage with additional charges of 1¢ per request.

Most CIOs need to ensure that their private data center infrastructure evolves to integrate the new “commoditized” Public Cloud offerings. This allows them to maximize their existing investment and opens up opportunity for a future “unified design” where you easily move your data and share compute resources in a federated model either for purposes of managing peak load (cloud bursting), minimizing time and money (brokering) or as a disaster recovery solution. To make this happen, some key features of the Cloud, virtualization, provisioning on demand & Quality of Service (QoS) based workload management, are being integrated into privately owned infrastructure. This gives the dynamic elastic infrastructure and on-demand, self-serve, self-managed, internet enabled, and consumption based structure needed to take advantage of hybrid or inter-cloud offerings.

A Look at the Future: Market Oriented Cloud Computing

Where is the focus now?  What is Cloud 2.0 now that a commodity layer of infrastructure is underway? The window of innovation over the next few years is now clearly focused above this commodity layer. You are not going to make your enterprise hardware cheaper than the big boys operating in the IaaS space.  This means that the real place of innovation and growth is in Platform-as-a-Service (PaaS) and Software-as-a-Service (SaaS) playground.  Expect to see traditional infrastructure and virtualization companies playing aggressively in the Platform area through in-house development or acquisitions. In particular, there is a high amount of innovation beginning to occur above the infrastructure layer, namely in the PaaS area, leading to what we call Market Oriented Cloud Computing (MOCC).

Market Oriented Cloud Computing encompasses approaches and technologies enabling the trading of IT services, and their seamless integration into the existing infrastructure, according to service level agreements established to ensure the desired Quality of Service.

Time Frame Private Infrastructure Public Infrastructure Market Situation
2006 – 2010: Cloud Computing Thinking Formation Legacy Private Networks Some Cloud Computing Adoption Confusion, trust, security, control concerns, jurisdiction issues slow down early adoption
2010 – 2012:Partial Market Oriented Cloud Computing Adoption Cloud-enabled private infrastructures: provisioning on demand and virtualization. Rapid Cloud Computing Adoption Market Oriented Platforms (i.e. Manjrasoft) enter Market; Period of Innovation Begins
2013 onward:Full Market Oriented Cloud Computing Adoption Market Oriented Cloud Computing Blurs line between Private/Public Cloud Computing is Mainstream Security, control and trust issues overcome.

Table 2. Future evolution of the Cloud Computing Market.

Table 2 shows the expected evolution of the Cloud Computing Market into the adoption of market-based strategies that shape the IT infrastructure of tomorrow. Partial adoption of MOCC is happening now inside Private Clouds with full adoption expected once security, control, trust and “standards” are in place. While we do not expect 100% of the market to move to the Cloud in three years, the mainstream adoption of Cloud Computing is in-line with Gartner Hype Cycle (Figure 1). In the near-term, enterprises are “cloudifying” their infrastructure, which is a partial adoption of the longer term trend to Market Oriented Cloud Computing. The “Cloud Qualities” that enterprises are adding include many areas that allow them to add applications and demand without buying additional hardware for an overall high resource utilization. These qualities include reservation aware scheduling, ability to apply dynamic QoS policies, virtualization, support of multi-tenancy and multiple applications on the same resources, ability to apply pricing and charge-back policies and more.

Figure 1. Gartner technology hype cycle.

Market Oriented Cloud Computing: What More?

How does Market Oriented Cloud Computing differ from Cloud Computing? Is it really a step forward or just another buzzword used to add more confusion?

The Cloud Computing model already introduces on demand provisioning, consumption based subscriptions, and also promises QoS based delivery of IT services. However, at present, service providers have inflexible pricing, generally limited to flat rates or tariffs based on usage thresholds, and consumers are restricted to offerings from a single provider at a time. Also, many providers have proprietary interfaces to their services thus restricting the ability of consumers to swap one provider for another. For Cloud computing to reach a broad and seamless adoption, it is required that the services follow standard interfaces. This enables full commoditization and thus, would pave the way for the creation of a market infrastructure for trading in services.

What characterizes Market Oriented Cloud Computing is the realization of a virtual market place – Cloud Exchange – where IT services are traded and brokered dynamically. This only happens if enterprises seamlessly move from one provider to another, without conversion costs and in a completely dynamic manner. Organizations are building their internal Private Clouds to be similar to Public Clouds. This is the first step that enables the transparent integration of the publicly provisioned IT services with the private premises. What is missing is the availability of a market where desired services are published and then automatically bid by matching the requirements of customers and providers. Some are already moving in this direction: Amazon introduced the concept of “spot instances” that are dynamically offered by the provider according to their availability and bid by the customer. Their effective usage and consumption is then determined by the spot price established by Amazon and the maximum price provided by the customers.

Market Oriented Computing has the same characteristics as Cloud Computing; therefore it is a dynamically provisioned unified computing resource allowing you to manage software and data storage as on aggregate capacity resulting in “real-time” infrastructure across public and private infrastructures. Market Oriented Cloud Computing goes one step further by allowing spread into multiple public and hybrid environments dynamically composed by trading service.

The realization of above Cloud Exchange is technically possible today, but not probable given the lack of standards and overall immaturity of the market. As vendors jockey to put forward their standard, and as concerns on security and trust begin to disappear, enterprises will move to take advantage of the new frontier of commodity like prices and quick time to market. Moreover, the presence of a demand based market place represents an opportunity for enterprises to shape their infrastructure for dynamically reacting to workload spikes and cut maintenance costs. It also allows possibility to temporary lease some in-house capacity during low usage periods, thus better Return on Investment. The Cloud Exchange is a meeting point where these new opportunities are provided.

Realizing the Vision: A Platform for Market Oriented Cloud Computing

Figure 2 illustrates the key components that shape the future scenario of Cloud Computing. In this vision, the “market place” plays a fundamental role. The dynamic provisioning of services from different vendors increases the competition in the value offering, resulting in a more consistent effort in providing a high quality and more accessible service.. To achieve this, Cloud providers no longer deploy traditional system-centric resource management architectures that do not provide incentives to share their resources and regard all service requests with equal importance. Instead, market-oriented resource management is necessary to regulate the supply and demand of Cloud resources to achieve market equilibrium (where supply = demand), providing feedback in terms of economic incentives for both Cloud consumers and providers, and promoting QoS-based resource allocation mechanisms that differentiate service requests based on their utility. In addition, clients benefit from the “potential” cost reduction of providers, which leads to a more competitive market and thus lower prices. This is the role of the market place.


Figure 2: Global Cloud exchange and market infrastructure for trading services.

From the provider point of view a specific infrastructure is put in place to effectively take advantage of the demand based market place. Figure 3 shows a component based view of the infrastructure supporting MOCC.

  • Public Interface Access. These are a set of standard interfaces for delivering IT services to end users and publishing them in the market place. These interfaces identify the access points of each Cloud Service provider.
  • SLA[3]-based resource allocator and workload manager. The SLA Resource Allocator and Workload Manager are responsible for ensuring that IT services are delivered with the desired QoS. This layer is a fundamental component and includes different operations such as resource and application metering, billing, accounting and market based scheduling.
  • Virtualization Layer.  Virtual Machine technology allows workload isolation, server consolidation, multi-tenancy, fine grain tuning of allocated resources, and execution sandboxing. Moreover, virtual machine instances are started and stopped on-demand on a single physical machine to meet accepted service requests, hence providing maximum flexibility to configure various partitions of resources on the same physical machine to different specific requirements of service requests.
  • Physical Infrastructure. It provides the horse power required to execute the Cloud workload. IaaS providers maintain multiple data-center that are maintained and made accessible through virtual infrastructure management software, such as those presented previously (vCloud express, Dynamic Data Center Toolkit, and others).

Such architecture ensures that crucial business operations of companies are performed with confidence by meeting deadlines [4]. Critical QoS parameters that change over time, such as time, cost, reliability and trust/security, characterize the future Cloud Computing market and a flexible and open infrastructure is the way to go for realizing this vision.

Figure 3. High-level market-oriented Cloud architecture for Cloud services  providers.

The similar infrastructure and component stack is expected within the private premises of the enterprise. In order to seamlessly integrate Public Cloud resources, the internal IT organization follows the same resource management model found in public infrastructure, on a different scale. In addition, two distinctive features have to be considered:

  • Heterogeneity of resources. Private Clouds tend to be composed by different resources, such as clusters, data-centers, workstations, and possibly Computing Grids. These resources are either virtual or physical. This requires uniform access and way of leveraging these resources.
  • Dynamic provisioning. Public Clouds address the need of integrating additional resources into the existing infrastructure during peak loads. In a true market oriented offering these operations are not performed statically but are triggered by the constraints of the current workload. SLA aware schedulers identify the additional resources (storage, compute, or other) required to meet the QoS requirements and resources are obtained by means of a market mediated negotiation with available providers.

Figure 4 describes the general architecture of a Private Cloud augmented with market oriented capabilities.

Figure 4. High-level market-oriented Cloud architecture for Cloud services providers.

From a customer point of view, a Cloud based commercial offering for enterprises is expected to:

  • Support customer-driven service management based on customer profiles and requested service requirements
  • Define computational risk management tactics to identify, assess, and manage risks involved in the execution of applications with regards to service requirements and customer needs
  • Derive appropriate market-based resource management strategies that encompass both customer-driven service management and computational risk management to sustain SLA oriented resource allocation
  • Incorporate autonomic resource management models that effectively self-manage changes in service requirements to satisfy both new service demands and existing service obligations
  • Leverage VM technology to dynamically assign resource shares according to service requirements.

These requirements are most likely addressed by Platform-as-a-Service offerings rather than a pure IaaS. There is now a vacuum in the area of infrastructure and applications platforms that many vendors are rushing to fill. The Platform as a Service (PaaS) market is growing at 160% annual growth rate (according to IDC, Gartner, AMR and William Blair & Co) and expected to reach to just around USD $9 to 10 Billion in 2012. This is by far the highest growth area in the Cloud.

To understand this better, we put together “Cloud Quality” Characteristics needed for enterprises to Cloud-enable their infrastructure. The Market Oriented Cloud Platform delivers on the qualities by being flexible with ability to easily work in multiple programming and multiple run-time environments. A new framework race is now happening that allows enterprises to manage based on the new demand based commodity infrastructure. These frameworks need to make it easy to manage, provision, monitor, secure and change resources when needed or based on pre-determined service levels that match the applications.

There is a shift from today’s supply-driven “build to peak” to a demand-driven, service-oriented approach. This results in real-time IT infrastructure with little spare capacity, but also gives more freedom to focus on business strategies rather than maintenance and system engineering. A Market Oriented Platform allows easy abstraction of underlying hardware and provides an elastic architecture that provisions and de-provisions on demand based on QoS requirements.

It is important for the platform to be flexible, easily customizable, and extensible while being service oriented to provide unique SLA/QoS & Web Services management, security and dynamic provisioning. This includes the ability to remotely control, monitor and dynamically change single and groups of nodes, which is not only important to simplify the management, but also to identify and remove bottlenecks.

Many of the existing middleware platforms are proprietary and tied to their infrastructure or applications’ service such as Google’s App Engine[1] and SalesForce’s Force.com. Most of the non-proprietary ones are Java/Linux based, with a few that rely on .NET framework. Outside those mentioned above, other companies providing Platform as a Service are: 3Tera, Apprenda, DataSynapse, Manjrasoft and Univa UD.

Cloud Quality (CQ) Characteristic Market Oriented Cloud Platform
Easy to Deploy Write once and deploy in multiple run-time environments.
Pay as you Go Pricing/Accounting modules to allow you to price based on resource usage
Demand Based Dynamic Provisioning based on QoS
Multi-tenant Resource Sharing: ability to host multiple users and applications across same infrastructure
Scalability From the small local network to the data-center. Scalable services for handling increased workloads and potentially large infrastructures.
Workload Distribution Provide custom workload Distribution Algorithms
Failure Management Strong support for failover and content replication. VMs can be easily migrated from one node to other.
Flexibility Customizable Services based on needs of applications. Pluggable and extensible architectures for implementing the system infrastructure.
Elasticity Dynamic Provisioning to VM based on QoS from public and private resources.
Service Oriented Architecture Service-based approach for infrastructure, workload management, and application submission.
Easy to Manage Monitoring, Reservation, Meter and Charging features.
Self Managed Auto plug scheduler as required – dynamic provisioning of scheduler
Quality of Service (QoS) Extensible set of parameters controlling the scheduling of workloads. Ability of dynamically change the value of these parameters in order to meet the continuously changing business needs of the enterprise.
High Resource Usage Combination of Multi-tenant and Provisioning based on QoS results in high utilization rate

Table 3: Expected features for a Market Oriented Cloud Computing Platform.

Summary

Infrastructure-as-a-Service solutions constitute the most popular and consolidated approach for dynamically delivering IT services introduced by Cloud Computing. IaaS offerings commoditize infrastructure and hardware and allow enterprise to elastically reshape their IT infrastructure. While the essence of Cloud Computing is provisioning IT services on demand, and IaaS value propositions are considerable step towards this direction, the flexible, efficient, and profitable use of these is still far away. The market segment of infrastructure on demand is now mature and a solid base on top of which build additional services that will lead to the widespread adoption of Cloud Computing.

To make this happen, it is necessary to adopt a market oriented approach where IT services are traded, provisioned, and advertised in competitive and open environment. This is the vision proposed by Market Oriented Cloud Computing. In this article we have characterized the fundamental properties of such model and listed a set of requirements that service providers and service consumers (i.e. Enterprises) have to meet in order to realize this vision. Market Oriented Cloud Computing is the natural evolution of Cloud Computing and identifies a scenario where the virtual public infrastructure is seamlessly and dynamically integrated with the private premises.

To realize this vision, Platform-as-a-Service solutions will play a fundamental role. In the next article, we will illustrate how to leverage these solutions to provide a heterogeneous, dynamic, and market oriented environment for Cloud Computing.




[1] From Forrester 2009 survey of 2,600 decision-makers from small and large companies in the US and Europe. http://www.reuters.com/article/pressRelease/idUS126722+04-Mar-2009+BW20090304

[2] R. Buyya, C. S. Yeo, S. Venugopal, J. Broberg, and I. Brandic, Cloud Computing and Emerging IT Platforms: Vision, Hype, and Reality for Delivering Computing as the 5th Utility, Future Generation Computer Systems, Volume 25, Number 6, Pages: 599-616, ISSN: 0167-739X, Elsevier Science, Amsterdam, The Netherlands, June 2009.

[3] SLA: Service Level Agreement

[4] Rajkumar Buyya, Suraj Pandey, and Christian Vecchiola, Cloudbus Toolkit for Market-Oriented Cloud Computing, Proceeding of the 1st International Conference on Cloud Computing (CloudCom 2009, Springer, Germany), Beijing, China, December 1-4, 2009.

Other Links:

  1. For a list of the “Top 150 companies in Cloud Computing”, Check out this list from Virtualization Journal: http://virtualization.sys-con.com/node/770174
  2. Another list in Datamation covers “85 companies shaping the emerging cloud” :http://itmanagement.earthweb.com/features/article.php/12297_3835941_1/85-Cloud-Computing-Vendors-Shaping-the-Emerging-Cloud.htm

[1] http://aws.amazon.com/ec2/

[2] http://aws.amazon.com/s3/

[3] http://www.mosso.com/

[4] http://www.allthingsdistributed.com/2009/08/amazon_virtual_private_cloud.html

[5] http://code.google.com/appengine/docs/whatisgoogleappengine.html

[6] http://www.microsoft.com/azure/

[7] http://www.salesforce.com

[8] http://www.clarenz.com

Market Oriented Federated Computing

Based on paper written by Christian Vecchiolla

Edited by Dexter Duncan

A key vision often mentioned in the Microsoft Azure/Cloud announcements is the idea of a hybrid network which builds on-top of the “first wave” of cloud computing infrastructure available from Amazon, Microsoft, etc.   A hybrid network is one that connects the private (corporate) network with publicly available (cloud) infrastructure.   For example, Microsoft is designing tools such as Dynamic Data Center Toolkit to work in both hoster and Enterprise environments.    The hoster version is already available with enterprise version coming in March 2010.   The reference to the hybrid version is sometime “in the future”.       Similarly, the Azure announcements initially focused on applications available in the cloud with more recent announcements focused on middleware and tools bridging the gap between enterprise and the cloud.      Most of the projects announced will enter a beta phase in 2010 and include “Sydney”, AppFabric, Next Generation Application Directory and some updates to .NET framework.

Many enterprises have grown accustomed to building private data centers to meet peak demand and are in process of setting up Virtual Machine environments that help use more of the private data resources without having to buy new hardware.       Since public clouds also operate using Virtual Machines, it is not a far stretch to see Cloud Computing as an extension to the existing corporate strategy, especially if a VPN is set up to offer same level and type of security that is in the private network.   Amazon is the first one to publicly announce a VPN service as part of their cloud offering, but it should be easy to set up with any cloud vendor by using standard encrypted IP Sec VPN connections.     You just need to specify a private IP address block, work out subnet addresses and bridge private and public network together using VPN router.

The most significant benefit of Cloud computing is the elasticity of resources, services and applications, which is the ability to automatically scale out based on demand and users’ quality of service requests.      Having a VPN set-up with dynamic provisioning would allow you to do this.      Another alternative is to set up a broker between the private network and the cloud provider and to manage traffic/demand based on pre-defined security policies.    Highly sensitive information therefore remain on the private cloud, while lower priority data is processed on Pay-as-you-Go basis.    Building on top of this, you could also build the broker to offer other Quality of Service (QoS) related services such as ability to consume public resources based on pre-determined budget or deadline.    Offering QoS based consumption is called Market Oriented Computing.

Hybrid Cloud Implementation – A sample of Federated Computing

A Melbourne based start-up company recognized the need to address hybrid networks and Market Oriented Computing  and introduced a product that could easily work in private, public or hybrid network.     Their product called “Aneka” literally means “many into one” since their product allows you to manage many compute environments as one.       The power of provisioning resources from various IaaS providers, is able to seamlessly combine Private and Public Cloud resources, and deploy Aneka-enabled applications in these heterogeneous and hybrid environments.   There is no commonly agreed standard for provisioning virtual infrastructure and each IaaS provider tends to use its own specific interface.  To  achieve a seamless integration between Aneka and various IaaS providers, it is essential to design an open, flexible, and extensible architecture, which allows to easily plug custom implementations for interacting with new and emerging IaaS providers. The below provides an overall view of the architecture of the Aneka resource provisioning framework. This is composed of three major components:

  • Resource Provisioning Service: this is an Aneka specific service that implements the service interface, thus allowing the service to be integrated into and managed by the Aneka Container. This service is essentially a lightweight component that wraps the resource pool manager and integrates it into Aneka.
  • Resource Pool Manager: manages all the registered resource pools and decides how to allocate resources from those pools. The resource pool manager provides a uniform interface for requesting additional resources from any private or public provider, and hides the complexity of managing multiple pools to the Resource Provisioning Service.
  • Resource Pools: container of virtual resources that mostly come from the same resource provider. A resource pool is in charge of managing the virtual resources that contains and eventually releasing them when they are no longer in use. Since each vendor exposes its own specific interfaces, the resource pool encapsulates the specific implementation of the communication protocol required to interact with it, and provides the pool manager an unified interface for acquiring, terminating, and monitoring a virtual resources.

The Resource Provisioning Service takes requests primarily from the scheduling service and delegates those requests to the pool manager. According to the configured policy, the pool manager determines the pool instance that will be used to provision or release a given number of resources. It is then the responsibility of the selected resource pool to handle and forward the request to the resource provider. Once the requests are successfully processed, the requested number of virtual resources will either join or leave the Aneka Cloud.

The advantage of this architecture is that it is fairly simple and makes extending the current capability of the system straightforward. The provisioning service deals with all the aspects that are related to the internal infrastructure of Aneka and hides its implementation details to the pool manager. The pool manager focuses on the management capabilities of resource pools and keeps them separate from the other components of Aneka. Finally, the implementation of a single resource pool is completely independent from the other two components as long as the required interfaces are implemented. This architecture enables greater flexibility and simplicity for third-party integration. For example, introducing a new IaaS provider only requires implementing the resource pool component and configuring the pool manager to integrate it into the Aneka Container.

Applying these principles across between a private network and one or more cloud service providers is sometimes called Market Oriented Federated Computing.

Update on Australia Cloud Computing

I am working on some proposals in Australia involving Software as a Service which ideally needs a hosting partner to provide Infrastructure as a Service.

I have been pleasantly surprised in the recent release of pricing from Melbourne IT on their Beta Cloud Computing offering.     They are the first major hosting company to offer cloud computing after Rejila (owned by  Ultra Serve) opened their service a few months ago.    As an update to my previous blog/survey on Australia Cloud Computing, this article compares prices (roughly) of those that are currently offering pay-as-you-go infrastructure.       For comparison, I have included a quote from Macquarie Telecom on their monthly rate for a virtual machine.   The prices do not include support & set-up costs.     More detail is needed on options such as availability of VPN, security options and storage costs, which I will update at a later date once I get more information.

If enterprise user has bursty requirements (e.g. does not need lots of computers year-round) and experiences weeks or months where having lots of computer capacity improves their business, they should look at Cloud Computing.    The core value proposition of Cloud Computing  is fast provisioning times of 1-2 minutes (instead of days) and paying a per hour rate on CPU usage as opposed to monthly contracts.    Noting that below IP transport data rates are high for many applications like 3D Rendering, all players offer variety of options in delivering data – from highspeed 4M/40M links to dark fiber links at 10G.    I note that it is now possible to get dedicated 4M in/out links for less than $700 per month.

Cloud Central

Cloud Central is relatively new and offer small and large virtual machines using the same API as Rackspace (Xen based).     They are focused only on offering Cloud Computing infrastructure.    See Cloud Central website for up to date details.

Cloud Central offers hourly rates and a free 1 month trial as part of their beta program.

  • Single CPU (Xeon), 4 G RAM is $0.48/hour
  • Dual CPU, 8 G RAM is $0.96/hour  (approximately monthly equivalent : $700).
  • Plan to offer High Availability and large 8 CPU/box options in early 2010.
  • Input and output data rates around $1-1.5/GB.
  • Update:  64 GB of Storage is included.    Additional Storage is $0.30 per GB

Update:

Intel Nehalem 5500 series Xeon CPU’s is planned for commercial release timeframe.

Cloud Central is testing VPN solutions which consists “of a Vyatta VPN appliance that the customer can deploy into the cloud, then they just need to configure the VPN to suit their requirements.  This will support IPsec site to site VPN, L2TP VPN, and OpenVPN protocols.”

Rejila

I have a lot of respect for Ultra Serve and the folks behind Rejila.   They took the risk and were first on the market to offer a true, load balanced, true Cloud Computing solution.   Saying this, their prices now look expensive compared to Melbourne IT.     See Rejila website.

Rejila offers hourly rates with:

  • Single CPU (Intel Nehalem Core) and 2 G RAM at $0.40/hour
  • Dual CPU and 4 G RAM at $0.80/hour (monthly equivalent $576)
  • Input/Output rates at $3/GB (with discounts for above 300GB)

Rejila allows you to customise your server with up to 8 GB RAM and 4 CPUs.

Melbourne IT (prices include GST)

Melbourne IT is the latest to offer a pay-as-you-go service.    Their rates are reasonable, although still not as cheap as Amazon or Rackspace (both in USA).  See Melbourne IT website

  • Single CPU (Intel Nehalem) and 2 G RAM at $0.167/hour
  • Single CPU and 4 G RAM at $0.326/hour
  • Dual CPU and 4 G RAM at $0.378/hour (equiv.$272/month)
  • Input/Output rates at $1.047 per GB
  • $0.327 Storage per GB per month

Macquarie Telecom Offering

There are plenty of hosts cheaper than Macquarie, but I am using them as a reference point since they are often cited as being the biggest in Australia (with Melbourne IT being second.)   Macquarie do not offer anything below a monthly rental, but I believe the Tudehope brothers would be silly to not offer something so0n, especially if they want to maintain leadership.    The growth of their hosting business is the main reason they achieved profitability this year and they have the experience and margins to take some leadership in Cloud Computing area.    Here is an idea on the cost (not including the data transfer/storage cost):

They charge $1600/month for single VM for development environment and $800 per month per VM for production.   (VM cpu equivalent is 1 Nehalem Core at 3GHz and 3 to 4G RAM).    They have cheaper options with blade servers or other large offering (16 cpu/box) amounting to less than $200/cpu, but customer has to sign 36 month contract.

Bigger Clouds are Coming! Hello Market Oriented Computing

The commodity layer of Cloud Computing is rapidly maturing, leaving room for the next wave of innovation. Market Oriented Infrastructure, Platforms and Software are demand based aspects that will drive growth above the commodity (platform) layer!  Cloud Nerve Network is the place to read about Market Oriented Cloud Computing.    Stay tuned for more Posts on Market Oriented Computing!

Paper on Market Oriented Cloud Computing

For a taste of some of the trends in Cloud Computing, have a look at this paper:

http://www.buyya.com/papers/Cloudbus-Keynote2009.pdf

Also, related paper on Market Oriented Cloud Computing published in Future Generation Computer Systems:

http://www.gridbus.org/papers/Cloud-FGCS2009.pdf