An ISAS Presentation on

CLOUD COMPUTING
ACKNOWLEDGEMENT
We are thankful to NIIT for providing us such a platform to
prove ourselves and show our potential. We heartily show
our gratitude towards Mr. Khownish Chatterjee – our
respected faculty who guided us with the candle of
knowledge through the darkness of ignorance.
OVERVIEW
INTRODUCTION
 Internet based computing working like a electric grid.
 Can be used as a metaphor for Internet.
 You don’t need a software or a server to use them.
 Uses the internet and central remote servers.
 It is a byproduct and consequence of the ease-of-access
to remote computing sites provided by the Internet.
 CONCEPT
Cloud computing is broken down into three
segments: "applications," "platforms," and
"infrastructure.“
• Concept generally incorporates combinations of
the following
1. Infrastructure as a service (IaaS)
2. Platform as a service (PaaS)
3. Software as a service(SaaS)
• Companies with large batch-oriented tasks can
get results as quickly as their programs can
scale.
• The infrastructure is shared. 
• The services are accessed on demand in units
that vary by service. 
HISTORY
 The underlying concept of cloud computing dates back to
1960s, when John McCarthy opined that "computation
may someday be organized as a public utility".
 The actual term "cloud" borrows from telephony in that
telecommunications companies, who until the 1990s
primarily offered dedicated point-to-point data circuits,
began offering Virtual Private Network (VPN) services
giving much lower cost.
 Amazon played a key role in the development of cloud
computing by modernizing their data centers after the
dot-com bubble, which, like most computer networks,
were using as little as 10% of their capacity.
HISTORY
 Amazon started providing access to their systems through Amazon
Web Service (AWS) on a utility computing basis in 2006.
 In 2007, Google, IBM, and a number of universities embarked on a
large scale cloud computing research project. In early 2008,
Eucalyptus became the first open source AWS API compatible
platform for deploying private clouds.
 March of 2010, Microsoft's CEO, Steve Ballmer, made his strongest
statement of betting the company's future in the cloud by
proclaiming "For the cloud, we're all in" and further stating "About
75 percent of our folks are doing entirely cloud based or entirely
cloud inspired, a year from now that will be 90 percent."
ROLE IN SERVICE ORIENTED ARCHITECTURE
FEATURES

 Agility.
 Cost
 Reliability
 Scalability
 security
FEATURES CONTD.
 Location dependency
 Multi-tenancy

1. Centralization

2. Peak load capacity

3. Utilization and Efficiency.

 Maintenance
 Metering
APPLICATION AREAS
APPLICATION AREAS
 Clients would be able to access their applications
and data from anywhere at any time.
 End user to cloud – An end user can get easy access
to the cloud applications.
 It could bring hardware costs down. You wouldn't
need to buy the fastest memory with the
most memory, because the cloud system would take
care of those needs for you.
APPLICATION AREAS
 A lot of IT organization can’t afford to invest in
supercomputer-class infrastructure. Yet, the
business could benefit from access to some pretty
compute-intensive analytic applications.
 Backup and recovery.
 Cloud computing systems give these organizations
company-wide access to computer applications.
Instead, the company could pay a metered fee to a
cloud computing company.
DEPLOYMENT MODELS
TYPES OF CLOUDS
1. Public cloud - Resources are dynamically
provisioned on a fine-grained.
2. Community Cloud - Established where several
organizations have similar requirements and seek
to share infrastructure.
3. Hybrid Cloud - Environment consisting of
multiple internal and/or external providers "will
be typical for most enterprises".
TYPES OF CLOUDS CONTD.
4. Private Cloud - The idea
was based upon direct
comparison with other
industries (e.g. the
electricity industry) and
the extensive use of hybrid
supply models to balance
and mitigate risks.
ARCHITECTURE
 Typically involves multiple cloud
components communicating with each other.
 The two most significant components of
cloud computing architecture are known as
the front end and the back end.
 The front end is the part seen by the client,
i.e. the computer user. This includes the
client’s network (or computer) and the
applications used to access the cloud via a
user interface such as Internet Explorer.
 The back end of the cloud computing
architecture is the ‘cloud’ itself, comprising
various computers, servers and data storage
devices.
LAYER
 Client - consists of computer hardware
and/or computer software.
 Applications- Cloud application services
or "Software as a Service (SaaS)" deliver
software as a service over the Internet.
1. Network-based access.
2. Managed from central locations.
3. Closer to a one-to-many model.
4. Centralized feature updating.
 Platform - Cloud platform services or
"Platform as a Service (PaaS)" deliver a
computing platform and/or solution
stack as a service
LAYERS CONTD.
 Infrastructure- Cloud infrastructure services or
"Infrastructure as a Service (IaaS)" delivers
computer infrastructure, typically a platform
virtualization environment as a service.
 Server - The servers layer consists of computer
hardware and/or computer software products
that are specifically designed for the delivery of
cloud services.
DIFFERENT ASPECTS OF CLOUD COMPUTING
COMMERCIAL CLOUD
RESEARCH
 Universities, vendors and government organizations are
investing in research.
  IBM/Google Academic Cloud Computing Initiative (ACCI).
 July 2008, HP, Intel Corporation and Yahoo! announced the
creation of a global, multi-data center, open source test bed
 April 2009, the National Science Foundation joined the
ACCI.
 July 2010, HP Labs India announced a new cloud-based
technology designed to simplify taking content and making
it mobile-enabled
INTERCLOUD
 The Intercloud is an interconnected global "cloud of clouds“.
 The term was first used in the context of cloud computing in
2007.
 Based on the key concept that each single cloud does not
have infinite physical resources.
 Raises many challenges concerning cloud federation,
security, interoperability, QoS, monitoring and billing.
 Combined many computer utilities together was originally
described by Douglas Parkhill.
STORAGE
 Data is stored on multiple virtual servers.
 Hosting companies operate large data centers.
 The data center operators, in the background, virtualizes the
resources according to the requirements of the customer
and expose them as virtual servers.

Storage Facility
CLOUD VERSUS GRID
 Cloud computing
 Full private cluster is
provisioned.
 Individual user can only
get a tiny fraction of the
total resource pool.
 No support for cloud
federation except
through the client
interface.
 Opaque with respect to
resources.
These differences mandate different architectures for each.
 Grid computing
 Built so that individual
users can get most, if not
all of the resources in a
single request.
 Middleware approach
takes federation as a first
principle.
 Resources are exposed,
often as bare metal.
PROS AND CONS OF CLOUD COMPUTING
 Governance
 Security, Privacy and control
 SLA guarantees
 Ownership and control
 Compliance and auditing
 Sarbanes and Oxley Act
 Reliability
 Good service provider with 99.999% availability
 Cloud independence – Vendor locking.
 Cloud provider goes out of business
 Data Security
 Cloud locking and Loss of control.
 Plan for moving data along with Cloud provider
 Cost.
 Simplicity.
 Tools.
 Controls on sensitive data.
 Out of business
 Big and small
 Scalability and cost outweigh reliability for small businesses
 Big businesses may have a problem
MICROSOFT AND AMAZON FACE CHALLENGES
 Globus/Nimbus
 Client-side cloud-computing interface to Globus-enabled TeraPort cluster at U of C
 Based on GT4 and the Globus Virtual Workspace Service
 Shares upsides and downsides of Globus-based grid technologies
 Enomalism (now called ECP)
 Start-up company distributing open source
 REST APIs
 Reservoir
 European open cloud project
 Many layers of cloud services and tools
 Ambitious and wide-reaching but not yet accessible as an implementation
 Eucalyptus
 Cloud Computing on Clusters
 Amazon Web Services compatible
 Supports kvm and Xen
 Open Nebulous

 Joyent
 Based on Java Script and Git
CLOUD INFRASTRUCTURE

Storage Networking Coolant

Storage Network Cables Control Center

CLOUD INFRASTRUCTURE

Network operations Physical Infrastructure Physical Security

center

Power infrastructure Network Cabling Fire safety

WHY CLOUD COMPUTING?
 Changed the face of IT.
 Gives advantage to major companies.
 Practical and Effective characteristics.
 Introduction to Hybrid approach.
CLOUD COMPUTING AND SOA.
 Complementary to each other.
 Can be pursued independently.
 Cannot replace each other.
 Budget issues.
 Platform and scalability issues.
WHAT IS CLOUD?
CHALLENGES IN IMPLEMENTATION
THE OBSTACLES
 Business Continuity and Service Availability.
 Data Lock-In.
 Data Confidentiality/Auditability.
 Data Transfer Bottlenecks.
 Performance Unpredictability.
THE OBSTACLES CONTD.
 Scalable Storage.
 Bugs in Large-Scale Distributed Systems.
 Scaling Quickly.
 Reputation Fate Sharing.
 Software Licensing.
CONCLUSION
 We predict cloud computing will grow.
 Applications software needs to both scale down
rapidly as well as scale up.
 Infrastructure software must be aware that it is no
longer running on bare metal.
 Hardware systems should be designed at the scale
of a container (at least a dozen racks), which will be
the minimum purchase size.
CREDITS
 Indraneel Banik Majumdar
 Cessna Bhattacharya
 Probuddho Ganguly
 Daipayan Banerjee
 Tanusree Majumdar
 Md. Faizan Ahmed
 Sandip Dutta
 Biplab dey
THANK YOU VIEWING OUR PRESENTATION
GRID COMPUTING
 Share Computers and data
 Evolved to harness inexpensive computers in Data center to solve variety of problems

 Harness power of loosely coupled computers to solve a technical or mathematical problem

 Used in commercial applications for drug discovery, economic forecasting, seismic analysis and

back-office
 Small to big

 Can be confined to a corporation

 Large public collaboration across many companies and networks

 Most grid solutions are built on

 Computer Agents

 Resource Manager

 Scheduler

 Compute grids

 Batch up jobs

 Submit the job to the scheduler, specifying requirements and SLA(specs) required for running

the job
 Scheduler matches specs with available resources and schedules the job to be run

 Farms could be as large as 10K cpus

 Most financial firms has grids like this back

 Grids lack automation, agility, simplicity and SLA guarantees