Cloud Computing: Computer Science & Engineering Mohit Gupta (1364510006)
Cloud Computing: Computer Science & Engineering Mohit Gupta (1364510006)
on
CLOUD COMPUTING
A Seminar report Submitted in Partial Fulfillment of the Requirements
for the Degree of
BACHELOR OF TECHNOLOGY
in
MOHIT GUPTA
[1364510006]
In
CERTIFICATE
This is to certify that Seminar Report entitled CLOUD COMPUTING is a bonafide
record of the work done by Mr. MOHIT GUPTA, 1364510006, in partial fulfillment of the
requirement for the award of degree B.Tech in Computer Science & Engineering to Ideal
Institute of Management and Technology, Ghaziabad, Dr. A.P.J Abdul Kalam Technical
University, Lucknow is a record of the candidate own work carried out by him under my
supervision.
Date:
Signature of Coordinator
Signature of Supervisor
Signature of HOD
Abstract
Cloud computing describes computation, software, data access, and storage
services that do not require end-user knowledge of the physical location and
configuration of the system that delivers the services. Parallels to this concept can be
drawn with the electricity grid where end-users consume power resources without any
necessary understanding of the component devices in the grid required to provide said
service. Cloud computing is a natural evolution of the widespread adoption of
virtualization, service-oriented architecture, autonomic and utility computing. Details are
abstracted from end-users, who no longer have need for expertise in, or control over, the
technology infrastructure "in the cloud" that supports them. Cloud computing describes a
new supplement, consumption, and delivery model for IT services based on Internet
protocols, and it typically involves provisioning of dynamically scalable and often
virtualized resources. It is a byproduct and consequence of the ease-of-access to remote
computing sites provided by the Internet. This frequently takes the form of web-based
tools or applications that users can access and use through a web browser as if it was a
program installed locally on their own computer.
TABLE CONTENTS
S. NO.
CHAPTER
1.
Chapter 1: Introduction
1.1
1.2
2.
3.
1.2.1
1.2.2
1.2.3
1.2.4
Chapter 2: Literature Survey
2.1
2.2
2.2
2.3
2.4
PAGE NO.
Cloud Computing
Concept of cloud Computing
05
06
Comparison
Implementation
Economics
Companies
07
07
07
08
11
11
12
13
13
14
History
Political Issues
Legal Issues
Security Issues
Risk mitigation
Chapter 3: Discussion
15
3.1
3.2
3.2.1
3.2.2
3.2.3
3.2.3
3.2.5
3.2.6
3.2.7
3.3
Key Characteristics
Component
Cloud computing Components
Application
Client
Infrastructure
Platform
Service
Storage
Architecture
15
16
16
17
17
18
18
18
19
19
3.4
3.4.1
3.4.2
3.4.3
Types
Public Cloud
Private Cloud
Hybrid Cloud
Roles
Provider
Vendor
User
Standards
Case study
Product & Service
Cloud(Operating System)
Browse & Operating System
Reception
20
21
21
21
22
22
23
23
23
24
25
29
30
30
31
32
3.5
3.5.1
3.5.2
3.5.3
4.
5.
TOPIC
3.6
3.7
3.8
3.9
3.9.1
3.9.2
Conclusion
References
CHAPTER 1
INTRODUCTION
Imagine yourself in the world where the users of the computer of todays internet
world dont have to run, install or store their application or data on their own computers,
imagine the world where every piece of your information or data would reside on the
Cloud (Internet).
1.2.1 Comparison:
Cloud computing is often confused with grid computing ("a form of distributed
computing whereby a 'super and virtual computer' is composed of a cluster of networked,
loosely-coupled computers, acting in concert to perform very large tasks"), utility
computing (the "packaging of computing resources, such as computation and storage, as
a metered service similar to a traditional public utility such as electricity") and autonomic
computing ("computer systems capable of self-management").
Indeed many cloud computing deployments as of 2009 depend on grids, have
autonomic characteristics and bill like utilities but cloud computing can be seen as a
natural next step from the grid-utility model. Some successful cloud architectures have
little or no centralized infrastructure or billing systems whatsoever, including peer-to-peer
networks like Bit Torrent and Skype and volunteer computing like
1.2.2 Implementation:
The majority of cloud computing infrastructure as of 2009 consists of reliable services
delivered through data centers and built on servers with different levels of virtualization
technologies. The services are accessible anywhere that has access to networking
infrastructure. The Cloud appears as a single point of access for all the computing needs
of consumers. Commercial offerings need to meet the quality of service requirements of
customers and typically offer service level agreements. Open standards are critical to the
growth of cloud computing and open source software has provided the foundation for
many cloud computing implementations.
1.2.3 Characteristics:
As customers generally do not own the infrastructure, they merely access or rent, they
can avoid capital expenditure and consume resources as a service, paying instead for
what they use. Many cloud-computing offerings have adopted the utility computing
model, which is analogous to how traditional utilities like electricity are consumed, while
others are billed on a subscription basis. Sharing "perishable and intangible" computing
7
power among multiple tenants can improve utilization rates, as servers are not left idle,
which can reduce costs significantly while increasing the speed of application
development. A side effect of this approach is that "computer capacity rises dramatically"
as customers do not have to engineer for peak loads. Adoption has been enabled by
"increased high-speed bandwidth" which makes it possible to receive the same response
times from centralized infrastructure at other sites.
1.2.4 Economics:
Cloud computing users can avoid capital expenditure (CapEx) on hardware, software
and services, rather paying a provider only for what they use. Consumption is billed on a
utility (e.g. resources consumed, like electricity) or subscription (e.g. time based, like a
newspaper) basis with little or no upfront cost. Other benefits of this time sharing style
approach are low barriers to entry, shared infrastructure and costs, low management
overhead and immediate access to a broad range of applications. Users can generally
terminate the contract at any time (thereby avoiding return on investment risk and
uncertainty) and the services are often covered by service level agreements with financial
penalties.
According to Nicholas Carr the strategic importance of information technology is
diminishing as it becomes standardized and cheaper. He argues that the cloud computing
paradigm shift is similar to the displacement of electricity generators by electricity grids
early in the 20th century.
1.2.5 Companies:
Providers including Amazon, Apple, Microsoft, Google, Sun and Yahoo exemplify the
use of cloud computing. It is being adopted by individual users through large enterprises
including General Electric, L'Oral, and Procter & Gamble.
CHAPTER 2
LITERATURE SURVEY
2.1 History:
The Cloud is a term with a long history in telephony, which has in the past decade,
been adopted as a metaphor for internet based services, with a common depiction in
network diagrams as a cloud outline.
The underlying concept dates back to 1960 when John McCarthy opined that
"computation may someday be organized as a public utility"; indeed it shares
characteristics with service bureaus which date back to the 1960s. The term cloud had
already come into commercial use in the early 1990s to refer to large ATM networks. By
the turn of the 21st century, the term "cloud computing" had started to appear, although
most of the focus at this time was on Software as a service (SaaS).
In 1999, Salesforce.com was established by Marc Benioff, Parker Harris, and his
fellows. They applied many technologies of consumer web sites like Google and Yahoo!
to business applications. They also provided the concept of "On demand" and "SaaS"
with their real business and successful customers. The key for SaaS is being customizable
by customer alone or with a small amount of help. Flexibility and speed for application
development have been drastically welcomed and accepted by business users.
IBM extended these concepts in 2001, as detailed in the Autonomic Computing
Manifesto -- which described advanced automation techniques such as self-monitoring,
self-healing, self-configuring, and self-optimizing in the management of complex IT
systems with heterogeneous storage, servers, applications, networks, security
mechanisms, and other system elements that can be virtualized across an enterprise.
10
12
13
CHAPTER 3
DISCUSSION
Device and location independence enable users to access systems using a web
browser regardless of their location or what device they are using, e.g., PC,
mobile. As infrastructure is off-site (typically provided by a third-party) and
accessed via the Internet the users can connect from anywhere.
Multi-tenancy enables sharing of resources and costs among a large pool of users,
allowing for:
o
Utilization and efficiency improvements for systems that are often only
10-20% utilized.
Reliability improves through the use of multiple redundant sites, which makes it
suitable for business continuity and disaster recovery. Nonetheless, most major
cloud computing services have suffered outages and IT and business managers are
able to do little when they are affected.
Scalability via dynamic ("on-demand") provisioning of resources on a finegrained, self-service basis near real-time, without users having to engineer for
14
Security typically improves due to centralization of data, increased securityfocused resources, etc., but raises concerns about loss of control over certain
sensitive data. Security is often as good as or better than traditional systems, in
part because providers are able to devote resources to solving security issues that
many customers cannot afford. Providers typically log accesses, but accessing the
audit logs themselves can be difficult or impossible.
3.2 Components:
Infrastructur
BitTorrent EC2 GoGrid Sun Grid 3tera
e
Platforms
Services
Storage
Standards
15
3.2.2 Application:
A cloud application leverages the Cloud in software architecture, often eliminating the
need to install and run the application on the customer's own computer, thus alleviating
the burden of software maintenance, ongoing operation, and support. For example:
3.2.3 Client:
A cloud client consists of computer hardware and/or computer software which relies
on cloud computing for application delivery, or which is specifically designed for
delivery of cloud services and which, in either case, is essentially useless without it. For
example:
3.2.4 Infrastructure:
Cloud infrastructure, such as Infrastructure as a service, is the delivery of computer
infrastructure, typically a platform virtualization environment, as a service. For example:
Management (RightScale)
Platform (Force.com)
3.2.5 Platform:
A cloud platform, such as Platform as a service, the delivery of a computing platform,
and/or solution stack as a service, facilitates deployment of applications without the cost
and complexity of buying and managing the underlying hardware and software layers.
For example:
Proprietary (Force.com)
3.2.6 Service:
A cloud service includes "products, services and solutions that are delivered and
consumed in real-time over the Internet". For example, Web Services ("software
system[s] designed to support interoperable machine-to-machine interaction over a
17
network") which may be accessed by other cloud computing components, software, e.g.,
Software plus service, or end users directly. Specific examples include:
3.2.7 Storage:
Cloud storage involves the delivery of data storage as a service, including databaselike services, often billed on a utility computing basis, e.g., per gigabyte per month. For
example:
3.3 Architecture:
Cloud architecture, the systems architecture of the software systems involved in the
delivery of cloud computing, comprises hardware and software designed by a cloud
architect who typically works for a cloud integrator. It typically involves multiple cloud
components communicating with each other over application programming interfaces,
usually web services.
This closely resembles the UNIX philosophy of having multiple programs doing one
thing well and working together over universal interfaces. Complexity is controlled and
the resulting systems are more manageable than their monolithic counterparts.
18
Cloud architecture extends to the client, where web browsers and/or software
applications access cloud applications.
Cloud storage architecture is loosely coupled, where metadata operations are
centralized enabling the data nodes to scale into the hundreds, each independently
delivering data to applications or user.
3.4 Types:
There are three type of cloud.
1. Public Cloud.
2. Private Cloud.
3. Hybrid Cloud.
19
20
Provider as they "will not have economies of scale to make it worth staying in the IT
business" or be able to afford private clouds.
The term has also been used in the logical rather than physical sense, for example in
reference to platform as service offerings, though such offerings including Microsoft's
Azure Services Platform are not available for on-premises deployment.
3.4.3 Hybrid cloud:
A hybrid cloud environment consisting of multiple internal and/or external providers
"will be typical for most enterprises".
21
3.5 Roles:
3.5.1 Provider:
A cloud computing provider or cloud computing service provider owns and operates
live cloud computing systems to deliver service to third parties. The barrier to entry is
also significantly higher with capital expenditure required and billing and management
creates some overhead. Nonetheless, significant operational efficiency and agility
advantages can be realized, even by small organizations, and server consolidation and
virtualization rollouts are already well underway. Amazon.com was the first such
provider, modernizing its data centers which, like most computer networks, were using as
little as 10% of its capacity at any one time just to leave room for occasional spikes. This
allowed small, fast-moving groups to add new features faster and easier, and they went
on to open it up to outsiders as Amazon Web Services in 2002 on a utility computing
basis.
3.5.2 User:
A user is a consumer of cloud computing. The privacy of users in cloud computing has
become of increasing concern. The rights of users are also an issue, which is being
addressed via a community effort to create a bill of rights.
3.5.3 Vendor:
A vendor sells products and services that facilitate the delivery, adoption and use of
cloud computing. For example:
3.6 Standards:
Cloud standards, a number of existing, typically lightweight, open standards, have
facilitated the growth of cloud computing, including:
Application
o
Syndication (Atom)
Client
o
Rows (AJAX)
Implementations
o
Platform:
o
Virtualization (OVF)\
Solution stacks (LAMP)
Service
o
Storage :
o
23
History:
Amazon announced a limited public beta of EC2 on August 25, 2006. Access to
EC2 was granted on a first come first served basis. EC2 became generally available
on October 23, 2008 along with support for Microsoft Windows Server.
Virtual machines:
EC2 uses Xen virtualization. Each virtual machine, called an "instance", functions
as a virtual private server in one of three sizes; small, large or extra large.
Amazon.com sizes instances based on "EC2 Compute Units" the equivalent CPU
capacity of physical hardware. One EC2 Compute Unit equals 1.0-1.2 GHz 2007
Opteron or 2007 Xeon processor. The system offers the following instance types:
Small Instance
The small instance (default) equates to "a system with 1.7 GB of memory, 1
EC2 Compute Unit (1 virtual core with 1 EC2 Compute Unit), 160 GB of instance
storage, 32-bit platform"
Large Instance
24
The large instance represents "a system with 7.5 GB of memory, 4 EC2
Compute Units (2 virtual cores with 2 EC2 Compute Units each), 850 GB
instance storage, 64-bit platform".
Extra Large Instance
The extra large instance offers the "equivalent of a system with 15 GB of
memory, 8 EC2 Compute Units (4 virtual cores with 2 EC2 Compute Units each),
1690 GB of instance storage, 64-bit platform."
High-CPU Instance
Instances of this family have proportionally more CPU resources than memory
(RAM) and address compute-intensive applications.
High-CPU Medium Instance
Instances of this family have the following configuration:
1.7 GB of memory
5 EC2 Compute Units (2 virtual cores with 2.5 EC2 Compute Units each)
32-bit platform
7 GB of memory
20 EC2 Compute Units (8 virtual cores with 2.5 EC2 Compute Units each)
64-bit platform
Pricing:
Amazon charges customers in two primary ways:
The hourly virtual machine rate is fixed, based on the capacity and features of the
virtual machine. Amazon advertising describes the pricing scheme as "you pay for
resources you consume," but defines resources such that an idle virtual machine is
consuming resources, as opposed to other pricing schemes where one would pay for basic
resources such as CPU time.
Customers can easily start and stop virtual machines to control charges, with Amazon
measuring with one hour granularity. Some are thus able to keep each virtual machine
running near capacity and effectively pay only for CPU time actually used.
As of March 2009, Amazon's time charge is about $73/month for the smallest virtual
machine without Windows and twelve times that for the largest one running Windows.
The data transfer charge ranges from $.10 to $.17 per gigabyte, depending on the
direction and monthly volume. Amazon does not have monthly minimums or account
maintenance charges.
Operating systems
When it launched in August 2006, the EC2 service offered Linux and later Sun
Microsystems' OpenSolaris and Solaris Express Community Edition. In October 2008,
EC2 added the Windows Server 2003 operating system to the list of available operating
systems.
Plans are in place for the Eucalyptus interface for the Amazon API to be packaged into
the standard Ubuntu distribution.
Persistent Storage:
Amazon.com provides persistent storage in the form of Elastic Block Storage (EBS).
Users can set up and manage volumes of sizes from 1GB to 1TB. The servers can attach
these instances of EBS to one server at a time in order to maintain data storage by the
servers.
26
Salesforce.com
Origins:
Salesforce.com was founded in 1999 by former Oracle executive Marc Benioff. In
June 2004, the company went public on the New York Stock Exchange under the stock
symbol CRM. Initial investors in salesforce.com were Marc Benioff, Larry Ellison,
Halsey Minor, Magdalena Yesil and Igor Sill, Geneva Venture Partners.
Current status:
Salesforce.com is headquartered in San Francisco, California, with regional
headquarters in Dublin (covering Europe, Middle East, and Africa), Singapore (covering
Asia Pacific less Japan), and Tokyo (covering Japan). Other major offices are in Toronto,
New York, London, Sydney, and San Mateo, California. Salesforce.com has its services
translated into 15 different languages and currently has 43,600 customers and over
1,000,000 subscribers. In 2008, Salesforce.com ranked 43rd on the list of largest software
companies in the world.
Following the Federal takeover of Freddie Mac and Fannie Mae in September 2008,
the S&P 500 removed the two mortgage giants after Wednesday, September 10, 2008,
and added Fastenal and Salesforce.com to the index, effective after Friday, September 12,
2008.
27
Service & Support, Partner Relationship Management, Marketing, Content, Ideas and
Analytics.
Force.com Platform
Salesforce.com Platform-as-a-Service product is known as the Force.com Platform.
The platform allows external developers to create add-on applications that integrate into
the main Salesforce application and are hosted on salesforce.com's infrastructure.
These applications are built using Apex (a proprietary Java-like programming language
for the Force.com Platform) and Visualforce (an XML-like syntax for building user
interfaces in HTML, AJAX or Flex).
AppExchange
Launched in 2005, AppExchange is a directory of applications built for Salesforce by
third-party developers which users can purchase and add to their Salesforce environment.
As of September 2008, there are over 800 applications available from over 450 ISVs.
Customization
Sales force users can customize their CRM application. In the system, there are tabs
such as "Contacts", "Reports", and "Accounts". Each tab contains associated information.
For example, "Contacts" has fields like First Name, Last Name, Email, etc.
28
Web Services
In addition to the web interface, Salesforce offers a Web Services API that enables
integration with other systems.
3.9.2 Reception:
Early reviews compared the operating system's user interface to Mac OS X and noted
the similarity of its browser to Google Chrome, although it is actually based on a
modified Mozilla Firefox browser.
Cloud can boot in just a few seconds. The operating system is designed for Netbooks,
Mobile Internet Devices, and PCs that are mainly used to browse the Internet. From
Cloud the user can quickly boot into the main OS, because Cloud continues booting the
main OS in the background.
4. Conclusion:
Cloud Computing is a vast topic and the above report does not give a high level
introduction to it. It is certainly not possible in the limited space of a report to do justice
30
to these technologies. What is in store for this technology in the near future? Well, Cloud
Computing is leading the industrys endeavor to bank on this revolutionary technology.
Cloud Computing Brings Possibilities..
Simplifies IT management
5. References:
[1]. www.wikipedia/cloud computing.com
[2]. www.infoworld.com/article/08/04/07/15FE-cloud-computing-reality_1.html
[3]. www.wiki.cloudcommunity.org/wiki/CloudComputing:Bill_of_Rights
[4]. www.davidchappell.com/CloudPlatforms--Chappell. PDF
[6]. www.thinkgos.com/cloud/index.html
[7]. www.salesforce.com
[8]. www.cloud computing.com
[9]. Chip Computer Magazine, December 2014 - Feb 2015 Edition
32
33