What is Cloud computing and IaaS?

Cloud computing is one of the most hyped paradigm shifts in computing in recent years. Many definitions of cloud computing exist, but they boil down to these criteria:

  • Use of shared resources – Instead of providing each application with a fixed amount of processing power and storage, cloud computing provides applications with resources from a shared pool. This is typically done using virtualization technology.
  • On demand use – A cloud is able to quickly scale up and down in term of resources. When temporarily more processing power or storage is needed, for instance because of a marketing campaign, the cloud can scale very quickly to the demand. When resource demand goes down, the cloud resources can scale down as well.
  • Pay per use – In a cloud environment actual usage of resources is billed. There are no capital expenses, only operational expenses. This in contrast with the investments needed to build a traditional datacenter.
  • Customer self-service – Because of optimal automation minimal systems management effort is needed to deploy systems or applications in a cloud environment. In most cases, end uses can deploy, start and stop systems or applications themselves.

It is important to realize that cloud computing is not about technology, it’s a business model. It enables organizations to cut cost while at the same time focusing on their primary business – they should run a business instead of a mail server.

Be aware that when using an cloud based solutions, the Internet connection becomes a Single Point of Failure. Internet availability and performance becomes critical and a redundant connection is therefore crucial.

The cloud model

Cloud computing can be divided into three service models and three deployment models, as shown in the next figure.

2012-11/cloud-model.jpg

Figure: Cloud computing

Deployment models

  • A public cloud deployment model is what most people mean by cloud computing. A public cloud is delivered by a cloud service provider (CSP), is accessible through the Internet, and available to the general public. Because of the typical large customer base public clouds largely benefit from economies of scale.
  • A private cloud is operated solely for a single organization, whether managed internally or by a third-party and hosted internally or externally. It extensively uses virtualization and standardization to bring down systems management cost and staff. As a rule of thumb, a private cloud is cost effective when more than 300 servers are hosted.
  • In a hybrid cloud deployment, one part of a service or application is provided by a public cloud, while another part is provided by a private cloud. This enables putting generic services (like email servers) in the public cloud while hosting specialized services (like a business specific application) in the private cloud. Hybrid clouds provide the flexibility of in house applications with the fault tolerance and scalability of public cloud based services.

Service models

  • Software-as-a-Service (SaaS) delivers full applications, that need little or no configuration. Examples are Hotmail, Linked-in, IBM Lotus Live, Facebook, Yammer, Twitter, Google Apps, and Salesforce.com.
  • Platform-as-a-Service (PaaS) delivers a scalable, high available, and open programming platform that can be used to build bespoke applications upon. Examples are Microsoft Azure and Google App Engine.
  • Infrastructure-as-a-Service (IaaS) delivers (virtual) servers, networking, and storage. Examples are Amazon Elastic Cloud (EC2), Terramark, and Rackspace.

Infrastructure as a Service (IaaS)

Infrastructure as a Service only provides servers (typically virtual machines), storage, networking and the systems management tools to manage these. In order to use IaaS, users must create and start a new server, and then install an operating system and their applications.

Since the cloud provider only provides basic services, like billing and monitoring, the user is responsible for patching and maintaining the operating systems and application software.

The main advantage of IaaS is that organizations don’t have to invest in hardware and a datacenter, and they only pay what they use. They still need their own system administrators though.

Be aware that not all operating systems and applications can be used in a IaaS cloud; many software licenses prohibit the use of a fully scalable, virtual environment like IaaS, where it is impossible to know in advance on which machines the software will run.


This entry was posted on Sunday 23 December 2012

Earlier articles

Infrastructure as code

My Book

DevOps for infrastructure

Infrastructure as a Service (IaaS)

(Hyper) Converged Infrastructure

Object storage

Software Defined Networking (SDN) and Network Function Virtualization (NFV)

Software Defined Storage (SDS)

What's the point of using Docker containers?

Identity and Access Management

Using user profiles to determine infrastructure load

Public wireless networks

Supercomputer architecture

Desktop virtualization

Stakeholder management

x86 platform architecture

Midrange systems architecture

Mainframe Architecture

Software Defined Data Center - SDDC

The Virtualization Model

What are concurrent users?

Performance and availability monitoring in levels

UX/UI has no business rules

Technical debt: a time related issue

Solution shaping workshops

Architecture life cycle

Project managers and architects

Using ArchiMate for describing infrastructures

Kruchten’s 4+1 views for solution architecture

The SEI stack of solution architecture frameworks

TOGAF and infrastructure architecture

The Zachman framework

An introduction to architecture frameworks

How to handle a Distributed Denial of Service (DDoS) attack

Architecture Principles

Views and viewpoints explained

Stakeholders and their concerns

Skills of a solution architect architect

Solution architects versus enterprise architects

Definition of IT Architecture

What is Big Data?

How to make your IT "Greener"

What is Cloud computing and IaaS?

Purchasing of IT infrastructure technologies and services

IDS/IPS systems

IP Protocol (IPv4) classes and subnets

Infrastructure Architecture - Course materials

Introduction to Bring Your Own Device (BYOD)

IT Infrastructure Architecture model

Fire prevention in the datacenter

Where to build your datacenter

Availability - Fall-back, hot site, warm site

Reliabilty of infrastructure components

Human factors in availability of systems

Business Continuity Management (BCM) and Disaster Recovery Plan (DRP)

Performance - Design for use

Performance concepts - Load balancing

Performance concepts - Scaling

Performance concept - Caching

Perceived performance

Ethical hacking

Computer crime

Introduction to Cryptography

Introduction to Risk management

The history of UNIX and Linux

The history of Microsoft Windows

The history of Novell NetWare

The history of operating systems - MS-DOS

The history of Storage

The history of Networking

The first computers

History of servers

Tips for getting your ITAC certificate

Studying TOGAF

Is your data safe in the cloud?

Proof of concept

Who needs a consistent backup?

Measuring Enterprise Architecture Maturity

Human factors in security

Master Certified IT Architect

ITAC certification

Open group ITAC /Open CA Certification

Human factors in security

Google outage

SAS 70

TOGAF 9 - What's new?

DYA: Development without architecture

Spam is big business

Why IT projects fail

Power and cooling

Let system administrators participate in projects

The 7 Habits of Highly Effective People

Archimate

A meeting with John Zachman

ITAC - IT Architect certification

Personal Information is Personal Property

The Irresistible Forces Meet the Movable Objects

Hardeningscheck and hack testing for new servers

Knowledge management

Information Lifecycle Management - What is ILM

LEAP: The Redmond trip

LEAP: The last Dutch masterclasses

What do system administrators do?

Is software ever finished?

SCADA systems

LEAP - Halfway through the Dutch masterclasses

Securing data: The Castle versus the Tank

Non-functional requirements

LEAP - Microsoft Lead Enterprise Architect Program

Reasons for making backups

Log analysis - Use your logging information

Archivering data - more than backup

Patterns in IT architecture

Layers in IT security

High performance clusters and grids

Zachman architecture model

High Availability clusters

Monitoring by system administrators

What is VMS?

IT Architecture certifications

Storage Area Networks (SAN)

Documentation for system administrators

Rootkits

Presentations: PowerPoint sheets are not enough

99,999% availability

Linux certification: RHCE and LPI

IT Infrastructure model

Sjaak Laan


Recommended links

Ruth Malan
Gaudi site
Esther Barthel's site on virtualization
Eltjo Poort's site on architecture


Feeds

 
XML: RSS Feed 
XML: Atom Feed 


Disclaimer

The postings on this site are my opinions and do not necessarily represent CGI’s strategies, views or opinions.

 

Copyright Sjaak Laan