CLOUD COMPUTING

Kumar Gaurish
13810043

1


Table of Contents

1. Introduction .............................................................................................................................. 2
2. Types of clouds ......................................................................................................................... 5
3. Characteristics of Cloud computing ....................................................................................... 7
4. Methodology ........................................................................................................................... 10
i. Application: ...................................................................................................................... 10
ii. Platform: ........................................................................................................................... 10
iii. Infrastructure: ................................................................................................................... 11
5. Implementing Cloud Computing: ......................................................................................... 12
i. Private Clouds: .................................................................................................................... 12
ii. Public Clouds: .................................................................................................................... 12
iii. Hybrid Clouds: .................................................................................................................. 13
6. Architecture Of Cloud Computing ........................................................................................ 15
7. Advantages Of Cloud Computing ......................................................................................... 24
8. Barriers To Cloud Computing ................................................................................................ 28
9. Conclusion ............................................................................................................................... 31
10. Refrences. ................................................................................................................................ 32



2


1. Introduction

Cloud computing is the convergence and evolution of several concepts from
virtualization, distributed application design, grid, and enterprise IT
management to enable a more approach for deploying and scaling applications.


Cloud promises real costs savings and agility to customers. Through cloud
computing, a company can rapidly deploy applications where the underlying
technology components can expand and contract with the natural ebb and flow
of the business life cycle. Traditionally, once an application was deployed it was
bound to a particular infrastructure, until the infrastructure was upgraded. The
3


result was low efficiency, utilization, and flexibility. Cloud enablers, such as
virtualization and grid computing, allow applications to be dynamically
deployed onto the most suitable infrastructure at run time. This elastic aspect of
cloud computing allows applications to scale and grow without needing
traditionalfork-lift upgrades.
IT departments and infrastructure providers are under increasing pressure to
provide computing infrastructure at the lowest possible cost. In order to do this,
the concepts of resource pooling, virtualization, dynamic provisioning, utility
and commodity computing must be leveraged to create a public or private cloud
that meets these needs. World-class data centers are now being formed that can
provide this Infrastructure-as-a-Service (IaaS) in a very efficient manner.

4


Customers can thus decide to develop their own applications, to run on their
own internal private clouds, or leverage software as a SaaS application that run
on public clouds. Integration and federation of services across both the public
and private cloud, so-called hybrid clouds, is an emerging area of interest.
The public cloud concept allows customers to develop and deploy applications
with tremendous speedwithout the procurement and red-tape issues of dealing
with potentially slow moving and costly .













5


2. Types of clouds




There are different types of clouds that you can subscribe to depending on your
needs. As a home user or small business owner, you will most likely use public
cloud services.

1.Public Cloud:
A public cloud can be accessed by any subscriber with an internet connection
and access to the cloud space.

2. Private Cloud:
A private cloud is established for a specific group or organization and limits
access to just that group.

6


3. Community Cloud:
A community cloud is shared among two or more organizations that have
similar cloud requirements.




4. Hybrid Cloud:
A hybrid cloud is essentially a combination of at least two clouds, where the
clouds included are a mixture of public, private, or community.





7


3. Characteristics of Cloud computing
Dynamic computing infrastructure:

Cloud computing requires a dynamic computing infrastructure. The foundation
for the dynamic infrastructure is a standardized, scalable, and secure physical
infrastructure. There should be levels of redundancy to ensure high levels of
availability, but mostly it must be easy to extend as usage growth demands it,
without requiring architecture rework. Next, it must be virtualized.
A dynamic computing infrastructure is critical to effectively supporting the
elastic nature of service provisioning and de-provisioning as requested by users
while maintaining high levels of reliability and security. The consolidation
provided by virtualization, coupled with provisioning automation, creates a high
level of utilization and reuse, ultimately yielding a very effective use of capital
equipment.

IT service-centric approach:
Cloud computing is IT (or business) service-centric. This is in sharp contrast to
more traditional system- or server- centric models. In most cases, users of the
cloud generally want to run some business service or application for a specific,
timely purpose; they dont want to get bogged down in the system and network
administration of the environment. They would prefer to quick and easy access
a dedicated instance of an application or service. By abstracting away the
server-centric view of the infrastructure, system users can easily access
powerful pre-defined computing environments designed specifically around
their service.
8


An IT Service Centric approach enables user adoption and business agility the
easier and faster a user can perform an administrative task, the more expedient
the business moves, reducing costs or driving revenue.

Self-service based usage model:
Interacting with the cloud requires some level of user self-service. Best of breed
self-service provides users the ability to upload, build, deploy, schedule,
manage, and report on their business services on demand. Self-service cloud
offerings must provide easy-to-use, intuitive user interfaces that equip users to
productively manage the service delivery lifecycle.


Minimally or self-managed platform:
For an IT team or a service provider to efficiently provide a cloud for its
constituents, they must leverage a technology platform that is self-managed.
Best-of-breed clouds enable self-management via software automation,
leveraging the following capabilities:
9


1. A provisioning engine for deploying services and tearing them down
recovering resources for high levels of reuse
2. Mechanisms for scheduling and reserving resource capacity Capabilities
for configuring, managing, and reporting to ensure resources can be
allocated and reallocated to multiple groups of users
3. Tools for controlling access to resources and policies for how resources
can be used or operations can be performed
All of these capabilities enable business agility while simultaneously enacting
critical and necessary administrativecontrol.





10


4. Methodology

Cloud computing is broken down into three segments: "applications,"
"platforms," and "infrastructure".

i. Application:

So far, the applications segment of cloud computing is the only segment that has
proven successful as a business model. By running business applications over
the Internet from centralized servers rather than from on-site servers, companies
can cut some serious costs. Furthermore, while avoiding maintenance costs,
licensing costs and the costs of the hardware required to run servers on-site,
companies are able to run applications much more efficiently from a computing
standpoint.

On demand software services come in a few different varieties that may vary in
their pricing scheme and how the software is delivered to the end users. In the
past, the end-user would generally purchase a license from the software
provider and then install and run the software directly from on-premise servers.
ii. Platform:
Platforms serve as an interface for users to access applications provided by
partners or in some cases the customers.
The following companies are some that have developed platforms that allow
end users to access applications from centralized servers using the Internet.
Next is the name of the platform used by the company:
1. Google (GOOG) - Apps Engine
11


2. Amazon.com (AMZN) - EC2
3. Microsoft (MSFT) - Windows Live
4. Terremark Worldwide (TMRK) - The Enterprise Cloud
5. Salesforce.com (CRM) - Force.com
6. NetSuite (N) - Suiteflex
7. Mosso - Mosso, a division of Rackspace
8. Metrisoft - MetrisoftSaaS Platform
iii. Infrastructure:
The final segment in cloud computing, known as infrastructure, is the backbone
of the entire concept. Infrastructure vendors provide the physical storage space
and processing capabilities that allow all the services described above.







12


5. Implementing Cloud Computing:

All of the architectural and organizational considerations mentioned herein are
generally apply to all implementations of a cloud infrastructure. As we focus on
building the cloud, a number of models have been developed for deploying a
cloud infrastructure.
i. Private Clouds:

In a private cloud, the infrastructure for implementing the cloud is controlled
completely by the enterprise. Typically, private clouds are implemented in the
data center of the enterprise and managed by internal resources.
A private cloud maintains all corporate data in resources under the control of
the legal and contractual umbrella of the organization. This eliminates the
regulatory, legal and security concerns associated with information being
processed on third party computing resources.
The private cloud can also be used by existing IT departments to dramatically
reduce their costs and as an opportunity to shift from a cost canter to a value
centre in the eyes of the business.
ii. Public Clouds:

In a public cloud, external organizations provide the infrastructure and
management required to implement the cloud. Public clouds dramatically
simplify implementation and are typically billed based on usage. This transfers
the cost from a capital expenditure to an operational expense and can quickly be
scaled to meet the organizations needs. Temporary applications or applications
with burst resource requirements typically benefit from the public clouds
13


ability to ratchet up resources when needed and then scale them back when they
are no longer needed. In a private cloud, the company would need to provision
for the worst case across all the applications that share the infrastructure. This
can result in wasted resources when utilization is not at its peak.


iii. Hybrid Clouds:
To meet the benefits of both approaches, newer execution models have been
developed to combine public and private clouds into a unified solution.
Applications with significant legal, regulatory or service level concerns for
information can be directed to a private cloud. Other applications with less
stringent regulatory or service level requirements can leverage a public cloud
infrastructure.
14


Implementation of a hybrid model requires additional coordination between the
private and public service management system. This typically involves a
federated policy management tool, seamless hybrid integration, federated
security, information asset management, coordinated provisioning control, and
unified monitoring systems.


















15


6. ARCHITECTURE OF CLOUD COMPUTING


Figure-Cloud Computing Architecture
According to the proposed architecture each individual PC act as a cloud partner
which offers the necessary resources to the cloud system from its available
resources. However each of these individual PC is the property of a particular
educational institute whereas the institute owned those PCs from the budget
sanctioned by the government for that particular institute. There is a local server
associated with individual institute who monitors everything ranging from PC
status to individual requests for that institute. The users associated with a
particular local server submit their request to the cloud via the local server. The
local server collects the entire request from the clients in its domain within a
16


specific time period and forward those request after verification. In addition
there are some providers who have the agreement with the cloud system and
offers different services to the user.
A. Request Initialization Procedure:
According to our propose architecture each user terminal
communicates the local server for receiving services from cloud sides. The
procedure is depicted in figure .


The steps of the procedure are summarized bellow:
1. First of all user request is sent to local server with necessary user
identification information like user id and password.
17


2. The authentication module of local server verifies the user. It then sends a
form with appropriate graphical user interface (GUI)
according to the label of user.
3. User provides exact service specifications through the user interfaces. After
receiving the exact specification from user the local server verifies the current
available resources, policy to the cloud like pricing policy, encryption system
and other data security etc.
4. If the user does not have an agreement to receive the requested services or if
the pricing policy.
mismatches, the local server immediately informs the user for alternatives like
immediate payment or payment through credit card etc.
5. If the user agrees with the current policy it sends an acknowledgement reply
message to the local server.
6. The local server send the user the requested resource as soon as it receives the
resources from the cloud system.


18



B. Resource Monitoring Procedure:
In our architecture we are providing a facility of sharing the unused resources.
Thus there must be a process to identify the unused resources. The procedure of
resource identification is depicted in the figure with a flow diagram.
Figure-: Flow Diagram of Sharing Resource Information
The cloud system sends a periodic salutation message to each server associated
with an institute to find out the status of their respective clients. Each server
replicates several copy of that salutation message and forwards each copy to the
client under its domain. The server waits until it receives the Resource
Information Message from all of its clients. When all the information from the
client comes, the server generates a recapitulate message based on the
information that it collects from the client end and send back the message to the
cloud system.

C. Resource Allocation Procedure:
The server collects the request from each client under its domain at a particular
time interval. Thereafter the server summarizes the total requests by combining
them according to the individual group of services. As for example if the server
of an institute accepts two request
from two distinct clients one with 10 GB of storage and one antivirus software
and second one with 5 GB of storage along with an antivirus software and
visual C++ software at a particular then it just summarizes the request with 15
GB of storage along with two Antivirus software and a visual C++ software.
The cloud system as soon receiving the request from the server end it just send
19


15 GB of storage, images of the two antivirus software and the entire visual
C++ software or the part of the software if necessary after a verification.


INTERNAL ARCHITECTURE OF CLOUD CENTRAL SYSTEM

The Architecture of Cloud Central System composed of two sub-layers. The
upper sub-layer performs several operations prior to offer any service such as
authentication, credit verification, scheduling and security. In addition there is a
government central control system associated with the cloud upper sub-layer to
monitor the operation of the cloud system. On the other hand the lower sub-
layers basically offers four different types of services such as SAAS, PASS,
IAAS or e-Learning tools as a service based on the user demands.

1) The Upper Sub-layer:
20


Security is a massive issue in cloud system as the services are accessed over the
internet. Since the individual client has the options to choose their own security
methods like encryption process, cloud system has the agreement with local
server to understand the security methods so that it
can interpret them. As we mentioned that users at several levels constitute our
educational system and therefore request for services are different for those
diverse levels of users. Hence it is very important to maintain the access method
by identifying the types of users and services. This sub-layer defines a policy of
equilibrium between User and Provider by taking several factors into
consideration such as user level, latency and throughput. According to the
policy the government sets different priority for different levels of users so that
the user with higher priority can access the resources with lower latency. The
policy also ensures the provider to run the software smoothly with maximum
throughput and highest load balance. The Authentication and Credit
Verification sub-layer associated with the upper sub-layer checks for the
validity of the local server as soon as a request for resources is come from the
server end. This sub-layer also verifies the user credit information for the
requested service. If it finds that the user has sufficient balances for the
requested services it accept the request as a valid one and transform the request
to the lower sub-layer. As soon as the lower sub-layer confirms the request from
its available resource pool it adjusts the user account after deducting the amount
for the requested service. There are two subsections associated with the
Government Rules as Rule Based sub-layer of the architecture namely the
planning and monitoring committee. The planning committee decides the prices
for different types of services based on analysis and agreement with the cloud
partners. It also decides how much funding needs to be allocated for individual
organization. Normally several factors are considered when it allocates a
specific amount of budget for a particular institute such as the level of
21


education, student number, student quality, area of study and progression of that
institute. Furthermore it can enhance the budget if it finds that the user is
demanding more resources continuously through their submitted comments.
The corruption monitoring committee monitors the daily proceedings of every
institute. In addition it also observes the objections come from the user end.
There are several types of objections that can be come from the user end such as
the improper resource distribution, shortage of resources, inappropriate software
or unmatched software etc. So the corruption committee is responsible for
taking necessary initiatives to sort out the problem associated with the user end.
The committee has also the power to take any action against the authority of the
institute involving in corruptions.

2) The Lower Sub-layer:
The lower part of the architecture gives access to the particular resources
requested by the user. Once the upper layer sends positive acknowledgement to
the lower layer it offers the particular services to the requested user. The Service
Identification Panel associating with the lower layer identifies the particular
service requested by each individual user. The cloud client-vendor-partner
instrumental panel creates an interaction between the operations performed in
the front-end and backend. However, since the vendors can not operate
autonomously without the help of their partners so instrumental panels
responsibility is to create interaction between cloud partners with the cloud
vendors and clients. The layer contains an Operational Panel, whose task is to
monitoring the circumstances, handling the PCs and managing images. This
panel contains a script based tools for constructing, configuring, monitoring,
controlling and maintaining the clusters. This tool is known as Extreme
Administrator Toolkit (xCAT). Each request arrives from the server ends in the
22


form of bare-metal image format is first loaded on xCAT and then process by
virtual cloud system. However it is possible that the desired image that is
already loaded in its xCAT system can not be found in any available real or
virtual server. In such case it looks for any available server that fulfils the
specifications depicted in that image and the xCAT system vigorously load that
image. The implementation panel associated with the lower layer provides a
distinct platform for the execution of the virtual software. It also ensures the
deployment of the total virtual software or part of the software package
effectively without
installation on the operation surface. The exhibition panel supervises the
instances of virtual exhibit and agglomerates the desktop windows. Since the
execution of the software ensues the decentralized procedure on different
physical or virtual machines so this panel ensures that users can interact with
the presentation window of those de-centrally executed software.
23







24


7. ADVANTAGES OF CLOUD COMPUTING



Unlimited storage capacity:
Cloud computing offers virtually limitless storage.
Your computer's current 200 Gbyte hard drive is small compared
to the hundreds of Pbytes available in the cloud.
Whatever you need to store, you can.




25



Increased data reliability:
Unlike desktop computing, in which if a hard disk crashes and
destroy all your valuable data, a computer crashing in the cloud
should not affect the storage of your data.
That also means that if your personal computer crashes, all your
data is still out there in the cloud, still accessible.
In a world where few individual desktop PC users back up their
data on a regular basis, cloud computing is a data-safe computing
platform!
Improved performance:
With few large programs hogging your computer's memory, you
will see better performance from your PC.
Computers in a cloud computing system boot and run faster
because they have fewer programs and processes loaded into
memory

Reduced software costs:
Instead of purchasing expensive software applications, you can get
most of what you need for free-ish!
That is right - most cloud computing applications today, such as
the Google Docs suite, are totally free.
26


That is a lot better than paying $200+ for similar Microsoft Office software -
which alone may be justification for switching to cloud applications

Unlimited storage capacity:
Cloud computing offers virtually limitless storage.
Your computer's current 200 Gbyte hard drive is small compared to
the hundreds of Pbytes available in the cloud.
Whatever you need to store, you can.

Increased data reliability:
Unlike desktop computing, in which if a hard disk crashes and
destroy all your valuable data, a computer crashing in the cloud
should not affect the storage of your data.
That also means that if your personal computer crashes, all your
data is still out there in the cloud, still accessible.
In a world where few individual desktop PC users back up their
data on a regular basis, cloud computing is a data-safe computing
platform!
Universal document access:
That is not a problem with cloud computing, because you do not
take your documents with you.
Instead, they stay in the cloud, and you can access them whenever
you have a computer and an Internet connection.
27


All your documents are instantly available from wherever you are.
Latest version availability:
Another document-related advantage of cloud computing is that
when you edit a document at home, that edited version is what you
see when you access the document at work.
The cloud always hosts the latest version of your documents; as
long as you are connected, you are not in danger of having an
outdated version.














28


8. BARRIERS TO CLOUD COMPUTING

IT cloud services are still largely in the early adoption phase. As such, it is no
surprise that theres a long list of issues cloud services suppliers need to address
to drive mainstream adoption. Heres how our respondents rated nine of the
challenges commonly ascribed to the cloud services model.


i. Customer Perspective:

Data Security:Many customers dont wish to trust their data to the cloud.
Data must be locally retained for regulatory reasons.
Latency:The cloud can be many milliseconds away. Not suitable for real-
time applications.
Application Availability:Cannot switch from existing legacy applications.
Equivalent cloud applications do not exist.

29


ii. Vendor Perspective:
1. Service Level Agreements
Security: with the businesses information and critical IT resources
outside the firewall, customers worry about their vulnerability to attack.
Cloud services dependability: The complex web of interdependency that
supports cloud services availability and performance from network
availability and performance, to the availability and performance of
the cloud service providers systems, and beyond, to the performance and
availability of the supply chain of services that the service provider
depends on cries out for suppliers who can offer greater transparency of
interdependencies as well as credible service level assurances.
2. Business Models
SaaS/PaaS models are challenging.
Much lower upfront revenue.
While customers certainly enjoy the economic and operational benefits of
the off-the-shelf, standardized nature of many cloud services, this survey
shows they nonetheless want greater ability to fit cloud services more
tightly into the context of their specific business. Users want to
maximize the leverage of their many other critical business systems in-
house legacy systems and, increasingly, externally-sourced cloud services
by being able to integrate across these systems. SaaS 1.0 systems
that lack standard-based APIs, and are effectively islands are of
diminishing value; this is why user should be include the requirement for
web services APIs in definition of cloud services.
30



3. Customer Lock-in
Customers want open/standard APIs.
Need to continuously add value.










31


9. CONCLUSION

Cloud computing offers real alternatives to IT departments for improved
flexibility and lower cost. Markets are developing for the delivery of software
applications, platforms, and infrastructure as a service to IT departments over
the cloud. These services are readily accessible on a pay-per-use basis and
offer great alternatives to businesses that need the flexibility to rent
infrastructure on a temporary basis or to reduce capital costs.
Architects in larger enterprises find that it may still be more cost effective to
provide the desired services in-house in the form of private clouds to
minimize cost and maximize compatibility with internal standards and
regulations. If so, there are several options for future-state systems and technical
architectures that architects should consider finding the right trade-off between
cost and flexibility. Using an architectural framework will help architects
evaluate these trade-offs within the context of the business architecture and
design a system that accomplishes the business goal.










32


10. REFERENCES:

[1]M. Armbrust, A. Fox, R. Griffith, A. Joseph, R. Katz, A.Konwinski, G. Lee,
D. Patterson, A. Rabkin, I. Stoica, M.Zaharia. Above the Clouds: A Berkeley
View of Cloud computing. Technical Report No. UCB/EECS-2009-28,
University of California at Berkley, USA, Feb. 10, 2009.

[2] L. Vaquero, L. Merino, and J. Caceres."A break in the clouds: towards a
cloud definition".SIGCOMM Comp. Communications Review, vol. 39, pp.
5055 (2009).