Understanding the cloud computing stack
Introduction
Key characteristics
At Glance
Standardization, Migration &Adaptation
Service models
Deployment models
Network as a Service
Software as a Service (SaaS).
Platform as a Service (PaaS).
Infrastructure as a Service (IaaS).
Communications as a Service (CaaS)
Data as a Service - DaaS
Benefits & Challenges
Security Risks & Challenges
Cloud Vendors
3. Introduction
Cloud computing
Is a type of Internet-based computing that
provides shared computer processing resources
and data to computers and other devices on
demand.
on-demand access to a shared pool of
configurable computing resources (e.g.,
computer networks, servers, storage,
applications and services),which can be rapidly
provisioned and released with minimal
management effort.
Cloud computing and storage solutions provide
users and enterprises with various capabilities
to store and process their data in third-
party data centers that may be located far from
the user–ranging in distance from across a city
to across the world.
.
4. Key characteristics
Cloud computing relies on sharing of resources. Cloud computing allows companies to
avoid up-front infrastructure costs (e.g., purchasing servers). As well, it enables
organizations to focus on their core businesses instead of spending time and money on
computer infrastructure. Cloud providers typically use a "pay as you go" model.
Cloud computing adopts concepts from Service-oriented Architecture (SOA) that can help
the user break these problems into services that can be integrated to provide a solution.
Cloud computing provides all of its resources as services, and makes use of the well-
established standards and best practices gained in the domain of SOA to allow global and
easy access to cloud services in a standardized way.
5. Key characteristics
Cloud computing exhibits the following key characteristics:
• Agility for organizations increase users, flexibility with re-provisioning, adding, or
expanding infrastructure.
• Cost reductions As public-cloud delivery model converts capital expenditures (e.g.,
buying servers) to operational expenditure. less in-house IT skills are required for
implementation .
• Device and location independence[enable users to access systems using a web
browser regardless of their location or what device they use .
• Maintenance of cloud computing applications is easier, because they do not need to
be installed on each user's computer .
• Multitenancy enables sharing of resources and costs across a large pool of users :
1. centralization of infrastructure in locations with lower costs (such as real estate,
electricity, etc.)
2. peak-load capacity increases (users need not engineer and pay for the
resources and equipment)
3. utilisation and efficiency
6. Key characteristics
• Performance is monitored by IT experts from the service provider, and consistent
and loosely coupled architectures .
• Productivity may be increased when multiple users can work on the same data
simultaneously.
• Reliability improves with the use of multiple redundant sites, which makes well-
designed cloud computing suitable for business continuity and disaster recovery.
• Scalability and elasticity via dynamic ("on-demand") provisioning of resources on a
fine-grained, self-service basis in near real-time.
• Security can improve due to centralization of data, increased security-focused
resources. Security is often as good as or better than other traditional systems
9. Standardization, Migration &Adaptation
Standardization holds a critical role in creating mass adoption of cloud computing.
1. Interoperability and vendor lock-in prevention
2. SLA definition
3. Monitoring definition
4. Security definition
5. Auditing definition
Migration and Adaptation
1. IT are the business hart, don't cloud too fast
2. Pay consideration to security and reliability
3. Move to the cloud in steps
4. Consider TCO
5. Local Telcos might provide cloud services with support
10. Service models
Software as a Service (SaaS).
The capability provided to the consumer is to use the provider’s applications running on a
cloud infrastructure. The applications are accessible from various client devices through either
a thin client interface, such as a web browser (e.g., web-based email), or a program interface.
The consumer does not manage or control the underlying cloud infrastructure including
network, servers, operating systems, storage, or even individual application capabilities, with
the possible exception of limited user-specific application configuration settings.
The NIST's definition of cloud computing defines
the service models as follows
1. Software as a Service (SaaS).
2. Platform as a Service (PaaS).
3. Infrastructure as a Service (IaaS).
11. Service models
Platform as a Service (PaaS).
The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-
created or acquired applications created using programming languages, libraries, services, and
tools supported by the provider. The consumer does not manage or control the underlying
cloud infrastructure including network, servers, operating systems, or storage, but has control
over the deployed applications and possibly configuration settings for the application-hosting
environment.
Infrastructure as a Service (IaaS).
The capability provided to the consumer is to provision processing, storage, networks, and
other fundamental computing resources where the consumer is able to deploy and run
arbitrary software, which can include operating systems and applications. The consumer does
not manage or control the underlying cloud infrastructure but has control over operating
systems, storage, and deployed applications; and possibly limited control of select networking
components (e.g., host firewalls).
12. Deployment models
NIST definition outlines four different deployment models:
Private cloud — Private clouds are provisioned and used by a single organization. Typically, they are
built and operated by that organization as well, but that need not be the case.
Examples are private clouds based on VMware or OpenStack, built by individual enterprises.
13. Deployment models
Public cloud — Public clouds are owned and operated by large external providers and deliver
service to all comers. Examples are Amazon Web Services EC2 and Google AppEngine.
Hybrid cloud — Of course, it’s possible to build a cloud environment that spans each of these
various models. Each piece of a hybrid cloud can be owned and operated by a different entity with
management software providing integration across the environment.
Community cloud — Community clouds are used by
a small set of known consumers who all share similar
requirements (performance, security, cost, etc.).
Typically, these consumers are drawn from the same
industry vertical (e.g., financial services), although this
need not be the case. Examples are the NYSE Capital
Markets Community Platform and Amazon’s GovCloud.
14. Network as a Service
Network as a service (NaaS) describes services for network transport connectivity.
NaaS involves the optimization of resource allocations by considering network and computing
resources as a unified whole.Includes the provision of a virtual network service by the owners
of the network infrastructure to a third party.Often this includes network virtualization using a
protocol such as OpenFlow
Some service models are
Virtual Private Network (VPN): Extends a private network and the resources contained
in the network across networks like the public Internet. It enables a host computer to
send and receive data across shared or public networks as if it were a private network
with the functionality and policies of the private network.
Bandwidth on demand (BoD): Technique by which network capacity is assigned based
on requirements between different nodes or users. Under this model link rates can be
dynamically adapted to the traffic demands of the nodes connected to the link
15. Network as a Service
Mobile network virtualization: Model in which a telecommunications manufacturer or
independent network operator builds and operates a network (wireless, or transport
connectivity) and sells its communication access capabilities to third parties (commonly
mobile phone operators) charging by capacity utilization.
A mobile virtual network operator (MVNO), is a mobile communications services
provider that does not own the radio spectrum or wireless network infrastructure over
which it provides services. Commonly a MVNO offers its communication services using
the network infrastructure of an established mobile network operator.
16. Communications as a Service (CaaS)
Communications as a Service (CaaS)
Traditionally, enterprises have acquired and deployed their own communications
infrastructure. This was by far the most economical approach, as enterprises could
deploy their own PBX switches and avoid the cost of individual phone lines for each
employee. With the advent of IP and virtualization of the data center, the
economics have shifted back in favour of a service provider model. The SP invests
in a virtualized data centre, negating the need for the enterprise to do so, and
offers a more flexible consumption model.
Outsourced enterprise communications solution where a third party vendor
(known as CaaS vendor) is responsible for the management of hardware and
software required for delivering Voice over IP (Voice as a Service), instant
messaging, and video conferencing applications using fixed and mobile devices.
• Example: IP-Centrex, a remote PBX
17. Data as a Service - DaaS
Data as a service (or DaaS) is a cousin of software as a service (SaaS). Like all
members of the "as a service" (aaS) family, DaaS builds on the concept that the
product (data in this case) can be provided on demand to the user regardless of
geographic or organizational separation of provider and consumer.
Additionally, the emergence of service-oriented architecture (SOA) has also rendered
the actual platform on which the data resides irrelevant. This development has
enabled the emergence of the relatively new concept of DaaS.
A software as a service or web service offering that provides customers with access
and analytics around a set of proprietary set of aggregated data.
Example - Salary.com
collects user data by offering individuals the ability to benchmark their compensation
levels against others. Sell anonomized data to companies (HR managers) for hiring and
compensation related usage.
18. Data as a Service - DaaS
Benefits
Data as a service brings the notion that data quality can happen in a centralized place,
cleansing and enriching data and offering it to different systems, applications or users,
irrespective of where they were in the organization or on the network.[
As such, data-as-a-service solutions provide the following advantages:
1. Agility
2. Cost-effectiveness
3. Data quality
Pricing models
1. Volume-based model
2. Data type-based model
Criticism- The drawbacks of data as a service are generally similar to those associated
with any type of cloud computing, such as the reliance of the customer on the service
provider's ability to avoid server downtime. Specific to the DaaS model, a common
criticism is that when compared to traditional data delivery.
19. Benefits & Challenges
Benefits Challenges
SaaS •Speed
•Reduced up-front cost,
•Transfer of some/all support
•Elimination of licensing risk
•Elimination of version
compatibility
•Reduced hardware footprint
•Extension of the security model
•Governance and billing obligations
management
•Synchronization of client
•Integrated end-user support
•Scalability
PaaS •Pay-as-you-go for
developmenttest, and production
environments
•Enables developers to focus on
application code
•Instant global platform
•Inherent scalability
•Simplified deployment model
•Governance
•Tie-in to the vendor
•Extension of the security model
• Connectivity
•3rd party SLA’s
20. Benefits & Challenges
Benefits Challenges
IaaS •Systems managed by SLA should
equate to fewer breaches
•Higher return on assets through
higher utilization
•Reduced cost driven by
• Less hardware
• Less floor space
•Lower power consumption
•Higher level of automation
from fewer administrators
•Able to match consumption to
demand
•Portability of applications
•Maturity of systems management
tools
•Integration across Cloud boundary
•Extension of internal security models
21. Security Risks & Challenges
Security Risks & Challenges
Conflicts with international privacy laws,
Data ownership
Service guarantees
Securing virtual machines
Massive outages
Encryption needs & Standards
Storing sensitive & personal information in clouds
Contingency planning / disaster recovery for clouds
22. Cloud Vendors
• The Public Cloud Vendors
▫ Amazon
▫ Google
▫ Microsoft
▫ Salesforce.com
• Private Cloud vendors (Data Centers)
▫ IBM
▫ Vmware
▫ Sun/Oracle
▫ 3Tera
Infrastructure Clouds
• Private
▫ 3Tera, IBM, Vmware, Eucalyptus
• Public
▫ Amazon, Rackspace, Gogrid, Joyent,
Terramark
Storage Based Clouds
• EMC (Mozy)
• Nirvanix
• Amazon S3
• RackSpace Mosso Cloud Files